Information processing device, control program, and control method

Abstract

To provide a technique for receiving a purchase request for a second user's voting ticket performed on the basis of prescribed notification by performing the notification to the second user in the case that a first user purchases a voting ticket on the basis of expectation of a distributor.SOLUTION: An information processing device capable of communicating with a terminal device used by a user through a communication network includes an acquisition part for acquiring voting information showing that a first user votes for a voting ticket on the basis of provider designation voting ticket information showing voting ticket information designated by a provider for providing the voting ticket information on a voting ticket for voting for a prescribed value in a prediction result to a competition, a notification part for notifying a terminal device of a second user relating to the first user of information on the provider by using prescribed relation information in the case of acquiring the voting information, and a reception part for receiving a voting ticket based on the provider designation voting ticket information from the second user on the basis of the notified information on the provider.SELECTED DRAWING: Figure 1

Description

[Technical field]

[0001] The present invention relates to an information processing device, a control program, and a control method. [Background technology]

[0002] In recent years, with the rapid spread of the Internet and improvements in the communication environment, various services are being provided via communication networks. One such service is a betting ticket purchasing system that enables betting in public races such as horse racing, boat racing, and bicycle racing.

[0003] Another example of such a service is a video distribution service, which accepts uploads from users who wish to receive video content and distributes the video content to users who wish to view the video content.

[0004] As a technology related to such a service, a game providing system that provides a multiplayer electronic game played by multiple players has been disclosed (for example, Patent Document 1). The game providing system includes a storage means for storing a database that associates information specifying characters operated by each of the multiple players with the content of activities performed in the electronic game by the player's operation, and a display means for referencing the database and displaying the characters in association with the content of activities related to the players in a lobby where the multiple players exchange information. [Prior art documents] [Patent documents]

[0005] [Patent Document 1] JP 2018-000938 A Summary of the Invention [Problem to be solved by the invention]

[0006] One of the above-mentioned video distribution services is, for example, a service that distributes video content related to predictions for public races. In the video content related to predictions for public races, for example, a distributor predicts the finishing order of the race, and viewers may purchase betting tickets by referring to the predictions. However, in the past, there was no technology that could link a user's purchase of a betting ticket by referring to the distributor's predictions to the voting behavior of a third party.

[0007] For example, in a multiplayer electronic game played by multiple players, the user may be notified of the behavioral information of friends, etc. For example, in the above-mentioned game providing system, the content of the activity performed by each character in the lobby is displayed.

[0008] However, when the activities of each character are notified separately, the actions of each character are independent, and the relationship between the actions cannot be understood. For example, it is not possible to know whether the actions of user X and user Y are linked.

[0009] This lack of clear correlation between actions is not limited to electronic games. In other words, there are no voting ticket purchasing systems that focus on correlation between actions, and when a user purchases a voting ticket based on a broadcaster's prediction, there is no technology that can link that to the voting behavior of a third party.

[0010] The present invention provides a technology for sending a predetermined notification to a second user when a first user purchases a voting ticket based on a broadcaster's prediction, and for accepting a request to purchase a voting ticket from the second user based on that notification. [Means for solving the problem]

[0011] According to one embodiment of the present invention, an information processing device capable of communicating with a terminal device used by a user via a communication network comprises an acquisition unit that acquires voting information indicating that a first user has cast a voting ticket based on provider-specified voting ticket information indicating voting ticket information specified by a provider who provides voting ticket information regarding a voting ticket for betting a predetermined value on a predicted outcome of a competition, a notification unit that, when the voting information is acquired, notifies a terminal device of a second user related to the first user of information regarding the provider using predetermined relationship information, and a reception unit that accepts a voting ticket based on the provider-specified voting ticket information from the second user based on the notified information regarding the provider. Effect of the Invention

[0012] According to one aspect of the present invention, when a first user purchases a voting ticket based on a broadcaster's prediction, a predetermined notification is sent to a second user, and a request to purchase a voting ticket from the second user based on that notification can be accepted. [Brief description of the drawings]

[0013] [Figure 1] FIG. 1 is a diagram illustrating an example of an information processing device according to an embodiment of the present invention. [Diagram 2] 1 is a diagram showing an example of a network configuration of a betting ticket purchasing system in this embodiment. [Diagram 3] FIG. 2 is a diagram showing an example of functional blocks of the betting ticket purchasing system in the present embodiment. [Figure 4] FIG. 2 is a diagram illustrating an example of a data structure of a database managed by a server in the present embodiment. [Diagram 5] FIG. 13 is a diagram showing an example of a distributor selection screen in the present embodiment. [Figure 6] FIG. 13 is a diagram showing an example of a distributor prediction screen in the present embodiment. [Figure 7] FIG. 13 is a diagram showing an example of a distributor recruitment forecast details screen in this embodiment. [Figure 8] FIG. 13 is a diagram showing an example of a voting ticket purchase screen in the present embodiment. [Figure 9] 13 illustrates a notification example (Example 1) according to the present embodiment. [Figure 10] 13 illustrates a notification example (Example 2) according to the present embodiment. [Figure 11] 13 illustrates a notification example (Example 3) according to the present embodiment. [Figure 12] FIG. 11 is a sequence diagram showing the sequence between the user terminal 12a and the server 16 in this embodiment up to the point where the user purchases a betting ticket by referring to the betting ticket specified by the distributor. [Figure 13] FIG. 11 is a sequence diagram showing the sequence between the user terminal 12b and the server 16 in this embodiment, up to the point where user Y purchases a betting ticket based on a notification that user X has purchased a betting ticket with reference to the betting ticket specified by distributor A. [Figure 14] 11 is a flowchart of a message generation process (S21) and a notification process (S22) performed by a notification control unit 48 in this embodiment. [Figure 15] FIG. 2 is an example of a configuration block diagram of a hardware environment of a computer that executes a program in this embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0014] 1 is a diagram showing an example of an information processing device in this embodiment. The information processing device 1 is an information processing device capable of communicating with a terminal device 5 used by a user via a communication network. The information processing device 1 includes an acquisition unit 2, a notification unit 3, and a reception unit 4. An example of the information processing device 1 is a server 16 described later. An example of the terminal device 5 is a user terminal 12 described later.

