JP6033268B2 - Program and information processing apparatus - Google Patents

Description

  The present invention relates to a program and an information processing apparatus used for a plurality of applications related to gaming machines.

  2. Description of the Related Art Conventionally, a technique for transmitting and receiving data generated from an application provided via a communication network such as the Internet, a LAN (Local Area Network), or a mobile phone network is known between a plurality of terminal devices.

  For example, Patent Document 1 discloses a technique for providing an event to a user of a terminal device and controlling the number of event occurrences according to the number of users.

JP 2013-128603 A

  However, the technique described in Patent Document 1 is based on data generated from one application provided by one developer. For this reason, when trying to link with an application provided by a developer different from the one developer, the development period will be prolonged or the cost will increase due to redevelopment to the specifications tailored to each application. As a result, it was difficult to link apps.

  In one aspect, it is an object of the present invention to provide a program and an information processing apparatus that can facilitate cooperation between a plurality of applications with different developers.

The program according to one aspect is a first application provided with the name of a first developer that generates game data, the first application being a simulation game imitating a ball game machine or a revolving game machine, and the program A central device that performs processing related to a second application , which is a second application provided with a second developer name different from the first developer name, which is a simulation game imitating a ball game machine or a revolving game machine a program used for, first the generated by the first application, acquired from the terminal device connected via a communication network game data indicative of a predetermined game result of the first application, is the acquisition the game data generated by one application, generated by the second application that has already been acquired, processing der managing integrated with game data indicating a predetermined game result of the second application Te, the value of a predetermined game result of the second application, adds the value of a predetermined game result of the first application.

  According to one aspect, it is possible to facilitate cooperation between a plurality of applications with different developers.

It is a schematic diagram which shows the outline | summary of an information processing system. It is a block diagram which shows the hardware group of information processing apparatus. It is a figure which shows an example of the data stored in user DB. It is a figure which shows an example of the data stored in application DB. It is a figure which shows an example of the data stored in the adjustment result DB. It is a block diagram which shows the hardware group of a terminal device. It is explanatory drawing which shows an example of the screen layout of an application selection screen. It is explanatory drawing which shows an example of the screen layout of a mode selection screen. It is explanatory drawing which shows an example of the screen layout of an application screen and a common application screen. It is explanatory drawing which shows an example of the screen layout of the common application screen which performed the common application and the 1st application, or the 2nd application. It is explanatory drawing which shows an example of the screen layout of a home screen. It is explanatory drawing which shows an example of the screen layout of a confirmation screen. It is explanatory drawing which shows an example of the screen layout of a payment screen. It is the flowchart which showed the process sequence of the encryption process in this embodiment. It is the flowchart which showed the process sequence of the encryption process in this embodiment. It is the flowchart which showed the process sequence of the encryption process in this embodiment. It is the flowchart which showed the process sequence of the encryption process in this embodiment. It is the flowchart which showed the process sequence of the encryption process in this embodiment. 6 is a block diagram illustrating a hardware group of an information processing apparatus according to Embodiment 2. FIG. It is a figure which shows an example of the data stored in user DB which concerns on Embodiment 2. FIG. It is a figure which shows an example of the data stored in emblem DB. It is explanatory drawing which shows an example of the screen layout of an emblem screen. It is explanatory drawing which shows an example of the screen layout of a friend screen. 5 is a flowchart illustrating an information processing system according to a second embodiment. 5 is a flowchart illustrating an information processing system according to a second embodiment. 5 is a flowchart illustrating an information processing system according to a second embodiment. FIG. 10 is a block diagram illustrating a hardware group of an information processing device according to a third embodiment. It is a figure which shows an example of the data stored in ranking DB. 10 is an explanatory diagram illustrating an example of a screen layout of a home screen according to Embodiment 3. FIG. It is explanatory drawing which shows an example of the screen layout of a ranking screen. 10 is a flowchart illustrating an information processing system according to a third embodiment.

Embodiment 1
Hereinafter, the present embodiment will be described with reference to the drawings. In the following description, top, bottom, left and right in each figure are used. FIG. 1 is a schematic diagram showing an outline of an information processing system. The information processing system is a terminal composed of an information processing device (central device) 1 and a terminal device (information processing device) 2A, 2B, 2C, or the like connected via a communication network N such as the Internet, a LAN, or a mobile phone network. The apparatus 2 is provided. The information processing apparatus 1 is, for example, a server computer or a personal computer. The information processing apparatus 1 in the present embodiment will be described as a server computer. The terminal device 2 is a mobile phone, a smartphone, a personal computer, or the like. The terminal device 2 in the present embodiment will be described as a mobile phone.

  An overview of the information processing system in the present embodiment will be described. The terminal device 2 outputs an acquisition request for a common app that can be used by a plurality of apps to the information processing device 1. In this specification, an application is, for example, a simulation game that imitates a ball game machine or a revolving game machine. The common application is a function for transmitting / receiving at least user game data to / from the information processing apparatus 1, and is a common module that can be installed in the application regardless of the developer. In this embodiment, a mode in which a common application is implemented in an application will be described. However, in the present embodiment, the common application may be software that operates independently on the terminal device 2.

  The terminal device 2 executes the application together with the application or the common application, and generates game data. The generated game data is output or acquired between the information processing device 1 and the terminal device 2. Details of the information processing system in the present embodiment will be described below.

  FIG. 2 is a block diagram illustrating a hardware group of the information processing apparatus 1. 2 includes a CPU (Central Processing Unit) 11, a storage unit 12, a RAM 13, an input unit 14, a display unit 15, and a communication unit 16.

  The CPU 11 is connected to each part of hardware via a bus. The CPU 11 includes, for example, one or a plurality of CPUs or a multi-core CPU. The CPU 11 performs control of each part of the hardware in accordance with the program 12P stored in the storage unit 12, for example, SRAM, DRAM, flash memory, or the like. The RAM 13 also functions as a storage unit, and temporarily stores various data generated when the CPU 11 executes various programs. The storage unit 12 is a nonvolatile memory such as an EEPROM (Electrically Erasable Programmable Read-Only Memory). The storage unit 12 stores various data required when the CPU 11 performs processing, a user DB 121, an application DB 122, a settlement result DB 123, and a program 12P. The input unit 14 is an input device such as a mouse, a keyboard, or a touch panel, and outputs received operation information to the CPU 11. The display unit 15 is a liquid crystal display or an organic EL (Electro Luminescence) display. The communication unit 16 is, for example, a wireless LAN card or a mobile phone communication module, and transmits / receives various information to / from the terminal device 2 via the communication network N.

  FIG. 3 is a diagram illustrating an example of data stored in the user DB 121. The user DB 121 is a database that stores the correspondence between users and applications. The user DB 121 includes a user ID column, a user name column, an application ID column, a cumulative experience value column, a level column, and a cumulative virtual money column. The user ID column stores user IDs (specific information) for specifying users who execute each of the plurality of applications. The name of the user is stored in the user name column. The application ID column stores an application ID for identifying each of a plurality of applications (applications). The accumulated experience value column stores accumulated experience values accumulated from the first execution of the application to the present. The level column stores a level determined according to the experience value. The accumulated virtual money column stores the accumulated virtual money accumulated from the first execution of the application to the present. Virtual money is money that can be used in a common application.

  The CPU 11 refers to the user DB 121 and determines whether there is game data generated by a first application or a second application described later. The game data includes, for example, the number of revolutions, difference ball, jackpot number, maximum number of consecutive Changs, short-time middle-big hit number, acquired experience value, acquired currency, accumulated experience value, accumulated virtual currency or level. The CPU 21 stores game data in the settlement result DB 123. When the CPU 11 determines that there is game data generated by the first application or the second application, the CPU 11 combines the game data generated by the first application or the second application with the game data generated by the running application. The CPU 11 stores game data combined with the accumulated experience value sequence, the level sequence, and the accumulated virtual currency sequence in the user DB 121. In the present embodiment, it is assumed that a first application described later is executed in advance, and game data is stored in the user DB 121.

  FIG. 4 is a diagram illustrating an example of data stored in the application DB 122. The application DB 122 is a database that stores information related to applications. The application DB 122 includes an application ID column, a developer column, an icon column, an application column, a name column, and the like.

  An application ID is stored in the application ID column. In the developer column, a developer name (developer name) indicating the name of the developer is stored. A developer is, for example, a developer of a company, brand, or individual who developed an application. In the icon column, an icon associated with the application ID is stored. An application associated with the application ID is stored in the application column. The name column stores the name of the application. In this embodiment, as shown in FIG. 4, the application ID 001 is provided by the developer A name, the application ID 002 is provided by the developer B name, and the application ID 003 is provided by the developer C name. Is.

