Race voting ticket purchase method, and race voting ticket purchase program

Abstract

To provide a race voting ticket purchase method and a race voting ticket purchase program which supports a user who is not familiar with purchase of a race voting ticket.SOLUTION: The present invention is directed to a race voting ticket purchase method of supporting purchase of a race voting ticket by a second user in a system formed of a first terminal of a first user, a second terminal of the second user, and a computer for carrying out communication. The method has a step of, if it is determined that sharing instructions specifying a betting content as a voting target selected by the first user among a plurality of voting targets is received from the first terminal, displaying identifiers corresponding to the betting content on the first terminal, a step of specifying the betting content from the identifier read out from the first terminal by the second terminal, and a step of displaying the specified betting content on the second terminal.SELECTED DRAWING: Figure 14

Description

Technical Field

[0001] This invention relates to a method for purchasing race betting tickets and a program for purchasing race betting tickets.

Background Art

[0002] An Internet voting system is known that enables the purchase of winning horse betting tickets via the Internet from a personal computer terminal or a mobile phone (see, for example, Patent Document 1).

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] In many cases, for the purchase of race betting tickets such as winning horse betting tickets that predict and vote on the finishing order of horses running in a horse race, or winning boat betting tickets that predict and vote on the finishing order of boats in a boat race, filling out a mark sheet is required.

[0005] Here, users who are enthusiastic about races such as horse racing and boat racing are likely to be accustomed to purchasing race betting tickets. Such users can determine the combination of numbers of the objects to be voted on, such as running horses or boats, and complete the filling out of the mark sheet method shortly before the race of the object to be voted on.

[0006] However, beginners in horse racing or boat racing, foreign tourists visiting Japan from overseas, etc. are likely not to be accustomed to purchasing race betting tickets. When such users who are not accustomed to purchasing race betting tickets purchase race betting tickets, it may take time to fill out the mark sheet method. Also, some users who are not accustomed to purchasing race betting tickets may find it difficult to determine the combination of numbers to buy.

[0007] Therefore, in one aspect, an object is to provide a race ticket purchase method and a race ticket purchase program for assisting a user who is not used to purchasing race tickets.

Means for Solving the Problem

[0008] In one embodiment, a race ticket purchase method is a race ticket purchase method for assisting the purchase of a race ticket by a second user by a computer that communicates with a first terminal of a first user and a second terminal of a second user, and when it is determined that a sharing instruction specifying a purchase target, which is a voting target selected by the first user from among a plurality of voting targets, is received from the first terminal, an identifier corresponding to the purchase target is displayed on the first terminal, the purchase target is specified from the identifier read by the second terminal from the first terminal, and the specified purchase target is displayed on the second terminal.

Effect of the Invention

[0009] It is possible to assist a user who is not used to purchasing race tickets.

Brief Description of the Drawings

[0010]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Figure 13

Figure 14

Figure 15

Figure 16

Figure 17

Figure 18

Embodiments for Carrying Out the Invention

[0011] Hereinafter, embodiments for carrying out the present case will be described with reference to the drawings. In this embodiment, horse racing will be described as an example of a race. For this reason, the race voting ticket will be described as a winning horse ticket (hereinafter referred to as a horse racing ticket), and the object of voting will be described as a racehorse. A racehorse is an example of an animal.

[0012] However, the race is not limited to horse racing, and may be a public competition such as boat racing, motorcycle racing, or auto racing. For this reason, the race voting ticket may be a winning boat ticket, a winning ticket, a winning car ticket, etc. Also, the object of voting may be a person such as a boat racer, a motorcycle racer, or an auto racer, or may be a vehicle such as a boat, a bicycle, or a motorcycle.

[0013] As shown in FIG. 1, within the facilities of the racecourse RC, guide plates 11 and 12 for guiding services (such as communication services and web services) available within the racecourse RC and its facilities are installed in various locations. For example, the guide plate 11 is installed at or near the information center of the racecourse RC. The guide plate 12 is installed at or near the souvenir shop of the racecourse RC.

[0014] On the guide plates 11 and 12, two-dimensional codes 11C and 12C for guiding to service use registration are posted. The two-dimensional codes 11C and 12C are the same. The two-dimensional codes 11C and 12C may be QR codes (registered trademarks), or may be other two-dimensional codes (such as PDF417 or Data Matrix, etc.) excluding QR codes (registered trademarks). Note that the guide plates 11 and 12 may be installed outside the racecourse RC (such as an off-course ticket sales office, an airport, a izakaya, etc.).

[0015] When users P1 and P2 who come to the racecourse RC together use the service, if it is user P1, user P1 operates his own first mobile terminal 100 to make the first mobile terminal 100 read the two-dimensional code 11C. Thereby, the first mobile terminal 100 can access a server device 300 (see FIG. 16) described later and use the service provided by the server device 300. Note that an application program (hereinafter referred to as a service app) for using the service may be installed in the first mobile terminal 100.

[0016] On the other hand, if it is user P2, user P2 operates their own second mobile terminal 200 to cause the second mobile terminal 200 to read the two-dimensional code 11C. As a result, the second mobile terminal 200 can access the server device 300 and use the services provided by the server device 300. Note that a service application may be installed on the second mobile terminal 200. The service application installed on the second mobile terminal 200 is the same as the service application installed on the first mobile terminal 100. In FIG. 1, a smartphone is shown as an example of the first mobile terminal 100 and the second mobile terminal 200, but a smart terminal including a tablet terminal may be used instead of the smartphone.