[0015] The acquisition unit 2 acquires voting information indicating that the first user has bet with the betting ticket based on provider-specified betting ticket information indicating betting ticket information specified by a provider (e.g., a distributor described later) who provides betting ticket information related to a betting ticket for betting a predetermined value on a predicted outcome of a race. An example of the acquisition unit 2 is the user betting ticket information acquisition unit 46 described later. The predetermined value may be, for example, money such as a bet, something with financial value, or points with no monetary value.

[0016] When the notification unit 3 acquires the voting information, it notifies the terminal device of the second user related to the first user of information about the provider by using predetermined relationship information. The notification may be, for example, a push notification (described later), a toast notification (described later), a message in a group chat (described later), or the like. An example of the notification unit 3 is a notification control unit 48 (described later).

[0017] The reception unit 4 receives a betting ticket based on the provider-specified betting ticket information from the second user based on the notified information about the provider. An example of the reception unit 4 is a user betting ticket information acquisition unit 46, which will be described later.

[0018] By configuring it in this manner, when a first user purchases a voting ticket based on the broadcaster's prediction, a predetermined notification is sent to the second user, and a request to purchase a voting ticket from the second user based on that notification can be accepted.

[0019] The notification unit 3 may notify, as the information regarding the provider, at least one of information notifying that the first user has cast the voting ticket based on the provider-designated voting ticket information, and provider-related information, which is information regarding the provider.

[0020] By configuring in this way, for example, it is possible to notify the second user that the first user has purchased a voting ticket based on the broadcaster's prediction, the contents of the broadcaster's prediction, etc.

[0021] When content related to the provider-specified betting ticket information is not displayed on the terminal device 5 of the second user, the notification unit 3 may notify the terminal device 5 of the second user of information related to the content related to the provider-specified betting ticket information as information related to the provider.

[0022] By configuring in this manner, for example, even if content related to the provider-specified betting ticket information is not in the active information in the terminal device 5 of the second user (for example, when the terminal device 5 is not running), it is possible to notify the terminal device 5 of the second user. The content of the notification is displayed on the terminal device 5 of the second user that receives the notification.

[0023] Here, the predetermined relationship information may be group information related to a preset group of users. In this case, the notification unit 3 can notify the terminal device 5 of the second user in the same group as the first user of the information based on the provider by using the group information.

[0024] With this configuration, users in the same group can be notified of the purchasing trends of other users. As a result, depending on the relationship between users, the voting ticket purchasing trends of a first user can encourage a second user to purchase a voting ticket, leading to the purchase of a voting ticket.

[0025] 2 is a diagram showing an example of a network configuration of a betting ticket purchasing system in this embodiment. The betting ticket purchasing system 11 includes one or more user terminals 12, one or more broadcaster terminals 15, a server 16, and a communication network 17. The one or more user terminals 12, the one or more broadcaster terminals 15, and the server 16 are connected to each other via the communication network 17 so as to be able to communicate with each other.

[0026] The user terminal 12 is a portable electronic terminal device having a communication function that can be connected to a communication network 17, such as a smartphone, tablet terminal, or mobile phone carried by a user. The user terminal 12 has 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 that allows input operations to be performed on a screen 14 and displays images on the screen 14, and is, for example, a touch panel display. The user terminal 12 may be a so-called personal computer.

[0027] The user terminal 12 can download and install a specific application program from an application program download site on the Internet. This allows the user to operate the application program by performing input operations on the operation display unit 13 of the user terminal 12. In this embodiment, as an example, it is assumed that dedicated application software (hereinafter referred to as "dedicated application software") that allows users to purchase betting tickets for public races such as horse races, boat races, and bicycle races, and that allows users to view distributors' predicted finishing orders, is installed in the user terminal 12.

[0028] By starting up this dedicated application software on the user terminal 12, the user can make the user terminal 12 access the server 16. When the user terminal 12 accesses the server 16, for example, the user may be required to input a user ID that has been registered in advance.

[0029] When the dedicated application software installed in the user terminal 12 is started, a graphical user interface (GUI) screen, which will be described later, is displayed on the screen 14 of the user terminal 12. The GUI screen displays video content related to the distributor's predictions of the finishing order of the race, as well as betting ticket information, etc. The user makes a prediction of the finishing order of the race with reference to the video content, etc. displayed on the GUI screen, and purchases a betting ticket via the user terminal 12 by making a specified input.

[0030] If the betting ticket the user has purchased wins the race result, the user will receive a payout based on the payout rate (also called "odds"). Betting tickets can be purchased either for a fee or free of charge. If betting tickets are purchased for a fee, the payout will be made in the form of money, for example. For this reason, the user ID is associated with the user's credit card number, bank account number, or the like, for the purpose of making payments. If betting tickets are purchased free of charge, they can be purchased using points (which have no value as currency) that can be used within the betting ticket purchasing system 11.

[0031] The distributor terminal 15 is a telegraph terminal device having a communication function that can be connected to the communication network 17, such as a computer, smartphone, tablet terminal, or mobile phone used by the distributor. In the present embodiment, as an example, it may be a personal computer. The distributor terminal 15 also has an imaging device that allows the distributor to shoot and distribute videos. The imaging device may be built into the distributor terminal 15 or may be an external type.

[0032] The distributor accesses the server 16 using the distributor terminal 15. Then, the distributor distributes video content (video content related to predicted finishing orders in a race) captured by an imaging device to the user terminal 12 via the server 16.

[0033] The server 16 is an information processing device that manages dedicated application programs installed in the user terminal 12. For example, the server 16 can stream video content posted by the distributor terminal 15 to the user terminal 12. The server 16 can also perform payment processing for purchasing betting tickets based on purchase instructions for betting tickets from the user terminal 12 and the distributor terminal 15. The server 16 may be a server system made up of one or more physical information processing devices, or may be a virtual server system made up of one or more virtual server devices.

[0034] 3 is a diagram showing an example of functional blocks of the betting ticket purchasing system 11 in this embodiment. Below, the functions of each of the user terminal 12, the broadcaster terminal 15, and the server 16 will be described.

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

[0036] The operation display unit 13 is a touch panel display that can receive inputs from a user's input operation and can also display information. 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.

[0037] The control unit 22 controls the overall operation of the user terminal 12. The control unit 22 functions as a display control unit 23, a predictive adoption unit 24, a purchase request unit 25, and a notification receiving unit 26 by executing an application program according to this embodiment.