In the present embodiment, as illustrated in FIG. 3, the information processing apparatus 1 manages a user ID for identifying a user and an application ID for identifying an application in association with each other, and is associated with each user ID. The game data of the application corresponding to each application ID is integrated and managed. Therefore, in FIG. 3, for example, for the user ID 0001, predetermined game results of three applications (application IDs 001, 002, 003) with different developers are integrated and managed. Therefore, even if new game data of app A (app ID 001), app B (app ID 002), or app C (app ID 003) is sent from the terminal device 2 specified by the user ID 0001, the game Regardless of the developer of the application that generated the data, the information processing apparatus 1 can reflect the new game data in the game data accumulated (integrated) so far.
In the present embodiment, when the game data is transmitted to the information processing apparatus 1, the common application installed in each application transmits the game data, the user ID, and the application ID to the information processing apparatus 1. Upon receiving these data, the information processing apparatus 1 updates each database shown in FIGS. 5 and 3 described later. That is, for game data to be integrated and managed, the database is updated by adding a predetermined value according to newly received game data.
Now, an example of a method for creating the user DB 121 shown in FIG. 3 will be described. In this embodiment, the common application transmits a user ID and an application ID to the information processing apparatus 1 when an application in which the common application is installed is activated. When the received user ID and application ID are not managed in association with each other in the user DB 121 shown in FIG. 3, the information processing apparatus 1 registers these data in association with the database. Note that the information processing apparatus 1 uses the user ID as a reference when constructing the database shown in FIG. Therefore, for each user ID, the application ID associated therewith is managed in association with the developer regardless of the developer.

  FIG. 5 is a diagram illustrating an example of data stored in the settlement result DB 123. The settlement result DB 123 is a database that stores game data generated by the application. The settlement result DB 123 includes a user ID column, an application ID column, a rotation number column, a difference ball column, a jackpot number column, an acquired experience value column, an acquired money column, and the like. Since the user ID column and application ID column of the settlement result DB 123 are the same as the operation and action of the user ID column and application ID column of the application DB 122, description thereof is omitted. That is, FIG. 5 is a database for managing game data for each play for each application owned by each user.

  The rotation number column stores the number of rotations of the slot, which is one time from when the number of the slot operates until it stops. A difference ball indicating a difference between the pachinko ball acquired by the user and the lost pachinko ball is stored in the difference ball row. The number of jackpots is stored in the jackpot number column. In the acquired experience value column, an acquired experience value indicating an experience value acquired from the execution of the application until the end of the application is stored. In the acquired money column, acquired money indicating virtual money acquired from the execution of the application to the end of the application is stored.

  The settlement result DB 123 is not limited to this. You may provide the highest consecutive resort frequency sequence or the time short, middle and big hit frequency sequence. The highest consecutive resort count column stores the highest consecutive resort count among the user's consecutive resort counts. The short-time, middle-big hit count column indicates the number of jackpots made during the opening of the digital shortening function or the electric accessory indicating that the rotation time of the slot is shortened.

  In the present embodiment, at the time of transmission of game data to the information processing apparatus 1, the common application transmits game data, a user ID, and an application ID. When receiving the data, the information processing apparatus 1 registers the received game data, user ID, and application ID in association with each other in the database shown in FIG.

  FIG. 6 is a block diagram illustrating a hardware group of the terminal device 2. The terminal device 2 illustrated in FIG. 6 includes a CPU 21, a storage unit 22, a RAM 23, an input unit 24, a display unit 25, and a communication unit 26. The operations and operations of the CPU 21, RAM 23 and communication unit 26 of the terminal device 2 are the same as the operations and operations of the CPU 11, RAM 13 and communication unit 16 of the information processing apparatus 1, and are not described for the sake of brevity.

  The storage unit 22 is, for example, an EEPROM, a hard disk, or a flash memory. The storage unit 22 stores various data necessary for the CPU 21 to perform processing, an application DB 221, a settlement result DB 222, a common application, and a program 22P. The input unit 24 is an input device such as a touch panel, and outputs received operation information to the CPU 21. The display unit 25 outputs the image data output from the CPU 21. The display unit 25 is a liquid crystal screen, for example. The touch panel is provided so as to cover the display screen of the display unit 25. For example, the touch panel receives a position designation on the display screen of the display unit 25 by a touch operation of a user's fingertip such as a tap, flick, or swipe. The input unit 24 may be various buttons for receiving user instructions, an enter key or a numeric keypad for receiving confirmation of instructions. The operations and operations of the application DB 221 and the settlement result DB 222 are the same as those of the application DB 122 and the settlement result DB 123, and the description is omitted for the sake of brevity. In the present embodiment, it is assumed that the application is installed in the terminal device 2.

  FIG. 7 is an explanatory diagram showing an example of the screen layout of the application selection screen 3. The application selection screen 3 is a screen for selecting an application. The application selection screen 3 includes an icon 31 configured by an icon 31A, 31B, 31C or the like provided at the upper end.

  The operation and operation of the application selection screen 3 are as follows. When the user performs a touch operation on any one of the plurality of icons 31, the CPU 21 refers to the application DB 221 to activate the application associated with the icon 31. For example, when the user performs a touch operation on the icon 31A, the CPU 21 refers to the application DB 221 to activate the application A associated with the icon A that is the same icon as the icon 31A. The CPU 21 displays the mode selection screen 5 on the display unit 25.

  FIG. 8 is an explanatory diagram showing an example of the screen layout of the mode selection screen 5. The mode selection screen 5 is a screen for selecting an application mode. As shown in FIG. 8, the mode selection screen 5 includes a normal button 50 provided at the lower left, a common application button 51 provided at the lower right, a developer name 52 provided at the lower right corner, and a lower end. And a link 53 provided in

  The operation and operation of the mode selection screen 5 are as follows. When the user performs a touch operation on the normal button 50, the CPU 21 displays an application screen 61 that is a screen on which the application associated with the application ID is executed on the display unit 25. For example, the CPU 21 executes the application A associated with the application ID “001”. When the user performs a touch operation on the common application button 51, the CPU 21 refers to the application DB 122 and executes the application associated with the application ID and the common application stored in the storage unit 22. For example, the CPU 21 executes the application A associated with the application ID “001” and the common application stored in the storage unit 22. The CPU 21 displays on the display unit 25 a common application screen 62 that is a screen on which the application associated with the application ID and the common application stored in the storage unit 22 are executed.

  When the user performs a touch operation on the link 53, the CPU 21 outputs a user ID and an acquisition request for a home screen 7 described later to the information processing apparatus 1. The CPU 11 acquires a user ID and an acquisition request for the home screen 7 from the terminal device 2. The CPU 11 refers to the user DB 121 and the application DB 122 to generate the home screen 7. The CPU 11 outputs the home screen 7 to the terminal device 2. The CPU 21 acquires the home screen 7 from the information processing apparatus 1. The CPU 21 displays the home screen 7 on the display unit 25.

  FIG. 9 is an explanatory diagram showing an example of the screen layout of the application screen 61 and the common application screen 62. FIG. 9A is an explanatory diagram showing the application screen 61. FIG. 9B is an explanatory diagram showing the common application screen 62 before the menu 60 is touched. FIG. 9C is an explanatory diagram showing the common application screen 62 after the menu 60 is touched. As shown in FIGS. 9B and 9C, the common application screen 62 includes a menu 60 provided at the lower left. As shown in FIG. 9C, the menu 60 includes a settlement button 601 and a home button 602.

  The operation and operation of the application screen 61 and the common application screen 62 are as follows. When the user touches various buttons (not shown) on the application screen 61, the CPU 21 generates game data for the application (FIG. 9A).

  When the user touches various buttons (not shown) on the common application screen 62, the CPU 21 generates game data for the application (FIG. 9B). When the user performs a touch operation on the menu 60, the CPU 21 extends the display of the menu 60 to the right side, and displays the settlement button 601 and the home button 602 on the menu 60 (FIG. 9C).

  When the user touches the home button 602, the CPU 21 outputs a user ID and an acquisition request for a home screen 7 described later to the information processing apparatus 1. The CPU 11 acquires a user ID and an acquisition request for the home screen 7 from the terminal device 2. The CPU 11 refers to the user DB 121 and the application DB 122 to generate the home screen 7. The CPU 11 outputs the home screen 7 to the terminal device 2. The CPU 21 acquires the home screen 7 from the information processing apparatus 1. The CPU 21 displays the home screen 7 on the display unit 25.

  When the user touches the settlement button 601, the CPU 21 acquires operation information and outputs the user ID, application ID, and game data to the information processing apparatus 1. The CPU 11 acquires a user ID, an application ID, and game data from the terminal device 2. The CPU 11 refers to the user DB 121 and generates the confirmation screen 8 based on the user ID, application ID, and game data. The confirmation screen 8 is a screen for confirming game data. The CPU 11 outputs the generated confirmation screen 8 to the terminal device 2. The CPU 11 acquires the confirmation screen 8 from the information processing apparatus 1. The CPU 11 outputs the confirmation screen 8 to the display unit 25.

  FIG. 10 is an explanatory diagram illustrating an example of a screen layout of the common application screen 62 that executes the common application and the first application or the second application. The first application is an application relating to a gaming machine provided by the first developer name. The first application is, for example, application A. The second application is an application related to a gaming machine provided with a second developer name different from the first application name. The second application is, for example, application B. FIG. 10A shows a common application screen 62 in which the common application and the first application are executed. FIG. 10B shows a common application screen 62 in which the common application and the second application are executed.

  As shown in FIGS. 10A and 10B, when the common app and the first app or the second app are executed, the common app screen 62 includes a menu 60 at the same position in each of the first app and the second app. The menu 60 performs the same operation and operation in each of the first application and the second application.

  FIG. 11 is an explanatory diagram showing an example of the screen layout of the home screen 7. The home screen 7 is a screen that displays information related to the common application. The home screen 7 includes a return button 70 provided at the upper right corner, a virtual money field 700 provided at the lower part of the back button 70, an experience value field 701 provided at the left part of the virtual money field 700, an experience A level field 702 provided in the upper part of the value field 701 and an icon 71 constituted by icons 71A, 71B, 71C, etc. are provided in the lower part.

  A specific method for generating the home screen 7 is as follows. The CPU 11 refers to the user DB 121. The CPU 11 generates a link of the mode selection screen 5 or the common application screen 62 on the return button 70. The CPU 11 generates 500 in the virtual currency column 700 because the user ID is “0001” and the first row of the accumulated virtual currency column in the user DB 121 is 500. The CPU 11 generates a bar graph corresponding to the accumulated experience value in the experience value column 701. Since the first row of the level column of the user DB 121 is 23, the CPU 11 generates 23 in the level column 702. The CPU 11 refers to the user DB 121 and generates icons 71A, 71B, and 71C associated with application IDs “001”, “002”, and “003” associated with the user ID “0001”.

  The operation and operation of the home screen 7 are as follows. When the user touches the return button 70, the CPU 21 displays the mode selection screen 5 or the common application screen 62 on the display unit 25. When the user performs a touch operation on the icon 71, the CPU 21 transitions to a download page of a market that sells the application.

  FIG. 12 is an explanatory diagram showing an example of the screen layout of the confirmation screen 8. The confirmation screen 8 includes a virtual currency field 800 provided in the upper right part, an experience value field 801 provided in the left part of the virtual money field 800, a level field 802 provided in the upper part of the experience value field 801, and a central part The jackpot number field 81 provided in the table, the revolution number field 82 provided at the bottom of the jackpot number field 81, the difference ball field 83 provided at the bottom of the revolution number field 82, and the left part at the lower end. A return button 84 and a settlement screen button 85 provided on the right side of the return button 84 are provided. The operation and operation of the virtual money field 800, the experience value field 801, the level field 802 and the return button 84 on the confirmation screen 8 are the same as those of the virtual money field 700, the experience value field 701, the level field 702 and the return button 70 on the home screen 7. Therefore, the description is omitted for the sake of brevity.

  A specific method for generating the confirmation screen 8 is as follows. The CPU 11 refers to the user DB 121 and the settlement result DB 123. The CPU 11 generates 2 in the jackpot count column 81 because the user ID is “0001”, the application ID is “001”, and the first row of the jackpot count column in the settlement result DB 123 is 2. The CPU 11 generates 109 in the rotation speed column 82 because the first row of the rotation speed column of the settlement result DB 123 is 109. The CPU 11 generates 3000 in the difference ball column 83 because the first row of the difference ball row in the settlement result DB 123 is 3000. The CPU 21 generates a link to the settlement screen 9 on the settlement screen button 85.

  The operation and operation of the confirmation screen 8 are as follows. When the user performs a touch operation on the settlement screen button 85, the CPU 21 outputs a user ID, an application ID, and a settlement screen 9 acquisition request to the information processing apparatus 1.

  FIG. 13 is an explanatory diagram showing an example of the screen layout of the settlement screen 9. The settlement screen 9 is a screen for displaying game data. The settlement screen 9 includes a virtual currency column 91 provided in the upper right portion, an experience value column 92 provided in the left portion of the virtual currency column 91, a level column 93 provided in the upper part of the experience value column 92, and a settlement window. 90. The settlement window 90 is a screen for displaying the contents of game data. The payment window 90 includes a name column 900 provided at the top, a rotation number column 901 provided at the bottom of the name column 900, a jackpot number column 902 provided at the bottom of the rotation number column 901, and a jackpot number column 902. A difference ball column 903 provided at the lower portion, an acquisition experience value column 904 provided at the lower portion of the difference ball column 903, and an earned money column 905 provided at the lower portion of the acquisition experience value column 904 are provided.

  The CPU 21 outputs an acquisition request for the user ID, application ID, and settlement screen 9 to the information processing apparatus 1. The CPU 11 acquires the acquisition request for the user ID, application ID, and settlement screen 9 from the terminal device 2. The CPU 11 refers to the application DB 122 and determines whether there is game data generated by the first application or the second application. When the CPU 11 determines that there is game data generated by the first application or the second application, the CPU 11 combines the game data generated by the first application or the second application with the game data generated by the running application. For example, the game data generated by the second application is added to the game data generated by the first application. The CPU 11 generates a settlement screen 9 based on the game data.

  A specific method for generating the settlement screen 9 is as follows. The CPU 11 refers to the user DB 121 and determines that there is game data generated by the first application because the accumulated experience value is 1000, the level is 23, and the accumulated virtual currency is 500. The CPU 11 adds the acquired experience value 10 to the accumulated experience value 1000 because the first row of the acquired experience value column of the settlement result DB 123 is 10. The CPU 11 adds 100 to the virtual currency 500 because the first row of the acquired currency string in the settlement result DB 123 is 100. The CPU 11 does not change the level even if the acquired experience value is added to the accumulated experience value, so the level is left as it is.

  The CPU 21 refers to the user DB 121, the application DB 122, and the settlement result DB 123. Since the user ID is “0001” and the first row of the name column of the application DB 122 is the name A, the CPU 11 generates the name A in the name column 900. The CPU 11 generates 10 in the acquired experience value column 904. The CPU 11 generates 100 in the earned money column 905 because the first row of the earned money column in the settlement result DB 123 is 100. The CPU 11 generates 600 in the virtual currency column 91. The CPU 11 generates a bar graph having a length corresponding to 1010 in the experience value column 92. The CPU 11 generates level 23 in the level column 93.

  The CPU 11 outputs the generated settlement screen 9 to the terminal device 2. The CPU 21 outputs the settlement screen 9 to the display unit 25.

  When the user performs a touch operation on the settlement screen 9, the CPU 21 outputs an acquisition request for the home screen 7 to the information processing apparatus 1. The CPU 11 acquires a user ID and an acquisition request for the home screen 7 from the terminal device 2. The CPU 11 refers to the user DB 121 and the application DB 122 and generates the home screen 7 based on the user ID. The CPU 11 outputs the generated home screen 7 to the information processing apparatus 1. The CPU 21 acquires the output home screen 7. The CPU 21 outputs the home screen 7 to the display unit 25.

  Next, a processing procedure of the information processing system will be described using a flowchart. 14 to 18 are flowcharts showing processing procedures in the present embodiment.

  The CPU 21 determines whether any one of the plurality of icons 31 on the application selection screen 3 or the plurality of icons 71 on the home screen 7 has been touch-operated (step S11). When the CPU 21 determines that any one of the plurality of icons 31 or 71 is not touch-operated (step S11: NO), the touch operation is performed on any one of the plurality of icons 31 or 71. Wait until there is. When the CPU 21 determines that any one of the plurality of icons 31 or 71 is touch-operated (step S11: YES), the CPU 21 refers to the application DB 221 (step S12). CPU21 starts the 2nd application matched with application ID matched with the icon 31 or 71 (step S13). Further, the CPU 21 outputs a user ID and an application ID of the selected application to the information processing apparatus 1.

  The CPU 21 displays the mode selection screen 5 on the display unit 25 (step S14). The CPU 21 determines whether or not the normal button 50 has been touched (step S15).

  When the CPU 21 determines that the normal button 50 is touch-operated (step S15: YES), the second application associated with the application ID is executed offline (step S16). That is, the CPU 21 executes the second application independently from the information processing apparatus 1. The CPU 21 displays the application screen 61 on the display unit 25 (step S17). The CPU 21 generates game data (step S18). The CPU 21 stores the game data in the settlement result DB 222 (step S19). The CPU 21 determines whether or not a touch operation has been performed on an application end button (not shown) (step S20). If it is determined that the application end button (not shown) has not been touched (step S20: NO), the CPU 21 moves to step S18 and repeats the process. CPU21 complete | finishes a process, when it determines with having performed touch operation of the application termination button (not shown) (step S20: YES).

  When determining that the normal button 50 has not been touch-operated (step S15: NO), the CPU 21 determines whether or not the common application button 51 has been touch-operated (step S21). If the CPU 21 determines that the common application button 51 is not touch-operated (step S21: NO), the process proceeds to step S15.

  When the CPU 21 determines that the common application button 51 is touch-operated (step S21: YES), the CPU 21 executes the common application and the application associated with the application ID (step S22). The CPU 21 displays the common application screen 62 on the display unit 25 (step S23). The CPU 21 generates game data (step S24).

  The CPU 21 determines whether or not the settlement button 601 has been touched (step S25). When it is determined that the settlement button 601 has not been touched (step S25: NO), the CPU 21 moves the process to step S24 and repeats the process. When the CPU 21 determines that the settlement button 601 is touch-operated (step S25: YES), the CPU 21 acquires operation information and outputs game data, a user ID, and an application ID to the information processing apparatus 1 (step S26).

  The CPU 11 of the information processing device 1 acquires the user ID and game data from the terminal device 2 (step S27). The CPU 11 refers to the user DB 121 and the settlement result DB 123 and generates a confirmation screen 8 based on the user ID, application ID, and game data (step S28). CPU11 outputs confirmation screen 8 to terminal unit 2 (Step S29). CPU21 acquires confirmation screen 8 from information processor 1 (Step S30).

  The CPU 21 displays the confirmation screen 8 on the display unit 25 (step S31). The CPU 21 determines whether or not the settlement screen button 85 has been touched (step S32). When it is determined that the settlement screen button 85 has not been touch-operated (step S32: NO), the CPU 21 waits until the settlement screen button 85 is touch-operated. When it is determined that the settlement screen button 85 is touched (step S32: YES), the CPU 21 outputs a user ID and a request for obtaining the settlement screen 9 to the information processing apparatus 1 (step S33).

  CPU11 acquires the acquisition request of user ID and the adjustment screen 9 from the terminal device 2 (step S34). The CPU 11 refers to the user DB 121 to determine whether there is game data generated by the first application or the second application (step S35). If the CPU 11 determines that there is no game data generated by the first application or the second application (step S35: NO), the process proceeds to step S37. When the CPU 11 determines that there is game data generated by the first application or the second application (step S35: YES), the game data generated by the first application or the second application and the game data generated by the application being executed are Are combined (step S36). The CPU 11 generates a settlement screen 9 based on the game data (step S37). The CPU 11 outputs the settlement screen 9 to the terminal device 2 (step S38). The CPU 21 acquires the settlement screen 9 from the information processing apparatus 1 (step S39). The CPU 21 displays the settlement screen 9 on the display unit 25 (step S40).

  The CPU 11 outputs a user ID and an acquisition request for the home screen 7 to the information processing apparatus 1 (step S41). The CPU 11 acquires a user ID and an acquisition request for the home screen 7 from the terminal device 2 (step S42). The CPU 11 refers to the user DB 121 and the application DB 122 and generates the home screen 7 based on the user ID (step S43). The CPU 11 outputs the home screen 7 to the terminal device 2 (step S44).

  CPU21 acquires home screen 7 from information processor 1 (Step S45). The CPU 21 displays the home screen 7 on the display unit 25 (step S46), moves the process to step S11, and repeats the process.

  According to one aspect, it is possible to facilitate cooperation between a plurality of apps with different developers by executing a common app that performs the same operation with a plurality of apps with different developers.

  According to one aspect, it is possible to easily combine data of a plurality of applications with different developers.

  According to one aspect, whether or not to execute a common application can be selected by the normal button 50 and the common application button 51. For this reason, usability improves.

  According to one aspect, the game data can be output to the information processing apparatus 1 by touching the settlement screen button 85 with a common application, so that the user can easily output the game data to the information processing apparatus 1. it can.

  According to one aspect, the application can be executed even offline.

