System and method of scorekeeping athletic events

Abstract

A user interface for statistical recordation of a basketball game includes a player display including a plurality of selectable players; and a graphical display depicting at least a portion of a basketball court and including one or more two-point regions and one or more three-point regions, wherein each of the one or more two-point regions and the one or more three-point regions include a shot attempt toggle configured for selection of a shot make or a shot miss, wherein the player display and the graphical display are accessible on a single page of the user interface.

Description

CROSS-REFERENCE TO RELATED APPLICATION

[0001] This application claims the benefit of and priority to U.S. Provisional Application 63 / 748,071, titled “SYSTEM AND METHOD OF SCOREKEEPING ATHLETIC EVENTS”, filed January 22, 2025, the contents of which are incorporated by reference herein.TECHNICAL FIELD

[0002] The subject matter disclosed herein generally relates to the field of recording and tracking sports data and more particularly to devices, systems, and methods for scorekeeping athletic events with a computing device.BACKGROUND

[0003] Sports fans enjoy following live sporting events, either by attending in-person or through television or radio broadcasts. However, when these options are unavailable, alternative tools such as internet-based utilities enable fans to track game data and statistics in real time, using input from individuals at the event via internet-connected devices. Amateur events, including youth games, school sports, or recreational leagues, are rarely broadcast and typically rely on manual scorekeeping, leaving non-attendees without live updates. Manual scorekeeping is often inefficient and imprecise. Therefore, a new interface is needed to enhance the accuracy and quality of recorded statistics, and to improve the availability of live data for sports, such as amateur sports.SUMMARY

[0004] According to one aspect, a user interface for statistical recordation of a basketball game includes: a player display including a plurality of selectable players; and a graphical display depicting at least a portion of a basketball court and including one or more two-point regions and one or more three-point regions, wherein each of the one or more two-point regions and the one or more three-point regions include a shot attempt toggle configured for selection of a shot make or a shot miss, wherein the player display and the graphical display are accessible on a single page of the user interface.

[0005] According to one aspect, a user interface for statistical recordation of a basketball game includes a player display including a plurality of selectable players; a graphical display depicting at least a portion of a basketball court and including one or more two-point shot regions and one or more three-point shot regions, wherein each of the one or more two-point shot regions and the one or more three-point shot regions include a shot toggle configured for selection of a shot make or a shot miss; and; a first player action toggle configured to dynamically provide a first visual indication based on selection of a shot make; and a second player action toggle configured to dynamically provide a second visual indication based on selection of a shot miss.

[0006] According to one aspect, a method for statistical recordation of a basketball game includes receiving a player selection and a shot toggle selection from a user interface, wherein the user interface includes: a player display including a plurality of selectable players; a graphical display depicting at least a portion of a basketball court and including one or more two-point shot regions and one or more three-point shot regions, wherein each of the one or more two-point shot regions and the one or more three-point shot regions include a shot toggle configured for the shot toggle selection of a shot make or a shot miss; and a scoreboard including a first team score and a second team score; and updating the scoreboard when the shot toggle selection is the shot make, wherein updating the scoreboard includes (1) determining whether the shot make was selected within the one or more two-point shot regions or the one or more three-point shot regions; and (2) determining whether the player selection corresponds to the first team score or the second team score.BRIEF DESCRIPTION OF THE DRAWINGS

[0007] FIG. 1A illustrates a view of a user interface (UI) for recording and transmitting real-time sports data, according to some embodiments.

[0008] FIG. 1B illustrates a view of the UI for recording and transmitting real-time sports data, according to some embodiments.

[0009] FIG. 2A illustrates a view of the UI for recording and transmitting real-time sports data, according to some embodiments.

[0010] FIG. 2B illustrates a view of the UI for recording and transmitting real-time sports data where the user has initiated a data input, according to some embodiments.

[0011] FIG. 2C illustrates a view of the UI for recording and transmitting real-time sports data where the user has initiated a data input, according to some embodiments.

[0012] FIG. 2D illustrates a view of the UI for recording and transmitting real-time sports data in the scoreboard state, according to some embodiments.

[0013] FIG. 3A illustrates a view of the UI for recording and transmitting real-time sports data, according to some embodiments.

[0014] FIG. 3B illustrates a view of the UI for recording and transmitting real-time sports data where the user has initiated a data input, according to some embodiments.

[0015] FIG. 3C illustrates a view of the UI for recording and transmitting real-time sports data where the user has initiated a data input, according to some embodiments.

[0016] FIG. 3D illustrates a view of the UI for recording and transmitting real-time sports data where the user has initiated a data input, according to some embodiments.

[0017] FIG. 4A illustrates a view of a UI for recording and transmitting real-time sports data, according to some embodiments.

[0018] FIG. 4B illustrates a view of the UI for recording and transmitting real-time sports data where the user has initiated a data input, according to some embodiments.

[0019] FIG. 4C illustrates a view of the UI for recording and transmitting real-time sports data where the user has initiated a data input, according to some embodiments.

[0020] FIG. 5 illustrates a view of a play-by-play UI generating a display based on recorded data from the database, according to some embodiments.

[0021] FIG. 6 illustrates a view of a statistical analysis UI generating a display based on recorded data from the database, according to some embodiments.

[0022] FIG. 7 illustrates a view of a statistical comparison UI generated based on recorded data from the database, according to some embodiments.

[0023] FIG. 8 illustrates a view of a player statistic UI generated based on recorded data from the database, according to some embodiments.

[0024] FIG. 9 illustrates a flow chart of a method of statistical recordation of a live basketball game, according to some embodiments.

[0025] FIG. 10 illustrates a view of a UI for recording and transmitting real-time sports data, according to some embodiments.

[0026] FIG. 11 illustrates a method for statistical recordation of a basketball game, according to some embodiments.

[0027] FIG. 12 illustrates a system for analyzing sports data, according to some embodiments.DETAILED DESCRIPTION

[0028] The present disclosure describes systems and methods for recording and transmitting real-time sports data, including a user interface (UI) for inputting statistics to a database. The UI includes a player display to allow a user to select which player has completed a recordable action in the game. The user may select the recordable action (e.g., shot action such as a shot make or shot miss and / or a player action such as a steal, assist, turnover, etc.) via a plurality of labeled toggles. The UI includes a graphical display to allow the user to record or view the region where a recordable action (e.g., a basketball shot) was performed or attempted from. In some embodiments, the UI is a single-page display, with no pop ups, to enable efficient and accurate data inputs. If, for instance, the UI was multi-page and / or included pop-up prompts or menus, the scorekeeper may not be able to accurately keep pace with the real-time statistical recordation of the sports game (e.g., a basketball game), due at least in part to the fast-paced nature of sports games. Data input to the UI is stored in a database, and may be compiled to produce advanced statistical analysis, including, for instance, shot chart statistics by shot region.

[0029] Amateur events, including youth games, school sports, or recreational leagues, are rarely broadcast and typically rely on manual scorekeeping, leaving non-attendees without live updates. Manual scorekeeping of amateur sports is often inefficient and imprecise. Therefore, a new interface is needed to enhance the accuracy and quality of recorded statistics, and to improve the availability of live data for sports, such as amateur sports.

[0030] FIG. 1A is a view of a user interface (UI) 100 for recording and transmitting real-time sports data, according to some embodiments. The user interface (UI) 100 includes at least one of a tab selection portion 110, a dynamic banner 120, a first statistical input toggle 130, a graphical display 140, a second statistical input toggle 150, a player display 160, a player action toggle 170, a scoreboard section 180, and a control section 190. In some embodiments, the UI 100 includes a graphical display 140, a player display 160, a player action toggle 170, and a scoreboard section 180. In some embodiments, the UI 100 is configured to record statistical data and transmit the recorded data to a database 102. The database 102 may be a local database (i.e., local to the computing device displaying the UI 100) and / or may be a remote or cloud-based database.

[0031] Tab selection portion 110 includes one or more toggles configured for a user to change a setting, select a game, view a user, view database status, and / or view statistics. Dynamic banner 120 includes one or more real-time statistics of the sports game, such as one or more team scores and / or a possession indicator. First statistical input toggle 130, second statistical input toggle 150, and player action toggle 170 represent a recordable action and can be selected based on live recordable actions as they occur in the sports game. Tab selection portion 110, dynamic banner 120, first statistical input toggle 130, second statistical input toggle 150, and player action toggle 170 are discussed further in FIG. 1B.

[0032] In some embodiments, a “toggle” refers to a user-selectable control (or other selectable region) that enables selection between discrete options, pages, and / or states -often a pair of opposing states (e.g., selected / unselected), and may use a different visual appearance to indicate the current state. For scorekeeping and statistics, the toggle can be implemented broadly as any bounded on-screen region that, when selected, records (or changes) a game action or classification, including, by way of example, a switch-style toggle, a checkbox-style toggle, a toggle button, or a grouped set of toggle buttons configured for exclusive selection. For example, the toggle can include (i) a “shot make” toggle and a “shot miss” toggle presented as mutually exclusive toggle buttons such that selecting one deselects the other, or (ii) a single toggle that alternates between “shot make” and “shot miss” states while visually indicating the currently selected outcome. For example, on a computing device having a touch-sensitive display, the “shot make” toggle may define a touch-sensitive region corresponding to the displayed control, and the toggle may be selected based on a touch input detected within the region of the toggle (e.g., a tap within the region), causing the computing device to record a made-shot event for an identified player and / or time in the game.

[0033] Graphical display 140 illustrates at least a portion of a field, court, or playing surface. While graphical display 140 illustrates at least a portion of a basketball court in FIG. 1A, in other embodiments, graphical display can represent fields or courts for alternative sports, such as tennis, soccer, baseball, and football. Player display 160 can illustrate one or more player icons, which can be selectable. Scoreboard section 180 can illustrate statistical data of the current sports game, and control section 190 can include one or more selectable toggles for changing an input, removing a past input, re-adding a past input, or changing a setting. Graphical display 140, player display 160, scoreboard section 180, and control section 190 are discussed further in FIG. 1B.

[0034] The UI of the present disclosure may be included in a software application and / or webpage configured to operate on a computing device, such as a cellular phone, tablet, or other computing device. The computing device may be a mobile electronic device configured to communicate with a remote wireless network. The computing device includes a processor and memory, and the computing device may further include a display. The processor can include at least one processing component, such as a microcontroller, microprocessor, central processing unit (CPU), graphics processing unit (GPU), tensor processing unit (TPU), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA), neural processing unit (NPU), quantum processor, or the like, configured to execute instructions to perform the functions described herein. The memory can include at least one storage medium, such as a non-volatile memory component (e.g., a FLASH memory), volatile memory component (e.g., magnetic memory), or the like, configured to store executable instructions and / or data. The memory may include one or more memory components local to the computing device and / or coupled to the computing device via a network, such as a cloud storage medium. The processor can execute instructions stored by the memory.

[0035] The computing device includes a memory or data storage capable of storing and running the software application. The computing device may be configured for receiving inputs from a user, such as inputs of recordable events. The computing device may collect and receive data related to the event and distribute the data for public viewing. Data and statistics related to the event can be input into the computing device by a user. Data may include one or more of numeric data, photographic data, video data, and / or sound data. The data can be uploaded to a remote or cloud-based database. The data can be transmitted to the database 102. Data in database 102 can be viewed locally or remotely, such as on a separate editing user interface utilized for viewing recorded actions in chronological order. Accordingly, flagged recorded actions (discussed further herein) can be viewed and / or edited in the separate editing user interface during or after the game. The editing user interface can show all input data streams from multiple users that input data into database 102.

[0036] FIG. 1B is a view of the UI 100 for recording and transmitting real-time sports data, according to some embodiments. Individual toggles and labels for each of the tab selection portion 110, the dynamic banner 120, the first statistical input toggle 130, the graphical display 140, the second statistical input toggle 150, the player display 160, the player action toggle 170, the scoreboard section 180, and the control section 190 are shown.

[0037] The tab selection portion 110 may include at least one of an input tab 112, a play-by-play tab 114, a statistic summary and analysis tab 116, and a network upload 118 control. Input tab 112 can include a user selection toggle. Input tab 112 can illustrate the currently selected user of the displayed instance of UI 100. The play-by-play tab 114 and the analysis tab 116 are described in FIGS. 5-8, below. The UI 100 may default to local storage, i.e., transmitting the input statistical data to a local database (e.g., the database 102). The network upload 118 may be selected by the user to upload locally saved data to a remote network. In some embodiments, the network upload 118 may control whether the data is uploaded to a local database and / or uploaded to a remote database. For instance, the network upload 118 can be selected by the user to enable live, real-time upload of statistical data to the database 102 via a network connection to allow other users to view the data in real-time. In some embodiments, the network upload 118 may be selected by the user to upload locally saved data to a remote network. This allows support for the user device being offline and synching submissions when the user(s) have connectivity again.

[0038] The dynamic banner 120 may include a first team icon 122a and a second team icon 122b, a first team score 124a and a second team score 124b, and / or a possession toggle 126. The dynamic banner 120 is updated as statistics are recorded in real-time. For instance, if the first team makes a shot (and the shot is recorded via the UI 100), the first team score 124a is updated to reflect the made shot. In some embodiments, the user may select the possession toggle 126 to indicate which team has possession of the ball (i.e., which team is on offense). The possession toggle 126 may lock certain statistics based on which team has possession, as for example, the first team cannot record a 3-point make (via a three-point make toggle 152) if the first team does not have possession of the ball. Locking toggles based on possession may improve accuracy of the recorded statistics. In some embodiments, the toggles are not locked based on possession, as the tracking of live possession (via the possession toggle 126) may slow the recordation of real-time statistics.

[0039] The first statistical input toggle 130 may include a free throw (FT) make toggle 132, an FT miss toggle 134, a block toggle 136, and / or a steal toggle 138. In some embodiments, related statistics (e.g., FT make and FT miss) may be located adjacent to each other to aid the user in inputting data. For instance, the block toggle 136 and the steal toggle 138 are located adjacent to each other as they are both indicative of defensive statistics.

[0040] The graphical display 140 includes a plurality of shot regions, including for instance, three-point shot regions 142a, 142b, 142c, 142d, 142e, two-point shot regions 144a, 144b, 144c, 144d, 144e, and / or a paint region 146. The user can select where a shot attempt of the basketball game was attempted at, i.e., which shot region on the graphical display 140 the shot attempt took place.

[0041] The second statistical input toggle 150 may include a three-point make toggle 152, a three-point miss toggle 154, a two-point make toggle 156, and a two-point miss toggle 158. Related statistical toggles (e.g., the three-point make toggle 152 and the three-point miss toggle 154) may be positioned adjacent to each other, and in some embodiments, mirrored over a centerline. For instance, the miss toggles (e.g., the FT miss toggle 134, the three-point miss toggle 154, and the two-point miss toggle 158) may be positioned on a first side of the UI 100, and the make toggles (e.g., the FT make toggle 132, the three-point make toggle 152, and the two-point make toggle 156) may be positioned on a second side of the UI 100. The symmetric positioning of the make / miss toggles and the adjacent positioning of related statistical toggles improves efficiency and accuracy of statistical recordation of a live basketball game.

[0042] In some embodiments, selection of the three-point make toggle 152 or the three-point miss toggle 154 may lock the two-point shot regions 144a, 144b, 144c, 144d, 144e and paint region 146 from being selected. Likewise, selection of the two-point make toggle 156 or two-point miss toggle 158 may lock the three-point shot regions 142a, 142b, 142c, 142d, 142e from being selected. Locking the shot region based on the recorded location of the shot attempt may improve efficiency and accuracy of statistical recordation of a live basketball game.

[0043] In some embodiments, the shot attempt (including make / miss and point total) can be recorded solely via interaction with the graphical display 140. For instance, selection of one of the three-point shot regions 142a, 142b, 142c, 142d, 142e will narrow the statistical input options to either a three-point make or a three-point miss. A single tap may indicate a miss, and a double tap (or press and hold) may indicate a make. Thus, the shot location, shot type (three-point versus two-point), and make / miss status may be recorded solely with the graphical display 140 (see, e.g., FIGS. 4A-C). This may be beneficial, as it reduces the number of toggles on the UI 100, thereby improving efficiency and accuracy of statistical recordation of a live basketball game.