[0038] The display control unit 23 controls the display state of the screen 14 based on user interface (UI) data 28 of a dedicated application program stored in the storage unit 27. In addition, the display control unit 23 communicates with the server 16 to display the video content distributed by the distributor and the betting ticket information specified by the distributor on the screen 14. Here, the betting ticket information specified by the distributor includes betting ticket information (unpurchased betting tickets) in which the distributor only predicted the order of arrival and purchased betting tickets.

[0039] When the prediction adoption unit 24 receives an instruction to adopt the betting ticket information designated by the broadcaster through an operation from the operation display unit 13, it holds the designated betting ticket information in a predetermined temporary holding area 29. At this time, the prediction adoption unit 24 can hold a part or all of the betting ticket information designated by the broadcaster in the predetermined temporary holding area 29 through an operation from the operation display unit 13. Furthermore, the prediction adoption unit 24 may add new betting ticket information based on the user's own prediction to the information on the betting ticket held in the temporary holding area 29 through an operation from the operation display unit 13.

[0040] The purchase request unit 25 transmits a purchase request to purchase the betting ticket information held in the temporary holding area 29 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 the settlement process for the purchase request.

[0041] The notification receiving unit 26 receives a notification from another user that another user has purchased a voting ticket with reference to a voting ticket designated by one of the broadcasters. In response to the notification received by the notification receiving unit 26, the display control unit 23 displays on the screen 14 that another user has purchased a voting ticket with reference to the voting ticket designated by the broadcaster. At the same time, the display control unit 23 displays a message asking the user whether or not to purchase a voting ticket with reference to the voting ticket designated by that broadcaster. Furthermore, when an input operation is performed on the operation display unit 13 to indicate an intention to purchase a voting ticket with reference to the voting ticket designated by that broadcaster, the display control unit 23 displays a screen for purchasing a voting ticket with reference to the voting ticket designated by that broadcaster.

[0042] Here, other users are users with whom a relationship has been formed in advance with the user, and for example, by connecting as so-called "friends," they can exchange messages with each other and form groups (communities). So-called "friends" refer to a relationship formed by mutual agreement, for example, when one user makes a friend request and the other user accepts the friend request.

[0043] Groups may be formed automatically based on information registered in advance by both users. For example, if the telephone numbers and email addresses of the other users are registered in the user terminals 12 of both users, the server 16 may automatically group them together. The server 16 may also group users who are viewing video content from the same distributor together.

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

[0045] The storage unit 27 also has a temporary storage area 29 for temporarily storing betting ticket information designated by the user. The temporary storage area 29 can also temporarily hold a part or all of the adopted betting ticket information when adopting the betting ticket information designated by the broadcaster. The temporary storage area 29 holds, for example, information identifying the race (race name or race ID, etc.), group number, bet on the group number (or betting points), and, when the betting ticket information is held by the prediction adoption unit 24, information identifying the broadcaster on whose behalf the betting ticket information is based (broadcaster name or broadcaster ID, etc.).

[0046] 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 devices connected to the communication network 17. The communication unit 31 communicates with the server 16 via the communication network 17.

[0047] The control unit 32 controls the overall operation of the distributor terminal 15. Based on instructions from the input unit 33, the control unit 32 distributes video content captured by the imaging unit 34 to the user terminal 12 via the server 16.

[0048] The input unit 33 is an input interface for inputting instructions or inputting instructions and data to the control unit 32. A distributor uses the input unit 33 to input predicted finishing order details for a target race, purchase voting tickets, and input instructions regarding distribution of video content. The imaging unit 34 is an imaging device such as a CCD (Charge Coupled Device).

[0049] The server 16 includes a communication unit 41, a control unit 42, and a storage unit 50. The communication unit 41 is an interface that enables communication with devices 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.

[0050] 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 broadcaster terminal 15, and performs control such as returning the execution result to the user terminal 12 or the broadcaster terminal 15. The control unit 42 executes the application program according to this embodiment, thereby functioning as a distribution control unit 43, a broadcaster betting ticket information acquisition unit 44, a broadcaster betting ticket information provision unit 45, a user betting ticket information acquisition unit 46, a payment processing unit 47, and a notification control unit 48.

[0051] The distribution control unit 43 receives video content shot by a distributor in response to a distribution request from the distributor, and distributes the received video content to a user terminal 12 on which a dedicated application program is running.

[0052] The broadcaster betting ticket information acquisition unit 44 acquires betting ticket information (broadcaster betting ticket information) designated by the broadcaster. Here, the broadcaster betting ticket information includes predicted information on the finishing order of the race input by the broadcaster and betting ticket information purchased by the broadcaster.

[0053] The broadcaster betting ticket information providing unit 45 provides the broadcaster betting ticket information acquired by the broadcaster betting ticket information acquiring unit 44 to the user terminal 12 in association with the video content of the corresponding broadcaster.

[0054] The user betting ticket information acquisition unit 46 acquires the user's betting ticket information stored in the temporary holding area 29 of the user terminal 12 in response to a betting ticket purchase request from the user terminal 12 .

[0055] The payment processing unit 47 performs payment processing for purchasing a betting ticket based on the user's betting ticket information acquired by the user betting ticket information acquisition unit 46. The payment processing is performed based on a pre-registered credit card, account number, etc.

[0056] When the payment for the betting ticket purchased by user X with reference to the betting ticket specified by the distributor is completed, the notification control unit 48 extracts user Y who has a pre-existing relationship with user X from the group information DB 53. When user Y who has a pre-existing relationship with user X is extracted, the notification control unit 48 generates a notification that user X made the purchase with reference to the betting ticket specified by the distributor and that includes information about the betting ticket specified by the distributor. The notification control unit 48 transmits the generated notification to the user terminal 12 of the extracted user Y.

[0057] It should be noted that the notification control unit 48 does not send a notification to the user terminal 12 of user X. Furthermore, if the extracted users have already purchased a voting ticket by referring to a voting ticket designated by distributor A or another distributor, the notification control unit 48 does not need to send the notification to those users.

[0058] The storage unit 50 stores a broadcaster betting ticket information database 51, a user betting ticket information database 52, and a group information database 53. In the following, the database will be referred to as "DB."

[0059] The broadcaster voting ticket information DB 51 is a database that manages the voting ticket information specified by the broadcaster. The user voting ticket information DB 52 is a database that manages the voting ticket information purchased by the user. The group information DB 53 is a database that manages groups (communities) formed by users.

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