[0017] Users P1 and P2 can perform temporary (e.g., limited to half a day or limited to the same day) simple use registration without being required to provide personal information (e.g., name, gender, etc.) according to the screen guidance provided by the service application. If users P1 and P2 perform simple use registration, they can use the services provided within the racecourse RC or the facility. For example, users P1 and P2 can use a service through the service application to share the combination of numbers assigned to the starting horses, which is the bet.

[0018] If user P1 is an enthusiastic heavy user who is familiar with horse racing and user P2 is a light user who is close to a beginner and not familiar with horse racing, if user P2 can share the bets of user P1, user P2 will not have trouble deciding on bets. In addition, when purchasing a lottery ticket, user P2 can avoid filling in the mark sheet method. Note that users P1 and P2 may be a group of Japanese people including friends or acquaintances, or a group of foreign travelers visiting Japan.

[0019] Hereinafter, first, a second embodiment in which a service application is installed on each of the first mobile terminal 100 and the second mobile terminal 200 will be described. Thereafter, a first embodiment in which each of the first mobile terminal 100 and the second mobile terminal 200 enjoys the services provided by the server device 300 will be described.

[0020] (Second Embodiment) In the second embodiment, a race voting ticket purchase system ST1 can be realized by the first mobile terminal 100 and the second mobile terminal 200. Hereinafter, the details of the race voting ticket purchase system ST1 will be described.

[0021] Referring to FIG. 2, the hardware configuration of the first mobile terminal 100 will be described. Note that since the hardware configuration of the second mobile terminal 200 is basically the same as that of the first mobile terminal 100, detailed description thereof will be omitted.

[0022] The first mobile terminal 100 includes a CPU (Central Processing Unit) 100A as a processor, a RAM (Random Access Memory) 100B, a ROM (Read Only Memory) 100C, an NVM (Non-Volatile Memory) 100D as memories, and an RF (Radio Frequency) circuit 100E. An antenna ATN is connected to the RF circuit 100E. A CPU that realizes a communication function may be used instead of the RF circuit 100E.

[0023] Further, the first mobile terminal 100 includes a camera 100F, a speaker 100G, a touch panel 100H, a display 100I, and a microphone 100J. From the CPU 100A to the microphone 100J are connected to each other by an internal bus 100K. At least the CPU 100A and the RAM 100B cooperate to realize a computer.

[0024] In the above-described RAM 100B, programs stored in the ROM 100C and the NVM 100D are stored by the CPU 100A. By the CPU 100A executing the stored programs, the CPU 100A realizes various functions described later and also executes a series of processes. Note that the programs may be in accordance with the flowcharts described later.

[0025] Referring to FIG. 3(a), the functional configuration of the first mobile terminal 100 will be described. Note that FIG. 3(a) shows the main part of the functions of the first mobile terminal 100.

[0026] As shown in FIG. 3(a), the first mobile terminal 100 includes a storage unit 110, a processing unit 120, an input unit 130, and a display unit 140. The storage unit 110 can be realized by at least one of the above-described RAM 100B, ROM 100C, and NVM 100D. The processing unit 120 can be realized by the above-described CPU 100A. The input unit 130 can be realized by the above-described camera 100F and touch panel 100H. The display unit 140 can be realized by the above-described display 100I. The storage unit 110, the processing unit 120, the input unit 130, and the display unit 140 are connected to each other. The storage unit 110 includes a voting data storage unit 111. The processing unit 120 includes a reception unit 121 and a generation unit 122.

[0027] The reception unit 121 determines whether it has received a sharing instruction specifying a purchase target from the input unit 130. The purchase target is a combination of the numbers (such as horse numbers or race numbers) of the selected racehorses selected by the user P1 from among a plurality of racehorses. For example, when the user P1 operates the input unit 130 and a predetermined button displayed on the display unit 140 is pressed, the reception unit 121 determines that it has received a sharing instruction. When the reception unit 121 determines that it has received a sharing instruction, it generates voting data including the purchase target specified by the sharing instruction, and stores the generated voting data in the voting data storage unit 111.

[0028] As a result, the voting data storage unit 111 stores voting data including the purchase target of the user P1. As shown in FIG. 4, the voting data includes a plurality of items such as, for example, a voting data ID (Identifier), a purchase identification flag, a membership number, a voting date, a betting type, a purchase target, odds, and an amount. Note that the odds item may or may not be included.

[0029] In the item of the voting data ID, an identifier for identifying the voting data is registered. This identifier is dynamically numbered and assigned to the voting data when a button for confirming the voting content described later is pressed or a button for purchasing a lottery ticket is pressed. In the item of the purchase identification flag, an identifier for identifying whether it is before or after purchasing a lottery ticket is registered. When a button for confirming the voting content is pressed, the identifier "0" is registered in the item of the purchase identification flag. When a button for purchasing a lottery ticket is pressed, the identifier "1" is registered in the item of the purchase identification flag.

[0030] In the item of the member number, the member numbers of users P1 and P2 are registered for each user. The member number is dynamically numbered when the above-mentioned use registration is performed and is uniquely assigned to each of users P1 and P2. In the item of the voting date, the date when a button for confirming the voting content is pressed or the date when a button for purchasing a lottery ticket is pressed is registered in the YYYYMMDD format. In each item of the betting type, the betting number, and the amount, for example, the betting type, the betting number selected by the operation of user P1, and the amount input by the operation of user P1 are registered for each betting number. In the item of the odds, the odds calculated by the race operating company are registered. The voting data storage unit 111 can store a plurality of voting data.

