Management device

Abstract

This management device comprises: an acquisition unit that, for each of a plurality of terminal devices, acquires usage information in which the type of a settlement application in which a prescribed process has been executed among a plurality of settlement applications, the date of use of the settlement application in which the prescribed process has been executed, and the position where the settlement application in which the prescribed process has been executed was used are associated with each other; a generation unit that, on the basis of the usage information, generates, for each of the plurality of settlement applications, aggregate information indicating, for each area, a transition in the number of users that have caused the prescribed process to be executed; and an analysis unit that analyzes the aggregate information.

Description

management device

[0001] The present invention relates to a management device.

[0002] A user of a terminal device may use a payment app when purchasing a product. If the store where the user purchases the product accepts multiple payment apps, the store may select a payment method to use for payment with the user based on the payment app used by the user.

[0003] For example, Patent Document 1 discloses an electronic transaction system including an electronic store and a terminal device. In this electronic transaction system, the electronic store and the terminal device are connected via a network. The terminal device uses an IC card reader provided on the terminal device to read information on multiple payment apps stored on the IC card. The terminal device also transmits a list of the payment apps to the electronic store. The electronic store receives the list of payment apps output by a control unit on the terminal device and selects a payment method that matches the list of payment apps received from the terminal device from among multiple payment methods supported by the electronic store. The electronic store also outputs payment information required for payment related to the selected payment method to the terminal device.

[0004] Japanese Patent Application Laid-Open No. 2001-22845

[0005] In conventional electronic transaction systems, users can make payments using payment apps. In such cases, the business providing the payment app can track how the payment app is used. However, in conventional electronic transaction systems, if multiple payment apps are installed on a user's terminal device, the business providing one payment app cannot track how the user used the other payment apps.

[0006] Therefore, an object of the present invention is to provide a management device that helps businesses analyze the number of users who use each of multiple payment apps.

[0007] A management device according to a preferred aspect of the present invention includes an acquisition unit that acquires, in each of a plurality of terminal devices, usage information that correlates the type of payment app among a plurality of payment apps on which a specified process was executed, the date of use of the payment app on which the specified process was executed, and the location where the payment app on which the specified process was executed was used; a generation unit that generates, based on the usage information, aggregate information that indicates the trend in the number of users who have executed the specified process for each of the plurality of payment apps, for each of a plurality of regions; and an analysis unit that analyzes the aggregate information.

[0008] According to the present invention, it is possible to provide a management device that helps a business operator analyze the number of users who use each of a plurality of payment applications.

[0009] 1 is a diagram showing the overall configuration of management system 1. A block diagram showing an example configuration of terminal device 30_K. A block diagram showing an example configuration of server 10. A block diagram showing the configuration of usage information database ADB. A table showing an example configuration of startup log database BDB. A table showing an example configuration of payment log database SDB. A graph showing the trend in the number of users who have launched first payment app AP1 per region. A graph showing the trend in the number of unique users t of first payment app AP1 and the trend in the number of unique users t of second payment app AP2 .... A flowchart showing the operation of server 10. 10 is a graph showing the trend of the value obtained by dividing the number t of unique users of the second payment app AP2 by the number t of unique users of the first payment app AP1.

[0010] 1: Configuration of the Embodiment Hereinafter, with reference to FIGS. 1 to 13, an example of the configuration of a management system 1 including a server 10 as a management device according to an embodiment of the present invention will be described.

[0011] 1-1: Overall Configuration FIG. 1 is a diagram showing the overall configuration of the management system 1. As shown in FIG. 1, the management system 1 includes a server 10 and terminal devices 30_1, 30_2, ..., 30_K, ..., 30_N. N is an integer equal to or greater than 1. K is an integer equal to or greater than 1 and less than N. In this embodiment, the terminal devices 30_1 to 30_N have the same configuration. However, terminal devices with different configurations may be included. The server 10 and each of the terminal devices 30_1, 30_2, ..., 30_K, ..., 30_N are connected to each other so as to be able to communicate with each other via a communication network NET.

[0012] The terminal device 30 is a terminal device used by a user. More specifically, the terminal device 30 is a terminal device used by a user to pay for a product or service using a payment app when purchasing the product or service. The terminal device 30 may be, for example, a smartphone, a smartwatch, or a tablet. However, the terminal device 30 is not limited to these devices. Note that FIG. 1 shows, as an example, an example in which a user UK uses a terminal device 30_K.

[0013] The server 10 acquires usage information, which is information relating to the use of payment apps on the terminal devices 30_1 to 30_N. Based on the usage information, the server 10 generates aggregate information indicating, for each region, the transition in the number of users who have executed a predetermined process for each of the multiple payment apps. The server 10 then analyzes the aggregate information. The server 10 is an example of a "management device."

[0014] 2 is a block diagram showing an example configuration of the terminal device 30_K. The terminal device 30_K includes a processing device 31, a storage device 32, a communication device 33, a display device 34, an input device 35, and a GPS device 36. The elements of the terminal device 30_K are connected to each other using one or more buses for communicating information.

[0015] The processing device 31 is a processor that controls the entire terminal device 30_K. The processing device 31 is configured, for example, using one or more chips. The processing device 31 is configured, for example, using a central processing unit (CPU) that includes an interface with peripheral devices, an arithmetic unit, a register, etc. Some or all of the functions of the processing device 31 may be realized using hardware such as a DSP, an ASIC, a PLD, and an FPGA. The processing device 31 executes various processes in parallel or sequentially.

[0016] Storage device 32 is a recording medium that can be read from and written to by processing device 31. Storage device 32 also stores a plurality of programs including control program PR3 executed by processing device 31. Storage device 32 also stores first payment application AP1 and second payment application AP2.