[0061] The broadcaster betting ticket information DB51 includes data items of "broadcaster ID", "race ID", "betting ticket", "purchase amount", and "video content ID". Hereinafter, each record of the broadcaster management DB51 may be referred to as broadcaster information. The item "broadcaster ID" stores information (broadcaster ID) that identifies the broadcaster. The item "race ID" stores information (race ID) that identifies the race. The item "betting ticket" stores the group numbers of the finishing order from 1st place to a predetermined position in the race (race) identified by the race ID. In this embodiment, for the sake of convenience, exacta bets, place bets, etc. are not mentioned, but these are not excluded. The item "purchase amount" stores the bet amount corresponding to the betting ticket information. The item "video content ID" stores information (video content ID) that identifies the video content of the corresponding broadcaster.

[0062] The user betting ticket information DB52 includes data items of "User ID", "Race ID", "Bet", "Purchase Amount", "Purchase Points", and "Broadcaster ID". The item "User ID" stores information (user ID) that identifies the user. The item "Race ID" stores information (race ID) that identifies the race. The item "Bet" stores the group numbers of the finishing order from 1st place to a specified position in the race (race) identified by the race ID. The item "Purchase Amount" stores the stake (an item used in the case of a paid event, and the stake is in currency) corresponding to the betting ticket information. The item "Purchase Points" stores the stake (an item used in the case of a free event, and the stake is in points) corresponding to the betting ticket information. The item "Broadcaster ID" stores the broadcaster ID of a broadcaster when a user purchases a betting ticket using a betting ticket designated by the broadcaster.

[0063] The group information DB 53 includes data items of "user ID" and "group ID." The item "user ID" stores information that identifies a user (distributor ID). The item "group ID" stores information that identifies a group of users (group ID).

[0064] In the group information DB 53, a record (group information) is added when a group is formed or when a new user is added as a member to a group. For example, when one user makes a friend request and the other user accepts the friend request, group information is added to the group information DB 53. Also, for example, when the telephone number and email address of the other user are registered in the user terminals 12 of both users, the server 16 registers them as the same group in the group information DB 53. Also, for example, the server 16 registers users who are watching video content of the same distributor as the same group in the group information DB 53.

[0065] Next, the user interface of the dedicated application program installed in the user terminal 12 will be described with reference to Figs. 5 to 8. When the user starts the dedicated application program in the user terminal 12, a screen for selecting a race for which betting tickets can be purchased at that time is displayed on the screen 14. The user operates the operation display unit 13 to select a target race. Then, the screen in Fig. 5 is displayed.

[0066] 5 is a diagram showing an example of a broadcaster selection screen in this embodiment. A broadcaster selection screen 61 includes a login user display field 62, an ownership amount display field 63, an ownership point display field 64, a purchase target race name display field 65, and a broadcaster list 66.

[0067] The logged-in user display field 62 displays the icon and user name of the user currently logged in to the betting ticket purchasing system 11 using the user terminal 12. The retained amount display field 63 displays the amount of money currently retained by the user in the betting ticket purchasing system 11. The retained points display field 64 displays the points currently retained by the user in the betting ticket purchasing system 11. The purchase target race name display field 65 displays the name of the race for which a betting ticket is to be purchased. The purchase target race name display field 65 also displays a message informing the user of the time remaining until the deadline for purchasing betting tickets for that race.

[0068] In the broadcaster list 66, thumbnail images 66a, 66b, 66c, ... of broadcaster information related to race predictions broadcast by each broadcaster for the race displayed in the purchase target race name display field 65 are displayed. The broadcaster list 66 can display broadcaster information that is not currently displayed by scrolling the screen using the operation display unit 13. The user uses the operation display unit 13 to tap, for example, thumbnail image 66a of broadcaster information of broadcaster A in the broadcaster list 66. Then, the screen shown in FIG. 6 is displayed.

[0069] 6 is a diagram showing an example of a broadcaster prediction screen in this embodiment. A broadcaster prediction screen 71 includes a login user display field 72, a selected broadcaster display field 73, a broadcaster video content display field 74, a broadcaster voting ticket information display field 75, and a prediction adoption button 76.

[0070] The login user display field 72 displays the icon and user name of the user currently logged in to the betting ticket purchase system 11 using the user terminal 12. The selected broadcaster display field 73 displays the name of the broadcaster selected in the broadcaster list 66 of the broadcaster selection screen 61. The broadcaster video content display field 74 displays the video content (e.g., live broadcast video in streaming format) of the selected broadcaster. The broadcaster voting ticket information display field 75 displays the voting ticket information specified by the broadcaster. The prediction adoption button 76 is a button that is pressed when adopting the voting ticket information of the broadcaster and purchasing a voting ticket. In the example of FIG. 6, the prediction adoption button 76 is given a caption to the effect that "I will join the prediction of broadcaster A." When the prediction adoption button 76 is tapped, the screen of FIG. 7 is displayed. At this time, the content of the broadcaster voting ticket information display field 75 is stored in the temporary holding area 29.

[0071] 7 is a diagram showing an example of a broadcaster employment forecast detail screen in this embodiment. A broadcaster employment forecast detail screen 81 includes a broadcaster video content display field 82, an owned points display field 83, an owned points addition specification field 84, an owned amount display field 85, an owned money addition specification field 86, a broadcaster forecast voting ticket display field 87, and an “Add to cart” button 95.

[0072] The distributor video content display field 82 displays the video content of the selected distributor (for example, live broadcast video in streaming format). The owned points display field 83 displays the points currently owned by the user in the betting ticket purchasing system 11. By tapping the owned points addition designation field 84, points (charge) that can be used only in the betting ticket purchasing system 11 to purchase betting tickets free of charge can be added. The owned amount display field 85 displays the amount of money currently owned by the user in the betting ticket purchasing system 11. By tapping the owned money addition designation field 86, an amount for purchasing betting tickets for a fee can be added (charged) to the betting ticket purchasing system 11. Note that in the betting ticket purchasing system 11, betting tickets can be purchased within the charged amount or points.

[0073] The broadcaster predicted betting ticket display field 87 includes a predicted betting ticket list 88, a yen / point selection switch 93, and a bet / bet point total display field 92. In the broadcaster predicted betting ticket display field 87, the betting ticket set number and bet or bet point designated by broadcaster A are displayed by default.

