Information processing device and method

Abstract

An information processing device 20 comprises: a first acquisition unit 21 that acquires payment information relating to cashless payment performed by launching a payment application program stored in a user terminal 10, and location information relating to the location where the cashless payment was performed; a second acquisition unit 22 that acquires launch history of both a first payment application program, the launch of which may result in the first acquisition unit 21 acquiring payment information, and a second payment application program, even the launch of which does not result in the first acquisition unit 21 acquiring payment information, and acquires location information relating to the location where each launch was executed; and a generation unit 24 that generates cashless payment scale information regarding the scale of cashless payments in an area to be analyzed, using payment information acquired by the first acquisition unit 21 for locations included in the area and launch history acquired by the second acquisition unit 22 for the locations included in the area.

Description

Information processing device and method

[0001] The present invention relates to a technology for estimating the scale of cashless payments.

[0002] The national and local governments are aiming to promote cashless payments, and the proportion of cashless payments in total payments is on the rise.

[0003] For example, Patent Document 1 discloses a system that includes a regional mesh statistical value / geographic information acquisition unit that acquires regional mesh statistical values, station statistical values, and geographic information by inputting the longitude and latitude of a store; an allocation / aggregation unit that sets a plurality of interpolation points within the store location point and the surrounding regional mesh or station mesh, assigns statistical values ​​to the interpolation points, and automatically aggregates the statistical values ​​assigned to the interpolation points within the aggregation area taking into account competing stores; a determination unit that determines the geographic business environment based on the aggregated values; a sales forecast model generation unit that specifies a sales forecast model for each geographic business environment for existing stores using machine learning techniques or statistical techniques; and a sales forecast unit that outputs sales forecast values ​​using the sales forecast model of the geographic business environment determined for the target store.

[0004] Japanese Patent Application Laid-Open No. 2023-5135

[0005] Each payment service provider operating a cashless payment business can determine the scale of cashless payments made by its own company in a certain region from the payment information it holds, but it cannot determine the scale of cashless payments made in the entire region, including cashless payments made by other companies.

[0006] Therefore, the present invention aims to provide a system that allows a payment service provider to estimate the scale of cashless payments in an entire region, including cashless payments by not only its own company but also other companies.

[0007] In order to solve the above problem, the present invention provides an information processing device comprising: a first acquisition unit that acquires payment information regarding a cashless payment made by launching a payment application program stored in a user terminal and location information regarding the location where the cashless payment was made; a second acquisition unit that acquires the launch history of a first payment application program from which the payment information can be acquired by the first acquisition unit when launched, and a second payment application program from which the payment information is not acquired by the first acquisition unit even when launched, and location information regarding the location where the launch was made; and a generation unit that generates cashless payment scale information regarding the scale of cashless payments in an area to be analyzed using the payment information acquired by the first acquisition unit for locations included in the area and the launch history acquired by the second acquisition unit for locations included in the area.

[0008] According to the present invention, a payment service provider can estimate the scale of cashless payments in an entire region, including not only its own but also cashless payments made by other companies.

[0009] FIG. 1 is a block diagram showing an example of a configuration of an information processing system 1 according to an embodiment of the present invention. FIG. 2 is a block diagram showing an example of a hardware configuration of a server device 20 according to the embodiment. FIG. 3 is a block diagram showing an example of a functional configuration of the server device 20. FIG. 4 is a diagram illustrating an example of location information data according to the embodiment. FIG. 5 is a diagram illustrating an example of startup history data according to the embodiment. FIG. 6 is a diagram illustrating an example of payment information data according to the embodiment. A flowchart showing an example of the operation of the server device 20. FIG. 7 is a block diagram showing an example of a functional configuration of the server device 20 according to a modified example. FIG. 8 is a diagram illustrating an example of user attribute data according to a modified example. FIG. 9 is a diagram illustrating an example of store attribute data according to a modified example. FIG. 10 is a block diagram showing an example of a functional configuration of the server device 20 according to a modified example.

