KR102236051B1 - Method for sharing betting details and server therefor - Google Patents

Abstract

According to an embodiment, a method for sharing bet details between users in a betting game for predicting a result of an actual sports match, comprising the steps of: receiving a bet list request from a first user from a user terminal; Generating a bet list including at least one bet detail made by a first user and transmitting the bet list to a first user terminal; Receiving a request for sharing the bet details to be shared among at least one bet details from the first user terminal; Generating a bet history viewing area corresponding to the bet history to be shared; And registering the bet history viewing area in a preset area, wherein the bet history viewing area includes an identifier of the first user, a betting history identification icon, and betting information on the betting history to be shared, and the betting information is a betting game A method for sharing bet details may be provided, further comprising at least one of a type, a total odds, a hit status, and a title.

Description

How to share bet details and the server {METHOD FOR SHARING BETTING DETAILS AND SERVER THEREFOR}

The present disclosure relates to a betting history sharing method and server, and in a betting game that predicts the actual sports match results in more detail, in a betting history sharing method and server that allows a user to share their betting history with other users. About.

A betting game such as Toto or Proto is a game that predicts a result before a game is held for an athletic event, and receives dividends by ranking according to the game result (winning result). Types of betting games include winning, losing, and losing in athletics, scoring, scoring games, mixed games, special games that match winners, ranks, and scorers, and specific games. There are recordable games that match the record of various matches such as the score of the player, the scorer, and the winner.

Betting games are active both offline and online. In online betting games, users use virtual goods to bet on the result of an actual match and receive a dividend in virtual goods according to the match result. Online betting games are made of virtual goods, not real goods, so they have the advantage of being less burdened and easier to access compared to offline methods.

In online or offline betting games, whether or not to win is decided according to the results of the actual match, so the overall situation of the match and league such as the performance of the club the user bet on, the condition and performance of the players participating in the match, and the match between clubs, etc. It is important. However, it is difficult for a general user to grasp all the information that can be considered when placing a bet, and even if a lot of information is provided to a general user, it is very difficult to place a bet by analyzing the information. In some cases, betting game companies provide information about the odds per team to users participating in the game. However, there is a problem in that a general user can increase the hit rate for a betting game based on the odds alone, and as a result, newly introduced users cannot enjoy the betting game for a long time, and the number of users gradually decreases. In addition, since the content provided in the betting game is limited, there is a problem that a user with a high level of knowledge other than a general user quickly loses interest.

Therefore, there is a need for a new method that can increase the interest of users playing betting games and increase the sustainability of the betting game.

Korean Patent Publication No. 10-2010-0001466

An object of the present disclosure is to provide a method and a server for sharing betting details that can increase the interest of users playing online betting games and increase the sustainability of the betting game.

According to an embodiment, a method for sharing bet details for sharing bet details among users, the method comprising: receiving a bet list request from a first user from a user terminal; Generating a bet list including at least one bet detail made by a first user and transmitting the bet list to a first user terminal; Receiving a request for sharing the bet details to be shared among at least one bet details from the first user terminal; Generating a bet history viewing area corresponding to the bet history to be shared; And registering the bet history viewing area in a preset area, wherein the bet history viewing area includes an identifier of the first user, a betting history identification icon, and betting information on the betting history to be shared, and the betting information is a betting game A method for sharing bet details may be provided, further comprising at least one of a type, a total odds, a hit status, and a title.

According to an embodiment, the bet list request is made through a bet list request area of a screen input from the first user terminal, and the bet list request area may be in at least one of a chat area and a bulletin board area.

According to an embodiment, when the bet list request is made within the chat area, registering the bet history viewing area in the preset area may be performed by registering the bet history viewing area in the chat log area included in the chat area.

According to an embodiment, after the step of registering a bet history viewing area in a preset area, receiving a bookmark request signal for a sharing target bet history from a first user terminal or a second user terminal; And registering a bet history viewing area corresponding to the shared bet history in the bookmark area of the user account that has transmitted the bookmark request signal, wherein the bookmark area is included in the chat area and is an area separated from the chat log area. I can.

According to an embodiment, after all the matches included in the sharing target bet history have ended, the step of updating the hit status included in the bet history viewing area in the chat log area and the bookmark area may be further included.

According to an embodiment, the step of generating the bet history viewing area includes: when a bet list request is made within the chat area, the content displayed through the bet history viewing area is generated in a form that is distinct from the general message in the chat log area. It may be provided a method for sharing bet details comprising a step.

According to an embodiment, registering the bet history viewing area in the preset area includes registering the bet history viewing area in the post list area included in the bulletin board area when a bet list request is made through the bulletin board area. I can.

According to an embodiment, upon receiving a request signal through the bet details viewing area from a first user terminal or a second user terminal, transmitting bet information included in the share target bet details to the user terminal that has transmitted the request signal. It may contain more.

According to an embodiment, as a betting history sharing server for sharing betting details, receiving a bet list request from a first user terminal, generating a bet list including at least one bet details placed by the first user, and placing a bet A communication unit that transmits the list to the first user terminal and receives a request for sharing the bet details to be shared among at least one bet details from the first user terminal; And a control unit that creates a bet history viewing area corresponding to the bet history to be shared, and registers the bet history viewing area in a preset area, wherein the bet history viewing area is an identifier of the first user, a bet history identification icon, and a target to be shared. A bet history sharing server may be provided that includes betting information on betting details, and the betting information further includes at least one of a betting game type, a total odds rate, a hit status, and a title.

According to an embodiment, the bet list request is made through a bet list request area of a screen input from the first user terminal, and the bet list request area may be in at least one of a chat area and a bulletin board area.

According to an embodiment, when the communication unit receives a request for a bet list made in the chat area, the control unit registers the bet history viewing area in the chat log area included in the chat area to register the bet history viewing area in a preset area. have.

According to an embodiment, after the control unit registers the bet details viewing area within a preset area, when the communication unit receives a bookmark request signal for the share target bet details from the first user terminal or the second user terminal, the control unit receives the bookmark request signal. A bet history viewing area corresponding to the sharing target bet history is further registered in the bookmark area of the user account that transmits the message, and the bookmark area may be included in the chat area and may be a separate area from the chat log area.

According to an embodiment, the control unit may update the hit status included in the bet history viewing area in the chat log area and the bookmark area after all matches included in the sharing target bet history have ended.

According to an embodiment, when a request for a bet list is made within the chat area, the controller may generate a content displayed through the bet history viewing area in a form that is distinguished from a general message in the chat log area.

According to an embodiment, when the bet list request is made through the bulletin board area, the controller may register the bet history viewing area in the post list area included in the bulletin board area.

According to an embodiment, when the communication unit receives a request signal through the bet details viewing area from the first user terminal or the second user terminal, the control unit transmits bet information included in the share target bet details to the user terminal that has transmitted the request signal. The communication unit can be controlled to transmit.