[0074] The yen / point selection switch 93 is a switch button that switches between purchasing a betting ticket with a fee or without a fee. When purchasing a betting ticket with a fee, the user designates "yen", and when purchasing a betting ticket without a fee (for use only within the betting ticket purchasing system), the user designates "Pt (points)".

[0075] The prediction betting ticket list 88 includes a group number display field 89, an odds display field 90, and a bet / betting point display field 91. The betting group number display field 89 is a field for displaying the group number to be bet on, and displays the group number specified by the distributor. In the example of FIG. 7, the prediction betting ticket list 88 displays three group numbers: the group number of "1st place No. 1, 2nd place No. 4", the group number of "1st place No. 1, 2nd place No. 4", and the group number of "1st place No. 1, 2nd place No. 2, 3rd place No. 4".

[0076] The odds display field 90 displays odds corresponding to the group number displayed in the betting group number display field 89. The stake / betting point display field 91 displays the stake or betting points for each group number. The stake / betting point total display field 92 displays the total of the stake / betting point display fields 90 in the predicted betting ticket list 87a.

[0077] When the "Add to Cart" button 95 is tapped, a voting ticket purchase screen described in FIG. 8 is displayed.

[0078] 6, the content of the broadcaster voting ticket information display field 75 is stored in the temporary storage area 29. However, this is not limited to the above. For example, the content of the broadcaster predicted voting ticket display field 87 may be stored in the temporary storage area 29 when the "Add to cart" button 95 is tapped.

[0079] 8 is a diagram showing an example of a voting ticket purchase screen in this embodiment. The voting ticket purchase screen 101 includes a distributor video content display field 102, an owned point display field 103, an owned point addition specification field 104, an owned amount display field 105, an owned amount addition specification field 106, a distributor predicted voting ticket display field 107, and a purchase execution button 116.

[0080] The distributor video content display field 102, the owned points display field 103, the owned points addition designation field 104, the owned amount display field 105, and the owned money addition designation field 106 are similar to the distributor video content display field 82, the owned points display field 83, the owned points addition designation field 84, the owned amount display field 85, and the owned money addition designation field 86 in Figure 7, respectively, and so their explanations will be omitted.

[0081] The broadcaster predicted betting ticket display field 107 includes a predicted betting ticket list 108, a betting amount / betting point total display field 112, a set unit purchase button 113, an edit button 114, and a delete button 115. The broadcaster predicted betting ticket display field 107 displays, by default, the set number of the betting ticket and the betting amount or betting points specified by broadcaster A.

[0082] The prediction betting ticket list 108 includes a pair number display field 109, an odds display field 110, and a stake / betting point display field 111. The pair number display field 109, the odds display field 110, the stake / betting point display field 111, and the stake / betting point total display field 112 are similar to the pair number display field 89, the odds display field 90, the stake / betting point display field 91, and the stake / betting point total display field 92 in Fig. 7, respectively, and therefore description thereof will be omitted.

[0083] The set purchase button 113 is a button for purchasing betting tickets in units of a set, where a combination of betting tickets in the prediction betting ticket list 108 is considered as one set. Each time the "+" button of the set purchase button 113 is tapped, the number of sets to be purchased is increased. Each time the "-" button of the set purchase button 113 is tapped, the number of sets to be purchased is decreased.

[0084] By tapping the edit button 114, the user can edit the contents of the forecast voting ticket list 108. For example, the user can change the purchase unit from points (free) to yen (paid), or from yen (paid) to points (free), add a new prediction by the user himself to the forecast voting ticket list 108, or delete a specified group number from the forecast voting ticket list 108. By tapping the delete button 115, the distributor forecast voting ticket display field 107 can be deleted.

[0085] When the purchase execution button 116 is tapped, the purchase process for the betting ticket information specified on the betting ticket purchase screen 101 is executed.

[0086] As explained above, by operating the screens in Fig. 5 to Fig. 8, a user can insert a betting ticket with reference to the betting ticket predicted by the selected broadcaster. In this way, for example, assume that user X purchases a betting ticket using his / her own user terminal 12a with reference to the betting ticket predicted by broadcaster A. Then, user terminal 12b of user Y, who has a predetermined relationship with user X, is notified that user X purchased a betting ticket with reference to the betting ticket predicted by broadcaster A. This will be explained using Figs. 9 to 11.

[0087] Fig. 9 is a notification example (Example 1) in this embodiment. Fig. 9 shows an example of a push notification displayed on the screen 14 based on notification information from the server 16 when the above-mentioned dedicated application program is not in an active state in the user terminal 12b.

[0088] In Fig. 9, a message 121 is displayed by push notification on the home screen of the operating system (OS) of the user terminal 12b. The message 121 displays that the user X purchased a ballot ticket based on the ballot ticket predicted by the broadcaster A, and further displays a display recommending the user Y to purchase a ballot ticket as well. Furthermore, the message 121 includes a link (link information) to the broadcaster adoption prediction details screen 81 (Fig. 7) for the ballot ticket specified by the broadcaster A.

[0089] Here, the "link information" includes information for identifying a transition destination screen (eg, a screen ID) and information for identifying the broadcaster voting ticket information of a broadcaster to be displayed on the transition destination screen (eg, a broadcaster ID).

[0090] Therefore, when user Y taps on this message 121, the dedicated application program becomes active, and based on the link information, a distributor adoption prediction details screen 81 (FIG. 7) for the voting ticket specified by distributor A is displayed. From this point on, user Y can purchase a voting ticket by referring to distributor A's prediction, just like user X, by performing the operations described in FIGS. 7 and 8.

[0091] In this way, even if content related to the broadcaster betting ticket information is not displayed on the user terminal 12b of user Y (for example, when the dedicated application program is not active), information regarding the content related to the broadcaster betting ticket information can be displayed on the user terminal 12b by a push notification from the server 16.

[0092] Fig. 10 is a notification example (Example 2) in this embodiment. Fig. 10 shows an example of a toast notification displayed on the screen 14 based on notification information from the server 16 when the above-mentioned dedicated application program is in an active state in the user terminal 12b. A toast notification is a temporary pop-up display of a message notification.

[0093] In the example of FIG. 10, the toast notification 131 displays an icon 132 of user X, a message indicating that user X purchased a voting ticket based on broadcaster A's prediction, and a "Join in" button 133.

[0094] The "Jump in" button 133 is a button to be tapped when joining the prediction of distributor A. The "Jump in" button 133 has a link (link information) to distributor adoption prediction details screen 81 (FIG. 7) for the voting ticket designated by distributor A.

