TWI625150B - Application system for an interaction between fans and a live baseball game - Google Patents

Abstract

The present invention discloses an application system that interacts with a live stadium, and includes a cloud server and an application. The cloud server is a list of players who are registered in one of a plurality of baseball players, and stores baseball history data of one of a plurality of baseball players and fan interaction data of one of a plurality of fans. The application is installed on an electronic device, and the electronic device can be connected to the cloud server, which allows the fans to simulate the attacker, the garrison or the coach who is playing on the field to specifically reach the fans and the stadium. One of the effects of live interaction.

Description

Application system that interacts with the stadium

The following description is about a software application system, especially an application system that can interact with the stadium live.

Baseball is a group ball game in which two teams of at least nine people perform a "batting-running" form in a fan-shaped course. The baseball player is divided into two sides: the attacking party and the defending party. The attacking player uses the bat to hit the ball thrown by the defending pitcher, and then runs along the four bases. When he successfully runs a circle and returns to the home base. A score of 1 is available; the defender uses the glove to catch or throw the ball hit by the attacker to the attacker. In the game, the two teams took turns to attack and defend, and the team with the highest score in the nine games won.

At present, the operators of baseball games are painstakingly trying to attract more fans to enter the stadium to watch the ball. The reason is that the popularity of cable TV, fans can watch the favorite team at home, without special running. Go to the stadium to watch the game. The most direct way is to reduce the cost of tickets to attract the audience, but this way will lead to low income of the operators, and when the income of the operators is low, the overall quality of the baseball game is likely to decline. And make fans even more reluctant to watch this game.

Therefore, the inventors have proposed a novel application system that interacts with the stadium to solve the existing problems.

In view of the above-mentioned problems, the present invention proposes an application system that can interact with the stadium to increase the fun of fans entering the stadium to watch the ball.

In view of the above-mentioned conventional problems, the present invention proposes an application system that can interact with the stadium live to provide an opinion of the fans when they enter their viewing game, and thereby establish relevant baseball history data.

Based on the above objective, the present invention provides an application system for interacting with a stadium, which is suitable for watching a baseball game in a stadium. The baseball game may include an attacker and a garrison. The application system includes a cloud server. And the application. The cloud server is a list of players who are registered in one of a plurality of baseball players, and stores baseball history data of one of a plurality of baseball players and fan interaction data of one of a plurality of fans. The application system is installed on an electronic device, and the application comprises a network connection unit, a stadium live input unit, an attack and defense analog inquiry unit and a result input unit. The network connection unit connects to the cloud server within the stadium to query or update baseball history data or fan interaction data. The stadium live input unit can provide the fans with input of actual offensive and defensive data of one of the current baseball games. The actual offensive and defensive data includes the information of the striker, the information of the pitcher or the defensive position of the defender. The attack and defense party analog query unit can use the network connection unit to query the cloud server for whether there is any data in the baseball history data that meets the striker, the pitcher or the garrison. If there is a match, the striker, the pitcher or the garrison is selected. One, and according to one of the selected strikers, pitchers, or garrisons, the relative combatant's strike strategy, the defensive defensive strategy, or the pitcher's ball-matching strategy are provided in the historical data of the baseball. The result input unit is for the fans to input the selected strike strategy, defensive strategy or ball-matching strategy, and is uploaded to the cloud server by the network connection unit. After a time interval, the cloud server updates the fan interaction data according to the received strike strategy, defensive strategy, or ball-matching strategy, and updates the baseball history data based on the results of the baseball game.

Preferably, the application further comprises a fan interaction unit, and the fan interaction unit provides an interaction interface including the first identity of the striker and the second identity of the pitcher, and the first identity and the second identity are selected by the fan and the other fan respectively. When the fans choose the first identity, the fans choose one of the strike strategies. When the fans choose the second identity, the fans choose one of the ball-matching strategies.

