JP2021119540A - Information processing device, dividend execution program, and dividend execution method - Google Patents

Abstract

To provide technology that increases variations of a hit pattern and improves a user's success experience.SOLUTION: The above problem is solved by comprising: an acceptance unit for accepting, from a user, a vote content that uses a first value for a game; a first dividend processing unit for paying a dividend to the user using the first value when the accepted vote content satisfies a first condition for hit in the game; and a second dividend processing unit for paying a dividend to the user using a second value when the accepted vote content satisfies a second condition for hit in the game.SELECTED DRAWING: Figure 1

Description

The present invention relates to an information processing device, a dividend execution program, and a dividend execution method.

In recent years, various services have been provided via communication networks with the dramatic spread of the Internet and the improvement of communication environments. As one of such services, for example, a voting ticket purchasing system that enables voting in public sports such as horse racing, boat racing, and bicycle racing is disclosed.

Further, as one of the other services, for example, there is a video distribution service. The video distribution service provides a service that accepts uploads from users who desire to provide video content and distributes the video content to users who desire to view the video content. As one of the video distribution services, for example, there is a service that distributes video contents related to the prediction of public competition.

By the way, as a betting ticket game for a game machine, a real betting ticket game is disclosed in which the order of arrival of horse racing races actually held at a racetrack is predicted and points earned are paid out to a player based on the race result. In the real betting ticket game, in addition to the credits used in the normal betting ticket game, bets are made using the points granted to the player. If the prediction is correct, the earned points are paid out to the player based on the odds, and the earned points can be exchanged for various items that can be used in the betting ticket game and the training game (for example, Patent Document 1).

Japanese Unexamined Patent Publication No. 2013-230314

In public competitions such as bicycle races, the types of voting tickets (gambling ceremony) that can be voted on are determined. For example, as a betting type in a bicycle race, triple single (car number three consecutive wins single type), triple double (car number three consecutive wins double type), two car singles (car number two consecutive wins single type), double doubles (car number two consecutive wins). There are seven types of betting types: double type), two-frame single (frame number two consecutive wins single type), two-frame double (frame number two consecutive wins double type), and wide (expanded two consecutive wins double type).

The triple single is a betting ceremony in which the first, second, and third players are hit in order. The triple is a betting ceremony in which the first, second, and third players are hit in any order. The two-car single is a betting type in which the first and second players are hit in order. The double-double is a betting ceremony in which the first and second players are hit in any order. The two-frame single is a betting type in which the first and second players are placed in order. The two-frame duplication is a betting type in which the first and second players are placed in any order. Wide is a betting ceremony in which two players who come within the third place are hit in any order.

Further, in the lottery, for example, the lottery numbers before and after the last digit number of the first prize are known as front and back prizes.

In this way, there are various betting formulas depending on the nature of the competition, and the user can purchase various types of betting formulas using the betting formula and have a higher probability of hitting the target. You can buy betting-type voting tickets that seem to be expensive.

However, there are many combinations of betting ceremonies in public competitions, and the probability of hitting is not high. Users who do not hit the mark may lose their motivation to vote and gradually stop voting. In this case, if the deviation continues, the user loses the motivation to vote again, which may lead to withdrawal from the voting service.

The present invention provides a technique for increasing the variation of the hit pattern and improving the successful experience of the user.

In the information processing device according to one aspect of the present invention, the reception unit that receives the voting content using the first value for the competition from the user and the received voting content satisfy the first hit condition in the competition. In this case, if the first payout processing unit that pays a dividend to the user using the first value and the received voting content satisfy the second hit condition in the competition, the second value is used to the user. It is characterized by having a second dividend processing unit that pays dividends.

According to one aspect of the present invention, it is possible to increase the variation of the hit pattern and improve the successful experience of the user.

It is a figure which shows an example of the information processing apparatus in this embodiment. It is a figure which shows an example of the network configuration of the voting ticket purchase system in this embodiment. It is a figure which shows an example of the functional block of the voting ticket purchase system 11 in this embodiment. It is a figure which shows the data structure example of the database managed by the server 16 in this embodiment. It is a figure explaining an example of the betting type in this embodiment. It is a figure which shows the example of the distributor selection screen in this embodiment. It is a figure which shows the example of the distributor prediction screen in this embodiment. It is a figure which shows the example of the voting ticket purchase screen in this embodiment. It is a figure which shows the privilege grant notice in this embodiment. This is an example of a chat screen used when communicating between group members in the present embodiment. It is a sequence diagram until the distributor voting ticket information is displayed between the user terminal 12 and the server 16 in this embodiment. It is a sequence diagram (Example 1) until the voting ticket is purchased based on the distributor voting ticket information between the user terminal 12 and the server 16 in this embodiment. It is a sequence diagram (Example 2) until the voting ticket is purchased based on the distributor voting ticket information between the user terminal 12 and the server 16 in this embodiment. It is a flowchart of the hit pattern determination and dividend processing (Example 1) in this embodiment. It is a flowchart of the hit pattern determination and dividend processing (Example 2) in this embodiment. It is a flowchart about the setting process of the original betting type in this embodiment. This is an example of a block diagram of a hardware environment of a computer that executes a program in this embodiment.

FIG. 1 is a diagram showing an example of an information processing device according to the present embodiment. The information processing device 1 includes a reception unit 2, a first dividend processing unit 3, and a second dividend processing unit 4. As an example of the information processing device 1, a server 16 described later can be mentioned.

The reception unit 2 receives the voting content from the user using the first value (for example, money, information goods that can be converted into money, etc.) for the competition. An example of the reception unit 2 is the user voting ticket information acquisition unit 46, which will be described later.

When the received voting content satisfies the first hit condition in the competition, the first dividend processing unit 3 pays a dividend to the user using the first value. An example of the first dividend processing unit 3 is the hit determination / dividend processing unit 48, which will be described later.

The second payout processing unit 4 pays a dividend to the user using the second value (for example, free points that cannot be exchanged for money) when the received vote content satisfies the second hit condition in the competition. .. An example of the second dividend processing unit 4 is the hit determination / dividend processing unit 48, which will be described later.

With this configuration, it is possible to increase the variation of the hit pattern and improve the successful experience of the user.

The second payout processing unit 4 determines that the second hit condition is satisfied when a part of the voting targets specified by the predetermined betting formula included in the received voting content matches the winning order in which the winning or losing is confirmed. You can.

With this configuration, for example, even if you purchase a double voting ticket, or if you win only one or two, you can hit it and hit the user. You can pay dividends.

The second payout processing unit 4 determines the winning or losing, in which the predetermined winning or losing rank number is specified according to the winning or losing ranking among the voting targets specified by the predetermined betting formula included in the received voting content. If the number is different from the order of arrival, it may be determined that the second hit condition is satisfied.

By configuring in this way, for example, when purchasing a single voting ticket with N (arbitrary integer) number, if the winning voting ticket number is N-1 or N + 1, it will be hit by the front and back prizes. It can be regarded as a dividend to the user.

The second dividend processing unit 4 is based on the dividend amount based on the first value, or based on the voting amount for the voting target specified by the predetermined betting formula included in the received voting content and the odds of the voting target. 2 The amount of dividends based on value may be determined. With this configuration, the dividend amount based on the second value can be determined based on the dividend amount based on the first value or based on the purchase amount and odds of the voting ticket.

The information processing device 1 further includes a storage unit 5 and a notification unit 6. The storage unit 5 stores the competition specific information (for example, the race venue, the race name, etc.) that identifies the competition for which the vote has been made in relation to the dividend according to the determined second value. An example of the storage unit 5 is the privilege management database 57, which will be described later.

When the payout by the second value is paid, the notification unit 6 notifies the user of the privilege (for example, a special product, the value available in the game, etc.) related to the competition specific information specified based on the payout by the second value. do. An example of the notification unit 6 is the notification unit 49, which will be described later.