[0010] [Embodiment] [Configuration] FIG. 1 is a diagram illustrating an example of the configuration of an information processing system 1 according to an embodiment of the present invention. The information processing system 1 includes multiple user terminals 10 each portable by multiple users, a server device 20 corresponding to the information processing device of the present invention, multiple payment systems 30a, 30b, 30c, etc. that perform cashless payment processing, and a communication network 2 including a wireless communication network or a wired communication network that communicatively connects these. The user terminals 10 are wirelessly communicable computers such as smartphones, wearable devices, or tablets. The server device 20 may be composed of a single computer or multiple computers. Each payment system 30a, 30b, 30c, etc. is operated by a different cashless payment service provider. Hereinafter, the payment systems 30a, 30b, 30c, etc. will be collectively referred to as payment system 30.

[0011] User terminal 10 stores at least one payment application program for cashless payments, such as QR code (registered trademark) payments and electronic money payments, at stores, etc. User terminal 10 launches one of the stored payment application programs and performs a predetermined operation to request cashless payment from one of payment systems 30a, 30b, 30c, etc. operated by a cashless payment provider corresponding to that payment application program. In this embodiment, a telecommunications provider providing communication services to user terminal 10 operates server device 20 and one of multiple cashless payment providers. In FIG. 1 , it is assumed that payment system 30a of payment systems 30a, 30b, 30c, etc. is operated by that telecommunications provider.