Preferably, after the fan and another fan select one of the strike strategies and one of the ball-matching strategies, the fan interaction unit may display one of the strike strategies and one of the ball-matching strategies to the fans and the other. One of the fans' electronic devices on the screen.

Preferably, one of the strike strategies selected by the fan and another fan and one of the ball-matching strategies are uploaded to the cloud server via the network connection unit, and the fan interaction data is updated.

Preferably, the strike strategy includes hits, shorts, longs, high flying sacrifices or sacrificial strikes. The ball strategy includes a straight ball, a sliding ball, a curved ball, a bad ball, a touch ball, a butterfly ball or a finger ball.

Preferably, the application further includes a coach simulation unit that provides the fan selection of the coaching identity, the defensive coaching identity, or the pitcher coaching identity of the baseball player, and provides the ability to combat coaching, defensive coaching, or pitcher coaching. The strategy that identity should adopt.

Preferably, the strategy of combating the identity of the coach includes long strokes, high flying sacrifices, sacrificial strikes, shorts, hits or swing directions under various ball numbers. The strategy of defending the coach status includes predicting the fall of the striker after hitting the ball. As well as the scope of the proposed garrison, the strategy of the pitcher's coaching identities may include a ball-matching strategy based on the weakness of the striker.

Preferably, the stadium live input unit, the attack and defense party analog query unit, and the result input unit are displayed on one of the screens of the electronic device.

Preferably, when the attack and defense party simulation query unit queries the cloud server for the same data in the baseball history data that meets the striker, the pitcher or the garrison, if there is no match, the cloud server obtains the plurality according to the approximate condition. The list of players in the baseball player is selected from the list of hitters, pitchers, or defenders.

Preferably, the approximation conditions include any combination of age, size, strike rate, defensive rate, garrison position, match time or above in accordance with the striker, pitcher or garrison.

Preferably, when the cloud server receives the actual attack and defense data uploaded by the fan, the cloud server performs a data collection process on the actual attack and defense data to update the baseball history data.

The features, the contents and advantages of the present invention, and the advantages thereof, will be understood by the present invention. The present invention will be described in detail with reference to the accompanying drawings, The use of the present invention is not intended to be a limitation of the scope of the present invention, and the scope of the present invention is not limited by the scope and configuration of the accompanying drawings.

The advantages and features of the present invention, as well as the technical methods of the present invention, are described in more detail with reference to the exemplary embodiments and the accompanying drawings, and the present invention may be implemented in various forms and should not be construed as limited thereby. The embodiments of the present invention, and the embodiments of the present invention are intended to provide a more complete and complete and complete disclosure of the scope of the present invention, and The scope of the patent application is defined.

Please refer to FIG. 1, which is a schematic diagram of a baseball game according to an embodiment of the present invention. In the present embodiment, the general baseball game 91 is used as an example. In this baseball game 91, only one hitter 9311 can strike on the court 90 at a time, and the hitter 9311 attempts to throw the pitcher 9321. The baseball is hit, and the plurality of players in the garrison 932 are responsible for killing the baseball that was shot, or passing the hitting baseball to the appropriate base bag to assassinate the striker 9311. The application system of the present invention interacting with the stadium can use the schematic diagram of FIG. 1 as an example of the following embodiments, and therefore, the description will be made first.

Please refer to FIG. 2 and FIG. 3 , which are a first block diagram and a second block diagram of an application system for interacting with the stadium according to an embodiment of the present invention, and please refer to FIG. 1 together. In the embodiment, the application system 100 interacting with the stadium can be adapted to view one of the baseball games 91 in the stadium 90. The baseball game 91 can include an attacker and a garrison 932. The application system 100 that interacts with the stadium can include a cloud server 10 and an application 20. The cloud server 10 can be a computer host or a workstation. The application 20 can be a web application and can be installed on a tablet or a smart phone.