With this configuration, for example, instead of the dividend by the second value, the user is provided with a special product of the competition venue specified by the competition specific information according to the dividend amount of the second value as a prize. Becomes possible.

The second dividend processing unit 4 receives the voting content obtained by voting by the user based on all or part of the voting ticket information specified by the provider who provides the expected result for the competition. If this is the case, the user may be the target of the second value dividend.

With this configuration, when the user votes by adopting the provider's expectation, if the second hit condition is satisfied, the dividend can be paid.

If the received voting content is the voting content obtained by voting by the users who formed a group with each other regarding the voting, the second dividend processing unit 4 may also target the user for the dividend by the second value. good.

With this configuration, in the case of forming a group of group chats and voting, if the second hit condition is satisfied, it can be the target of dividends.

The information processing device 1 further includes a generation unit 7. The generation unit 7 may generate the second hit condition based on the hit condition specified by the provider who provides the expected result for the competition or the operator who manages the competition. As an example of the generation unit 7, a betting type registration unit 50, which will be described later, can be mentioned.

With this configuration, the distributor and the management side can independently set the second hit condition.

FIG. 2 is a diagram showing an example of the network configuration of the voting ticket purchasing system according to the present embodiment. The voting ticket purchasing system 11 includes one or more user terminals 12, one or more distributor terminals 15, a server 16, and a communication network 17. One or more user terminals 12, one or more distributor terminals 15, and a server 16 are connected to each other so as to be able to communicate with each other via a communication network 17.

The user terminal 12 is a portable electronic terminal device having a communication function capable of connecting to a communication network 17 such as a smartphone, a tablet terminal, or a mobile phone carried by a user. The user terminal 12 includes an operation display unit 13, a microphone for inputting sound, a speaker for outputting sound, and the like. The operation display unit 13 is a device capable of performing an input operation on the screen 14 and displaying an image on the screen 14, for example, a touch panel display. The user terminal 12 may be a so-called personal computer.

The user terminal 12 can download and install a predetermined application program from an application program download site on the Internet. As a result, the user can operate the application program by performing an input operation on the operation display unit 13 of the user terminal 12. In this embodiment, as an example, it is possible to purchase voting tickets in public competitions such as horse racing, boat racing, and bicycle racing (hereinafter, may be referred to as "competition"), and view the order of arrival forecast by the distributor. It is assumed that possible dedicated application software (hereinafter referred to as "dedicated application software") is installed on the user terminal 12.

The user can make the user terminal 12 access the server 16 by starting the dedicated application software on the user terminal 12. When the user terminal 12 accesses the server 16, for example, the input of a user ID registered in advance may be required.

When the dedicated application software installed on the user terminal 12 is started, the graphical user interface (GUI) screen described later is displayed on the screen 14 of the user terminal 12. In the GUI image, video content and voting ticket information related to the prediction of the finish order of the competition by the distributor are displayed. The user can purchase a voting ticket via the user terminal 12 by predicting the finish order of the competition with reference to the moving image content displayed on the GUI image and performing a predetermined input.

Then, when the purchased voting ticket hits the race result, the user is based on the payout ratio (also referred to as "odds". The odds are calculated according to the amount of paid voting tickets). Receive dividends. Voting tickets can be purchased for a fee or for free. If the purchase of a voting ticket is paid, the dividend will be paid in cash as an example. Therefore, the user ID is associated with, for example, a user's credit card number, a bank account number, or the like for making a payment. If the purchase of the voting ticket is free (that is, if the voting ticket can be voted free of charge), the free points that can be used in the voting ticket purchasing system 11 (cannot be exchanged for money) are used for voting. Can be done. In the following, it is referred to as "purchasing" not only when a voting ticket is designated and voted (purchased) for a fee, but also when a voting ticket is designated and voted free of charge. Further, in the following, the money bet on the voting target, that is, the bet includes points to bet free of charge (betting points).

The distributor terminal 15 is a telegraph terminal device having a communication function capable of connecting to a communication network 17 such as a computer, a smartphone, a tablet terminal, or a mobile phone used by the distributor, for example. In the present embodiment, the distributor terminal 15 may be a personal computer as an example. In addition, the distributor terminal 15 has an imaging device for the distributor to shoot and distribute a moving image. The image pickup device may be built in the distributor terminal 15 or may be an external type.

The distributor uses the distributor terminal 15 to access the server 16. Then, the distributor distributes the moving image content (video content related to the prediction of the finish order of the competition) taken by using the imaging device to the user terminal 12 via the server 16.

The server 16 is an information processing device that manages the dedicated application program installed in the user terminal 12. For example, the server 16 can stream the moving image content posted from the distributor terminal 15 to the user terminal 12.

Further, the server 16 can perform payment processing for purchasing the voting ticket based on the voting ticket purchase instruction from the user terminal 12 and the distributor terminal 15. In addition, the server 16 pays a dividend (refund) based on the hit voting target, the stake, and the odds to the user who hit the purchased voting ticket after the order of arrival of the competition is confirmed. I do.

The server 16 may be a server system composed of one or more physical information processing devices, or may be a virtual server system composed of one or more virtual server devices.

FIG. 3 is a diagram showing an example of a functional block of the voting ticket purchasing system 11 according to the present embodiment. Hereinafter, the functions of the user terminal 12, the distributor terminal 15, and the server 16 will be described.

The user terminal 12 includes an operation display unit 13, a communication unit 21, a control unit 22, and a storage unit 26. The communication unit 21 is an interface that enables communication with a device connected to the communication network 17. Here, the communication unit 21 communicates with the server 16 via the communication network 17.

The operation display unit 13 is a touch panel display capable of inputting and displaying by a user's input operation. In the present embodiment, a touch panel display is used as an example, but the present invention is not limited to this, and the input unit and the display unit may be independent of each other.

The control unit 22 controls the operation of the entire user terminal 12. The control unit 22 functions as a display control unit 23, an expected adoption unit 24, and a purchase request unit 25 by executing the application program according to the present embodiment.

The display control unit 23 controls the display state of the screen 14 based on the user interface (UI) data 27 of the dedicated application program stored in the storage unit 26. At the same time, the display control unit 23 communicates with the server 16 to display the video content distributed by the distributor and the voting ticket information designated by the distributor on the screen 14. Here, the voting ticket information designated by the distributor includes the voting ticket information (unpurchased voting ticket) and the purchased voting ticket that the distributor only predicted the order of arrival.

When the predictive recruitment unit 24 receives an instruction to adopt the voting ticket information designated by the distributor by the operation from the operation display unit 13, the designated voting ticket information is transferred to the predetermined temporary holding area 28. Hold. At this time, the predictive adoption unit 24 can hold a part or all of the voting ticket information designated by the distributor in the predetermined temporary holding area 28 by the operation from the operation display unit 13. Further, the prediction adoption unit 24 may add new voting ticket information based on the user's own prediction to the information regarding the voting ticket held in the temporary holding area 28 by the operation from the operation display unit 13.

The purchase request unit 25 transmits a purchase request for purchasing the voting ticket information held in the temporary holding area 28 to the server 16 in response to an instruction from the operation display unit 13. The purchase request unit 25 receives a purchase completion notification from the server 16 that has performed payment processing for the purchase request.

The storage unit 26 stores installed programs (including dedicated application programs according to the present embodiment), various data, and the like. In the present embodiment, the storage unit 26 stores UI data 27 and the like as an example. Here, the data includes not only status information and character data but also graphical data.

In addition, the storage unit 26 has a temporary holding area 28 for temporarily holding the voting ticket information designated by the user. In addition, when the voting ticket information designated by the distributor is adopted, a part or all of the voting ticket information to be adopted can be temporarily held in the temporary holding area 28. In the temporary holding area 28, for example, when information identifying the competition (race name or race ID, etc.), finish order information, stakes (wager points), and voting ticket information are held by the expected recruitment unit 24, Information (distributor name, distributor ID, etc.) that identifies the distributor, which is the basis of the voting ticket information, is retained.

