The present invention generally relates to game tournaments. More specifically, the present invention relates to online game tournament integration.
There are presently a wide variety of online games played in a variety of different modes. Some games are played head-to-head against one or more player, while others are played in teams, which may or may not be against another team. The ability to compete against other players and/or teams lends itself to tournament-style play. Similar to real-world tournaments, such a tournament for online games may involve setting up, identifying qualified players, ranking or seeding players, bracketing or matching each round, scheduling competitions, resolving disputes, broadcasting the tournament competitions, results verification, and timely communication of tournament data.
Many game titles do not provide native support for tournament-style play, however. As such, current online tournaments may be run by end-users or third parties whose systems are not integrated into the game and which therefore lack visibility and insight into in-game and tournament activities. Such online tournaments may therefore experience significant barriers to entry, as well as face problems in implementation. Such problems may lessen enjoyment and other benefits not only for the players, but also for spectators, commentators and other streamers, developers, sponsors, etc. As a result, tournaments may tend to be run by third parties for popular titles with numerous expert players. Such tournaments may exclude or at least be discouraging to novice players, as well as fail to offer less popular game titles.
One problem in the early stages of holding a tournament may involve skills evaluation. Tournaments are more competitive and therefore successful, for example, when disparities in skill level are not too great. Expert players may find it boring to play inexperienced players, while the inexperienced players may find it demoralizing to play expert players. Further, such games as played between players of wide disparate skill level are often short and have predictable outcomes, leading spectators to be bored as well.
Spectators may further face difficulties in identifying competitions that are part of a tournament, as well as obtaining tournament-related information. A spectator of games may avail themselves of a stream from a variety of online media outlets (e.g., Twitch). Such outlets may publish games from numerous players (including players who are not participating in tournaments), however, making it difficult or at least inconvenient for the spectator to identify which games are part of a particular tournament of interest. Such inconvenience risks loss of an interested audience of spectators.
The ability to attract, retain, and encourage repeat spectators is especially important to professional and semi-professional players whose gameplay may be sponsored. In addition to players who may be sponsored, commentators and other individuals who may seek to provide content related to tournaments may also face various difficulties in obtaining tournament data.
There is, therefore, a need in the art for improved systems and methods for online tournament integration.
Embodiments of the present invention allow for online tournament integration. A plurality of game titles each associated with at least one tournament may be hosted on a gaming network platform. Real-time gameplay data in matches involving the plurality of game titles may be tracked. Each match may be associated with a stream. Memory may store stream parameters and metrics associated with the at least one tournament. A predefined achievement may be identified for the at least one tournament when the tracked gameplay data for a match meets the stored metrics. The identified achievement may be determined to meet the stream parameters. A notification may be provided to the user device that includes a link to a stream of the match.
Various embodiments may include systems for online tournament integration. Such systems may include at least one game network server that hosts a plurality of game titles each associated with at least one tournament and tracks real-time gameplay data in matches involving the plurality of game titles and associated with a stream. Systems may further include at least one tournament server that stores one or more stream parameters and one or more metrics associated with the at least one tournament, identifies a predefined achievement for the at least one tournament when the tracked gameplay data for a match meets the stored metrics, determines that the identified achievement meets the stream parameters, and provides a notification to the user device, the notification including a link to a stream of the match.
Further embodiments may include methods for online tournament integration. Such methods may include hosting a plurality of game titles each associated with at least one tournament, tracking real-time gameplay data in matches involving the plurality of game titles and associated with a stream, storing one or more stream parameters and one or more metrics associated with the at least one tournament, identifying a predefined achievement for the at least one tournament when the tracked gameplay data for a match meets the stored metrics, determining that the identified achievement meets the stream parameters, and providing a notification to the user device, the notification including a link to a stream of the match.
Yet further embodiments may include non-transitory computer-readable storage media having embodied thereon programs executable to perform such methods as described above.
Embodiments of the present invention allow for online tournament integration. A plurality of game titles each associated with at least one tournament may be hosted on a gaming network platform. Real-time gameplay data in matches involving the plurality of game titles may be tracked. Each match may be associated with a stream. Memory may store stream parameters and metrics associated with the at least one tournament. A predefined achievement may be identified for the at least one tournament when the tracked gameplay data for a match meets the stored metrics. The identified achievement may be determined to meet the stream parameters. A notification may be provided to the user device that includes a link to a stream of the match.
Such online tournament integration may allow for tournaments to be held by individuals, developers, and other vendors. Providing online tournament integration may involve simple and generic tools for setting up and running a tournament at the platform level, while providing visibility into specific games. As such, a user may use such tools to set up a small tournament with friends who are casual players, while an event planner may use such tools to run a large tournament with numerous participants, complex rules, and involving even a plurality of game titles.
As illustrated, players 108, 109, and 110 are permitted access to online tournament system 112 using respective client devices (e.g., 108A, 109A, and 110A). Although client devices 108A, 109A, and 110A, are depicted as game console devices, it is understood that the client devices can include various types of processor-based systems, including but not limited to: personal computing devices, smartphones, tablets, other portable gaming devices, and the like. Such client devices 108A-110A may also be configured to access data from other storage media, such as memory cards or disk drives as may be appropriate in the case of downloaded services. Client devices 108A-110A may include standard hardware computing components such as network and media interfaces, non-transitory computer-readable storage (memory), and processors for executing instructions that may be stored in memory. Example of hardware systems that can be used to implement the client device are discussed in further detail below with respect to
Similarly, developers (e.g., 105, 106 and 107), are permitted access to online tournament system 112 via their respective computing systems (e.g., 105A, 106A, and 107A). Developer computing systems 105A-107A may include any type of server or other computing device as is known in the art, including standard hardware computing components such as network and media interfaces, non-transitory computer-readable storage (memory), and processors for executing instructions or accessing information that may be stored in memory. The functionalities of multiple servers may be integrated into a single server. Any of the aforementioned servers (or an integrated server) may take on certain client-side, cache, or proxy server characteristics. These characteristics may depend on the particular network placement of the server or certain configurations of the server. It is understood that a greater (or fewer) number of players and/or developers can be engaged with environment 100, without departing from the scope of the disclosed technology.
The players 108-110 may be registered with a user account associated with gaming network 104. Such user accounts may allow the user to access and play a variety of media titles on the gaming network platform. Gaming network 104 may further provides its registered users with options for verified accounts (e.g., for professional, semi-pro, or other celebrity users), team management, community tools, events tracking, social tools (e.g., friends lists), following other accounts, instant messaging, browsing live and archived streams, and other features related to playing or spectating games on the platform.
Gaming network 104 may be integrated with online tournament system 112 so as to allow for automatic communication of gameplay data. The gameplay data can be received by online tournament system 112, for example, using an application programming interface (API), such as API 114. Subsequently, the gameplay data can be passed from API 114 to statistics module 116 for use in player analysis. In a similar manner, game-play statistics can be collected by API 114 and passed to statistics module 116. Depending on implementation, gameplay statistics can be collected via active monitoring of an online game environment, or received from one or more external systems, for example, as part of a game performance data set that includes information describing individual player performance for one or more game titles and/or genre categories.
Online tournament system 112 may create and support tournament-style competitions between various players 108 (or teams of players) and for various game titles, as well as support related activities for streamers and spectators. A tournament may be created by a developer 106, player 108, or third party organizer (not pictured) by submitting a request over public network 102 and gaming network 104 to online tournament system 112. A tournament may be organized, for example, in conjunction with the new game title release. Such a tournament may specify that the tournament season starts one month after the game title release and last for three months. Players who register may be ranked during the season, and such rankings may be used to determine seeding and bracketing during the tournament. Such rankings may carry over to a certain extent between different tournament seasons, but may also be adjusted based on certain factors (e.g., lack of activity). In some embodiments, players that have played in previous seasons may enter the following season at a higher tier than brand new players. Further, the highest-ranked players may be dropped down a level so that they have room improve throughout the season.
A tournament may be customized in accordance with certain specified parameters, such as the game title(s) to be played, type of tournament (e.g., single elimination, double elimination, Swiss-system, round robin, deathmatch, racing), bracket types, match types, timeframe, a number of participants, and requirements or parameters for participating, match duration, level of competition, specific maps to be played, and/or strategies to be implemented. In some embodiments, the tournament organizer may further specify how the players may qualify, as well as how gameplay may be evaluated. For example, the tournament organizer may specify one or more in-game conditions or actions that increase or decrease the player's rankings with respect to other players. In some instances, a player access list can be used to specify specific players or types of players to be included (or excluded) from competition in a given tournament. Some tournaments may be available to high-ranking players only, while other tournaments may be organized specifically for casual or new players.
The online tournament system 112 may further provide a way for players having a user account in the gaming network platform to register for tournament play. Because the registering player may already have a user account, registration for tournament play may involve linking or otherwise accessing the user account information for use in tournament registration, as well as for associated qualification verification, recruiting and invitations, team-building, notifications, reminders, match scheduling and check-ins, updated brackets, results verification, real-time reporting, dispute management, and broadcast/stream production. A player account may be associated with a group of friends, for example, which may be a basis for sending out invitations to participate in the tournament, team-building, or organizing spectator watch parties.
For game titles that may be played in teams, a team may be associated with a team account or profile that includes such data for use by online tournament system 112. Such a team profile may be linked to the individual team member profiles. The online tournament system 112 may provide team management tools for use in scheduling and otherwise managing tournament participation by the team.
Spectator tools may also be provided to enable users to discover, tune in, watch, and interact in relation to the tournament. Discovery may involve providing certain kinds of information (e.g., from player or team profiles) so that a would-be spectator may determine whether a player, team, match, tournament, commentator, or other content producer/streamer may be of interest. A spectator—who may have their own user account—may further subscribe or follow a player, team, game title, or tournament of interest. Such a subscriber may therefore be provided with automatic notifications based on certain events or activities (e.g., scores, lead changes, game results, standings after each round, updated brackets) detected on the platform as being related to the subject of interest.
In addition to the features discussed above, online tournament system 112 may further use such data from user and team accounts and profiles to track tournament progress, update brackets and leaderboards, schedule matches, and perform other tournament-related functions. Conversely, information regarding each individual player's or team's progress or activities within the tournament may be automatically populated to the respective player or team profile. For example, a player profile may be tagged or include some other indicator that the player is participating in a particular tournament, what ranking or seeding the player is assigned, schedule of tournament matches, opponents (and associated rankings), real-time tournament data related to the player, links to streams of previously played tournament matches, links to active tournament matches, information regarding future tournament matches, etc.
Moreover, a spectator looking to observe a particular player may be linked to information regarding tournament streams involving the player of interest, as well as other tournament information regarding the player. In addition, a spectator looking specifically to observe tournament matches may be linked to active tournament streams of ongoing matches, as well as be provided with the latest updates regarding the tournament.
Because the metrics that are used to evaluate player performance for a particular game can vary widely between game title and type, the ability to rank and seed players require consideration of certain metrics. Such metrics may be converted from data generated in existing game titles or may be tracked at the platform during certain specified gameplay modes. Some legacy game titles may have their own ranking systems, which a tournament organizer may or may not rely on. A tournament organizer may elect to convert some or all of the existing ranking systems for use in tournament play. Creation of a tournament and corresponding parameters can be managed at the platform level, for example, by one or more of players 108-110. That is, individual players, player collectives, or other parties can specify the game-performance attributes desired for structuring the tournament.
To convert a legacy game title, a conversion key—provided by the game title developer or another party—may be applied to specific game-performance attributes so as to evaluate different players' performance relating to the game title in a standardized way. For example, the conversion key may extract and evaluate certain metrics (e.g., number of points scored, number of points allowed, number of kills, race times) with appropriate weights applied to each metric. Legacy game titles that rank each user using basic points-based systems may be mapped directly via percentiles of the ranked players.
Such standardization further allows for an objective comparison of skill level, which may provide a basis for rankings, seedings, and matchmaking. Different genres of games—and different roles within each game—may involve different standards. Team-based gameplay, for example, may involve teammates with different types of skill sets (e.g., different weaponry, resources, in-game abilities, powers, etc.). As such, the game play of different team members may be evaluated in accordance with the different standards despite playing in the same game title.
In some embodiments, a game developer may elect to take advantage of the tournament tools provided by online tournament system 112 to support tournaments for a certain game title. Such game titles may therefore offer a tournament mode in which gameplay is associated with an identified tournament, whether for qualification, participation, or reporting. A player may elect to play in other modes, for example, while learning to play a new game title, play in a different role/character, practicing certain skills, casual games, or other types of game that the player may not want to be counted or considered with respect to a tournament.
Tournament mode may also be used to qualify and be ranked or seeded for a tournament. As noted above, a tournament organizer may specify certain requirements, qualifications, or grouping criteria (e.g., for different skill levels). To qualify to play in an expert-level tournament, a player must be ranked at a certain level (e.g., top 50) among all players on the gaming network 104 platform that have registered with the tournament. A player seeking to qualify at that level may select tournament mode after training in practice mode, and points or other metrics achieved during a game played in tournament mode may therefore be considered in ranking that player. In some cases, metrics may be weighted based on various factors, including degree of difficulty, expertise or ranking of the opponent(s) played, how recent the achievements were, context of game (e.g., qualifying round vs. finals), etc. During a qualification period, for example, online tournament system 112 may evaluate the game performance attributes, and gameplay statistics to determine a skill level for each player in a given league, e.g., using processing/ranking module 118. Determinations of skill level can vary depending upon the specified game performance attributes, and can vary between game titles, and/or game genres. By way of example, skill level for a given player can be based on one or more of: collected points, a number of wins/losses, total game time, achieve difficulty level, and/or a number of “kills,” etc. Because game play occurs on the gaming network 104 platform, online tournament system 112 may obtain such results automatically and in real time, thereby by allowing for metrics generation, evaluation, and use in updating rankings, achievements designations, and leaderboards.
In some aspects, players registered for a given tournament can be ranked into multiple categories or tiers of skill level. For example, players may be categorized into a platinum tier for being in the top 2% of players, into a gold tier for being in the next 20% of players, into a silver tier for being in the next 28% of players, and into a bronze tier designated for the last 32%. Such tiers may further be subdivided as needed into+ or − subdivisions. A player categorized as gold+ may be close to being moved into the platinum tier, for example, while a player categorized as gold− may be close to falling into the silver tier.
Designations of achievement or skill level can be provided based on the overall ranking of a player or group of players. For example, digital badges, trophies, or medals can be provided to the top-ranked player (or player team), and published on an associated player (or team) profile. Such designations may be awarded as to a current season and remain visible in future seasons. Different designations may be provided for different game titles, different combinations of achievements, overall ratings, etc. Not only can such designations and tier levels serve as the basis for matching competitors, but such indicators may be searched by spectators looking to watch players of a certain level in a certain game title. Various search and sorting options may be provided (e.g., game title, ranking, stream parameters) so that players or potential spectators may filter through the available game streams, players, teams, tournaments, etc. to find other players of interest. A player may wish to find a similarly-skilled practice sparring partner, for example, or a teammate with complementary skills. Such spectators may choose to follow such players, for example, and request notifications, reminders, and schedules relating to matches involving the player(s) of interest. In some embodiments, such designations may be made available through other outlets (e.g., stream sources such as Twitch) for searching and filtering based on a standardized skill evaluation system.
Different ranking systems may be available for different game titles. Moreover, different ranking systems may be available for tournaments. A tournament may involve multiple game titles, for example, and as such, a ranking system may combine and/or weight different individual rankings within the game titles as desired by the tournament organizer. An overall ranking for any combination of games played on the platform may also be available. As such, a player may distinguish themselves as a skilled player not only in one or a few game titles (or even a game family or genre), but within multiple different types of games.
Depending on the number of registrants, a tournament may hold a set of qualifying rounds to reduce the number of registrants to a desired number. Alternatively, the tournament organizer may elect to have an invitation-based system based on rankings and any other factors deemed appropriate.
Moreover, because the online tournament system 112 is in communication with gaming network 104, the online tournament system 112 may receive and analyze game data in real-time. As such, online tournament system 112 may detect when a match has started, when the match is particularly active or competitive, and other in-game events. For example, certain in-game events may be associated with certain game data or metrics. Use of certain weaponry, exhibition of certain character moves or maneuvers, scoring in a certain amount or pattern, etc., may be indicative of an unusual or otherwise notable in-game event. As such, screenshots or video may be captured regarding such events and published with links that can take a spectator to the stream, whether at the beginning of the match or directly to illustrated point of interest. Such links may be accessed in real-time (e.g., as the match is occurring) or in association with an archived stream. In some embodiments, such links may be published on the gaming network 104 platform (e.g., landing pages, leaderboards, communities, forums, user profiles, team profiles, tournament profiles, bookmarks) or on sites associated with the player, team, developer, tournament organizer, broadcaster, or other content producer or streamer.
The identification of unusual, interesting, or otherwise significant events may also allow for advertising, promotion, discovery, and related functions. As such, notifications, reminders, video clips, screenshots, and other data may also be generated and provided to other parties, players, spectators, and potential spectators in real-time regarding such events. Such data may also support commentators and third-party broadcasters/streamers for use in producing their respective content streams.
In step 210, a tournament request may be received by online tournament system 112. As noted herein, the tournament requested may be small (e.g., requested by an individual user for a small group of friends) or large (e.g., massive multiplayer game titles with numerous participants). A tournament request may involve one or more game titles available through gaming network 104, as well as may specify a variety of parameters for qualifying, rankings, scheduling, etc. A player having a user account (or team having a team account) on gaming network 104 may register and have their data automatically shared with online tournament system 112 for use in facilitating registration, rankings, promotions, awards, searches, and other tournament-related activities. The tournament request may further explain the ranking system, which may include any combination of gameplay metrics used to evaluate each registrant in a standardized way.
In step 220, gameplay may be tracked for the game titles specified in the tournament request. As described above, a player may switch between different modes of game play. While gameplay during practice mode may be excluded from consideration with respect to towards tournament qualification, gameplay during a tournament mode may be considered and its metrics counted toward tournament-related rankings. The particular metrics being tracked and evaluated may differ by game title and by parameters specified by the tournament organizer. Further, the parameters may be weighted differently based on preferences specified by the tournament organizer as well.
In step 230, the relevant gameplay by all tournament registrants may therefore be ranked in accordance with the tournament-specific parameters. One or more leaderboards (e.g., individual metrics or combined metrics) may be maintained throughout the qualification phase and tournament. Designations indicative of high metrics may also be populated to the profile of the player or team that achieved such metrics. Such designations may include badges, trophies, titles, etc., and may be awarded periodically (e.g., highest scorer during a specified week) or for an overall tournament.
In step 240, the qualification phase may end with a number of registered players (or teams). If the number is higher than the number specified by the tournament organizer, one or more initial rounds may be held to determine which players/teams advance to the official tournament rounds. Some embodiments may allow the top players to advance automatically (e.g., a bye), while lower-ranked players may be required to compete in the initial rounds in order to continue to play in the tournament.
In step 250, brackets may be assigned. In some embodiments, brackets may be assigned based on rankings. The type of brackets may depend on the type of matches (e.g., head-to-head or multiplayer) being played. Further, rankings may also be adjusted during the tournament. As such, a player or team that has a low ranking at the beginning of the tournament may nevertheless advance and be given a top seed based on high-level tournament play. As noted above, because the tournament games are played in gaming network 104, the gameplay data therein may be automatically evaluated and published to various profiles, landing pages, and other designated outlets and recipients.
In step 260, a broadcast stream may be automatically generated for each tournament game and published on the gaming network 104 platform in any of the various pages and locations discussed herein. The broadcast stream may further be tagged with any of the relevant data associated therewith, including participating players, teams, game titles, respective designations (e.g., involving a top-ranked player), and any in-game events that may be determined to be of interest.
In step 310, multiple tournaments may be hosted on the gaming network 104 platform. Such tournaments may be organized and held as described with respect to the method illustrated in
In step 320, any achievements occurring during the tournaments may be tracked in real-time. Because the games or matches are being played on the gaming network 104 platform, the respective gameplay data may be evaluated in real-time to identify noteworthy in-game events, which may not only include scores or lead changes, but also unusual movement combinations, notable speeds, notable kills, etc.
In step 330, participant profiles may be updated in real-time regarding such achievements, so as to notify spectators, subscribers, developers, sponsors, broadcasters, commentators, upcoming competitors, etc. Such achievements may also be published or otherwise pushed out through various channels (e.g., Twitch) that may track such players, teams, or matches.
In step 340, stream parameters may be specified by a party interested in the tournament. A potential spectator, for example, may be a user of gaming network 104 who may have subscribed to watch matches involving certain tournament participants (players or teams). As such, any streams involving the subjects of interest may be filtered and sorted based on the parameters. Sorting may further be based on current rankings, current participation in a match, notable in-game events, etc., or any other factor of interest that may be specified by a spectator.
In step 350, the available streams may be filtered and sorted in accordance with the parameters specified in step 340. In some instances, the available streams may include archived but unwatched streams, as well as live streams.
In step 360, the filtered and sorted results (e.g., a list of streams) may be displayed to the requesting party. The bases for such filtering and sorting—which may be associated with the notability designations discussed herein—may also be displayed in conjunction with the results, thereby allowing the party (e.g., spectator) to jump not only to a stream of interest, but directly to a notable event depicted within the stream.
The user device 400 may include various elements as illustrated in
The tracking device 424 may be a camera, which includes eye-tracking capabilities. The camera may be integrated into or attached as a peripheral device to user device 400. In typical eye-tracking devices, infrared non-collimated light is reflected from the eye and sensed by a camera or optical sensor. The information is then analyzed to extract eye rotation from changes in reflections. Camera-based trackers focus on one or both eyes and record their movement as the viewer looks at some type of stimulus. Camera-based eye trackers use the center of the pupil and light to create corneal reflections (CRs). The vector between the pupil center and the CR can be used to compute the point of regard on surface or the gaze direction. A simple calibration procedure of the viewer is usually needed before using the eye tracker.
Alternatively, more sensitive trackers use reflections from the front of the cornea and that back of the lens of the eye as features to track over time. Even more sensitive trackers image features from inside the eye, including retinal blood vessels, and follow these features as the eye rotates.
Most eye tracking devices use a sampling rate of at least 30 Hz, although 50/60 Hz is most common. Some tracking devises run as high as 1250 Hz, which is needed to capture detail of very rapid eye movement.
A range camera may instead be used with the present invention to capture gestures made by the user and is capable of facial recognition. A range camera is typically used to capture and interpret specific gestures, which allows a hands-free control of an entertainment system. This technology may use an infrared projector, a camera, a depth sensor, and a microchip to track the movement of objects and individuals in three dimensions. This user device may also employ a variant of image-based three-dimensional reconstruction.
The tracking device 424 may include a microphone integrated into or attached as a peripheral device to user device 400 that captures voice data. The microphone may conduct acoustic source localization and/or ambient noise suppression.
Alternatively, tracking device 424 may be the controller of the user device 400. The controller may use a combination of built-in accelerometers and infrared detection to sense its position in 3D space when pointed at the LEDs in a sensor nearby, attached to, or integrated into the console of the entertainment system. This design allows users to control functionalities of the user device 400 with physical gestures as well as button-presses. The controller connects to the user device 400 using wireless technology that allows data exchange over short distances (e.g., 30 feet). The controller may additionally include a “rumble” feature (i.e., a shaking of the controller during certain points in the game) and/or an internal speaker.
The controller may additionally or alternatively be designed to capture biometric readings using sensors in the remote to record data including, for example, skin moisture, heart rhythm, and muscle movement.
As noted above, the user device 400 may be an electronic gaming console. Alternatively, the user device 400 may be implemented as a general-purpose computer, a set-top box, or a hand-held gaming device. Further, similar user devices may contain more or less operating components.
CPU 404, vector unit 406, graphics processing unit 408, and I/O processor 410 communicate via system bus 436. Further, the CPU 404 communicates with the main memory 402 via a dedicated bus 438, while the vector unit 406 and the graphics processing unit 408 may communicate through a dedicated bus 440. The CPU 404 executes programs stored in the OS ROM 426 and the main memory 402. The main memory 402 may contain pre-stored programs and programs transferred through the I/O Processor 410 from a CD-ROM, DVD-ROM, or other optical disc (not shown) using the optical disc control unit 432. The I/O processor 410 primarily controls data exchanges between the various devices of the user device 400 including the CPU 404, the vector unit 406, the graphics processing unit 408, and the controller interface 414.
The graphics processing unit 408 executes graphics instructions received from the CPU 404 and the vector unit 406 to produce images for display on a display device (not shown). For example, the vector unit 406 may transform objects from three-dimensional coordinates to two-dimensional coordinates, and send the two-dimensional coordinates to the graphics processing unit 408. Furthermore, the sound processing unit 430 executes instructions to produce sound signals that are outputted to an audio device such as speakers (not shown).
A user of the user device 400 provides instructions via the controller interface 414 to the CPU 404. For example, the user may instruct the CPU 404 to store certain information on the memory card 416 or instruct the user device 400 to perform some specified action.
Other devices may be connected to the user device 400 via the USB interface 418, the IEEE 1394 interface 420, and the AUX interface 422. Specifically, a tracking device 424, including a camera or a sensor may be connected to the user device 400 via the AUX interface 422, while a controller may be connected via the USB interface 418.
The present invention may be implemented in an application that may be operable using a variety of devices. Non-transitory computer-readable storage media refer to any medium or media that participate in providing instructions to a central processing unit (CPU) for execution. Such media can take many forms, including, but not limited to, non-volatile and volatile media such as optical or magnetic disks and dynamic memory, respectively. Common forms of non-transitory computer-readable media include, for example, a floppy disk, a flexible disk, a hard disk, magnetic tape, any other magnetic medium, a CD-ROM disk, digital video disk (DVD), any other optical medium, RAM, PROM, EPROM, a FLASHEPROM, and any other memory chip or cartridge.
Various forms of transmission media may be involved in carrying one or more sequences of one or more instructions to a CPU for execution. A bus carries the data to system RAM, from which a CPU retrieves and executes the instructions. The instructions received by system RAM can optionally be stored on a fixed disk either before or after execution by a CPU. Various forms of storage may likewise be implemented as well as the necessary network interfaces and network topologies to implement the same.
The foregoing detailed description of the technology has been presented for purposes of illustration and description. It is not intended to be exhaustive or to limit the technology to the precise form disclosed. Many modifications and variations are possible in light of the above teaching. The described embodiments were chosen in order to best explain the principles of the technology, its practical application, and to enable others skilled in the art to utilize the technology in various embodiments and with various modifications as are suited to the particular use contemplated. It is intended that the scope of the technology be defined by the claim.
The present application is a continuation and claims the priority benefit of U.S. patent application Ser. No. 17/207,679 filed Mar. 21, 2021, now U.S. Pat. No. 11,617,961, which is a continuation and claims the priority benefit of U.S. patent application Ser. No. 15/908,569 filed Feb. 28, 2018, now U.S. Pat. No. 10,953,335, which are incorporated herein by reference in their entirety.
Number | Name | Date | Kind |
---|---|---|---|
5729471 | Jain et al. | Mar 1998 | A |
5995518 | Burns et al. | Nov 1999 | A |
6415317 | Yelon et al. | Jul 2002 | B1 |
6546421 | Wynblatt et al. | Apr 2003 | B1 |
6631522 | Erdelyi | Oct 2003 | B1 |
6877134 | Fuller et al. | Apr 2005 | B1 |
7499475 | Kashiwagi et al. | Mar 2009 | B2 |
8025572 | Spanton et al. | Sep 2011 | B2 |
8187104 | Pearce | May 2012 | B2 |
8202167 | Ackely et al. | Jun 2012 | B2 |
8645844 | Strobel et al. | Feb 2014 | B1 |
8702520 | Seelig et al. | Apr 2014 | B2 |
9216356 | Grier | Dec 2015 | B2 |
9233305 | Laakkonen et al. | Jan 2016 | B2 |
9433855 | Keeker et al. | Sep 2016 | B1 |
9473825 | Gossweiler et al. | Oct 2016 | B2 |
9479602 | Paradise et al. | Oct 2016 | B1 |
9497424 | Kosseifi et al. | Nov 2016 | B2 |
9561433 | Pieron et al. | Feb 2017 | B1 |
9782678 | Long et al. | Oct 2017 | B2 |
9814987 | Lawson | Nov 2017 | B1 |
9860477 | Kummer et al. | Jan 2018 | B2 |
9871997 | Kosseifi et al. | Jan 2018 | B2 |
9968856 | Ninoles et al. | May 2018 | B1 |
10277813 | Thomas et al. | Apr 2019 | B1 |
10471360 | Trombetta | Nov 2019 | B2 |
10617145 | Besso et al. | Apr 2020 | B2 |
10751623 | Trombetta | Aug 2020 | B2 |
10765938 | Trombetta | Sep 2020 | B2 |
10765957 | Trombetta | Sep 2020 | B2 |
10792576 | Trombetta | Oct 2020 | B2 |
10792577 | Trombetta | Oct 2020 | B2 |
10814228 | Trombetta | Oct 2020 | B2 |
10818142 | Trombetta | Oct 2020 | B2 |
10953322 | Trombetta | Mar 2021 | B2 |
10953335 | Thielbar | Mar 2021 | B2 |
11065548 | Trombetta | Jul 2021 | B2 |
11241630 | Trombetta | Feb 2022 | B2 |
11426654 | Trombetta | Aug 2022 | B2 |
11439918 | Trombetta | Sep 2022 | B2 |
11439919 | Trombetta | Sep 2022 | B2 |
11452943 | Trombetta | Sep 2022 | B2 |
11600144 | Trombetta | Mar 2023 | B2 |
11612816 | Trombetta | Mar 2023 | B2 |
11617961 | Thielbar | Apr 2023 | B2 |
11660531 | Trombetta | May 2023 | B2 |
11660544 | Trombetta | May 2023 | B2 |
20020034980 | Lemmons et al. | Mar 2002 | A1 |
20020107040 | Crandall et al. | Aug 2002 | A1 |
20030177347 | Schneier et al. | Sep 2003 | A1 |
20030190960 | Jokipii | Oct 2003 | A1 |
20030220143 | Shteyn et al. | Nov 2003 | A1 |
20030228908 | Caiafa et al. | Dec 2003 | A1 |
20040147306 | Randall et al. | Jul 2004 | A1 |
20040189701 | Badt | Sep 2004 | A1 |
20040257994 | Paskett et al. | Dec 2004 | A1 |
20040266535 | Reeves | Dec 2004 | A1 |
20050020359 | Ackely et al. | Jan 2005 | A1 |
20050026699 | Kinzer | Feb 2005 | A1 |
20050070355 | Shimizu | Mar 2005 | A1 |
20060105827 | Metzger et al. | May 2006 | A1 |
20060247060 | Hanson et al. | Nov 2006 | A1 |
20060287096 | O'Kelley et al. | Dec 2006 | A1 |
20070018952 | Arseneau et al. | Jan 2007 | A1 |
20070021058 | Aresneau et al. | Jan 2007 | A1 |
20070070914 | Abigail | Mar 2007 | A1 |
20070117617 | Spanton et al. | May 2007 | A1 |
20070117635 | Spanton et al. | May 2007 | A1 |
20070149272 | Dinkin | Jun 2007 | A1 |
20070149288 | Nickell et al. | Jun 2007 | A1 |
20070179792 | Kramer | Aug 2007 | A1 |
20070191102 | Coliz et al. | Aug 2007 | A1 |
20070243936 | Binenstock | Oct 2007 | A1 |
20070248261 | Zhou et al. | Oct 2007 | A1 |
20080079752 | Gates et al. | Apr 2008 | A1 |
20080113815 | Weingardt et al. | May 2008 | A1 |
20080119286 | Brunstetter et al. | May 2008 | A1 |
20080200254 | Cayce et al. | Aug 2008 | A1 |
20090036214 | Dahl | Feb 2009 | A1 |
20090042646 | Sarkar et al. | Feb 2009 | A1 |
20090082110 | Relyea et al. | Mar 2009 | A1 |
20090144448 | Smith | Jun 2009 | A1 |
20090208181 | Cottrell | Aug 2009 | A1 |
20090225828 | Perlman et al. | Sep 2009 | A1 |
20090271821 | Zalewski | Oct 2009 | A1 |
20090275374 | Nelson et al. | Nov 2009 | A1 |
20100099330 | Digiovanni | Apr 2010 | A1 |
20100100512 | Brodin et al. | Apr 2010 | A1 |
20100240443 | Baerlocher et al. | Sep 2010 | A1 |
20100306813 | Perry et al. | Dec 2010 | A1 |
20110092282 | Gary | Apr 2011 | A1 |
20110207523 | Filipour et al. | Aug 2011 | A1 |
20110250939 | Hobler | Oct 2011 | A1 |
20110263332 | Mizrachi | Oct 2011 | A1 |
20110263333 | Dokei et al. | Oct 2011 | A1 |
20110275431 | Hirzel et al. | Nov 2011 | A1 |
20110319160 | Arn et al. | Dec 2011 | A1 |
20120093481 | McDowell et al. | Apr 2012 | A1 |
20120123566 | Ross | May 2012 | A1 |
20120142411 | Thompson et al. | Jun 2012 | A1 |
20120278439 | Ahiska et al. | Nov 2012 | A1 |
20120283017 | Ahiska et al. | Nov 2012 | A1 |
20130002949 | Raveendran et al. | Jan 2013 | A1 |
20130007013 | Geisner et al. | Jan 2013 | A1 |
20130083173 | Geisner et al. | Apr 2013 | A1 |
20130123019 | Sullivan et al. | May 2013 | A1 |
20130231189 | Beeler | Sep 2013 | A1 |
20130254680 | Buhr et al. | Sep 2013 | A1 |
20130296051 | Gault et al. | Nov 2013 | A1 |
20130324239 | Ur et al. | Dec 2013 | A1 |
20130331192 | Betti et al. | Dec 2013 | A1 |
20140004951 | Kern et al. | Jan 2014 | A1 |
20140031121 | Kern et al. | Jan 2014 | A1 |
20140087846 | Bryan et al. | Mar 2014 | A1 |
20140087851 | Low et al. | Mar 2014 | A1 |
20140113718 | Norman et al. | Apr 2014 | A1 |
20140142921 | Gleadall et al. | May 2014 | A1 |
20140171039 | Bjontegard | Jun 2014 | A1 |
20140171182 | Versaci | Jun 2014 | A1 |
20140179440 | Perry | Jun 2014 | A1 |
20140228112 | Laakkonen et al. | Aug 2014 | A1 |
20140274307 | Gonzalez | Sep 2014 | A1 |
20140274368 | Cotter | Sep 2014 | A1 |
20140274370 | Shah | Sep 2014 | A1 |
20140297408 | Zabala | Oct 2014 | A1 |
20140331265 | Mozell et al. | Nov 2014 | A1 |
20140370979 | Zahn et al. | Dec 2014 | A1 |
20150005052 | Harrington et al. | Jan 2015 | A1 |
20150011283 | Sanford et al. | Jan 2015 | A1 |
20150018990 | Shachar et al. | Jan 2015 | A1 |
20150024850 | Kokami et al. | Jan 2015 | A1 |
20150088289 | Robbins et al. | Mar 2015 | A1 |
20150113548 | Stern et al. | Apr 2015 | A1 |
20150141140 | Lampe et al. | May 2015 | A1 |
20150148137 | Harris | May 2015 | A1 |
20150238859 | Fear | Aug 2015 | A1 |
20150248792 | Abovitz et al. | Sep 2015 | A1 |
20150281029 | Callahan et al. | Oct 2015 | A1 |
20150306502 | Angelopoulos | Oct 2015 | A1 |
20150348373 | Weingardt et al. | Dec 2015 | A1 |
20150375117 | Thompson et al. | Dec 2015 | A1 |
20160051895 | Hood | Feb 2016 | A1 |
20160193530 | Parker et al. | Jul 2016 | A1 |
20160214012 | Nishikawa | Jul 2016 | A1 |
20160217660 | Marks | Jul 2016 | A1 |
20160243450 | Cotter | Aug 2016 | A1 |
20160253865 | Men et al. | Sep 2016 | A1 |
20160286244 | Chang et al. | Sep 2016 | A1 |
20160310843 | Webb | Oct 2016 | A1 |
20160365121 | DeCaprio | Dec 2016 | A1 |
20160373499 | Wagner et al. | Dec 2016 | A1 |
20170001111 | Willette et al. | Jan 2017 | A1 |
20170001112 | Gilmore | Jan 2017 | A1 |
20170001122 | Leung et al. | Jan 2017 | A1 |
20170003740 | Verfaillie et al. | Jan 2017 | A1 |
20170003784 | Garg et al. | Jan 2017 | A1 |
20170006074 | Oates | Jan 2017 | A1 |
20170072324 | Navok et al. | Mar 2017 | A1 |
20170113143 | Marr | Apr 2017 | A1 |
20170157512 | Long et al. | Jun 2017 | A1 |
20170182426 | Loeb et al. | Jun 2017 | A1 |
20170209795 | Harvey et al. | Jul 2017 | A1 |
20170266549 | Paradise | Sep 2017 | A1 |
20170266552 | Paradise | Sep 2017 | A1 |
20170270751 | Paradise | Sep 2017 | A1 |
20170282075 | Michot et al. | Oct 2017 | A1 |
20170282082 | Hubbard | Oct 2017 | A1 |
20170304724 | Cotter | Oct 2017 | A1 |
20170332131 | Opsenica et al. | Nov 2017 | A1 |
20170354875 | Marks et al. | Dec 2017 | A1 |
20170374402 | Pogorelik et al. | Dec 2017 | A1 |
20180001199 | Gary | Jan 2018 | A1 |
20180001216 | Bruzzo | Jan 2018 | A1 |
20180077438 | Hensen et al. | Mar 2018 | A1 |
20180139257 | Ninoles et al. | May 2018 | A1 |
20180167656 | Ortiz et al. | Jun 2018 | A1 |
20180192144 | McElroy | Jul 2018 | A1 |
20180250598 | Trombetta | Sep 2018 | A1 |
20180250600 | Trombetta | Sep 2018 | A1 |
20180367820 | Abulikemu | Dec 2018 | A1 |
20190099675 | Khan et al. | Apr 2019 | A1 |
20190102941 | Khan et al. | Apr 2019 | A1 |
20190118098 | Payzer et al. | Apr 2019 | A1 |
20190262705 | Trombetta | Aug 2019 | A1 |
20190262706 | Trombetta | Aug 2019 | A1 |
20190262712 | Trombetta | Aug 2019 | A1 |
20190262713 | Trombetta | Aug 2019 | A1 |
20190262717 | Thielbar | Aug 2019 | A1 |
20190262720 | Trombetta | Aug 2019 | A1 |
20190262723 | Trombetta | Aug 2019 | A1 |
20190262724 | Trombetta | Aug 2019 | A1 |
20190262727 | Trombetta | Aug 2019 | A1 |
20190266845 | Trombetta | Aug 2019 | A1 |
20200179812 | Trombetta | Jun 2020 | A1 |
20200384364 | Trombetta | Dec 2020 | A1 |
20200398157 | Trombetta | Dec 2020 | A1 |
20200398169 | Trombetta | Dec 2020 | A1 |
20200406152 | Trombetta | Dec 2020 | A1 |
20210016190 | Trombetta | Jan 2021 | A1 |
20210043044 | Trombetta | Feb 2021 | A1 |
20210052982 | Trombetta | Feb 2021 | A1 |
20210178257 | Trombetta | Jun 2021 | A1 |
20210205711 | Thielbar | Jul 2021 | A1 |
20210346809 | Trombetta | Nov 2021 | A1 |
20220409997 | Harris | Dec 2022 | A1 |
20230249062 | Trombetta | Aug 2023 | A1 |
Number | Date | Country |
---|---|---|
1607535 | Apr 2005 | CN |
104394400 | Mar 2015 | CN |
105188867 | Dec 2015 | CN |
105227952 | Jan 2016 | CN |
107360442 | Nov 2017 | CN |
107735152 | Feb 2018 | CN |
110201395 | Sep 2019 | CN |
110201398 | Sep 2019 | CN |
110201399 | Sep 2019 | CN |
110201401 | Sep 2019 | CN |
110201402 | Sep 2019 | CN |
110201404 | Sep 2019 | CN |
110573221 | Dec 2019 | CN |
111971097 | Nov 2020 | CN |
112423854 | Feb 2021 | CN |
112423855 | Feb 2021 | CN |
112543669 | Mar 2021 | CN |
117580622 | Feb 2024 | CN |
ZL201980015974.8 | Apr 2024 | CN |
3058996 | Aug 2016 | EP |
3592441 | Jan 2020 | EP |
3758813 | Jan 2021 | EP |
3758814 | Jan 2021 | EP |
3758815 | Jan 2021 | EP |
3758816 | Jan 2021 | EP |
3758818 | Jan 2021 | EP |
3758819 | Jan 2021 | EP |
3758821 | Jan 2021 | EP |
3759930 | Jan 2021 | EP |
3759934 | Jan 2021 | EP |
3758820 | Feb 2021 | EP |
4363069 | May 2024 | EP |
0109964 | Jun 2001 | GB |
517732 | Feb 2024 | IN |
530996 | Mar 2024 | IN |
2001-170360 | Jun 2001 | JP |
2007-036830 | Feb 2007 | JP |
2011-512172 | Apr 2011 | JP |
2011-224204 | Nov 2011 | JP |
2012-176127 | Sep 2012 | JP |
2021-514748 | Jun 2021 | JP |
2021-514749 | Jun 2021 | JP |
2021-514750 | Jun 2021 | JP |
2021-514751 | Jun 2021 | JP |
2021-514752 | Jun 2021 | JP |
2021-514753 | Jun 2021 | JP |
2021-514754 | Jun 2021 | JP |
2021-515485 | Jun 2021 | JP |
2021-516087 | Jul 2021 | JP |
2021-516088 | Jul 2021 | JP |
7184913 | Nov 2022 | JP |
7184914 | Nov 2022 | JP |
7239596 | Mar 2023 | JP |
7250026 | Mar 2023 | JP |
7268046 | Apr 2023 | JP |
7296978 | Jun 2023 | JP |
7369133 | Oct 2023 | JP |
7386169 | Nov 2023 | JP |
7438959 | Feb 2024 | JP |
10-2020-0126975 | Nov 2020 | KR |
10-2020-0127169 | Nov 2020 | KR |
10-2020-0127172 | Nov 2020 | KR |
10-2020-0127173 | Nov 2020 | KR |
10-2020-0128523 | Nov 2020 | KR |
10-2020-0135946 | Dec 2020 | KR |
10-2020-0136894 | Dec 2020 | KR |
10-2418756 | Jul 2022 | KR |
10-2577365 | Sep 2023 | KR |
10-2590690 | Oct 2023 | KR |
10-2602398 | Nov 2023 | KR |
WO 2010030313 | Mar 2010 | WO |
WO 2014109435 | Jul 2014 | WO |
WO 2016048204 | Mar 2016 | WO |
WO 2016201333 | Dec 2016 | WO |
WO 2017004433 | Jan 2017 | WO |
WO 2018004812 | Jan 2018 | WO |
WO 2018160274 | Sep 2018 | WO |
WO 2018165191 | Sep 2018 | WO |
WO 2019168614 | Sep 2019 | WO |
WO 2019168615 | Sep 2019 | WO |
WO 2019168619 | Sep 2019 | WO |
WO 2019168620 | Sep 2019 | WO |
WO 2019168630 | Sep 2019 | WO |
WO 2019168631 | Sep 2019 | WO |
WO 2019168636 | Sep 2019 | WO |
WO 2019168637 | Sep 2019 | WO |
WO 2019168638 | Sep 2019 | WO |
WO 2019168646 | Sep 2019 | WO |
WO 2023277992 | Jan 2023 | WO |
Entry |
---|
Dietrich et al., Carlos; “Baseball4D: A tool for baseball game reconstruction & visualization”, 2014 IEEE Conference on Visual Analytics Science and Technology (VAST), IEEE, Oct. 25, 2014, pp. 23-32. |
NAHL ranked #1 by The Junior Hockey News_North American Hockey League_NAHL.pdf, http://nahl.com/news/story.cfm?id=15090, Jul. 16, 2015 (Year: 2015). |
Racing game video curation application “Motor Tube” starts delivering its service, 4Gamer.net [online], Nov. 17, 2016 https://msygroup.com/pressrelease/%E6%A0%BC%E9%97%98%E3%82%B2%E3%83%BC%E3%83%A0%E5%B0%82%E9%96%80%E5%8B%95%E7%94%BB%E3%82%AD%E3%83%A5%E3%83%AC%E3%83%BC%E3%82%B7%E3%83%A7%E3%83%B3%E3%8 2%A2%E3%83%97%E3%83%AA%E3%80%8C%E6%A0%BC%E3%82%B2/ [retrieved on: Nov. 25, 2022]. |
Support is announced for battle game video curation application “Kak-gei Tube”, MSY [onlin], Jul. 14, 2016, https://www.4gamer.net/games/251/G025195/20161117017/, [retrieved on: Nov. 25, 2022]. |
Star soldier stage 01, high score 341,100, YouTube [online], May 22, 2011, https://www.youtube.com/watch?v=S2NMFJ7PtDQ, [retrieved on: Nov. 27, 2023] (document showing well-known art; newly cited document). |
Mario kart 64, Mario circuit 1′14″48 Non-SC time attach, YouTube [online], Oct. 16, 2015, https://www.youtube.com/watch?v=4qJIKWUduPO, [retrieved on: Nov. 27, 2023]. |
Application No. 19760732.8 Decision to Refuse dated Mar. 20, 2024. |
Application No. 19760732.8 Extended European Search Report dated Oct. 1, 2021. |
Application No. 2020-545251 Final Notification of Reasons for Refusal dated Sep. 5, 2023. |
Application No. 2020-545251 Final Notification of Reasons for Refusal dated Mar. 28, 2023. |
Application No. 2020-545251 Non-Final Notification of Reasons for Refusal dated Oct. 11, 2022. |
Application No. 201880028575.0, First Office Action dated Feb. 20, 2023. |
Application No. 18763374.8, Extended European Search Report dated Dec. 14, 2020. |
Application No. 10-2019-7029332 Office Action dated Oct. 19, 2021. |
Application No. 19760888.8 Extended European Search Report dated Oct. 27, 2021. |
Application No. 2020-545273 Non-Final Notification of Reasons for Refusal dated Oct. 18, 2022. |
Application No. 201910110368.6 First Office Action dated Jan. 18, 2024. |
Application No. 19761465.4 Extended European Search Report dated Sep. 1, 2021. |
Application No. 2020-55313 Decision of Refusel dated Dec. 5, 2023. |
Application No. 2020-55313 Non-Final Notification of Reasons for Refusal dated Jun. 13, 2023. |
Application No. 2020-55313 Non-Final Notification of Reasons for Refusal dated Dec. 6, 2022. |
Application No. 10-2020-7025084 Office Action dated Sep. 8, 2023. |
Application No. 201910110397.2 Office Action dated Jan. 9, 2024. |
Application No. 19760016.6 Extended European Search Report dated Oct. 8, 2021. |
Application No. 2020-545317 Non-Final Notification of Reasons for Refusal dated Nov. 15, 2022. |
Application No. 201910110390.0 First Office Action dated Jan. 22, 2024. |
Application No. 19759929.3 Office Action dated Jun. 23, 2023. |
Application No. 19759929.3 Extended European Search Report dated Oct. 25, 2021. |
Application No. 2020-545263 Final Notification of Reasons for Refusal dated Jun. 13, 2023. |
Application No. 2020-545263 Non-Final Notification of Reasons for Refusal dated Dec. 6, 2022. |
Application No. 10-2020-7025049 Office Action dated Jan. 4, 2024. |
Application No. 201910110370.3 First Office Action dated Mar. 14, 2024. |
Application No. 19761341.7 Office Action dated Jan. 19, 2023. |
Application No. 19761341.7 Extended European Search Report dated Aug. 17, 2021. |
Application No. 2020-545320 Notification of Reasons for Refusal dated Nov. 15, 2022. |
Application No. 201980015977.1 First Office Action dated Feb. 28, 2024. |
Application No. 19760240.2 Extended European Search Report dated Feb. 2, 2022. |
Application No. 19760240.2 Partial Supplementary European Search Report dated Oct. 13, 2021. |
Application No. 2020-545275 Notification of Reasons for Refusal dated Apr. 18, 2023. |
Application No. 2020-545275 Non-Final Notification of Reasons for Refusal dated Oct. 18, 2022. |
Application No. 10-2020-7024342 Office Action dated Feb. 15, 2024. |
Application No. 201980015974.8 Second Office Action date Nov. 30, 2023. |
Application No. 201980015974.8 First Office Action dated May 23, 2023. |
Application No. 19761523.0 Office Action dated Jan. 17, 2024. |
Application No. 19761523.0 Office Action dated Aug. 1, 2023. |
Application No. 19761523.0 Office Action dated Jan. 18, 2023. |
Application No. 19761523.0 Extended European Search Report dated Aug. 12, 2021. |
Application No. 2020-545245 Non-Final Notification of Reason(s) for Refusal dated Oct. 4, 2022. |
Application No. 10-2020-7024343 Office Action dated Jan. 4, 2024. |
Application No. 19760890.4 Office Action dated Jun. 13, 2023. |
Application No. 19760890.4 Extended European Search Report dated Nov. 10, 2021. |
Application No. 201910110398.7 First Office Action dated Jan. 25, 2024. |
Application No. 202027037125 First Examination Report dated Aug. 5, 2021. |
Application No. 19760493.7 Extended European Search Report dated Sep. 2, 2021. |
Application No. 202027037244 First Examination Report dated Dec. 15, 2021. |
PCT Application No. PCT/US2018/013378 International Preliminary Report On Patentability dated Sep. 3, 2019. |
PCT Application No. PCT/US2018/013378 International Search Report and Written Opinion dated Mar. 8, 2018. |
PCT Application No. PCT/US2018/021197 International Preliminary Report on Patentability dated Sep. 10, 2020. |
PCT Application No. PCT/US2018/021197 International Search Report and Written Opinion dated May 30, 2018. |
PCT Application No. PCT/US2019/015120 International Preliminary Report on Patentability dated Sep. 1, 2020. |
PCT Application No. PCT/US2019/015120 International Search Report and Written Opinion dated Apr. 15, 2019. |
PCT Application No. PCT/US2019/015273 International Preliminary Report on Patentability dated Sep. 1, 2020. |
PCT Application No. PCT/US2019/015273 International Search Report and Written Opinion dated Apr. 23, 2019. |
PCT Application No. PCT/US2019/015124 International Preliminary Report on Patentability dated Sep. 1, 2020. |
PCT Application No. PCT/US2019/015124 International Search Report and Written Opinion dated Apr. 15, 2019. |
PCT Application No. PCT/US2019/015275 International Preliminary Report on Patentability dated Sep. 1, 2020. |
PCT Application No. PCT/US2019/015275 International Search Report and Written Opinion dated Apr. 23, 2019. |
PCT Application No. PCT/US2019/016167 International Preliminary Report on Patentability dated Sep. 1, 2020. |
PCT Application No. PCT/US2019/016167 International Search Report and Written Opinion dated Aug. 26, 2019. |
PCT Application No. PCT/US2019/016180 International Preliminary Report on Patentability dated Sep. 1, 2020. |
PCT Application No. PCT/US2019/016180 International Search Report and Written Opinion dated Apr. 23, 2019. |
PCT Application No. PCT/US2019/016686 International Preliminary Report on Patentability dated Sep. 1, 2020. |
PCT Application No. PCT/US2019/016686 International Search Report and Written Opinion dated Apr. 10, 2019. |
PCT Application No. PCT/US2019/016698 International Preliminary Report on Patentability dated Sep. 1, 2020. |
PCT Application No. PCT/US2019/016698 International Search Report and Written Opinion dated Apr. 11, 2019. |
PCT Application No. PCT/US2019/016694 International Preliminary Report on Patentability dated Sep. 1, 2020. |
PCT Application No. PCT/US2019/016694 International Search Report and Written Opinion dated Apr. 15, 2019. |
PCT Application No. PCT/US2019/017100 International Preliminary Report on Patentability dated Sep. 1, 2020. |
PCT Application No. PCT/US2019/017100 International Search Report and Written Opinion dated Apr. 17, 2019. |
PCT Application No. PCT/US2022/024943 International Search Report and Written Opinion dated Jul. 28, 2022. |
PCT Application No. PCT/US2022/024943 International Preliminary Report on Patentability dated Jan. 11, 2024. |
U.S. Appl. No. 15/448,356 Final Office Action mailed Jul. 28, 2021. |
U.S. Appl. No. 15/448,356 Office Action mailed Apr. 12, 2021. |
U.S. Appl. No. 15/448,356 Final Office Action mailed Oct. 21, 2020. |
Docket No. SIENA-16254 U.S. Appl. No. 15/448,356 Office Action mailed May 28, 2020 |
U.S. Appl. No. 15/448,356 Final Office Action mailed Aug. 6, 2019. |
U.S. Appl. No. 15/448,356 Office Action mailed Jan. 8, 2019. |
U.S. Appl. No. 15/448,356 Final Office Action mailed Aug. 31, 2018. |
U.S. Appl. No. 15/448,356 Office Action mailed Mar. 5, 2018. |
U.S. Appl. No. 15/450,602 Final Office Action mailed Nov. 2, 2018. |
U.S. Appl. No. 15/450,602 Office Action mailed Apr. 6, 2018. |
U.S. Appl. No. 16/681,477 Office Action mailed Mar. 19, 2021. |
U.S. Appl. No. 16/681,477 Final Office Action mailed Nov. 30, 2020. |
U.S. Appl. No. 16/681,477 Office Action mailed Apr. 16, 2020. |
U.S. Appl. No. 15/908,569 Office Action mailed Mar. 27, 2020. |
U.S. Appl. No. 15/908,569 Office Action mailed Jun. 28, 2019. |
U.S. Appl. No. 17/207,679 Office Action mailed Jul. 22, 2022. |
U.S. Appl. No. 15/908,722 Office Action mailed Oct. 30, 2020. |
U.S. Appl. No. 15/908,722 Final Office Action mailed Jun. 12, 2020. |
U.S. Appl. No. 15/908,722 Office Action mailed Jun. 28, 2019. |
U.S. Appl. No. 17/380,373 Office Action mailed Aug. 5, 2022. |
U.S. Appl. No. 15/908,635 Office Action mailed Jun. 28, 2019. |
U.S. Appl. No. 17/080,551 Office Action mailed May 12, 2022. |
U.S. Appl. No. 15/908,531 Office Action mailed Jun. 28, 2019. |
U.S. Appl. No. 17/014,149 Office Action mailed Sep. 29, 2021. |
U.S. Appl. No. 15/908,657 Office Action mailed Jun. 28, 2019. |
U.S. Appl. No. 17/014,182 Office Action mailed Sep. 29, 2021. |
U.S. Appl. No. 15/908,438 Office Action mailed Oct. 3, 2019. |
U.S. Appl. No. 17/000,841 Office Action mailed Sep. 20, 2021. |
U.S. Appl. No. 15/908,345 Office Action mailed Jan. 10, 2020. |
U.S. Appl. No. 17/015,845 Office Action mailed Oct. 6, 2021. |
U.S. Appl. No. 15/908,704 Final Office Action mailed Jun. 12, 2020. |
U.S. Appl. No. 15/908,704 Office Action mailed Jun. 28, 2019. |
U.S. Appl. No. 17/188,544 Office Action mailed Jun. 27, 2022. |
U.S. Appl. No. 18/135,036 Office Action mailed Nov. 24, 2023. |
U.S. Appl. No. 15/908,712 Office Action mailed Aug. 8, 2019. |
U.S. Appl. No. 17/060,458 Office Action mailed Oct. 6, 2021. |
U.S. Appl. No. 15/908,707 Final Office Action mailed Nov. 18, 2019. |
U.S. Appl. No. 15/908,707 Office Action mailed Jul. 17, 2019. |
U.S. Appl. No. 17/080,580 Office Action mailed May 26, 2022. |
U.S. Appl. No. 17/362,416 Final Office Action mailed Aug. 4, 2023. |
U.S. Appl. No. 17/362,416 Final Office Action mailed May 9, 2023. |
U.S. Appl. No. 17/362,416 Final Office Action mailed Feb. 14, 2023. |
U.S. Appl. No. 17/362,416 Office Action mailed Sep. 6, 2022. |
Application No. 201910110365.2 First Office Action dated Mar. 19, 2024. |
Application No. 10-2020-7025084 Office Action dated Apr. 18, 2024. |
Application No. 201980021871.2 Office Action dated Mar. 28, 2024. |
Number | Date | Country | |
---|---|---|---|
20230233947 A1 | Jul 2023 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 17207679 | Mar 2021 | US |
Child | 18130672 | US | |
Parent | 15908569 | Feb 2018 | US |
Child | 17207679 | US |