According to an embodiment, a computer-readable recording medium storing a computer program for performing a method of sharing bet details may be provided.

The method for sharing bet details and the server according to an embodiment may induce interest of users by providing new content to a betting game. In addition, the method for sharing bet details and the server according to an embodiment allows the user to provide his or her bet details to other users, as well as to activate the community in the betting game by checking the betting details of other users, Users can obtain more various information related to betting.

1 is a conceptual diagram of an online betting system according to an embodiment.
2 is a flowchart of a method for providing a betting game according to an embodiment.
3 and 4 are flowcharts illustrating a method of sharing bet details according to an embodiment.
5 to 10 are conceptual diagrams for explaining a process of sharing bet details through a chat area using a method of sharing bet details according to an embodiment.
11 is a flowchart of a method for sharing bet details according to another embodiment.
12 to 14 are conceptual diagrams for explaining a process of registering a bet history viewing area in a bookmark area using a bet history sharing method according to an exemplary embodiment.
15 to 20 are conceptual diagrams illustrating a process of sharing bet details through a bulletin board area using a method for sharing bet details according to an embodiment.
21 is a block diagram of a betting history sharing server according to an embodiment.

Hereinafter, exemplary embodiments will be described in detail with reference to the accompanying drawings. Here, repeated descriptions, well-known functions that may unnecessarily obscure the subject matter, and detailed descriptions of configurations are omitted. The embodiments are provided to more completely explain the present disclosure to those with average knowledge in the art. Accordingly, the shapes and sizes of elements in the drawings may be variously provided for clearer description.

Embodiments of the present disclosure may be represented by functional block configurations and various processing steps. Some or all of these functional blocks may be implemented with various numbers of hardware and/or software components that perform specific functions described in the present disclosure. For example, the functional blocks of the present disclosure may be implemented by one or more microprocessors, or may be implemented by circuit configurations for a predetermined function. In addition, for example, the functional blocks of the present disclosure may be implemented in various programming or scripting languages. Functional blocks may be implemented as an algorithm executed on one or more processors. In addition, the present disclosure may employ conventional techniques for electronic environment setting, signal processing, and/or data processing.

Further, the connecting lines or connecting members between the components shown in the drawings are merely illustrative of functional connections and/or physical or circuit connections. In an actual device, connections between components may be represented by various functional connections, physical connections, or circuit connections that can be replaced or added. The connection between each component can be connected through a wireless network as well as a direct, physical, and circuit connection.

In addition, terms such as "... unit" and "module" described in this specification mean a unit that processes at least one function or operation, which may be implemented as hardware or software or a combination of hardware and software. have. The "unit" and "module" are stored in an addressable storage medium and may be implemented by a program that can be executed by a processor.

For example, "sub" and "module" refer to components such as software components, object-oriented software components, class components, and task components, processes, functions, properties, and programs. It can be implemented by procedures, subroutines, segments of program code, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays and variables.

1 is a conceptual diagram of an online betting system 1000 according to an embodiment. The online betting system 1000 according to an embodiment includes a plurality of user terminals 10 and 20, a betting game server 30, and a betting history sharing server 100. Here, the betting game server 30 and the betting history sharing server 100 are configured by function to help understanding, and the embodiments implemented in the betting game server 30 and the betting history sharing server 100 are single It may be implemented as a configuration of or more subdivided configurations. In addition, although the user terminals 10 and 20 in FIG. 1 are shown as laptop computers, this is only an example and may be implemented as a personal computer (PC) or a portable terminal such as a smart phone or a tablet PC.

The betting game server 30 functions to provide a betting game to a plurality of users. For example, the betting game server 30 may transmit game information about games to be opened in the future to the plurality of user terminals 10 and 20 based on the current time. Here, the match information for the matches may be classified for each sport and the league to which the match belongs, and the match information may include a match start time, betting game information for each match, odds for each betting game, and the like. In general, betting games (or online betting games) are not only games of winning, losing, and losing of athletic games, but also scoring and consequent scores, and a mixture of them. There are a variety of games such as games, special games that match the winners, ranks, and scorers, and record games that match the records of various games such as the score of a specific match, scorers, and winners. The betting game server 30 calls game information for matches for each of a plurality of sports or leagues according to an administrator's input or through communication with an external server, and calls this information at the request of users (1, 2). Can be transmitted to the user terminals 10 and 20.

Users 1 and 2 may check game information provided by the betting game server 30 through their user terminals 10 and 20, and enjoy a betting game according to the game information.

As described above, the online betting game has a problem in that the hit rate of general users is low and the content is limited, so that users can quickly lose interest in the betting game. Online betting games are less burdensome than offline betting games, so it is easy to attract new users. However, there is a problem that the number of users gradually decreases because it is difficult for newly introduced users to enjoy betting games for a long time due to the above-described reasons. In order to solve this problem, the online betting system 1000 according to an embodiment further includes a betting history sharing server 100 capable of providing new content to a betting game.

The bet details sharing server 100 functions to share bet details between users 1 and 2. Here, the bet details may be defined as an object indicating how the user (1, 2) made a bet, and such bet details may be composed of bet information of various attributes. For example, the bet information may be defined as information including at least one of a game bet by a user, a type of game used for betting, a purchase date and time, a bet amount, odds, a total odds, an expected winning amount, and a hit status.

When all the betting information included in each betting history matches the actual game result, the users 1 and 2 may receive the dividend amount according to the betting result to their account through the betting game server 30. For example, among users participating in the online betting game, the first user 1 may play the betting game by predicting the result of one or more matches per bet. The betting details may include details of betting with one or more games for one or more games bet by the users 1 and 2. Here, there may be a situation where the first user 1 wants to disclose the details of his bet to other users.

To this end, the bet details sharing server 100 according to an embodiment provides a function for the users 1 and 2 to disclose their bet details to other users. In addition, when sharing bet details has to go through a complicated method, users may not use the sharing function due to the complexity. Therefore, the bet history sharing server 100 can provide a function of sharing information between users (1, 2) such as chat rooms and bulletin boards in a game platform that users can easily access, and bet history with little effort in chat rooms and bulletin boards. Make it possible to share. In particular, the chat room can be accessed from various screens as well as the main screen for communication between users (1, 2), and the bet history sharing server 100 bets a number of chat rooms arranged on a number of and various screens. By selecting a location for sharing the details, it is possible to increase the convenience of users (1, 2) who wish to be provided with a sharing function of the bet details.