The cloud server 10 can log in to the player list 11 including one of a plurality of baseball players, and the cloud server 10 can store one of the plurality of baseball players baseball history data 12 and one of the plurality of fans' fan interaction data 13. In detail, the baseball history data 12 may be related sports data of each baseball player's baseball career, such as strike rate, good defensive position, left (right) hitter, good pitching type, etc., and may also include different blows. Strategy 14, defensive strategy 15 and a pitching strategy 16 currently available to a pitcher 9321.

The application 20 is mounted on an electronic device 94, wherein the electronic device 94 can be a tablet or a smart phone. The application 20 can include a network connection unit 21, a stadium live input unit 22, an offensive and defensive simulation query unit 23, and a result input unit 24, respectively, as described below.

The network connection unit 21 is used to connect to the cloud server 10 in the stadium 90 to query or update the baseball history data 12 or the fan interaction data 13. In detail, the stadium 90 can set up multiple wireless routers. The network connection unit 21 is responsible for connecting to the wireless routers, and then connecting the wireless routers to the cloud server 10 to ensure that the application 20 can only be connected within the stadium 90 and logged into the cloud server 10. on.

The stadium live input unit 22 provides the actual attack and defense data 221 input by the fan on the electronic device 94 to the current baseball game 91. The actual attack and defense data 221 may include the information of the striker 9311, the information of the pitcher 9321, the defensive position of the defender 932, or It is the result of the game. In more detail, the information of the hitter 9311 may include the identity information of one of the striker 9311, the type of hitting the hit and the type of hitting, etc., and the information of the pitcher 9321 may include the identity information of the pitcher 9321. The type of pitching that is thrown by him and the number of balls he throws when facing the striker 9311, and so on.

The attack and defense party simulation query unit 23 can use the network connection unit 21 to query the cloud server 10 whether the stored baseball history data 12 has data corresponding to the striker 9311, the pitcher 9321 or the garrison 932. If there is a match, then Select one of the striker 9311, the pitcher 9321 or the garrison 932, and according to one of the selected striker 9311, the pitcher 9321 or the garrison 932, the striker 9311 is matched against the baseball history data 12 Strategy 14, defensive strategy 15 of the garrison 932 or the ball tactic 16 of the pitcher 9321. The result input unit 24 is available for the fan to input the selected strike strategy 14, the defensive strategy 15 or the match strategy 16 and is uploaded to the cloud server 10 by the network connection unit 21.

In other words, the attack and defense party simulation query unit 23 allows the fans to simulate themselves as players who are playing in the game. For example, if the pitcher currently playing on the field is Wang Daming, the fan can use the attack and defense party simulation query unit 23 to query whether the cloud server 10 has the data of the Wang Daming player. When the match is met, the screen of the electronic device 94 is displayed. You can display all the ball-matching strategies of Wang Daming players, let the fans choose.

On the other hand, if the player in the baseball game 91 is not registered in the cloud server 10, the attack and defense party simulation query unit 23 cannot query the cloud server 10 for the hitter 9311 and the pitcher having the same baseball history data 12. 9321 or garrison 932 information. At this time, the cloud server 10 will select the data corresponding to the striker 9311, the pitcher 9321 or the garrison 932 from the player list 11 of the plurality of baseball players that have been registered according to an approximate condition 17. The approximation condition 17 includes any combination of the age, the size, the strike rate, the defensive rate, the defensive position, the match time or the above of the striker 9311, the pitcher 9321, or the garrison 932. The block diagram is shown in Figure 3.

Preferably, after a time interval, the cloud server 10 can update the fan interaction data 13 according to the received fan's attack strategy 14, the defensive strategy 15 or the ball-matching strategy 16, and according to the actual attack and defense uploaded by the fans. The data 221 is to update the baseball history data 12.

In a preferred embodiment of the present invention, the stadium live input unit 22, the offensive and defensive analog inquiry unit 23, and the result input unit 24 may be displayed on one of the screens of the electronic device 94.