[0017] The first payment app AP1 and the second payment app AP2 are applications used by the user UK of the terminal device 30_K to pay for products or services purchased by the user UK. The first payment app AP1 and the second payment app AP2 are provided by competing companies. When purchasing a product or service, the user UK of the terminal device 30_K selects either the first payment app AP1 or the second payment app AP2 using the input device 35 described below. The processing device 31 launches the selected payment app AP. The user UK then uses the launched payment app AP to pay for the product or service.

[0018] 2, storage device 32 stores two payment apps AP, a first payment app AP1 and a second payment app AP2. However, for ease of explanation, the number of payment apps AP stored in storage device 32 is limited to two, and storage device 32 may store any number of payment apps AP, such as three or more.

[0019] The communication device 33 is hardware serving as a transmitting / receiving device for communicating with other devices. The communication device 33 is also referred to as, for example, a network device, a network controller, a network card, or a communication module. The communication device 33 may include a connector for wired connection and an interface circuit corresponding to the connector. The communication device 33 may also include a wireless communication interface. Examples of the connector and interface circuit for wired connection include products that comply with wired LAN, IEEE 1394, and USB. Examples of the wireless communication interface include products that comply with wireless LAN, Bluetooth (registered trademark), etc.

[0020] The display device 34 is a device that displays images and text information. The display device 34 displays various images under the control of the processing device 31. For example, various display panels such as a liquid crystal display panel and an organic EL (Electro Luminescence) display panel are suitably used as the display device 34.

[0021] The input device 35 accepts operations from a user UK of the terminal device 30_K. For example, the input device 35 includes a keyboard, a touchpad, a touch panel, or a pointing device such as a mouse. Here, if the input device 35 includes a touch panel, it may also serve as the display device 34.

[0022] The GPS device 36 receives radio waves from multiple satellites. The GPS device 36 also generates location information from the received radio waves. The location information indicates the location of the terminal device 30. The location information may be in any format as long as it can identify the location. The location information indicates, for example, the latitude and longitude of the terminal device 30. As an example, the location information is obtained from the GPS device 36. However, the terminal device 30 may obtain the location information by any method. The obtained location information is output to the processing device 31.

[0023] The processing device 31 reads and executes the control program PR3 from the storage device 32. As a result, the processing device 31 functions as a selection unit 311, a start-up unit 312, a settlement unit 313, and a communication control unit 314.

[0024] The selection unit 311 selects either the first payment app AP1 or the second payment app AP2 based on input by the user UK using the input device 35. For example, the user UK touches with their finger either the icon of the first payment app AP1 or the icon of the second payment app AP2 displayed on the display device 34. The touch panel included in the input device 35 detects the touch on either icon by the user UK. The input device 35 accepts the touch on either icon as an operation performed by the user UK. The selection unit 311 selects either the first payment app AP1 or the second payment app AP2 based on the operation performed by the user UK accepted by the input device 35.

[0025] The launching unit 312 launches the first payment application AP1 or the second payment application AP2 selected by the selection unit 311.

[0026] After the first payment app AP1 or the second payment app AP2 is launched, the payment unit 313 pays for the goods or services purchased by the user UK based on the user UK's operation on the input device 35. More specifically, after the first payment app AP1 or the second payment app AP2 is launched, the display device 34 displays the screen of the launched payment app AP. The user UK performs an operation to make a payment on the screen of the payment app AP. Based on the operation, the payment unit 313 pays for the goods or services purchased by the user UK by communicating with an external server of the business company that provides the first payment app AP1 or the second payment app AP2.

[0027] The communication control unit 314 causes the communication device 33 to transmit and receive various information to and from external devices. In this embodiment, the communication control unit 314 causes the communication device 33 to transmit, to the server 10, a startup log, which is a log related to the startup of the first payment app AP1 and the second payment app AP2, and a payment log, which is a log related to payments. Details of the startup log will be described later with reference to FIG. 5. Details of the payment log will be described later with reference to FIG. 6.

[0028] 1-3: Server Configuration Fig. 3 is a block diagram showing an example configuration of the server 10. The server 10 includes a processing device 11, a storage device 12, a communication device 13, a display device 14, and an input device 15. The elements of the server 10 are connected to each other using one or more buses for communicating information.

[0029] The processing device 11 is a processor that controls the entire server 10. The server 10 is configured, for example, using one or more chips. The server 10 is configured, for example, using a central processing unit (CPU) that includes an interface with peripheral devices, an arithmetic unit, and registers. Some or all of the functions of the server 10 may be realized using hardware such as a DSP, ASIC, PLD, and FPGA. The processing device 31 executes various processes in parallel or sequentially.

[0030] The storage device 12 is a recording medium that can be read from and written to by the processing device 11. The storage device 12 also stores a plurality of programs including a control program PR1 executed by the processing device 11. The storage device 12 also stores a usage information database ADB and a region name table LT.

[0031] 4 is a block diagram showing the configuration of the usage information database ADB. The usage information database ADB comprises a startup log database BDB and a payment log database SDB. The startup log database BDB is a database that stores startup logs of the first payment application AP1 and the second payment application AP2 provided in terminal devices 30_1 to 30_K. The payment log database SDB is a database that stores payment logs of the first payment application AP1 and the second payment application AP2 provided in terminal devices 30_1 to 30_K.