The distributor terminal 15 includes a communication unit 31, a control unit 32, an input unit 33, and an imaging unit 34. The communication unit 31 is an interface that enables communication with a device connected to the communication network 17. The communication unit 31 communicates with the server 16 via the communication network 17.

The control unit 32 controls the operation of the entire distributor terminal 15. Based on the instruction from the input unit 33, the control unit 32 distributes the moving image content captured by the imaging unit 34 to the user terminal 12 via the server 16.

The input unit 33 is an input interface for inputting an instruction or data to the control unit 32. The distributor uses the input unit 33 to input the expected content of the finish order of the target competition, purchase a voting ticket, and input an instruction regarding distribution of the video content. The imaging unit 34 is an imaging device such as a CCD (Charge Coupled Device).

The server 16 includes a communication unit 41, a control unit 42, and a storage unit 51. The communication unit 41 is an interface that enables communication with a device connected to the communication network 17. The communication unit 41 communicates with the user terminal 12 and the distributor terminal 15 via the communication network 17.

The control unit 42 controls the operation of the entire server 16. At the same time, the control unit 42 executes processing in response to a request from the user terminal 12 or the distributor terminal 15, and controls such as returning the execution result to the user terminal 12 or the distributor terminal 15. By executing the application program according to the present embodiment, the control unit 42 sets the distribution control unit 43, the distributor voting ticket information acquisition unit 44, the distributor voting ticket information providing unit 45, the user voting ticket information acquisition unit 46, and the settlement. It functions as a processing unit 47, a hit determination / dividend processing unit 48, a notification unit 49, and a betting type registration unit 50.

The distribution control unit 43 receives the distributor information about the distributor and the video content captured by the distributor in response to the distribution request from the distributor. The distribution control unit 43 registers the distributor information in the storage unit 51. The distribution control unit 43 distributes the registered distributor information to the user terminal 12 on which the dedicated application program is running. At the same time, the distribution control unit 43 distributes the received video content to the user terminal 12 on which the dedicated application program is running.

The distributor voting ticket information acquisition unit 44 acquires the voting ticket information (distributor voting ticket information) designated by the distributor. Here, the distributor voting ticket information includes the prediction information of the finish order of the competition input by the distributor and the voting ticket information purchased by the distributor.

The distributor voting ticket information providing unit 45 provides the distributor voting ticket information acquired by the distributor voting ticket information acquisition unit 44 to the user terminal 12 in relation to the video content of the corresponding distributor.

The user voting ticket information acquisition unit 46 acquires the voting ticket information of the user held in the temporary holding area 28 of the user terminal 12 in response to the voting ticket purchase request from the user terminal 12.

The payment processing unit 47 performs payment processing for purchasing a voting ticket based on the user's voting ticket information acquired by the user voting ticket information acquisition unit 46. The payment process is performed based on the credit card, account number, etc. registered in advance.

After the result of the competition is confirmed, the hit determination / dividend processing unit 48 determines the hit number or group number if the voting ticket information purchased in the competition includes a voting ticket with a hit number or group number. The refund amount is calculated by multiplying the vote amount cast against the above by the fixed odds. More specifically, the hit determination / payout processing unit 48 pays a first value (for example, money) to the user who voted in the conventional betting ceremony in the competition and hit the target, and the competition A second value (for example, free points that can be used in this system) is paid to the user who voted in the betting formula specified independently in the above and hit the target.

When the dividend by the second value is paid, the notification unit 49 identifies the privilege (special product, value that can be used in the game, etc.) corresponding to the second value from the privilege management database 57, and informs the user of the information about the privilege. Notice.

Since the betting ceremony registration unit 50 has a predetermined authority such as an operator or a distributor of the voting ticket purchasing system 11, when a predetermined input is made, the betting ceremony management database uniquely designated in the competition is used. Register at 59.

The storage unit 51 includes a distributor management database 52, a distributor voting ticket information database 53, a user information management database 54, a user voting ticket information database 55, an odds information database 56, a privilege management database 57, a group management database 58, and a betting ceremony management. Store the database. In the following, the database will be referred to as "DB".

The distributor management DB 52 is a database that manages distributors. The distributor voting ticket information DB 53 is a database that manages voting ticket information designated by the distributor. The user information management DB 54 is a database that manages information about users. The user voting ticket information DB 55 is a database that manages voting ticket information purchased by the user. The odds information DB 56 is a database that manages information regarding odds in competition. The privilege management DB 57 is a database that manages information related to the privilege. The group information DB 58 is a database that manages groups (communities) formed by users for each race. The betting type management DB is a database that manages betting types for each race.

FIG. 4 is a diagram showing an example of a data structure of a database managed by the server 16 in the present embodiment.

The distributor management DB 52 includes data items of "distributor ID", "race ID", and "video content ID". In the following, each record of the distributor management DB 52 may be referred to as distributor information. Information that identifies the distributor (distributor ID) is stored in the item "distributor ID". Information that identifies the competition (race ID) is stored in the item "race ID". In the item "video content ID", information (video content ID) for identifying the video content of the corresponding distributor is stored.

The distributor voting ticket information DB 53 includes data items of "distributor ID", "race ID", "voting ticket", "betting type", "purchase amount", and "video content ID". Information that identifies the distributor (distributor ID) is stored in the item "distributor ID". Information that identifies the competition (race ID) is stored in the item "race ID". In the item "voting ticket", the number of the first place in the competition (race) specified by the race ID or the group number of the finish order from the first place to the predetermined rank is stored. In the item "betting type", the type of betting (win, double win, triple single, etc.) is stored. In the item "purchase amount", the amount of the stake corresponding to the voting ticket information is stored. In the item "video content ID", information (video content ID) for identifying the video content of the corresponding distributor is stored.

The user information management DB 54 includes data items of "user ID", "user name", "email address", "holding amount", and "holding Pt". Information that identifies a user (user ID) is stored in the item "user ID". The name of the user is stored in the item "user name". The user's e-mail address is stored in the item "e-mail address". In the item "holding amount", the amount currently available to the user in the voting ticket purchasing system 11 is stored. In the item "possessed Pt", points currently available to the user in the voting ticket purchasing system 11 are stored.

The user voting ticket information DB 55 includes data items of "user ID", "race ID", "voting ticket", "betting type", "purchase amount", "purchase Pt", and "distributor ID". Information that identifies a user (user ID) is stored in the item "user ID". Information that identifies the competition (race ID) is stored in the item "race ID". In the item "voting ticket", the number of the first place in the competition (race) specified by the race ID or the group number of the finish order from the first place to the predetermined rank is stored. In the item "betting type", the type of betting (win, double win, triple single, etc.) is stored. In the item "purchase amount", the amount of the stake corresponding to the voting ticket information (the item used in the case of payment and the currency is the stake) is stored. In the item "Purchase Pt", the amount of the stake corresponding to the voting ticket information (the item used in the case of free of charge, and the points are the stakes) is stored. In the item "Distributor ID", when the user purchases a voting ticket by adopting the voting ticket specified by the distributor, the distributor ID of the distributor is stored.

The odds information DB 56 includes data items of "race ID", "trifecta", "betting type", "odds", and "unique betting flag". Information that identifies the competition (race ID) is stored in the item "race ID". In the item "trifecta", a combination of numbers (including group numbers) to be voted corresponding to the betting ceremony in the competition (race) specified by the race ID is stored. In the item "betting type", the type of betting (win, double win, triple single, etc.) is stored. In the item "odds", odds information corresponding to each voting ticket is stored. The item "unique betting type flag" is a flag for determining whether or not the betting type of the "trifecta" is a betting type uniquely specified in the competition. When the original betting type flag = 0, it indicates that the betting type is conventional in the competition. When the original betting type flag = 1, it indicates that the betting type is uniquely specified in the competition.