[0044] The player display 160 includes a plurality of selectable players. The player display can include a plurality of first selectable players corresponding to a first team and / or a plurality of second selectable players corresponding to a second team. In some embodiments, the player display shows a plurality of first selectable players corresponding to the first team and hides the plurality of second selectable players corresponding to the second team. In other embodiments, the player display shows an icon for a first team and an icon for a second team, where the team as a whole is selectable in place of an individual player. In one example, the player display 160 includes at least one of a plurality of bench players 164a, 164b, 164c, 164d, a plurality of on-court players 166a, 166b, 166c, 166d, 166e, a first team icon 168, and an edit toggle 162 to modify player status (in-game versus bench). Database 102 can store the amount of time each player is on the court and / or on the bench.

[0045] In some embodiments, the player display 160 includes a dynamic scroll, where the list of players can scroll (e.g., vertically scroll). In some embodiments, the edit toggle 162 allows players to be swapped, e.g., a bench player can be selected and an in-game player can be selected to swap positions. The plurality of on-court players 166a, 166b, 166c, 166d, 166e may be selectable to associate a player with a given action. For instance, a block may occur in-game, and to record the block, the user may select the block toggle 136 and select the on-court player 166a to associate the player with the block. In some embodiments, the player display 160 includes a foul indicator on each player. For instance, the on-court player 166a in FIG. 1B has four fouls. In some embodiments, the foul indicator is color-coded to indicate caution (e.g., red or yellow) when a player is approaching the maximum number of fouls prior to disqualification.

[0046] The player action toggle 170 may include at least one of an assist toggle 172, a turnover toggle 174, an offensive rebound toggle 176, a defensive rebound toggle 178, and a possession indicator 175. Related statistical toggles (e.g., offensive rebound toggle 176 and the defensive rebound toggle 178) may be positioned adjacent to each other, and in some embodiments, mirrored over a centerline.

[0047] The player action toggle 170 can include a first player action toggle and a second player action toggle. The first player action toggle can include at least one of assist toggle 172, turnover toggle 174, offensive rebound toggle 176, defensive rebound toggle 178, and possession indicator 175. The second player action toggle can include at least one of assist toggle 172, turnover toggle 174, offensive rebound toggle 176, defensive rebound toggle 178, and possession indicator 175. In some embodiments, the first player action toggle and the second player action toggle are different.

[0048] The first player action toggle (e.g., button or button region) can dynamically adjust based on a selected input from the user. In some embodiments, the first player action toggle dynamically adjusts based on a selected shot attempt. In this example, the first player action toggle can dynamically adjust when a shot toggle, configured for selection of a shot make or a shot miss, has been selected. For example, the first player action toggle is configured to dynamically adjust when a shot make is selected. Dynamically adjusting can include providing a first visual indication. In one example, the first visual indication includes an appearance change, such as a change in color, opacity, and / or brightness. In another example, the first visual indication includes transforming from a visually hidden state to a visually appearing state.

[0049] During utilization of the UI, a shot make can be selected. The shot make can be selected in conjunction with a selected player. When a shot make is selected, such as via selection of one of the regions of the graphical display 140 (see, e.g., FIGS. 4A-C), the first player action toggle can immediately, or within a time frame (e.g., less than 1 second or less than 3 seconds), dynamically adjust to highlight a possible coordinated selection to the user. For example, when a shot attempt is a shot make, it is likely there is a coordinated selection, such as assist toggle 172, that the user would like to select. An assist is a coordinated selection with a shot make because a scorekeeper typically records an assist right after a shot make, since an assist in basketball is only awarded when the last pass leads directly to a score, so it cannot be confirmed until the shot attempt is a shot make. Therefore, when a shot attempt is a shot make and the user selects a shot make, the first player action toggle can exhibit a first visual indication that includes an appearance change, such as a change in color, opacity, and / or brightness, to indicate a possible coordinated selection. By indicating a possible coordinated selection to the user, the scorekeeping efficiency can be increased, as the first visual indication can quickly guide the user to a likely coordinated selection. Additionally, the scorekeeping accuracy can be improved by automatically indicating possible coordinated selection(s) to the user. The user can decide whether to select the first player action toggle based on the outcome in the game. The first visual indication can appear without a pop-up window or menu.

[0050] The second player action toggle (e.g., button or button region) can dynamically adjust based on a selected input from the user. In some embodiments, the second player action toggle dynamically adjusts based on a selected shot attempt. In this example, the second player action toggle can dynamically adjust when a shot toggle, configured for selection of a shot make or a shot miss, has been selected. For example, the second player action toggle is configured to dynamically adjust when a shot miss is selected. Dynamically adjusting can include providing a first visual indication. In one example, the first visual indication includes an appearance change, such as a change in color, opacity, and / or brightness. In another example, the first visual indication includes transforming from a visually hidden state to a visually appearing state.

[0051] During utilization of the UI, a shot miss can be selected. The shot miss can be selected in conjunction with a selected player. When a shot miss is selected, such as via selection of one of the regions of the graphical display 140 (see e.g., FIGS. 4A-C), the second player action toggle can immediately, or within a time frame (e.g., less than 1 second or less than 3 seconds), dynamically adjust to highlight a possible coordinated selection to the user. For example, when a shot attempt is a shot miss, it is likely there is a coordinated selection, such as offensive rebound toggle 176 or defensive rebound toggle 178, that the user would like to select. A rebound (e.g., offensive rebound or defensive rebound) is a coordinated selection with a shot miss because a rebound is only credited once a shot is missed and a player (or team) secures the live ball, so scorekeepers record it after the shot miss when possession is established. Therefore, when a shot attempt is a shot miss and the user selects a shot miss, the second player action toggle can exhibit a first visual indication that includes an appearance change, such as a change in color, opacity, and / or brightness, to indicate a possible coordinated selection. By indicating a possible coordinated selection to the user, the scorekeeping efficiency can be increased. Additionally, the scorekeeping accuracy can be improved by automatically indicating possible coordinated selection(s) to the user. The user can decide whether to select the second player action toggle based on the outcome in the game.

[0052] The scoreboard section 180 may include a first foul indicator 182a, a second foul indicator 182b, a first timeout indicator 184a, a second timeout indicator 184b, an edit toggle 186, and / or a timer 188. In some embodiments, dynamic banner 120 and scoreboard section 180 can be combined as one region or section. Accordingly, one or more features / configurations of dynamic banner 120 can be combined with one or more features / configurations of scoreboard section 180. The first foul indicator 182a and the second foul indicator 182b may indicate bonus and / or double bonus based on the number of recorded fouls. The control section 190 may include an undo toggle 192 and a redo toggle 194. The undo toggle 192 and / or the redo toggle 194 may enable the user to quickly remove / add statistical inputs with one click, i.e., instead of bringing up an edit screen.

[0053] User interfaces of the present disclosure can be a single-page user interface for inputting statistical data of a live basketball game. The single-page user interface can be a single rendered user-interface view (e.g., one viewport) that is presented as a single, continuous page to the user, such that the relevant toggles (e.g., buttons) and graphical displays are available within that same view rather than being moved to a different page or screen. For example, the toggles and graphical displays may be laid out so that, within the same viewport, the user can directly view and select the toggles while simultaneously viewing the associated graphical displays. The single-page user interface can include implementations where the toggles and graphical display(s) remain on the same page even if the user scrolls within that page (e.g., the user interface is not replaced by a different page / screen), and where additional options are not presented via an overlaid popover / popup menu that appears on top of the page.

[0054] For example, the UI 100 does not include pop-up prompts and does not require the user to leave the single-page user interface to enter statistics. The UI 100 provides shot-attempt location data (via the graphical display 140) on the single-page user interface. The dynamic banner 120, the first statistical input toggle 130, the graphical display 140, the second statistical input toggle 150, the player display 160, the player action toggle 170, the scoreboard section 180, and the control section 190 are static regions (i.e., each region is fixed on the display, although the toggles, prompts, banners may dynamically update as the game progresses), and therefore, the user can access all relevant toggles, controls, and displays all at once—without needing to scroll through or select the proper prompt. The single-page configuration is beneficial, as the user can access inputs to all relevant statistical data on a single screen without going through a series of pop-up and / or prompts, which thereby improves the efficiency and accuracy of data recordation. If, for instance, the user interface was multiple pages, input of statistics may fall behind the actual pace of play of the basketball game, leading to inaccuracies and missed statistics.

[0055] FIG. 2A is a view of the UI 100 for recording and transmitting real-time sports data, according to some embodiments. The UI 100 in FIG. 2A is in a scoreboard state, i.e., a data input has not been initiated by the user, and the dynamic banner 120 displays the game score.

[0056] FIG. 2B is a view of the UI 100 for recording and transmitting real-time sports data where the user has initiated a data input, according to some embodiments. For instance, the user has selected the steal toggle 138, which generates a bolded steal toggle 238. Bolded toggles, such as bolded steal toggle 238, can exhibit at least one visual appearance change compared to the unselected toggle, such as steal toggle 138. For example, bolded steal toggle 238 can exhibit bolded text characters, such as the text “steal” in bold characters. In another example, and as shown in FIG. 2B, bolded steal toggle 238 includes a bold border surrounding the toggle region.

[0057] The selection of the steal toggle 138 can lock one or more other controls / toggles of the UI 100, including, for example, the graphical display 140. A locked graphical display basketball court 240 is generated from the selection of the steal toggle 138. In some embodiments, the dynamic banner 120 is updated when the user initiates a data input. For instance, a steal statistic banner 220 is generated when the user initiates input of a steal statistic. The steal statistic banner 220 displays the total number of team steals, and in some embodiments, includes a comparison between the first team steals and the second team steals. The dynamic banner 120 may be updated to correspond to the type of statistic input by the user, e.g., for input of a block statistic, the dynamic banner 120 may be updated to display total team blocks.

[0058] FIG. 2C is a view of the UI 100 for recording and transmitting real-time sports data where the user has initiated a data input, according to some embodiments. The user has selected the on-court player 166e, which thereby generates a bolded player icon 266e. Thus, the on-court player 166e has been associated with a steal statistic. The dynamic banner 120 is updated to an individual steal banner 222. The individual steal banner 222 displays the total number of steals associated with the selected player. Upon selection of both the action (the steal toggle 138) and the player (the on-court player 166e), a filled steal icon 239 is generated and a confirmation icon 204 is generated. The filled steal icon 239 and / or the confirmation icon 204 confirms that the statistic has been recorded. The individual steal banner 222 may provide an additional confirmation to the user that the correct player has been selected.

[0059] If, for instance, an incorrect player or statistic is recorded, the user may use the control section 190, and specifically the undo toggle 192 and / or the redo toggle 194 to go back / forward to fix errors. For example, if the user selects both the action (the steal toggle 138) and the player (the on-court player 166e), as shown in FIG. 2C, the undo toggle 192 will undo the most recent input (e.g., the selection of the on-court player 166e in this case), and the UI 100 will return to the display of FIG. 2B.

[0060] When both the action (the steal toggle 138) and the player (the on-court player 166e) are selected and the user is satisfied with the input statistics (e.g., verifies that the dynamic banner 120 includes the correct player and stat), the UI may return to the scoreboard state. FIG. 2D is a view of the UI 100 for recording and transmitting real-time sports data in the scoreboard state, according to some embodiments. The input statistic is saved in a local database (e.g., the database 102) and / or uploaded to a network database (e.g., the database 102).

[0061] FIG. 3A is a view of the UI 100 for recording and transmitting real-time sports data, according to some embodiments. The UI 100 in FIG. 3A is in a scoreboard state, i.e., a data input has not been initiated by the user, and the dynamic banner 120 displays the game score.

[0062] FIG. 3B is a view of the UI 100 for recording and transmitting real-time sports data where the user has initiated a data input, according to some embodiments. For instance, the user has selected the two-point miss toggle 158, which generates a bolded two-point miss display 358. The input of a two-point shot attempt may activate the graphical display 140 and may activate the dynamic banner 120 to generate a two-point shot banner 320. The two-point shot banner 320 displays team statistics of two-point shot make / misses and / or percentage, and in some embodiments, includes a comparison between the first team and the second team.

[0063] FIG. 3C is a view of the UI for recording and transmitting real-time sports data where the user has initiated a data input, according to some embodiments. The user has selected a shot region on the graphical display 140, namely, the two-point shot region 144d, which generates a bolded (and / or highlighted) shot region 344d in an activated graphical display basketball court 340. The shot region selected by the user is indicative of the region on the basketball court where the shot attempt occurred.

[0064] FIG. 3D is a view of the UI 100 for recording and transmitting real-time sports data where the user has initiated a data input, according to some embodiments. The user has selected the on-court player 166e, which thereby generates a bolded player icon 366e. Thus, the on-court player 166e has been associated with a two-point miss statistic from the two-point shot region 144d. The activated graphical display basketball court 340 (and / or the graphical display 140) is updated to include a confirmation icon 304, and the dynamic banner 120 is updated to include an individual scoring banner 322. The bolded two-point miss display 358 can be updated to a filled two-point miss display 360, and the filled two-point miss display 360 may include a confirmation icon like confirmation icon 304.

[0065] The individual scoring banner 322 may include total points, field goal attempts, field goal makes, three-point attempts, and / or three-point makes. In some embodiments, the individual scoring banner 322 may include a bolded (or highlighted) display of the most recent statistical scoring input, i.e., in this case, a two-point miss. The individual scoring banner 322 may include a player icon, a player number, and / or a player name. The confirmation icon 304 and the individual scoring banner 322 provide an efficient confirmation that the relevant statistic was entered into the database and an efficient double-check for the user that the input statistic was accurate (correct action and correct player). After a delay period (e.g., 2 seconds), the UI 100 will revert back to the scoreboard state shown in FIG. 3A, with an updated score if points were scored.

[0066] FIG. 4A is a view of a UI 400 for recording and transmitting real-time sports data, according to some embodiments. The UI 400 in FIG. 4A is in a scoreboard state, e.g., a data input has not been initiated by the user, and the dynamic banner 120 displays the game score. In some embodiments, the UI 400 does not include the second statistical input toggle 150, the three-point make toggle 152, the three-point miss toggle 154, the two-point make toggle 156, and / or the two-point miss toggle 158. The shot make / miss can be recorded solely with the graphical display 140 of the UI 400. In one non-limiting example, the player display and the graphical display are accessible on a single page of the user interface.

[0067] UI 400 can include graphical display 140 depicting at least a portion of a basketball court and including one or more two-point regions and one or more three-point regions, wherein each of the one or more two-point regions and the one or more three-point regions include a shot attempt toggle configured for selection of a shot make or a shot miss. In one example, the shot attempt toggle fills the entire region that the shot attempt toggle is included within. For example, a user can click anywhere within a single region to select a shot make or a shot miss. As an example, activated two-point shot region 444d is shown in FIG. 4B. In other embodiments, the shot attempt toggle fills a portion of the region that the shot attempt toggle is included within.

[0068] During utilization, for example, a region of graphical display 140 can be selected based on an outcome of the game. For example, each region can be toggled for selection of a shot make or a shot miss. In some embodiments, the “toggle” refers to a user-selectable control (or other selectable region) that enables selection between discrete states and may use different visual appearances to indicate the current / selected state.

[0069] In some embodiments, each of the one or more two-point regions and the one or more three-point regions include a shot attempt toggle having a first discrete state, a second discrete state, and a third discrete state. The first discrete state is an unselected state, such as that of two-point shot region 144d. The second discrete state is representative of a shot miss, such as that of shot region 344d. The third discrete state is representative of a shot make. The user can select a region of graphical display 140 to switch between the discrete states, with various orders possible. For example, a single tap of a mobile device having a touch screen can convert a region to the second discrete state, and a double tap can convert the region to a third discrete state.

[0070] Data can be sent to database 102 when the second discrete state or the third discrete state is selected. In some embodiments, data is sent to database 102 once the second discrete state or the third discrete state is selected in coordination with a selected player. Data can be sent to the database 102 immediately upon selection, or can be sent after 0.5 seconds, after 1 second, or after 2 seconds of selecting the second discrete state or the third discrete state – allowing the user a chance to toggle through discrete states before data is sent to database 102.

[0071] FIG. 4B is a view of the UI 400 for recording and transmitting real-time sports data where the user has initiated a data input, according to some embodiments. For instance, the user has selected the two-point shot region 144d. The selection of the two-point shot region 144d with a single tap may indicate a missed shot from that region. In some embodiments, the selection of the two-point shot region 144d with a double tap and / or press-and-hold may indicate a made shot from that region. The graphical display 140 may be activated when the user selects a region, generating an activated graphical display basketball court 440. The activated graphical display basketball court 440 may display a first color (e.g., red) to indicate a missed shot input and a second color (e.g., green) to indicate a made shot input. FIG. 4B shows a missed-shot input on activated two-point shot region 444d. Input of a shot attempt may alter the dynamic banner 120 to display a shot banner 420. The shot banner 420 displays team statistics of shot make / misses and / or percentage, and in some embodiments, includes a comparison between the first team and the second team.