In another embodiment, the bet history sharing server 100 may further provide hit information of a user (hereinafter, referred to as a first user) who wishes to share the bet history to other users. Users who want to refer to the bet details may check the hit information of the first user who registered the bet details together when inquiring the bet details. Here, the hit information of the first user 1 may be cumulative information on the result obtained by betting by the first user, and users who want to refer to the bet details may first determine the accuracy of the prediction of the bet details shared by the first user. The user's hit information can be used as an objective criterion for betting. Accordingly, even users who lack knowledge about games or betting can increase the winning rate of bets by considering the first user's hit information and objective information about the game.

When the bet history sharing function is provided through the betting history sharing server 100 as described above in the online betting game, even a general user with little knowledge of the games, betting history shared among users or shared by a specific user Through the confirmation of, the result of the actual game can be predicted with a higher probability. In addition, when sharing the bet details, the first user's hit information may be provided to the users, so that the users can place a bet with a higher probability of winning by using the first user's hit information.

In addition, according to an embodiment, since users' betting details may be provided through a chat room or a bulletin board, users can check other users' betting details in a chat room or bulletin board that is visited at a high frequency, which is a user who enjoys betting games. It can increase the residence time of the children. In addition, through the sharing of betting details, users can share their opinions on the shared betting details, thereby increasing interest in betting games, activating the community, and further increasing the utilization of chat rooms and bulletin boards.

As such, the betting history sharing server 100 according to an exemplary embodiment may provide content that users with high knowledge or high hit rate can feel interest as well as general users. Now, a method for providing a betting game and a method for sharing bet details through the online betting system 1000 or the betting details sharing server 100 according to an embodiment will be further described with reference to FIGS. 2 to 20. The online betting system 1000 or the betting details sharing server 100 according to an embodiment may provide a process of providing a betting game to a user and a process of assisting in sharing bet details between users.

2 is a flowchart of a method for providing a betting game according to an embodiment.

First, the betting game server 30 may transmit game information to the first user terminal 10, and information on the odds, total odds, and expected winning amount according to the user's bet input through the first user terminal 10. Can be transmitted to the user terminal 10. Here, the total odds are a value determined according to the odds of a bet selected by the user and the number of bets, and may be defined as the product of the odds of the betting game bet by the user. For example, if the first user places a bet on two betting games, and the odds of each betting game bet by the user are 1.5, the total odds are 1.5 * 1.5 = 2.25.

As the first user 1 proceeds with the betting game, a step (S10) of making a bet request to the betting game server 30 through the first user terminal 10 is performed. When requesting a bet through step S10, the first user terminal 10 sends the betting game server 30 to the user's identifier (eg, account ID, unique identification code, etc.), bet amount, game type, etc., Various information indicating which user has bet, which game has bet, which game type has been used, and how much has bet can be transmitted.

Step S21 is a step of determining whether the betting game server 30 has received a bet request from the user terminals 10 and 20. As a result of the determination, when a bet request is received from the user terminals 10 and 20, step S22 is performed, and if not, step S25 is performed. Hereinafter, for convenience of explanation, it is assumed that a bet request is received from the first user terminal 10.

Step S22 is a step of generating bet details according to the information received through step S10, step S23 is a step of allocating the bet details to the account of the first user 1, and step S24 is from the holding amount of the first user. This is the step of deducting the bet amount. In addition, when generating the bet details in step S22, the betting game server 30 stores information received from the first user terminal 10 in step S21 and hit information (eg, prediction accuracy) of the first user. Including, you can create a bet history.

Step S25 is a step of determining whether all matches included in the betting details have ended. As a result of the determination, when all the matches are over, step S26 is performed. Otherwise, step S21 is performed.

Step S26 is a step of determining whether the bet details and the actual match result of the matches match. If all the betting details are the same as the actual match result (that is, if the user hits all the match results), step S27 is performed, and if not, step S21 is performed.

Step S27 is a step of adding at least a portion of the winning amount to the holding amount of the first user 1 (for example, the account of the first user 1). For example, step S27 may be performed by adding the entire winning amount or the remaining amount of the winning amount excluding fees to the holding amount of the first user 1.

In the above description, step S26 has been described as being performed after the end of all matches. However, this is only an example, and step S25 can be accomplished by determining whether to end in one game unit, and step S26 is performed by determining whether the actual game result is hit in one game unit determined to have ended through step S25. I can. In this case, after step S26, a step of determining whether the match of all matches included in the bet history has ended may be further included, and in step S27, after the step of determining whether the match of all matches included in the betting history has ended, the bet history It can be performed according to whether or not the betting games included in the hit.

3 and 4 are flowcharts illustrating a method of sharing bet details according to an embodiment. The method for sharing bet details according to an embodiment may be performed by the bet details sharing server 100, and serves to provide sharing or disclosure of betting details between users using a chat room or a bulletin board in a game platform. To this end, the method of sharing bet details may be divided into a process of registering the bet details in a chat room or a bulletin board, and a process of providing the bet details to a user who has requested the bet details according to the request of the first or second user. In the following description, it is assumed that a first user among a plurality of users requests to share bet details, and a process of registering bet details in a chat room or a bulletin board will be first described with reference to FIG. 3.

Step S31 is a step of requesting a bet list including the bet details of the user 1 to the bet details sharing server 100 according to a request from the first user 1 by the first user terminal 10. Step S31 may be performed by the first user 1 through an input through a bet list request area existing in the game platform. In one embodiment, the bet list request area may be located in the chat area and the bulletin board area in the game platform. That is, the first user 1 may request his own bet list by chatting through the chat area or by using the bet list request area in the chat area or the bulletin board area while writing a post on the bulletin board.

Step S110 is a step of determining whether the bet history sharing server 100 has received a request for a bet list from any one of the plurality of user terminals 10 and 20. As a result of the determination, when a request for a bet list is received from any one user terminal (for example, the first user terminal 10), step S120 is performed, and if not, step S130 is performed.

Step S120 is a step of creating a bet list by searching for betting details of a user (for example, the first user 1) requesting a bet list from a storage unit (not shown) and listing the searched bet details. Here, in step S120, bet details may be included in the bet list according to a preset condition, which is performed regardless of whether or not the bet details are hit. Of course, in step S120, a bet list may be generated by filtering the failed bet details, the bets details past a preset period, and the like according to the user's setting.

The bet list may be included in the bet list screen. The bet list screen may be arranged line by line as one bet detail unit. For example, the bet list screen may display betting information such as game type, purchase date and time, bet amount, odds, expected winning amount, hit status, etc. as a single bet history unit, and each bet according to the user's manipulation. More detailed betting information related to the details may be further displayed. In addition, the bet list screen may further include a first search area, and a bet history matching a user's desired condition may be searched through a search function provided in the first search area. The bet list screen may be generated based on the bet list in the bet history sharing server 100 or the user terminals 10 and 20.

Step S125 is a step of transmitting the bet list generated through step S120 to the first user terminal 10.