[0032] FIG. 5 is a table showing an example of the configuration of the activation log database BDB. The activation logs stored in the activation log database BDB include the following components: "terminal device," "app type," "activation processing date and time," and "location information." "Terminal device" indicates the terminal device on which the first payment app AP1 or the second payment app AP2 was activated. "App type" indicates the type of payment app AP activated on the terminal device 30 indicated by "terminal device." "Activation processing date and time" indicates the date and time when the payment app AP was activated on the terminal device 30 indicated by "terminal device." "Location information" indicates the location of the terminal device 30 at the time the payment app AP was activated on the terminal device 30 indicated by "terminal device." As an example, the activation log in the first row of the activation log database BDB shown in FIG. 5 indicates that the second payment app AP2 was activated on the terminal device 30_3 at 22:31:05 on August 14, 2023, with the terminal device 30_3 located at latitude a and longitude b.

[0033] FIG. 6 is a table showing an example of the configuration of the payment log database SDB. The payment log stored in the payment log database SDB has the following components: "terminal device," "app type," "payment processing date and time," and "location information." "Terminal device" indicates the terminal device on which the payment for a product or service was made using the first payment application AP1 or the second payment application AP2. "App type" indicates the type of payment application AP used for payment in the terminal device 30 indicated by "terminal device." "Payment processing date and time" indicates the date and time when the payment for a product or service was made using the payment application AP in the terminal device 30 indicated by "terminal device." "Location information" indicates the location of the terminal device 30 at the time when the payment for a product or service was made using the payment application AP in the terminal device 30 indicated by "terminal device." As an example, the first line of the payment log of the payment log database SDB illustrated in Figure 5 indicates that the price of a product or service was paid for by the second payment application AP2 on terminal device 30_4 at 23:10:07 on August 14, 2023, with terminal device 30-4 located at latitude i and longitude j.

[0034] The region name table LT defines the correspondence between latitude and longitude and region names. The generation unit 112, which will be described later, derives the region name to which the location indicated by each "location information" belongs by comparing the "location information" stored in each of the activation log database BDB and the payment log database SDB with the region name table LT.

[0035] In FIG. 3 , the communication device 13 is hardware serving as a transmitting / receiving device for communicating with other devices. The communication device 13 is also referred to as, for example, a network device, a network controller, a network card, or a communication module. The communication device 13 may include a connector for wired connection and an interface circuit corresponding to the connector. The communication device 33 may also include a wireless communication interface. Examples of the connector and interface circuit for wired connection include products that comply with wired LAN, IEEE 1394, and USB. Examples of the wireless communication interface include products that comply with wireless LAN, Bluetooth (registered trademark), etc.

[0036] The display device 14 is a device that displays images and text information. The display device 14 displays various images under the control of the processing device 11. For example, various display panels such as a liquid crystal display panel and an organic EL (Electro Luminescence) display panel are suitably used as the display device 14.

[0037] The input device 15 accepts operations from an administrator of the server 10. For example, the input device 15 includes a keyboard, a touchpad, a touch panel, or a pointing device such as a mouse. Here, if the input device 15 includes a touch panel, it may also serve as the display device 14.

[0038] The processing device 11 reads and executes the control program PR1 from the storage device 12. As a result, the processing device 11 functions as an acquisition unit 111, a generation unit 112, an analysis unit 113, and a transmission unit 114.

[0039] Acquisition unit 111 acquires usage information related to the use of multiple payment app APs, including first payment app AP1 and second payment app AP2, from each of terminal devices 30_1 to 30_K. The usage information is information that correlates the type of payment app AP on which a predetermined process was executed, the date of use of the payment app AP on which the predetermined process was executed, and the location at which the payment app AP on which the predetermined process was executed was used. The usage information includes the above-mentioned startup log and the above-mentioned payment log. The startup log is a log related to the startup of the payment app AP on which the startup process was executed as the above-mentioned "predetermined process." Furthermore, the payment log is a log related to payments made using the payment app AP on which payment processing was executed as the above-mentioned "predetermined process."

[0040] In the activation log database BDB illustrated in Fig. 5, "application type" corresponds to the above-mentioned "type of payment application AP on which a predetermined process was executed." The date included in "activation processing date and time" corresponds to the above-mentioned "date of use of the payment application AP on which a predetermined process was executed." "Location information" corresponds to the above-mentioned "location at which the payment application AP on which a predetermined process was executed was used."

[0041] In the payment log database SDB illustrated in Fig. 6, "application type" corresponds to the above-mentioned "type of payment application AP on which the predetermined process was executed." The date included in "payment processing date and time" corresponds to the above-mentioned "date of use of the payment application AP on which the predetermined process was executed." "Location information" corresponds to the above-mentioned "location where the payment application on which the predetermined process was executed was used."

[0042] 3, the acquisition unit 111 stores the acquired usage information in a usage information database ADB. More specifically, the acquisition unit 111 stores the startup log included in the acquired usage information in a startup log database BDB included in the usage information database ADB. The acquisition unit 111 also stores the payment log included in the acquired usage information in a payment log database SDB included in the usage information database ADB.

[0043] The generation unit 112 generates, based on the usage information stored in the usage information database ADB, aggregate information indicating, for each region, the trend in the number of users who have executed a predetermined process for each of the multiple payment applications AP. The trend in the number of users is an aggregate value for each predetermined period. The predetermined period may be, for example, one day, one week, or one month.