The privilege management DB 57 includes data items of "venue ID", "race ID", "privilege ID", and "location of privilege". Information (venue ID) that identifies the venue (competition venue) is stored in the item "venue ID". Information that identifies the competition (race ID) is stored in the item "race ID". Information that identifies the privilege (privilege ID) is stored in the item "privilege ID". In the item "location of the privilege", an address indicating the storage location of the privilege (for example, privilege video content, still image, character pattern data, etc.) specified by the privilege ID is stored. In addition, the privilege may be a special product or a free gift in the venue or area. In this case, the item "location of benefits" stores information indicating the storage location of special products and prizes and the location of the exchange.

The group management DB 58 includes data items of "user ID", "group ID," and "race ID". Information that identifies the user (distributor ID) is stored in the item "user ID". Information (group ID) for identifying a user's group is stored in the item "group ID". Information that identifies the competition (race ID) is stored in the item "race ID".

A record (group information) is added to the group management DB 58 when a group of users is formed for a certain race or when a new user is added to the group as a member. For example, when one user makes a friend request and the other user approves the friend request, the group information is added to the group management DB 58. Further, for example, when the telephone number and the e-mail address of the other party are registered in the user terminals 12 of both users, the server 16 registers them in the group management DB 58 as the same group. Further, for example, the server 16 registers the users who are viewing the video content of the same distributor as the same group in the group management DB 58.

The betting type management DB 59 includes data items of "race ID", "betting type", and "unique betting type flag". Information that identifies the competition (race ID) is stored in the item "race ID". In the item "betting type", the type of betting (win, double win, triple single, etc.) is stored. The item "unique betting type flag" is a flag for determining whether or not the betting type of the "trifecta" is a betting type uniquely specified in the competition. When the original betting flag = 0, it indicates that the betting type is conventional in the competition. When the original betting type flag = 1, it indicates that the betting type is uniquely specified in the competition.

FIG. 5 is a diagram illustrating an example of a betting type according to the present embodiment. In the present embodiment, a bicycle race will be described as an example of the competition. The types of betting types in bicycle races are usually "triple single", "triple double", "double car single", "double double", "double frame single", "double frame double", and "wide". There are seven types of betting ceremonies.

The "triple single" is a betting ceremony in which the first, second, and third players are hit in order. "Triple" is a betting ceremony in which players in 1st, 2nd, and 3rd place are hit in any order. "Two-car single" is a betting ceremony in which the first and second players are hit in order. "Double and double" is a betting ceremony in which the first and second players are hit in any order. "Single 2 slots" is a betting ceremony in which the slots of the 1st and 2nd players are placed in order. The "two-frame double" is a betting type in which the first and second players are placed in any order. "Wide" is a betting ceremony in which two players who come within the third place are hit in any order. In FIG. 5, these seven types of betting types are indicated by the original betting type flag = 0.

In the present embodiment, in addition to these seven types of betting types, betting types can be set independently for each race. In FIG. 5, for a certain race, for example, "win", "double win", "around triple single", "around triple double", "around two cars", "around double double", "two frames". Eight types of betting formulas, "around single" and "around two frames," shall be newly set independently (corresponding to the hatched betting types in FIG. 5).

"Winning" is a betting ceremony in which the number of the first car is guessed. "Double win" is a betting type in which one of the 1st to 2nd (or 3rd) car numbers is assigned. "Around the triple unit" is a betting type that guesses the front and back of the third car number in the triple unit. "Before and after triplet" is a betting type that hits the front and back of the third car number in triplet. "Around 2 cars" is a betting type that hits the front and back of the 2nd car number in 2 cars. "Before and after double double" is a betting type that guesses the front and back of the second car number in double double. "Around 2 frames" is a betting type that hits the front and back of the 2nd car number in 2 frames. "Before and after 2 frames" refers to the front and back of the 2nd frame number in 2 frames. In FIG. 5, these eight unique betting types are indicated by the unique betting flag = 1.

Next, the user interface of the dedicated application program installed on the user terminal 12 will be described with reference to FIGS. 6, 7, and 8. When the dedicated application program is started on the user terminal 12, a screen for selecting a race for which a voting ticket can be purchased at that time is displayed on the screen 14. When the user operates the operation display unit 13 to select a target race, the screen of FIG. 6 is displayed.

FIG. 6 is a diagram showing an example of a distributor selection screen in the present embodiment. The distributor selection screen 61 includes a login user display field 62, a holding amount display field 63, a holding point display field 64, a purchase target race name display field 65, and a distributor list 66.

In the login user display field 62, the icon and user name of the user who is currently logged in to the voting ticket purchasing system 11 using the user terminal 12 are displayed. In the holding amount display column 63, the amount currently held by the user in the voting ticket purchasing system 11 is displayed. In the holding point display column 64, the points currently held by the user in the voting ticket purchasing system 11 are displayed. In the purchase target race name display field 65, the race name for which the voting ticket is to be purchased is displayed. In the purchase target race name display field 65, a message notifying the time until the purchase deadline of the voting ticket for the race is displayed.

In the distributor list 66, thumbnail images 66a, 66b, 66c, ... Corresponding to the distributor information regarding the race prediction are displayed for the race displayed in the purchase target race name display field 65. The distributor list 66 can display the distributor information that is not currently displayed by the scroll operation by the operation display unit 13. When the thumbnail image 66 of any of the distributors is tapped, the screen of FIG. 7 is displayed for that distributor.

FIG. 7 is a diagram showing an example of a distributor prediction screen in the present embodiment. The distributor prediction screen 71 includes a race name display column 72, a selected distributor display column 73, a distributor video content display column 74, a distributor voting ticket information display column 75, and a detailed display button 76.

The race name of this time is displayed in the race name display column 72. In the race name display field 72, a message notifying the time until the purchase deadline of the voting ticket for the race is also displayed. In the selected distributor display field 73, the distributor name or the like selected in the distributor list 66 of the distributor selection screen 61 is displayed. In the distributor video content display field 74, the video content of the selected distributor (for example, a live distribution video in a streaming format) is displayed. In the distributor voting ticket information display field 75, the group number of the voting ticket specified by the distributor (including the target number when the betting ceremony is a win or a double win. The same shall apply hereinafter) and the odds thereof are displayed. NS. When the detail display button 76 is tapped, the screen of FIG. 8 is displayed, and the detailed contents of the voting ticket specified by the distributor can be confirmed.

FIG. 8 is a diagram showing an example of a voting ticket purchase screen according to the present embodiment. The voting ticket purchase screen 81 has a distributor video content display column 82, a holding point display column 83, a holding point addition designation column 84, a holding amount display column 85, a holding money addition designation column 86, a distributor expected voting ticket display column 87, Includes purchase execution button 96.

In the distributor video content display field 82, the video content of the selected distributor (for example, a live distribution video in a streaming format) is displayed. In the holding point display column 83, the points currently held by the user in the voting ticket purchasing system 11 are displayed. By tapping the possessed point addition designation field 84, points (charges) used only in the voting ticket purchasing system 11 can be added in order to purchase the voting ticket free of charge. In the holding amount display column 85, the amount currently held by the user in the voting ticket purchasing system 11 is displayed. By tapping the holding money addition designation field 86, the amount for purchasing the voting ticket for a fee can be added (charged) to the voting ticket purchasing system 11. In the voting ticket purchasing system 11, the voting ticket can be purchased within the charged amount or within the points.