[0095] Therefore, when user Y taps on this "Join in" button 133, a broadcaster adoption prediction details screen 81 (FIG. 7) for the voting ticket specified by broadcaster A is displayed based on the link information. From this point on, user Y can purchase a voting ticket by referring to broadcaster A's prediction, just like user X, by performing the operations described in FIGS. 7 and 8.

[0096] Fig. 11 is a notification example (Example 3) in this embodiment. Fig. 11 is an example of a chat screen 141 displayed by operating a dedicated application program. On the chat screen 141, users in a predetermined group can exchange messages (group chat) using the chat function of the dedicated application program described above.

[0097] FIG. 11 shows an example of a message that is displayed when users exchange messages within a group and a member of the group purchases a voting ticket based on broadcaster A's prediction.

[0098] Message 142 displays information that User X, a member of the group, purchased a voting ticket based on Broadcaster A's predictions, the details of Broadcaster A's predictions of the finishing order, and a "Join in" button 143.

[0099] The "Jump in" button 143 is a button to be tapped when joining the prediction of distributor A. The "Jump in" button 143 has a link (link information) to distributor adoption prediction details screen 81 (FIG. 7) for the voting ticket designated by distributor A.

[0100] Therefore, when user Y taps on this "Join in" button 143, a broadcaster adoption prediction details screen 81 (FIG. 7) for the voting ticket specified by broadcaster A is displayed based on the link information. From this point on, user Y can purchase a voting ticket by referring to broadcaster A's prediction, just like user X, by performing the operations described in FIGS. 7 and 8.

[0101] 12 is a sequence diagram of the process between the user terminal 12a and the server 16 in this embodiment, up until the user X purchases a betting ticket by referring to the betting ticket specified by the broadcaster. The user X operates the user terminal 12a to start up an installed dedicated application program (S1). Then, the user terminal 12a with the dedicated application program started up makes a data acquisition request to the server 16 (S2). In response, the server 16 transmits broadcaster information (including the broadcaster ID, race ID, and video content ID) to the user terminal 12 (S3).

[0102] 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. 5. The user selects, for example, a thumbnail image 66a of the distributor information of distributor A from the distributor list 66 (S4). Then, the user terminal 12a requests the video content of distributor A based on the video content ID (S5). In response to the request, the user terminal 12a receives the video content from the server 16 (S6). The user terminal 12a plays the received video content on the distributor prediction screen 71 of FIG. 6.

[0103] When broadcaster A specifies the group number of the betting ticket for the finishing order and the purchase amount, the server 16 (broadcaster betting ticket information acquisition unit 44) acquires the details (broadcaster betting ticket information) (S7). The broadcaster betting ticket information includes the broadcaster ID, the race ID, the group number of the betting ticket, the purchase amount, and the video content ID. The server 16 (broadcaster betting ticket information acquisition unit 44) registers the acquired broadcaster betting ticket information in the broadcaster betting ticket information DB 51. The server 16 (broadcaster betting ticket information provision unit 45) then distributes the broadcaster betting ticket information to the user terminal 12 (12a) that is watching the video content of broadcaster A (S8).

[0104] The user terminal 12a displays the set number of the betting ticket included in the broadcaster voting information of the broadcaster A transmitted from the server 16 in the broadcaster voting ticket information display field 75 of the broadcaster prediction screen 71 of FIG. (S9).

[0105] User X taps the prediction adoption button 76 on the broadcaster prediction screen 71 in Fig. 6. Then, the user terminal 12a (prediction adoption unit 24) holds the broadcaster voting ticket information in the temporary holding area 29 (S10). At this time, a broadcaster adoption prediction details screen 81 in Fig. 7 is displayed. When the "Add to cart" button 95 in Fig. 7 is tapped, a voting ticket purchase screen 101 in Fig. 8 is displayed.

[0106] On the betting ticket purchase screen 101, the user may erase part of the broadcaster voting ticket information, or add the user's own predicted voting ticket information to the broadcaster voting ticket information. The user also designates the bet (or betting points) for each piece of voting ticket information (S11). In response to these operations, the user terminal 12a (prediction adoption unit 24) updates the information stored in the temporary storage area 29. That is, the user terminal 12a (prediction adoption unit 24) updates the contents of the temporary storage area 29 in response to the input operation on the betting ticket purchase screen 101 (storing all or part of the broadcaster voting ticket information in the temporary storage area 29).

[0107] When the betting ticket to be purchased is confirmed on the betting ticket purchase screen 101, the user X taps the purchase execution button 116 (S12). Then, the user terminal 12a (purchase request unit 25) transmits a purchase request including the user betting ticket information (including the user ID, race ID, betting ticket set number, purchase amount (or purchase Pt), and broadcaster ID) based on the contents of the temporary holding area 29 to the server 16 (S13).

[0108] 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 contents of the user voting ticket information included in the acquired purchase request in the user voting ticket information DB 52. The server 16 (payment processing unit 47) performs payment processing for the purchase of the voting ticket based on the purchase request (S14). When the payment processing is completed, the server 16 updates the contents of the user owned information DB 52 based on the payment details, and notifies the user terminal 12 of the completion of the payment processing (S15).

[0109] FIG. 13 is a sequence diagram showing the sequence between the user terminal 12b and the server 16 in this embodiment, up to the point where user Y purchases a betting ticket based on a notification that user X has purchased a betting ticket with reference to the betting ticket specified by distributor A.

[0110] After S15 in FIG. 12, the server 16 (notification control unit 48) uses the user ID of user X to extract the user ID of a user who belongs to the same group as user X from the group information DB 53. When the user ID of a user who belongs to the same group as user X is extracted, the server 16 (notification control unit 48) performs a message generation process (S21). Here, it is assumed that the user ID of user Y is extracted as a member who belongs to the same group as user X. The server 16 (notification control unit 48) transmits a notification to the user terminal 12b of user Y extracted in S21 that user X has purchased a betting ticket by referring to the betting ticket specified by distributor A. (S22).

[0111] The user terminal 12b (notification receiving unit 26) receives the notification from the server 16. Then, as described in Fig. 9 to Fig. 11, based on the notification, the user terminal 12b (display control unit 23) displays on the screen 14 a message to the effect that User X has purchased a betting ticket with reference to the betting ticket specified by Distributor A (S23).