[0044] More specifically, generation unit 112 generates tally information indicating, for each region, the transition in the number of users who have caused first payment app AP1 to execute a predetermined process. As one example, generation unit 112 generates tally information indicating, for each region, the transition in the number of users who have launched first payment app AP1 based on activation logs stored in activation log database BDB. As another example, generation unit 112 generates tally information indicating, for each region, the transition in the number of users who have paid for goods or services using first payment app AP1 based on payment logs stored in payment log database SDB. In this case, generation unit 112 derives the name of the region to which the location belongs by comparing the location indicated by the "location information" included in each activation log and payment log with region name table LT. Furthermore, generation unit 112 counts the number of terminal devices 30 as the number of users for each derived region name, thereby generating tally information indicating, for each region, the transition in the number of users who have caused first payment app AP1 to execute a predetermined process.

[0045] Furthermore, based on the usage information stored in the usage information database ADB, the generation unit 112 generates information for each region indicating the change in the number of users who have caused the second payment app AP2 to execute a predetermined process. As one example, the generation unit 112 generates tally information for each region indicating the change in the number of users who have launched the second payment app AP2 based on the activation logs stored in the activation log database BDB. As another example, the generation unit 112 generates tally information for each region indicating the change in the number of users who have paid for goods or services using the second payment app AP2 based on the payment logs stored in the payment log database SDB. In this case, the generation unit 112 derives the name of the region to which the location belongs by comparing the location indicated by the "location information" included in each activation log and payment log with the region name table LT. For each derived region name, the generation unit 112 counts the number of terminal devices 30 as the number of users, thereby generating tally information for each region indicating the change in the number of users who have caused the second payment app AP2 to execute a predetermined process.

[0046] FIG. 7 is a graph generated by the generation unit 112, showing the transition of the number of users who launched the first payment app AP1 for each region. The horizontal axis of the graph shown in FIG. 7 indicates the passage of time. The vertical axis of the graph indicates the number t of unique users who launched the first payment app AP1 for each region. For example, if user UK launched the first payment app AP1 at least once on August 14, 2023, that number would be counted as one launch by user UK. On the other hand, even if user UK launched the first payment app AP1 two or more times on August 14, 2023, that number would only be counted as one launch by user UK. Furthermore, the number of launches by each user on August 14, 2023, is counted individually. The number t of unique users on the vertical axis of the graph in FIG. 7 is equal to the total number of launches by all users in each region in August 2023 or September 2023.

[0047] In the example shown in FIG. 7 , the aggregate information generated by generation unit 112 indicates that the number t of unique users of the first payment app AP1 in city A is decreasing from August 2023 to September 2023. The aggregate information also indicates that the number t of unique users of the first payment app AP1 in city B is increasing from August 2023 to September 2023. The aggregate information also indicates that the number t of unique users of the first payment app AP1 in city C is decreasing from August 2023 to September 2023. The accounting information also indicates that the number t of unique users of the first payment app AP1 in city D is increasing from August 2023 to September 2023.

[0048] In FIG. 3, the analysis unit 113 analyzes the aggregate information generated by the generation unit 112 .

[0049] For example, analysis unit 113 identifies regions where the number t of unique users who have caused first payment app AP1 to execute a predetermined process tends to decrease, based on the aggregate information generated by generation unit 112. More specifically, analysis unit 113 identifies regions where the number t of unique users who have launched first payment app AP1 tends to decrease, based on the trend in the number t of unique users for each region generated by generation unit 112. Analysis unit 113 also identifies regions where the number t of unique users who have paid for goods or services using first payment app AP1 tends to decrease, based on the trend in the number t of unique users for each region generated by generation unit 112.

[0050] In the example shown in FIG. 7, the analysis unit 113 identifies City A and City C as areas where the number t of unique users tends to decrease.

[0051] 3 , analysis unit 113 calculates, based on the tally information, a first user increase indicating an increase in the number of users who have caused the first payment app AP1 to execute a predetermined process in a predetermined area during a predetermined period. Analysis unit 113 also calculates, based on the tally information, a second user increase indicating an increase in the number of users who have caused the second payment app AP2 to execute the same type of predetermined process in a predetermined area during a predetermined period. Analysis unit 113 also calculates a relative increase by subtracting the second user increase from the first user increase. Furthermore, if the relative increase exceeds a threshold, analysis unit 113 determines that the provider of first payment app AP1 has implemented a campaign to increase the number of users of first payment app AP1 in the above-mentioned predetermined area.

[0052] More specifically, based on the tally information, analysis unit 113 calculates a first user increase number indicating an increase in the number of users who have launched first payment app AP1 in a predetermined region during a predetermined period. Furthermore, based on the tally information, analysis unit 113 calculates a second user increase number indicating an increase in the number of users who have launched second payment app AP2 in the same predetermined region during the same predetermined period. Furthermore, analysis unit 113 calculates a relative increase number by subtracting the second user increase number from the first user increase number. Furthermore, if the relative increase number exceeds a threshold, analysis unit 113 determines that the provider of first payment app AP1 has implemented a campaign to increase the number of users of first payment app AP1 in the above-mentioned predetermined region.

[0053] Alternatively, analysis unit 113 calculates, based on the aggregate information, a first user increase indicating an increase in the number of users who paid for goods or services using first payment app AP1 in a specified region during a specified period. Furthermore, analysis unit 113 calculates, based on the aggregate information, a second user increase indicating an increase in the number of users who paid for goods or services using second payment app AP2 in the same specified region during the same specified period. Furthermore, analysis unit 113 calculates a relative increase by subtracting the second user increase from the first user increase. Furthermore, if the relative increase exceeds a threshold, analysis unit 113 determines that the provider of first payment app AP1 has implemented a campaign to increase the number of users of first payment app AP1 in the specified region.