It is worth mentioning that the stadium live input unit 22 and the cloud server 10 can establish a decentralized input attack and defense data 12 mechanism, the purpose of which is to provide different fans to upload the offensive and defensive data of the game in a decentralized manner, and in the cloud. The server 10 performs the rounding. For example, fans can enter various offensive and defensive data and upload them to the cloud server 10 during the game, such as through the stadium or television or other devices, and use a data aggregation mechanism on the cloud server 10 (for example, The mode of the input data is obtained by the fans to share the value of the same offensive and defensive data, and the baseball history data 12 is established.

It should be understood that, in the embodiment of the present invention, the data collection mechanism is implemented by using the mode of the input data, and the purpose is to filter out the incorrect attack and defense data input by a few fans, so that the baseball history data 12 can be presented. Give a correct value. However, the data aggregation mechanism is not limited to the above, and it may also include the average, maximum, minimum or other statistical methods of data presentation.

In addition, the application 20 can be configured to batchly transmit the results of the game and the strike strategy 14, defensive strategy 15 or ball-matching strategy 16 sent by the fans, and when the cloud server 10 receives a batch of multiple fans. When the strike strategy 14, the defensive strategy 15 or the match strategy 16 information, the relevant big data can be calculated. For example, the cloud server 10 can calculate the proportion of the predicted first shot of the pitcher 9321 in the baseball game 91 when facing the striker 9311 as a good ball. It can also be calculated in the baseball game 91. What is the ratio of predicting a strong strike to a hit? By publishing such data, every fan who uploads data can be more integrated into the game, and the team’s operators can also know the expectations of most fans. And then adjust the direction of their decision-making.

Please refer to FIG. 4 and FIG. 5 , which are block diagrams and schematic diagrams of an application system for interacting with the stadium according to another embodiment of the present invention, and please refer to FIG. 1 together. As shown in the figure, the technical features of the cloud server 10 and the application 20 in the application system 100 interacting with the stadium are the same as those in FIG. 1, and it is worth mentioning that in this embodiment, the application 20 can Further comprising a fan interaction unit 25, the fan interaction unit 25 can provide an interactive interface comprising one of the first identity 251 of the current on-the-spot hitter 9311 and one of the second identity 252 of the pitcher 9321.

The fans and a fan can respectively select the first identity 251 and the second identity 252 on the screen of the electronic device 94. If the fan selects the first identity 251, the fan can select one of the strike strategies 14 if When the fans choose the second identity 252, the fans choose one of the ball strategy 16 . The strike strategy 14 may include hits, shorts, longs, high flying sacrifices or sacrificial strikes. The ball strategy 16 may include a straight ball, a slide ball, a curved ball, a bad ball, a touch ball, a butterfly ball or a finger ball. The above-mentioned strike strategy 14 and the ball-matching strategy 16 are implemented by way of example and are not limited thereto.

When the fan and the fan select one of the strike strategy 14 and one of the match strategy 16 , the fan interaction unit 25 may display one of the strike strategy 14 and one of the match strategy 16 to the fan and The fan's electronic device 94 is on the screen. Finally, one of the strike strategies 14 selected by the fans and the fans and one of the ball-matching strategies 16 can be uploaded to the cloud server 10 via the network connection unit 21, and the fan interaction data 13 is further updated.

In other words, the fans on the field and another fan can use this fan interaction unit 25 to simulate one of the hitter 9311 and the pitcher 9321, and the fans can perform this fan interaction unit 25 at rest, thereby enhancing the fans. In this baseball game 91 one of the sense of participation and fun.

Please refer to FIG. 6, which is a block diagram of an application system for interacting with the stadium in accordance with the second embodiment of the present invention, and please refer to FIG. 1 together. As shown in the figure, the technical features of the cloud server 10 and the application 20 in the application system 100 interacting with the stadium are the same as those in the first figure. It is worth mentioning that the application 20 may further include a coach simulation unit. 26, the coaching simulation unit 26 provides the fan selection of a combat coaching identity 261, a defensive coaching identity 262, or a pitcher coaching identity 263 on the baseball game 91, and provides a combat coaching identity 261, a defensive coaching identity 262, or a pitcher coach. The strategy that identity 263 should adopt.

In detail, the coaching simulation unit 26 can be generated on the screen in an interactive interface, and the interactive interface is presented by the application 20, and the interactive interface provides the combat coaching identity 261 on the baseball game 91, the garrison coach. Identity 262 or pitcher coach identity 263, and fans can use the touch to select the coaching identity to choose, and try to simulate the identity of one of the coaches to release the strategy. The strategy of combating coach identity 261 may include long-term, high-flying sacrifices, sacrifice strikes, shorts, hits, or swing directions under various ball numbers. The strategy of defending coach identity 262 may include predicting the hitter 9311 after hitting the ball. The placement of the pitcher and the scope of the proposed defensive, the strategy of the pitcher coaching identity 263 may include a ball-matching strategy 16 based on the weakness of the striker 9311.

It can be known from the above that the application system of the present invention interacting with the stadium can indeed provide the fans with a new experience when watching the game on the stadium. Through the interaction between the fans or the interaction between the fans and the system, the fans can Enjoy a different kind of fun, and the cloud server can aggregate the actual offensive and defensive data uploaded by all fans according to the requirements, and then present a meaningful and correct baseball history data. In addition, the data collected by the cloud server can also be provided to the decision makers for reference of the strategy implementation. Therefore, compared with the prior art, the application system of the present invention interacting with the stadium real thing is novel and progressive, and It can be provided to relevant industries for specific implementation.

The embodiments described above are merely illustrative of the technical spirit and the features of the present invention, and the objects of the present invention can be understood by those skilled in the art, and the scope of the present invention cannot be limited thereto. That is, the equivalent variations or modifications made by the spirit of the present invention should still be included in the scope of the present invention.

100‧‧‧Application system that interacts with the stadium
10‧‧‧Cloud Server
11‧‧‧List of players
12‧‧‧Baseball history data
13‧‧‧fan interaction data
14‧‧‧Beat strategy
15‧‧‧ defensive strategy
16‧‧‧With ball strategy
17‧‧‧ Approximate conditions
20‧‧‧Application
21‧‧‧Network connection unit
22‧‧‧Camp live input unit
221‧‧‧ Actual offensive and defensive data
23‧‧‧ offensive and defensive simulation inquiry unit
24‧‧‧Result input unit
25‧‧‧Fans Interactive Unit
251‧‧‧First identity
252‧‧‧Second identity
26‧‧‧Coach simulation unit
261‧‧‧Combat coaching status
262‧‧‧ Guardian identity
263‧‧‧Pitcher coaching status
90‧‧‧ Stadium
91‧‧‧ baseball game
9311‧‧‧Batterers
932‧‧‧ Guardian
9321‧‧‧Player
94‧‧‧Electronic devices

The above and other features and advantages of the present invention will become more apparent from the detailed description of the exemplary embodiments thereof. 2 is a first block diagram of an application system that interacts with the stadium in accordance with an embodiment of the present invention. Figure 3 is a second block diagram of an application system that interacts with the stadium in accordance with an embodiment of the present invention. Figure 4 is a block diagram of an application system that interacts with the stadium in accordance with another embodiment of the present invention. Figure 5 is a schematic diagram of an application system that interacts with the stadium in accordance with another embodiment of the present invention. Figure 6 is a block diagram of an application system that interacts with the stadium in accordance with a second embodiment of the present invention.

Claims (10)

An application system capable of interacting with the stadium, suitable for watching a baseball player in a stadium. The baseball game includes an attacker and a garrison. The application system includes: a cloud server, which is a plurality of login servers. a list of players of a baseball player, and stores baseball history data of one of the plurality of baseball players and fan interaction data of one of the plurality of fans; and an application installed on an electronic device, the application comprising: a network The connection unit is connected to the cloud server in the stadium to query or update the baseball history data or the fan interaction data; a stadium live input unit provides the fan to input the actual attack and defense data of one of the current baseball games. The actual attack and defense data includes a hitter's data, a pitcher's data, or the defensive position of the defender; an attack and defense party simulation query unit uses the network connection unit to query the cloud server for the baseball history Whether there is any data in the data that meets the striker, the pitcher or the garrison. If there is a match, then One of the striker, the pitcher, or the servant, and one of the striker, the pitcher, or the servant selected to provide the baseball historical data in accordance with one of the striker's strike strategies a defensive strategy of the garrison or one of the pitching strategies of the pitcher; and a result input unit for the fan to input the selected strike strategy, the defensive strategy or the match strategy, and the net The road connection unit uploads to the cloud server; after a time interval, the cloud server updates the fan interaction data according to the received strike strategy, the defensive strategy or the ball-matching strategy, and receives the The actual offensive and defensive data uploaded by the fans to update the baseball history data. For example, the application system that can interact with the stadium lively according to item 1 of the patent application, wherein the application further comprises a fan interaction unit, the fan interaction unit provides a first identity including one of the strikers and a second identity of the pitcher One of the interactive interfaces, and the fan and the other fan respectively select the first identity and the second identity. When the fan selects the first identity, the fan selects one of the strike strategies when the When the fans choose the second identity, the fan selects one of the ball-matching strategies. An application system that can interact with the stadium lively according to item 2 of the patent application scope, wherein the fan and the other fan select one of the strike strategies and one of the ball-matching strategies, the fan interaction unit will One of the strike strategies and one of the ball-matching strategies is displayed on one of the electronic devices of the fan and the other fan. An application system that can interact with the stadium lively according to item 2 of the patent application, wherein one of the blow strategy selected by the fan and the other fan and one of the ball-matching strategies is connected via the network The line unit uploads to the cloud server and updates the fan interaction data. For example, the application system of the second part of the patent application can interact with the actual situation of the stadium, wherein the attack strategy includes hitting, short-scoring, long-scoring, high-flying sacrifice or sacrificial strike, and the ball-playing strategy includes a straight ball, a sliding ball, a curved ball, and a bad ball. Ball, touch ball, butterfly ball or finger ball. For example, the application system that can interact with the stadium lively in the first application of the patent scope, wherein the application further comprises a coach simulation unit, which provides the fan to select one of the baseball players to combat the coach identity, a garrison The coach status is either a pitcher coach and provides the strategy to combat the coaching identity, the identity of the garrison coach, or the identity of the pitcher coach. For example, the application system that can interact with the stadium lively according to item 6 of the patent application scope, wherein the strategy for combating the identity of the coach includes long strokes, high flying sacrifices, sacrifice strikes, shorts, hits or swing directions under various ball numbers. The defensive coaching strategy includes predicting the location of the hitter after hitting the ball and the scope of the proposed garrison. The strategy of the pitcher's coaching identity includes a ball-matching strategy based on the weakness of the striker. For example, the application system that can interact with the stadium lively according to item 1 of the patent application, wherein the stadium live input unit, the attack and defense party simulation query unit, and the result input unit are displayed on one screen of the electronic device. An application system that can interact with the stadium lively according to the first aspect of the patent application, wherein the attack and defense party simulation query unit queries the cloud server whether the baseball history data meets the striker, the pitcher, or the servant In the case of the same information, if there is no match, the cloud server selects the information corresponding to the striker, the pitcher or the servant from the list of players of the plurality of baseball players according to an approximate condition. An application system that can interact with the stadium lively according to the first aspect of the patent application, wherein when the cloud server receives the actual attack and defense data uploaded by the fan, the system performs a data aggregation process on the actual attack and defense data to update the Baseball history data.