[0031] Returning to Fig. 3(a), the generation unit 122 monitors the voting data storage unit 111 and determines whether voting data is stored in the voting data storage unit 111. When voting data is stored in the voting data storage unit 111, the generation unit 122 acquires the voting data from the voting data storage unit 111 and generates a two-dimensional code for sharing betting numbers corresponding to the acquired voting data from the acquired voting data. The two-dimensional code for sharing betting numbers is an example of an identifier.

[0032] Note that, although details will be described later, the two-dimensional code for sharing purchase items generated by the generation unit 122 is different from the above two-dimensional codes C1 and C2 prepared in advance for service use registration. When the generation unit 122 generates a two-dimensional code for sharing purchase items, the generated two-dimensional code is displayed on the display unit 140. As a result, a sharing guidance screen including the two-dimensional code generated by the generation unit 122 appears on the first mobile terminal 100.

[0033] Referring to FIG. 3(b), the functional configuration of the second mobile terminal 200 will be described. Note that in FIG. 3(b), the main parts of the functions of the second mobile terminal 200 are shown.

[0034] As shown in FIG. 3(b), the second mobile terminal 200 includes a storage unit 210, a processing unit 220, an input unit 230, and a display unit 240. Since the hardware corresponding to the storage unit 210, the processing unit 220, the input unit 230, and the display unit 240 is the same as that of the above-described storage unit 110, processing unit 120, input unit 230, and display unit 240, detailed description thereof will be omitted. The storage unit 210 includes a two-dimensional code storage unit 211. The processing unit 220 includes a reading unit 221, a specifying unit 222, and an output unit 223.

[0035] The reading unit 221 reads the two-dimensional code in the sharing guidance screen that appears on the first mobile terminal 100 based on the operation of the user P2. The reading unit 221 reads the two-dimensional code via the input unit 230. Here, the reading unit 221 includes a two-dimensional code reader. Therefore, the reading unit 221 can read the two-dimensional code using the two-dimensional code reader. When the reading unit 221 reads the two-dimensional code, the read two-dimensional code is stored in the two-dimensional code storage unit 211. As a result, the two-dimensional code storage unit 211 stores the two-dimensional code. Each time the reading unit 221 reads a two-dimensional code, the read two-dimensional code is stored in the two-dimensional code storage unit 211. Therefore, the two-dimensional code storage unit 211 may store a plurality of two-dimensional codes.

[0036] The specific unit 222 monitors the two-dimensional code storage unit 211 and determines whether a two-dimensional code is stored in the two-dimensional code storage unit 211. When a two-dimensional code is stored in the two-dimensional code storage unit 211, the specific unit 222 acquires the two-dimensional code from the two-dimensional code storage unit 211 and restores voting data from the two-dimensional code. For example, the specific unit 222 restores voting data from the two-dimensional code by analyzing or decrypting the two-dimensional code. Since the voting data includes the purchase items of user P1, the specific unit 222 identifies the purchase items of user P1 by restoring the voting data.

[0037] The output unit 223 displays the voting data identified by the specific unit 222 on the display unit 240. As a result, the purchase items included in the voting data appear on the second mobile terminal 200, and user P2 can confirm the purchase items of user P1. In this way, by the cooperation of the first mobile terminal 100 and the second mobile terminal 200, the purchase items are shared between user P1 and user P2.

[0038] Here, for example, it is also assumed that the purchase items are shared between user P1 and user P2 by transmitting a hard copy (so-called screenshot) of the screen including the purchase items from the first mobile terminal 100 to the second mobile terminal 200. However, by sharing the purchase items through the service application, the operation burden on user P2 is reduced. Specifically, user P2 can share the purchase items of user P1 with fewer operation times than when sharing with a hard copy of the screen including the purchase items, and can also avoid filling in the mark sheet method.

[0039] With reference to FIGS. 5 to 12, the operation of the first mobile terminal 100 will be described.

[0040] First, as shown in FIG. 5, the reception unit 121 displays a purchase screen (step S1). For example, when user P1 launches the service application installed on the first mobile terminal 100, as shown in FIG. 6, the reception unit 121 displays a ticket purchase screen 101 for horse racing tickets. The purchase screen 101 includes race numbers for which the finishing order of the running horses has been determined, race numbers for which the purchase of horse racing tickets has closed, and race numbers indicating the period during which the purchase of horse racing tickets is accepted (e.g., race number "8R"). Further, the purchase screen 101 includes a plurality of types of menu buttons BT1, BT2, BT3, and BT4. The menu buttons BT1, BT2, and BT3 are buttons for transitioning to another screen from the purchase screen 101. The menu button BT4 is a button for instructing the reading of a two-dimensional code for shared purchases.

[0041] Here, the reception unit 121 waits until it receives a first instruction (step S2: NO). For example, as shown in FIG. 6, when the menu button BT2 for issuing the first instruction is pressed by the finger of user P1, the reception unit 121 can receive the first instruction. Therefore, the reception unit 121 waits until the menu button BT2 is pressed.

[0042] When the first instruction is received (step S2: YES), the reception unit 121 displays a bet selection screen (step S3). As shown in FIG. 7, the bet selection screen 102 includes a selection button BT5 for selecting the number of the running horse, a selection button BT6 for selecting the betting type, and a screen transition button BT7 for issuing a second instruction.

[0043] Here, the reception unit 121 waits until it receives a second instruction (step S4: NO). For example, as shown in FIG. 7, when the selection buttons BT5 and BT6 are pressed by the finger of user P1 to indicate a bet, and the screen transition button BT7 for issuing the second instruction is pressed by the finger of user P1, the reception unit 121 can receive the second instruction. Therefore, the reception unit 121 waits until the screen transition button BT7 is pressed by the finger of user P1.