The distributor expected voting ticket display column 87 includes an expected voting ticket list 87a, a stake / bet point total display column 92, a set unit purchase button 93, an edit button 94, and a delete button 95. In the distributor expected voting ticket display field 87, the group number of the voting ticket designated by the distributor A and the stake or bet point are displayed by default.

The expected voting ticket list 87a includes a betting type 88, a group number display field 89, an odds display field 90, and a stake / bet point display field 91. The betting type 88 is a column for displaying the betting type to be voted. The voting group number display field 89 is a column for displaying the voting number or group number, and displays the number or group number designated by the distributor. In the example of FIG. 8, in the expected voting ticket list 87a, the car number of "winning 4th", the group number of "3 consecutive doubles before and after 1st place 3rd, 2nd place 8th, 3rd place 9th", and "2 cars" Four group numbers are displayed: the group number of "single 1st, 5th, 2nd, 2nd" and the group number of "3 consecutive singles, 1st, 8th, 2nd, 5th, 3rd, 2nd".

In the odds display field 90, the numbers displayed in the voting group number display field 88 or the odds corresponding to the group number are displayed. In the bet / bet point display field 91, the bet or bet point for each number or each group number is displayed. In the bet / bet point total display column 92, the total of the bet / bet point display column 91 in the expected voting ticket list 87a is displayed.

The set unit purchase button 93 is a button for purchasing voting tickets in units of the set, assuming that the combination of voting tickets in the expected voting ticket list 87a is one set. Each time the "+" button of the set unit purchase button 93 is pressed, the set to be purchased can be added. Each time the "-" button of the set unit purchase button 93 is pressed, the set to be purchased can be subtracted.

By pressing the edit button 94, the contents of the expected voting ticket list 87a can be edited. For editing, for example, the unit to be purchased can be changed from points (free) to yen (paid), from yen (paid) to points (free), and the user's own forecast is newly added to the forecast voting ticket list 87a. Can be added, a predetermined group number can be deleted from the expected voting ticket list 87a, and the like. By pressing the delete button 95, the distributor expected voting ticket display field 87 can be deleted.

FIG. 9 is a diagram showing a privilege grant notification in the present embodiment. It is assumed that the user purchases a trifecta using FIG. 8, the race is performed, the order of arrival is confirmed, and then the trifecta with the original betting type flag = 1 hits the mark. In this case, the message 100 notifying the privilege grant is displayed on the screen 14. When the user taps the address described in the message 100, a predetermined moving image content (for example, the moving image content of the distributor A) is displayed on the screen 14 as a privilege.

FIG. 10 is an example of a chat screen used when communicating between group members in the present embodiment. On the chat screen 111, users can exchange messages (group chat) within a predetermined group by using the chat function of the dedicated application program described above. FIG. 10 shows an example of a message displayed when a member of the group purchases a voting ticket with reference to the prediction of the distributor A when users are exchanging messages with each other in the group.

In the message 112, the fact that the user X, who is a member of the group, purchased the voting ticket with reference to the forecast of the distributor A, the content of the arrival order forecast of the distributor A, and the "ride" button 113 are displayed. There is.

The "ride" button 113 is a button to be tapped when riding the prediction of the distributor A. The "ride" button 113 is provided with a link (link information) to the distributor recruitment forecast detail screen 81 (FIG. 8) for the voting ticket designated by the distributor A.

Therefore, when the user Y taps the "ride" button 113, the distributor adoption prediction detail screen 81 (FIG. 8) for the voting ticket designated by the distributor A is displayed based on the link information. After that, by performing the operation described with reference to FIG. 8, the user Y can purchase the voting ticket with reference to the prediction of the distributor A in the same manner as the user X.

FIG. 11 is a sequence diagram until the distributor voting ticket information between the user terminal 12 and the server 16 in the present embodiment is displayed. The user operates the user terminal 12 to start the installed dedicated application program (S1). Then, the user terminal 12 in which the dedicated application program is started makes a data acquisition request to the server 16 (S2).

The server 16 acquires the distributor information (including the distributor ID, the race ID, and the video content ID) of the distributor who predicts the race to be started from the distributor management DB 52 (S3). The server 16 transmits the acquired distributor information to the user terminal 12 (S4).

When the user terminal 12 receives the distributor information from the server 16, the user terminal 12 displays the distributor information in the distributor list 66 of FIG. 6 (S5). The user selects, for example, the thumbnail image 66a of the distributor information of the distributor A from the distributor list 66 (S6). Then, the user terminal 12 requests the video content of the distributor A based on the video content ID (S7). The user terminal 12 receives the video content from the server 16 in response to the request (S8). The user terminal 12 reproduces the received moving image content on the distributor prediction screen 71 of FIG.

When the distributor A specifies a voting ticket, the server 16 (distributor voting ticket information acquisition unit 44) acquires the content (distributor voting ticket information) (S9). The distributor voting ticket information includes a distributor ID, a race ID, a voting ticket number or group number, a purchase price, and a video content ID. The server 16 (distributor voting ticket information acquisition unit 44) registers the acquired distributor voting ticket information in the distributor voting ticket information DB 53. Then, the server 16 (distributor voting ticket information providing unit 45) distributes the distributor voting ticket information to the user terminal 12 viewing the video content of the distributor A (S10).

The user terminal 12 displays the voting ticket number or group number included in the distributor voting information of the distributor A transmitted from the server 16 in the distributor voting ticket information display field 75 of the distributor prediction screen 71 of FIG. (S11).

FIG. 12 is a sequence diagram (Example 1) of purchasing a voting ticket based on the distributor voting ticket information between the user terminal 12 and the server 16 in the present embodiment.

The user taps the detail display button 76 on the distributor prediction screen 71 of FIG. 7. Then, the user terminal 12 (predictive recruitment unit 24) holds the distributor voting ticket information in the temporary holding area 28 (S21). At this time, the voting ticket purchase screen 81 of FIG. 8 is displayed.

On the voting ticket purchase screen 81, the user may delete a part of the distributor voting ticket information or add the voting ticket information predicted by the user to the distributor voting ticket information. In addition, the user specifies a stake for each voting ticket information (S22). In response to these operations, the user terminal 12 (prediction adoption unit 24) updates the information held in the temporary hold area 28. That is, the user terminal 12 (prediction adoption unit 24) updates the contents of the temporary hold area 28 according to the input operation on the voting ticket purchase screen 81 (all or part of the distributor voting ticket information is set to the temporary hold area 28). Hold).

On the voting ticket purchase screen 81, when the voting ticket to be purchased is confirmed, the user taps the purchase execution button 96 (S23). Then, the user terminal 12 (purchase request unit 25) determines the user voting ticket information (user ID, race ID, voting ticket number or group number, purchase amount (or purchase Pt)) based on the contents of the temporary holding area 28. A purchase request including the distributor ID) is transmitted to the server 16 (S24). If the user adds a voting ticket that is different from the distributor's expectation, the voting ticket information may not include the distributor ID information.

The server 16 (user voting ticket information acquisition unit 46) acquires the purchase request. The server 16 (user voting ticket information acquisition unit 46) registers the content of the user voting ticket information included in the acquired purchase request in the user voting ticket information DB 55. The server 16 (payment processing unit 47) performs payment processing related to the purchase of voting tickets based on the purchase request (S25). When the payment process is completed, the server 16 updates the content of the user information management DB 54 based on the payment content and notifies the user terminal 12 of the completion of the payment process (S26).

The server 16 registers the confirmed odds information in the odds information DB 56 after the voting time for the race is closed. When the order of arrival is confirmed after the race, the server 16 (hit determination / dividend processing unit 48) uses the user voting ticket information DB 55, the odds information DB 56, and the betting ceremony management DB 59 to target the voting ticket of which betting type. It is determined whether or not the hit has been made (hit pattern determination), and the hit voting ticket information is processed for dividends (S27). In the hit pattern determination, the voting ticket hit by the betting formula with the original betting type flag = 0 and the voting ticket hit by the betting type with the original betting type flag = 1 are determined respectively.