[0054] As an example, Figures 8 to 11 are graphs showing the trend in the number t of unique users who caused the first payment app AP1 to execute a predetermined process and the trend in the number t of unique users who caused the second payment app AP2 to execute a predetermined process in City A. In the graphs shown in Figures 8 to 11, the horizontal axis represents time, and the vertical axis represents the number t of unique users. Note that in Figures 8 to 11, the number t of unique users of the first payment app AP1 in August 2023 is designated a1, and the number t of unique users of the first payment app AP1 in September 2023 is designated a2. Also, in Figures 8 to 11, the number t of unique users of the second payment app AP2 in August 2023 is designated b1, and the number t of unique users of the second payment app AP2 in September 2023 is designated b2.

[0055] 8, analysis unit 113 calculates Δa=a2-a1 as the first user increase. Furthermore, analysis unit 113 calculates Δb=b2-b1 as the second user increase. Furthermore, analysis unit 113 calculates Δa-Δb as the relative increase. If the relative increase Δa-Δb exceeds a threshold, analysis unit 113 determines that the provider of first payment app AP1 has implemented a campaign to increase the number of users of first payment app AP1 in City A.

[0056] In addition, if the first user increase number Δa and the second user increase number Δb calculated using the same method as above are in an inverse correlation relationship, the analysis unit 113 determines that the first payment app AP1 and the second payment app AP2 are in a competitive relationship.

[0057] In the example shown in Figure 8, the number of unique users t of the first payment app AP1 and the number of unique users t of the second payment app AP2 are both increasing. Therefore, there is no inverse correlation between the number of first users increased Δa and the number of second users increased Δb. As a result, the analysis unit 113 determines that the first payment app AP1 and the second payment app AP2 are not in a competitive relationship.

[0058] In the example shown in Figure 9, the number of unique users t of the first payment app AP1 and the number of unique users t of the second payment app AP2 are both decreasing. Therefore, there is no inverse correlation between the number of first users increased Δa and the number of second users increased Δb. As a result, the analysis unit 113 determines that the first payment app AP1 and the second payment app AP2 are not in a competitive relationship.

[0059] In the example shown in Figure 10, the number of unique users t of the first payment app AP1 is decreasing, while the number of unique users t of the second payment app AP2 is increasing. Therefore, the number of first users increased Δa and the number of second users increased Δb are in an inverse correlation. As a result, the analysis unit 113 determines that the first payment app AP1 and the second payment app AP2 are in a competitive relationship.

[0060] In the example shown in Figure 11, the number of unique users t of the first payment app AP1 is increasing, while the number of unique users t of the second payment app AP2 is decreasing. Therefore, there is an inverse correlation between the number of first users Δa and the number of second users Δb. As a result, the analysis unit 113 determines that the first payment app AP1 and the second payment app AP2 are in a competitive relationship.

[0061] 3, analysis unit 113 calculates, based on the aggregate information, an increase in first users, which indicates an increase in the number of users who have executed a predetermined process using first payment app AP1 in a predetermined region compared to the same period of the previous year. If the increase in first users exceeds a threshold, analysis unit 113 determines that the provider of first payment app AP1 has implemented a campaign to increase the number of users of first payment app AP1.

[0062] More specifically, analysis unit 113 calculates, based on the aggregate information, a first user increase Δa indicating an increase in the number of users who have launched first payment app AP1 in a predetermined period of time in a predetermined area. Alternatively, analysis unit 113 calculates, based on the aggregate information, a first user increase Δa indicating an increase in the number of users who have paid for goods or services using first payment app AP1 in a predetermined period of time in a predetermined area. Furthermore, when first user increase Δa exceeds a threshold, analysis unit 113 determines that the provider of first payment app AP1 has implemented a campaign to increase the number of users of first payment app AP1.

[0063] As an example, Figure 12 is a graph showing the change in the number t of unique users who executed a predetermined process using the first payment app AP1 in City A. In the graph shown in Figure 12, the horizontal axis represents time, and the vertical axis represents the number t of unique users. In Figure 12, the number t of unique users of the first payment app AP1 in September 2022 is represented as a1, and the number t of unique users of the first payment app AP1 in September 2023 is represented as a2.

[0064] Analysis unit 113 calculates the above-mentioned first user increase number as Δa = a2 - a1. If Δa exceeds a threshold, analysis unit 113 determines that the provider of first payment app AP1 has implemented a campaign to increase the number of users of first payment app AP1.

[0065] 3 , if analysis unit 113 determines that a campaign to increase the number of users of first payment app AP1 has been implemented in a predetermined area, transmission unit 114 transmits a notification encouraging use of second payment app AP2 in the predetermined area to terminal device 30 via communication device 13. The notification may be an email or a message sent using second payment app AP2.

[0066] 1-4: Operation of the Embodiment FIG. 10 is a flowchart showing a first operation of the server 10. As shown in FIG.

[0067] In step S1, processing device 11 functions as acquisition unit 111. Processing device 11 acquires, for each of multiple terminal devices 30, usage information that associates the type of payment app AP on which a predetermined process was executed among multiple payment apps AP, the date of use of the payment app AP on which the predetermined process was executed, and the name of the region where the payment app AP on which the predetermined process was executed was used.

[0068] In step S2, processing device 11 functions as generation unit 112. Based on the usage information acquired in step S1, processing device 11 generates aggregate information indicating, for each region, the transition in the number of users who have executed a predetermined process for each of the plurality of payment apps AP.

[0069] In step S3, the processing device 11 functions as the analysis unit 113. The processing device 11 analyzes the aggregated information generated in step S2.