The first user 1 checks the bet list or the bet list screen through the first user terminal 10, and selects the bet details to be shared to be shared by the first user 1. Here, the sharing target bet details may be defined as betting details shared by the users 1 and 2. In step S32, a step of requesting the first user 1 to share the bet details selected as the bet details to be shared to the bet details sharing server 100 is performed. Here, the bet list screen has a share request area for the share target bet details, and the first user 1 may perform a request by inputting through the share request area.

Step S130 is a step of determining whether the bet details sharing server 100 has received a request for sharing the bet details to be shared from any one of the plurality of user terminals. As a result of the determination, when a request for sharing the bet details to be shared is received from any one of the user terminals, step S140 is performed, and if not, step S160 or S180 is performed. In this example, since it is assumed that the first user terminal 10 requests to share the betting details to be shared, step S140 may be performed.

In step S140, the bet history sharing server 100 generates a bet history viewing area corresponding to the bet history to be shared, and in step S150, the bet history sharing server 100 registers the bet history viewing area in a preset area. Step.

In one embodiment, the bet history viewing area may be defined as an area for displaying the bet history to be shared, and a function such as a hyperlink may be provided in the bet history viewing area. For example, if the first user (1) or another user (for example, the second user (2)) selects the bet history viewing area (for example, click or touch, etc.), the user who entered the bet is bet The bet details corresponding to the details viewing area may be exposed in the form of a new window, or the current screen may be moved to a screen including the bet details. In the following, a screen created or moved according to a view request from the first user 1 or the second user 2 is referred to as a bet detail screen.

The preset area may be a chat area or a bulletin board area. Specifically, the preset area may be a chat log area of a chat room or a post list area of a bulletin board. As described above, the share target bet details may be shared with other users through a chat room or a bulletin board, and the share location of the share target bet details will be determined according to the location requesting the bet list in the game platform through step S31. I can. For example, when the step S31 is made in the chat area in the game platform, the preset area is a chat log area, and when the step S31 is made in the bulletin board area in the game platform, the preset area may be a post list area.

First, it is assumed that step S31 is made in the chat area. When step S31 is made in the chat area, step S140 may further include extracting information to be exposed to other users from the betting information on the bet to be shared. In general, chat rooms within a game platform are relatively narrow. When all the betting information on the betting history to be shared is displayed in the chat room, most of the chat log area of the chat room is covered by the betting history viewing area, and thus the chat function, which is a unique function of the chat room, may be degraded. Accordingly, the step S140 may generate a bet history viewing area by extracting some of the bet information included in the sharing target bet history without including all of the bet information on the betting history to be shared in the betting history viewing area. In one embodiment, the bet history viewing area may indicate an identifier of the first user 1, a bet game type, a total odds rate, and a hit status.

In addition, step S140 may include adding a bet history identification icon in the bet history viewing area so that the users 1 and 2 can easily distinguish between the general chat and the bet history viewing area in the chat log area. In addition, the step S140 may further include performing an emphasis processing on the content included in the bet history viewing area so that users can distinguish between the general chat and the bet history viewing area in the chat log area. Here, the highlighting process may be performed by differentiating the color, size, thickness, underline, shadow, background color, etc. of the content included in the bet history viewing area and the general message included in the chat log area. In addition to the above-described method, various other methods may be further applied to the emphasis processing. The generated bet history viewing area may be registered in the chat log area in step S150 and disclosed to other users.

In addition, the users 1 and 2 may request a bet list on the post creation screen accessible through the bulletin board area. In general, the post creation screen includes an area in which a user can input a title and content. Users (1, 2) can write their desired title and content through the areas included in the post creation screen, and add the bet details in the post through the bet list request area included in the post creation screen. You can share your bet details.

In order to provide bet history sharing through a post, if step S31 is made in the bulletin board area, step S140 may further include extracting the title of the post written by the first user 1. Posts can contain a variety of information inside a chat room than in a chat room, so the process of extracting the information described above is not essential. Instead, step S140 may perform the step of extracting the title input by the first user 1. Through this, when the bet history viewing area is in the post list area of the bulletin board, the first user 1's identifier, bet history identification icon, and title may be exposed in the bet history viewing area. The information exposed through the bet history viewing area is not limited to the above, and may be variously changed. When a post registration is requested from the user, a process of registering a post including betting details in the post list area in step S150 is performed.

In addition, even if step S31 is made in the bulletin board area, step S140 further includes the step of adding a bet history identification icon in the bet history viewing area so that users can distinguish between general posts and posts including betting history in the post list area. can do. In addition, as in the example in the chat area, step S140 may further include a step of highlighting the title area for the post including the bet details, that is, the bet details viewing area.

Now, referring to FIG. 4, a description will be given of a process of providing bet details to the user who requested the bet according to the request of the users 1 and 2. In the following description, it is assumed that the second user 2 requests to view the shared bet details registered in a chat room or a bulletin board through the second user terminal 20.

Step S41 is a step of transmitting a request signal to the bet history sharing server 100 by selecting a bet history viewing area registered in a chat room or a bulletin board by the second user terminal 20. As described with reference to FIG. 3, a bet history viewing area corresponding to the bet history to be shared registered by the first user 1 is exposed on the chat room or the bulletin board, and the second user 2 accesses the second user terminal 20. Through this, it is possible to request a view through an input (for example, a touch or a click) for a bet history viewing area. As described above, the content displayed in the bet history viewing area may be different according to the position of the bet history viewing area in the game platform.

Step S160 is a step of transmitting the bet details to be shared, requested through step S41, to the second user terminal 20. In an embodiment, step S160 may be accomplished by generating a bet details screen for the bet details to be shared and transmitting the bet details screen to the second user terminal 20. As described above, the bet details screen may be provided in the form of a new window in the second user terminal 20 or may be provided in the form of page movement.

Step S42 is a step of displaying, by the second user terminal 20, the share target bet details or bet details screen received through the step S160 through the display unit. Through step S42, betting information on the sharing target bet details may be exposed to the second user through the display unit of the second user terminal 20. The amount of betting information exposed through the display may vary, and according to an embodiment, match information such as the date and time of the match, the team participating in the match, the team selected by the user, the odds rate, the number of games selected, the total odds, the purchase amount, the expected winning amount, and the like. It may include at least one of a hit status.

The method for sharing bet details according to an embodiment may assist in sharing bet details among users in a chat room or a bulletin board through the above-described processes. In addition, the method for sharing bet details according to an embodiment may be linked with the betting game server 30 to update a hit status among bet details registered in a chat room or on a bulletin board. For example, in the sharing target bet history registered in a chat room or a bulletin board, the bet information on the hit status may change the status value according to whether the matches included in each share target bet history are ended and whether or not they are hit. For example, if the match included in the share target bet history is before the start, the hit status may be'purchased' or'waiting', and at least one match among the matches included in the share target bet history is If it is finished and the user's prediction is unsuccessful, the hit status may be'Hit failed'.If all matches included in the shared bet history have ended and all predictions by the user are successful, the hit status is'Hit Success 'Can be. In order to update the bet information on the share target bet details, steps S51, S175, and S180 may be further performed.