[0012] Therefore, a telecommunications carrier (its own company) that provides communication services to user terminal 10 can accurately determine the scale of cashless payments in a certain area based on the payment information of cashless payments held by payment system 30a, but cannot accurately determine the scale of cashless payments based on payment information held by payment systems 30b, 30c, etc. other than payment system 30a (i.e., payment information held by telecommunications carriers that correspond to other companies from the company's perspective).

[0013] Therefore, server device 20 estimates the scale of cashless payments in the above-mentioned area using payment information held by payment system 30a and the launch history of one or more payment application programs stored in user terminal 10. Note that, since a telecommunications carrier operates both server device 20 and payment system 30a, in Figure 1, server device 20 and payment system 30a may be connected by a dedicated line, or payment system 30a may be configured to include server device 20.

[0014] FIG. 2 is a diagram showing the hardware configuration of the server device 20. The server device 20 is physically configured as a computer including a processor 2001, a memory 2002, a storage 2003, a communication device 2004, an input device 2005, an output device 2006, and a bus connecting these devices. Each of these devices operates using power supplied from a battery (not shown). In the following description, the term "device" can be interpreted as a circuit, a device, a unit, or the like. The hardware configuration of the server device 20 may be configured to include one or more of the devices shown in FIG. 2, or may be configured without including some of the devices. Furthermore, the server device 20 may be configured by communicating with multiple devices each having a different housing.

[0015] Each function in the server device 20 is realized by loading specified software (programs) onto hardware such as the processor 2001 and memory 2002, causing the processor 2001 to perform calculations, control communication via the communication device 2004, and control at least one of reading and writing data in the memory 2002 and storage 2003.

[0016] The processor 2001 controls the entire computer by running, for example, an operating system. The processor 2001 may be configured as a central processing unit (CPU) including an interface with peripheral devices, a control device, an arithmetic unit, a register, etc. Furthermore, for example, a baseband signal processing unit, a call processing unit, etc. may be realized by the processor 2001.

[0017] The processor 2001 reads programs (program codes), software modules, data, etc. from at least one of the storage 2003 and the communication device 2004 into the memory 2002 and executes various processes in accordance with these. The programs used are those that cause a computer to execute at least some of the operations described below. The functional blocks of the server device 20 may be implemented by a control program stored in the memory 2002 and running on the processor 2001. Various processes may be executed by one processor 2001, or may be executed simultaneously or sequentially by two or more processors 2001. The processor 2001 may be implemented by one or more chips. The programs may be transmitted to the server device 20 via a telecommunications line.

[0018] The memory 2002 is a computer-readable recording medium and may be configured by, for example, at least one of a read-only memory (ROM), an erasable programmable ROM (EPROM), an electrically erasable programmable ROM (EEPROM), a random access memory (RAM), etc. The memory 2002 may also be called a register, a cache, a main memory (primary storage device), etc. The memory 2002 can store executable programs (program codes), software modules, etc. for implementing the method according to this embodiment.

[0019] Storage 2003 is a computer-readable recording medium, and may be composed of at least one of, for example, an optical disk such as a CD-ROM (Compact Disc ROM), a hard disk drive, a flexible disk, a magneto-optical disk (e.g., a compact disk, a digital versatile disk, a Blu-ray (registered trademark) disk), a smart card, a flash memory (e.g., a card, a stick, a key drive), a floppy (registered trademark) disk, a magnetic strip, etc. Storage 2003 may also be called an auxiliary storage device.

[0020] The communication device 2004 is hardware (transmission / reception device) for communicating between computers via at least one of a wired network and a wireless network, and is also called, for example, a network device, a network controller, a network card, or a communication module.

[0021] Each device, such as the processor 2001 and the memory 2002, is connected by a bus for communicating information. The bus may be configured using a single bus, or may be configured using different buses between each device.

[0022] The server device 20 may be configured to include hardware such as a microprocessor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a programmable logic device (PLD), or a field programmable gate array (FPGA), and some or all of the functional blocks may be realized by the hardware. For example, the processor 2001 may be implemented using at least one of these pieces of hardware.

[0023] The user terminal 10 is physically configured as a computer device including a processor, memory, storage, a communication device, an input device, an output device, and a bus connecting these devices. The processor, memory, and storage of the user terminal 10 are hardware similar to the processor 2001, memory 2002, and storage 2003 of the server device 20. The communication device of the user terminal 10 may be configured to include a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc. to realize at least one of frequency division duplex (FDD) and time division duplex (TDD). For example, the transmitting and receiving antenna, amplifier unit, transmitting and receiving unit, and transmission path interface may be realized by a communication device. The transmitting and receiving unit may be implemented as a transmitting unit and a receiving unit that are physically or logically separated. The input device of the user terminal 10 is an input device that accepts input from outside (e.g., a key, a microphone, a switch, a button, a GPS unit including a GPS antenna, etc.). The output device of the user terminal 10 is an output device (e.g., a display, a speaker, an LED lamp, etc.) that outputs to the outside. Note that the input device and the output device may be integrated into one device (e.g., a touch screen).

[0024] 3 is a block diagram showing the functional configuration of the server device 20. In the server device 20, a processor 2001 reads a program or the like from a storage 2003 into a memory 2002 and executes the program, thereby realizing the functions of a first acquisition unit 21, a second acquisition unit 22, a storage unit 23, a generation unit 24, and an output unit 25.

[0025] The first acquisition unit 21 acquires payment information related to a cashless payment made by launching a payment application program stored in the user terminal 10, and location information related to the location where the cashless payment was made. As described above, the telecommunications carrier that provides communication services to the user terminal 10 operates the payment system 30a and the server device 20, and therefore can acquire the payment information held by the payment system 30a via the first acquisition unit 21 of the server device 20. The first acquisition unit 21 acquires the payment information from the payment system 30a together with a user ID for identifying the user using the user terminal 10.

[0026] The first acquisition unit 21 also acquires location information indicating the location of the user terminal 10 together with the user ID, for example, from a positioning means (not shown). The positioning means referred to here may be any well-known positioning means, and may be, for example, a GPS unit provided in the user terminal 10, or a system that performs positioning of the user terminal 10 using a method known as base station positioning.

[0027] 4, the storage unit 23 stores the user ID and payment information acquired by the first acquisition unit 21 in association with each other. The payment information includes at least the date and time of the cashless payment and the payment amount.

[0028] 5, the storage unit 23 stores the user ID and the location information acquired by the first acquisition unit 21 in association with each other. This location information includes at least the date and time when the positioning of the user terminal 10 was performed and the location where the positioning was performed.

[0029] As described above, the payment information includes the payment date and time, and the location information includes the positioning date and time, so the location where the cashless payment was made can be identified by identifying a pair of payment information and location information that minimizes the difference between the payment date and time and the positioning date and time. Of course, the date and time of the cashless payment and the date and time of the positioning may not exactly match, but here, the location measured on the date and time of the positioning that is closest to the payment date and time is considered to be the location where the cashless payment was made.

[0030] Returning to the explanation of Figure 3, the second acquisition unit 22 acquires the launch history and location information relating to the location at which the application programs, for which payment information can be acquired by the first acquisition unit 21 when launched on the user terminal 10, and the launch history of application programs, for which payment information is not acquired by the first acquisition unit 21 even when launched on the user terminal 10. The application programs, for which payment information can be acquired by the first acquisition unit 21 when launched on the user terminal 10, are payment application programs for requesting cashless payment from the payment system 30a operated by the telecommunications carrier, and are hereinafter referred to as first payment application programs.

[0031] In contrast, an application program for which payment information is not acquired by first acquisition unit 21 even when launched on user terminal 10 is a payment application program for requesting cashless payment from payment systems 30b, 30c, etc. other than payment system 30a, and is hereinafter referred to as a second payment application program. Note that one user terminal 10 may have multiple second payment application programs.

[0032] The operating system (OS) stored in the user terminal 10 has a function for saving a launch history when an application program is launched on the user terminal 10. This function is valid regardless of whether the launched application program is the first payment application program or the second payment application program. The launch history includes at least program identification information (e.g., program name) for identifying the launched application program and the launch date and time, and the second acquisition unit 22 acquires this launch history from the user terminal 10 together with the user ID.

[0033] The second acquisition unit 22 also acquires, from a positioning means (not shown), location information indicating the location of the user terminal 10 together with the user ID. The positioning means referred to here may be any well-known positioning means as described above, and may be, for example, a GPS unit provided in the user terminal 10, or a system that performs positioning of the user terminal 10 using a method known as base station positioning.

[0034] 6, the storage unit 23 stores the user ID acquired by the second acquisition unit 22 and the launch history of each application program in association with each other. The launch history includes at least the program name of each application program (application A, application B, application C, etc.) and the launch date and time of the application program.

[0035] As described above, the startup history includes the startup date and time, and the location information includes the positioning date and time, so the location at which each application program was started can be identified by identifying a pair of startup history and location information that minimizes the difference between the startup date and time and the positioning date and time. Of course, the date and time at which an application program was started and the date and time at which its positioning was performed may not exactly match, but here, the location that was determined at the date and time at which the positioning was performed that is closest to the date and time at which the application program was started is considered to be the location at which the application program was started.

[0036] Returning to the explanation of Figure 3, the generation unit 24 generates cashless payment scale information regarding the scale of cashless payments in an area to be analyzed (hereinafter referred to as the area to be analyzed), such as a city, ward, town, village, or prefecture, by using payment information acquired by the first acquisition unit 21 for locations included in the area to be analyzed and activation history acquired by the second acquisition unit 22 for locations included in the area to be analyzed. A specific generation method is as follows.

[0037] Based on the payment information acquired by the first acquisition unit 21 for locations included in the analysis area, it is possible to identify the amount of cashless payments processed by the payment system 30a in the analysis area. Specifically, when the analysis area and analysis period are specified, the generation unit 24 extracts payment information processed at locations included in the analysis area during the analysis period from the content acquired and stored by the first acquisition unit 21 as shown in Figures 4 and 5, and calculates the sum of the payment amounts included in the extracted payment information. This sum corresponds to the amount of cashless payments processed by the payment system 30a in the analysis area and analysis period, and will be referred to as the company's cashless payment amount M below.

[0038] Then, the generation unit 24 calculates a coefficient A for the company's cashless payment amount M to generate cashless payment scale information including the amount processed for payment by the payment systems 30b, 30c, etc. from the company's cashless payment amount M.

[0039] Specifically, the generation unit 24 calculates the number of payments C1 made using the first payment application program by referring to the contents acquired and stored by the first acquisition unit 21 as illustrated in Figures 4 and 5 and counting the number of payment information items processed during the analysis period at locations included in the analysis area.

[0040] Next, generation unit 24 counts the number of times the second payment application program has been launched during the analysis period at locations included in the analysis area, by referring to the content acquired and stored by second acquisition unit 22 as shown in Figures 4 and 6. Since the second payment application program must be launched in order to make a cashless payment using the second payment application program, generation unit 24 can be considered to be the number of times cashless payments have been made using the second payment application program.

[0041] The generation unit then calculates the coefficient A as the value obtained by using the number of payments C1 made using the first payment application program as the denominator and the sum of the number of payments C1 made using the first payment application program and the number of times S2 the second payment application program is launched as the numerator.

[0042] In other words, coefficient A = (sum of number of payments C1 using the first payment application program and number of times S2 the second payment application program is started) / (number of payments C1 using the first payment application program).

[0043] Then, the generation unit 24 calculates the amount calculated by multiplying the coefficient A by the company's cashless payment amount M as the cashless payment scale information.

[0044] As described above, the generation unit 24 generates cashless payment scale information by multiplying a coefficient A, which has as its denominator the number of payments C1 using the first payment application program identified based on the payment information acquired by the first acquisition unit 21 for locations included in the analysis area, and the numerator the sum of the number of payments C1 using the first payment application program and the number of launches S2 of the second payment application program identified from the launch history acquired by the second acquisition unit 22 for locations included in the analysis area, by the company's cashless payment amount M in the analysis area identified from the payment information acquired by the first acquisition unit 21 for locations included in the analysis area.

[0045] Then, the output unit 25 outputs the cashless payment scale information generated by the generation unit 24 to the outside.

[0046] [Operation] Next, the operation of this embodiment will be described. FIG. 7 is a flowchart showing an example of the operation of the server device 20. Before the process shown in FIG. 7 is started, the first acquisition unit 21 and the second acquisition unit 22 acquire location information of each user's user terminal 10, for example, periodically or intermittently, and store the location information in the storage unit 23 in association with the user ID of the user. Also, before the process shown in FIG. 7 is started, the first acquisition unit 21 acquires payment information of each user, for example, when a cashless payment is made or periodically, and stores the payment information in the storage unit 23 in association with the user ID of the user. Also, before the process shown in FIG. 7 is started, the second acquisition unit 22 acquires the startup history of each user terminal 10, for example, when a payment application program is started or periodically, and stores the startup history in the storage unit 23 in association with the user ID of the user.

[0047] In Figure 7, when a certain analysis area and analysis period are specified, the generation unit 24 extracts from the memory unit 23 payment information processed at locations included in the analysis area during the analysis period, and the startup history of the payment application program at locations included in the analysis area during the analysis period (step S11).

[0048] Next, the generation unit 24 calculates the sum of the payment amounts contained in the extracted payment information (company's cashless payment amount M) as the amount of cashless payments processed by the payment system 30a in the above-mentioned analysis area and analysis period (step S12).

[0049] Next, the generation unit 24 calculates the coefficient A for the company's cashless payment amount M using the formula: coefficient A = (the sum of the number of payments C1 using the first payment application program and the number of times the second payment application program is launched S2) / (the number of payments C1 using the first payment application program) (step S13).

[0050] Next, the generation unit 24 uses the coefficient A calculated in steps S12 and S13 and the company's cashless payment amount M to calculate the amount calculated by coefficient A x company's cashless payment amount M as cashless payment scale information (step S14).

[0051] The output unit 25 outputs the cashless payment scale information generated by the generation unit 24 (step S15). This cashless payment scale information can be viewed, for example, by displaying or printing it, and by viewing it, the scale of cashless payments in the entire analysis target area can be known.

[0052] According to the embodiment described above, it is possible to estimate the overall scale of cashless payments in a certain analysis area and analysis period.

[0053] [Modifications] The present invention is not limited to the above-described embodiment. The above-described embodiment may be modified as follows. Furthermore, two or more of the following modifications may be combined and implemented.

[0054] [Variant 1] In the above embodiment, the coefficient A for the company's cashless payment amount M was calculated using the formula: coefficient A = (sum of the number of payments C1 using the first payment application program and the number of times the second payment application program was launched S2) / (number of payments C1 using the first payment application program).

[0055] In this formula, the number of activations S1 of the first payment application program may be used instead of the number of payments C1 using the first payment application program. In other words, the generation unit 24 may generate cashless payment scale information by multiplying a coefficient A, which is obtained by using the number of activations S2 of the first payment application program identified from the activation history acquired by the second acquisition unit 22 for locations included in the analysis area as a denominator and the sum of the number of activations S2 of the first payment application program identified from the activation history acquired by the second acquisition unit 22 for locations included in the analysis area and the number of activations of the second payment application program identified from the activation history acquired by the second acquisition unit 22 for locations included in the analysis area as a numerator, by the amount of cashless payments in the analysis area (the company's cashless payment amount M) identified from the payment information acquired by the first acquisition unit 21 for locations included in the analysis area. This makes it possible to generate cashless payment scale information without using the number of payments C1 using the first payment application program.

[0056] [Variation 2] The generation unit 24 may generate cashless payment scale information for each attribute of a user using the user terminal 10 or for each attribute of a store where a cashless payment has been made. In this case, the storage unit 23 stores the user attributes (e.g., age, gender, etc.) of each user in association with the user ID of the user, as illustrated in FIG. 9 , or stores the store attributes (e.g., category such as convenience store, drug store, supermarket, etc., and store size, etc.) of each store in association with a store ID for identifying the store, as illustrated in FIG. 10 . The generation unit 24 classifies the information acquired by the first acquisition unit 21 and the second acquisition unit 22 into groups based on the user attributes or store attributes described above, and generates cashless payment scale information for each group. This makes it possible to estimate the overall scale of cashless payments for each of these attributes.

[0057] [Variation 3] For example, it may be possible to investigate the scale of cashless payments for each attribute as described above from the results of a national census, a prefectural statistical survey, etc. Therefore, as shown in Fig. 8 , server device 20 may include a third acquisition unit 26 that acquires cashless payment scale information regarding the scale of cashless payments investigated for each attribute through a national census, a prefectural statistical survey, etc., and an evaluation unit 27 that compares the cashless payment scale information acquired by the third acquisition unit 26 with the cashless payment scale information generated by the generation unit 24 and performs evaluation based on the result of the comparison.

[0058] The cashless payment scale information regarding the scale of cashless payments surveyed for each attribute is, for example, information that indicates the total amount of cashless payments made by users belonging to each decade-year age group in the analysis area. The third acquisition unit 26 inputs (i.e., acquires) such cashless payment scale information obtained from an external source, such as a research organization, into the server device 20. The evaluation unit 27 then compares the cashless payment scale information acquired by the third acquisition unit 26 with the cashless payment scale information generated by the generation unit 24 for users belonging to each decade-year age group in the analysis area, and evaluates that the smaller the difference, the higher the accuracy of the cashless payment scale information generated by the generation unit 24. This makes it possible to evaluate the accuracy of the cashless payment scale information for each of these attributes.

[0059] [Variation 4] It is conceivable that a contract exists in which the payment amount when a user makes a cashless payment using the second payment application program is billed to the user through a credit card service provided to the user by the cashless payment provider operating payment system 30a. In this way, when the payment amount for a cashless payment using the second payment application program is billed to the user through a credit card service provided to the user by the cashless payment provider operating payment system 30a, the cashless payment provider operating payment system 30a can obtain payment information for the cashless payment using the second payment application program based on the service provision history of the credit card service.

[0060] Therefore, as shown in Figure 11, server device 20 may include a fourth acquisition unit 28 that acquires payment information for cashless payments using the second payment application program that are billed by the credit card service. In this case, generation unit 24 generates cashless payment scale information using the payment information acquired by fourth acquisition unit 28 for locations included in the analysis area, instead of the launch history of the second payment application program. This can further improve the accuracy of estimating the overall scale of cashless payments.

[0061] [Other Modifications] The block diagrams used to explain the above embodiments show functional blocks. These functional blocks (components) are 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 directly or indirectly connected (for example, using wires, wirelessly, etc.) and these multiple devices. The functional block may also be realized by combining software with the single device or the multiple devices.

[0062] Functions include, but are not limited to, judgment, determination, judgment, calculation, computation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, consideration, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, and assignment. For example, a functional block (component) that performs transmission is called a transmitting unit or transmitter. As mentioned above, there are no particular limitations on how these functions are implemented.

[0063] For example, the server device 20 in one embodiment of the present disclosure may function as a computer that performs the processing of the present disclosure.

[0064] Each aspect / embodiment described in the present disclosure may be applied to at least one of systems using LTE (Long Term Evolution), LTE-Advanced (LTE-A), SUPER 3G, IMT-Advanced, 4G (4th generation mobile communication system), 5G (5th generation mobile communication system), FRA (Future Radio Access), NR (New Radio), W-CDMA (registered trademark), GSM (registered trademark), CDMA2000, UMB (ULtra Mobile Broadband), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, UWB (ULtra-WIDE Band), Bluetooth (registered trademark), or other suitable systems, and next-generation systems extended based on these. Furthermore, a combination of multiple systems (e.g., a combination of at least one of LTE and LTE-A with 5G, etc.) may also be applied.

[0065] The present invention may also be an information processing method including: a first acquisition step of acquiring payment information regarding a cashless payment performed by launching a payment application program stored on a user terminal and location information regarding the location where the cashless payment was performed; a second acquisition step of acquiring the launch history of a first payment application program that, when launched, can acquire the payment information in the first acquisition step, and a second payment application program that, even when launched, does not acquire the payment information in the first acquisition step, and location information regarding the location where the launch occurred; and a generation step of generating cashless payment scale information regarding the scale of cashless payments in an area to be analyzed using the payment information acquired in the first acquisition step for locations included in the area and the launch history acquired in the second acquisition step for locations included in the area. The processing procedures, sequences, flowcharts, and the like of each aspect / embodiment described in this disclosure may be reordered as long as they are consistent. For example, the methods described in this disclosure present various step elements in an exemplary order and are not limited to the specific order presented.

[0066] Input and output information may be stored in a specific location (for example, 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.

[0067] The determination may be made based on a value represented by one bit (0 or 1), a Boolean value (true or false), or a numerical comparison (e.g., comparison with a predetermined value).

[0068] 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.

[0069] Software, whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise, should be construed broadly 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. Additionally, software, instructions, information, etc. may 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 such wired and / or wireless technologies are included within the definition of a transmission medium.

[0070] The information, signals, etc. described in this disclosure 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 voltage, current, electromagnetic waves, magnetic fields or magnetic particles, optical fields or photons, or any combination thereof. Note that terms described in this disclosure and terms necessary for understanding this disclosure may be replaced with terms having the same or similar meanings.

[0071] Furthermore, the information, parameters, etc. described in this disclosure may be expressed using absolute values, may be expressed using relative values ​​from a predetermined value, or may be expressed using other corresponding information.

[0072] As used in this disclosure, the phrase "based on" does not mean "based only on," unless expressly stated otherwise. In other words, the phrase "based on" means both "based only on" and "based at least on."

[0073] As used in this disclosure, any reference to an element using a designation such as "first," "second," etc. does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient method of distinguishing between two or more elements. Thus, a reference to a first and a second element does not imply that only two elements may be employed or that the first element must in some way precede the second element.

[0074] The "unit" in the configuration of each of the above devices may be replaced with "means," "circuit," "device," etc.

[0075] When the terms "include," "including," and variations thereof are used in this disclosure, these terms are intended to be inclusive, similar to the term "comprising." Furthermore, when the term "or" is used in this disclosure, it is not intended to be an exclusive or.

[0076] In this disclosure, where articles are added by translation, such as a, an, and the in English, the disclosure may include that the nouns following these articles are in the plural form.

[0077] In the present 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 "coupled" may also be interpreted in the same way as "different."

[0078] 1: Information processing system, 2: Communication network, 20: Server device, 21: First acquisition unit, 22: Second acquisition unit, 23: Memory unit, 24: Generation unit, 25: Output unit, 26: Third acquisition unit, 27: Evaluation unit, 28: Fourth acquisition unit, 2001: Processor, 2002: Memory, 2003: Storage, 2004: Communication device, 30a, 30b, 30c: Payment system.

Claims

1. An information processing device comprising: a first acquisition unit that acquires payment information regarding cashless payments made by launching a payment application program stored in a user terminal and location information regarding the location where the cashless payment was made; a second acquisition unit that acquires the launch history of a first payment application program from which the payment information can be acquired by the first acquisition unit when launched, and a second payment application program from which the payment information is not acquired by the first acquisition unit even when launched, and location information regarding the location where the launch was made; and a generation unit that generates cashless payment scale information regarding the scale of cashless payments in an area to be analyzed using the payment information acquired by the first acquisition unit for locations included in the area and the launch history acquired by the second acquisition unit for locations included in the area.

2. The information processing device described in claim 1, characterized in that the generation unit generates the cashless payment scale information by multiplying a coefficient whose denominator is the number of payments using a first payment application program identified based on payment information acquired by the first acquisition unit for locations included in the area and whose numerator is the sum of the number of payments using the first payment application program and the number of launches of a second payment application program identified from the launch history acquired by the second acquisition unit for locations included in the area by the amount of cashless payments in the area identified from the payment information acquired by the first acquisition unit for locations included in the area.

3. The information processing device described in claim 1, characterized in that the generation unit generates the cashless payment scale information by multiplying a coefficient whose denominator is the number of launches of the first payment application program identified from the launch history acquired by the second acquisition unit for locations included in the area and whose numerator is the sum of the number of launches of the first payment application program identified from the launch history acquired by the second acquisition unit for locations included in the area and the number of launches of the second payment application program identified from the launch history acquired by the second acquisition unit for locations included in the area by the amount of cashless payments in the area identified from payment information acquired by the first acquisition unit for locations included in the area.

4. The information processing device described in claim 1, characterized in that the generation unit generates the cashless payment scale information for each attribute of the user using the user terminal or for each attribute of the store where the cashless payment was made.

5. The information processing device according to claim 4, further comprising: a third acquisition unit that acquires cashless payment scale information regarding the scale of cashless payments investigated for each attribute; and an evaluation unit that compares the cashless payment scale information acquired by the third acquisition unit with the cashless payment scale information generated by the generation unit and performs an evaluation based on the results of the comparison.

6. The information processing device of claim 1 further comprising: a fourth acquisition unit that acquires payment information for the cashless payment using the second payment application program that is invoiced by the credit card service when the payment amount for the cashless payment using the second payment application program is invoiced to the user by a cashless payment provider corresponding to the first payment application program; and the generation unit generates the cashless payment scale information using the payment information acquired by the fourth acquisition unit for locations included in the area to be analyzed.

7. An information processing method comprising: a first acquisition step of acquiring payment information regarding a cashless payment made by launching a payment application program stored in a user terminal and location information regarding the location where the cashless payment was made; a second acquisition step of acquiring the launch history of a first payment application program from which the payment information can be acquired in the first acquisition step when launched, and a second payment application program from which the payment information is not acquired in the first acquisition step even when launched, and location information regarding the location where the launch was made; and a generation step of generating cashless payment scale information regarding the scale of cashless payments in an area to be analyzed using the payment information acquired in the first acquisition step for locations included in the area and the launch history acquired in the second acquisition step for locations included in the area.

Images