[0070] 1-5: Effects of the Embodiment Server 10 as a management device according to the present embodiment includes an acquisition unit 111, a generation unit 112, and an analysis unit 113. Acquisition unit 111 acquires, for each of a plurality of terminal devices 30, usage information that correlates the type of payment app AP on which a predetermined process was executed among a plurality of payment apps AP, the date of use of the payment app AP on which the predetermined process was executed, and the location where the payment app AP on which the predetermined process was executed was used. Based on the usage information, generation unit 112 generates aggregate information that indicates, for each of a plurality of regions, the transition in the number of users who have executed the predetermined process for each of the plurality of payment apps AP. Analysis unit 113 analyzes the aggregate information.

[0071] As a result, the server 10 becomes a management device that helps the business operator analyze the number of users who use each of the multiple payment applications AP.

[0072] More specifically, the business operator can analyze aggregated information based on the type of payment app AP on which a predetermined process was executed, the date of use of the payment app AP on which the predetermined process was executed, and the name of the region where the payment app AP on which the predetermined process was executed was used, thereby enabling the business operator to analyze information regarding the number of users using the payment app AP for each region where the payment app AP was used.

[0073] Furthermore, in server 10 according to the present embodiment, the multiple payment apps AP include first payment app AP 1. Based on the aggregated information, analysis unit 113 identifies from the multiple areas a region where the number of users who have caused first payment app AP 1 to execute a predetermined process is on the decline.

[0074] As a result, server 10 can indicate to a second provider competing with a first provider that provides first payment application AP1 the areas where it is likely to increase the number of users of the payment application AP that it provides.

[0075] Furthermore, in server 10 according to this embodiment, the multiple payment applications AP include a first payment application AP1 and a second payment application AP2. Based on the aggregate information, analysis unit 113 calculates a first user increase indicating an increase in the number of users who have caused the first payment application AP1 to execute a predetermined process in a predetermined area during a predetermined period. Based on the aggregate information, analysis unit 113 also calculates a second user increase indicating an increase in the number of users who have caused the second payment application AP2 to execute a predetermined process in a predetermined area during a predetermined period. Analysis unit 113 also calculates a relative increase by subtracting the second user increase from the first user increase. If the relative increase exceeds a threshold, analysis unit 113 determines that a campaign to increase users of first payment application AP1 has been implemented.

[0076] As a result, the server 10 can indicate to a second provider that competes with the first provider that provides the first payment application AP1 the areas in which the first provider has conducted a campaign to increase its users.

[0077] Furthermore, in server 10 according to this embodiment, the multiple payment applications AP include a first payment application AP1. Analysis unit 113 calculates, based on the aggregate information, a first user increase indicating an increase in the number of users who have caused first payment application AP1 to execute a predetermined process in a predetermined region compared to the same period of the previous year. Furthermore, analysis unit 113 determines that a campaign to increase the number of users of first payment application AP1 has been implemented if the first user increase exceeds a threshold.

[0078] As a result, the server 10 can indicate to a second provider that competes with the first provider that provides the first payment application AP1 the areas in which the first provider has conducted a campaign to increase its users.

[0079] Furthermore, in server 10 according to this embodiment, the multiple payment apps AP include a first payment app AP1 and a second payment app AP2. Analysis unit 113 calculates a first user increase number indicating an increase in the number of users who have caused first payment app AP1 to execute a predetermined process during a predetermined period, based on the aggregation information. Analysis unit 113 also calculates a second user increase number indicating an increase in the number of users who have caused second payment app AP2 to execute a predetermined process during a predetermined period, based on the aggregation information. Furthermore, analysis unit 113 determines that first payment app AP1 and second payment app AP2 are in a competitive relationship when there is an inverse correlation between the first user increase number and the second user increase number.

[0080] As a result, server 10 can indicate to a second provider that competes with a first provider that provides first payment application AP1, the areas in which the second provider is in a competitive relationship with the first provider.

[0081] Furthermore, in server 10 according to the present embodiment, the multiple payment apps AP include a first payment app AP1 and a second payment app AP2. Server 10 includes transmitter 114 that, when analyzer 113 analyzes that a campaign to increase the number of users of first payment app AP1 has been implemented in a specified area, transmits a notification promoting use of second payment app AP2 in the specified area.

[0082] As a result, the server 10 can implement a campaign to promote the use of the second payment app AP2 that it provides to terminal devices in an area where a second provider that competes with the first provider that provides the first payment app AP1 is implementing a campaign to increase users.

[0083] In addition, in the server 10 according to the present embodiment, the predetermined process is a startup process for starting up the payment app AP. The usage information includes a startup log indicating the type of the payment app AP for which the startup process was executed and the date of use of the payment app AP for which the startup process was executed.

[0084] As a result, the server 10 becomes a management device that helps the business operator analyze the number of users who use each of a plurality of payment applications APs based on the startup logs of the payment applications APs.

[0085] In addition, in the server 10 according to the present embodiment, the predetermined process is a payment process using a payment app AP. The usage information includes a payment log indicating the type of the payment app AP on which the payment process was executed and the date of use of the payment app AP on which the payment process was executed.

[0086] As a result, the server 10 becomes a management device that helps the business operator analyze the number of users who use each of multiple payment applications APs based on the payment logs of the payment applications APs.

[0087] 2: Modifications The present disclosure is not limited to the above-described embodiments. Specific modifications are exemplified below.

[0088] 2-1: Variation 1 Analysis unit 113 may classify the regions included in the usage information into regions where a relatively large number of terminal devices 30 are expected to newly install second payment app AP2 and regions where a relatively small number of terminal devices 30 are expected to install second payment app AP2. In this case, analysis unit 113 classifies the regions included in the usage information based on the change in the number t of unique users of first payment app AP1 and the change in the number t of unique users of second payment app AP2 for each region over a predetermined period.