According to one embodiment, the bet details shared by the user terminals 10 and 20 may represent a bet on a combination of various matches included in the bet details, but according to another embodiment, the match included in the bet details It may include only betting information for some of the games, and whether to share betting information for a certain match may be selected by the users 1 and 2 who wish to share the betting details. According to an embodiment, when only betting information for some games is to be shared, it may be determined that the hit information included in the sharing target bet history is hit information for each match.

Step S51 is a step of transmitting a hit status to the betting history sharing server 100 after the end of the betting game server 30 (one match or all games included in the shared bet history).

Step S175 is a step of determining whether a hit status has been received from the betting game server 30 by the bet history sharing server 100. If it is determined that a hit status has been received from the betting game server 30, step S180 is performed, otherwise, the steps described with reference to FIG. 3 are performed again.

Step S180 is a step of updating the betting information included in the sharing target bet details registered in the chat room or the bulletin board, specifically, whether a hit status included in the betting information.

In the above description, steps S51 to S180 are shown to be performed after step S160, but this is only an example, and steps S51 to S180 may be performed at any time among the steps described with reference to FIGS. 3 and 4.

5 to 10 are conceptual diagrams for explaining a process of sharing bet details through a chat area using a method of sharing bet details according to an embodiment. Specifically, FIG. 5 shows an example of a screen provided by the game platform, and FIGS. 6 to 9 are through the user terminals 10 and 20 in the process of the users 1 and 2 sharing their betting details in a chat room. An example of the displayed screens is shown, and FIG. 10 shows an example of a screen displayed through the user terminals 10 and 20 of the users 1 and 2 requesting to view the bet details to be shared. The screens described below may be generated by the betting game server 30 or the betting history sharing server 100 and transmitted to the user terminals 10 and 20.

5 shows an example of a screen of a game platform displayed through user terminals 10 and 20. In the game platform, the screen includes a menu area mr, a first information area ir ₁ , a second information area ir ₂ , a chat area, and a content area conr. The menu area (mr) is an area used for switching between various contents provided by the betting game server 30 according to an embodiment, and the first information area (ir ₁ ) is selected through the menu area (mr). The second information area ir ₂ is an area indicating information (eg, game ID, holding amount, etc.) of users 1 and 2 who have logged in to the game platform. The content area (conr) is an area in which content within the game platform provided by the betting game server 30 is displayed according to an input to the menu area (mr), and the chat area (chatr) is a chat between users 1 and 2 It is an area that provides a chat room to perform. In an embodiment, even if the users 1 and 2 select various menus through input through the menu area mr and provide various contents to the user, the above-described areas may be disposed at the same location.

6 shows an example of a chat area provided through the online betting system 1000 and displayed through the user terminals 10 and 20 according to an embodiment. The chat area (chatr) includes a chat log area (clr), a message input area (mir), and a first bet list request area (bsr ₁ ).

The message input area (mir) is an area in which users (1, 2) can input a message through an input unit (not shown), and the chat log area (clr) is an area in which messages input by users (1, 2) are displayed. Area. As is known, messages entered by multiple users (1, 2) can be displayed in the chat log area (clr) by line, and each time a new message is added, existing messages in the chat log area (clr) are It is moved upward or downward.

The first bet list request area bsr ₁ is an area for providing users 1 and 2 with their own bet list. When the user (1, 2) _{clicks or touches the first bet list request area (bsr 1} ), the user terminal (10, 20) requests the bet list of the user (1, 2) to the bet history sharing server 100 do. At this time, the bet history sharing server 100 searches the bet details of the user (for example, the first user 1) who requested the bet list from the storage unit (not shown), and the searched bet details and each searched A bet list is created by listing the bet details.

7 and 8 are an example of a bet list screen generated by the bet history sharing server 100 according to a request of the bet list and displayed on the user terminals 10 and 20. The bet list screen may be provided to the users 1 and 2 in the form of a new window on the game platform. The bet list screen may include a first search area (sr ₁ ), a bet list area (blr), a check area (chr), and a detailed information spread area (dr).

The bet list area (blr) is an area in which a bet list generated by the bet history sharing server 100 is displayed. In this example, it is assumed that the user (1, 2) has placed a bet on a win/loss game among a plurality of betting games, and there are three betting details by making three bets. In this case, three bet details may be displayed in the bet list area (blr). In this example, the number of bet details in the bet list generated by the bet history sharing server 100 is shown as three, but this is only an example, and 0, 1, 2, 4, or more, etc. Likewise, it can be changed in various ways according to the number of bets made by the user and a preset condition.

The first search area sr ₁ includes a search condition that a user can input to check some of the bet details that can be shared with other users. The user can check the bet details that match the conditions among the betting details by entering various search conditions. In FIG. 7, it is shown that only the period can be changed in the first search area sr ₁ , but this is only an example, and the search may be performed by various attributes such as game type, purchase date, bet amount, odds, and expected winning amount.

The user can check the bet details displayed in the bet list area (blr), and can check detailed information on each bet details through input through the _{detailed information spread areas (dr 1} to dr _{3 ).}

_{FIG. 8 is when a user inputs a first detailed information spread area (dr 1} ) for a first bet detail in the example of FIG. 7 (eg, clicks a first detailed information spread area (dr ₁ ) or When touching), shows an example of the bet list screen displayed on the user terminal.

Referring to FIG. 8, detailed information on the first bet details is displayed below the first bet details through the input operation of the users 1 and 2. In one embodiment, the bet list screen may include various betting information related to betting details, for example, betting amount, odds rate, total odds rate, expected winning amount, etc. upon request from a user.

In this example, the first bet details assume a situation created by betting on two of the entire matches. In addition, it is assumed that a user bets on a win, a draw, a draw of a loss in the first game, and a bet on a win, a draw, and a win of the loss in the second game. The user can check other bet details by selecting each area included in the bet list screen. Thereafter, the users 1 and 2 may select the bet details to be shared through the input unit (not shown) and request sharing. For example, the user may select the bet details to be shared through the check area (chr), and request sharing of the selected bet details (eg, bet details to be shared) through the share request area (sar). . In this case, the user terminal of the user may request to share the bet details selected by the user (hereinafter, bet details to be shared) to the bet details sharing server 100. Thereafter, the bet history sharing server 100 may create a bet history viewing area corresponding to the bet history to be shared, and register it.