[0072] FIG. 4C is a view of the UI 400 for recording and transmitting real-time sports data where the user has initiated a data input, according to some embodiments. The user has selected the on-court player 166e, which thereby generates a bolded player icon 466e. Thus, the on-court player 166e has been associated with a two-point miss statistic from the two-point shot region 144d. The activated graphical display basketball court 440 (and / or the graphical display 140) is updated to include a confirmation icon 404. The confirmation icon 404 and the shot banner 420 provide an efficient confirmation that the relevant statistic was entered into the database and an efficient double-check for the user that the input statistic was accurate (correct action and correct player). After a delay period (e.g., 2 seconds), the UI 400 will revert back to the scoreboard state shown in FIG. 4A, with an updated score if points were scored. While FIG. 4C demonstrates that the on-court player 166e has been associated with a two-point miss statistic from the two-point shot region 144d after the two-point shot region 144d has been selected, in other embodiments the on-court player 166e can be selected before the shot region is selected.

[0073] The UI 400 provides a simplified display (as compared to the UI 100), as there are fewer input toggles and static sections to choose from. Shot attempts, shot makes (and thereby points scored), and shot location can be recorded from the graphical display 140. The scoring statistics recorded via the graphical display 140 can be associated with a player via the player display 160. The UI 400 thereby enables a user to record advanced basketball scoring statistics of a live basketball game with a minimum of two clicks (a first click for shot attempt location and make / miss status, and a second click for player). The two-click (or two input) statistical recordation provides quick and accurate recordation of player statistics from a single UI screen (no pop-up prompts nor multi-page UI).

[0074] The scoreboard can be updated based on selection of a shot region in UI 400. The scoreboard can be updated when the shot toggle selection is a shot make. Updating the scoreboard can include (1) determining whether the shot make was selected within the one or more two-point shot regions or the one or more three-point shot regions; and (2) determining whether the player selection corresponds to the first team score or the second team score. Updating the scoreboard is discussed further in method 1100.

[0075] Multiple users / scorekeepers can input recordable actions (sequentially, contemporaneously, and / or simultaneously) into UI 100, UI 400, and / or UI 1000 (discussed in FIG. 10), such as on multiple computing devices. In some embodiments, the system supports concurrent scorekeeping / input by multiple users during a single game session. For example, two or more scorekeepers may each operate a respective computing device (e.g., smartphone, tablet, laptop, or other computing device) executing an instance of the software to input recordable actions in real time as game events occur. The multiple computing devices may be associated with a synchronized game timeline such that the recordable actions entered on any device are communicated to database 102 and may be reflected to the other devices substantially contemporaneously. In this manner, the system enables simultaneous, multi-device entry of recordable actions for the same game, including entries made by different users for different teams, players, or player action types, while maintaining a unified record of game scoring and statistics.

[0076] The multiple computing devices may be associated with a synchronized game timeline such that the recordable actions entered on any device are communicated to database 102, with a recordable action being coordinated with a game time. Multiple computing devices can be in communication with each other using near-field communication. Multiple computing devices can be used without network connection, as data from the multiple devices can later be uploaded to database 102 and can be associated with a synchronized game timeline.

[0077] Regarding utilizing multiple users, one or more users can be designated as a primary scorekeeper(s). In some embodiments, a recordable action input by the primary scorekeeper(s) can alter the first team score or the second team score (e.g., shown in dynamic banner 120). In one example, the first team can designate a first primary scorekeeper to record score for the first team, and the second team can designate a second primary scorekeeper to record score for the second team. In another example, a primary scorekeeper inputs scores for both the first team and the second team, altering both the first team score and the second team score in real time. The computing devices may be associated with a synchronized game timeline such that the recordable actions entered by the primary scorekeeper(s) are communicated to database 102 and may be reflected to the other computing devices substantially contemporaneously.

[0078] In some embodiments, users other than the primary scorekeeper(s) may input recordable actions that do not change the first team score and the second team score. For example, users other than the primary scorekeeper(s) may select a player action toggle, where data indicative of the selected player action toggle is sent to database 102. In other embodiments, users other than the primary scorekeeper(s) may input recordable actions that do not alter data sent to database 102, where the recordable actions are stored locally for the individual user to view live or at a later time. Distinct settings can be applied to each user to alter capabilities of the individual user.

[0079] Multiple users can be utilized for entering distinct statistics throughout the game. For example, a first user can be designated to enter shot attempts, while a second user can be designated to enter rebounds. The first user can designate themselves as the shot attempt recorder, and UI 100, UI 400, and / or UI 1000 can notify other users of this designation. UI 100, UI 400, and / or UI 1000 can also notify users of open designations that have not been selected by any other user, such as player fouls.

[0080] As discussed, multiple users can input recordable actions (sequentially, contemporaneously, and / or simultaneously) into UI 100, UI 400, and / or UI 1000, such as on multiple computing devices. All, or a portion, of the data from multiple users can be sent to database 102. In some embodiments, the system receives data, from a first user using a first instance of the user interface, to database 102 and determines whether to update one or more distinct instances based on the data from the first user. In one example, the determination is made based on the user settings. The system can determine whether to update based on the designated user type, such as a primary scorekeeper. For example, if the first user is a primary scorekeeper, the system updates one or more distinct instances based on the data input by the first user. For example, when a primary scorekeeper selects a shot make, the system can update dynamic banner 120 (for all users viewing the game) by updating a team score based on which player was selectively coordinated with the shot make. Updating the team score can include updating the team score on multiple client devices running the software application including UI 100, UI 400, and / or UI 1000.

[0081] FIG. 5 is a view of a play-by-play UI 500 generating a display based on recorded data from the database 102, according to some embodiments. The play-by-play UI 500 may be accessed via the play-by-play tab 114 on the UI 100. Alternatively, or additionally, play-by-play UI 500 can be accessed via a distinct computing device, such as a tablet or laptop computer. The play-by-play UI 500 includes a score banner 520 which displays the current game score of the live basketball game (or final score if the game is completed). The score banner 520 includes a filter toggle 522 to filter by team, player, statistic type, etc. Each play of the play-by-play log includes one or more of time, team, brief description of play, score, player, and upload status. For instance, a local database icon 524 may be displayed when the data has been stored locally on the electronic device, and an upload complete icon 526 may be displayed when the data is uploaded to a network database.

[0082] FIG. 6 is a view of a statistical analysis UI 600 generating a display based on recorded data from the database 102, according to some embodiments. The statistical analysis UI 600 includes a graphical display 640. The graphical display 640 includes a plurality of three-point shot regions 642a, 642b, 642c, 642d, 642e, a plurality of two-point shot regions 644a, 644b, 644c, 644d, 644e, and a paint region 646. The graphical display 640 displays a summary of shot attempts and shot makes per region of the court, based on data input into the graphical display 140. For instance, the graphical display 640 shows one shot attempt from the three-point shot region 642c, and zero shot makes from the three point shot region 642c. The graphical display 640 may be color coded based on a shooting percentage. For instance, regions where the shooting percentage (percentage of field goal makes versus attempts) exceeds 50% may be a first color (e.g., green), regions where the shooting percentage is between 20%-50% may be a second color (e.g., yellow), and regions where the shooting percentage is less than 20% may be a third color (e.g., red). The thresholds and colors may be modified by the user. Other visual appearances can be utilized in addition, or alternatively, to colors.

[0083] The graphical display 640 may provide live-game insights based on the data recorded by the UI 100 or UI 400. For instance, a team may target shots from the regions on the court where shooting percentage is high—and avoid taking shots from regions where shooting percentage is low. The graphical display 640 may highlight areas of improvement for teams, e.g., if shooting percentage along the baseline is low, the team may recognize the deficiency and practice shooting from the baseline.

[0084] In some embodiments, the graphical display 640 may be generated for each player, if, for instance, the user selects a player from the player display 160. The graphical display 640 can be used by players and coaches to recognize strengths and weaknesses of an individual player, and highlight areas of improvement (e.g., three-point shooting from the right side) to practice.

[0085] The statistical analysis UI 600 may include a first team toggle 662, a second team toggle 668, and a comparison toggle 664. The statistical analysis UI 600 shown in FIG. 6 has selected the comparison toggle 664. Each statistical category, e.g., a field goal made stat 652 and a two-point made stat 654 may include a comparison between the first team and the second team.

[0086] FIG. 7 is a view of a statistical comparison UI 700 generated based on recorded data from the database 102, according to some embodiments. Data from the database 102, recorded via the UI 100 or UI 400, may be compiled into first team statistics 706a and second team statistics 706b. The data may be displayed side-by-side to allow a user to compare the respective stats. FIG. 8 is a view of a player statistic UI 800 generated based on recorded data from the database 102, according to some embodiments. Data from the database 102, recorded via the UI 100 or UI 400, may be compiled into player statistics 808. The data may be displayed by category.

[0087] FIG. 9 is a flow chart of a method 900 of statistical recordation of a live basketball game, according to some embodiments. Method 900 includes providing 910 a user interface (UI). The UI may include any and / or all features of the UI 100 and / or UI 400 described above. The UI may be provided / accessed on an electronic device, including for instance, a computing device such as a tablet or smart phone. A shot region is selected 920 from the plurality of shot regions on the graphical display basketball court of the UI based on a shot attempt location of the live basketball game. A player is selected 930 from the player display of the UI based on which player attempted the shot attempt in the live basketball game. The recorded data is uploaded 940 into a database. The database may be local (i.e., saved on the electronic device) and / or may be a cloud-based database.

[0088] FIG. 10 illustrates a view of a UI for recording and transmitting real-time sports data, according to some embodiments. User interface (UI) 1000 can include one or more features and / or configurations of UI 100 and / or UI 400. UI 1000 includes at least one of tab selection portion 110, dynamic banner 120, graphical display 140, player display 160, player action toggle 170, scoreboard section 180, control section 190, settings toggle 1015, result display 1025, a plurality of team toggles 1035, substitution toggle 1045, and flag toggle 1055. UI 1000 can include all of tab selection portion 110, dynamic banner 120, graphical display 140, player display 160, player action toggle 170, scoreboard section 180, control section 190, settings toggle 1015, result display 1025, a plurality of team toggles 1035, substitution toggle 1045, and flag toggle 1055.

[0089] Settings toggle 1015 can be selected to view and / or update one or more settings coordinated with the UI 1000 and / or database 102. In some embodiments, settings toggle 1015 can be selected to show one or more settings coordinated with the UI 1000 and / or database 102 within the same page of UI 1000. In other embodiments, settings toggle 1015 can be selected to show one or more settings coordinated with the UI 1000 and / or database 102 in a pop-up menu. Settings coordinated with UI 1000 can include at least one of a view setting, a database setting, a team setting, or a scorekeeper setting. For example, settings toggle 1015 can be selected to change a view of UI 1000, such as changing a position of one or more of tab selection portion 110, dynamic banner 120, graphical display 140, player display 160, player action toggle 170, scoreboard section 180, control section 190, settings toggle 1015, result display 1025, a plurality of team toggles 1035, substitution toggle 1045, and flag toggle 1055. As an example, graphical display 140 can be repositioned above result display 1025. As another example, graphical display 140 can be repositioned below scoreboard section 180.

[0090] Result display 1025 visibly shows one or more results of the current sports game. For example, result display 1025 includes one or more previously recorded player actions and / or shot attempt results. The one or more previously recorded player actions and / or shot attempt results can be arranged in chronological order, from bottom to top, or from top to bottom. In the embodiment shown in FIG. 10, the one or more previously recorded player actions and / or shot attempt results are arranged in chronological order from bottom to top. For example, the latest recorded action is an assist, coordinated with selected player number 17. Result display 1025 can be updated continuously throughout the live sports game. In one example, result display 1025 is updated on all client devices, but is only updated based on input from one or more primary scorekeepers.

[0091] The one or more previously recorded player actions and / or shot attempt results shown in result display 1025 can be manually flagged (e.g., marked) by one or more users. For example, manually flagging the one or more previously recorded player actions and / or shot attempt results shown in result display 1025 can include selecting at least one of the one or more previously recorded player actions and the shot attempt result. Accordingly, each of the previously recorded player actions and the shot attempt result can include a toggle for the user to select and flag the result. In other embodiments, the user can flag one or more previously recorded player actions and / or shot attempt results shown in result display 1025 using a flag toggle, such as flag toggle 1055.

[0092] A selected portion within result display 1025 can exhibit at least one change in visual appearance compared to an unselected state. In one example, the color can be changed to indicate a selected state. In another example, a symbol, such as a flag, can be added adjacent one or more previously recorded player actions and / or shot attempt results shown in result display 1025. Manually flagging one or more previously recorded player actions and / or shot attempt results shown in result display 1025 can be beneficial to “mark” a recordable action for later view, or to indicate the recordable action may have been entered by mistake.

[0093] While graphical display 140 in FIG. 10 illustrates one or more two-point regions and one or more three-point regions of a portion of a basketball court, in some embodiments graphical display 140 can illustrate a greater portion of the basketball court, such as the entire basketball court. While graphical display 140 in FIG. 10 illustrates one or more two-point regions and one or more three-point regions of a portion of a basketball court, user interfaces of the present disclosure can be configured for other sports, such as football, baseball, soccer, volleyball, tennis, and pickleball. Therefore, graphical display 140 can be dynamically updated to display a portion of a court or field depending on the selected sports game. For sports other than basketball, one or more components of UI 1000 can be updated according to the selected sport, such as one or more of dynamic banner 120, player display 160, player action toggle 170, and scoreboard section 180.

[0094] The plurality of team toggles 1035 generally includes a first team toggle and a second team toggle. The first team toggle is associated with a first team, and the second team toggle is associated with a second team. The first team toggle can include a team logo and / or team name. The second team toggle can include a team logo and / or team name. The first team toggle and the second team toggle can be configured to dynamically change which players are shown in player display 160. For example, when the first team toggle is selected, the on-court players associated with the first team are shown in player display 160. In some embodiments, when the on-court players associated with the first team are shown in player display 160, players associated with the second team are not shown in player display 160.

[0095] Substitution toggle 1045 can be selected to change one or more players shown in player display 160. For example, one or more on-court players can be substituted with one or more bench players. In some embodiments, the player display 160 includes a dynamic scroll, where the list of players can scroll (e.g., vertically scroll). In some embodiments, the substitution toggle 1045 allows players to be swapped, e.g., a bench player can be selected, and an in-game player can be selected to swap positions.

[0096] Flag toggle 1055 can be selected to mark a recorded action. Marking a recorded action can include selecting flag toggle 1055, where when flag toggle 1055 is selected, the latest recorded action is marked. For example, if the user believes that the latest recorded action may have been entered by mistake, or if the user would like to quickly find the latest recorded action at a later time, the user can select flag toggle 1055 to mark the latest recorded action. In other embodiments, the user can select flag toggle 1055 and then select a recorded action to mark within result display 1025. The marked recorded action can be dynamically changed to highlight the recorded action. For example, the marked recorded action can exhibit a visual appearance change, such as a color change within the region of the recorded action within result display 1025.

[0097] FIG. 11 illustrates a method for statistical recordation of a basketball game, according to some embodiments. A player selection and a shot toggle selection are received 1110 from a user interface. The user interface can include one or more user interfaces of the present disclosure. The player selection and the shot toggle selection can be received at database 102.

[0098] The player selection includes data representative of a selected player, where the selected player includes a player selected from player display 160. Data representative of the selected player can include at least one of the player’s name, the team associated with the selected player, and one or more player statistics. Often, a shot toggle selection is selected in coordination with the player selection, based on which individual player completed the shot attempt. In some embodiments, the player selection and the shot toggle selection are transmitted to database 102 substantially simultaneously. The shot toggle selection can include data received from a shot attempt toggle. For example, the shot attempt toggle can be the shot attempt toggle discussed for UI 400.

[0099] Data received from the shot attempt toggle can include shot attempt data. Shot attempt data can include data indicative of a shot make or a shot miss. For example, each of the one or more two-point regions and the one or more three-point regions of graphical display 140 can include a shot attempt toggle having a first discrete state, a second discrete state, and a third discrete state. The first discrete state is an unselected state, such as that of two-point shot region 144d. The second discrete state is representative of a shot miss, such as that of shot region 344d. The third discrete state is representative of a shot make. In some embodiments, a fourth discrete state can be utilized for a 1-point free throw make. In some embodiments, the free throw attempt can be a separate region in graphical display 140.