[0112] User Y taps the link information included in the notification (for example, message 121 in FIG. 9, "Join" button 133 in FIG. 10, "Join" button 143 in FIG. 11) (S24). Then, user terminal 12b (prediction adoption unit 24) requests broadcaster voting ticket information of broadcaster A from server 16 based on the link information (S25).

[0113] Based on the request, the server 16 acquires the broadcaster betting ticket information of broadcaster A from the broadcaster betting ticket information DB, and transmits it to the user terminal 12b (S26).

[0114] The user terminal 12b receives the broadcaster voting ticket information of broadcaster A from the server 16. Then, the user terminal 12b displays the predicted content of broadcaster A on the broadcaster adoption prediction detail screen 81 of Fig. 7 based on the link information and the broadcaster voting ticket information of broadcaster A (S27). At this time, the user terminal 12b (prediction adoption unit 24) holds the broadcaster voting ticket information of broadcaster B in the temporary holding area 29 (S28). When user Y taps the "Add to cart" button 95 in Fig. 7, the voting ticket purchase screen 101 of Fig. 8 is displayed.

[0115] On the betting ticket purchase screen 101, user Y may erase part of the broadcaster voting ticket information, or add voting ticket information predicted by user Y himself to the broadcaster voting ticket information. User Y also designates a bet (or betting points) for each piece of voting ticket information (S29). In response to these operations, user terminal 12b (prediction adoption unit 24) updates the information stored in the temporary storage area 29. That is, user terminal 12b (prediction adoption unit 24) updates the contents of the temporary storage area 29 in response to the input operation on the betting ticket purchase screen 101 (storing all or part of the broadcaster voting ticket information in the temporary storage area 29).

[0116] When the betting ticket to be purchased is confirmed on the betting ticket purchase screen 101, User Y taps the purchase execution button 116 (S30). Then, the user terminal 12b (purchase request unit 25) transmits a purchase request including the user betting ticket information (including the user ID, race ID, betting ticket set number, purchase amount (or purchase Pt), and broadcaster ID) based on the contents of the temporary holding area 29 to the server 16 (S31).

[0117] 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 contents of the user voting ticket information included in the acquired purchase request in the user voting ticket information DB 52. The server 16 (payment processing unit 47) performs payment processing for the purchase of the voting ticket based on the purchase request (S32). When the payment processing is completed, the server 16 updates the contents of the user owned information DB 52 based on the payment details, and notifies the user terminal 12 of the completion of the payment processing (S33).

[0118] 14 is a flowchart of the message generation process (S21) and the notification process (S22) by the notification control unit 48 in this embodiment. The notification control unit 48 detects the completion of the settlement process for the betting ticket purchased by the user X with reference to the prediction of the distributor A (S41).

[0119] Then, the notification control unit 48 uses the user ID of the user X to extract the user IDs of users who belong to the same group as the user X from the group information DB 53 (S42). If the user IDs of users who belong to the same group as the user X are not extracted, that is, if there are no other members who belong to the group (NO in S43), this flow ends.

[0120] When the user ID of a user belonging to the same group as user X is extracted, that is, when there are other members belonging to the group (YES in S43), the notification control unit 48 generates a message including link information (S44). For example, assume that the user ID of user Y is extracted as a member belonging to the same group as user X. In this case, the notification control unit 48 generates a message to the effect that user X has purchased a voting ticket with reference to the voting ticket specified by broadcaster A. Then, the notification control unit 48 adds link information to the message for screen transition to a broadcaster adoption forecast details screen 81 for broadcaster A. As described above, the link information includes information identifying the transition destination screen (e.g., a screen ID) and information identifying the broadcaster voting ticket information of the broadcaster to be displayed on the transition destination screen (e.g., a broadcaster ID).

[0121] The notification control unit 48 transmits the message with the link information to the user terminal 12 of the user extracted in S42 (S45). Note that, if the extracted users have already purchased a betting ticket with reference to the betting ticket specified by Distributor A or another distributor, the notification control unit 48 does not need to transmit the notification to those users.

[0122] 15 is an example of a configuration block diagram of a hardware environment of a computer that executes a program in this embodiment. A computer 151 functions as a user terminal 12, a distributor terminal 15, or a server 16. The computer 151 is composed of a CPU 152, a ROM 153, a RAM 154, a storage device 155, an input I / F 156, an output I / F 157, a communication I / F 158, a reading device 159, and a bus 160.

[0123] Here, CPU refers to a central processing unit. ROM refers to a read-only memory. RAM refers to a random access memory. I / F refers to an interface. To the bus 160, the CPU 152, ROM 153, RAM 154, storage device 155, input I / F 156, output I / F 157, communication I / F 158, and, if necessary, a reading device 159 are connected.

[0124] When the computer 151 is the server 16, the CPU 152 reads out the program according to this embodiment from the storage device 155, and functions as a distribution control unit 43, a distributor betting ticket information acquisition unit 44, a distributor betting ticket information provision unit 45, a user betting ticket information acquisition unit 46, a settlement processing unit 47, and a notification control unit 48. The ROM 153 indicates a read-only memory. The RAM 154 is a temporary storage memory.

[0125] The storage device 155 is a device that stores a large amount of information. As the storage device 155, various types of storage devices such as a hard disk, a solid state drive (SSD), a flash memory card, etc. are usable. The storage device 155 stores a program according to an embodiment of the present invention and various data stored in the storage unit 40.

[0126] The input I / F 156 can be connected to input devices such as a keyboard, a mouse, an electronic camera, a web camera, a microphone, a scanner, a sensor, a tablet, a touch panel display, an information reading device, etc. The output I / F 157 can be connected to output devices such as a display, a touch panel, a projector, a printer, a speaker, etc.

[0127] The communication I / F 158 is an interface such as a port for connecting to a communication network and communicating with other devices. The communication network may be the Internet, a local area network (LAN), a wide area network (WAN), a dedicated line, a wired line, a wireless line, etc. The reading device 159 is a device for reading a portable recording medium.

[0128] The program for realizing the process described in the above embodiment may be stored in, for example, the storage device 155 from the program provider via the communication network and the communication I / F 158. The program for realizing the process described in the above embodiment may be stored in a portable storage medium that is commercially available and distributed. In this case, the portable storage medium may be set in the reading device 155, and the program may be read and executed by the CPU 152. As the portable storage medium, various types of storage media such as CD-ROM, flexible disk, optical disk, magneto-optical disk, IC card, USB memory device, and semiconductor memory card can be used. The program stored in such a storage medium is read by the reading device 159.