Embodiment 2
FIG. 19 is a block diagram illustrating a hardware group of the information processing apparatus 1 according to the second embodiment. The storage unit of the information processing apparatus 1 illustrated in FIG. 19 further includes an emblem DB 124. In the following, the configuration and operation other than those specifically described are the same as those of the first embodiment, and the description is omitted for the sake of brevity.

  FIG. 20 is a diagram illustrating an example of data stored in the user DB 121 according to the second embodiment. The user DB 121 further includes a friend ID column and an emblem ID column. In the friend ID column, a friend ID associated with the user ID is stored. The emblem ID column stores an emblem ID for identifying the emblem. The friend ID column and the emblem ID column are stored in advance.

  FIG. 21 is a diagram illustrating an example of data stored in the emblem DB 124. The emblem DB 124 is a database that stores information on emblems (items) that are items that can be selected through a common application. The emblem DB 124 includes an emblem ID column, an icon column, a name column, an effect column, and the like.

  The emblem ID column stores an emblem ID for identifying the emblem. In the icon column, an icon associated with the emblem ID is stored. The name column stores the name of the emblem. For example, an experience value of 3% increase in experience value, 25% increase in jackpot number, or 13% increase in rotation speed is stored. An experience value increase of 3% indicates that the acquired experience value increases by 3%. An increase in the number of jackpots by 25% indicates that the number of jackpots is increased by 25%. An increase in the rotational speed of 13% indicates that the rotational speed is increased by 13%. The effect column stores the effect of the emblem in the application.

  The emblem ID column, icon column, name column, and effect column of the emblem DB 124 are stored in advance.

  FIG. 22 is an explanatory diagram showing an example of the screen layout of the emblem screen 10. The emblem screen 10 is a screen for selecting an emblem.

  The emblem screen 10 includes a virtual currency field 100 provided in the upper right part, an experience value field 101 provided in the left part of the virtual money field 100, a level field 102 provided in the upper part of the experience value field 101, and an experience value. A memblem column 106 composed of three memblem columns 103, 104, and 105 provided in the left-right direction at the bottom of the column 101, and a selection column 10A, 10B provided in the left-right direction at the lower part of the memble column 106 A selection column 107 configured by 10C and the like, an assistant selection column 108 provided at the lower portion, and a start 109 provided at the lower portion of the assistant selection column 108 are provided. Since the actions and operations of the virtual currency field 100, the experience value field 101, and the level field 102 on the emblem screen 10 are the same as the virtual currency field 700, the experience value field 701, and the level field 702 on the home screen 7, they are described for the sake of brevity. Omitted.

  After the CPU 21 adds the common application and executes the application, the CPU 21 outputs an acquisition request for the emblem screen 10 to the information processing apparatus 1. The CPU 11 acquires a user ID and an acquisition request for the emblem screen 10 from the terminal device 2. The CPU 11 generates an emblem screen 10 based on the emblem DB 124.

  The method for generating the emblem screen 10 is as follows. The CPU 11 refers to the emblem DB 124. The CPU 11 generates an icon associated with the emblem ID associated with the user ID in the selection field 107.

  A specific method for generating the emblem screen 10 is as follows. The CPU 11 refers to the emblem DB 124. The CPU 11 generates emblems A, B, and C associated with the emblem IDs “11”, “12”, and “13” associated with the user ID “0001” in the selection columns 10A, 10B, and 10C.

  The CPU 11 outputs the emblem screen 10 to the terminal device 2. The CPU 21 acquires the emblem screen 10 from the information processing apparatus 1. The CPU 21 displays the emblem screen 10 on the display unit 25.

  The operation and operation of the emblem screen 10 are as follows. When the user touches the icon in the selection column 107 and then drops the icon in the emblem column 106, the CPU 21 stores the emblem ID associated with the icon in the storage unit 22. The CPU 21 displays an icon in the memble column 106.

  When the user performs a touch operation on the assistant selection field 108, the CPU 21 outputs the friend ID to the information processing apparatus 1. The CPU 11 acquires a friend ID from the information processing apparatus 1. The CPU 11 generates a friend screen 110 based on the friend ID. The CPU 11 outputs the friend screen 110 to the terminal device 2. The CPU 21 acquires the friend screen 110 from the information processing apparatus 1. The CPU 21 displays the friend screen 110 on the display unit 25. When the user touches start 109, the common application screen 62 is displayed.

  Specific actions and operations of the emblem screen 10 are as follows. When the user touches the icon A in the selection field 10 </ b> A and drops the icon A in the emblem field 103, the CPU 21 stores the emblem ID “11” associated with the icon A in the storage unit 22. The CPU 21 displays an icon A in the meiblem column 106.

  When the user touches the assistant selection field 108, the CPU 21 outputs the friend ID “0001” to the information processing apparatus 1. The CPU 11 acquires the friend ID “0001” from the information processing apparatus 1. The CPU 11 generates a friend screen 110 based on the friend ID “0001”. The CPU 11 outputs the friend screen 110 to the terminal device 2. The CPU 21 acquires the friend screen 110 from the information processing apparatus 1. The CPU 21 displays the friend screen 110 on the display unit 25.

  FIG. 23 is an explanatory diagram showing an example of the screen layout of the friend screen 110. The friend screen 110 is a screen for selecting an emblem associated with the friend ID. The friend screen 110 includes an emblem column 111 configured by emblem columns 11A, 11B, 11C, and 11D provided in the vertical direction, a user name column 112 configured by user name columns 11E, 11F, 11G, and 11H, and the like. And a start 113 provided in the center.

  The generation method of the friend screen 110 is as follows. The CPU 11 refers to the user DB 121 and the emblem DB 124. The CPU 11 generates an emblem ID icon associated with the same user ID as the friend ID in the emblem column 111. The CPU 11 generates a user name associated with the same user ID as the friend ID in the user name column 112.

  A specific method for generating the friend screen 110 is as follows. The CPU 11 refers to the user DB 121 and the emblem DB 124. The CPU 11 uses the emblems A, B, and C of the emblem IDs “11”, “12”, “13”, and “11” that are associated with the friend IDs “0002” and “0003” that are associated with the friend ID “0001”. And A are generated in the emblem columns 11A, 11B, 11C, and 11D. The CPU 11 generates user B, user B, user B, and user C in the user name columns 11E, 11F, 11G, and 11H.

  The operation and operation of the friend screen 110 are as follows. When the user touches start 113, the CPU 21 stores the emblem ID associated with the same user ID as the friend ID in the storage unit 22.

  Specific actions and operations of the friend screen 110 are as follows. When the user touches the start 113, the CPU 21 stores the emblem IDs “11”, “12”, “13”, and “11” associated with the emblems A, B, C, and A in the storage unit 22.

  The operation and operation of the common application screen 62 are as follows. The user touches the settlement button 601. The CPU 21 outputs the game data, the user ID, and the emblem ID stored in the storage unit 22 to the information processing apparatus 1. The CPU 11 acquires the game data, the user ID, and the emblem ID stored in the storage unit 22 from the terminal device 2. CPU11 changes game data based on emblem ID. Specifically, the CPU 21 changes the game data by applying the experience value 3% up, the jackpot number up 25% and the rotation number up 13% corresponding to the emblem IDs “11”, “12” and “13”. . The CPU 11 outputs the changed game data to the terminal device 2. The CPU 11 acquires the changed game data from the information processing apparatus 1.

  24 to 26 are flowcharts illustrating the information processing system according to the second embodiment. Since the processing of steps S11 to S46 is the same as that of the information processing system according to the first embodiment described above, description thereof is omitted for the sake of brevity. CPU21 outputs the acquisition request of a user ID and the emblem screen 10 to the information processing apparatus 1 after complete | finishing the process of step S22 (step S60). CPU11 acquires the acquisition request of user ID and the emblem screen 10 from the terminal device 2 (step S61). The CPU 11 generates the emblem screen 10 based on the user ID and the emblem DB 124 (step S62). The CPU 11 outputs the emblem screen 10 to the terminal device 2 (step S63). CPU21 acquires emblem screen 10 from information processor 1 (Step S64). The CPU 21 displays the emblem screen 10 on the display unit 25 (step S65).

  The CPU 21 determines whether or not the icon has been dropped on the MYBLEM column 106 (step S66). When the CPU 21 determines that the icon has been dropped on the emblem column 106 (step S66: YES), the emblem ID is stored in the storage unit 22 (step S67), and the process returns to step S66.

  When the CPU 21 determines that the icon has not been dropped on the memble field 106 (step S66: NO), the CPU 21 determines whether or not the assistant selection field 108 has been touched (step S68). When it is determined that the assistant selection field 108 has not been touched (step S68: NO), the CPU 21 determines whether or not the start 109 has been touched (step S77).

  If the CPU 21 determines that the start 109 has not been touched (step S77: NO), the process proceeds to step S66. When the CPU 21 determines that the start 109 has been touched (step S77: YES), the process proceeds to step S23. When it is determined that the assistant selection field 108 is touched (step S68: YES), the CPU 21 outputs the friend ID to the information processing apparatus 1 (step S69).

  CPU11 acquires friend ID from the terminal device 2 (step S70). The CPU 11 generates a friend screen 110 based on the friend ID (step S71). CPU11 outputs friend screen 110 to terminal unit 2 (Step S72). CPU21 acquires friend screen 110 from information processor 1 (Step S73). CPU21 displays the friend screen 110 on the display part 25 (step S74).

  The CPU 21 determines whether or not the start 113 is touched (step S75). If the CPU 21 determines that the start 113 is not touch-operated (step S75: NO), the CPU 21 waits until the start 113 is touch-operated. If the CPU 21 determines that the start 113 has been touched (step S75: YES), the emblem ID is stored in the storage unit 22 (step S76), and the process returns to step S23.

  CPU21 outputs game data, user ID, and emblem ID to the information processing apparatus 1 after complete | finishing the process of step S32 (step S78). CPU11 acquires game data, user ID, and emblem ID from the terminal device 2 (step S79). CPU11 changes game data based on emblem ID (step S80). That is, the CPU 11 changes the game data by applying the effect associated with the emblem ID to the game data. The CPU 11 outputs the changed game data to the terminal device 2 (step S81). CPU21 acquires the changed game data from the information processing apparatus 1 (step S82), and moves a process to step S33.

  According to one aspect, since a common emblem corresponding to each of a plurality of apps provided by different developers can be used, convenience for the user is improved.