[0100] Data received from the shot attempt toggle can include region data. As discussed, graphical display 140 can illustrate at least a portion of a basketball court and includes one or more two-point regions and one or more three-point regions, where each of the one or more two-point regions and the one or more three-point regions include a shot attempt toggle configured for selection of a shot make or a shot miss. The region data can include a specific location (e.g., x,y coordinates) selected by the user in a coordinate space. The x,y coordinates can indicate which region was selected by mapping the x,y coordinates to the displayed court geometry. The region data can include which specific region was selected by the user. For example, the specific region can be one of two-point shot regions 144a, 144b, 144c, 144d, 144e, paint region 146, and three-point shot regions 142a, 142b, 142c, 142d, 142e. Each of these specific regions can be pre-classified in the database 102 as corresponding to a 2-point region or value, or a 3-point region or value.

[0101] The scoreboard is updated 1120 when the shot toggle selection is the shot make. Updating 1120 can include (1) determining whether the shot make was selected within the one or more two-point shot regions or the one or more three-point shot regions; and (2) determining whether the player selection corresponds to the first team score or the second team score. Determining whether the shot make was selected within the one or more two-point shot regions or the one or more three-point shot regions can include analyzing the latest data received from the shot attempt toggle from a user, such as the primary scorekeeper.

[0102] Analyzing the latest data received from the shot attempt toggle can include reviewing, in database 102, for the most recent shot toggle selection received in coordination with the player selection. Database 102 can be continuously reviewed using timestamps and / or sequence identifiers. Analyzing the latest data received from the most recent shot toggle selection can include matching region data from the selected shot attempt toggle with a pre-classified region in the database. Analyzing the latest data received from the most recent shot toggle selection can include mapping user selected (e.g., tapped position on a touch interface) x,y coordinates to the displayed court geometry.

[0103] Determining whether the player selection corresponds to the first team score or the second team score can include reviewing the player selection coordinated with the most recent shot toggle selection. In one example, it is determined that the player selection corresponds to the first team score or the second team score by matching the player selection to a pre-classified team roster stored in database 102. In another example, it is determined that the player selection corresponds to the first team score or the second team score by receiving data representative of the selected player, where the selected player includes a player selected from player display 160. Data representative of the selected player can include the team associated with the selected player.

[0104] When it is determined that the scoreboard should be updated 1120, the scoreboard on each instance of the user interface can be substantially simultaneously updated. For example, when the latest shot toggle selection corresponds to the third discrete state, the scoreboard can be updated by applying the corresponding point value (+2 or +3) to the appropriate team score. The scoreboard can be selectively updated based on which user inputs the data to database 102.

[0105] Updating the scoreboard based on a shot toggle selection in graphical display 140 increases scorekeeping efficiency. Scorekeeping efficiency can be increased by updating both the scoreboard (e.g., team score) and player statistics based on a shot toggle selection and a player selection, removing one or more additional conventional steps. For example, conventionally, when a player makes a shot in basketball, a scorekeeper would select all of (1) a score toggle (e.g., separate buttons for +1, +2, or +3 points) to update the total team score; (2) a player shot attempt statistic; and (3) the corresponding player. Further, updating the scoreboard based on a shot toggle selection in graphical display 140 can improve accuracy, since basketball is fast-paced, and a visual indicator (e.g., color change) of a shot make in a shot region can improve statistical accuracy.

[0106] While embodiments of the present disclosure include user interfaces for recording statistics of a basketball game, in other embodiments, the user interfaces can be utilized for other sports, such as tennis, soccer, baseball, and football. For example, for soccer, UI 100 can include tab selection portion 110, dynamic banner 120 showing at least the team scores, graphical display 140 showing at least a portion of a soccer field, player display 160, player action toggle 170 (e.g., soccer action for a pass, assist, block, and / or save), and scoreboard section 180 including a clock, such as a countdown timer.

[0107] FIG. 12 illustrates system 1200 for analyzing sports data, according to some embodiments. System 1200 includes a computing device 1201 that includes processor 1220 and memory 1230. Processor 1220 can include at least one processing component such as a microcontroller, microprocessor, central processing unit (CPU), graphics processing unit (GPU), tensor processing unit (TPU), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA), neural processing unit (NPU), quantum processor, or the like configured to execute instructions to perform the functions described herein. Memory 1230 can include at least one storage medium such as a non-volatile memory component (e.g., a FLASH memory), volatile memory component (e.g., magnetic memory), or the like configured to store executable instructions and / or data. Memory 1230 may include one or more memory components local to the computing device 1201 and / or coupled to the computing device via a network such as a cloud storage medium. Processor 1220 can execute instructions stored by memory 1230. System 1200 can implement one or more methods of the present disclosure. System 1200 can be in communication with, and / or include UI 100, UI 400, UI 1000, and / or database 102.

[0108] In some examples, the various techniques described herein for updating the user interface or analyzing recorded data may be implemented by software instructions executable by the processor 1220 to perform the various functions described. In other examples, such instructions may be executed to implement a machine learning model trained to implement the various functions described. In one example, the machine learning model can input recorded data entered by one or more users to determine accuracy of the recorded data.

[0109] The inputs 1210 to the system and / or machine learning model can include recorded data of the present disclosure, such as a recordable action (e.g., shot action such as a shot make or shot miss and / or a player action such as a steal, assist, turnover, etc.), a time of game, a possession indication, and / or a selected player. Input 1210 can include a shot toggle selection. In one example, the input 1210 includes a shot make and a coordinated selected player. In another example, the input 1210 can include data from one or more selected toggles of UI 100, UI 400, and / or UI 1000. In another example, the input 1210 can include video data (such as a recording or live feed of the current game) or photographic data.

[0110] The machine learning model can analyze the input 1210 (e.g., recorded data) to determine the accuracy of the recorded data. For example, the machine learning model can analyze the recorded data to determine the quantitative accuracy of the recorded data, indicating a possible scorekeeping mistake based on a low quantitative accuracy determination. Additionally, or alternatively to manual user flagging discussed herein, the machine learning model can determine a predicted accuracy of the latest recorded data and can automatically flag the latest recorded data based on a low quantitative accuracy determination. This can be beneficial to increase scorekeeping accuracy and efficiency, as system 1200 can automatically flag user input to indicate a possible statistical error to the user.

[0111] Output 1240 can include a numerical value, a Boolean value, and / or a dataset based on data from input 1210. In one example, output 1240 includes a quantitative accuracy. For example, output 1240 can include a numerical value, such as a numerical percentage value. For example, the numerical value can be a value ranging from 0 to 100. The numerical value can be compared to a pre-determined threshold.

[0112] In one example, output 1240 includes instructions to remove the latest recorded action when the numerical value corresponding to a quantitative accuracy is less than a pre-determined threshold. For example, the pre-determined threshold can include a numerical value, such as 10, 20, 30, 40, 50, or 60. By way of example, if a scorekeeper mistakenly enters the wrong statistic, output 1240 could output a value of 10, indicating a 10% accuracy determination, and if the threshold is 20%, system 1200 can process the instructions to remove the latest recorded action from the user interface display and / or the database.

[0113] In another example, output 1240 includes instructions to flag a recorded action when the numerical value corresponding to a quantitative accuracy is less than a pre-determined threshold. For example, the pre-determined threshold can include a numerical value, such as 10, 20, 30, 40, 50, or 60. By way of example, if a scorekeeper mistakenly enters the wrong statistic, output 1240 could output a value of 10, indicating a 10% accuracy determination, and if the threshold is 20%, system 1200 can process the instructions to flag the recorded action.

[0114] Such a machine learning model may be trained using supervised or unsupervised training data to operate as described. For example, the machine learning model may be fed measured or automatically generated deterministic training data with a known outcome until the machine learning model is configured to replicate a desired outcome when fed with new training or other data. The machine learning model may store associations in memory based on the training. Once trained, the machine learning model may be instantiated on the same or a different processor, including processor 1220 of computing device 1201, and use the stored associations to automatically process new data. In some examples, once instantiated, the machine learning model may continue training and updating stored associations as the machine learning model processes new data.

[0115] The training data for training the model can include at least one of video data (such as a video recording), photographic data, past recorded data, and associations of pre-determined flagged actions. For example, associations of pre-determined flagged actions can include manually flagged actions, such as flagged actions using flag toggle 1055. Additionally, the trained model can undergo further training by user input, such as via a user interface. For example, the user can accept or decline an automatically flagged action determined by system 1200.

[0116] In some examples, system 1200 may include a single machine learning model executing on the processor previously trained and configured to operate alone or in combination with traditional software to perform the various functions described herein. In other examples, the system 1200 may include multiple machine learning models each trained and / or instantiated to execute different parts of the various methods described, alone or in combination with traditional software.

[0117] While the invention has been described with reference to an exemplary embodiment(s), it will be understood by those skilled in the art that various changes may be made and equivalents may be substituted for elements thereof without departing from the scope of the invention. In addition, many modifications may be made to adapt a particular situation or material to the teachings of the invention without departing from the essential scope thereof. Therefore, it is intended that the invention not be limited to the particular embodiment(s) disclosed, but that the invention will include all embodiments falling within the scope of the appended claims.Discussion of Possible Embodiments

[0118] Clause 1. A user interface for statistical recordation of a basketball game, comprising: a player display including a plurality of selectable players; and a graphical display depicting at least a portion of a basketball court and including one or more two-point regions and one or more three-point regions, wherein each of the one or more two-point regions and the one or more three-point regions include a shot attempt toggle configured for selection of a shot make or a shot miss, wherein the player display and the graphical display are accessible on a single page of the user interface.

[0119] The clause of the preceding paragraph can optionally include, additionally and / or alternatively any one or more of the following features, configurations and / or additional components.

[0120] Clause 2. The user interface of clause 1, wherein the player display includes a plurality of dynamic player icons on a scroll wheel.

[0121] Clause 3. The user interface of clause 2, wherein each of the plurality of dynamic player icons includes a foul indicator.

[0122] Clause 4. The user interface of clause 1, further including a scoreboard including a first team score and a second team score.

[0123] Clause 5. The user interface of clause 4, wherein the scoreboard is configured to update based on: (1) whether the shot make is selected in the one or more two-point regions or the one or more three-point regions; and (2) selection of one player from the plurality of selectable players.

[0124] Clause 6. The user interface of clause 1, including a first player action toggle configured to dynamically provide a first visual indication based on selection of a shot make.

[0125] Clause 7. The user interface of clause 6, wherein the first player action toggle includes an assist toggle configured to associate an assist with one or more of the plurality of selectable players.

[0126] Clause 8. A user interface for statistical recordation of a basketball game, comprising: a player display including a plurality of selectable players; a graphical display depicting at least a portion of a basketball court and including one or more two-point shot regions and one or more three-point shot regions, wherein each of the one or more two-point shot regions and the one or more three-point shot regions include a shot toggle configured for selection of a shot make or a shot miss; and; a first player action toggle configured to dynamically provide a first visual indication based on selection of a shot make; and a second player action toggle configured to dynamically provide a second visual indication based on selection of a shot miss.

[0127] The clause of the preceding paragraph can optionally include, additionally and / or alternatively any one or more of the following features, configurations and / or additional components.

[0128] Clause 9. The user interface of clause 8, wherein the first player action toggle includes an assist toggle configured to associate an assist with one or more of the plurality of selectable players.

[0129] Clause 10. The user interface of clause 8, wherein the second player action toggle includes a rebound toggle configured to associate a rebound with one or more of the plurality of selectable players.

[0130] Clause 11. The user interface of clause 8, wherein the player display and the graphical display are static regions that are simultaneously accessible by a user.

[0131] Clause 12. The user interface of clause 11, wherein the player display, the graphical display, the first player action toggle, and the second player action toggle are included on a single page of the user interface.

[0132] Clause 13. The user interface of clause 8, further including a scoreboard including a first team score and a second team score.

[0133] Clause 14. The user interface of clause 8, wherein the player display includes a plurality of dynamic player icons.

[0134] Clause 15. The user interface of clause 14, wherein each of the plurality of dynamic player icons includes a foul indicator.

[0135] Clause 16. The user interface of clause 8, wherein the first player action toggle and the second player action toggle are arranged exterior to the graphical display.

[0136] Clause 17. The user interface of clause 8, wherein the first visual indication includes a color change.

[0137] Clause 18. A method for statistical recordation of a basketball game, comprising: receiving a player selection and a shot toggle selection from a user interface, wherein the user interface includes: a player display including a plurality of selectable players; a graphical display depicting at least a portion of a basketball court and including one or more two-point shot regions and one or more three-point shot regions, wherein each of the one or more two-point shot regions and the one or more three-point shot regions include a shot toggle configured for the shot toggle selection of a shot make or a shot miss; and a scoreboard including a first team score and a second team score; and updating the scoreboard when the shot toggle selection is the shot make, wherein updating the scoreboard includes (1) determining whether the shot make was selected within the one or more two-point shot regions or the one or more three-point shot regions; and (2) determining whether the player selection corresponds to the first team score or the second team score.

[0138] The clause of the preceding paragraph can optionally include, additionally and / or alternatively any one or more of the following features, configurations and / or additional components.

[0139] Clause 19. The method of clause 18, wherein the player display and the graphical display are accessible on a single page of the user interface.

[0140] Clause 20. The method of clause 19, wherein the user interface includes a first player action toggle configured to dynamically provide a first visual indication based on selection of a shot make.

[0141] Clause 21. A user interface (UI) for statistical recordation of a live basketball game includes: a player display including a plurality of selectable players; and a graphical display including a plurality of three-point shot regions and a plurality of two-point shot region; wherein a shot attempt of the live basketball game is recorded via selection of a region of the graphical display basketball court and a selection of one of the selectable players of the player display.

[0142] Clause 22. A method of statistical recordation of a live basketball game includes: providing a user interface (UI), the UI including: a player display, and a plurality of shot regions on a graphical display, selecting a shot region from the plurality of shot regions on the graphical basketball court based on a shot location of the live basketball game; and selecting a player from the player display based on which on-court player attempted a shot attempt.

Examples

Embodiment Construction

