Patent Grant
11972579
Embodiments of the disclosure relate to the field of user adaptive training and entertainment platforms. More specifically, one embodiment of the disclosure relates to an automated, computerized system for tracking an object within an enclosed space including a plurality of time-synchronized cameras specifically calibrated and configured to detect the object within a series of captured images and determine a trajectory of the object as it approaches a predefined point within the space such as a wall.
In various sports, to be in control of the ball is of importance to every level of player. The ability to control an awkward bouncing or awkwardly thrown or launched ball quickly and effectively gives the player with the ball the immediate advantage. A player's first touch is often the difference between success and failure in most situations within a sporting event. Additionally, accuracy in passing and shooting a ball is essential in developing a well-rounded game in most sports. As players develop in skill, the level of competition increases, which typically results in an increase in the speed of game situations thereby demanding more speed from the player. Consequently, there is a greater need for accurate and precise interactions with a ball, such as accurate shooting and passing. Often, players cannot always place a ball, either to score a goal or even to place a shot or pass within a specific location of the goal (or desired location)—e.g., out of the reach of the goalie; therefore, a player may miss out on an opportunity to score points or assist a teammate.
Players can improve the accuracy of their shooting and passing by performing shooting and passing drills. Often, however, a player is unable to concentrate on keeping track of the location of each pass or shot within a goal or other area during drills involving several balls. Therefore, by the end of the drill, a player typically does not remember his/her accuracy and cannot determine whether he/she is improving based on results of previous drills. Additionally, although players may utilize video recording to review their training sessions or game play, a player may not understand the proper mechanics of performing certain moves or drills, and as a result, fail to learn anything from merely watching a video recording. Video recording technologies exist in which a video is captured of a ball (such as a golf ball) being hit from a static position with computer analysis performed on the player's swing. However, most sports are not limited to hitting a static ball; therefore, current technologies used to analyze a golf swing cannot be applied to analyze all aspects of other sports in which a critical component of the game is receiving a moving object.
In addition to the aim of many athletes to improve their performance within a specific sport, there is a large portion of the world population that enjoys sports and participates recreationally as opposed to competitively. This portion of the population may desire to participate in sport-like activities that do not necessarily require fully suiting up and participating in an organized, or even unorganized, sporting match. Using soccer, or football as it is referred to throughout most of the world, as one example, a person or groups of persons may desire to recreationally kick a soccer ball around or at a goal within a social atmosphere. Further, this group of persons may desire to compete against each other in ways such as determining who can most accurately kick a set of balls without having to chase after missed shots or collect kicked balls.
Additionally, this person or group of persons may desire to have their experience incorporate some form of video technology that enables simulation of various scenarios, such as simulating taking a penalty shot against a famous goalkeeper. Even further, this person or group of persons may desire to see a replay of their interactions with the ball.
The systems and methods disclosed herein provide unique and novel solutions to address shortcomings of current technologies with respect to the above. The concepts provided herein will become more apparent to those of skill in the art in view of the accompanying drawings and following description, which disclose particular embodiments of such concepts in greater detail.
Embodiments of the disclosure are illustrated by way of example and not by way of limitation in the figures of the accompanying drawings, in which like references indicate similar elements and in which:
Various embodiments of the disclosure relate to an object tracking system that improves object tracking within a defined space and generating graphical visualizations based on data obtained or determined as a result of the object tracking. In some particular embodiments, the object tracking system includes a plurality of cameras that capture a series of images of a defined space following the launch of an object. The object tracking system further includes logic that receives the captured images and performs object recognition analyses to detect the object within images and “track” the object as it moves through the defined space.
More particularly, the plurality of cameras may be disposed around a defined space in a mirrored configuration such that half of the cameras are disposed on a first side of the defined space and the other half of the cameras are disposed on a second side, opposite the first side. Specifically, a first camera on a first side of the defined space is mirrored in physical placement and orientation by a second camera on the second side. The orientation of the cameras is such that an entire half of the defined space is captured by the field of view of at least two cameras on a given side, where the given side is opposite the side within the field of view. Additionally, the cameras are time-synchronized so each camera captures an image simultaneously (e.g., within a 40-nanosecond range) such that the object is located at the same point in the defined space in each image. The set of captured images for a given time are analyzed by logic of the object tracking system to detect the object and triangulate the object's position within the defined space using two of the captured images.
As will be discussed in further detail below, the camera configuration described above solves the problem of failing to capture two images where both images contain a moving object to be tracked at the same location and where both images are not affected by occlusion from the moving object, i.e., the object being within a close proximity to the camera lens such as substantially 1-1.5 meters. The need for two such images stems from the use of triangulation to determine the object's location within the defined space.
Further embodiments of the disclosure relate to an analysis of the moving object's determined location over time to determine a particular point on a wall, screen, netting, etc., of the defined space that the object is expected to contact and generating a visual graphic for display based on the determined point. For instance, the object may be traveling through the defined space toward a wall of the defined space and, when the object is determined to be a threshold distance from the wall based on the location tracking, the logic of the object tracking system may perform an analysis to determine a point on the wall that the object is expected to hit. The logic may then cause a graphic visualization to be displayed on the wall based on the determined point. As an alternative embodiment, a netting may be placed in front of an electronic screen (e.g., a television screen or monitor in communication with a computer), on which the visual graphic is rendered.
The examples provided in the disclosure are generally based in athletics and use specific terms relevant to sports (e.g., kick, ball); however, the disclosure is not intended to be limited to such examples. Instead, the such examples are merely intended to provide for an illustrative and clear description of the features of the invention. Further, although American soccer (generally referred to as “football” elsewhere in the world including the United Kingdom for example) is used as the primarily example, the disclosure is not so limited and instead applies to various sports including, but not limited or restricted to, soccer (football), American football, softball, baseball, hockey, tennis, golf, lacrosse, Frisbee, ping pong, rugby and/or basketball. The specific examples provided are done so for purposes of clarity and continuity throughout the description and illustrations.
Current camera systems and accompanying computer vision logic are insufficient to fill the particular objectives referenced above. Specifically, no current camera system and accompanying computer vision technology includes a plurality of time-synchronized cameras that capture a series of images such that accompanying computer vision logic may analyze a plurality of images, such that the analyses track the location of an object from the moment it is launched until the time the ball is received by a player, and from the moment the ball is released by the player toward a particular point or area (e.g., a screen, wall, or other designated area such as a physical goal apparatus). It should be understood that the term a “goal scored” (or comparable wording) refers to a ball contacting a particular a point of the screen 102, where some graphic is displayed on the screen 102.
In particular, one aspect in which current camera systems and accompanying computer vision logic fail to meet the above objectives is the inability of such systems and logic to handle the tracking of certain “large” objects at a close range, especially when the object is moving within a defined space. One example of a large object is a soccer ball where close range may refer to 1-1.5 meters from a camera lens. In some instances, the defined space may be 4.5 meters wide, 10 meters long, and approximately 3-3.5 meters in height. However, these measurements are merely intended as one illustration and not intended to be limited in any respect.
When considering traditional sports arenas or playing fields, there are a number of readily apparent differences from the predefined space discussed herein with one exemplary embodiment illustrated in
As one illustrative example, an American football stadium may have several cameras disposed around the stadium positioned to capture images or video of the football game. As the cameras are placed so far from the action, the football does not come close enough to a camera to occlude the view of the camera. Stated otherwise, as the football is so small relative to the field of view of the camera, the camera does not suffer from issues of ball occlusion. Thus, the camera configurations and accompanying logic of current camera systems do not account for possible occlusion of a camera's field of view. Further, such camera systems are not time-synchronized and configured to capture images simultaneously (e.g., within 40 nanoseconds).
The invention disclosed herein addresses new problems that arose due to the desire to track an object within a small and/or confined playing surface (“a studio space”). In particular, the studio space configuration created the problem of an object (e.g., a ball) occluding the view of a camera when the ball came within a close distance of the camera (e.g., substantially 1 meter) such that an image captured by the occluded camera lens is insufficient for use by logic of the object-tracking system to triangulate the location of the ball. In particular, when an image is captured with the ball at such a close distance to the lens of the camera, the logic of the object-tracking system cannot identify features of the studio space due to ball occlusion and therefore cannot use the image to triangulate the location of the ball.
As will be discussed in further detail below, the invention addresses the occlusion problem through a particular camera configuration where a plurality of cameras are disposed surrounding the playing surface of the studio space such that half of the plurality of cameras are located on a first side of the playing surface and the other half of the plurality of cameras are located on the opposite side, where the two halves are located in mirrored physical placement and orientation. Further, the configuration is such that a longitudinal half of the playing surface is within the field of view of at least two cameras located on the opposite side of the playing surface. As a result, the logic of the object tracking systems discussed below will have at least two images containing the ball that are unaffected by the ball occlusion problem discussed above.
Before some particular embodiments are disclosed in greater detail, it should be understood that the particular embodiments disclosed herein do not limit the scope of the concepts provided herein. It should also be understood that a particular embodiment disclosed herein can have features that can be readily separated from the particular embodiment and optionally combined with or substituted for features of any of a number of other embodiments disclosed herein.
Regarding terms used herein, it should also be understood the terms are for the purpose of describing some particular embodiments, and the terms do not limit the scope of the concepts provided herein. Ordinal numbers (e.g., first, second, third, etc.) are generally used to distinguish or identify different features or steps in a group of features or steps, and do not supply a serial or numerical limitation. For example, “first,” “second,” and “third” features or steps need not necessarily appear in that order, and the particular embodiments including such features or steps need not necessarily be limited to the three features or steps. Labels such as “left,” “right,” “top,” “bottom,” “front,” “back,” and the like are used for convenience and are not intended to imply, for example, any particular fixed location, orientation, or direction. Instead, such labels are used to reflect, for example, relative location, orientation, or directions. Singular forms of “a,” “an,” and “the” include plural references unless the context clearly dictates otherwise.
In certain situations, the terms “logic” and “subsystem” are representative of hardware, firmware, and/or software that is configured to perform one or more functions. As hardware, the logic (or subsystem) may include circuitry having data processing and/or storage functionality. Examples of such circuitry may include, but are not limited or restricted to a processor, a programmable gate array, a microcontroller, an application specific integrated circuit, wireless receiver, transmitter and/or transceiver circuitry, semiconductor memory, or combinatorial logic.
Alternatively, or in combination with hardware circuitry, the logic (or subsystem) may be software in the form of one or more software modules. The software modules may include an executable application, a daemon application, an application programming interface (API), a subroutine, a function, a procedure, an applet, a servlet, a routine, source code, a shared library/dynamic load library, or even one or more instructions. The software module(s) may be stored in any type of a suitable non-transitory storage medium, or transitory storage medium (e.g., electrical, optical, acoustical or other form of propagated signals such as carrier waves, infrared signals, or digital signals). Examples of non-transitory storage medium may include, but are not limited or restricted to a programmable circuit; a semiconductor memory; non-persistent storage such as volatile memory (e.g., any type of random access memory “RAM”); persistent storage such as non-volatile memory (e.g., read-only memory “ROM”, power-backed RAM, flash memory, phase-change memory, etc.), a solid-state drive, hard disk drive, an optical disc drive, or a portable memory device. As firmware, the logic (or subsystem) may be stored in persistent storage.
The term “network device” should be generally construed as physical logic (electronics) or virtualized logic with data processing capability and/or a capability of connecting to any type of network, such as a public network (e.g., internet), a private network (e.g., any type of local area network), a public cloud network (e.g., Amazon Web Service (AWS®), Microsoft Azure®, Google Cloud®, etc.), or a private cloud network. Examples of a network device may include, but are not limited or restricted to, any of the following: a server; a mainframe; a firewall; a data transfer device (e.g., intermediary communication device, router, repeater, portable mobile hotspot, etc.); an endpoint device (e.g., a laptop, a smartphone, a tablet, a desktop computer, a netbook, gaming console, etc.); or a virtual device being software that supports data capture, preliminary analysis of meta-information associated with cybersecurity intelligence.
The term “message” generally refers to signaling (wired or wireless) as either information placed in a prescribed format and transmitted in accordance with a suitable delivery protocol or information made accessible through a logical data structure such as an API. Examples of the delivery protocol include, but are not limited or restricted to HTTP (Hypertext Transfer Protocol); HTTPS (HTTP Secure); Simple Mail Transfer Protocol (SMTP); File Transfer Protocol (FTP); iMESSAGE®, Instant Message Access Protocol (IMAP); or the like. Hence, each message may be in the form of one or more packets, frames, or any other series of bits having the prescribed, structured format.
The term “computerized” generally represents that any corresponding operations are conducted by hardware in combination with software and/or firmware.
The term “transmission medium” generally refers to a physical or logical communication link (or path) between two or more network devices. For instance, as a physical communication path, wired and/or wireless interconnects in the form of electrical wiring, optical fiber, cable, bus trace, or a wireless channel using infrared, radio frequency (RF), may be used.
In certain instances, the terms “compare,” comparing,” “comparison,” or other tenses thereof generally mean determining if a match (e.g., identical or a prescribed level of correlation) is achieved between two items where one of the items may include content within meta-information associated with the feature.
Finally, the terms “or” and “and/or” as used herein are to be interpreted as inclusive or meaning any one or any combination. As an example, “A, B or C” or “A, B and/or C” mean “any of the following: A; B; C; A and B; A and C; B and C; A, B and C.” An exception to this definition will occur only when a combination of elements, functions, steps or acts are in some way inherently mutually exclusive.
As this invention is susceptible to embodiments of many different forms, it is intended that the present disclosure is to be considered as an example of the principles of the invention and not intended to limit the invention to the specific embodiments shown and described.
Referring to
The studio environment includes a studio space 100 configured for a player 116 to receive a ball 114 from a ball launching machine 105 and return the ball 114 in the direction of the ball launching machine 105 at a screen 102 (or wall). It is noted that one or more players may participate; however, a single player is illustrated for the sake of clarity. In the illustrative embodiment shown, the studio environment comprises the trapezoidal-shaped studio space 100, where sides of the studio space 100 are labeled as A-D. A ball launching machine 105 and screen 102 are located at side A and an opening may be located at side B, which may allow the player to enter the playing space 100. In some embodiments, a wall having a door or entrance way may be comprise side B. In some embodiments, the wall of side B may be a mesh or netting. Further, a projector may be disposed at side B (i.e., affixed to an upper portion of a wall or the ceiling) and configured to project an image onto the screen 102. However, in other embodiments, the projector 112 may be located distal the screen 102 on side A relative to side B (e.g., located behind the screen 102 relative to the playing surface 110). Additionally, the projector 112 may project an image on any of the walls of the space 100. It should be understood that the projector 112 may be positioned elsewhere within the studio environment. Additionally, sides C-D further surround the studio space 100, where each of the sides C-D include half of the plurality of cameras utilized in tracking the ball 114.
As shown, six cameras form the plurality of cameras utilized in tracking the ball 114. As will be discussed below, embodiments of an object-tracking system include a plurality of cameras and a plurality of logic modules. In particular, the plurality of cameras of the object-tracking system are configured to capture images of a ball launched by a ball launching machine 105 and the accompanying logic may perform analyses of the captured images to track the ball 114 as it travels to the player 116 and is returned toward the screen 102 (e.g., as the player kicks the ball toward the screen). Although the exemplary embodiment of the figures herein illustrates that the plurality of cameras is comprised of six cameras, the disclosure is not limited to this number. The object-tracking system may include an alternative even number of cameras configured to capture images for object tracking, such as 2, 4, 8, 10, etc., such that half of the plurality is located on side C and the other half is located on side D with each half being mirrored in physical position and orientation to the other half. Additional cameras will be discussed below configured to capture images for replay generation and/or human pose estimation.
The logic of the object-tracking system (illustrated in
As one example, a player 114 may be participating in a virtual game comprising a virtual goalie and goal displayed on the screen 102 by the projector 112 such that the player 114 is to receive a ball 114 from the ball launching machine 105 and kick the ball 114 at the screen 102 attempting to place the ball 114 such that the ball 114 contacts the screen 102 in a position resulting in a “goal,” i.e., the ball is to contact the screen at a location within virtual goal posts displayed on the screen other than where the goalie is positioned. In such an embodiment, the plurality of cameras and logic of the object-tracking system may, collectively, capture a plurality of images of the playing surface 110 and analyze the captured images to identify the location of the ball 114 as it travels toward the player 116, as the player 116 interacts with the ball 114 and as the ball 114 travels away from the player 116 and toward the screen 102. The logic may further determine an expected contact point on the screen 102 (e.g., coordinates of the screen 102, or “screen coordinates”) and generate instructions causing the projector 112 to display a visual on the screen 102, e.g., providing a virtual display of a ball passing by the goalie or a ball being blocked by the goalie.
In further detail, the object-tracking system includes a specific configuration of the plurality of cameras to capture images of the playing surface 110 and screen 102 following the launch of a ball 114. The plurality of cameras is positioned in a mirrored configuration such that camera 1 and camera 2 are at mirrored positions relative to a center axis 130 (as seen in
Additionally, the cameras of the object-tracking system are time-synchronized such that each camera captures an image at the same time. As will be discussed, time-synchronization is integral in the configuration in order to enable the accompanying logic to triangulate the position of the ball 114 using an image pair (i.e., two images captured from two separate cameras at the same time).
Referring now to
Based on
a. System Calibration
Each camera of the object-tracking system is included in a calibration process involving both of an intrinsic and an extrinsic calibration. The intrinsic calibration enables logic of the object-tracking system to determine the distortion that occurs with each camera when dewarping an image captured by that camera. It should be understood that “dewarping” may also be referred to as flattening and/or undistorting. The extrinsic calibration enables the system logic to determine the relationship between each camera and every other camera. The extrinsic calibration includes determining how a flat plane of an image captured by a first camera relates to a flat plane of an image captured by a second camera. Further, the calibration process may include determination of a set of transformation matrices, where a transformation matrix is generated for each camera pair, where a transformation matrix corresponds to the transformation of a 3D point in camera coordinates to world reference coordinates. In one embodiment, the transformation matrices are in turn used to calculate the Fundamental matrices and the origin transform, where the origin point is assumed to be the top intersecting corner of the screen or wall 102 on side A with side C.
Additionally, for each camera pair, a 2D grid of points mapping the overlapping views of each camera of the pair to each other. Additional detail regarding the calibration process is discussed with respect to
Referring to
The logic of the object-tracking system 200 may comprise several logic modules including a calibration logic 202, a time synchronization logic 204, an image acquisition logic 206, a screen display logic 208, a triangulation logic 212, a region-of-interest (ROI) detection logic 210, a coordinate determination logic 214 and a player profile logic 219. The object-tracking system 200 may further include an image acquisition repository 216 and a calibration data repository 218.
Generally, the calibration logic 202, when executed by the one or more processors 203, performs operations of the intrinsic and extrinsic calibration processes referenced above and discussed further with respect to
The image acquisition logic 206, when executed by the one or more processors 203, performs operations to obtain images captured by the cameras. Such operations may include retrieving, i.e., querying or downloading, the captured images from a ring buffer of each camera. In some instances, the image acquisition logic 206 retrieves the captured images at a rate equal to the frame rate of the cameras. In some instances, the cameras of the object-tracking system 200 are configured to capture images at a frame rate within the range of 80-100 frames/second. The retrieved images may be stored in the image acquisition repository 216. In some embodiments, the captured images have an aspect ratio of 1920×1080 pixels.
The screen display logic 208, when executed by the one or more processors 203, performs operations configured to generate instructions to cause a graphic to be displayed by the projector 112 onto the screen 102. In addition, the instructions may cause an alteration of the graphic currently displayed.
The ROI detection logic 210, when executed by the one or more processors 203, performs operations that detect particular regions of interest within the captured images. Such operations may include determination of a subsection of each captured image to analyze in attempting to detect a ball, a player and/or other objects, such as bottles, glasses, shoes, pets, etc. (and/or a player). For instance, the ROI detection logic 210 may initially utilize the known locations of each camera of the object-tracking system 200 and of the ball launching machine 105 as well as the known launch speed and launch orientation of a ball to determine a subsection (“the ROI”) of each captured image to analyze when attempting to find the ball following its launch. Following the initial detection of the ball, the ROI detection logic 210 may utilize previously analyzed images and the known launch speed and launch orientation to detect a subsection (the ROI) to analyze when attempting to track the ball. In some embodiments, the size of the ROI may range from substantially 100×100 pixels to 400×400 pixels. In some embodiments, the size of the ROI to be determined may be configurable prior to runtime. It should also be noted that the ROI need not be a square but may take other dimensions.
The object recognition logic 211, when executed by the one or more processors, performs image analysis operations to analyze captured images and perform one or more of image classification, object localization, object detection and/or object segmentation (“object recognition”). Various methods may be utilized to perform the object recognition including, for example, convoluted neural networks or other trained machine learning models.
The triangulation logic 212, when executed by the one or more processors, performs triangulation operations using two captured images (captured at the same time) that determine the location of the ball and/or player(s) within the studio space. The triangulated location information may be provided to the ROI detection logic 210 for use in determining the subsection of subsequent images for analysis.
Together, the analyses and processing of the captured images of by the object recognition logic 211 and the triangulation logic 212 generate object-tracking data (or, with reference to the embodiments illustrated herein, “ball-tracking data”). The object-tracking data refers to data indicating one or more of the following: a location of a detected object within a plurality of captured images, a label of the detected object (i.e., identifying or classifying the object), a bounding box of the object and the object's location within the studio space at multiple times. For instance, the object-tracking data may include a listing of the object's location within the studio space at every 10 milliseconds subsequent to the launch of the object. However, other timing periods may be used, and the disclosure is not intended to be limited to 10 millisecond increments.
The coordinate determination logic 214, when executed by the one or more processors 203, performs operations that include execution of a ballistic trajectory equation based on the data obtained from tracking the ball (i.e., continued determination of its triangulated location as the ball travels toward the player and is then returned toward the screen 102). The ballistic trajectory equation results in a determination of a set of coordinates indicating a point on the screen 102 that the ball is expected to contact. The determined coordinates may be provided to the screen display logic 208 for generation of instructions to cause a graphic to be displayed on the screen 102, for example, at the determined coordinates.
In some embodiments, each launch of a ball may be associated with a particular player profile or with a session where the session is associated with a particular player profile. For instance, prior in initiating a session in which one or more balls are launched from a ball machine, the player may provide player profile credentials (e.g., via a network device) that are received by player profile logic 219. The player profile logic 219 may, when executed by the one or more processors 203, perform operations to associate all data retrieved with a particular session and processing performed thereon with a player profile corresponding to the received credentials. For example, generated replays, determined metrics, one or more captured images, etc., may be associated with the player's player profile and stored in the profile repository 220. As used herein, the term “session” may refer to one or more balls launched by the ball launching machine, where each ball launched is associated with a particular instruction received by the ball launching machine. For example, a session refers to the launching of a series of balls that a player is to receive and return toward the screen 102 (e.g., via a kick or motion with one's head). The session may be initiated by receipt of an instruction by the ball launching machine 205, where the instruction details one or more of a number of balls to launch, launch parameters for one or more balls and a timing between each launch. Additionally, other embodiments include instructions that launch balls in response to the player and ball interactions and/or where the ball contacts the screen 102 (e.g., end the session after a threshold number of “goals” based on where a number of balls contacts the screen 102).
a. Calibration
Referring to
Herein, the method 300 starts with performance of an intrinsic calibration on each camera of the plurality to determine the distortion that occurs when dewarping an image captured by the camera (block 302). With reference to
The method 300 continues with performance of an extrinsic calibration on each camera pair of the plurality to determine how a flat plane of each camera relates to a flat plane of every other camera (block 306). With reference to
The method 300 further includes operations directed at determining a transformation matrix between each camera pair. Specifically, the method 300 continues by capturing an image of a portion of the predetermined space that includes one or more markers (block 310). It should be understood that, in some embodiments, the images captured in the operations discussed above may be utilized in place of the operation of capturing additional images. Subsequently, for each camera pair, the method 300 includes the determination of a transformation matrix that corresponds to the transformation of a three-dimensional (3D) point in camera coordinates to world reference coordinates (block 312). Following performance of the transformation matrices determinations, the transformation matrices are stored, for example in the calibration data repository 218 (block 314).
Further, for each camera pair, the method 300 involves the generation of a two-dimensional (2D) grid of points that maps overlapping views of each camera within the camera pair (block 316). Finally, the method 300 ends with following the storage of each 2D grid, for example in the calibration data repository 218 (block 318). As will be discussed below, for example with respect to
b. Object Tracking
Referring now to
The assumptions that were discussed with respect to
The method 400 begins as each of the time-synchronized plurality of cameras captures images at a predetermined frame rate (block 402). System logic, e.g., the image acquisition logic 206, when executed by the one or more processors, performs operations to obtain images captured by the cameras, e.g., querying, downloading or receiving, the captured images from a ring buffer of each camera (block 404). In some instances, the image acquisition logic retrieves the captured images at a rate equal to the frame rate of the camera. In some instances, the cameras of the object-tracking system are configured to capture images at a frame rate within the range of 80-100 frames/second. The retrieved images may be stored in the image acquisition repository 216.
Based on knowledge of the disposition (e.g., physical placement and orientation) of each of the plurality of the cameras of the object-tracking system and knowledge of the ball launching machine 105 (including launch parameters of a launched ball), system logic, e.g., the ROI detection logic 210, determines a portion of each image having the highest probability of containing the launched ball (block 406). More specifically, based on the known launch parameters of a ball, such as angle, orientation and speed, the ROI detection logic 210 estimates a location of the ball within the studio space, wherein the estimated location corresponds to a position within captured images by two or more cameras at a given time. Thus, the ROI detection logic 210 determines a region of interest being a portion of the captured images having the highest probability of containing the ball.
Following the determination of the region of interest for a set of images, system logic, e.g., object recognition logic 211, performs operations to analyze the region of interest of the images in order to detect and identify a ball. Once the ball is detected and identified, system logic, e.g., triangulation logic 212, performs a triangulation process to determine a location of the ball in 3D space using two captured images in which the ball was identified (block 408). The object recognition data and the triangulated location of the ball along with the captured images and a corresponding timestamp (collectively “ball-tracking data”) may be stored in, for example, the image acquisition repository 216.
Upon determination of a triangulated location of the ball, the ROI detection logic 210 in combination with the triangulation logic 212 determines a subsection of subsequent images having the highest probability of containing the ball (block 410). In some embodiments, following the determination of a triangulated location of the ball in multiple (e.g., three) pairs of captured images, the ROI detection logic 210 utilizes the triangulated locations to estimate a subsection of a subsequently captured image having the highest probability of containing the ball. In such embodiments, prior to the determination of the triangulated location of the ball in multiple captured images, the ROI detection logic 210 continues determination of the subsection of each captured image having the highest probability of containing the ball using the launch parameters and known configuration of the cameras.
Further in some embodiments when the set of captured images for a given time does not contain the ball (or the ball otherwise goes unidentified), the ROI detection logic 210 may revert to using the launch parameters of the ball to estimate the subsection of subsequent captured images having the highest probability of containing the ball (until a triangulated location of the ball is identified for a predetermined number of captured images, e.g., three).
Referring now to
The camera pair that captured the two selected images is identified such that subsequent images captured by the camera pair will be utilized in continued tracking of the ball. Specifically, the method 400 continues to track the ball as the ball travels back toward the screen (wall, etc.), such as the screen 102 of
In embodiments in which an object-tracking system is applied to soccer (“football” in the UK), such as illustrated in
As is discussed herein, the entire sequence of the ball traveling toward the player, the player receiving and interacting with the ball, and the ball returning toward the screen is captured by the plurality of cameras positioned about the studio space. Further, system logic determines a location of the ball (and optionally the player) within 3D space of the playing surface 110 of
As the ball is continually tracked as discussed above, the system logic, e.g., the triangulation logic 212, determines when the ball is within a predetermined distance from the screen 102. In such an instance, the coordinate determination logic 216 performs processing on the triangulated location using a ballistic trajectory equation to determine coordinates of the screen 102 that the ball is expected to hit (block 418). In some embodiments, the coordinate determination logic 216 is initiated when the triangulation logic 212 determines that the ball is 75 cm away from the screen 102. In other embodiments, the coordinate determination logic 216 is initiated when the triangulation logic 212 determines that the ball is 60 cm away from the screen 102. However, the distance of the ball away from the screen at which the coordinate determination logic 216 is activated is configurable prior to runtime.
In addition to the configuration of the plurality of cameras utilized in tracking the ball, the lighting equipment of the studio space 100 is specifically configured to provide sufficient light to the playing surface 110 (e.g., approximately 350-400 lux) while also providing a dark surface at least on the screen 102 to increase the visibility of the projected or displayed image thereon (e.g., approximately 5-8 lux). As should be understood, images captured by the plurality of cameras (cameras 1-8, where cameras 7-8 are discussed below) of well-lit areas (e.g., 350-400 lux) are better suited for analysis by the logic of the object tracking system 200 when identifying the ball, player and/or other object. However, in contrast, the projection or display of the visual image on at least the screen 102 appears best in poorly lit areas (e.g., 0-8 lux). Thus, the lighting equipment of the studio space 100 (not shown) is specifically configured to provide a dimly lit area proximate the screen 102 (e.g., approximately 60-75 cm in front of the screen 102 of approximately 5-8 lux) and a well-lit area for the playing surface 110 (e.g., approximately 350-400 lux).
Still referring to
As non-limiting examples, the visualization may include a ball being shot passed a goalie indicating a goal was scored by the player or a ball being stopped by the goalie. However, as noted above, the visualizations provided need not correspond directly to a representation of a sporting event but may instead include fanciful or imaginative gameplay such as a ball extending into the screen to break up a meteor approaching the screen or knock over a zombie displayed on the screen. The gameplay illustrated on the screen may take on any embodiment.
c. Auxiliary Systems
In addition to the object-tracking as discussed above, the logic of the object-tracking system 200 may further analyze the captured images to detect objects such as a player 116 in a proximal portion of the playing surface 110 relative to the screen 102, multiple balls on the playing surface 110 or in a gutter 106, additional players on the playing surface 110, and/or particular body positions of the player 116, as will be discussed below. As used herein, the term “proximal portion” is intended to mean a portion of the playing surface 110 relative to a particular point, e.g., the proximal portion of the playing surface 110 relative to the screen 102 is intended to mean the portion is the portion of the playing surface 110 that is near the screen 102. In contrast, the term “distal portion” is intended to mean a portion of the playing surface 110 that is away from a relative point (i.e., further from the relative point than the proximal portion).
In some embodiments, when a player is detected in a proximal portion of the playing surface 110 relative to the ball launching machine 205, the object recognition logic 211 may transit an instruction to the ball launching machine 205 to pause or stop the current session. Other warnings may be provided as well such as an audible or visual queue instructing the player 116 to move further back relative to the screen 102 (such may be provided to a central control center so that an administrator or supervisor may also pause or cancel the session). As is shown in
In some embodiments, when multiple balls on the playing surface 110 or in a gutter 106, the object recognition logic 211 may transit an instruction to the ball launching machine 205 to pause or stop the current session. For example, the object recognition logic 211 may detect a plurality of balls on the playing surface due to mishits by the player 116, or otherwise, such that the balls have not gone into gutter 106 for collection and placement within a queue or hopper to be launched. In some embodiments, when a predetermined number of balls is detected on the playing surface 110, e.g., five (5), the object recognition logic 211 may transit an instruction to the ball launching machine 205 to pause or stop the current session. Additionally, warnings, either audible or visual, may be generated that instruct the player 116 to gather the balls and place them in the gutter 106. In some embodiments, when multiple players on the playing surface 110, the object recognition logic 211 may transit an instruction to the ball launching machine 205 to pause or stop the current session; however, in some embodiments, multiple players are expected to be on the playing surface 110.
Further, particular body positions of the player 116 may be detected by logic, such as the human pose estimation logic 604, described below. In some embodiments, detection of certain body positions may trigger or initiate operations such as the transmission of an instruction to the ball launching machine 205 to pause or cancel the session or initiation of a process to generate a replay video by the replay generation logic 602, described below.
With respect to detection of objects within the gutter 106, specific operations are performed given the amount of light provided to the area directly in front of the screen 102, where the gutter 106 is located (see
Referring now to
The 2-camera replay system includes a first camera, camera 7, that is positioned above the screen (and typically above the center point) with a field of view facing toward the player (e.g., toward the second end). The 2-camera replay system additionally includes a second camera, camera 8, that is positioned above the playing surface of the studio (and typically above a position at which the player stands) with a field of view facing toward the screen (e.g., toward the first end). The camera 7 captures images of the player at, for example, a frame rate of 30 frames/second with each image having a high resolution (e.g., 5 MP). The camera 8 also captures images at a frame rate of 30 frames/second with each image having an identical resolution as camera 7. The camera 8 is positioned to capture images of the screen.
Referring to
Processing of the replay generation logic 602 may triggered in various manners, which may include, for example via manual input from a bystander, automatically in response to a goal scored and/or in response to detection of certain poses of the player. As will be discussed below, the replay generation logic 602 may receive data from the human pose estimation logic 604 indicating a particular pose of the player (e.g., hands extending above his/her head indicating a celebration). Specifically, the replay generation logic 602, when executed by the one or more processors 203, performs operations to obtain a series of images captured by the cameras 7-8, determine a location of the ball within the studio space through processing the series of images as discussed above with respect to
The human pose estimation logic 604, when executed by one or more of the processors 203, performs operations to obtain images captured by cameras 1-8, obtain ball-tracking data as generated by the triangulation logic 212 and/or the ROI detection logic 210 indicating a location of the ball and a player, when applicable, within the images captured by the cameras 1-6, segment the player and the ball in the images captured by the cameras 1-6 to generate a bounding box around the player, utilize epipolar geometry to project the bounding box onto a set of images captured by one or more of cameras 7-8, perform a human pose estimation on the images captured by the cameras 7-8 to identify points of the player's body, determine player-ball interaction statistics (such as a touch sequence and/or dwell time) and optionally provide a human pose estimation to the replay generation logic 602.
Referring to
The assumptions that were discussed with respect to
Based on the location of the ball within the studio space, a determination is made as to whether the ball is located proximate a threshold line relative to the ball launching machine 105 (or screen 102) (block 706). When the ball is located proximate the threshold line (yes at block 706), the method 700 includes an operation of selecting a series of images captured by camera 8 (block 708). When the ball is not located proximate the threshold line (no at block 706), the method 700 includes an operation of selecting a series of images captured by camera 7 (block 710). Following selection of a series of images, the method 700 includes an operation of generating a replay video using the selected series of images (block 712). The replay video may be stored be stored in the profile repository 220 in association with the player's profile.
In certain embodiments, the generation of a replay video may be triggered based on particular situations within the session such as a particular number of goals scored (e.g., where a threshold number of goals are scored and the session ends, where a replay video is generated on the final goal scored). Various other configurable scenarios have been contemplated to trigger generation of a reply and are within the scope of this disclosure including, but not limited or restricted to, detection of a particular pose by the player (using the human pose estimation logic 604), detection of a particular touch sequence, etc.
Referring now to
The assumptions that were discussed with respect to
Further, the method 800 may include an operation, performed by the human pose estimation logic 604, when executed by one or more of processors, of obtaining ball-tracking data as generated by the triangulation logic 212 and/or the ROI detection logic 210, where the ball-tracking data indicates a location of the ball and a player, when applicable, within the images captured by the cameras 1-6 (block 804). Based on the ball-tracking data, the human pose estimation logic 604 segments the ball from the player to identify the player and generate a bounding box around the player. The segmentation of the ball and player may be performed in the same manner as discussed above with respect to
Based on the ball-tracking data and the bounding box, the human pose estimation logic 604, when executed by one or more of processors, utilizes epipolar geometry to project the bounding box around the player onto each image of the set of images captured by at least one of cameras 7-8 (block 806). The human pose estimation logic 604 is able to project to the bounding box generate from images of the cameras 1-6 onto images of the cameras 7-8 as each of the cameras 1-8 are included in the calibration process discussed above. Specifically, the calibration process of
Utilizing the bounding boxes projected onto the images captured by the cameras 7-8, the human pose estimation logic 604, when executed by one or more of processors, performs operations comprising a human pose estimation to identify points of the player's body (e.g., hand, elbow, shoulder, head, torso, knee, foot, etc.) (block 808). Following identification of points of the player's body, the human pose estimation logic 604, when executed by one or more of processors, performs operations to identify the player's location in the studio from the ball-tracking data obtained from the triangulation logic 212 and/or the ROI detection logic 210 (block 810).
Further, the human pose estimation logic 604, when executed by one or more of processors, analyzes the images captured by one or more of the cameras 1-8 along with the identified points of the player's body to determine player-ball interaction statistics (block 812). In some preferred embodiments, the human pose estimation logic 604 analyzes the images captured by one or more of the cameras 1-7. Some examples of the player-ball interaction statistics may include, but are not limited or restricted to, a touch sequence of the ball by the player (“touch sequence”) and dwell time. A touch sequence may refer to a number of touches of the ball by the player and/or an indication of which points of the player's body touched the ball. Dwell time may refer to the duration of the time from receipt of the ball (e.g., a player's first touch) to release of the ball (e.g., a player's last touch). The player-ball interaction statistics may be stored in, for example, the profile repository 220, in association with a specific player.
Optionally, not shown, the human pose estimation logic 604 may, when executed by one or more of processors, determine an estimated human pose based on, for example, comparison or correlation against known human poses, and provide an indication of the estimated human pose to the replay generation logic 602, which may trigger initiation of operations to generate a replay video.
While some particular embodiments have been disclosed herein, and while the particular embodiments have been disclosed in some detail, it is not the intention for the particular embodiments to limit the scope of the concepts provided herein. Additional adaptations and/or modifications can appear to those of ordinary skill in the art, and, in broader aspects, these adaptations and/or modifications are encompassed as well. Accordingly, departures may be made from the particular embodiments disclosed herein without departing from the scope of the concepts provided herein.
This application is a continuation of U.S. patent application Ser. No. 16/993,030, filed Aug. 13, 2020, which issued as U.S. Pat. No. 11,514,590, the entire contents of which is incorporated by reference herein.
| Number | Name | Date | Kind |
|---|---|---|---|
| 2440274 | Ibisch | Apr 1948 | A |
| 3913552 | Yarur et al. | Oct 1975 | A |
| 3918711 | Zak | Nov 1975 | A |
| 3989246 | Brown et al. | Nov 1976 | A |
| 4025071 | Hodges | May 1977 | A |
| 4029315 | Bon | Jun 1977 | A |
| 4150825 | Wilson | Apr 1979 | A |
| 4442823 | Floyd et al. | Apr 1984 | A |
| 4535992 | Slagle | Aug 1985 | A |
| 4645458 | Williams | Feb 1987 | A |
| 4726616 | Schmidt | Feb 1988 | A |
| 4751642 | Silva et al. | Jun 1988 | A |
| 4882676 | Van De Kop et al. | Nov 1989 | A |
| 4915384 | Bear | Apr 1990 | A |
| 4919428 | Perkins | Apr 1990 | A |
| 5107820 | Salansky | Apr 1992 | A |
| 5125653 | Kovacs et al. | Jun 1992 | A |
| 5188367 | Gipe et al. | Feb 1993 | A |
| 5264765 | Pecorino et al. | Nov 1993 | A |
| 5342041 | Agulnek et al. | Aug 1994 | A |
| 5344137 | Komori | Sep 1994 | A |
| 5359986 | Magrath, III et al. | Nov 1994 | A |
| 5361455 | Kiefer | Nov 1994 | A |
| 5365427 | Soignet et al. | Nov 1994 | A |
| 5438518 | Bianco et al. | Aug 1995 | A |
| 5447314 | Yamazaki et al. | Sep 1995 | A |
| 5464208 | Pierce | Nov 1995 | A |
| 5465978 | Magnone et al. | Nov 1995 | A |
| 5489099 | Rankin et al. | Feb 1996 | A |
| 5490493 | Salansky | Feb 1996 | A |
| 5498000 | Cuneo | Mar 1996 | A |
| 5529205 | Corney et al. | Jun 1996 | A |
| 5556106 | Jurcisin | Sep 1996 | A |
| 5649523 | Scott | Jul 1997 | A |
| 5683302 | Harrell et al. | Nov 1997 | A |
| 5697791 | Nashner et al. | Dec 1997 | A |
| 5722384 | Cox | Mar 1998 | A |
| 5768151 | Lowy et al. | Jun 1998 | A |
| 5860873 | Karasavas | Jan 1999 | A |
| 5868578 | Baum | Feb 1999 | A |
| 5873797 | Garn | Feb 1999 | A |
| 5882204 | Iannazo et al. | Mar 1999 | A |
| 5897445 | Sanders | Apr 1999 | A |
| 5911214 | Andrews | Jun 1999 | A |
| 5938545 | Cooper et al. | Aug 1999 | A |
| 6042492 | Baum | Mar 2000 | A |
| 6073489 | French et al. | Jun 2000 | A |
| 6082350 | Crews et al. | Jul 2000 | A |
| 6098458 | French et al. | Aug 2000 | A |
| 6179720 | Rankin et al. | Jan 2001 | B1 |
| 6182649 | Battersby et al. | Feb 2001 | B1 |
| 6190271 | Rappaport et al. | Feb 2001 | B1 |
| 6237583 | Ripley et al. | May 2001 | B1 |
| 6263279 | Bianco et al. | Jul 2001 | B1 |
| 6308565 | French et al. | Oct 2001 | B1 |
| 6320173 | Vock et al. | Nov 2001 | B1 |
| 6533675 | Funk | Mar 2003 | B2 |
| 6539931 | Trajkovic et al. | Apr 2003 | B2 |
| 6565448 | Cameron et al. | May 2003 | B2 |
| 6707487 | Aman et al. | Mar 2004 | B1 |
| 6774349 | Vock et al. | Aug 2004 | B2 |
| 6816185 | Harmath | Nov 2004 | B2 |
| 7040998 | Jolliffe et al. | May 2006 | B2 |
| 7082938 | Wilmot | Aug 2006 | B2 |
| 7100791 | Berger | Sep 2006 | B2 |
| 7335116 | Petrov | Feb 2008 | B2 |
| 7559163 | Ofuji et al. | Jul 2009 | B2 |
| 7610909 | Greene, Jr. | Nov 2009 | B2 |
| 7815525 | Small | Oct 2010 | B2 |
| 7850536 | Fitzgerald | Dec 2010 | B1 |
| 7882831 | Alger | Feb 2011 | B2 |
| 7920052 | Costabile | Apr 2011 | B2 |
| 8142267 | Adams | Mar 2012 | B2 |
| 8164830 | Astill | Apr 2012 | B2 |
| 8210959 | Balardeta et al. | Jul 2012 | B2 |
| 8292733 | Crawford et al. | Oct 2012 | B2 |
| 8444499 | Balardeta et al. | May 2013 | B2 |
| 8597142 | Mayles et al. | Dec 2013 | B2 |
| 8617008 | Marty et al. | Dec 2013 | B2 |
| 8705799 | White et al. | Apr 2014 | B2 |
| 8840483 | Steusloff et al. | Sep 2014 | B1 |
| 8893698 | Boehner | Nov 2014 | B2 |
| 8992346 | Raposo | Mar 2015 | B1 |
| 9010309 | Lewis et al. | Apr 2015 | B2 |
| 9017188 | Joseph et al. | Apr 2015 | B2 |
| 9050519 | Ehlers et al. | Jun 2015 | B1 |
| 9162134 | Schwartz | Oct 2015 | B2 |
| 9216330 | Beck et al. | Dec 2015 | B2 |
| 9233292 | Joseph et al. | Jan 2016 | B2 |
| 9469945 | Khurgin | Oct 2016 | B2 |
| 9586099 | Holthouse | Mar 2017 | B2 |
| 9616346 | Nicora et al. | Apr 2017 | B2 |
| 9625321 | Cavallaro et al. | Apr 2017 | B2 |
| 9724584 | Campbell et al. | Aug 2017 | B1 |
| 9782648 | DeCarlo | Oct 2017 | B2 |
| 9901776 | Mettler | Feb 2018 | B2 |
| 9901804 | Vollbrecht et al. | Feb 2018 | B2 |
| 9968837 | Johnston | May 2018 | B2 |
| 9999823 | Chen et al. | Jun 2018 | B2 |
| 10092793 | Marty et al. | Oct 2018 | B1 |
| 10300361 | Khazanov et al. | May 2019 | B2 |
| 10360685 | Marty et al. | Jul 2019 | B2 |
| 10380409 | Thornbrue et al. | Aug 2019 | B2 |
| 10398957 | Altshuler et al. | Sep 2019 | B2 |
| 10456645 | Joo et al. | Oct 2019 | B2 |
| 10486024 | Joo et al. | Nov 2019 | B2 |
| 10486043 | Joo et al. | Nov 2019 | B2 |
| 10489656 | Lee et al. | Nov 2019 | B2 |
| 10600334 | Zhang et al. | Mar 2020 | B1 |
| 10653936 | Ganzer | May 2020 | B2 |
| 10695637 | Hennessy et al. | Jun 2020 | B2 |
| 10974121 | Thornbrue et al. | Apr 2021 | B2 |
| 11207582 | Lewis et al. | Dec 2021 | B2 |
| 11514590 | Spiteri | Nov 2022 | B2 |
| 20020148455 | Trajkovic et al. | Oct 2002 | A1 |
| 20030008731 | Anderson et al. | Jan 2003 | A1 |
| 20030092497 | Holcomb | May 2003 | A1 |
| 20030109322 | Funk et al. | Jun 2003 | A1 |
| 20030142210 | Carlbom et al. | Jul 2003 | A1 |
| 20030195052 | Cohen et al. | Oct 2003 | A1 |
| 20040058749 | Pirritano et al. | Mar 2004 | A1 |
| 20040061324 | Howard | Apr 2004 | A1 |
| 20040063521 | Oister et al. | Apr 2004 | A1 |
| 20040171388 | Couronne et al. | Sep 2004 | A1 |
| 20040185952 | Marshall | Sep 2004 | A1 |
| 20050143199 | Saroyan | Jun 2005 | A1 |
| 20050197198 | Otten et al. | Sep 2005 | A1 |
| 20050227792 | McCreary et al. | Oct 2005 | A1 |
| 20050272517 | Funk et al. | Dec 2005 | A1 |
| 20050288119 | Wang et al. | Dec 2005 | A1 |
| 20060063574 | Richardson et al. | Mar 2006 | A1 |
| 20060103086 | Niemeyer et al. | May 2006 | A1 |
| 20060118096 | Cucjen et al. | Jun 2006 | A1 |
| 20060236993 | Cucjen et al. | Oct 2006 | A1 |
| 20060247070 | Funk et al. | Nov 2006 | A1 |
| 20060281061 | Hightower et al. | Dec 2006 | A1 |
| 20070021226 | Tyroler | Jan 2007 | A1 |
| 20070021242 | Krickler | Jan 2007 | A1 |
| 20070238539 | Dawe et al. | Oct 2007 | A1 |
| 20080146365 | Miesak | Jun 2008 | A1 |
| 20080192116 | Tamir et al. | Aug 2008 | A1 |
| 20080237251 | Barber | Oct 2008 | A1 |
| 20080287207 | Manwaring | Nov 2008 | A1 |
| 20080300071 | Valaika | Dec 2008 | A1 |
| 20080312010 | Marty et al. | Dec 2008 | A1 |
| 20090048039 | Holthouse et al. | Feb 2009 | A1 |
| 20090074246 | Distante et al. | Mar 2009 | A1 |
| 20090127809 | Meers | May 2009 | A1 |
| 20090210078 | Crowley | Aug 2009 | A1 |
| 20100032904 | Yasuoka et al. | Feb 2010 | A1 |
| 20100041498 | Adams | Feb 2010 | A1 |
| 20100090428 | Meers et al. | Apr 2010 | A1 |
| 20100137079 | Burke et al. | Jun 2010 | A1 |
| 20100148445 | Wilkins | Jun 2010 | A1 |
| 20100151955 | Holden | Jun 2010 | A1 |
| 20100184534 | Chan et al. | Jul 2010 | A1 |
| 20100210377 | Lock | Aug 2010 | A1 |
| 20100261557 | Joseph et al. | Oct 2010 | A1 |
| 20110028230 | Balardeta et al. | Feb 2011 | A1 |
| 20110143848 | Balardeta et al. | Jun 2011 | A1 |
| 20110143849 | Balardeta et al. | Jun 2011 | A1 |
| 20110151986 | Denton et al. | Jun 2011 | A1 |
| 20110224025 | Balardeta et al. | Sep 2011 | A1 |
| 20110304497 | Molyneux et al. | Dec 2011 | A1 |
| 20120015753 | Denton et al. | Jan 2012 | A1 |
| 20120015754 | Balardeta et al. | Jan 2012 | A1 |
| 20120029666 | Crowley et al. | Feb 2012 | A1 |
| 20120157200 | Scavezze et al. | Jun 2012 | A1 |
| 20120172148 | Freeman | Jul 2012 | A1 |
| 20120238381 | Denton et al. | Sep 2012 | A1 |
| 20120303207 | Reindl | Nov 2012 | A1 |
| 20120309554 | Gibbs et al. | Dec 2012 | A1 |
| 20120322568 | Lindeman | Dec 2012 | A1 |
| 20130005512 | Joseph et al. | Jan 2013 | A1 |
| 20130018494 | Amini | Jan 2013 | A1 |
| 20130095961 | Marty et al. | Apr 2013 | A1 |
| 20130104869 | Lewis et al. | May 2013 | A1 |
| 20130157786 | Joseph et al. | Jun 2013 | A1 |
| 20130210563 | Hollinger | Aug 2013 | A1 |
| 20130225305 | Yang et al. | Aug 2013 | A1 |
| 20130271458 | Andriluka et al. | Oct 2013 | A1 |
| 20130317634 | French et al. | Nov 2013 | A1 |
| 20130324310 | Leech et al. | Dec 2013 | A1 |
| 20140003666 | Park et al. | Jan 2014 | A1 |
| 20140128171 | Anderson | May 2014 | A1 |
| 20140330411 | Lochmann | Nov 2014 | A1 |
| 20150116501 | McCoy et al. | Apr 2015 | A1 |
| 20150202508 | Wise, Jr. | Jul 2015 | A1 |
| 20150292261 | Chou | Oct 2015 | A1 |
| 20160008662 | Cronin et al. | Jan 2016 | A1 |
| 20160023042 | Cherry | Jan 2016 | A1 |
| 20160023083 | Tawwater et al. | Jan 2016 | A1 |
| 20160074735 | Dawe et al. | Mar 2016 | A1 |
| 20160158626 | Dolige et al. | Jun 2016 | A1 |
| 20160193500 | Webster et al. | Jul 2016 | A1 |
| 20170021259 | Dismuke | Jan 2017 | A1 |
| 20170120132 | Shin et al. | May 2017 | A1 |
| 20170157484 | Altshuler et al. | Jun 2017 | A1 |
| 20170182361 | Tuxen et al. | Jun 2017 | A1 |
| 20170189753 | Polifka | Jul 2017 | A1 |
| 20170203182 | Spelman et al. | Jul 2017 | A1 |
| 20170259144 | Eddie | Sep 2017 | A1 |
| 20170259145 | Kline | Sep 2017 | A1 |
| 20170274262 | Sanchez et al. | Sep 2017 | A1 |
| 20170291093 | Janssen | Oct 2017 | A1 |
| 20170304705 | Hermandorfer | Oct 2017 | A1 |
| 20170319930 | Lewis et al. | Nov 2017 | A1 |
| 20170333777 | Spivak et al. | Nov 2017 | A1 |
| 20170340943 | Pierotti et al. | Nov 2017 | A1 |
| 20180036590 | DeAngelis et al. | Feb 2018 | A1 |
| 20180036616 | McKenney | Feb 2018 | A1 |
| 20180056124 | Marty et al. | Mar 2018 | A1 |
| 20180071577 | Swartz et al. | Mar 2018 | A1 |
| 20180137363 | Campagnoli et al. | May 2018 | A1 |
| 20180140917 | Song et al. | May 2018 | A1 |
| 20180189971 | Hildreth | Jul 2018 | A1 |
| 20180290019 | Rahimi et al. | Oct 2018 | A1 |
| 20180301169 | Ricciardi | Oct 2018 | A1 |
| 20180318715 | Dawe et al. | Nov 2018 | A1 |
| 20190087661 | Lee et al. | Mar 2019 | A1 |
| 20200298087 | Hermandorfer et al. | Sep 2020 | A1 |
| 20210146218 | Lewis et al. | May 2021 | A1 |
| 20210279896 | Tong et al. | Sep 2021 | A1 |
| 20210350566 | Hu | Nov 2021 | A1 |
| 20220051419 | Spiteri | Feb 2022 | A1 |
| 20220391620 | Spiteri | Dec 2022 | A1 |
| Number | Date | Country |
|---|---|---|
| 2005248763 | Jun 2010 | AU |
| 2476010 | Jan 2005 | CA |
| 2931744 | Dec 2014 | CA |
| 2892188 | Apr 2007 | CN |
| 1824352 | Apr 2010 | CN |
| 102389634 | Mar 2012 | CN |
| 202223857 | May 2012 | CN |
| 103706088 | Apr 2014 | CN |
| 205964896 | Feb 2017 | CN |
| 104504694 | Jul 2017 | CN |
| 19938761 | Feb 2001 | DE |
| 102015225776 | Jun 2017 | DE |
| 1477825 | Nov 2004 | EP |
| 1897599 | Mar 2008 | EP |
| 1913981 | Apr 2008 | EP |
| 2227299 | Sep 2010 | EP |
| 2218483 | Mar 2017 | EP |
| 3188810 | Jul 2017 | EP |
| 3242728 | Nov 2017 | EP |
| 2196859 | May 1991 | GB |
| 2337385 | Nov 1999 | GB |
| 2442070 | Mar 2008 | GB |
| 2487047 | Jul 2012 | GB |
| 2487209 | Jul 2012 | GB |
| 2505417 | Mar 2014 | GB |
| 2539837 | Dec 2016 | GB |
| 2544561 | May 2017 | GB |
| 2560032 | Aug 2018 | GB |
| 2010112956 | May 2010 | JP |
| 101579382 | Dec 2015 | KR |
| 20160124254 | Oct 2016 | KR |
| 20170104700 | Sep 2017 | KR |
| 101799650 | Nov 2017 | KR |
| M353032 | Mar 2009 | TW |
| M551080 | Nov 2017 | TW |
| 9521661 | Aug 1995 | WO |
| 2003032006 | Apr 2003 | WO |
| 2006126976 | Nov 2006 | WO |
| 2007037705 | Apr 2007 | WO |
| 2009138929 | Nov 2009 | WO |
| 2010102037 | Sep 2010 | WO |
| 2011106888 | Sep 2011 | WO |
| 2012161768 | Nov 2012 | WO |
| 2014021549 | Feb 2014 | WO |
| 2015112646 | Jul 2015 | WO |
| 2016206412 | Dec 2016 | WO |
| Entry |
|---|
| U.S. Appl. No. 16/993,035, filed Aug. 13, 2020 Notice of Allowance dated Mar. 7, 2023. |
| U.S. Appl. No. 17/562,270, filed Dec. 27, 2021 Notice of Allowance dated May 15, 2023. |
| Anon., “Epipolar geometry” https://en.wikipedia.org/wiki/Epipolar_geometry, last accessed May 4, 2020. |
| Anonymous: “From Fashion to Football Vision Pushes the Envelope of Entertainment” Nov. 24, 2014; Nov. 24, 2014; URL: https//www.automate.org/industry-insights/from-fashion-to-football-vision-pushes-the-envelope-of-entertainment. |
| C. Spiteri et al. “Quasi-thematic feature detection and tracking for future rover long-distance autonomous navigation.” Conference: Symposium on Advanced Space Technologies in Robotics and Automation, vol. 12, May 2013. |
| C. Spiteri, “Planetary Robotic Vision Processing for Terrain Assessment,” Section 6.1.1—Doctoral Thesis, Surrey Space Centre, Faculty of Engineering and Physical Sciences, University of Surrey. 2018. |
| C. Spiteri, et al. “Structure Augmented Monocular Saliency for Planetary Rovers,” Robotics and Autonomous Systems, vol. 88, Feb. 2017, pp. 1-10. |
| Careless James: “Bringing the Matrix to the NFL TV Tech,” Sep. 9, 2013; Sep. 9, 2013 Retrieved from the Internet URL: https//www.tvtechnology.com/news/bringing-the-matrix-to-the-nfl. |
| Costa Brandon: “The Next Big Thing How Replay Technologies freeD System Is Taking Sports TV by Storm,” Oct. 11, 2013; Oct. 11, 2013; URL: https//www.sportsvideo.org/2013/10/11/the-next-big-thing-how-replay-technologies-freed-system-is-taking-sports-tv-by-storm/. |
| PCT/US2021/025250 filed Mar. 31, 2021 International Search Report and Written Opinion dated Nov. 12, 2021. |
| R. I. Hartley et al. “Triangulation” CVIU—Computer Vision and Image Understanding, vol. 68, No. 2, pp. 146-157, Nov. 1997. |
| R. Sára, “3D Computer Vision” pp. 85-88, 100, 91-95. Oct. 30, 2012. |
| U.S. Appl. No. 16/993,030, filed Aug. 13, 2020 Non-Final Office Action dated Nov. 26, 2021. |
| U.S. Appl. No. 16/993,030, filed Aug. 13, 2020 Notice of Allowance dated Jul. 22, 2022. |
| U.S. Appl. No. 16/993,035, filed Aug. 13, 2020 Final Office Action dated Jan. 18, 2022. |
| U.S. Appl. No. 16/993,035, filed Aug. 13, 2020 Final Office Action dated Nov. 7, 2022. |
| U.S. Appl. No. 16/993,035, filed Aug. 13, 2020 Non-Final Office Action dated Jun. 29, 2022. |
| U.S. Appl. No. 16/993,035, filed Aug. 13, 2020 Non-Final Office Action dated Sep. 20, 2021. |
| C. Spiteri, “Generating a Three-Dimensional Topography of a Training Environment,” filed Jul. 21, 2023, U.S. Appl. No. 18/224,987 including its prosecution history. |
| C. Spiteri, “System and Method for Object Tracking and Metric Generation,” filed Aug. 13, 2020, U.S. Appl. No. 16/993,035 including its prosecution history. |
| C. Spiteri, “System and Method for Object Tracking Using a Subsection of a Sequence of Images, ” filed Jul. 14, 2023, U.S. Appl. No. 18/222,283 including its prosecution history. |
| C. Spiteri, “System and Method for Object Tracking,” filed Aug. 13, 2020, U.S. Appl. No. 16/993,030 Including its prosecution history. |
| E. J. Lewis et al., “Ball Throwing Machine and Method,” filed Feb. 9, 2015, U.S. Appl. No. 14/617,599 including its prosecution history. |
| E. J. Lewis et al., “Ball Throwing Machine and Method,” filed Jul. 27, 2017, U.S. Appl. No. 15/662,150 including its prosecution history. |
| E. J. Lewis et al., “Ball Throwing Machine and Method,” filed Nov. 2, 2011, U.S. Appl. No. 13/287,749 including its prosecution history. |
| E. J. Lewis et al., “Detection of the Speed of an Object Passing Through a Goal Plane,” filed Mar. 28, 2023, U.S. Appl. No. 18/191,755 including its prosecution history. |
| E. J. Lewis et al., “Goal Apparatus,” filed Sep. 19, 2018, U.S. Appl. No. 29/663,886 including its prosecution history. |
| E. J. Lewis et al., “System and Method for a User Adaptive Training and Gaming Platform,” filed Dec. 27, 2021, U.S. Appl. No. 17/562,270 including its prosecution history. |
| E. J. Lewis et al., “System and Method for a User Adaptive Training and Gaming Platform,” filed Nov. 15, 2019, U.S. Appl. No. 16/686,003 including its prosecution history. |
| E. J. Lewis et al., “System and Method for Object Tracking in Coordination With a Ball-Throwing Machine,” filed Aug. 17, 2020, U.S. Appl. No. 16/995,289 including its prosecution history. |
| E. J. Lewis et al., “System, Apparatus and Method for an Intelligent Goal,” filed Oct. 25, 2018, U.S. Appl. No. 16/171,127 including its prosecution history. |
| E. J. Lewis et al., “System, Apparatus and Method for Ball Throwing Machine and Intelligent Goal,” filed Dec. 9, 2016, U.S. Appl. No. 15/374,984 including its prosecution history. |
| S. Plumer et al., “System and Method for Altering the Motion of a Foosball,” filed Mar. 7, 2023, U.S. Appl. No. 18/180,109 including its prosecution history. |
| S. Plumer et al., “System and Method for Foosball Table Implementing Playing Obstacles,” filed Mar. 4, 2021, U.S. Appl. No. 17/192,766 including its prosecution history. |
| “HitTrax,” https://www.hittrax.com, last accessed Aug. 23, 2021. |
| PCT/US2020/060355 filed Nov. 13, 2020 International Search Report and Written Opinion dated Feb. 5, 2021. |
| U.S. Appl. No. 16/686,003, filed Nov. 15, 2019 Advisory Action dated Aug. 10, 2021. |
| U.S. Appl. No. 16/686,003, filed Nov. 15, 2019 Final Office Action dated May 19, 2021. |
| U.S. Appl. No. 16/686,003, filed Nov. 15, 2019 Non-Final Office Action dated Dec. 7, 2020. |
| U.S. Appl. No. 16/686,003, filed Nov. 15, 2019 Notice of Allowance dated Sep. 1, 2021. |
| U.S. Appl. No. 17/562,270, filed Dec. 27, 2021 Non-Final Office Action dated Nov. 25, 2022. |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 16993030 | Aug 2020 | US |
| Child | 17994834 | US |