9 shows an example of a chat area (chatr) including a _{bet history viewing area (rr 1} ) registered by the bet history sharing server 100. As shown in FIG. 9, the bet history sharing server 100 may _{register the bet history viewing area rr 1} in the chat log area clr. In addition, the bet history viewing area rr ₁ registered in the chat log area clr may include at least one of a user's identifier, a bet history identification icon, a bet game type, a total odds, and a hit status. As described above, since the width of the chat log area clr is limited, it is not appropriate to include all bet information on the bet details to be shared in the _{bet history viewing area rr 1.} Accordingly, the bet history sharing server 100 extracts only some of the bet information in consideration of the characteristics of the chat log area clr.

In the chat area, the user (eg, the first user 1) who requested the sharing of the bet to be shared, as well as other users (eg, the second user, the third user, etc.) This is the area that can be checked through the user terminal. When any one of the plurality of users (hereinafter, referred to as the second user) _{inputs through the bet history viewing area (rr 1} ), the user terminal of the second user 2 (hereinafter, referred to as the second user terminal 20) ) Transmits a request signal to the bet details sharing server 100, and the bet details sharing server 100 transmits the bet details for the requested sharing target bet details to the second user terminal 20. In one embodiment, the bet details sharing server 100 may transmit a bet details screen to the second user terminal 20.

10 is a diagram illustrating an example of a bet details screen transmitted from the bet details sharing server 100 and displayed through the second user terminal 20. As described above, when the bet details are shared in a chat area, it is difficult to display all of the bet details due to the limitation of the width of the chat area. Accordingly, when the bet details are shared in a chat area, the bet details screen may be displayed through the second user terminal 20 in the form of a new window as shown in FIG. 10. In addition, the bet details screen may include at least one of a bet details, a bet amount, a dividend rate, a total dividend rate, and an expected winning amount.

As described with reference to FIGS. 6 to 10, the betting history sharing server 100 according to an embodiment provides sharing of betting history through a chat room (eg, a chat area). However, in the chat log area in the chat area, each time a new message is added, the content of the past message is moved up or down and disappears from the screen. Of course, if a message is added only up to a certain level, the user can check it with a scroll bar placed on one side of the chat log area, but if a large number of messages are input beyond a certain level, the user can view the bet details that the user wants to check. It can be difficult to find an area. In addition, when more messages are added, the betting history viewing area shared by the first user may disappear from the chat log area. In addition, when the first user registers betting details to be shared before the start of the match, the hit status is displayed only as'purchased' or'waiting'. Due to the nature of the chat area, it is difficult for the bet history viewing area to remain in the chat log area until the end of the match, so it is difficult for other users to know whether or not the shared bet history corresponding to the bet history viewing area is hit. Therefore, the method of sharing bet details according to another embodiment further includes a bookmark area that is separated from a chat area in which a conversation between users occurs, and the betting details shared by the user or betting details shared by other users are stored in the bookmark area. Can be displayed. According to an embodiment, each user may utilize a bookmark area provided for each user.

11 is a flowchart of a method for sharing bet details according to another embodiment. A method of sharing bet details according to another embodiment is substantially the same as in one embodiment, except that a bookmark area is used. Accordingly, FIG. 11 omits the illustration of steps S210 to S250 corresponding to steps S110 to S150 described with reference to FIG. 3. In the following, other embodiments will be described focusing on differences from one embodiment. In addition, it is assumed that the user who requested the bookmark is the second user 2 below.

Step S61 is a step of transmitting a request signal by input manipulation through the bet history viewing area registered in the chat room by the second user terminal 20, and step S260 is the betting history to be shared in the bet history sharing server 100 It is a step of transmitting the bet details for, and step S62 is a step of displaying the bet details for the share target bet details in the second user terminal 20. Steps S61, S260, and S62 are substantially the same as steps S41, S160, and S42 described with reference to FIG. 4, and thus redundant descriptions are omitted.

The second user 2 may select selected as the bet history viewing area desired to be registered as a bookmark, and perform an operation for displaying in the bookmark area. When receiving an operation for requesting a bookmark from the second user 2, the second user terminal 20 may request the bet history sharing server 100 to register the bookmark requested bet history viewing area as a bookmark in step S63. .

In step S270, the bet history sharing server 100 displays the bookmarked bet history viewing area in the bookmark area in the terminal used by the second user 2 (for example, the second user terminal 20). You can register the browsing area. Here, the bookmark area may be located in the chat area, and in this case, it may be located at the top, bottom, or side of the chat log area. However, if the bookmark area is a location that can be displayed together with the chat area, even if it is not included in the chat area, the bookmark area may be displayed in various locations that are distinguished from other information.

Steps S275 and S280 are substantially the same as steps S175 and S180 described with reference to FIG. 4, and thus redundant descriptions are omitted.

As another embodiment, when the second user 2 selects the bet history viewing area desired to be registered as a bookmark, the second user terminal 20 may display the corresponding bet history viewing area in the bookmark area by itself. . That is, without the process of requesting that the bet history sharing server 100 register the bet history viewing area in the bookmark area, the second user terminal 20 displays the bet history viewing area selected to be displayed in the bookmark area when the chat area is activated. You can decide to display it in the bookmark area. In this case, the bet history sharing server 100 may not perform step S270.

12 to 14 are conceptual diagrams for explaining a process of registering a bet history viewing area in a bookmark area using a bet history sharing method according to another embodiment. Since the process of registering the bet history viewing area in the chat log area clr and the areas included in the chat area have been described in detail with reference to FIGS. 6 to 9, the differences will be mainly described below.

The chat area (chatr) includes a chat log area (clr), a message input area (mir), and a first bet list request area (bsr ₁ ). In addition, as shown in FIG. 12, the chat area (chatr) may further include a bookmark area (bmr). The bookmark area bmr is a space for registering bet details of interest to the user, and may be assigned to each user, and may be disposed at the top, bottom, or side of the chat log area clr.

In one embodiment, it is assumed that the user (1, 2) selects the bet history viewing area (rr ₁₂ ) in the chat log area (clr) and performs an operation for registering a bookmark. Here, the operation for registering the bookmark may be performed by various operations, such as drag and drop, and additional input after selecting a bet history viewing area. The user terminals 10 and 20 may perform a bookmark registration request to the bet history sharing server 100 according to a user's manipulation.

13 shows an example of _{the bet history viewing area (rr 22} ) registered in the bookmark area (bmr) through the processing of the bet history sharing server 100. Referring to FIG. 13, it can be seen that _{the bet history viewing area rr 12} in the chat log area clr is registered as the bet history viewing area rr _{22 in the bookmark area bmr.} Since the bookmark area (bmr) is not affected by the user's or other user's message input, even if a large number of messages are added to the chat log area (clr) over time, the user can place a bet registered in the bookmark area (bmr). You can easily check the history viewing areas.