[0129] The program may be installed on a stand-alone computer, or may be installed by a cloud computer and provide only the functions to the user. In the present embodiment, an application program capable of communicating with the server 16 is installed on the user terminal 12 to control the betting ticket purchasing system in the present embodiment, but this is not limiting. 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.

[0130] According to this embodiment, when user X purchases a voting ticket based on broadcaster A's prediction, user Y can be notified that user X has purchased the voting ticket based on broadcaster A's prediction. As a result, user Y can be encouraged to purchase the voting ticket predicted by broadcaster A based on that notification. In this case, a notification that user X, who has a certain relationship with user Y, has purchased a voting ticket based on broadcaster A's prediction is more likely to lead user Y to purchase a voting ticket based on broadcaster A's prediction than a notification that a third party unrelated to user Y has purchased a voting ticket based on broadcaster A's prediction. Therefore, when user Y purchases a voting ticket based on broadcaster A's prediction, This can improve the odds of purchasing a ballot based on a prediction of the winner.

[0131] Although the present aspect has been described above based on the embodiment and modified examples, the above-mentioned embodiment of the aspect is intended to facilitate understanding of the present aspect and does not limit the present aspect. The present aspect may be modified or improved without departing from the spirit and scope of the claims, and equivalents are included in the present aspect. Furthermore, if a technical feature is not described as essential in this specification, it may be deleted as appropriate.

[0132] In addition to the above embodiment, the following is further noted. (Appendix 1) An information processing device capable of communicating with a terminal device used by a user via a communication network, an acquisition unit that acquires voting information indicating that a first user has cast a ballot with a ballot based on provider-specified ballot information indicating ballot information specified by a provider that provides ballot information related to a ballot for casting a predetermined value on a predicted outcome of a race; a notification unit that, when the voting information is acquired, notifies a terminal device of a second user related to the first user of information related to the provider by using predetermined relationship information; a reception unit that receives a betting ticket based on the provider-specified betting ticket information from the second user based on the notified information about the provider; An information processing device comprising: By configuring it in this manner, when a first user purchases a voting ticket based on the broadcaster's prediction, a predetermined notification is sent to the second user, and a request to purchase a voting ticket from the second user based on that notification can be accepted. (Appendix 2) The notification unit notifies, as the information regarding the provider, at least one of information notifying that the first user has cast the betting ticket based on the provider-designated betting ticket information and provider-related information which is information regarding the provider. 2. The information processing device according to claim 1 . By configuring in this way, for example, it is possible to notify the second user that the first user has purchased a voting ticket based on the broadcaster's prediction, the contents of the broadcaster's prediction, etc. (Appendix 3) When content related to the provider-designated betting ticket information is not displayed on the terminal device of the second user, the notification unit notifies the terminal device of the second user of information related to the content related to the provider-designated betting ticket information as information related to the provider. 2. The information processing device according to claim 1 . By configuring in this manner, for example, even if content related to the provider-specified betting ticket information is not in the active information in the terminal device 5 of the second user (for example, when the terminal device 5 is not running), it is possible to notify the terminal device 5 of the second user. The content of the notification is displayed on the terminal device 5 of the second user that receives the notification. (Appendix 4) the predetermined relationship information is group information related to a preset group of users, The notification unit notifies a terminal device of a second user in the same group as the first user of information based on the provider by using the group information. 4. The information processing device according to claim 1, With this configuration, users in the same group can be notified of the purchasing trends of other users. As a result, depending on the relationship between users, the voting ticket purchasing trends of a first user can encourage a second user to purchase a voting ticket, leading to the purchase of a voting ticket. (Appendix 5) A computer capable of communicating with a terminal device used by a user via a communication network, an acquisition process for acquiring voting information indicating that a first user has cast a ballot based on provider-specified ballot information indicating ballot information specified by a provider who provides ballot information related to a ballot for casting a predetermined value on a predicted outcome of a race; a notification process for notifying a terminal device of a second user related to the first user of information about the provider when the voting information is acquired, using predetermined relationship information; an acceptance process for accepting a betting ticket based on the provider-specified betting ticket information from the second user based on the notified information about the provider; A control program that executes the above. By configuring it in this manner, when a first user purchases a voting ticket based on the broadcaster's prediction, a predetermined notification is sent to the second user, and a request to purchase a voting ticket from the second user based on that notification can be accepted. (Appendix 6) A computer capable of communicating with a terminal device used by a user via a communication network, an acquisition process for acquiring voting information indicating that a first user has cast a ballot based on provider-specified ballot information indicating ballot information specified by a provider who provides ballot information related to a ballot for casting a predetermined value on a predicted outcome of a race; a notification process for notifying a terminal device of a second user related to the first user of information about the provider when the voting information is acquired, using predetermined relationship information; an acceptance process for accepting a betting ticket based on the provider-specified betting ticket information from the second user based on the notified information about the provider; A control method for performing the above. By configuring it in this manner, when a first user purchases a voting ticket based on the broadcaster's prediction, a predetermined notification is sent to the second user, and a request to purchase a voting ticket from the second user based on that notification can be accepted. [Explanation of symbols]

[0133] 1. Information processing device 2 Acquisition part 3 Notification section 4. Reception 5 Terminal Equipment 11. Voting Ticket Purchase System 12 User terminal 15 Distributor terminal 16 Servers 17. Communications Networks 41 Communications Department 42 Control section 43 Distribution control section 44 Broadcaster Voting Ticket Information Acquisition Department 45 Broadcaster Voting Ticket Information Department 46 User voting ticket information acquisition unit 47 Payment Processing Unit 48 Notification control section 50 Storage section 51 Broadcaster voting ticket information DB 52 User voting ticket information DB 53 Group Information DB

Claims

[Claim 1] An information processing device capable of communicating with a terminal device used by a user via a communication network, an acquisition unit that acquires voting information indicating that a first user has cast a ballot with a ballot based on provider-specified ballot information indicating ballot information specified by a provider that provides ballot information related to a ballot for casting a predetermined value on a predicted outcome of a race; a notification unit that, when the voting information is acquired, notifies a terminal device of a second user related to the first user of information related to the provider by using predetermined relationship information; a reception unit that receives a betting ticket based on the provider-designated betting ticket information from the second user based on the notified information about the provider; An information processing device comprising:

Images