The server 16 pays a dividend to the hit user (S28). The server 16 makes a monetary refund to, for example, a user who has purchased a voting ticket that hits the betting formula with the original betting formula flag = 0. Further, for example, the server 16 provides a refund with free points and a privilege corresponding to the points to a user who has purchased a voting ticket hit by a betting type with a unique betting type flag = 1 (award grant notification). )I do.

For example, the message 100 shown in FIG. 9 is displayed on the screen 14 of the user terminal 12 that has received the privilege grant notification. The user taps, for example, the address displayed in the message 100 in FIG. Then, the user terminal 12 makes a privilege viewing request (or a privilege viewing request; the same applies hereinafter) to the server 16.

The server 16 distributes the privilege video content for the privilege viewing request to the requesting user terminal 12. The distributed privilege video content is displayed on the screen 14 of the user terminal 12.

FIG. 13 is a sequence diagram (Example 2) of purchasing a voting ticket based on the distributor voting ticket information between the user terminal 12 and the server 16 in the present embodiment. FIG. 13 is a sequence diagram in the case where the distributor voting ticket information of the distributor A is stored in the temporary holding area 28 and the distributor voting ticket information of another distributor is displayed before the purchase.

After S11 in FIG. 11, the user taps the detail display button 76 on the distributor prediction screen 71 in FIG. 7. Then, the user terminal 12 (predictive recruitment unit 24) holds the distributor voting ticket information of the distributor A in the temporary holding area 28 (S41). At this time, the voting ticket purchase screen 81 of FIG. 8 is displayed. After that, the user operates the operation display unit 13 to return to the distributor selection screen 61 of FIG. Since the distributor voting ticket information of the distributor A held in the temporary holding area 28 is retained until the end of the race, it is possible to return to the voting ticket purchase screen 81 of FIG. 8 for the distributor A again. For example, the distributor voting ticket information of the distributor A is displayed.

From the distributor list 66 on the distributor selection screen 61, the user selects the thumbnail image 66b of the distributor information of the distributor B (S42). Then, the user terminal 12 requests the video content of the distributor B (S43). The user terminal 12 receives the video content from the server 16 in response to the request (S44). The user terminal 12 reproduces the received moving image content on the distributor prediction screen 71 of FIG.

When the distributor B specifies a voting ticket, the server 16 (distributor voting ticket information acquisition unit 44) acquires the content (distributor voting ticket information). The distributor voting ticket information includes a distributor ID, a race ID, a voting ticket number or group number, a purchase price, and a video content ID. The server 16 (distributor voting ticket information acquisition unit 44) registers the acquired distributor voting ticket information in the distributor voting ticket information DB 53. Then, the server 16 (distributor voting ticket information providing unit 45) distributes the distributor voting ticket information of the distributor B to the user terminal 12 viewing the video content of the distributor B (S45).

The user terminal 12 displays the voting ticket number or group number included in the distributor voting information of the distributor B transmitted from the server 16 in the distributor voting ticket information display field 75 of the distributor prediction screen 71 of FIG. (S46). Then, the user taps the detail display button 76 on the distributor prediction screen 71 of FIG. 7. Then, the user terminal 12 (predictive recruitment unit 24) holds the distributor voting ticket information of the distributor B in the temporary holding area 28 (S47). At this time, the voting ticket purchase screen 81 of FIG. 8 is displayed.

On the voting ticket purchase screen 81, the user may delete a part of the distributor voting ticket information of the distributor B, or add the voting ticket information predicted by the user to the distributor voting ticket information. In addition, the user specifies a stake for each voting ticket information (S48). In response to these operations, the user terminal 12 (prediction adoption unit 24) updates the information held in the temporary hold area 28. That is, the user terminal 12 (prediction adoption unit 24) updates the contents of the temporary hold area 28 according to the input operation on the voting ticket purchase screen 81 (all or part of the distributor voting ticket information is set to the temporary hold area 28). Hold).

On the voting ticket purchase screen 81, when the voting ticket to be purchased is confirmed, the user taps the purchase execution button 96 (S49). Then, the user terminal 12 (purchase request unit 25) uses the user voting ticket information (user ID, race ID, voting ticket group number, purchase amount (or purchase Pt), distributor) based on the contents of the temporary holding area 28. A purchase request including (including an ID) is transmitted to the server 16 (S50). If the user adds a voting ticket that is different from the distributor's expectation, the voting ticket information may not include the distributor ID information.

Here, the purchase request is a purchase request based on the contents of the temporary hold area 28 specified in S47 and S48. As a result, only the voting ticket purchased on the screen where the purchase execution button 96 was tapped most recently may be purchased. Further, the user terminal 12 (purchase request unit 25) may also transmit a purchase request based on the contents of the temporary hold area 28 specified in S41. That is, when the voting ticket information indicating the purchase intention by the user based on the voting tickets designated by each of the plurality of distributors is held in the temporary holding area 28 each time, and the purchase execution button 96 is tapped. , The user device 12 may collectively transmit the voting ticket information held in the temporary holding area 28 to the server 16. As a result, the settlement processing can be performed collectively.

The server 16 (user voting ticket information acquisition unit 46) acquires the purchase request. The server 16 (user voting ticket information acquisition unit 46) registers the content of the user voting ticket information included in the acquired purchase request in the user voting ticket information DB 55. The server 16 (payment processing unit 47) performs payment processing related to the purchase of voting tickets based on the purchase request (S51). When the payment process is completed, the server 16 updates the content of the user information management DB 54 based on the payment content and notifies the user terminal 12 of the completion of the payment process (S52).

The server 16 registers the confirmed odds information in the odds information DB 56 after the voting time for the race is closed. When the order of arrival is confirmed after the race, the server 16 (hit determination / dividend processing unit 48) uses the user voting ticket information DB 55, the odds information DB 56, and the betting ceremony management DB 59 to target the voting ticket of which betting type. It is determined whether or not the hit has been made (hit pattern determination), and the hit voting ticket information is processed for dividends (S53). In the hit pattern determination, the voting ticket hit by the betting formula with the original betting type flag = 0 and the voting ticket hit by the betting type with the original betting type flag = 1 are determined respectively.

The server 16 pays a dividend to the hit user (S54). The server 16 makes a monetary refund to, for example, a user who has purchased a voting ticket that hits the betting formula with the original betting formula flag = 0. Further, for example, the server 16 provides a refund with free points and a privilege corresponding to the points to a user who has purchased a voting ticket hit by a betting type with a unique betting type flag = 1 (award grant notification). )I do.

For example, the message 100 shown in FIG. 9 is displayed on the screen 14 of the user terminal 12 that has received the privilege grant notification. The user taps, for example, the address displayed in the message 100 in FIG. Then, the user terminal 12 makes a privilege viewing request to the server 16.

The server 16 distributes the privilege video content for the privilege viewing request to the requesting user terminal 12. The distributed privilege video content is displayed on the screen 14 of the user terminal 12.

FIG. 14 is a flowchart of the hit pattern determination and the dividend processing (Example 1) in the present embodiment. The hit determination / dividend processing unit 48 obtains a notification that the finish order of the race has been confirmed (S71). Then, the hit determination / payout processing unit 48 identifies all the hit patterns in the race from the odds information DB 56 and the betting type management DB 59 (S72). Here, all the hit patterns include the hit number and the hit group number of the betting formula with the original betting type flag = 0, and the hit number and the hit group number of the betting type with the unique betting type flag = 1.

The hit determination / dividend processing unit 48 extracts the hit user voting ticket information from the user voting ticket information DB 55 (S73). Here, the hit determination / dividend processing unit 48 uses the hit pattern (specified betting type, hit number (or hit group number)) specified in S72 from the user voting ticket information DB 55. , Extract the user voting ticket information of the user who purchased the hit voting ticket.