[0044] When the second instruction is received (step S4: YES), the reception unit 121 displays an amount input screen (step S5). As shown in FIG. 8, the amount input screen 103 includes an input field BX for inputting the bet amount for the purchase item instructed by the user P1 as the voting amount, and a screen transition button BT8 for issuing a third instruction. Although not shown, the amount input screen 103 includes software keys representing a numeric keypad near the input field BX.

[0045] Here, the reception unit 121 waits until the third instruction is received (step S6: NO). For example, when a software key is pressed by the finger of the user P1, and as shown in FIG. 8, the voting amount is input into the input field BX corresponding to the purchase item, and the screen transition button BT8 for issuing the third instruction is pressed by the finger of the user P1, the reception unit 121 can receive the third instruction. Therefore, the reception unit 121 waits until the screen transition button BT8 is pressed by the finger of the user P1.

[0046] When the third instruction is received (step S6: YES), the reception unit 121 determines the voting content (step S7) and displays a voting content confirmation screen (step S8). As shown in FIG. 9, the voting content confirmation screen 104 includes voting content such as the purchase item such as the horse number and combination number and the voting amount, a purchase button BT9 for instructing the purchase process of the lottery ticket specified by the purchase item, and a sharing button BT10 for instructing the sharing of the purchase item.

[0047] Here, the reception unit 121 waits until a sharing instruction or a fourth instruction is received (step S9: NO, step S10: NO). For example, as shown in FIG. 9, when the purchase button BT9 for issuing the fourth instruction is pressed by the finger of the user P1, the reception unit 121 can receive the fourth instruction. Also, as shown in FIG. 10, when the sharing button BT10 for issuing a sharing instruction specifying the purchase item is pressed by the finger of the user P1, the reception unit 121 can receive the sharing instruction. Therefore, the reception unit 121 waits until the purchase button BT9 or the sharing button BT10 is pressed by the finger of the user P1.

[0048] For example, when receiving the fourth instruction without receiving a sharing instruction (step S9: NO, step S10: YES), the reception unit 121 displays a purchase completion screen (step S11). As shown in FIG. 11, the purchase completion screen 105 includes a plurality of types of menu buttons BT1, BT2, BT3, BT4 and voting content. Further, the purchase completion screen 105 includes a reception number of the vote, a reception date and time of the vote, a total vote amount, and a sharing button BT10 for instructing sharing of the purchase item.

[0049] Here, the reception unit 121 determines whether or not it has received a sharing instruction (step S12). If it has not received a sharing instruction (step S12: NO), the first mobile terminal 100 ends a series of processes. For example, when the menu button BT1 that issues the fifth instruction is pressed by the finger of the user P1 without receiving a sharing instruction, the first mobile terminal 100 ends a series of processes.

[0050] On the other hand, as shown in FIGS. 10 and 11, when the sharing button BT10 that issues a sharing instruction is pressed by the finger of the user P1, the reception unit 121 can receive the sharing instruction. Therefore, in the processes of steps S9 and S10, when the reception unit 121 receives a sharing instruction without receiving the fourth instruction (step S9: YES, step S10: NO), or in the process of step S12, when the reception unit 121 receives a sharing instruction (step S12: YES), the generation unit 122 generates a two-dimensional code (step S13). More specifically, when receiving a sharing instruction, the reception unit 121 generates voting data including the purchase item specified by the sharing instruction. Thereby, the generation unit 122 can generate a two-dimensional code for sharing the purchase item according to the voting data from the voting data.

[0051] When the two-dimensional code is generated, the generation unit 122 displays the two-dimensional code on the display unit 140 (step S14). For example, when the sharing button BT10 is pressed on the voting content confirmation screen 104, as shown in FIG. 12, the generation unit 122 arranges and displays the two-dimensional code 13C for sharing the purchase item on the sharing guidance screen 13 that overlaps the voting content confirmation screen 104. The two-dimensional code 13C may be a QR code (registered trademark), or may be another two-dimensional code (for example, PDF417, etc.) other than the QR code (registered trademark).

[0052] When the generation unit 122 displays the two-dimensional code, the first mobile terminal 100 ends a series of processes. Although not shown, when the sharing button BT10 is pressed on the purchase completion screen 105, similar to the case of the voting content confirmation screen 104, the generation unit 122 arranges and displays the two-dimensional code 13C for sharing the purchase item on the sharing guidance screen 13 that overlaps the purchase completion screen 105. In this way, when the user P1 shares the purchase item with the user P2, the two-dimensional code 13C for sharing the purchase item to be presented to the user P2 is prepared in advance and waits.

[0053] Referring to FIGS. 13 and 14, the operation of the second mobile terminal 200 will be described.

[0054] First, when the user P2 starts the service application installed on the second mobile terminal 200, similar to the case of the first mobile terminal 100, the reading unit 221 displays the horse lottery purchase screen (see FIG. 6). Here, as shown in FIG. 13, the reading unit 221 waits until a reading instruction is received (step S21: NO). For example, as shown in FIG. 14(a), when the menu button BT4 for issuing a reading instruction is pressed by the finger of the user P2, the reading unit 221 can receive the reading instruction. Therefore, the reading unit 221 waits until the menu button BT4 is pressed.