[0028] The present disclosure describes systems and methods for recording and transmitting real-time sports data, including a user interface (UI) for inputting statistics to a database. The UI includes a player display to allow a user to select which player has completed a recordable action in the game. The user may select the recordable action (e.g., shot action such as a shot make or shot miss and / or a player action such as a steal, assist, turnover, etc.) via a plurality of labeled toggles. The UI includes a graphical display to allow the user to record or view the region where a recordable action (e.g., a basketball shot) was performed or attempted from. In some embodiments, the UI is a single-page display, with no pop ups, to enable efficient and accurate data inputs. If, for instance, the UI was multi-page and / or included pop-up prompts or menus, the scorekeeper may not be able to accurately keep pace with the real-time statistical recordation of the sports game (e.g., a...

CROSS-REFERENCE TO RELATED APPLICATION

[0001] This application claims the benefit of and priority to U.S. Provisional Application 63 / 748,071, titled “SYSTEM AND METHOD OF SCOREKEEPING ATHLETIC EVENTS”, filed January 22, 2025, the contents of which are incorporated by reference herein.TECHNICAL FIELD

[0002] The subject matter disclosed herein generally relates to the field of recording and tracking sports data and more particularly to devices, systems, and methods for scorekeeping athletic events with a computing device.BACKGROUND

[0003] Sports fans enjoy following live sporting events, either by attending in-person or through television or radio broadcasts. However, when these options are unavailable, alternative tools such as internet-based utilities enable fans to track game data and statistics in real time, using input from individuals at the event via internet-connected devices. Amateur events, including youth games, school sports, or recreational leagues, are rarely broadcast and typically rely on manual scorekeeping, leaving non-attendees without live updates. Manual scorekeeping is often inefficient and imprecise. Therefore, a new interface is needed to enhance the accuracy and quality of recorded statistics, and to improve the availability of live data for sports, such as amateur sports.SUMMARY

[0004] According to one aspect, a user interface for statistical recordation of a basketball game includes: a player display including a plurality of selectable players; and a graphical display depicting at least a portion of a basketball court and including one or more two-point regions and one or more three-point regions, wherein each of the one or more two-point regions and the one or more three-point regions include a shot attempt toggle configured for selection of a shot make or a shot miss, wherein the player display and the graphical display are accessible on a single page of the user interface.

[0005] According to one aspect, a user interface for statistical recordation of a basketball game includes a player display including a plurality of selectable players; a graphical display depicting at least a portion of a basketball court and including one or more two-point shot regions and one or more three-point shot regions, wherein each of the one or more two-point shot regions and the one or more three-point shot regions include a shot toggle configured for selection of a shot make or a shot miss; and; a first player action toggle configured to dynamically provide a first visual indication based on selection of a shot make; and a second player action toggle configured to dynamically provide a second visual indication based on selection of a shot miss.

[0006] According to one aspect, a method for statistical recordation of a basketball game includes receiving a player selection and a shot toggle selection from a user interface, wherein the user interface includes: a player display including a plurality of selectable players; a graphical display depicting at least a portion of a basketball court and including one or more two-point shot regions and one or more three-point shot regions, wherein each of the one or more two-point shot regions and the one or more three-point shot regions include a shot toggle configured for the shot toggle selection of a shot make or a shot miss; and a scoreboard including a first team score and a second team score; and updating the scoreboard when the shot toggle selection is the shot make, wherein updating the scoreboard includes (1) determining whether the shot make was selected within the one or more two-point shot regions or the one or more three-point shot regions; and (2) determining whether the player selection corresponds to the first team score or the second team score.BRIEF DESCRIPTION OF THE DRAWINGS

[0007] FIG. 1A illustrates a view of a user interface (UI) for recording and transmitting real-time sports data, according to some embodiments.

[0008] FIG. 1B illustrates a view of the UI for recording and transmitting real-time sports data, according to some embodiments.

[0009] FIG. 2A illustrates a view of the UI for recording and transmitting real-time sports data, according to some embodiments.

[0010] FIG. 2B illustrates a view of the UI for recording and transmitting real-time sports data where the user has initiated a data input, according to some embodiments.

[0011] FIG. 2C illustrates a view of the UI for recording and transmitting real-time sports data where the user has initiated a data input, according to some embodiments.

[0012] FIG. 2D illustrates a view of the UI for recording and transmitting real-time sports data in the scoreboard state, according to some embodiments.

[0013] FIG. 3A illustrates a view of the UI for recording and transmitting real-time sports data, according to some embodiments.

[0014] FIG. 3B illustrates a view of the UI for recording and transmitting real-time sports data where the user has initiated a data input, according to some embodiments.

[0015] FIG. 3C illustrates a view of the UI for recording and transmitting real-time sports data where the user has initiated a data input, according to some embodiments.

[0016] FIG. 3D illustrates a view of the UI for recording and transmitting real-time sports data where the user has initiated a data input, according to some embodiments.

[0017] FIG. 4A illustrates a view of a UI for recording and transmitting real-time sports data, according to some embodiments.

[0018] FIG. 4B illustrates a view of the UI for recording and transmitting real-time sports data where the user has initiated a data input, according to some embodiments.

[0019] FIG. 4C illustrates a view of the UI for recording and transmitting real-time sports data where the user has initiated a data input, according to some embodiments.

[0020] FIG. 5 illustrates a view of a play-by-play UI generating a display based on recorded data from the database, according to some embodiments.

[0021] FIG. 6 illustrates a view of a statistical analysis UI generating a display based on recorded data from the database, according to some embodiments.

[0022] FIG. 7 illustrates a view of a statistical comparison UI generated based on recorded data from the database, according to some embodiments.

[0023] FIG. 8 illustrates a view of a player statistic UI generated based on recorded data from the database, according to some embodiments.

[0024] FIG. 9 illustrates a flow chart of a method of statistical recordation of a live basketball game, according to some embodiments.

[0025] FIG. 10 illustrates a view of a UI for recording and transmitting real-time sports data, according to some embodiments.

[0026] FIG. 11 illustrates a method for statistical recordation of a basketball game, according to some embodiments.

[0027] FIG. 12 illustrates a system for analyzing sports data, according to some embodiments.DETAILED DESCRIPTION

[0028] The present disclosure describes systems and methods for recording and transmitting real-time sports data, including a user interface (UI) for inputting statistics to a database. The UI includes a player display to allow a user to select which player has completed a recordable action in the game. The user may select the recordable action (e.g., shot action such as a shot make or shot miss and / or a player action such as a steal, assist, turnover, etc.) via a plurality of labeled toggles. The UI includes a graphical display to allow the user to record or view the region where a recordable action (e.g., a basketball shot) was performed or attempted from. In some embodiments, the UI is a single-page display, with no pop ups, to enable efficient and accurate data inputs. If, for instance, the UI was multi-page and / or included pop-up prompts or menus, the scorekeeper may not be able to accurately keep pace with the real-time statistical recordation of the sports game (e.g., a basketball game), due at least in part to the fast-paced nature of sports games. Data input to the UI is stored in a database, and may be compiled to produce advanced statistical analysis, including, for instance, shot chart statistics by shot region.

[0029] Amateur events, including youth games, school sports, or recreational leagues, are rarely broadcast and typically rely on manual scorekeeping, leaving non-attendees without live updates. Manual scorekeeping of amateur sports is often inefficient and imprecise. Therefore, a new interface is needed to enhance the accuracy and quality of recorded statistics, and to improve the availability of live data for sports, such as amateur sports.

[0030] FIG. 1A is a view of a user interface (UI) 100 for recording and transmitting real-time sports data, according to some embodiments. The user interface (UI) 100 includes at least one of a tab selection portion 110, a dynamic banner 120, a first statistical input toggle 130, a graphical display 140, a second statistical input toggle 150, a player display 160, a player action toggle 170, a scoreboard section 180, and a control section 190. In some embodiments, the UI 100 includes a graphical display 140, a player display 160, a player action toggle 170, and a scoreboard section 180. In some embodiments, the UI 100 is configured to record statistical data and transmit the recorded data to a database 102. The database 102 may be a local database (i.e., local to the computing device displaying the UI 100) and / or may be a remote or cloud-based database.

[0031] Tab selection portion 110 includes one or more toggles configured for a user to change a setting, select a game, view a user, view database status, and / or view statistics. Dynamic banner 120 includes one or more real-time statistics of the sports game, such as one or more team scores and / or a possession indicator. First statistical input toggle 130, second statistical input toggle 150, and player action toggle 170 represent a recordable action and can be selected based on live recordable actions as they occur in the sports game. Tab selection portion 110, dynamic banner 120, first statistical input toggle 130, second statistical input toggle 150, and player action toggle 170 are discussed further in FIG. 1B.

[0032] In some embodiments, a “toggle” refers to a user-selectable control (or other selectable region) that enables selection between discrete options, pages, and / or states -often a pair of opposing states (e.g., selected / unselected), and may use a different visual appearance to indicate the current state. For scorekeeping and statistics, the toggle can be implemented broadly as any bounded on-screen region that, when selected, records (or changes) a game action or classification, including, by way of example, a switch-style toggle, a checkbox-style toggle, a toggle button, or a grouped set of toggle buttons configured for exclusive selection. For example, the toggle can include (i) a “shot make” toggle and a “shot miss” toggle presented as mutually exclusive toggle buttons such that selecting one deselects the other, or (ii) a single toggle that alternates between “shot make” and “shot miss” states while visually indicating the currently selected outcome. For example, on a computing device having a touch-sensitive display, the “shot make” toggle may define a touch-sensitive region corresponding to the displayed control, and the toggle may be selected based on a touch input detected within the region of the toggle (e.g., a tap within the region), causing the computing device to record a made-shot event for an identified player and / or time in the game.

[0033] Graphical display 140 illustrates at least a portion of a field, court, or playing surface. While graphical display 140 illustrates at least a portion of a basketball court in FIG. 1A, in other embodiments, graphical display can represent fields or courts for alternative sports, such as tennis, soccer, baseball, and football. Player display 160 can illustrate one or more player icons, which can be selectable. Scoreboard section 180 can illustrate statistical data of the current sports game, and control section 190 can include one or more selectable toggles for changing an input, removing a past input, re-adding a past input, or changing a setting. Graphical display 140, player display 160, scoreboard section 180, and control section 190 are discussed further in FIG. 1B.

[0034] The UI of the present disclosure may be included in a software application and / or webpage configured to operate on a computing device, such as a cellular phone, tablet, or other computing device. The computing device may be a mobile electronic device configured to communicate with a remote wireless network. The computing device includes a processor and memory, and the computing device may further include a display. The processor can include at least one processing component, such as a microcontroller, microprocessor, central processing unit (CPU), graphics processing unit (GPU), tensor processing unit (TPU), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA), neural processing unit (NPU), quantum processor, or the like, configured to execute instructions to perform the functions described herein. The memory can include at least one storage medium, such as a non-volatile memory component (e.g., a FLASH memory), volatile memory component (e.g., magnetic memory), or the like, configured to store executable instructions and / or data. The memory may include one or more memory components local to the computing device and / or coupled to the computing device via a network, such as a cloud storage medium. The processor can execute instructions stored by the memory.

[0035] The computing device includes a memory or data storage capable of storing and running the software application. The computing device may be configured for receiving inputs from a user, such as inputs of recordable events. The computing device may collect and receive data related to the event and distribute the data for public viewing. Data and statistics related to the event can be input into the computing device by a user. Data may include one or more of numeric data, photographic data, video data, and / or sound data. The data can be uploaded to a remote or cloud-based database. The data can be transmitted to the database 102. Data in database 102 can be viewed locally or remotely, such as on a separate editing user interface utilized for viewing recorded actions in chronological order. Accordingly, flagged recorded actions (discussed further herein) can be viewed and / or edited in the separate editing user interface during or after the game. The editing user interface can show all input data streams from multiple users that input data into database 102.

[0036] FIG. 1B is a view of the UI 100 for recording and transmitting real-time sports data, according to some embodiments. Individual toggles and labels for each of the tab selection portion 110, the dynamic banner 120, the first statistical input toggle 130, the graphical display 140, the second statistical input toggle 150, the player display 160, the player action toggle 170, the scoreboard section 180, and the control section 190 are shown.

[0037] The tab selection portion 110 may include at least one of an input tab 112, a play-by-play tab 114, a statistic summary and analysis tab 116, and a network upload 118 control. Input tab 112 can include a user selection toggle. Input tab 112 can illustrate the currently selected user of the displayed instance of UI 100. The play-by-play tab 114 and the analysis tab 116 are described in FIGS. 5-8, below. The UI 100 may default to local storage, i.e., transmitting the input statistical data to a local database (e.g., the database 102). The network upload 118 may be selected by the user to upload locally saved data to a remote network. In some embodiments, the network upload 118 may control whether the data is uploaded to a local database and / or uploaded to a remote database. For instance, the network upload 118 can be selected by the user to enable live, real-time upload of statistical data to the database 102 via a network connection to allow other users to view the data in real-time. In some embodiments, the network upload 118 may be selected by the user to upload locally saved data to a remote network. This allows support for the user device being offline and synching submissions when the user(s) have connectivity again.

[0038] The dynamic banner 120 may include a first team icon 122a and a second team icon 122b, a first team score 124a and a second team score 124b, and / or a possession toggle 126. The dynamic banner 120 is updated as statistics are recorded in real-time. For instance, if the first team makes a shot (and the shot is recorded via the UI 100), the first team score 124a is updated to reflect the made shot. In some embodiments, the user may select the possession toggle 126 to indicate which team has possession of the ball (i.e., which team is on offense). The possession toggle 126 may lock certain statistics based on which team has possession, as for example, the first team cannot record a 3-point make (via a three-point make toggle 152) if the first team does not have possession of the ball. Locking toggles based on possession may improve accuracy of the recorded statistics. In some embodiments, the toggles are not locked based on possession, as the tracking of live possession (via the possession toggle 126) may slow the recordation of real-time statistics.

[0039] The first statistical input toggle 130 may include a free throw (FT) make toggle 132, an FT miss toggle 134, a block toggle 136, and / or a steal toggle 138. In some embodiments, related statistics (e.g., FT make and FT miss) may be located adjacent to each other to aid the user in inputting data. For instance, the block toggle 136 and the steal toggle 138 are located adjacent to each other as they are both indicative of defensive statistics.

[0040] The graphical display 140 includes a plurality of shot regions, including for instance, three-point shot regions 142a, 142b, 142c, 142d, 142e, two-point shot regions 144a, 144b, 144c, 144d, 144e, and / or a paint region 146. The user can select where a shot attempt of the basketball game was attempted at, i.e., which shot region on the graphical display 140 the shot attempt took place.

[0041] The second statistical input toggle 150 may include a three-point make toggle 152, a three-point miss toggle 154, a two-point make toggle 156, and a two-point miss toggle 158. Related statistical toggles (e.g., the three-point make toggle 152 and the three-point miss toggle 154) may be positioned adjacent to each other, and in some embodiments, mirrored over a centerline. For instance, the miss toggles (e.g., the FT miss toggle 134, the three-point miss toggle 154, and the two-point miss toggle 158) may be positioned on a first side of the UI 100, and the make toggles (e.g., the FT make toggle 132, the three-point make toggle 152, and the two-point make toggle 156) may be positioned on a second side of the UI 100. The symmetric positioning of the make / miss toggles and the adjacent positioning of related statistical toggles improves efficiency and accuracy of statistical recordation of a live basketball game.

[0042] In some embodiments, selection of the three-point make toggle 152 or the three-point miss toggle 154 may lock the two-point shot regions 144a, 144b, 144c, 144d, 144e and paint region 146 from being selected. Likewise, selection of the two-point make toggle 156 or two-point miss toggle 158 may lock the three-point shot regions 142a, 142b, 142c, 142d, 142e from being selected. Locking the shot region based on the recorded location of the shot attempt may improve efficiency and accuracy of statistical recordation of a live basketball game.

[0043] In some embodiments, the shot attempt (including make / miss and point total) can be recorded solely via interaction with the graphical display 140. For instance, selection of one of the three-point shot regions 142a, 142b, 142c, 142d, 142e will narrow the statistical input options to either a three-point make or a three-point miss. A single tap may indicate a miss, and a double tap (or press and hold) may indicate a make. Thus, the shot location, shot type (three-point versus two-point), and make / miss status may be recorded solely with the graphical display 140 (see, e.g., FIGS. 4A-C). This may be beneficial, as it reduces the number of toggles on the UI 100, thereby improving efficiency and accuracy of statistical recordation of a live basketball game.

[0044] The player display 160 includes a plurality of selectable players. The player display can include a plurality of first selectable players corresponding to a first team and / or a plurality of second selectable players corresponding to a second team. In some embodiments, the player display shows a plurality of first selectable players corresponding to the first team and hides the plurality of second selectable players corresponding to the second team. In other embodiments, the player display shows an icon for a first team and an icon for a second team, where the team as a whole is selectable in place of an individual player. In one example, the player display 160 includes at least one of a plurality of bench players 164a, 164b, 164c, 164d, a plurality of on-court players 166a, 166b, 166c, 166d, 166e, a first team icon 168, and an edit toggle 162 to modify player status (in-game versus bench). Database 102 can store the amount of time each player is on the court and / or on the bench.

[0045] In some embodiments, the player display 160 includes a dynamic scroll, where the list of players can scroll (e.g., vertically scroll). In some embodiments, the edit toggle 162 allows players to be swapped, e.g., a bench player can be selected and an in-game player can be selected to swap positions. The plurality of on-court players 166a, 166b, 166c, 166d, 166e may be selectable to associate a player with a given action. For instance, a block may occur in-game, and to record the block, the user may select the block toggle 136 and select the on-court player 166a to associate the player with the block. In some embodiments, the player display 160 includes a foul indicator on each player. For instance, the on-court player 166a in FIG. 1B has four fouls. In some embodiments, the foul indicator is color-coded to indicate caution (e.g., red or yellow) when a player is approaching the maximum number of fouls prior to disqualification.

[0046] The player action toggle 170 may include at least one of an assist toggle 172, a turnover toggle 174, an offensive rebound toggle 176, a defensive rebound toggle 178, and a possession indicator 175. Related statistical toggles (e.g., offensive rebound toggle 176 and the defensive rebound toggle 178) may be positioned adjacent to each other, and in some embodiments, mirrored over a centerline.

[0047] The player action toggle 170 can include a first player action toggle and a second player action toggle. The first player action toggle can include at least one of assist toggle 172, turnover toggle 174, offensive rebound toggle 176, defensive rebound toggle 178, and possession indicator 175. The second player action toggle can include at least one of assist toggle 172, turnover toggle 174, offensive rebound toggle 176, defensive rebound toggle 178, and possession indicator 175. In some embodiments, the first player action toggle and the second player action toggle are different.