The hit determination / dividend processing unit 48 performs the processes of S74 to S77 described below for each of the extracted user voting ticket information (betting type). First, the hit determination / dividend processing unit 48 determines whether or not the item "voting ticket" and the item "betting type" included in the user voting ticket information are normal hit patterns based on the odds information DB 56. do. Here, the hit determination / dividend processing unit 48 is a normal target when the unique betting type flag of the odds information corresponding to the item "voting ticket" and the item "betting type" included in the user voting ticket information is 0. It is determined that the pattern is medium (YES in S74). In this case, the hit determination / dividend processing unit 48 makes a refund based on the first value (for example, money), and refunds the refund to the user as a dividend (S75).

When the unique betting type flag of the odds information corresponding to the item "voting ticket" and the item "betting type" included in the user voting ticket information is 1, the hit determination / dividend processing unit 48 uses a unique hit pattern. It is determined that there is (NO in S74). In this case, the hit determination / dividend processing unit 48 makes a refund based on the second value (for example, free points) and refunds the refund points to the user as a dividend (S76). In addition, when voting with free points, the hit determination / dividend processing unit 48 may not make a refund by its own betting formula.

FIG. 15 is a flowchart of the hit pattern determination and the dividend processing (Example 2) in the present embodiment. FIG. 15 shows the flowchart of FIG. 14 with the processing of S81 and S82 added. FIG. 15 is an example in which a user who has purchased a voting ticket with reference to the distributor's expectation or a user who has formed a group among users for a race is targeted for a dividend by a second value.
The hit determination / dividend processing unit 48 obtains a notification that the finish order of the race has been confirmed (S71). Then, the hit determination / payout processing unit 48 identifies all the hit patterns in the race from the odds information DB 56 and the betting type management DB 59 (S72). Here, all the hit patterns include the hit number and the hit group number of the betting formula with the original betting type flag = 0, and the hit number and the hit group number of the betting type with the unique betting type flag = 1.

The hit determination / dividend processing unit 48 extracts the hit user voting ticket information from the user voting ticket information DB 55 (S73). Here, the hit determination / dividend processing unit 48 uses the hit pattern (specified betting type, hit number (or hit group number)) specified in S72 from the user voting ticket information DB 55. , Extract the user voting ticket information of the user who purchased the hit voting ticket.

The hit determination / dividend processing unit 48 performs the processes of S74 to S77 described below for each of the extracted user voting ticket information (betting type). First, the hit determination / dividend processing unit 48 determines whether or not the item "voting ticket" and the item "betting type" included in the user voting ticket information are normal hit patterns based on the odds information DB 56. do. Here, the hit determination / dividend processing unit 48 is a normal target when the unique betting type flag of the odds information corresponding to the item "voting ticket" and the item "betting type" included in the user voting ticket information is 0. It is determined that the pattern is medium (YES in S74). In this case, the hit determination / dividend processing unit 48 makes a refund based on the first value (for example, money), and refunds the refund to the user as a dividend (S75).

When the unique betting type flag of the odds information corresponding to the item "voting ticket" and the item "betting type" included in the user voting ticket information is 1, the hit determination / dividend processing unit 48 uses a unique hit pattern. It is determined that there is (NO in S74).

In this case, the hit determination / dividend processing unit 48 is based on the item "distributor ID" of the user voting ticket information, and the voting ticket is voted by the user with reference to the voting ticket information specified by the distributor. (S81). That is, when valid information (distributor ID) is not registered in the item "distributor ID" of m user voting ticket information, the hit determination / dividend processing unit 48 votes the voting ticket specified by the distributor. It is determined that the purchase was not made with reference to the ticket information (NO in S81), and the process proceeds to S82.

When valid information (distributor ID) is registered in the user voting ticket information item "distributor ID", the hit determination / dividend processing unit 48 determines the voting ticket information that the voting ticket is designated by the distributor. It is determined that the product was purchased with reference to (YES in S81), and the process proceeds to S76.

Next, the hit determination / dividend processing unit 48 determines whether or not the voting ticket has been voted by the users who formed a group among the users regarding the voting (S82). Here, the hit determination / dividend processing unit 48 searches the group management DB 58 using the user ID and the race ID as keys. When the group information corresponding to the user ID and the race ID is not registered (NO in S82), the hit determination / dividend processing unit 48 processes the next user voting ticket information after S74.

The hit determination / dividend processing unit 48 searches the group management DB 58 using the user ID and the race ID as keys. When the group information corresponding to the user ID and the race ID is registered, the hit determination / dividend processing unit 48 determines that the voting ticket has been voted by the users who formed a group with each other regarding voting. (YES in S82)

If it is determined to be YES in S81 or YES in S82, the hit determination / dividend processing unit 48 makes a refund based on the second value (for example, free points) and refunds the refund points to the user as a dividend (for example, free points). S76).

FIG. 16 is a flowchart relating to the setting process of the original betting type in the present embodiment. The operator can set his own betting ceremony for each race. Specifically, the operator accesses the server 16 using his / her own terminal and registers his / her own betting type. The distributor may also be able to set his / her own betting type by using the distributor terminal 15 if he / she can acquire the predetermined authority through the predetermined procedure.

The betting type registration unit 50 acquires the hit condition (unique betting type) specified by the operator or the distributor (S91). Here, the original betting type includes the type of the original betting type and the content of the betting type.

The betting type registration unit 50 generates a second hit condition based on the acquired original betting type and reflects it in the odds information DB 56 (S92). Here, the betting type registration unit 50 registers the acquired original betting type in the betting type management DB 59. At this time, the betting type registration unit 50 registers the original betting type acquired with the original betting type flag = 1 in the betting type management DB 59. As a result, the unique betting type set with the unique betting flag = 1 is generated as the second hit condition.

FIG. 17 is an example of a block diagram of a hardware environment of a computer that executes a program according to the present embodiment. The computer 101 functions as a user terminal 12, a distributor terminal 15, or a server 16. The computer 101 is composed of a CPU 102, a ROM 103, a RAM 104, a storage device 105, an input I / F 106, an output I / F 107, a communication I / F 108, a reading device 109, and a bus 110.

Here, the CPU indicates a central processing unit. ROM indicates read-only memory. RAM represents a random access memory. I / F indicates an interface. A CPU 102, a ROM 103, a RAM 104, a storage device 105, an input I / F 106, an output I / F 107, a communication I / F 108, and a reading device 109 are connected to the bus 110, if necessary.

When the computer 101 is the server 16, the CPU 102 reads the program according to the present embodiment from the storage device 105, and the distribution control unit 43, the distributor voting ticket information acquisition unit 44, the distributor voting ticket information providing unit 45, and the user voting ticket. It functions as an information acquisition unit 46, a settlement processing unit 47, a hit determination / dividend processing unit 48, a notification unit 49, and a betting type registration unit 50. ROM 103 indicates a read-only memory. The RAM 104 is a memory that is temporarily stored.

The storage device 105 is a device that stores a large amount of information. As the storage device 105, various types of storage devices such as a hard disk, a solid state drive (SSD), and a flash memory card can be used. When the computer 101 is the server 16, the storage device 105 stores the program according to the embodiment of the present invention and various data stored in the storage unit 51.

The input I / F 106 can be connected to an input device such as a keyboard, a mouse, an electronic camera, a webcam, a microphone, a scanner, a sensor, a tablet, a touch panel display, and an information reading device. Further, the output I / F 107 can be connected to an output device such as a display, a touch panel, a projector, a printer, and a speaker.

The communication I / F 108 is an interface such as a port for connecting to a communication network and communicating with another device. The communication network may be a communication network such as the Internet, a local area network (LAN), a wide area network (WAN), a leased line, a wired network, or a wireless network. The reading device 109 is a device that reads a portable recording medium.