[0055] When a reading instruction is received (step S21: YES), the reading unit 221 reads the two-dimensional code (step S22). For example, as shown in FIG. 14(a), the user P2 separates the second mobile terminal 200 from the first mobile terminal 100 and positions the reading frame 15 of the reading unit 221 at the two-dimensional code 13C. Thereby, the reading unit 221 can read the two-dimensional code 13C via the input unit 230. When the reading unit 221 reads the two-dimensional code, it stores the read two-dimensional code in the two-dimensional code storage unit 211.

[0056] When the reading unit 221 reads the two-dimensional code, the specifying unit 222 specifies a purchase item from the two-dimensional code read by the reading unit 221 (step S23). More specifically, the specifying unit 222 acquires the two-dimensional code from the two-dimensional code storage unit 211 and restores the voting data from the acquired two-dimensional code. The voting data includes the purchase item of the user P1. Therefore, the specifying unit 222 can specify the purchase item of the user P1 by restoring the voting data.

[0057] When the specifying unit 222 specifies the purchase item, the output unit 223 displays a predetermined screen including the purchase item specified by the specifying unit 222 on the display unit 240 (step S24). For example, when the sharing button BT10 is pressed on the voting content confirmation screen 104, as shown in FIG. 14(b), the output unit 223 displays a voting content confirmation screen 204 similar to the voting content confirmation screen 104 as the predetermined screen on the display unit 240. Thereby, the user P2 can receive the sharing of the purchase item of the user P1. Also, here, when the purchase button BT9 for accepting the purchase of the lottery ticket specified by the purchase item is pressed by the user P2, the lottery ticket displayed on the voting content confirmation screen 204 can be purchased. The purchase button BT9 is an example of the accepting means. Although not shown, when the sharing button BT10 is pressed on the purchase completion screen 105, the output unit 223 displays a purchase completion screen similar to the purchase completion screen 105 as the predetermined screen on the display unit 240. Thereby, the user P2 can share the purchase item of the user P1. When the output unit 223 displays the predetermined screen, the second mobile terminal 200 ends a series of processes.

[0058] As described above, according to this embodiment, the user P2 who is not used to purchasing lottery tickets can share the betting items of the user P1 who is used to purchasing lottery tickets. Therefore, the user P2 can make a decision on the betting items without difficulty. In addition, since the betting items can be shared through the service application, the user P2 can avoid the operation burden associated with filling in the mark sheet method when purchasing lottery tickets. Furthermore, since the service application is used, the user P2 can also avoid operations such as receiving a hard copy of the screen including the betting items from the first mobile terminal 100 or taking a photo of this screen. In this way, the race voting ticket purchase system ST1 can support the user P2 who is not used to purchasing lottery tickets.

[0059] Also, according to this embodiment, in each of the situations before and after the purchase of lottery tickets by the user P1, the user P2 can share the betting items with the user P1. Before purchasing lottery tickets, the user P2 can share the betting items that the user P1 plans to purchase. Thereby, the user P2 can grasp the tendency of the betting items in the consideration stage of the user P1. On the other hand, after purchasing lottery tickets, the user P2 can share the betting items that the user P1 actually purchased. Thereby, the user P2 can surely purchase the same betting items as those of the user P1.

[0060] (Third Embodiment) Referring to FIG. 15, the third embodiment will be described. For example, on the purchase screen 101 (see FIG. 6), when the menu button BT3 is pressed by the finger of the user P1, as shown in FIG. 15, the reception unit 121 displays the purchase history reference screen 106 on the display unit 140. The purchase history reference screen 106 includes the history of lottery tickets purchased by the user P1 and a sharing button BT10 for instructing sharing of betting items.

[0061] When the shared button BT10 is pressed by the finger of the user P1, the generation unit 122 generates a two-dimensional code for shared purchase based on all of the voting data according to the history of the horse race tickets. Thereby, similarly to the case described with reference to FIG. 12, the generation unit 122 can arrange and display the two-dimensional code for shared purchase on the shared guidance screen that overlaps the purchase history reference screen 106.

[0062] (First Embodiment) Referring to FIGS. 16 to 18, the first embodiment will be described. In the first embodiment, each of the browsers of the first mobile terminal 100 and the second mobile terminal 200 enjoys the service provided by the server device 300. According to the first embodiment, installation of the service application on the first mobile terminal 100 and the second mobile terminal 200 is avoided. As a result, consumption of the storage capacity of the memory provided in each of the first mobile terminal 100 and the second mobile terminal 200 is suppressed.

[0063] As shown in FIG. 16, the race voting ticket purchase system ST2 is realized by adding the server device 300 to the above-described first mobile terminal 100 and second mobile terminal 200. The server device 300 communicates wirelessly with the first mobile terminal 100 and the second mobile terminal 200 via the communication network NW and the mobile base station BS to cooperate. The server device 300 undertakes and executes a part of the processes executed by the first mobile terminal 100 and the second mobile terminal 200. Note that the communication network NW may include either or both of a LAN (Local Area Network) and the Internet.

[0064] Referring to FIG. 17, the hardware configuration of the server device 300 will be described.

[0065] As shown in FIG. 17, the server device 300 includes a CPU 300A, a RAM 300B, and a ROM 300C. The server device 300 includes a network I / F (interface) 300D and an HDD (Hard Disk Drive) 300E. Instead of the HDD 300E, an SSD (Solid State Drive) may be employed.

[0066] The server device 300 may include at least one of an input I / F 300F, an output I / F 300G, an input / output I / F 300H, and a drive device 300I as necessary. From the CPU 300A to the drive device 300I, they are connected to each other by an internal bus 300J. That is, the server device 300 can be realized by a computer.