[0048] The first player action toggle (e.g., button or button region) can dynamically adjust based on a selected input from the user. In some embodiments, the first player action toggle dynamically adjusts based on a selected shot attempt. In this example, the first player action toggle can dynamically adjust when a shot toggle, configured for selection of a shot make or a shot miss, has been selected. For example, the first player action toggle is configured to dynamically adjust when a shot make is selected. Dynamically adjusting can include providing a first visual indication. In one example, the first visual indication includes an appearance change, such as a change in color, opacity, and / or brightness. In another example, the first visual indication includes transforming from a visually hidden state to a visually appearing state.

[0049] During utilization of the UI, a shot make can be selected. The shot make can be selected in conjunction with a selected player. When a shot make is selected, such as via selection of one of the regions of the graphical display 140 (see, e.g., FIGS. 4A-C), the first player action toggle can immediately, or within a time frame (e.g., less than 1 second or less than 3 seconds), dynamically adjust to highlight a possible coordinated selection to the user. For example, when a shot attempt is a shot make, it is likely there is a coordinated selection, such as assist toggle 172, that the user would like to select. An assist is a coordinated selection with a shot make because a scorekeeper typically records an assist right after a shot make, since an assist in basketball is only awarded when the last pass leads directly to a score, so it cannot be confirmed until the shot attempt is a shot make. Therefore, when a shot attempt is a shot make and the user selects a shot make, the first player action toggle can exhibit a first visual indication that includes an appearance change, such as a change in color, opacity, and / or brightness, to indicate a possible coordinated selection. By indicating a possible coordinated selection to the user, the scorekeeping efficiency can be increased, as the first visual indication can quickly guide the user to a likely coordinated selection. Additionally, the scorekeeping accuracy can be improved by automatically indicating possible coordinated selection(s) to the user. The user can decide whether to select the first player action toggle based on the outcome in the game. The first visual indication can appear without a pop-up window or menu.

[0050] The second player action toggle (e.g., button or button region) can dynamically adjust based on a selected input from the user. In some embodiments, the second player action toggle dynamically adjusts based on a selected shot attempt. In this example, the second player action toggle can dynamically adjust when a shot toggle, configured for selection of a shot make or a shot miss, has been selected. For example, the second player action toggle is configured to dynamically adjust when a shot miss is selected. Dynamically adjusting can include providing a first visual indication. In one example, the first visual indication includes an appearance change, such as a change in color, opacity, and / or brightness. In another example, the first visual indication includes transforming from a visually hidden state to a visually appearing state.

[0051] During utilization of the UI, a shot miss can be selected. The shot miss can be selected in conjunction with a selected player. When a shot miss is selected, such as via selection of one of the regions of the graphical display 140 (see e.g., FIGS. 4A-C), the second player action toggle can immediately, or within a time frame (e.g., less than 1 second or less than 3 seconds), dynamically adjust to highlight a possible coordinated selection to the user. For example, when a shot attempt is a shot miss, it is likely there is a coordinated selection, such as offensive rebound toggle 176 or defensive rebound toggle 178, that the user would like to select. A rebound (e.g., offensive rebound or defensive rebound) is a coordinated selection with a shot miss because a rebound is only credited once a shot is missed and a player (or team) secures the live ball, so scorekeepers record it after the shot miss when possession is established. Therefore, when a shot attempt is a shot miss and the user selects a shot miss, the second player action toggle can exhibit a first visual indication that includes an appearance change, such as a change in color, opacity, and / or brightness, to indicate a possible coordinated selection. By indicating a possible coordinated selection to the user, the scorekeeping efficiency can be increased. Additionally, the scorekeeping accuracy can be improved by automatically indicating possible coordinated selection(s) to the user. The user can decide whether to select the second player action toggle based on the outcome in the game.

[0052] The scoreboard section 180 may include a first foul indicator 182a, a second foul indicator 182b, a first timeout indicator 184a, a second timeout indicator 184b, an edit toggle 186, and / or a timer 188. In some embodiments, dynamic banner 120 and scoreboard section 180 can be combined as one region or section. Accordingly, one or more features / configurations of dynamic banner 120 can be combined with one or more features / configurations of scoreboard section 180. The first foul indicator 182a and the second foul indicator 182b may indicate bonus and / or double bonus based on the number of recorded fouls. The control section 190 may include an undo toggle 192 and a redo toggle 194. The undo toggle 192 and / or the redo toggle 194 may enable the user to quickly remove / add statistical inputs with one click, i.e., instead of bringing up an edit screen.

[0053] User interfaces of the present disclosure can be a single-page user interface for inputting statistical data of a live basketball game. The single-page user interface can be a single rendered user-interface view (e.g., one viewport) that is presented as a single, continuous page to the user, such that the relevant toggles (e.g., buttons) and graphical displays are available within that same view rather than being moved to a different page or screen. For example, the toggles and graphical displays may be laid out so that, within the same viewport, the user can directly view and select the toggles while simultaneously viewing the associated graphical displays. The single-page user interface can include implementations where the toggles and graphical display(s) remain on the same page even if the user scrolls within that page (e.g., the user interface is not replaced by a different page / screen), and where additional options are not presented via an overlaid popover / popup menu that appears on top of the page.

[0054] For example, the UI 100 does not include pop-up prompts and does not require the user to leave the single-page user interface to enter statistics. The UI 100 provides shot-attempt location data (via the graphical display 140) on the single-page user interface. The dynamic banner 120, the first statistical input toggle 130, the graphical display 140, the second statistical input toggle 150, the player display 160, the player action toggle 170, the scoreboard section 180, and the control section 190 are static regions (i.e., each region is fixed on the display, although the toggles, prompts, banners may dynamically update as the game progresses), and therefore, the user can access all relevant toggles, controls, and displays all at once—without needing to scroll through or select the proper prompt. The single-page configuration is beneficial, as the user can access inputs to all relevant statistical data on a single screen without going through a series of pop-up and / or prompts, which thereby improves the efficiency and accuracy of data recordation. If, for instance, the user interface was multiple pages, input of statistics may fall behind the actual pace of play of the basketball game, leading to inaccuracies and missed statistics.

[0055] FIG. 2A is a view of the UI 100 for recording and transmitting real-time sports data, according to some embodiments. The UI 100 in FIG. 2A is in a scoreboard state, i.e., a data input has not been initiated by the user, and the dynamic banner 120 displays the game score.

[0056] FIG. 2B is a view of the UI 100 for recording and transmitting real-time sports data where the user has initiated a data input, according to some embodiments. For instance, the user has selected the steal toggle 138, which generates a bolded steal toggle 238. Bolded toggles, such as bolded steal toggle 238, can exhibit at least one visual appearance change compared to the unselected toggle, such as steal toggle 138. For example, bolded steal toggle 238 can exhibit bolded text characters, such as the text “steal” in bold characters. In another example, and as shown in FIG. 2B, bolded steal toggle 238 includes a bold border surrounding the toggle region.

[0057] The selection of the steal toggle 138 can lock one or more other controls / toggles of the UI 100, including, for example, the graphical display 140. A locked graphical display basketball court 240 is generated from the selection of the steal toggle 138. In some embodiments, the dynamic banner 120 is updated when the user initiates a data input. For instance, a steal statistic banner 220 is generated when the user initiates input of a steal statistic. The steal statistic banner 220 displays the total number of team steals, and in some embodiments, includes a comparison between the first team steals and the second team steals. The dynamic banner 120 may be updated to correspond to the type of statistic input by the user, e.g., for input of a block statistic, the dynamic banner 120 may be updated to display total team blocks.

[0058] FIG. 2C is a view of the UI 100 for recording and transmitting real-time sports data where the user has initiated a data input, according to some embodiments. The user has selected the on-court player 166e, which thereby generates a bolded player icon 266e. Thus, the on-court player 166e has been associated with a steal statistic. The dynamic banner 120 is updated to an individual steal banner 222. The individual steal banner 222 displays the total number of steals associated with the selected player. Upon selection of both the action (the steal toggle 138) and the player (the on-court player 166e), a filled steal icon 239 is generated and a confirmation icon 204 is generated. The filled steal icon 239 and / or the confirmation icon 204 confirms that the statistic has been recorded. The individual steal banner 222 may provide an additional confirmation to the user that the correct player has been selected.

[0059] If, for instance, an incorrect player or statistic is recorded, the user may use the control section 190, and specifically the undo toggle 192 and / or the redo toggle 194 to go back / forward to fix errors. For example, if the user selects both the action (the steal toggle 138) and the player (the on-court player 166e), as shown in FIG. 2C, the undo toggle 192 will undo the most recent input (e.g., the selection of the on-court player 166e in this case), and the UI 100 will return to the display of FIG. 2B.

[0060] When both the action (the steal toggle 138) and the player (the on-court player 166e) are selected and the user is satisfied with the input statistics (e.g., verifies that the dynamic banner 120 includes the correct player and stat), the UI may return to the scoreboard state. FIG. 2D is a view of the UI 100 for recording and transmitting real-time sports data in the scoreboard state, according to some embodiments. The input statistic is saved in a local database (e.g., the database 102) and / or uploaded to a network database (e.g., the database 102).

[0061] FIG. 3A is a view of the UI 100 for recording and transmitting real-time sports data, according to some embodiments. The UI 100 in FIG. 3A is in a scoreboard state, i.e., a data input has not been initiated by the user, and the dynamic banner 120 displays the game score.

[0062] FIG. 3B is a view of the UI 100 for recording and transmitting real-time sports data where the user has initiated a data input, according to some embodiments. For instance, the user has selected the two-point miss toggle 158, which generates a bolded two-point miss display 358. The input of a two-point shot attempt may activate the graphical display 140 and may activate the dynamic banner 120 to generate a two-point shot banner 320. The two-point shot banner 320 displays team statistics of two-point shot make / misses and / or percentage, and in some embodiments, includes a comparison between the first team and the second team.

[0063] FIG. 3C is a view of the UI for recording and transmitting real-time sports data where the user has initiated a data input, according to some embodiments. The user has selected a shot region on the graphical display 140, namely, the two-point shot region 144d, which generates a bolded (and / or highlighted) shot region 344d in an activated graphical display basketball court 340. The shot region selected by the user is indicative of the region on the basketball court where the shot attempt occurred.

[0064] FIG. 3D is a view of the UI 100 for recording and transmitting real-time sports data where the user has initiated a data input, according to some embodiments. The user has selected the on-court player 166e, which thereby generates a bolded player icon 366e. Thus, the on-court player 166e has been associated with a two-point miss statistic from the two-point shot region 144d. The activated graphical display basketball court 340 (and / or the graphical display 140) is updated to include a confirmation icon 304, and the dynamic banner 120 is updated to include an individual scoring banner 322. The bolded two-point miss display 358 can be updated to a filled two-point miss display 360, and the filled two-point miss display 360 may include a confirmation icon like confirmation icon 304.

[0065] The individual scoring banner 322 may include total points, field goal attempts, field goal makes, three-point attempts, and / or three-point makes. In some embodiments, the individual scoring banner 322 may include a bolded (or highlighted) display of the most recent statistical scoring input, i.e., in this case, a two-point miss. The individual scoring banner 322 may include a player icon, a player number, and / or a player name. The confirmation icon 304 and the individual scoring banner 322 provide an efficient confirmation that the relevant statistic was entered into the database and an efficient double-check for the user that the input statistic was accurate (correct action and correct player). After a delay period (e.g., 2 seconds), the UI 100 will revert back to the scoreboard state shown in FIG. 3A, with an updated score if points were scored.

[0066] FIG. 4A is a view of a UI 400 for recording and transmitting real-time sports data, according to some embodiments. The UI 400 in FIG. 4A is in a scoreboard state, e.g., a data input has not been initiated by the user, and the dynamic banner 120 displays the game score. In some embodiments, the UI 400 does not include the second statistical input toggle 150, the three-point make toggle 152, the three-point miss toggle 154, the two-point make toggle 156, and / or the two-point miss toggle 158. The shot make / miss can be recorded solely with the graphical display 140 of the UI 400. In one non-limiting example, the player display and the graphical display are accessible on a single page of the user interface.

[0067] UI 400 can include graphical display 140 depicting at least a portion of a basketball court and including one or more two-point regions and one or more three-point regions, wherein each of the one or more two-point regions and the one or more three-point regions include a shot attempt toggle configured for selection of a shot make or a shot miss. In one example, the shot attempt toggle fills the entire region that the shot attempt toggle is included within. For example, a user can click anywhere within a single region to select a shot make or a shot miss. As an example, activated two-point shot region 444d is shown in FIG. 4B. In other embodiments, the shot attempt toggle fills a portion of the region that the shot attempt toggle is included within.

[0068] During utilization, for example, a region of graphical display 140 can be selected based on an outcome of the game. For example, each region can be toggled for selection of a shot make or a shot miss. In some embodiments, the “toggle” refers to a user-selectable control (or other selectable region) that enables selection between discrete states and may use different visual appearances to indicate the current / selected state.

[0069] In some embodiments, each of the one or more two-point regions and the one or more three-point regions include a shot attempt toggle having a first discrete state, a second discrete state, and a third discrete state. The first discrete state is an unselected state, such as that of two-point shot region 144d. The second discrete state is representative of a shot miss, such as that of shot region 344d. The third discrete state is representative of a shot make. The user can select a region of graphical display 140 to switch between the discrete states, with various orders possible. For example, a single tap of a mobile device having a touch screen can convert a region to the second discrete state, and a double tap can convert the region to a third discrete state.

[0070] Data can be sent to database 102 when the second discrete state or the third discrete state is selected. In some embodiments, data is sent to database 102 once the second discrete state or the third discrete state is selected in coordination with a selected player. Data can be sent to the database 102 immediately upon selection, or can be sent after 0.5 seconds, after 1 second, or after 2 seconds of selecting the second discrete state or the third discrete state – allowing the user a chance to toggle through discrete states before data is sent to database 102.

[0071] FIG. 4B is a view of the UI 400 for recording and transmitting real-time sports data where the user has initiated a data input, according to some embodiments. For instance, the user has selected the two-point shot region 144d. The selection of the two-point shot region 144d with a single tap may indicate a missed shot from that region. In some embodiments, the selection of the two-point shot region 144d with a double tap and / or press-and-hold may indicate a made shot from that region. The graphical display 140 may be activated when the user selects a region, generating an activated graphical display basketball court 440. The activated graphical display basketball court 440 may display a first color (e.g., red) to indicate a missed shot input and a second color (e.g., green) to indicate a made shot input. FIG. 4B shows a missed-shot input on activated two-point shot region 444d. Input of a shot attempt may alter the dynamic banner 120 to display a shot banner 420. The shot banner 420 displays team statistics of shot make / misses and / or percentage, and in some embodiments, includes a comparison between the first team and the second team.

[0072] FIG. 4C is a view of the UI 400 for recording and transmitting real-time sports data where the user has initiated a data input, according to some embodiments. The user has selected the on-court player 166e, which thereby generates a bolded player icon 466e. Thus, the on-court player 166e has been associated with a two-point miss statistic from the two-point shot region 144d. The activated graphical display basketball court 440 (and / or the graphical display 140) is updated to include a confirmation icon 404. The confirmation icon 404 and the shot banner 420 provide an efficient confirmation that the relevant statistic was entered into the database and an efficient double-check for the user that the input statistic was accurate (correct action and correct player). After a delay period (e.g., 2 seconds), the UI 400 will revert back to the scoreboard state shown in FIG. 4A, with an updated score if points were scored. While FIG. 4C demonstrates that the on-court player 166e has been associated with a two-point miss statistic from the two-point shot region 144d after the two-point shot region 144d has been selected, in other embodiments the on-court player 166e can be selected before the shot region is selected.

[0073] The UI 400 provides a simplified display (as compared to the UI 100), as there are fewer input toggles and static sections to choose from. Shot attempts, shot makes (and thereby points scored), and shot location can be recorded from the graphical display 140. The scoring statistics recorded via the graphical display 140 can be associated with a player via the player display 160. The UI 400 thereby enables a user to record advanced basketball scoring statistics of a live basketball game with a minimum of two clicks (a first click for shot attempt location and make / miss status, and a second click for player). The two-click (or two input) statistical recordation provides quick and accurate recordation of player statistics from a single UI screen (no pop-up prompts nor multi-page UI).