Embodiment 3
FIG. 27 is a block diagram illustrating a hardware group of the information processing apparatus 1 according to the third embodiment. The storage unit of the information processing apparatus 1 illustrated in FIG. 27 further includes a ranking DB 125. In the following, the configuration and operation other than those specifically described are the same as those of the second embodiment, and the description is omitted for the sake of brevity.

  FIG. 28 is a diagram illustrating an example of data stored in the ranking DB 125. The ranking DB 125 includes a user ID column and a ranking column. A user ID is stored in the user ID column. The ranking of the user is stored in the ranking column.

  The user ID column of the ranking DB 125 is stored in advance. The CPU 11 generates a rank according to the game data. Specifically, for example, the CPU 11 generates a rank in the order in which there are many difference balls. The CPU 11 stores the generated rank in the ranking DB 125.

  FIG. 29 is an explanatory diagram showing an example of the screen layout of the home screen 7 according to the third embodiment. The home screen 7 includes a ranking button 72 at the center.

  The operation and operation of the home screen 7 according to Embodiment 3 are as follows. When the user touches the ranking button 72, the CPU 21 outputs a user ID and an acquisition request for the ranking screen 120 to the information processing apparatus 1. The CPU 11 acquires the acquisition request for the user ID and the ranking screen 120 from the terminal device 2. The CPU 11 generates a rank according to the game data. The CPU 11 stores the generated rank in the ranking DB 125.

  The CPU 11 generates a ranking screen 120 based on the user DB 121, the settlement result DB 123, and the ranking DB 125.

  The CPU 11 outputs a ranking screen 120 to the terminal device 2. The CPU 21 acquires the ranking screen 120 from the information processing apparatus 1. The CPU 21 displays the ranking screen 120 on the display unit 25.

  FIG. 30 is an explanatory diagram showing an example of the screen layout of the ranking screen 120. The ranking screen 120 includes a user name field 128 composed of a plurality of user name fields 12A, 12B, 12C, etc. provided in the vertical direction in the center, and a difference field 12D, 12E provided in the vertical direction in the right part. The difference ball column 129 comprised by 12F etc. is provided.

  A method for generating the ranking screen 120 is as follows. The CPU 11 refers to the user DB 121, the settlement result DB 123, and the ranking DB 125. The CPU 11 generates a rank associated with the user ID according to the game data. Specifically, the CPU 11 generates a rank in the order in which there are many difference balls. The CPU 11 generates a user name associated with the user ID associated with the rank in the user name column 128. The CPU 11 generates a difference ball associated with the user ID in the difference ball column 129.

  A specific method for generating the ranking screen 120 is as follows. The CPU 11 refers to the user DB 121, the settlement result DB 123, and the ranking DB 125. The difference balls associated with the user IDs “001”, “002”, and “003” in the first, second, and third lines of the settlement result DB 123 are 3000, 2000, and 1000, respectively. In addition, user A, user B, and user C are associated with user IDs “001”, “002”, and “003” in the first, second, and third lines of the user DB 121. Accordingly, the user A has the largest difference ball, the user B has the largest difference ball after the user A, and the user C has the largest difference ball after the user B. Therefore, the CPU 11 generates user A in the user name column 12A, generates user B in the user name column 12B, and generates user C in the user name column 12C. The CPU 11 generates 3000 in the difference ball column 12D, generates 2000 in the difference ball column 12E, and generates 1000 in the difference ball column 12F.

  FIG. 31 is a flowchart showing an information processing system according to the third embodiment. Since the processing of steps S11 to S82 is the same as that of the information processing system according to the second embodiment, the description thereof is omitted for the sake of brevity. When determining that the icon 31 or 71 is not touch-operated (step S11: NO), the CPU 21 determines whether the ranking button 72 is touch-operated (step S90). If the CPU 21 determines that the ranking button 72 has not been touch-operated (step S90: NO), the process proceeds to step S11 and the process is repeated. When the CPU 21 determines that the ranking button 72 has been touched (step S90: YES), the CPU 21 outputs a user ID and an acquisition request for the ranking screen 120 to the information processing apparatus 1 (step S91).

  CPU11 acquires the acquisition request of user ID and the ranking screen 120 from the terminal device 2 (step S92). The CPU 11 generates a rank according to the game data (step S93). Specifically, for example, the CPU 11 generates a rank in order from the highest level. The CPU 11 stores the generated rank in the ranking DB 125 (step S94).

  CPU11 produces | generates the ranking screen 120 based on user DB121 and ranking DB125 (step S95). CPU11 outputs ranking screen 120 to terminal unit 2 (Step S96). CPU21 acquires ranking screen 120 from information processor 1 (Step S97). The CPU 21 displays the ranking screen 120 on the display unit 25 (step S98), and the process proceeds to step S12.

  According to one aspect, since a ranking can be created from game data generated from a plurality of apps with different developers, not only between users who execute one app but also between users who execute each of a plurality of apps. Improve competitiveness.

  In the present embodiment, the CPU 11 generates a rank according to the level, but the rank generation method is not limited to this. The CPU 11 may generate a rank according to the experience value, the number of rotations, the difference ball, the number of jackpots, virtual money, the highest consecutive number of times sequence or the number of short-time, middle and big hits.

  The embodiment disclosed this time is to be considered as illustrative in all points and not restrictive. The scope of the present invention is defined by the terms of the claims, rather than the meanings described above, and is intended to include any modifications within the scope and meaning equivalent to the terms of the claims.