[0067] An input device 710 is connected to the input I / F 300F. Examples of the input device 710 include a keyboard, a mouse, a touch panel, etc. A display device 720 is connected to the output I / F 300G. Examples of the display device 720 include a liquid crystal display. A semiconductor memory 730 is connected to the input / output I / F 300H. Examples of the semiconductor memory 730 include a USB (Universal Serial Bus) memory, a flash memory, etc. The input / output I / F 300H reads the race ticket purchase program stored in the semiconductor memory 730. The input I / F 300F and the input / output I / F 300H are provided with, for example, USB ports. The output I / F 300G is provided with, for example, a display port.

[0068] A portable recording medium 740 is inserted into the drive device 300I. Examples of the portable recording medium 740 include removable disks such as a CD (Compact Disc)-ROM and a DVD (Digital Versatile Disc). The drive device 300I reads the race ticket purchase program recorded on the portable recording medium 740. The network I / F 300D is provided with, for example, a LAN port, a communication circuit, etc. The communication circuit includes either one or both of a wired communication circuit and a wireless communication circuit. The network I / F 300D is connected to the communication network NW described above.

[0069] In the RAM 300B, a race ticket purchase program stored in at least one of the ROM 300C, the HDD 300E, and the semiconductor memory 730 is temporarily stored by the CPU 300A. In the RAM 300B, a race ticket purchase program recorded on the portable recording medium 740 is temporarily stored by the CPU 300A. By executing the stored race ticket purchase program by the CPU 300A, the CPU 300A executes a race ticket purchase method including various processes described later. Note that the race ticket purchase program may be in accordance with the flowchart described later.

[0070] Referring to FIG. 18, the operation of the server device 300 will be described. Note that various screens displayed on the first portable terminal 100 and the second portable terminal 200 are basically the same as the screens described with reference to FIGS. 6 to 12 and FIGS. 14(a) and (b). For this reason, detailed description of the screens will be omitted.

[0071] As shown in FIG. 18, the server device 300 displays a purchase screen on the first portable terminal 100 (step S31). For example, when the first portable terminal 100 accesses the server device 300 based on the operation of the user P1, the server device 300 displays a horse race ticket purchase screen 101 (see FIG. 6). The server device 300 waits until it receives a first instruction from the first portable terminal 100 (step S32: NO). As described above, the server device 300 waits until the menu button BT2 (see FIG. 6) of the first portable terminal 100 is pressed.

[0072] When the first instruction is received (step S32: YES), the server device 300 displays a purchase item selection screen on the first mobile terminal 100 (step S33). The server device 300 waits until a second instruction from the first mobile terminal 100 is received (step S34: NO). For example, when the selection buttons BT5, BT6 (see FIG. 7) are pressed by the finger of the user P1 to indicate a purchase item and the screen transition button BT7 (see FIG. 7) for issuing the second instruction is pressed by the finger of the user P1, the server device 300 can receive the second instruction. Therefore, the server device 300 waits until the screen transition button BT7 is pressed by the finger of the user P1.

[0073] When the second instruction is received (step S34: YES), the server device 300 displays an amount input screen on the first mobile terminal 100 (step S35). The server device 300 waits until a third instruction from the first mobile terminal 100 is received (step S36: NO). For example, when a voting amount is input in the input field BX (see FIG. 8) and the screen transition button BT8 (see FIG. 8) for issuing the third instruction is pressed by the finger of the user P1, the server device 300 can receive the third instruction. Therefore, the server device 300 waits until the screen transition button BT8 is pressed by the finger of the user P1.

[0074] When the third instruction is received (step S36: YES), the server device 300 determines the voting content (step S37) and displays a voting content confirmation screen on the first mobile terminal 100 (step S38). The server device 300 waits until a sharing instruction or a fourth instruction from the first mobile terminal 100 is received (step S39: NO, step S40: NO).

[0075] For example, when the purchase button BT9 (see FIG. 9) that issues the fourth instruction is pressed by the finger of user P1, the server device 300 can receive the fourth instruction. Also, when the sharing button BT10 (see FIG. 10) that issues a sharing instruction specifying a purchase item is pressed by the finger of user P1, the server device 300 can receive the sharing instruction. Therefore, the server device 300 waits until either the purchase button BT9 or the sharing button BT10 is pressed by the finger of user P1.

[0076] For example, if the fourth instruction is received without receiving a sharing instruction (step S39: NO, step S40: YES), the server device 300 displays a purchase completion screen on the first mobile terminal 100 (step S41). Here, the server device 300 determines whether it has received a sharing instruction from the first mobile terminal 100 (step S42). If the sharing instruction has not been received (step S42: NO), the server device 300 ends the series of processes. For example, if the menu button BT1 (see FIG. 11) that issues the fifth instruction is pressed by the finger of user P1 without receiving a sharing instruction, the server device 300 ends the series of processes.

[0077] On the other hand, when the sharing button BT10 (see FIGS. 10 and 11) that issues a sharing instruction is pressed by the finger of user P1, the server device 300 can receive the sharing instruction. Therefore, in the processes of steps S39 and S40, if the server device 300 receives a sharing instruction without receiving the fourth instruction (step S39: YES, step S40: NO), or in the process of step S42, if the server device 300 receives a sharing instruction (step S42: YES), the server device 300 generates a two-dimensional code (step S43).

[0078] More specifically, when a sharing instruction is received, the server device 300 generates voting data including the purchase item specified by the sharing instruction. Thereby, the server device 300 can generate a two-dimensional code for sharing the purchase item according to the voting data from the voting data.