[0074] The scoreboard can be updated based on selection of a shot region in UI 400. The scoreboard can be updated when the shot toggle selection is a shot make. Updating the scoreboard can include (1) determining whether the shot make was selected within the one or more two-point shot regions or the one or more three-point shot regions; and (2) determining whether the player selection corresponds to the first team score or the second team score. Updating the scoreboard is discussed further in method 1100.

[0075] Multiple users / scorekeepers can input recordable actions (sequentially, contemporaneously, and / or simultaneously) into UI 100, UI 400, and / or UI 1000 (discussed in FIG. 10), such as on multiple computing devices. In some embodiments, the system supports concurrent scorekeeping / input by multiple users during a single game session. For example, two or more scorekeepers may each operate a respective computing device (e.g., smartphone, tablet, laptop, or other computing device) executing an instance of the software to input recordable actions in real time as game events occur. The multiple computing devices may be associated with a synchronized game timeline such that the recordable actions entered on any device are communicated to database 102 and may be reflected to the other devices substantially contemporaneously. In this manner, the system enables simultaneous, multi-device entry of recordable actions for the same game, including entries made by different users for different teams, players, or player action types, while maintaining a unified record of game scoring and statistics.

[0076] The multiple computing devices may be associated with a synchronized game timeline such that the recordable actions entered on any device are communicated to database 102, with a recordable action being coordinated with a game time. Multiple computing devices can be in communication with each other using near-field communication. Multiple computing devices can be used without network connection, as data from the multiple devices can later be uploaded to database 102 and can be associated with a synchronized game timeline.

[0077] Regarding utilizing multiple users, one or more users can be designated as a primary scorekeeper(s). In some embodiments, a recordable action input by the primary scorekeeper(s) can alter the first team score or the second team score (e.g., shown in dynamic banner 120). In one example, the first team can designate a first primary scorekeeper to record score for the first team, and the second team can designate a second primary scorekeeper to record score for the second team. In another example, a primary scorekeeper inputs scores for both the first team and the second team, altering both the first team score and the second team score in real time. The computing devices may be associated with a synchronized game timeline such that the recordable actions entered by the primary scorekeeper(s) are communicated to database 102 and may be reflected to the other computing devices substantially contemporaneously.

[0078] In some embodiments, users other than the primary scorekeeper(s) may input recordable actions that do not change the first team score and the second team score. For example, users other than the primary scorekeeper(s) may select a player action toggle, where data indicative of the selected player action toggle is sent to database 102. In other embodiments, users other than the primary scorekeeper(s) may input recordable actions that do not alter data sent to database 102, where the recordable actions are stored locally for the individual user to view live or at a later time. Distinct settings can be applied to each user to alter capabilities of the individual user.

[0079] Multiple users can be utilized for entering distinct statistics throughout the game. For example, a first user can be designated to enter shot attempts, while a second user can be designated to enter rebounds. The first user can designate themselves as the shot attempt recorder, and UI 100, UI 400, and / or UI 1000 can notify other users of this designation. UI 100, UI 400, and / or UI 1000 can also notify users of open designations that have not been selected by any other user, such as player fouls.

[0080] As discussed, multiple users can input recordable actions (sequentially, contemporaneously, and / or simultaneously) into UI 100, UI 400, and / or UI 1000, such as on multiple computing devices. All, or a portion, of the data from multiple users can be sent to database 102. In some embodiments, the system receives data, from a first user using a first instance of the user interface, to database 102 and determines whether to update one or more distinct instances based on the data from the first user. In one example, the determination is made based on the user settings. The system can determine whether to update based on the designated user type, such as a primary scorekeeper. For example, if the first user is a primary scorekeeper, the system updates one or more distinct instances based on the data input by the first user. For example, when a primary scorekeeper selects a shot make, the system can update dynamic banner 120 (for all users viewing the game) by updating a team score based on which player was selectively coordinated with the shot make. Updating the team score can include updating the team score on multiple client devices running the software application including UI 100, UI 400, and / or UI 1000.

[0081] FIG. 5 is a view of a play-by-play UI 500 generating a display based on recorded data from the database 102, according to some embodiments. The play-by-play UI 500 may be accessed via the play-by-play tab 114 on the UI 100. Alternatively, or additionally, play-by-play UI 500 can be accessed via a distinct computing device, such as a tablet or laptop computer. The play-by-play UI 500 includes a score banner 520 which displays the current game score of the live basketball game (or final score if the game is completed). The score banner 520 includes a filter toggle 522 to filter by team, player, statistic type, etc. Each play of the play-by-play log includes one or more of time, team, brief description of play, score, player, and upload status. For instance, a local database icon 524 may be displayed when the data has been stored locally on the electronic device, and an upload complete icon 526 may be displayed when the data is uploaded to a network database.

[0082] FIG. 6 is a view of a statistical analysis UI 600 generating a display based on recorded data from the database 102, according to some embodiments. The statistical analysis UI 600 includes a graphical display 640. The graphical display 640 includes a plurality of three-point shot regions 642a, 642b, 642c, 642d, 642e, a plurality of two-point shot regions 644a, 644b, 644c, 644d, 644e, and a paint region 646. The graphical display 640 displays a summary of shot attempts and shot makes per region of the court, based on data input into the graphical display 140. For instance, the graphical display 640 shows one shot attempt from the three-point shot region 642c, and zero shot makes from the three point shot region 642c. The graphical display 640 may be color coded based on a shooting percentage. For instance, regions where the shooting percentage (percentage of field goal makes versus attempts) exceeds 50% may be a first color (e.g., green), regions where the shooting percentage is between 20%-50% may be a second color (e.g., yellow), and regions where the shooting percentage is less than 20% may be a third color (e.g., red). The thresholds and colors may be modified by the user. Other visual appearances can be utilized in addition, or alternatively, to colors.

[0083] The graphical display 640 may provide live-game insights based on the data recorded by the UI 100 or UI 400. For instance, a team may target shots from the regions on the court where shooting percentage is high—and avoid taking shots from regions where shooting percentage is low. The graphical display 640 may highlight areas of improvement for teams, e.g., if shooting percentage along the baseline is low, the team may recognize the deficiency and practice shooting from the baseline.

[0084] In some embodiments, the graphical display 640 may be generated for each player, if, for instance, the user selects a player from the player display 160. The graphical display 640 can be used by players and coaches to recognize strengths and weaknesses of an individual player, and highlight areas of improvement (e.g., three-point shooting from the right side) to practice.

[0085] The statistical analysis UI 600 may include a first team toggle 662, a second team toggle 668, and a comparison toggle 664. The statistical analysis UI 600 shown in FIG. 6 has selected the comparison toggle 664. Each statistical category, e.g., a field goal made stat 652 and a two-point made stat 654 may include a comparison between the first team and the second team.

[0086] FIG. 7 is a view of a statistical comparison UI 700 generated based on recorded data from the database 102, according to some embodiments. Data from the database 102, recorded via the UI 100 or UI 400, may be compiled into first team statistics 706a and second team statistics 706b. The data may be displayed side-by-side to allow a user to compare the respective stats. FIG. 8 is a view of a player statistic UI 800 generated based on recorded data from the database 102, according to some embodiments. Data from the database 102, recorded via the UI 100 or UI 400, may be compiled into player statistics 808. The data may be displayed by category.

[0087] FIG. 9 is a flow chart of a method 900 of statistical recordation of a live basketball game, according to some embodiments. Method 900 includes providing 910 a user interface (UI). The UI may include any and / or all features of the UI 100 and / or UI 400 described above. The UI may be provided / accessed on an electronic device, including for instance, a computing device such as a tablet or smart phone. A shot region is selected 920 from the plurality of shot regions on the graphical display basketball court of the UI based on a shot attempt location of the live basketball game. A player is selected 930 from the player display of the UI based on which player attempted the shot attempt in the live basketball game. The recorded data is uploaded 940 into a database. The database may be local (i.e., saved on the electronic device) and / or may be a cloud-based database.

[0088] FIG. 10 illustrates a view of a UI for recording and transmitting real-time sports data, according to some embodiments. User interface (UI) 1000 can include one or more features and / or configurations of UI 100 and / or UI 400. UI 1000 includes at least one of tab selection portion 110, dynamic banner 120, graphical display 140, player display 160, player action toggle 170, scoreboard section 180, control section 190, settings toggle 1015, result display 1025, a plurality of team toggles 1035, substitution toggle 1045, and flag toggle 1055. UI 1000 can include all of tab selection portion 110, dynamic banner 120, graphical display 140, player display 160, player action toggle 170, scoreboard section 180, control section 190, settings toggle 1015, result display 1025, a plurality of team toggles 1035, substitution toggle 1045, and flag toggle 1055.

[0089] Settings toggle 1015 can be selected to view and / or update one or more settings coordinated with the UI 1000 and / or database 102. In some embodiments, settings toggle 1015 can be selected to show one or more settings coordinated with the UI 1000 and / or database 102 within the same page of UI 1000. In other embodiments, settings toggle 1015 can be selected to show one or more settings coordinated with the UI 1000 and / or database 102 in a pop-up menu. Settings coordinated with UI 1000 can include at least one of a view setting, a database setting, a team setting, or a scorekeeper setting. For example, settings toggle 1015 can be selected to change a view of UI 1000, such as changing a position of one or more of tab selection portion 110, dynamic banner 120, graphical display 140, player display 160, player action toggle 170, scoreboard section 180, control section 190, settings toggle 1015, result display 1025, a plurality of team toggles 1035, substitution toggle 1045, and flag toggle 1055. As an example, graphical display 140 can be repositioned above result display 1025. As another example, graphical display 140 can be repositioned below scoreboard section 180.

[0090] Result display 1025 visibly shows one or more results of the current sports game. For example, result display 1025 includes one or more previously recorded player actions and / or shot attempt results. The one or more previously recorded player actions and / or shot attempt results can be arranged in chronological order, from bottom to top, or from top to bottom. In the embodiment shown in FIG. 10, the one or more previously recorded player actions and / or shot attempt results are arranged in chronological order from bottom to top. For example, the latest recorded action is an assist, coordinated with selected player number 17. Result display 1025 can be updated continuously throughout the live sports game. In one example, result display 1025 is updated on all client devices, but is only updated based on input from one or more primary scorekeepers.

[0091] The one or more previously recorded player actions and / or shot attempt results shown in result display 1025 can be manually flagged (e.g., marked) by one or more users. For example, manually flagging the one or more previously recorded player actions and / or shot attempt results shown in result display 1025 can include selecting at least one of the one or more previously recorded player actions and the shot attempt result. Accordingly, each of the previously recorded player actions and the shot attempt result can include a toggle for the user to select and flag the result. In other embodiments, the user can flag one or more previously recorded player actions and / or shot attempt results shown in result display 1025 using a flag toggle, such as flag toggle 1055.

[0092] A selected portion within result display 1025 can exhibit at least one change in visual appearance compared to an unselected state. In one example, the color can be changed to indicate a selected state. In another example, a symbol, such as a flag, can be added adjacent one or more previously recorded player actions and / or shot attempt results shown in result display 1025. Manually flagging one or more previously recorded player actions and / or shot attempt results shown in result display 1025 can be beneficial to “mark” a recordable action for later view, or to indicate the recordable action may have been entered by mistake.

[0093] While graphical display 140 in FIG. 10 illustrates one or more two-point regions and one or more three-point regions of a portion of a basketball court, in some embodiments graphical display 140 can illustrate a greater portion of the basketball court, such as the entire basketball court. While graphical display 140 in FIG. 10 illustrates one or more two-point regions and one or more three-point regions of a portion of a basketball court, user interfaces of the present disclosure can be configured for other sports, such as football, baseball, soccer, volleyball, tennis, and pickleball. Therefore, graphical display 140 can be dynamically updated to display a portion of a court or field depending on the selected sports game. For sports other than basketball, one or more components of UI 1000 can be updated according to the selected sport, such as one or more of dynamic banner 120, player display 160, player action toggle 170, and scoreboard section 180.

[0094] The plurality of team toggles 1035 generally includes a first team toggle and a second team toggle. The first team toggle is associated with a first team, and the second team toggle is associated with a second team. The first team toggle can include a team logo and / or team name. The second team toggle can include a team logo and / or team name. The first team toggle and the second team toggle can be configured to dynamically change which players are shown in player display 160. For example, when the first team toggle is selected, the on-court players associated with the first team are shown in player display 160. In some embodiments, when the on-court players associated with the first team are shown in player display 160, players associated with the second team are not shown in player display 160.

[0095] Substitution toggle 1045 can be selected to change one or more players shown in player display 160. For example, one or more on-court players can be substituted with one or more bench players. In some embodiments, the player display 160 includes a dynamic scroll, where the list of players can scroll (e.g., vertically scroll). In some embodiments, the substitution toggle 1045 allows players to be swapped, e.g., a bench player can be selected, and an in-game player can be selected to swap positions.

[0096] Flag toggle 1055 can be selected to mark a recorded action. Marking a recorded action can include selecting flag toggle 1055, where when flag toggle 1055 is selected, the latest recorded action is marked. For example, if the user believes that the latest recorded action may have been entered by mistake, or if the user would like to quickly find the latest recorded action at a later time, the user can select flag toggle 1055 to mark the latest recorded action. In other embodiments, the user can select flag toggle 1055 and then select a recorded action to mark within result display 1025. The marked recorded action can be dynamically changed to highlight the recorded action. For example, the marked recorded action can exhibit a visual appearance change, such as a color change within the region of the recorded action within result display 1025.

[0097] FIG. 11 illustrates a method for statistical recordation of a basketball game, according to some embodiments. A player selection and a shot toggle selection are received 1110 from a user interface. The user interface can include one or more user interfaces of the present disclosure. The player selection and the shot toggle selection can be received at database 102.

[0098] The player selection includes data representative of a selected player, where the selected player includes a player selected from player display 160. Data representative of the selected player can include at least one of the player’s name, the team associated with the selected player, and one or more player statistics. Often, a shot toggle selection is selected in coordination with the player selection, based on which individual player completed the shot attempt. In some embodiments, the player selection and the shot toggle selection are transmitted to database 102 substantially simultaneously. The shot toggle selection can include data received from a shot attempt toggle. For example, the shot attempt toggle can be the shot attempt toggle discussed for UI 400.

[0099] Data received from the shot attempt toggle can include shot attempt data. Shot attempt data can include data indicative of a shot make or a shot miss. For example, each of the one or more two-point regions and the one or more three-point regions of graphical display 140 can include a shot attempt toggle having a first discrete state, a second discrete state, and a third discrete state. The first discrete state is an unselected state, such as that of two-point shot region 144d. The second discrete state is representative of a shot miss, such as that of shot region 344d. The third discrete state is representative of a shot make. In some embodiments, a fourth discrete state can be utilized for a 1-point free throw make. In some embodiments, the free throw attempt can be a separate region in graphical display 140.

[0100] Data received from the shot attempt toggle can include region data. As discussed, graphical display 140 can illustrate at least a portion of a basketball court and includes one or more two-point regions and one or more three-point regions, where each of the one or more two-point regions and the one or more three-point regions include a shot attempt toggle configured for selection of a shot make or a shot miss. The region data can include a specific location (e.g., x,y coordinates) selected by the user in a coordinate space. The x,y coordinates can indicate which region was selected by mapping the x,y coordinates to the displayed court geometry. The region data can include which specific region was selected by the user. For example, the specific region can be one of two-point shot regions 144a, 144b, 144c, 144d, 144e, paint region 146, and three-point shot regions 142a, 142b, 142c, 142d, 142e. Each of these specific regions can be pre-classified in the database 102 as corresponding to a 2-point region or value, or a 3-point region or value.

[0101] The scoreboard is updated 1120 when the shot toggle selection is the shot make. Updating 1120 can include (1) determining whether the shot make was selected within the one or more two-point shot regions or the one or more three-point shot regions; and (2) determining whether the player selection corresponds to the first team score or the second team score. Determining whether the shot make was selected within the one or more two-point shot regions or the one or more three-point shot regions can include analyzing the latest data received from the shot attempt toggle from a user, such as the primary scorekeeper.

[0102] Analyzing the latest data received from the shot attempt toggle can include reviewing, in database 102, for the most recent shot toggle selection received in coordination with the player selection. Database 102 can be continuously reviewed using timestamps and / or sequence identifiers. Analyzing the latest data received from the most recent shot toggle selection can include matching region data from the selected shot attempt toggle with a pre-classified region in the database. Analyzing the latest data received from the most recent shot toggle selection can include mapping user selected (e.g., tapped position on a touch interface) x,y coordinates to the displayed court geometry.