[0089] More specifically, the analysis unit 113 classifies an area where the value obtained by dividing the number of unique users t of the second payment app AP2 by the number of unique users t of the first payment app AP1 increases over a specified period as an area where a relatively large number of terminal devices are expected to newly install the second payment app AP2.

[0090] When the analysis unit 113 divides the number t of unique users of the second payment app AP2 by the number t of unique users of the first payment app AP1, the number t of unique users of the first payment app AP1 is the number t of unique users who launched the first payment app AP1 in a predetermined period. In this case, the number t of unique users of the second payment app AP2 is the number t of unique users who launched the second payment app AP2 in a predetermined period. Alternatively, when the analysis unit 113 divides the number t of unique users of the second payment app AP2 by the number t of unique users of the first payment app AP1, the number t of unique users of the first payment app AP1 is the number t of unique users who paid for goods or services using the first payment app AP1 in a predetermined period. In this case, the number t of unique users of the second payment app AP2 is the number t of unique users who paid for goods or services using the second payment app AP2 in a predetermined period.

[0091] As an example, Figure 14 is a graph showing the trend of the value obtained by dividing the number of unique users t of the second payment app AP2 by the number of unique users t of the first payment app AP1 in cities P, Q, S, and R.

[0092] In the example shown in Figure 14, in cities R and S, the value obtained by dividing the number of unique users t of the second payment app AP2 by the number of unique users t of the first payment app AP1 increases from August 2023 to September 2023. Meanwhile, in cities P and Q, the value obtained by dividing the number of unique users t of the second payment app AP2 by the number of unique users t of the first payment app AP1 increases from August 2023 to September 2023. The analysis unit 113 classifies cities R and S as areas where a relatively large number of terminal devices will newly install the second payment app AP2. Meanwhile, the analysis unit 113 classifies cities P and Q as areas where a relatively small number of terminal devices will newly install the second payment app AP2.

[0093] 3: Others (1) In the above-described embodiment, ROM and RAM are exemplified as storage device 12 and storage device 32, but other suitable storage media may also be used, such as flexible disks, magneto-optical disks (e.g., compact disks, digital versatile disks, Blu-ray (registered trademark) disks), smart cards, flash memory devices (e.g., cards, sticks, key drives), CD-ROMs (Compact Disc-ROMs), registers, removable disks, hard disks, floppy (registered trademark) disks, magnetic strips, databases, servers, and other suitable storage media.

[0094] (2) In the above-described embodiments, the described information, signals, etc. may be represented using any of a variety of different technologies. For example, data, instructions, commands, information, signals, bits, symbols, chips, etc. that may be referred to throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or magnetic particles, optical fields or photons, or any combination thereof.

[0095] (3) In the above-described embodiment, input and output information may be stored in a specific location (for example, a memory) or may be managed using a management table. Input and output information may be overwritten, updated, or added to. Output information may be deleted. Input information may be transmitted to another device.

[0096] (4) In the above-described embodiment, the determination may be made based on a value (0 or 1) represented using one bit, a Boolean value (true or false), or a comparison of numerical values ​​(e.g., comparison with a predetermined value).

[0097] (5) The order of the exemplary procedures, sequences, flowcharts, etc. illustrated in the above-described embodiments may be rearranged unless inconsistent. For example, the methods described in this disclosure present elements of various steps using an example order, and are not limited to the particular order presented.

[0098] (6) Each function illustrated in Figures 1 to 14 is realized by any combination of hardware and / or software. Furthermore, the method for realizing each functional block is not particularly limited. That is, each functional block may be realized using a single device that is physically or logically coupled, or may be realized using two or more physically or logically separated devices that are connected directly or indirectly (e.g., wired, wireless, etc.) and these multiple devices. A functional block may be realized by combining software with the single device or the multiple devices.

[0099] (7) The programs exemplified in the above-described embodiments should be broadly construed to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, etc., regardless of whether they are called software, firmware, middleware, microcode, hardware description language, or by other names.

[0100] Software, instructions, information, etc. may also be transmitted or received over a transmission medium. For example, if software is transmitted from a website, server, or other remote source using wired technologies (such as coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL)), and / or wireless technologies (such as infrared, microwave), then these wired and / or wireless technologies are included within the definition of transmission media.

[0101] (8) In each of the foregoing embodiments, the terms "system" and "network" are used interchangeably.

[0102] (9) The information, parameters, etc. described in this disclosure may be expressed using absolute values, relative values ​​from a predetermined value, or corresponding other information.

[0103] (10) In the above-described embodiment, the server 10 and the terminal devices 30_1 to 30_N may be mobile stations (MS). A mobile station may also be referred to by those skilled in the art as a subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, or some other appropriate term. In the present disclosure, terms such as "mobile station," "user terminal," "user equipment (UE)," and "terminal" may be used interchangeably.

[0104] (11) In the above-described embodiments, the terms "connected," "coupled," or any variations thereof refer to any direct or indirect connection or coupling between two or more elements, and may include the presence of one or more intermediate elements between two elements that are "connected" or "coupled" to each other. The coupling or connection between elements may be a physical coupling or connection, a logical coupling or connection, or a combination thereof. For example, "connected" may be read as "access." As used in this disclosure, two elements may be considered to be "connected" or "coupled" to each other using at least one of one or more wires, cables, and printed electrical connections, as well as electromagnetic energy having wavelengths in the radio frequency range, microwave range, and optical (both visible and invisible) range, as some non-limiting and non-exhaustive examples.

[0105] (12) In the above embodiments, the phrase "based on" does not mean "based only on," unless otherwise specified. In other words, the phrase "based on" means both "based only on" and "based at least on."