14 shows an example in which a large amount of messages are added to the chat log area clr. The example shown in FIG. 14 assumes a situation in which all matches corresponding to the betting history viewing area included in the bookmark area bmr have ended after a certain period of time has passed since the example of FIG. 13. The bookmark area bmr is an area separated from the chat log area clr. That is, even if a message from a number of users is input in the chat log area (clr), and the message displayed in the chat log area (clr) is constantly changing, the user can share the betting history of interest through the bookmark area (bmr). In addition to being able to easily check at any time, it is also easy to check whether or not the betting history to be shared is hit when all matches are over.

In addition, after the user checks the bet history viewing area (rr ₁₃ ), it may be further added to the bookmark area (bmr). Since the process of registering the bet history viewing area in the bookmark area has been described in detail above, a duplicate description will be omitted.

15 to 20 are conceptual diagrams illustrating a process of sharing bet details through a bulletin board area using a method for sharing bet details according to an embodiment.

15 shows an example of a bulletin board screen provided through a game platform and displayed through a user terminal. The bulletin board screen includes a menu area (mr), a first information area (ir ₁ ), a second information area (ir ₂ ), a chat area (chatr), and a bulletin board area (br). Here, the menu area mr, the first information area ir ₁ , the second information area ir ₂ , and the chat area have been described in detail with reference to FIG. 5, and thus redundant descriptions are omitted.

The bulletin board area (br) is an area that provides a bulletin board for users to write posts or browse other posts. The bulletin board area br may include a post list area lr in which posts are registered and a writing request area wr. The creation request area (wr) is an area used when a user wants to register a new post.

16 shows an example of a post creation screen generated by requesting the creation of a new post by the users 1 and 2 through the writing request area wr. The post writing area includes a classification area in which a category of a post can be determined, a title writing area for inputting a title, a content writing area for inputting content, and a second bet list request area bsr ₂ .

The second bet list request area bsr ₂ is an area for providing their own bet list to the users 1 and 2, similar to _{the first bet list request area bsr 1} described with reference to FIGS. 6 to 9 . When the user (1, 2) _{clicks or touches the second bet list request area (bsr 2} ), the user terminal (10, 20) requests the bet list of the user (1, 2) to the bet history sharing server 100 do. At this time, the bet history sharing server 100 searches for the bet details of the users 1 and 2 requesting the bet list from the storage unit (not shown) and generates a bet list listing.

17 is an example of a bet list screen generated by the bet history sharing server 100 according to a request of a user's bet list and displayed on the user terminals 10 and 20. As described with reference to FIG. 7, the users 1 and 2 may select the bet details to be shared through the bet list screen, and request sharing of the share target bet details through the share request area sar. Since the feature of the method of requesting to share the bet details to be shared through the bet list screen is the same as or very similar to the method using the above-described chat area, a redundant description will be omitted.

18 illustrates an example of a post creation screen to which bet details are added through a request for sharing bet details to be shared. Referring to FIG. 18, a bet breakdown bdr for a share target bet breakdown may be added below the content creation area. The bulletin board is registered on the bulletin board only when the user touches or clicks the writing completion button due to its characteristics. Therefore, the bet history sharing server 100 according to an embodiment does not directly register the bet details for the betting details to be shared on the bulletin board, as shown in FIG. 18, but includes them in the bet details post creation screen. When the user (1, 2) completes the creation of the items included in the post and inputs it through the write complete button, the post including the bet details is registered in the post list area.

19 shows an example of a post list area lr in which a post including bet details is registered through the process described with reference to FIGS. 16 to 18. Referring to FIG. 19, it can be seen that a post registered according to the request of the users 1 and 2 is registered in the post list area lr, and the bet history viewing area rr ₃₁ corresponds to the item of the post. In addition, in the post list area (lr), general posts and posts including betting details may be distinguished through a bet details identification icon. As described above, in the post including the bet details, in addition to the method of using the above bet details identification icon, a method of highlighting the item of the corresponding post may be further adopted. For example, when the second user 2 _{inputs through the bet history viewing area (rr 31} ), as shown in FIG. 20, the first user of the first user 1 requested by the post including the bet details It can be displayed through the terminal 10.

As described with reference to FIGS. 3 to 20, the betting history sharing server 100 according to an embodiment may provide new content that provides sharing of betting details between users to a betting game. As described above, due to its nature, betting games have a high probability of winning only when they have a lot of knowledge about the game, team, and players, and general users with little knowledge may lose interest quickly because the likelihood of winning is low. In addition, even users with a lot of knowledge can quickly lose interest due to the limitations of the content provided by the betting game with only a general betting game.

On the other hand, the bet details sharing server 100 according to an embodiment provides a function of sharing bet details between users using a chat room or a bulletin board. Therefore, even if users do not know detailed information about the match, team, etc., which is the target of the betting game through the chat room or bulletin board, they can comprehensively check other users' betting history and the user's hit history, and thus bet history with high probability of winning. You can check the information about the field and enjoy the betting game. In addition, since betting details are shared through a chat room or bulletin board through which users can exchange opinions, there is an advantage in that a community between users can be activated more and the access time of users can be increased.

21 is a block diagram of a bet history sharing server 100 according to an embodiment. The betting details sharing server 100 according to an embodiment may perform a function of providing sharing of betting details between the first user 1 and the second user 2. To this end, the bet history sharing server 100 according to an embodiment may include a communication unit 110 and a control unit 120. In addition, in the following description, portions overlapping with those mentioned above will be omitted.

The communication unit 110 functions to provide wired or wireless communication with the betting game server 30 and a plurality of user terminals 10 and 20. As described with reference to FIG. 1, the betting history sharing server 100 according to an embodiment may be implemented in one configuration with the betting game server 30. In this case, the communication unit 110 may provide a communication function between the plurality of user terminals 10 and 20 and the bet history sharing server 100.

The control unit 120 functions to provide sharing of betting details between the first user 1 and the second user 2. To this end, the controller 120 may perform the following functions.

First, when receiving a bet list request from the first user terminal 10, the control unit 120 generates a bet list including at least one bet details placed by the first user 1, and generates a bet list. 1 Send to the user terminal 10. As described above, the bet list request may be made through the bet list request area in at least one of the chat area and the bulletin board area. Since the description of the bet list request method and the bet list request area has been described in detail above, duplicate descriptions are omitted.

In addition, the control unit 120 may receive a request for sharing the bet details to be shared among at least one bet details from the first user terminal 10. In this case, the control unit 120 creates a bet history viewing area corresponding to the bet history to be shared, and registers the bet history viewing area in a preset area. The preset area may be a chat log area or a post list area in the chat area, and the registration position of the bet history viewing area is determined based on a position requesting the bet list.