[0103] Determining whether the player selection corresponds to the first team score or the second team score can include reviewing the player selection coordinated with the most recent shot toggle selection. In one example, it is determined that the player selection corresponds to the first team score or the second team score by matching the player selection to a pre-classified team roster stored in database 102. In another example, it is determined that the player selection corresponds to the first team score or the second team score by receiving data representative of the selected player, where the selected player includes a player selected from player display 160. Data representative of the selected player can include the team associated with the selected player.

[0104] When it is determined that the scoreboard should be updated 1120, the scoreboard on each instance of the user interface can be substantially simultaneously updated. For example, when the latest shot toggle selection corresponds to the third discrete state, the scoreboard can be updated by applying the corresponding point value (+2 or +3) to the appropriate team score. The scoreboard can be selectively updated based on which user inputs the data to database 102.

[0105] Updating the scoreboard based on a shot toggle selection in graphical display 140 increases scorekeeping efficiency. Scorekeeping efficiency can be increased by updating both the scoreboard (e.g., team score) and player statistics based on a shot toggle selection and a player selection, removing one or more additional conventional steps. For example, conventionally, when a player makes a shot in basketball, a scorekeeper would select all of (1) a score toggle (e.g., separate buttons for +1, +2, or +3 points) to update the total team score; (2) a player shot attempt statistic; and (3) the corresponding player. Further, updating the scoreboard based on a shot toggle selection in graphical display 140 can improve accuracy, since basketball is fast-paced, and a visual indicator (e.g., color change) of a shot make in a shot region can improve statistical accuracy.

[0106] While embodiments of the present disclosure include user interfaces for recording statistics of a basketball game, in other embodiments, the user interfaces can be utilized for other sports, such as tennis, soccer, baseball, and football. For example, for soccer, UI 100 can include tab selection portion 110, dynamic banner 120 showing at least the team scores, graphical display 140 showing at least a portion of a soccer field, player display 160, player action toggle 170 (e.g., soccer action for a pass, assist, block, and / or save), and scoreboard section 180 including a clock, such as a countdown timer.

[0107] FIG. 12 illustrates system 1200 for analyzing sports data, according to some embodiments. System 1200 includes a computing device 1201 that includes processor 1220 and memory 1230. Processor 1220 can include at least one processing component such as a microcontroller, microprocessor, central processing unit (CPU), graphics processing unit (GPU), tensor processing unit (TPU), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA), neural processing unit (NPU), quantum processor, or the like configured to execute instructions to perform the functions described herein. Memory 1230 can include at least one storage medium such as a non-volatile memory component (e.g., a FLASH memory), volatile memory component (e.g., magnetic memory), or the like configured to store executable instructions and / or data. Memory 1230 may include one or more memory components local to the computing device 1201 and / or coupled to the computing device via a network such as a cloud storage medium. Processor 1220 can execute instructions stored by memory 1230. System 1200 can implement one or more methods of the present disclosure. System 1200 can be in communication with, and / or include UI 100, UI 400, UI 1000, and / or database 102.

[0108] In some examples, the various techniques described herein for updating the user interface or analyzing recorded data may be implemented by software instructions executable by the processor 1220 to perform the various functions described. In other examples, such instructions may be executed to implement a machine learning model trained to implement the various functions described. In one example, the machine learning model can input recorded data entered by one or more users to determine accuracy of the recorded data.

[0109] The inputs 1210 to the system and / or machine learning model can include recorded data of the present disclosure, such as a recordable action (e.g., shot action such as a shot make or shot miss and / or a player action such as a steal, assist, turnover, etc.), a time of game, a possession indication, and / or a selected player. Input 1210 can include a shot toggle selection. In one example, the input 1210 includes a shot make and a coordinated selected player. In another example, the input 1210 can include data from one or more selected toggles of UI 100, UI 400, and / or UI 1000. In another example, the input 1210 can include video data (such as a recording or live feed of the current game) or photographic data.

[0110] The machine learning model can analyze the input 1210 (e.g., recorded data) to determine the accuracy of the recorded data. For example, the machine learning model can analyze the recorded data to determine the quantitative accuracy of the recorded data, indicating a possible scorekeeping mistake based on a low quantitative accuracy determination. Additionally, or alternatively to manual user flagging discussed herein, the machine learning model can determine a predicted accuracy of the latest recorded data and can automatically flag the latest recorded data based on a low quantitative accuracy determination. This can be beneficial to increase scorekeeping accuracy and efficiency, as system 1200 can automatically flag user input to indicate a possible statistical error to the user.

[0111] Output 1240 can include a numerical value, a Boolean value, and / or a dataset based on data from input 1210. In one example, output 1240 includes a quantitative accuracy. For example, output 1240 can include a numerical value, such as a numerical percentage value. For example, the numerical value can be a value ranging from 0 to 100. The numerical value can be compared to a pre-determined threshold.

[0112] In one example, output 1240 includes instructions to remove the latest recorded action when the numerical value corresponding to a quantitative accuracy is less than a pre-determined threshold. For example, the pre-determined threshold can include a numerical value, such as 10, 20, 30, 40, 50, or 60. By way of example, if a scorekeeper mistakenly enters the wrong statistic, output 1240 could output a value of 10, indicating a 10% accuracy determination, and if the threshold is 20%, system 1200 can process the instructions to remove the latest recorded action from the user interface display and / or the database.

[0113] In another example, output 1240 includes instructions to flag a recorded action when the numerical value corresponding to a quantitative accuracy is less than a pre-determined threshold. For example, the pre-determined threshold can include a numerical value, such as 10, 20, 30, 40, 50, or 60. By way of example, if a scorekeeper mistakenly enters the wrong statistic, output 1240 could output a value of 10, indicating a 10% accuracy determination, and if the threshold is 20%, system 1200 can process the instructions to flag the recorded action.

[0114] Such a machine learning model may be trained using supervised or unsupervised training data to operate as described. For example, the machine learning model may be fed measured or automatically generated deterministic training data with a known outcome until the machine learning model is configured to replicate a desired outcome when fed with new training or other data. The machine learning model may store associations in memory based on the training. Once trained, the machine learning model may be instantiated on the same or a different processor, including processor 1220 of computing device 1201, and use the stored associations to automatically process new data. In some examples, once instantiated, the machine learning model may continue training and updating stored associations as the machine learning model processes new data.

[0115] The training data for training the model can include at least one of video data (such as a video recording), photographic data, past recorded data, and associations of pre-determined flagged actions. For example, associations of pre-determined flagged actions can include manually flagged actions, such as flagged actions using flag toggle 1055. Additionally, the trained model can undergo further training by user input, such as via a user interface. For example, the user can accept or decline an automatically flagged action determined by system 1200.

[0116] In some examples, system 1200 may include a single machine learning model executing on the processor previously trained and configured to operate alone or in combination with traditional software to perform the various functions described herein. In other examples, the system 1200 may include multiple machine learning models each trained and / or instantiated to execute different parts of the various methods described, alone or in combination with traditional software.

[0117] While the invention has been described with reference to an exemplary embodiment(s), it will be understood by those skilled in the art that various changes may be made and equivalents may be substituted for elements thereof without departing from the scope of the invention. In addition, many modifications may be made to adapt a particular situation or material to the teachings of the invention without departing from the essential scope thereof. Therefore, it is intended that the invention not be limited to the particular embodiment(s) disclosed, but that the invention will include all embodiments falling within the scope of the appended claims.Discussion of Possible Embodiments

[0118] Clause 1. A user interface for statistical recordation of a basketball game, comprising: a player display including a plurality of selectable players; and a graphical display depicting at least a portion of a basketball court and including one or more two-point regions and one or more three-point regions, wherein each of the one or more two-point regions and the one or more three-point regions include a shot attempt toggle configured for selection of a shot make or a shot miss, wherein the player display and the graphical display are accessible on a single page of the user interface.

[0119] The clause of the preceding paragraph can optionally include, additionally and / or alternatively any one or more of the following features, configurations and / or additional components.

[0120] Clause 2. The user interface of clause 1, wherein the player display includes a plurality of dynamic player icons on a scroll wheel.

[0121] Clause 3. The user interface of clause 2, wherein each of the plurality of dynamic player icons includes a foul indicator.

[0122] Clause 4. The user interface of clause 1, further including a scoreboard including a first team score and a second team score.

[0123] Clause 5. The user interface of clause 4, wherein the scoreboard is configured to update based on: (1) whether the shot make is selected in the one or more two-point regions or the one or more three-point regions; and (2) selection of one player from the plurality of selectable players.

[0124] Clause 6. The user interface of clause 1, including a first player action toggle configured to dynamically provide a first visual indication based on selection of a shot make.

[0125] Clause 7. The user interface of clause 6, wherein the first player action toggle includes an assist toggle configured to associate an assist with one or more of the plurality of selectable players.

[0126] Clause 8. A user interface for statistical recordation of a basketball game, comprising: a player display including a plurality of selectable players; a graphical display depicting at least a portion of a basketball court and including one or more two-point shot regions and one or more three-point shot regions, wherein each of the one or more two-point shot regions and the one or more three-point shot regions include a shot toggle configured for selection of a shot make or a shot miss; and; a first player action toggle configured to dynamically provide a first visual indication based on selection of a shot make; and a second player action toggle configured to dynamically provide a second visual indication based on selection of a shot miss.

[0127] The clause of the preceding paragraph can optionally include, additionally and / or alternatively any one or more of the following features, configurations and / or additional components.

[0128] Clause 9. The user interface of clause 8, wherein the first player action toggle includes an assist toggle configured to associate an assist with one or more of the plurality of selectable players.

[0129] Clause 10. The user interface of clause 8, wherein the second player action toggle includes a rebound toggle configured to associate a rebound with one or more of the plurality of selectable players.

[0130] Clause 11. The user interface of clause 8, wherein the player display and the graphical display are static regions that are simultaneously accessible by a user.

[0131] Clause 12. The user interface of clause 11, wherein the player display, the graphical display, the first player action toggle, and the second player action toggle are included on a single page of the user interface.

[0132] Clause 13. The user interface of clause 8, further including a scoreboard including a first team score and a second team score.

[0133] Clause 14. The user interface of clause 8, wherein the player display includes a plurality of dynamic player icons.

[0134] Clause 15. The user interface of clause 14, wherein each of the plurality of dynamic player icons includes a foul indicator.

[0135] Clause 16. The user interface of clause 8, wherein the first player action toggle and the second player action toggle are arranged exterior to the graphical display.

[0136] Clause 17. The user interface of clause 8, wherein the first visual indication includes a color change.

[0137] Clause 18. A method for statistical recordation of a basketball game, comprising: receiving a player selection and a shot toggle selection from a user interface, wherein the user interface includes: a player display including a plurality of selectable players; a graphical display depicting at least a portion of a basketball court and including one or more two-point shot regions and one or more three-point shot regions, wherein each of the one or more two-point shot regions and the one or more three-point shot regions include a shot toggle configured for the shot toggle selection of a shot make or a shot miss; and a scoreboard including a first team score and a second team score; and updating the scoreboard when the shot toggle selection is the shot make, wherein updating the scoreboard includes (1) determining whether the shot make was selected within the one or more two-point shot regions or the one or more three-point shot regions; and (2) determining whether the player selection corresponds to the first team score or the second team score.

[0138] The clause of the preceding paragraph can optionally include, additionally and / or alternatively any one or more of the following features, configurations and / or additional components.

[0139] Clause 19. The method of clause 18, wherein the player display and the graphical display are accessible on a single page of the user interface.

[0140] Clause 20. The method of clause 19, wherein the user interface includes a first player action toggle configured to dynamically provide a first visual indication based on selection of a shot make.

[0141] Clause 21. A user interface (UI) for statistical recordation of a live basketball game includes: a player display including a plurality of selectable players; and a graphical display including a plurality of three-point shot regions and a plurality of two-point shot region; wherein a shot attempt of the live basketball game is recorded via selection of a region of the graphical display basketball court and a selection of one of the selectable players of the player display.

[0142] Clause 22. A method of statistical recordation of a live basketball game includes: providing a user interface (UI), the UI including: a player display, and a plurality of shot regions on a graphical display, selecting a shot region from the plurality of shot regions on the graphical basketball court based on a shot location of the live basketball game; and selecting a player from the player display based on which on-court player attempted a shot attempt.

Examples

Embodiment Construction

[0028] The present disclosure describes systems and methods for recording and transmitting real-time sports data, including a user interface (UI) for inputting statistics to a database. The UI includes a player display to allow a user to select which player has completed a recordable action in the game. The user may select the recordable action (e.g., shot action such as a shot make or shot miss and / or a player action such as a steal, assist, turnover, etc.) via a plurality of labeled toggles. The UI includes a graphical display to allow the user to record or view the region where a recordable action (e.g., a basketball shot) was performed or attempted from. In some embodiments, the UI is a single-page display, with no pop ups, to enable efficient and accurate data inputs. If, for instance, the UI was multi-page and / or included pop-up prompts or menus, the scorekeeper may not be able to accurately keep pace with the real-time statistical recordation of the sports game (e.g., a...

Claims

1. A user interface for statistical recordation of a basketball game, comprising:a player display including a plurality of selectable players; and a graphical display depicting at least a portion of a basketball court and including one or more two-point regions and one or more three-point regions, wherein each of the one or more two-point regions and the one or more three-point regions include a shot attempt toggle configured for selection of a shot make or a shot miss, wherein the player display and the graphical display are accessible on a single page of the user interface.

2. The user interface of claim 1, wherein the player display includes a plurality of dynamic player icons on a scroll wheel.

3. The user interface of claim 2, wherein each of the plurality of dynamic player icons includes a foul indicator.

4. The user interface of claim 1, further including a scoreboard including a first team score and a second team score.

5. The user interface of claim 4, wherein the scoreboard is configured to update based on: (1) whether the shot make is selected in the one or more two-point regions or the one or more three-point regions; and (2) selection of one player from the plurality of selectable players.

6. The user interface of claim 1, including a first player action toggle configured to dynamically provide a first visual indication based on selection of a shot make.

7. The user interface of claim 6, wherein the first player action toggle includes an assist toggle configured to associate an assist with one or more of the plurality of selectable players.

8. A user interface for statistical recordation of a basketball game, comprising:a player display including a plurality of selectable players;a graphical display depicting at least a portion of a basketball court and including one or more two-point shot regions and one or more three-point shot regions, wherein each of the one or more two-point shot regions and the one or more three-point shot regions include a shot toggle configured for selection of a shot make or a shot miss; and;a first player action toggle configured to dynamically provide a first visual indication based on selection of a shot make; anda second player action toggle configured to dynamically provide a second visual indication based on selection of a shot miss.

9. The user interface of claim 8, wherein the first player action toggle includes an assist toggle configured to associate an assist with one or more of the plurality of selectable players.

10. The user interface of claim 8, wherein the second player action toggle includes a rebound toggle configured to associate a rebound with one or more of the plurality of selectable players.

11. The user interface of claim 8, wherein the player display and the graphical display are static regions that are simultaneously accessible by a user.

12. The user interface of claim 11, wherein the player display, the graphical display, the first player action toggle, and the second player action toggle are included on a single page of the user interface.

13. The user interface of claim 8, further including a scoreboard including a first team score and a second team score.

14. The user interface of claim 8, wherein the player display includes a plurality of dynamic player icons.

15. The user interface of claim 14, wherein each of the plurality of dynamic player icons includes a foul indicator.

16. The user interface of claim 8, wherein the first player action toggle and the second player action toggle are arranged exterior to the graphical display.

17. The user interface of claim 8, wherein the first visual indication includes a color change.

18. A method for statistical recordation of a basketball game, comprising:receiving a player selection and a shot toggle selection from a user interface, wherein the user interface includes:a player display including a plurality of selectable players; a graphical display depicting at least a portion of a basketball court and including one or more two-point shot regions and one or more three-point shot regions, wherein each of the one or more two-point shot regions and the one or more three-point shot regions include a shot toggle configured for the shot toggle selection of a shot make or a shot miss; anda scoreboard including a first team score and a second team score; andupdating the scoreboard when the shot toggle selection is the shot make, wherein updating the scoreboard includes (1) determining whether the shot make was selected within the one or more two-point shot regions or the one or more three-point shot regions; and (2) determining whether the player selection corresponds to the first team score or the second team score.

19. The method of claim 18, wherein the player display and the graphical display are accessible on a single page of the user interface.

20. The method of claim 19, wherein the user interface includes a first player action toggle configured to dynamically provide a first visual indication based on selection of a shot make.

Images