[0079] When generating a two-dimensional code, the server device 300 displays the two-dimensional code on the first mobile terminal 100 (step S44). For example, when the sharing button BT10 (see FIG. 10) is pressed on the voting content confirmation screen 104, the server device 300 arranges and displays the two-dimensional code 13C for ticket sharing on the sharing guidance screen 13 that overlaps the voting content confirmation screen 104 (see FIG. 12).

[0080] When the server device 300 displays the two-dimensional code on the first mobile terminal 100, the server device 300 waits until it receives a reading instruction from the second mobile terminal 200 (step S45: NO). For example, when the second mobile terminal 200 accesses the server device 300 based on the operation of user P2, the server device 300 displays the ticket purchase screen 101 (see FIG. 6). Then, when the menu button BT4 (see FIG. 14(a)) for issuing a reading instruction is pressed by the finger of user P2, the server device 300 can receive the reading instruction. Therefore, the server device 300 waits until the menu button BT4 is pressed.

[0081] When receiving a reading instruction (step S45: YES), the server device 300 acquires a URL (Uniform Resource Locator) from the second mobile terminal 200 (step S46). For example, when receiving a reading instruction, the server device 300 transmits a web page including JavaScript (registered trademark) to the second mobile terminal 200. When the reading unit 221 of the second mobile terminal 200 receives the web page, it activates the input unit 230 based on JavaScript (registered trademark).

[0082] Specifically, the reading unit 221 activates the camera realized by the input unit 230. User P2 separates the second mobile terminal 200 from the first mobile terminal 100 and positions the reading frame 15 of the reading unit 221 on the two-dimensional code 13C (see FIG. 14(a)). Thereby, the reading unit 221 can read the two-dimensional code 13C via the input unit 230.

[0083] When the reading unit 221 reads a two-dimensional code, it analyzes the read two-dimensional code in JavaScript (registered trademark) and extracts the URL included in the two-dimensional code. The URL extracted by the reading unit 221 is information for specifying the items of interest that the server device 300 holds as data to be shared. By the reading unit 221 sending the URL to the server device 300 and requesting the items of interest, the server device 300 can acquire the URL and provide the items of interest of user P1 to the second mobile terminal 200.

[0084] When acquiring the URL, the server device 300 specifies the items of interest from the URL (step S47). More specifically, the server device 300 specifies the item of interest corresponding to the URL from among a plurality of items of interest stored in the server device 300. When the server device 300 specifies the item of interest, the server device 300 displays a predetermined screen including the specified item of interest on the second mobile terminal 200 (step S48).

[0085] For example, when the share button BT10 (see FIG. 10) is pressed on the vote content confirmation screen 104, the server device 300 displays a vote content confirmation screen 204 similar to the vote content confirmation screen 104 as a predetermined screen on the second mobile terminal 200 (see FIG. 14(b)). Thereby, user P2 can receive the sharing of the items of interest of user P1.

[0086] Although not shown, when the share button BT10 (see FIG. 11) is pressed on the purchase completion screen 105, the server device 300 displays a purchase completion screen similar to the purchase completion screen 105 as a predetermined screen on the second mobile terminal 200. Thereby, user P2 can share the items of interest of user P1. When the server device 300 displays the predetermined screen, the server device 300 ends a series of processes.

[0087] In this way, the server device 300 waits until it receives from the first mobile terminal 100 a sharing instruction that specifies the combination of the numbers of the selected racehorses from among a plurality of racehorses, which is the combination of numbers of the horses to bet on selected by the user P1. The first mobile terminal 100 transmits the sharing instruction wirelessly to the server device 300. As a result, the sharing instruction reaches the server device 300 via the mobile base station BS and the communication network NW.

[0088] When the server device 300 determines that it has received the sharing instruction, it generates a two-dimensional code for sharing the combination of numbers of the horses to bet on according to the combination of numbers of the horses to bet on, and displays it on the first mobile terminal 100. As a result, a sharing guidance screen including the two-dimensional code for sharing the combination of numbers of the horses to bet on appears on the first mobile terminal 100 in the same manner as described with reference to FIG. 12. As a result, the second mobile terminal 200 of the user P2 can read the two-dimensional code that appears on the first mobile terminal 100 from the first mobile terminal 100.

[0089] The server device 300 waits until it acquires the URL included in the two-dimensional code from the second mobile terminal 200. The second mobile terminal 200 transmits the URL wirelessly to the server device 300. As a result, the URL reaches the server device 300 via the mobile base station BS and the communication network NW.

[0090] When the server device 300 acquires the URL transmitted from the second mobile terminal 200, it specifies the combination of numbers of the horses to bet on of the user P1 from the URL, and displays the specified combination of numbers of the horses to bet on on the second mobile terminal 200. As a result, the combination of numbers of the horses to bet on of the user P1 appears on the second mobile terminal 200 in the same manner as described with reference to FIG. 14(b). In this way, even if the user P2 is not used to purchasing lottery tickets or determining the combination of numbers of the horses to bet on, the user P2 can easily share the combination of numbers of the horses to bet on of the user P1.

[0091] As described above in detail are the preferred embodiments of the present invention. However, the present invention is not limited to the specific embodiments described, and various modifications and changes are possible within the scope of the gist of the present invention described in the claims. For example, instead of the two-dimensional codes 11C and 12C, NFC (Near Field Communication) tag seals may be attached to the guide plates 11 and 12.