The program that realizes the processing described in the above embodiment may be stored in the storage device 105, for example, from the program provider side via the communication network and the communication I / F 108. Further, the program that realizes the processing described in the above embodiment may be stored in a commercially available and distributed portable storage medium. In this case, the portable storage medium may be set in the reading device 105, and the program may be read and executed by the CPU 102. As the portable storage medium, various types of storage media such as a CD-ROM, a flexible disk, an optical disk, a magneto-optical disk, an IC card, a USB memory device, and a semiconductor memory card can be used. The program stored in such a storage medium is read by the reading device 109.

In addition, the program may be installed on a stand-alone computer, or may be installed by a cloud computer to provide only the functions to the user. Further, in the present embodiment, an application program capable of communicating with the server 16 is installed in the user terminal 12 to control the voting ticket purchasing system in the present embodiment, but the present invention is not limited to this. For example, a Web browser installed on the user terminal 12 may be used to access the server 16 and use the system according to the present embodiment operated on the server 16 side.

According to this embodiment, it is possible to increase the variation of the hit pattern and improve the successful experience of the user. The hit pattern is not limited to single wins, double wins, and front and back prizes, and for example, the lowest or the second from the lowest may be hit.

The benefits are registered in the privilege management DB 57, but different benefits may be registered for each venue where the competition is held, or different benefits may be registered for each competition (race). ..

Further, the privilege may be not only a moving image but also a still image, music data, text data, or a predetermined program. The still image may include not only a photograph but also a character design, a cartoon, and the like. Further, the text data may be content such as a novel. The music data may be data in which only the audio part of the moving image content is recorded, data having only audio, or music data. The predetermined program may be, for example, a game program. Further, the privilege may be an access right to a predetermined website or the like, an item object or the like that can be used in a predetermined game program, an experience value for leveling up, or the like. In addition, as described above, the privilege may be a special product or a prize in the venue or area.

Although the present embodiment has been described above based on the embodiments and modifications, the embodiments of the above-described embodiments are for facilitating the understanding of the present embodiment and do not limit the present embodiment. This aspect may be modified or improved without departing from its spirit and claims, and this aspect includes its equivalents. In addition, if the technical feature is not described as essential in the present specification, it may be deleted as appropriate.

In addition to the above embodiment, the following will be added.
(Appendix 1)
A reception department that accepts voting content using the first value for the competition from users,
When the received voting content satisfies the first hit condition in the competition, the first payout processing unit that pays the user by using the first value, and the first payout processing unit.
When the received voting content satisfies the second hit condition in the competition, the second payout processing unit that pays the user by using the second value, and the second payout processing unit.
An information processing device characterized by being equipped with.
With this configuration, it is possible to increase the variation of the hit pattern and improve the successful experience of the user.
(Appendix 2)
The second payout processing unit satisfies the second hit condition when a part of the voting targets specified by the predetermined betting formula included in the received voting content matches the winning order in which the winning or losing is confirmed. The information processing apparatus according to Appendix 1, wherein the determination is made.
With this configuration, even if you purchase a double voting ticket, even if you win only one or two, you will hit it and pay out to the user. be able to.
(Appendix 3)
In the second payout processing unit, the winning / losing number is specified according to the winning / losing order among the voting targets specified by the predetermined betting formula included in the received voting content. The information processing apparatus according to Appendix 1, wherein when is a number different from the confirmed order of arrival, it is determined that the second hit condition is satisfied.
By configuring in this way, for example, when purchasing a single voting ticket with N (N is an arbitrary integer) number, if the winning voting ticket number is N-1 or N + 1, it will be awarded before and after. It can be regarded as a hit and paid to the user.
(Appendix 4)
The second dividend processing unit is based on the dividend amount based on the first value, or based on the voting amount for the voting target specified by the predetermined betting formula included in the received voting content and the odds of the voting target. The information processing apparatus according to any one of Supplementary note 1 to 3, wherein the dividend amount based on the second value is determined.
With this configuration, the dividend amount based on the second value can be determined based on the dividend amount based on the first value or based on the purchase amount and odds of the voting ticket.
(Appendix 5)
The information processing device further
A storage unit that stores the competition-specific information that identifies the competition for which the vote was made and the determined dividend based on the second value in relation to each other.
When the dividend based on the second value is paid, a notification unit for notifying the user of the privilege related to the competition specific information specified based on the dividend based on the second value, and the notification unit.
The information processing apparatus according to any one of Supplementary note 1 to 4, wherein the information processing apparatus is provided with.
With this configuration, for example, instead of the dividend by the second value, the user is provided with a special product of the competition venue specified by the competition specific information according to the dividend amount of the second value as a prize. Becomes possible.
(Appendix 6)
The second payout processing unit is obtained by the received voting content being voted by the user based on all or part of the voting ticket information specified by the provider who provides the expected result for the competition. The information processing apparatus according to any one of Supplementary Provisions 1 to 6, wherein the user is subject to a dividend based on the second value in the case of the voting content.
With this configuration, when the user votes with reference to the provider's expectation, and if the second hit condition is satisfied, the dividend will be paid.
(Appendix 7)
When the received voting content is the voting content obtained by voting by the users who form a group with each other regarding the voting, the second dividend processing unit pays the user a dividend based on the second value. The information processing apparatus according to any one of Supplementary note 1 to 6, wherein the information processing apparatus is the subject of the above.
With this configuration, in the case of forming a group of group chats and voting, if the second hit condition is satisfied, the dividend will be paid.
(Appendix 8)
The information processing device further
Appendix 1 to include a generator that generates the second hit condition based on the hit condition specified by the provider who provides the expected result for the competition or the operator who operates the competition. The information processing apparatus according to any one of 7.
With this configuration, the distributor and the management side can independently set the second hit condition.
(Appendix 9)
On the computer
Reception processing that accepts voting content using the first value for the competition from the user,
When the received voting content satisfies the first hit condition in the competition, the first payout process of paying a payout to the user using the first value, and
When the received voting content satisfies the second hit condition in the competition, the second payout process of paying the user using the second value, and the second payout process.
Dividend execution program characterized by executing.
With this configuration, it is possible to increase the variation of the hit pattern and improve the successful experience of the user.
(Appendix 10)
The computer
Accepting the content of the vote using the first value for the competition from the user,
When the received voting content satisfies the first hit condition in the competition, the first value is used to pay a dividend to the user.
If the received voting content satisfies the second hit condition in the competition, the second value is used to pay the user.
Dividend execution method characterized by this.
With this configuration, it is possible to increase the variation of the hit pattern and improve the successful experience of the user.

1 Information processing device 2 Providing unit 3 Acquisition unit 4 Decision unit 5 Terminal device 11 Voting ticket purchasing system 12 User terminal 15 Distributor terminal 16 Server 17 Communication network 41 Communication unit 42 Control unit 43 Distribution control unit 44 Distributor voting ticket information acquisition Department 45 Distributor Voting Ticket Information Providing Department 46 User Voting Ticket Information Acquisition Department 47 Payment Processing Department 48 Hit Judgment / Dividend Processing Department 49 Notification Department 50 Bet Type Registration Department 51 Storage Department 52 Distributor Management DB
53 Distributor voting ticket information DB
53 User information management DB
55 User Voting Ticket Information DB
56 Odds Information DB
57 Benefit management DB
58 Group management DB
59 Betting type management DB

Claims (1)

A reception department that accepts voting content using the first value for the competition from users,
When the received voting content satisfies the first hit condition in the competition, the first payout processing unit that pays the user by using the first value, and the first payout processing unit.
When the received voting content satisfies the second hit condition in the competition, the second payout processing unit that pays the user by using the second value, and the second payout processing unit.
An information processing device characterized by being equipped with.

Images