1 Information processing equipment (central equipment)
2 Terminal device (information processing device)
12P program 22P program

Claims (8)

A first application provided with a first developer name for generating game data, which is a simulation game imitating a ball game machine or a revolving game machine, and the first developer name Is a program used for a central device that performs processing related to the second application, which is a simulation game simulating a ball game machine or a revolving game machine, provided by a different second developer name. And
Acquiring game data generated by the first application and indicating a predetermined game result of the first application from a terminal device connected via a communication network;
In the process of managing the game data generated by the acquired first application in an integrated manner with the game data indicating the predetermined game result of the second application generated by the already acquired second application. A program for causing the central device to execute a process of adding a value of a predetermined game result of the first application to a value of a predetermined game result of the second application. Accepts selection of items pertaining to the first or second app,
The program according to claim 1, wherein, when game data is output from the terminal device, the central device further executes a process of changing the game data according to an item for which selection has been received.   The program according to claim 1 or 2, further causing the central device to execute a process of transmitting the integrated game data to the terminal device via the communication network. A first application provided with a first developer name for generating game data, which is a simulation game imitating a ball game machine or a revolving game machine, and the first developer name Is a second application provided with a different second developer name, and is an information processing apparatus that performs processing related to the second application, which is a simulation game imitating a ball game machine or a revolving game machine,
Means for acquiring a user ID for identifying a user of the terminal device, an app ID for identifying the app, and game data generated by the app, transmitted from the terminal device in which the first app and the second app are installed; ,
The user ID, the application ID of the first application, the application ID of the second application, game data indicating a predetermined game result of the first application, and game data indicating a predetermined game result of the second application Storage means for associating and storing integrated data;
When the user ID, the application ID, and the game data are acquired by the acquiring unit, the acquired game data is stored in the corresponding integrated data with reference to the acquired user ID and application ID in the storage unit. And a means for adding a predetermined game result value of the acquired game data to a predetermined game result value of the corresponding integrated data. A first application provided with a first developer name for generating game data, which is a simulation game imitating a ball game machine or a revolving game machine, and the first developer name Is a second application provided with a different second developer name, which is a program used for a terminal device that performs processing related to the second application, which is a simulation game simulating a ball game machine or a revolving game machine. And
Output common image data on the first app and the second app,
When operation information for operating the image is acquired during execution of the first application, game data generated by the first application and indicating a predetermined game result of the first application is connected via a communication network. Output to the central unit
When operation information for operating the image is acquired during execution of the second application, game data indicating a predetermined game result of the second application generated by the second application is output to the central device ,
The program which makes the said terminal device perform the process which acquires the game data with which the game data produced | generated by the said 1st and 2nd application were combined from the said central apparatus . A first application provided with a first developer name for generating game data, which is a simulation game imitating a ball game machine or a revolving game machine, and the first developer name Is a second application provided with a different second developer name, which is a program used for a terminal device that performs processing related to the second application, which is a simulation game simulating a ball game machine or a revolving game machine. And
When game data indicating a predetermined game result of the first application is generated by the first application, the game data, a user ID for identifying a user of the terminal device, and a first for identifying the first application Send the app ID to the central device connected via the communication network,
When game data indicating a predetermined game result of the second application is generated by the second application, the central device determines the game data, the user ID, and a second application ID for identifying the second application. Send to
The program which makes the said terminal device perform the process which acquires the game data with which the game data produced | generated by the said 1st and 2nd application were combined from the said central apparatus . Whether to execute a common application that operates in common on the first and second applications together with the first or second application that has received the activation instruction when the activation instruction of the first application or the second application is received Or accepting the selection of whether to execute the first or second app that has received the start command without executing the common app,
When a selection to execute the common application is received together with the first or second application that has received the activation command, the first or second application is executed, and the first and second applications are executed on the first and second applications. The program according to claim 5 or 6 , further causing the terminal device to execute a process of displaying a common image on the second application. The program according to claim 7 , wherein when the selection of executing the first or second application that has received a start command without executing the common application is received, the first or second application is executed offline.

Images