[0092] In addition, the following supplementary notes are disclosed regarding the above description. (Supplementary Note 1) A race ticket purchase method for assisting the purchase of a race ticket by the second user by a computer that communicates between the first terminal of the first user and the second terminal of the second user, which, when it is determined that a sharing instruction identifying a purchase target selected by the first user from among a plurality of voting targets is received from the first terminal, displays an identifier corresponding to the purchase target on the first terminal, identifies the purchase target from the identifier read by the second terminal from the first terminal, and displays the identified purchase target on the second terminal, and the computer executes the process. (Supplementary Note 2) The race ticket purchase method according to Supplementary Note 1, characterized in that a reception means for receiving the purchase of a race ticket specified by the displayed purchase target is displayed on the second terminal. (Supplementary Note 3) The race ticket purchase method according to Supplementary Note 1 or 2, characterized in that the identifier is a two-dimensional code. (Supplementary Note 4) The race ticket purchase method according to Supplementary Note 1 or 2, characterized in that the plurality of voting targets are any one of a plurality of animals, a plurality of persons, and a plurality of vehicles. (Appendix 5) A race ticket purchase program for a computer that communicates with a first terminal of a first user and a second terminal of a second user to assist the second user in purchasing a race ticket. When it is determined that a sharing instruction specifying a purchase target, which is a voting target selected by the first user from among a plurality of voting targets, has been received from the first terminal, an identifier corresponding to the purchase target is displayed on the first terminal, the purchase target is specified from the identifier read by the second terminal from the first terminal, and the specified purchase target is displayed on the second terminal. A race ticket purchase program for causing a computer to execute the process. (Appendix 6) A race ticket purchase program in which a first terminal of a first user and a second terminal of a second user cooperate to assist the second user in purchasing a race ticket. When it is determined that a sharing instruction specifying a purchase target, which is a voting target selected by the first user from among a plurality of voting targets, has been received from the first terminal, an identifier corresponding to the purchase target is displayed on the first terminal, the purchase target is specified from the identifier read by the second terminal from the first terminal, and the specified purchase target is displayed on the second terminal. A race ticket purchase program for causing a computer to execute the process. (Appendix 7) A race ticket purchase program in which a first terminal of a first user cooperates with a second terminal of a second user to assist the second user in purchasing a race ticket. When it is determined that a sharing instruction specifying a purchase target, which is a voting target selected by the first user from among a plurality of voting targets, has been received by a computer included in the first terminal, a process of displaying an identifier corresponding to the purchase target is executed. A race ticket purchase program characterized by this. (Appendix 8) A race ticket purchase program in which a second terminal of a second user cooperates with a first terminal of a first user to assist the second user in purchasing a race ticket. A computer included in the second terminal reads an identifier corresponding to a purchase target, which is a voting target selected by the first user from among a plurality of voting targets, from the first terminal, specifies the purchase target from the read identifier, and executes a process of displaying the specified purchase target. A race ticket purchase program characterized by this.

Explanation of Symbols

[0093] 11C, 12C, 13C Two-dimensional Code 100 First Mobile Terminal 200 Second Mobile Terminal 300 Server Device BT4 Menu Button BT9 Purchase Button BT10 Sharing Button P1, P2 Users ST1, ST2 Race Voting Ticket Purchase System

Claims

1. A race ticket purchase method for assisting the purchase of a race ticket by a second user by a computer that communicates with a first terminal of a first user and a second terminal of a second user, comprising: When it is determined that a sharing instruction identifying a purchase target, which is a voting target selected by the first user from a plurality of voting targets, is received from the first terminal, an identifier corresponding to the purchase target is displayed on the first terminal; Identifying the purchase target from the identifier read by the second terminal from the first terminal; Displaying the identified purchase target on the second terminal; A race ticket purchase method in which the computer executes the process.

2. Displaying, on the second terminal, a reception means for receiving a purchase of a race ticket specified by the displayed purchase target; The race ticket purchase method according to claim 1, characterized in that.

3. A race ticket purchase program for assisting the purchase of a race ticket by a second user by a computer that communicates with a first terminal of a first user and a second terminal of a second user, comprising: When it is determined that a sharing instruction identifying a purchase target, which is a voting target selected by the first user from a plurality of voting targets, is received from the first terminal, an identifier corresponding to the purchase target is displayed on the first terminal; Identifying the purchase target from the identifier read by the second terminal from the first terminal; Displaying the identified purchase target on the second terminal; A race ticket purchase program for causing the computer to execute the process.

4. A race ticket purchase program for assisting the purchase of a race ticket by a second user in cooperation between a first terminal of a first user and a second terminal of a second user, comprising: When it is determined that a sharing instruction identifying a purchase target, which is a voting target selected by the first user from a plurality of voting targets, is received from the first terminal, an identifier corresponding to the purchase target is displayed on the first terminal; Identifying the purchase target from the identifier read by the second terminal from the first terminal; Displaying the identified purchase target on the second terminal; A race ticket purchase program for causing a computer to execute the process.

5. A race ticket purchase program for assisting the purchase of a race ticket by a second user in cooperation between a first terminal of a first user and a second terminal of a second user, wherein: On the computer included in the first terminal When it is determined that a shared instruction specifying a purchase target, which is a voting target selected by the first user from among a plurality of voting targets, has been received, a process of displaying an identifier corresponding to the purchase target is executed. A race ticket purchase program characterized by the above.

6. A race ticket purchase program in which a second terminal of a second user cooperates with a first terminal of a first user to support the purchase of a race ticket by the second user, on a computer included in the second terminal, reads an identifier corresponding to a purchase target, which is a voting target selected by the first user from among a plurality of voting targets, from the first terminal, identifies the purchase target from the read identifier, and displays the identified purchase target. A race ticket purchase program characterized by executing the process.

Images