[0106] (13) As used in this disclosure, the terms "determining" and "determining" may encompass a wide variety of actions. "Determining" and "determining" may include, for example, judging, calculating, computing, processing, deriving, investigating, looking up, searching, inquiring (e.g., searching a table, database, or other data structure), and ascertaining something that is considered to be a "determining." Also, "determining" and "determining" may include receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, accessing (e.g., accessing data in memory), and so on. Furthermore, "judgment" and "decision" can include regarding resolving, selecting, choosing, establishing, comparing, etc. as having been "judged" or "decided." In other words, "judgment" and "decision" can include regarding some action as having been "judged" or "decided." Furthermore, "judgment (decision)" can be interpreted as "assuming," "expecting," "considering," etc.

[0107] (14) In the above embodiments, when the terms "include," "including," and variations thereof are used, these terms are intended to be inclusive, similar to the term "comprising." Furthermore, the term "or," as used in this disclosure, is not intended to be an exclusive or.

[0108] (15) In this disclosure, where articles are added by translation, such as a, an, and the in English, this disclosure may include the nouns following these articles being plural.

[0109] (16) In this disclosure, the term "A and B are different" may mean "A and B are different from each other." The term may also mean "A and B are each different from C." Terms such as "separate" and "combined" may also be interpreted in the same way as "different."

[0110] (17) Each aspect / embodiment described in this disclosure may be used alone, in combination, or switched depending on the implementation. Notification of predetermined information (e.g., notification that "X is true") is not limited to explicit notification, but may be implicit (e.g., not notifying the predetermined information).

[0111] Although the present disclosure has been described in detail above, it is clear to those skilled in the art that the present disclosure is not limited to the embodiments described herein. The present disclosure can be implemented in modified and altered forms without departing from the spirit and scope of the present disclosure as defined by the claims. Therefore, the description of the present disclosure is intended to be illustrative and does not have any limiting meaning on the present disclosure.

[0112] 1: Management system, 10: Server, 11: Processing device, 12: Storage device, 13: Communication device, 14: Display device, 15: Input device, 30: Terminal device, 31: Processing device, 32: Storage device, 33: Communication device, 34: Display device, 35: Input device, 111: Acquisition unit, 112: Generation unit, 113: Analysis unit, 114: Transmission unit, 311: Selection unit, 312: Startup unit, 313: Payment unit, 314: Communication control unit, ADB: Usage information database, AP: Payment application, AP1: First payment application, AP2: Second payment application, BDB: Startup log database, LT: Area name table, NET: Communication network, PR1: Control program, PR3: Control program, SDB: Payment log database, t: Number of unique users, UK: User, Δa: Number of first users added, Δb: Number of second users added

Claims

1. A management device comprising: an acquisition unit that acquires, in each of a plurality of terminal devices, usage information that correlates the type of payment app among a plurality of payment apps in which a specified process was executed, the date of use of the payment app in which the specified process was executed, and the location where the payment app in which the specified process was executed was used; a generation unit that generates aggregate information indicating, based on the usage information, the trend in the number of users who have executed the specified process for each of the plurality of payment apps, for each of a plurality of regions; and an analysis unit that analyzes the aggregate information.

2. The management device of claim 1, wherein the plurality of payment apps includes a first payment app, and the analysis unit identifies from the plurality of regions an area where the number of users who have caused the first payment app to execute the specified process tends to decrease based on the aggregated information.

3. The management device of claim 1, wherein the multiple payment apps include a first payment app and a second payment app, and the analysis unit: calculates a first user increase number indicating an increase in the number of users who have caused the first payment app to execute the specified process in a specified area during a specified period based on the aggregation information; calculates a second user increase number indicating an increase in the number of users who have caused the second payment app to execute the specified process in the specified area during the specified period based on the aggregation information; calculates a relative increase number by subtracting the second user increase number from the first user increase number; and determines that a campaign to increase the number of users of the first payment app has been implemented if the relative increase number exceeds a threshold.

4. The management device of claim 1, wherein the plurality of payment apps include a first payment app, and the analysis unit calculates a first user increase number indicating an increase in the number of users who have caused the first payment app to execute the specified process in a specified region compared to the same period of the previous year based on the aggregated information, and determines that a campaign to increase the number of users of the first payment app has been implemented if the first user increase number exceeds a threshold value.

5. The management device of claim 1, wherein the multiple payment apps include a first payment app and a second payment app, and the analysis unit: calculates a first user increase number indicating an increase in the number of users who have caused the first payment app to execute the specified process during a specified period based on the aggregation information; calculates a second user increase number indicating an increase in the number of users who have caused the second payment app to execute the specified process in the specified period in the region based on the aggregation information; and determines that the first payment app and the second payment app are in a competitive relationship when the first user increase number and the second user increase number are in an inverse correlation relationship.

6. The management device of claim 1, wherein the plurality of payment apps include a first payment app and a second payment app, and further comprising a transmission unit that, when the analysis unit analyzes that a campaign has been implemented in a specified area to increase the number of users of the first payment app, transmits a notification to promote use of the second payment app in the specified area.

7. The management device of claim 1, wherein the specified process is a startup process in which the payment app is launched, and the usage information includes a startup log indicating the type of payment app for which the startup process was executed among multiple payment apps, and the date of use of the payment app for which the startup process was executed.

8. The management device of claim 1, wherein the specified processing is a payment processing using the payment app, and the usage information includes a payment log indicating a type of payment app among a plurality of payment apps for which the payment processing was executed, and a date of use of the payment app for which the payment processing was executed.

Images