The bet history viewing area includes an identifier of the first user 1 and a bet history identification icon, and may further include at least one of a betting game type, a total odds, a hit status, and a title. For example, when a bet list request is made in the chat area, the control unit 120 includes the identifier of the first user 1, the bet history identification icon, the type of betting game, the total odds and the hit status, and the bet history viewing area Can be created. And, when the bet history viewing area is made in the post writing area included in the post area, the control unit 120 may generate the bet history viewing area by including the identifier of the first user 1, the bet history identification icon, and the title. have.

In addition, the control unit 120 may add a bet history identification icon to the bet history viewing area in order to distinguish between the general message or post and the bet history viewing area, and may perform emphasis on the bet history viewing area. Description of the emphasis processing has been described in detail above, and thus will be omitted.

In addition, when the control unit 120 receives a request signal from the first user terminal 10 or the second user terminal 20 through the bet details viewing area, the bet details of the bet details to be shared to the user terminal that transmitted the request signal And bet information can be transmitted.

In addition, the control unit 120 may provide a bookmark function for a bet history viewing area. For example, the control unit 120 receives a bookmark request signal for a bet to be shared from the first user terminal 10 or the second user terminal 20, and transmits the bookmark request signal to the bookmark area of the user account. You can register the bet history viewing area corresponding to the bet history to be shared. Here, the bookmark area is included in the chat area and represents an area separated from the chat log area.

In addition, when receiving a hit status from the betting game server 30, the control unit 120 may update the hit status of the share target bet details registered in the chat log area, the bookmark area, and the post list area.

The exemplary methods according to the present disclosure include program instructions executed by a processor, a software module, a microcode, a computer program product recorded on a recording medium readable by a computer (including all devices having an information processing function), It can be implemented in a variety of ways, including applications, logic circuits, application specific semiconductors, or firmware. Examples of the computer-readable recording medium include, but are not limited to, ROM, RAM, CD, DVD, magnetic tape, hard disk, floppy disk, hard disk, optical data storage device, and the like. Further, the computer-readable recording medium is distributed over a computer system connected through a network, so that computer-readable codes can be stored and executed in a distributed manner.

The above description is only an exemplary description, and various modifications may be made without departing from the technical idea by a person skilled in the art belonging to the technical field of the present disclosure.

100: bet history sharing server 110: communication
120: control unit

Claims (17)

As a method of sharing bet details between users,
Receiving a bet list request from a first user from a first user terminal in at least one of a chat area and a bulletin board area through a communication unit of the bet history sharing server;
Generating a bet list including at least one bet detail made by the first user, and transmitting the bet list to the first user terminal through the communication unit;
Receiving, from the first user terminal, a request for sharing the bet details to be shared among the at least one bet details through the communication unit;
Generating a betting history viewing area corresponding to the sharing target bet history through a control unit of the betting history sharing server; And
And registering the bet history viewing area in a preset area through the control unit,
When the bet list request is made within the chat area, the preset area corresponds to the chat log area included in the chat area,
After the step of registering the bet history viewing area within a preset area,
And registering the bet history viewing area corresponding to the sharing target bet history in a bookmark area included in the chat area, wherein the bookmark area is an area separated from the chat log area,
The bet history viewing area includes an identifier of the first user, a bet history identification icon, and betting information on the sharing target bet history, and the betting information includes at least one of a betting game type, a total odds, a hit status, and a title. Betting history sharing method, characterized in that it further comprises. The method of claim 1,
The bet list request is made through the bet list request area of the screen input from the first user terminal,
The bet list request area is a bet history sharing method, characterized in that in at least one of the chat area and the bulletin board area. delete The method of claim 1,
After the step of registering the bet history viewing area within a preset area,
Further comprising the step of receiving a bookmark request signal for the sharing target bet details from the first user terminal or the second user terminal,
The bookmark area is a bet details sharing method, characterized in that the bookmark area of the user account that transmitted the bookmark request signal. The method of claim 4,
After all the matches included in the sharing target bet details have ended, updating a hit status included in the bet history viewing area in the chat log area and the bookmark area. Way. The method of claim 1, wherein the step of creating the bet history viewing area,
When the request for the bet list is made within the chat area, the method of sharing bet details comprising the step of generating a content displayed through the bet history viewing area in a form that is distinguished from a general message in the chat log area. . The method of claim 1, wherein registering the bet history viewing area in a preset area
And when the bet list request is made through the bulletin board area, registering the bet history viewing area in the post list area included in the bulletin board area. The method of claim 1,
When receiving a request signal through the bet details viewing area from the first user terminal or the second user terminal, transmitting the bet information included in the share target bet details to the user terminal that has transmitted the request signal. Betting history sharing method comprising a. As a betting history sharing server that shares betting history,
Receiving a bet list request from a first user terminal in at least one of a chat area and a bulletin board area, generating a bet list including at least one bet details placed by the first user, and generating the bet list as the first A communication unit that transmits to a user terminal and receives a request for sharing the bet details to be shared among the at least one bet details from the first user terminal; And
And a control unit for generating a bet history viewing area corresponding to the sharing target bet history, and registering the bet history viewing area in a preset area,
When the bet list request is made within the chat area, the preset area corresponds to the chat log area included in the chat area,
The control unit, after registering the bet history viewing area in a preset area,
Registering the bet history viewing area corresponding to the sharing target bet history in a bookmark area included in the chat area, the bookmark area is an area separated from the chat log area,
The bet history viewing area includes an identifier of the first user, a bet history identification icon, and betting information on the sharing target bet history, and the betting information includes at least one of a betting game type, a total odds, a hit status, and a title. Betting history sharing server, characterized in that it further comprises. The method of claim 9,
The bet list request is made through the bet list request area of the screen input from the first user terminal,
The bet list request area is a bet history sharing server, characterized in that in at least one of the chat area and the bulletin board area. delete The method of claim 9,
After the control unit registers the bet details viewing area in a preset area, the communication unit receives a bookmark request signal for the sharing target bet details from the first user terminal or the second user terminal,
The bookmark region is a bet history sharing server, characterized in that the bookmark region of the user account that transmitted the bookmark request signal. The method of claim 12,
The control unit is a bet history sharing server, characterized in that after all the matches included in the sharing target bet history are ended, update the hit status included in the bet history viewing area in the chat log area and the bookmark area. The method of claim 9,
When the request for the bet list is made within the chat area, the control unit generates a content displayed through the bet history viewing area in a form that is distinguished from a general message in the chat log area. The method of claim 9,
When the request for the bet list is made through the bulletin board area, the control unit registers the bet history viewing area in a post list area included in the bulletin board area. The method of claim 9,
When the communication unit receives a request signal through the bet history viewing area from the first user terminal or the second user terminal,
The control unit controls the communication unit to transmit the bet information included in the sharing target bet details to the user terminal that has transmitted the request signal. A computer-readable recording medium containing a computer program for performing the method of sharing bet details of any one of claims 1, 2 and 4 to 8.

Images