CN113826133A

CN113826133A - Information processing method, program, terminal, and server

Info

Publication number: CN113826133A
Application number: CN202080036197.8A
Authority: CN
Inventors: 滨窄亮介; 真崎洋辅
Original assignee: Line Pay Corp
Current assignee: Line Pay Corp
Priority date: 2019-06-17
Filing date: 2020-05-22
Publication date: 2021-12-21
Also published as: WO2020255621A1; JP2020204884A; KR20220020803A

Abstract

The information processing method of a terminal which executes processing related to settlement based on code information includes: receiving 1 st code information associated with 1 st expiration date by the server from the server via a communication unit of the terminal; storing the received 1 st code information in a storage unit of the terminal by a control unit of the terminal; and executing, by the control unit, a process related to settlement based on the 1 st code information, the settlement being executed by the server based on the time and the 1 st expiration date based on the process related to settlement.

Description

Information processing method, program, terminal, and server

Technical Field

The present disclosure relates to an information processing method, a program, a terminal, and a server.

Background

Recently, services that enable terminals or terminal users to manage electronic money (electronic money) and to settle accounts using electronic money have become widespread through applications that can be executed on terminals such as smartphones. For example, patent document 1 discloses a technique for settling the purchase amount of a product. However, the settlement using the electronic money is sometimes inconvenient, and for example, the settlement using the electronic money may not be performed depending on the communication environment or the communication state of the terminal.

Prior art documents

Patent document

Patent document 1: JP 2002-176671A

Disclosure of Invention

According to the 1 st aspect of the present invention, an information processing method of a terminal that executes processing relating to settlement based on code information, includes: receiving 1 st code information associated with 1 st expiration date by the server from the server via a communication unit of the terminal; storing the received 1 st code information in a storage unit of the terminal by a control unit of the terminal; and executing, by the control unit, a process related to settlement based on the 1 st code information, the settlement being executed by the server based on the time and the 1 st expiration date based on the process related to settlement.

According to the 2 nd aspect of the present invention, a program executed by a computer of a terminal that executes processing relating to settlement based on code information includes: receiving 1 st code information associated with 1 st expiration date by the server from the server via a communication unit of the terminal; a storage unit for storing the received 1 st code information in the terminal; and executing processing relating to settlement based on the 1 st code information, the settlement being executed by the server in accordance with the timing based on the processing relating to settlement and the 1 st expiration date.

According to the 3 rd aspect of the present invention, a terminal for executing a process related to settlement based on code information includes: a communication unit for receiving 1 st code information associated with 1 st expiration date from the server; and a control unit for storing the received 1 st code information in the storage unit of the terminal, wherein the control unit executes a process related to settlement based on the 1 st code information, and the settlement is executed by the server based on a time and a1 st expiration date based on the process related to settlement.

According to the 4 th aspect of the present invention, a terminal that executes processing relating to settlement based on code information includes: a processor that reads a program stored in the memory and performs a program-based process, the processor performing: a process of receiving 1 st code information associated with the 1 st expiration date by the server from the server via a communication unit of the terminal; a process of storing the received 1 st code information in a memory; and settlement-related processing based on the 1 st code information, the settlement being executed by the server according to the timing and the 1 st expiration date based on the settlement-related processing.

According to the 5 th aspect of the present invention, an information processing method of a server for managing settlement based on code information, comprises: a storage unit for associating the 1 st code information with the 1 st expiration date and storing the information in the server by a control unit of the server; transmitting the 1 st code information to a terminal performing processing related to settlement via a communication unit of the server; receiving, via the communication unit, the 1 st code information and information based on a time of a process related to settlement performed based on the 1 st code information; and a process of performing settlement by the control section based on the 1 st expiration date associated with the received 1 st code information and the received time based on the process related to the settlement.

According to the 6 th aspect of the present invention, a program executed by a computer of a server that manages settlement based on code information, includes: a storage unit for associating the 1 st code information with the 1 st expiration date and storing the information in the server; transmitting the 1 st code information to a terminal performing processing related to settlement via a communication unit of the server; receiving, via the communication unit, the 1 st code information and information based on a time of a process related to settlement performed based on the 1 st code information; and a process of performing settlement based on the 1 st term of validity associated with the received 1 st code information and the received time based on the process related to settlement.

According to the 7 th aspect of the present invention, a server for managing settlement based on code information includes: a storage unit for storing the 1 st code information in association with the 1 st expiration date; a communication unit for transmitting the 1 st code information to a terminal performing a process related to settlement based on the 1 st code information, and receiving the 1 st code information and information based on a time of the process related to the settlement; and a control unit for performing settlement processing based on the 1 st expiration date associated with the received 1 st code information and the received time based on the settlement processing.

According to the 8 th aspect of the present invention, a server for managing settlement based on code information includes: a processor that reads a program stored in the memory and executes a program-based process, the processor performing: a process of associating and storing the 1 st code information with the 1 st term of validity in a memory; a process of transmitting the 1 st code information to a terminal performing a process related to settlement based on the 1 st code information and receiving the 1 st code information and information based on a time of the process related to the settlement; and a process of performing settlement according to the 1 st term of validity associated with the received 1 st code information and the received timing based on the process related to settlement.

Drawings

Fig. 1 is a diagram showing an example of a configuration of a communication system according to an embodiment.

Fig. 2 is a diagram showing an example of a system configuration of a store POS system according to an embodiment.

Fig. 3-1 is a flowchart showing an example of a flow of processing executed by various apparatuses in one embodiment of the present invention.

Fig. 3-2 is a diagram showing an example of a display screen of a terminal in one embodiment of the present invention.

Fig. 3 to 3 are diagrams showing an example of a display screen of a terminal in one embodiment of the present invention.

Fig. 3 to 4 are flowcharts showing an example of the flow of processing executed by various apparatuses in one embodiment of the present invention.

Fig. 4-1 is a diagram showing an example of functions realized by the control unit of the server according to embodiment 1.

Fig. 4-2 is a diagram showing an example of information stored in the storage unit of the server according to embodiment 1.

Fig. 4 to 3 are diagrams showing an example of user registration data according to embodiment 1.

Fig. 4 to 4 are diagrams showing an example of the store registration data according to embodiment 1.

Fig. 4 to 5 are diagrams showing an example of the settlement management database according to embodiment 1.

Fig. 4 to 6 are diagrams showing an example of the code management database according to embodiment 1.

Fig. 4 to 7 are diagrams showing an example of functions realized by the control unit of the terminal according to embodiment 1.

Fig. 4 to 8 are diagrams showing an example of information stored in the storage unit of the terminal according to embodiment 1.

Fig. 4 to 9 are diagrams showing an example of the code storage data for display of the 1 st terminal according to embodiment 1.

Fig. 4 to 10 are diagrams showing an example of settlement data according to embodiment 1.

Fig. 4 to 11 are diagrams showing an example of a display screen of the terminal according to embodiment 1.

Fig. 4 to 12 are diagrams showing an example of a display screen of the terminal according to embodiment 1.

Fig. 4 to 13 are diagrams showing an example of a display screen of the terminal according to embodiment 1.

Fig. 4 to 14 are flowcharts showing an example of the flow of processing executed by each apparatus according to embodiment 1.

Fig. 4 to 15 are diagrams showing an example of the 2 nd terminal display code storage data according to the 1 st modification.

Fig. 4 to 16 are diagrams showing an example of a display screen of the terminal according to modification 1.

Fig. 4 to 17 are diagrams showing an example of a display screen of the terminal according to modification 1.

Fig. 4 to 18 are diagrams showing an example of a display screen of the terminal according to modification 1.

Fig. 4 to 19 are diagrams showing an example of a display screen of the terminal according to modification 1.

Fig. 4 to 20 are diagrams showing an example of a display screen of the terminal according to modification 1.

Fig. 4 to 21 are diagrams showing an example of a display screen of the terminal according to modification 1.

Fig. 4 to 22 are flowcharts showing an example of the flow of processing executed by each of the apparatuses according to modification 1.

Fig. 5-1 is a diagram showing an example of information stored in the storage unit of the terminal according to embodiment 2.

Fig. 5-2 is a flowchart showing an example of the flow of processing executed by various apparatuses according to embodiment 2.

Fig. 5-3 are diagrams showing an example of information stored in the storage unit of the terminal according to embodiment 2.

Fig. 5 to 4 are diagrams showing an example of code update condition data according to embodiment 2.

Fig. 5 to 5 are flowcharts showing an example of the flow of processing executed by each apparatus according to embodiment 2.

Fig. 6-1 is a diagram showing an example of information stored in the storage unit of the server according to embodiment 3.

Fig. 6-2 is a diagram showing an example of the per-account management database according to embodiment 3.

Fig. 7-1 is a flowchart showing an example of the 1 st code display processing according to embodiment 4.

Fig. 7-2 is a flowchart showing an example of the 2 nd code display processing according to embodiment 4.

Fig. 7-3 are flowcharts showing an example of the 3 rd code display processing according to embodiment 4.

Fig. 8 is a flowchart showing an example of the code management database according to embodiment 5.

Detailed Description

< compliance of legal matters >

Note that the disclosure described in this specification is premised on a legal matter of a country of implementation required for the implementation of the disclosure, such as a secret of communication.

Embodiments for implementing the information processing method and the like according to the present disclosure will be described with reference to the drawings.

[ System Structure ]

Fig. 1 shows an example of a configuration of a communication system 1 according to an embodiment of the present disclosure.

As shown in fig. 1, in the communication system 1, a server 10, terminals 20 (

terminals

20A, 20B, terminals 20C, … …), and a store POS system 40 are connected via a network 30.

The server 10 provides a transceiving service enabling contents including messages and the like between the terminals 20 to the terminals 20 owned by the user via the network 30. The server 10 communicates with the terminal 20 to provide a service (hereinafter, referred to as "settlement service") for realizing electronic settlement (which is not limited to but an example of settlement). In addition, there is no limitation on the number of terminals 20 connected to the network 30.

The network 30 serves to connect one or more terminals 20, one or more servers 10, and one or more store POS systems 40. That is, the network 30 is a communication network providing a connection path so that the various devices can transmit and receive data after being connected.

One or more portions of the network 30 may or may not be a wired or wireless network. The network 30, not being limited but by way of example, may include: ad hoc networks (ad hoc networks), intranets, extranets, Virtual Private Networks (VPNs), Local Area Networks (LANs), Wireless LANs (WLANs), Wide Area Networks (WANs), wireless WANs (wireless WANs: wws), Metropolitan Area Networks (MANs), a portion of the internet, a portion of the Public Switched Telephone Network (PSTN), a mobile Telephone Network, an ISDN (integrated service digital Network, ISDN), a wireless LAN, LTE (long term evolution), cdma (code division multiple access), Bluetooth (registered trademark), satellite communications, and the like, or a combination of two or more of these. The network 30 may include one or more networks 30.

The terminal 20 (the terminal 20A, the terminal 20B, the terminal 20C, and the terminal … …) (which is not limited but is an example of a terminal and an information processing apparatus) may be any terminal as long as it is an information processing terminal capable of realizing the functions described in the embodiments. The terminal 20, not being limited but by way of example, includes: a smart phone, a mobile phone (feature phone), a computer (such as, but not limited to, a desktop, laptop, tablet, etc.), a media computer platform (such as, but not limited to, a cable, satellite set-top box, digital video recorder), a handheld computer device (such as, but not limited to, a PDA (personal digital assistant), email client, etc.), a wearable terminal (eyewear device, watch-type device, etc.), or other type of computer, or a communications platform. In addition, the terminal 20 may also be expressed as an information processing terminal.

Since the structures of the

terminals

20A, 20B, and 20C are substantially the same, the terminal 20 will be described in the following description. Further, as necessary, a terminal used by the user X is expressed as the terminal 20X, and user information in a predetermined service associated with the user X or the terminal 20X is expressed as the user information X. The user information is information of a user associated with an account used by the user in a predetermined service. The user information includes, by way of example and not limitation, information entered by the user or assigned by a predetermined service, which is associated with the user, such as the name of the user, the icon image of the user, the age of the user, the sex of the user, the residence of the user, the interests and hobbies of the user, the identifier of the user, and the like, and any one or a combination of these pieces of information may be used, or none of these pieces of information may be used.

The server 10 (not limited to, but an example of a server, an information processing apparatus, and an information management apparatus) has a function of providing a predetermined service to the terminal 20. The server 10 may be any information processing device as long as it can realize the functions described in the embodiments. The server 10, not being limited but by way of example, includes: a server device, a computer (such as, but not limited to, a desktop, laptop, tablet, etc.), a media computer platform (such as, but not limited to, a cable, satellite set-top box, digital video recorder), a handheld computer device (such as, but not limited to, a PDA, email client, etc.), or other type of computer, or communications platform. In addition, the server 10 may also be expressed as an information processing apparatus. In a case where it is not necessary to distinguish between the server 10 and the terminal 20, the server 10 and the terminal 20 may be described as information processing apparatuses, respectively, or may not be described as such.

In the embodiments described below, the server 10 has a function of providing a service for settlement by a settlement application.

The store POS system 40 is a POS system introduced into a store and used in cooperation with an operator operating the server 10.

The store POS system 40 includes, by way of example and not limitation: a store code reader device 50, a code cash register 60 and a store server 70.

[ Hardware (HW) configuration of each device ]

An HW configuration of each device included in the communication system 1 will be described.

(1) HW structure of terminal

Fig. 1 shows an example of the HW configuration of the terminal 20.

The terminal 20 includes: a control unit 21 (CPU), a storage unit 28, a communication I/F22 (interface), an input/output unit 23, a display unit 24, a microphone 25, a speaker 26, a camera 27, a clock unit 29A, and a position calculation information detection unit 29B. The components of the HW of the terminal 20 are connected to each other via a bus B, by way of example and not limitation. Note that the HW configuration of the terminal 20 does not necessarily include all the components. The terminal 20 may be configured by removing each component such as the microphone 25 and the camera 27 or a plurality of components, but is not limited thereto.

The communication I/F22 transmits and receives various data via the network 30. The communication may be performed by any of wire or wireless, and any communication protocol may be used as long as mutual communication can be performed. The communication I/F22 has a function of performing communication with various devices such as the server 10 via the network 30. The communication I/F22 transmits various data to various devices such as the server 10 in accordance with instructions from the control unit 21. The communication I/F22 receives various data transmitted from various devices such as the server 10 and transmits the data to the control unit 21. Note that the communication I/F22 may be expressed as a communication unit only. In addition, when the communication I/F22 is configured by a physically structured circuit, the communication I/F may be expressed as a communication circuit.

The input/output unit 23 includes a device for inputting various operations to the terminal 20 and a device for outputting a processing result processed by the terminal 20. The input/output unit 23 may be integrated with the input unit and the output unit, may be separated from the input unit and the output unit, or may not be.

The input unit is implemented by any one or a combination of all kinds of devices that can receive an input from a user and transmit information related to the input to the control unit 21. The input unit includes, but is not limited to, a touch panel, a touch display, a hard key (hard key) such as a keyboard, a pointing device such as a mouse, a camera (operation input via a moving image), and a microphone (operation input by voice).

The output unit is realized by any one or a combination of all kinds of devices that can output the processing result processed by the control unit 21. The output section includes, by way of example and not limitation, a touch panel, a touch display, a speaker (voice output), a lens (such as, by way of example and not limitation, 3d (three dimensional) output, hologram output), a printer, and the like.

The display unit 24 may be implemented by any one or a combination of all kinds of devices capable of displaying data based on display data written in the frame buffer. The Display unit 24 includes, but is not limited to, a touch panel, a touch Display, a monitor (such as a liquid crystal Display, an oeld (organic electroluminescent Display), a Head Mounted Display (HDM), a projection map, a hologram, and a device capable of displaying an image, text information, and the like in air or the like (which may or may not be vacuum), as examples. Note that these display units 24 may display the display data in 3D, or may not display the display data in 3D.

When the input/output unit 23 is a touch panel, the input/output unit 23 and the display unit 24 may be arranged to face each other with substantially the same size and shape.

The clock unit 29A is a built-in clock of the terminal 20, and outputs time information (time information). The clock unit 29A is configured to have a clock using a crystal oscillator, for example, without limitation. The clock unit 29A may be expressed as a time counting unit or a time information detecting unit, by way of example and not limitation.

The clock unit 29A may or may not have a clock to which the nitz (network Identity and Time zone) standard is applied.

The position calculation information detection unit 29B is a functional unit that detects (measures) information (hereinafter, referred to as "position calculation information") required by the control unit 21 to calculate (measure) the position of the terminal 20 of the user. The position-calculation information detection unit 29B may be expressed as a position-calculation sensor unit, by way of example and not limitation.

The position calculation information detection unit 29B includes, by way of example and not limitation, a satellite Positioning sensor (satellite Positioning unit) for calculating the position of the terminal 20 using a satellite Positioning system such as gps (global Positioning system), an inertial Measurement sensor (inertial Measurement unit) for calculating the position of the terminal 20 using an inertial navigation system, and the like.

The satellite positioning means includes, by way of example and not limitation, an RF receiving circuit that converts an RF (radio frequency) signal including a positioning satellite signal transmitted from a positioning satellite received via an antenna not shown into a digital signal, a baseband processing circuit that acquires the positioning satellite signal by performing correlation processing or the like on the digital signal output from the RF receiving circuit, and outputs information such as satellite orbit data and time data extracted from the positioning satellite signal as position calculation information, and the like.

The inertial measurement unit has an inertial sensor, which is a sensor that detects information required to calculate the position of the terminal 20 through inertial navigation computation. The inertial sensor includes, by way of example and not limitation, a 3-axis acceleration sensor and a 3-axis gyro sensor, and outputs, as the information for position calculation, an acceleration detected by the acceleration sensor and an angular velocity detected by the gyro sensor.

The control unit 21 has a physically configured circuit for executing a function realized by a code or a command included in a program, and may be realized by a data processing device incorporated in hardware, by way of example and not limitation. Therefore, the control unit 21 may be expressed as a control circuit, or may not be expressed as such.

By way of example and not limitation, the control unit 21 includes: a Central Processing Unit (CPU), a microprocessor (microprocessor), a processor core (processor core), a multiprocessor (multiprocessor), an ASIC (application-specific integrated circuit), and an FPGA (field programmable gate array).

The storage unit 28 has a function of storing various programs and various data required for the operation of the terminal 20. The storage unit 28 includes, but is not limited to, various storage media such as hdd (hard disk drive), ssd (solid state drive), flash memory, ram (random access memory), and rom (read only memory). The storage unit 28 may be expressed as a memory (memory) or may not be expressed as such.

The terminal 20 stores the program P in the storage unit 28, and the control unit 21 executes the program P to perform processing as each unit included in the control unit 21. In other words, the program P stored in the storage section 28 causes the terminal 20 to realize each function executed by the control section 21. The program P may be expressed as a program module, or may not be expressed as such.

The microphone 25 is used to input voice data. The speaker 26 is used to output voice data. The camera 27 is used to acquire moving image data.

(2) HW architecture for servers

Fig. 1 shows an example of the HW configuration of the server 10.

The server 10 includes: a control unit 11(CPU), a storage unit 15, a communication I/F14 (interface), an input/output unit 12, and a display 13. By way of example and not limitation, the components of the HW of the server 10 are connected to each other via a bus B. The HW of the server 10 does not necessarily include all the components as the HW of the server 10. By way of example and not limitation, the HW of server 10 may or may not be configured to remove display 13.

The control unit 11 has a physically structured circuit for executing a function realized by a code or a command included in a program, and may be realized by a data processing device incorporated in hardware, by way of example and not limitation.

The control unit 11 is typically a Central Processing Unit (CPU), but may be a microprocessor, a processor core, a multiprocessor, an ASIC, or an FPGA, or not. In the present disclosure, the control unit 11 is not limited to these.

The storage unit 15 has a function of storing various programs and various data required for the operation of the server 10. The storage section 15 may be implemented by various storage media such as an HDD, an SSD, and a flash memory. However, in the present disclosure, the storage unit 15 is not limited to these. The storage unit 15 may be described as a memory (memory) or may not be described as such.

The communication I/F14 transmits and receives various data via the network 30. The communication may be performed by wire or wirelessly, and any communication protocol may be used as long as mutual communication can be performed. The communication I/F14 has a function of performing communication with various devices such as the terminal 20 via the network 30. The communication I/F14 transmits various data to various devices such as the terminal 20 in accordance with instructions from the control unit 11. The communication I/F14 receives various data transmitted from various devices such as the terminal 20 and transmits the data to the control unit 11. In addition, the communication I/F14 is expressed only as a communication section in some cases. In addition, when the communication I/F14 is configured by a physically structured circuit, it may be expressed as a communication circuit.

The input/output unit 12 is implemented by a device that inputs various operations for the server 10. The input/output unit 12 is implemented by any one or a combination of all types of devices that can receive an input from a user and transmit information related to the input to the control unit 11. The input/output unit 12 is typically implemented by a hard key represented by a keyboard or the like, or a pointing device such as a mouse. The input/output unit 12 may include, but is not limited to, a touch panel, a camera (operation input via a moving image), and a microphone (operation input based on voice), and may not include this. However, in the present disclosure, the input-output section 12 is not limited to these.

The display 13 is typically implemented by a monitor (not limited but by way of example, a liquid crystal display or an oeld (organic electronic display)). The display 13 may be a head mounted display (HDM) or the like, or may not be so. These displays 13 may or may not display the display data in 3D. In the present disclosure, the display 13 is not limited to these.

The clock unit 19 is a built-in clock of the server 10, and outputs time information (time information). The Clock section 19 is not limited to this, but is configured to have, as a hardware Clock, a Real Time Clock (RTC), a system Clock, and the like. The clock unit 19 may be expressed as a time counting unit or a time information detecting unit, by way of example and not limitation.

(3) System structure of shop POS

Fig. 2 shows an example of the system configuration of the store POS system 40.

The store POS system 40 is a POS system that is introduced into a store and used in cooperation with the operator that operates the server 10, and includes, by way of example and not limitation, a store code reader device 50, a code cash register 60, and a store server 70.

The store code reader device 50 is communicatively connected to the code cash register 60 or the store server 70 via a POS communication I/F57 (such as, by way of example and not limitation, a wired communication I/F or a wireless communication I/F in a store), and reads a code image for terminal display displayed on the display unit 24 of the terminal 20 when checkout is performed with the code cash register 60. Then, based on the code image for reading terminal display, settlement request information is transmitted to the server 10 through the communication I/F54, and after the server 10 executes settlement, information on the result of the settlement (for example, a settlement completion notification for shop described below) is received from the server 10 through the communication I/F54.

The store code reader device 50 includes, by way of example and not limitation: control unit 51, input/output unit 52, display unit 53, communication I/F54, storage unit 55, audio output unit 56, POS communication I/F57, code reader 58, and clock unit 59.

The code reader 58 is a code reader for reading a two-dimensional code, and in the present specification, includes a two-dimensional code reader (for example, a QR code reader) for reading a code for terminal display, which is a two-dimensional code (for example, a QR code (registered trademark)) displayed on the display unit 24 of the terminal 20 and presented by the user of the terminal 20.

The code cash register 60 is not limited to the above, but is connected to the store code reader device 50 and the store server 70 through the POS communication I/F57, for example, and issues a receipt printed with information such as the total amount of the sold commodities and the balance of the electronic money of the user of the terminal 20 based on the store settlement completion notification received by the store code reader device 50 from the server 10. Further, by way of example and not limitation, a display that is provided integrally with the code cash register 60 or that is provided separately from the code cash register 60 and whose display surface faces the client side may be configured. The code cash register 60 is configured as a cash register capable of supporting a settlement application, and may also be referred to as a fixed terminal supporting a settlement application.

The store server 70 manages various information such as store information on its own store, information on a product sold by its own store, information on a service provided by its own store, and information on sales volume for selling a product or providing a service in its own store, by way of example and not by way of limitation. The store server 70 is configured to be able to communicate with the store code reader device 50 and the code cash register 60 via the POS communication I/F57, and is configured to be able to communicate with an external device such as the server 10 via the network 30.

The store server 70 is not necessarily configured to be able to communicate directly with the store code reader device 50, but may be configured to be able to communicate with the store code reader device 50 via the code register 60. For example, the store code reader device 50 may transmit the settlement completion notification for the store received from the server 10 to the code cash register 60, and then transmit the settlement completion notification from the code cash register 60 to the store server 70.

(4) Others

The server 10 stores the program P in the storage unit 15, and the control unit 11 executes the processes of the respective units included in the control unit 11 by executing the program P. That is, the program P stored in the storage unit 15 causes the server 10 to realize each function executed by the control unit 11. The program P may or may not be expressed as a program module.

The same applies to other devices.

In the embodiments of the present disclosure, the description is made in a manner that the program P is executed by the CPU of the terminal 20 and/or the server 10.

The same applies to other devices.

The control unit 21 of the terminal 20 and/or the control unit 11 of the server 10 may realize each process not only by a CPU having a control circuit but also by a logic circuit (hardware) formed on an integrated circuit (ic) chip, lsi (large Scale integration), or the like or a dedicated circuit. Note that these circuits may be implemented by one or a plurality of integrated circuits, or a plurality of processes described in each embodiment may be implemented by one integrated circuit, or may not be implemented. The LSI is also called VLSI, very large LSI, or extra large LSI depending on the degree of integration. Therefore, the control unit 21 may be expressed as a control circuit, or may not be expressed as such.

The same applies to other devices.

In addition, the program P (such as a software program, a computer program, or a program module, by way of example and not limitation) of each embodiment of the present disclosure may be provided in a state stored in a computer-readable storage medium, or may not be provided. The storage medium can store the program P in a "non-transitory tangible medium". The program P may or may not be a program for realizing a part of the functions of the embodiments of the present disclosure. The functions of the embodiments of the present disclosure may be realized by a combination with the program P already recorded in the storage medium, or may be a so-called differential file (differential program), or may not be so.

The storage medium may include one or more semiconductor-based or other Integrated Circuits (ICs) (such as, without limitation, a Field Programmable Gate Array (FPGA) or application specific IC (asic)), a Hard Disk Drive (HDD), a hybrid hard disk drive (HHD), an Optical Disk Drive (ODD), an optical magnetic disk, an opto-magnetic drive, a Floppy Disk Drive (FDD), a magnetic tape, a Solid State Drive (SSD), a RAM drive, a secure digital card or drive, any other suitable storage medium, or a suitable combination of two or more of these. The storage medium may be volatile, nonvolatile, or a combination of volatile and nonvolatile, where appropriate. In addition, the storage medium is not limited to these examples, and may be any device or medium as long as the program P can be stored. The storage medium may be expressed as a memory (memory) or not.

The server 10 and/or the terminal 20 can realize the functions of the plurality of functional units described in the embodiments by reading the program P stored in the storage medium and executing the read program P.

The same applies to other devices.

The program P of the present disclosure may be provided to the server 10 and/or the terminal 20 via an arbitrary transmission medium (a communication network, a broadcast wave, or the like) through which the program can be transmitted, or may not be provided. The server 10 and/or the terminal 20 realize the functions of the plurality of functional units described in the embodiments by executing the program P downloaded via a network or the like, by way of example and not limitation.

The same applies to other devices.

In addition, the program P in each embodiment of the present disclosure may be realized in a form of being embodied as a data signal by electronic transmission.

At least a part of the processing in the server 10 and/or the terminal 20 may be realized by cloud computing including one or more computers, or may not be realized.

The configuration may be such that at least a part of the processing in the terminal 20 is performed by the server 10, or may not be such. In this case, at least a part of the processing of each functional unit of the control unit 21 of the terminal 20 may be performed by the server 10.

It may be a configuration in which at least a part of the processing in the server 10 is performed by the terminal 20. In this case, at least a part of the processing of each functional unit of the control unit 11 of the server 10 may be performed by the terminal 20.

Unless explicitly mentioned, the determination structure in the embodiments of the present disclosure is not mandatory, and the prescribed process may be executed in a case where the determination condition is satisfied, or the prescribed process may not be executed in a case where the determination condition is not satisfied, or may not be so.

Further, the program of the present disclosure is not limited to the above, and can be realized by using a script language such as ActionScript and JavaScript (registered trademark), a compiling language such as Objective-C, Java (registered trademark), a markup language such as HTML5, or the like, as an example.

In addition, in this specification, the expression "through communication I/F" is used as appropriate. This means that the apparatus is not limited to the above, but is configured to transmit and receive various information and data via the communication I/F (via the communication unit) under the control of the control unit (such as a processor).

In the present specification, the term "is described as indicating a certain period of time. However, the term "period" may also be used instead of the term "period".

In addition, the term "deadline" may also be used to refer to a time or date and time (a certain time or a certain date and time) at which the period ends.

< embodiment 1 >

In recent years, as applications (application software) related to network services, applications (settlement applications) for electronic settlement using electronic money, applications (transfer applications) for transferring electronic money, and settlement applications that integrate a part of or all of the functions of these applications have been widely used, and the user of the terminal 20 can receive various services related to electronic money using these applications.

The embodiment described below is an embodiment in which the user of the terminal 20 performs settlement using a settlement application stored and executed in the terminal 20, but the embodiment is not limited to this and is an example. Specifically, a method is proposed in which settlement can be appropriately performed even offline.

Hereinafter, an operator who provides a settlement service using a settlement application is referred to as an "operator of the settlement service". The operator of the settlement service may be expressed as an operator providing the settlement application or an operator of the server 10, or may not be expressed as such.

In addition, hereinafter, the explanation will be made with the operation and management server 10 by the operator of the settlement service. In addition, hereinafter, the name of the Payment application will be illustrated and described as "paymate App" as appropriate.

The settlement application may be provided by the server 10 as a separate application having no function of a so-called Messaging Service (MS), or may be provided by the server 10 as a composite application having a function of the MS. The Messaging Service may or may not include an Instant Messaging Service (IMS) capable of transmitting and receiving contents such as simple messages between the terminals 20.

In addition, the settlement application may be provided by the server 10 as a separate application that does not have a function of a so-called Social Networking Service (SNS), or may be provided by the server 10 as a composite application having an SNS function.

Further, an MS (including IMS) may also be considered as a form (one form) of an SNS. Therefore, the MS and the SNS may or may not be distinguished.

In addition, the shop that cooperates with the operator of the settlement service is called "member shop (member shop)" and is shown as "member shop S1", "member shop S2", … … as shown in fig. 1.

The term "electronic money" refers to electronic money that is owned by the terminal 20 or the user of the terminal 20 and managed by the settlement application and is distinguished from physical money, and the term "settlement" refers to electronic settlement using the electronic money.

Further, electronic money may or may not be expressed as "electronic money" or "digital currency (digital money)".

Further, as "electronic money (electronic money)" or "digital currency (digital money)", legal money or virtual money may be used.

In addition, "electronic money (electronic money)" or "digital currency (digital money)" may also include encrypted currency (encrypted assets).

In addition, the virtual currency may include physical currency such as a coupon.

< Settlement method >

(1) On-line payment

First, as one aspect, a method of online payment will be described with reference to a flowchart.

Hereinafter, "presence" indicates that the terminal 20 can communicate with the server 10, and "presence state" indicates a state of the presence. In addition, "online settlement" means settlement performed by the server 10 in an online state.

Further, hereinafter, the communication between the terminal 20 and the server 10 is, not limited but by way of example, realized by the 1 st communication method which is realized via a base station or the like set by a carrier (communication carrier) and uses a different frequency band from the wireless LAN communication. The 1 st communication method includes, by way of example and not limitation, packet communication (so-called mobile data communication in the terminal 20).

As the communication method, a2 nd communication method different from the 1 st communication method may be used, or not. The 2 nd communication system includes, by way of example and not limitation, a wireless LAN (for example, WiFi (registered trademark)).

The "online status" may be defined as a status in which the terminal 20 and the server 10 can communicate with each other by at least one of the 1 st communication method and the 2 nd communication method, or may not be defined as such.

Fig. 3-1 is a flowchart showing an example of the flow of processing executed by each device in this case. The processing performed by the control unit 21 of the terminal 20, the processing performed by the control unit 51 of the store code reader device 50, and the processing performed by the control unit 11 of the server 10 are shown in this order from the left.

Each step in each process is represented by a combination of an upper case of letters and a number, and the term "step" is omitted in this specification.

Note that the flowcharts described below are merely examples of the processing in this embodiment, and some of the steps may not be executed in the flowcharts described below, or additional steps may be inserted.

These also apply to the other flowcharts in this specification.

First, the control unit 21 transmits code generation request information for requesting generation of a code for terminal display to the server 10 via the communication I/F22 (via the communication I/F22) (a 110).

Hereinafter, the "code information" is explained as a concept that is not limited but is an example as follows: this concept includes information stored in a code image or information stored in a code image (hereinafter, referred to as "original information" in the sense of original information) by symbolization (encoding) or the like, and a "code image" storing the original information. That is, the "code information" includes "original information" and "code image".

The "original information" may be expressed as "encoded information" or "stored information" or the like, or may not be expressed as such.

In addition, hereinafter, not limited but as an example, "code" should have substantially the same meaning as "code information".

However, these definitions are merely examples, and are not limited thereto.

For example, the term "code information" may or may not be used in the sense of "original information".

In addition, for example, the term "code" may or may not be used in the sense of a "code image".

In the present embodiment, as an example of the above-described original information, a "number for settlement" which is a number generated uniquely by the server 10 for each terminal 20 of the transmission source of the code generation request information or each user of the terminal 20 and which is a random number having a predetermined number of digits is exemplified. The settlement number is information associated with the terminal 20 or the user of the terminal 20, and may be information for settlement performed by the server 10.

Hereinafter, the code for settlement generated by the server 10 based on the code generation request information is referred to as a "code for terminal display", and a code image of the code for terminal display is referred to as a "code image for terminal display".

The settlement number is stored in the terminal display code image, and the details will be described later.

The settlement number and the terminal display code image are examples of "first information" for settlement using the code image, and are transmitted from the server 10.

Hereinafter, a case where the request server 10 generates the information of the code image for terminal display as the code generation request information will be described as an example. That is, in this process, by way of example and not limitation, the terminal 20 requests the server 10 to generate the code image for terminal display, and at a110, code generation request information requesting the generation of the code image for terminal display is transmitted to the server 10.

In the present specification, the "terminal display code" will be described as a code used for settlement of the settlement type "terminal code display".

In the settlement type "terminal code display", when the user of the terminal 20 pays in a store or the like, a code image for terminal display displayed on the terminal 20 is presented to a clerk at the code cash register 60 of the store by using a settlement application stored in the terminal 20. Then, the terminal display code image is read by the shop code reader device 50 or the like, thereby realizing settlement.

The terminal display code is a code (code image) presented to a clerk of a shop or the like by the user of the terminal 20, and therefore can be also expressed as a "presentation code" or a "user presentation code".

The code generation request information transmitted by a110 is not limited to this, but may include identification information for identifying the terminal 20 or the user of the terminal 20, as an example. For example, the information may include information of terminal identification information (e.g., a terminal ID) for identifying the own terminal 20, user identification information (e.g., a user ID) for identifying the user of the own terminal 20, account information (e.g., an application ID) of the settlement application, and the like.

When the code generation request information is received from the terminal 20 via the communication I/F14 (C110), the control unit 11 performs the terminal display code generation processing (C120).

Specifically, the random number of the predetermined digit is generated as the number for settlement by using, as an example and not by way of limitation, a method (algorithm) for generating a random number of a predetermined digit (for example, a digit of about 10 digits to 12 digits). Then, by way of example and not limitation, a code image for terminal display is generated in which at least the settlement number is included as the original information. More specifically, at least the calculation number is encoded (symbolized) and patterned (imaged) to generate a code image for terminal display represented by an image of a two-dimensional code (for example, a QR code). The identification information of the terminal 20 or the user of the terminal 20 included in the received code generation request information is stored in the storage unit 15 in association with the generated settlement number.

Next, the control unit 11 transmits the generated code for terminal display (in this example, the code image for terminal display) to the terminal 20 via the communication I/F14 (C130). The terminal 20 receives a code for terminal display (in this example, a code image for terminal display) from the server 10 via the communication I/F22 (a 130). In this case, the control unit 21 displays the received code image for terminal display on the display unit 24, not by way of limitation, but by way of example.

Then, when the code image for terminal display displayed on the display unit 24 is presented to the store clerk of the store by the user of the terminal 20, the control unit 51 performs control for causing the code reader 58 to read the code image for terminal display displayed on the display unit 24 of the terminal 20 (B150).

Then, the control unit 51 accesses the server 10 through the communication I/F54 using an application interface (API) or the like associated with the settlement application provided (distributed) by the operator of the settlement service, and transmits settlement request information including at least a settlement number obtained by decoding the read terminal display code image, identification information for identifying the store or the store reader device 50 (hereinafter referred to as "store identification information"), and a predetermined settlement amount (hereinafter referred to as "predetermined settlement amount") to the server 10 through the communication I/F54 (B160).

When the settlement request information is received from the store code reader device 50 via the communication I/F14 (C160), the control unit 11 performs the settlement process (C170). Specifically, it is determined whether or not the number for settlement included in the received settlement request information is stored in the storage unit 15 in association with the terminal 20 or the identification information of the user of the terminal 20. When the electronic money is stored in the storage unit 15, it is determined that the electronic money can be settled, and the electronic money is settled by subtracting a predetermined settlement amount from the balance of the electronic money of the terminal 20 or the user of the terminal 20 (the balance of the electronic money associated with the application ID of the settlement application) (hereinafter, simply referred to as "balance") identified by the identification information stored in association with the settlement number.

Then, the control unit 11 transmits a settlement completion notification for the store (hereinafter, referred to as "settlement completion notification for the store") to the store code reader device 50 via the communication I/F14 (C180). The counter settlement completion notification includes, by way of example and not limitation, counter settlement information such as the fact that the settlement has been completed (successful), the date and time at which the settlement was performed (the date and time of the settlement), and the amount of money for which the settlement was performed (the amount of the settlement).

The control unit 11 transmits a terminal settlement completion notification (hereinafter, referred to as a "terminal settlement completion notification") to the terminal 20 via the communication I/F14 (C190). The terminal settlement completion notification includes, by way of example and not limitation, terminal settlement information such as the settlement completion (success) information, the settlement execution date and time (settlement date and time), the settlement execution store identification information (settlement store identification information) of the store that executes the settlement, and the settlement execution amount (settlement amount).

Here, in the case where the settlement by the server 10 has succeeded, the notification of the completion of the settlement for the store and the notification of the completion of the settlement for the terminal are transmitted from the server 10, but the server 10 may not perform the settlement due to shortage of the balance or the like. In this case, a notification (for example, a settlement error notification or a settlement NG notification) indicating that the settlement has not been performed may be transmitted to the store code reader device 50 and the terminal 20.

The same applies to other processes.

When the notification of the completion of the settlement for the store is received from the server 10 via the communication I/F54 (B180), the control unit 51 ends the process.

When receiving the terminal settlement completion notification from the server 10 via the communication I/F22, the control unit 21 updates the balance stored in the terminal 20 as data of the settlement application based on the received terminal settlement completion notification. Further, the control unit 21 causes the display unit 24 to display the settlement result (a 190). Then, the control unit 21 ends the process.

Fig. 3-2 is a diagram showing an example of a home page displayed in the settlement application executed by the terminal 20.

The home page is a display screen displayed when the payment application is started, and the name "payment app (payment app)" of the payment application is displayed on the screen. In a frame therebelow, a balance (here, "3000 yen") is displayed, and a charge button for charging (adding) electronic money is displayed beside it. In addition, a plurality of function icons corresponding to various functions of the payment application are displayed thereunder.

Among these function icons, the icon indicated as "code" is not limited to a specific one but is an example of a "code icon" for displaying a code display screen on the display unit 24. When the user of the terminal 20 touches and operates the code icon, not limited to this, but as an example, the code generation request information is transmitted from the terminal 20 to the server 10, and the terminal display code is generated by the server 10. Then, the generated code for terminal display is transmitted from the server 10 to the terminal 20, and a code display screen shown in fig. 3-3 is displayed on the display unit 24 of the terminal 20.

Fig. 3-3 are diagrams showing an example of the code display screen.

On the code display screen, characters of "code" are displayed on the upper part of the screen, and on the lower part thereof, a settlement method, points owned by the user, and a point label for setting whether to perform settlement using the points are displayed.

Further, below the code image as the terminal display code acquired from the server 10, a one-dimensional terminal display code image represented by a barcode and a two-dimensional terminal display code image QC0 represented by a QR code are displayed in different areas within the display screen. In addition, as an example, a 12-digit settlement number is displayed below the barcode.

In this example, the terminal display code displayed on the code display screen has a time limit for displaying the code (hereinafter referred to as "code display time limit").

The code display time limit is not limited to this, but is, for example, a period during which the terminal 20 displays the terminal display code. The code display time limit is not limited to a specific example, and may be "a period from the date and time when the terminal displays the code (display start) until the code display time elapses". The change code display time may be set as appropriate, and may be "5 minutes" by way of example and not limitation.

Further, the remaining time of the code display term is displayed in a countdown format together with the updated mark and the updated character below the two-dimensional terminal display code image QC 0. The remaining time is displayed based on information clocked by the clock unit 29A of the terminal 20.

When the remaining time becomes "0", the code display screen is closed, and the terminal display code is configured not to be displayed. Thereafter, when the user of the terminal 20 desires to perform settlement, the terminal display code needs to be newly acquired from the server 10.

The user of the terminal 20 presents the code display screen shown in fig. 3-3 to the clerk of the store at the code cash register 60 within the code display period, and the code image for terminal display is read by the store code reader device 50 to perform settlement. In this case, the store code reader device 50 accesses the server 10 through the communication I/F54 using the API or the like described above, and transmits information necessary for settlement to the server 10. Thereby, the server 10 performs settlement processing.

Although the process for realizing online settlement has been described above, the terminal 20 and the server 10 must be in a communication-enabled state (online state) in order to apply the above process. Of course, the store code reader device 50 and the server 10 must also be in a communication capable state.

However, when the settlement is performed in a place where the radio wave condition is bad, such as underground, or when the settlement is performed in a condition where the line is congested, such as at an event venue, or when the communication is limited or the communication speed is limited due to the fact that the amount of communication of the terminal 20 exceeds a certain amount for a certain period of time (for example, one month), it is expected that the settlement will be difficult as a result of the communication being impossible (or difficult) between the terminal 20 and the server 10. Therefore, a method of realizing settlement even in such a case will be exemplified below.

(2) Offline payment

A method of offline payment, which is one aspect of the method of the present disclosure, will be described with reference to a flowchart.

Hereinafter, "offline" indicates that the terminal 20 cannot communicate with the server 10, and "offline state" indicates a state of the offline. In addition, "offline settlement" means settlement performed by the server 10 in an offline state. It is assumed that the store code reader device 50 can communicate with the server 10.

Fig. 3 to 4 are flowcharts showing an example of the flow of processing executed by each apparatus in this case. The view of the figure is the same as the above-described flowchart.

The flow chart in fig. 3-4 is a flow chart that rewrites the flow chart in fig. 3-1 to an offline specification. In contrast to the flowchart of fig. 3-1, by way of example and not limitation, the processing steps in the online state (e.g., a240), the processing steps in the offline state (e.g., a250, B280), and the processing steps when returning from the offline state to the online state (e.g., a290, C290) differ.

After a130, the control unit 21 stores the received terminal display code (in this example, the terminal display code image) in the storage unit 28(a 240).

Here, "store" means to store the received terminal display code in the storage unit 28 so as to be available later.

In addition, in this specification, there are cases where "storing" is simply expressed as "storing". In addition, the terminal display code may be stored as "the terminal display code is stored in the terminal display code storage data".

In this process, the terminal display code (in this example, the terminal display code image) acquired from the server 10 in the online state is stored (stored) in the storage unit 28 of the terminal 20 so that offline settlement can be performed. When settlement is required in an off-line state, the settlement is executed by using the stored code for terminal display, and communication with the server 10 is not required.

The concrete description is as follows. Assume that the offline state is entered after a 240.

Here, the terminal 20 detects that the offline state is reached by any one of the following methods, by way of example and not by way of limitation.

(A) While the terminal 20 is running the settlement application, a connection confirmation request is transmitted from the server 10 to the terminal 20 at a regular timing or a specific timing, and a connection response including identification information (for example, an application ID) is transmitted from the terminal 20 to the server 10 in response to the connection confirmation request. In this case, the control unit 21 of the terminal 20 determines that the server 10 is in the offline state when the connection confirmation request cannot be received.

(B) While the terminal 20 is running the settlement application, a connection notification including identification information (for example, an application ID) is transmitted from the terminal 20 to the server 10 at a regular timing or a specific timing, and the server 10 transmits a connection confirmation to the terminal 20 for the connection notification. In the offline state, the connection notification cannot be transmitted from the terminal 20 to the server 10. Therefore, the control unit 21 of the terminal 20 determines that the terminal is in the offline state when detecting that a transmission error of the connection notification has occurred, by way of example and not limitation.

Further, by way of example and not limitation, the terminal 20 may determine whether or not it is in an offline state by acquiring information on the communication status of its own terminal 20 using a library, an application, or the like that acquires the connection status of the network.

In the offline state, when the code image for terminal display stored in a240 is displayed on the display unit 24(a250) and the user presents the code image for terminal display to a clerk or the like in the store, the control unit 51 performs control to cause the code reader 58 to read the code image for terminal display displayed on the display unit 24 of the terminal 20 (B250). Then, the control unit 51 shifts the process to B160.

After B160, when the settlement completion notification for the store is received from the server 10 via the communication I/F54 (B280), the clerk or the like of the store verbally notifies the user of the terminal 20 that the offline settlement is completed (successful) based on the received settlement completion notification for the store.

After C180, the control unit 11 transmits a terminal settlement completion notification to the terminal 20 (C290). However, in the offline state, the terminal 20 cannot receive the terminal-use settlement completion notification. When the terminal 20 returns to the online state, the terminal 20 receives a terminal settlement completion notification transmitted from the server 10. When receiving the terminal settlement completion notification from the server 10 via the communication I/F22, the control unit 21 displays the result of the settlement on the display unit 24 based on the received terminal settlement completion notification (a 290).

The above-described process is an example of a process for performing offline settlement.

In the offline settlement, as described above, the terminal display code generated by the server 10 is stored in the terminal 20 in an online state. When the terminal enters an offline state, the settlement is performed using the stored terminal display code.

Here, in the offline settlement, as described above, the terminal display code generated by the server 10 is stored in the terminal 20. In this case, the user of the terminal 20 may not use the stored terminal display code for a long time. In this case, the time during which the terminal 20 or the user of the terminal 20 is associated with the terminal display code becomes long.

Thus, for example, when a code image of the terminal display code stored in the terminal 20 is displayed on the terminal 20, the code image is captured by a camera or the like of the terminal 20 of another user, and is thus improperly used for settlement or the like.

< functional Structure >

(1) Function structure of server

Fig. 4-1 is a diagram showing an example of functions realized by the control unit 11 of the server 10 according to the present embodiment.

Hereinafter, the user of the terminal 20 will be described as an example of performing the above-described settlement of the settlement type "terminal code display" by using the settlement application stored in the terminal 20, which is not limited to this but is an example.

The server 10 has a settlement management processing unit 111 as a function realized by the control unit 11.

The settlement management processing unit 111 has a function of performing settlement management processing for managing various information and data related to a settlement application executed in the terminal 20 and managing settlement using electronic money for the terminal 20 or the user of the terminal 20, based on the settlement management processing program 151 stored in the storage unit 15.

The settlement management processing section 111 includes, as functional sections, not by way of limitation, but by way of example: a terminal display code generation processing unit 1111 that generates a terminal display code by a terminal display code generation process; a settlement processing unit 1113 that performs settlement by settlement processing; and a code expiration date management processing section 1115 that sets and manages a code expiration date.

By way of example and not limitation, the terminal display code generation processing unit 1111 generates a terminal display code image represented by a two-dimensional code. The two-dimensional code is a code of a display type that holds information in the horizontal direction and the vertical direction, and includes a matrix type two-dimensional code (hereinafter, referred to as a "matrix code") in which small squares are arranged in the vertical direction and the left and right direction, a stack type two-dimensional code (hereinafter, referred to as a "stack code") in which a one-dimensional code (such as a barcode, without limitation) is repeated in the vertical direction, and the like.

In the present embodiment, for the sake of simplifying the description, a QR code (registered trademark), which is an example of a widely used matrix code, is described as an example of a terminal display code.

Unlike the present embodiment, as a matrix code other than the QR code, a code such as an SP code, a veri code, a maxi code, a CP code, or a chameleon code may be used or may not be used. In addition, various stacked codes may be used instead of the matrix code, or may not be used.

The terminal display code generation processing unit 1111 may generate a one-dimensional code (a barcode, for example, but not limited thereto) as the terminal display code in addition to a two-dimensional code (a QR code, for example, but not limited thereto), or may not generate the code. This is because some stores may not support reading of a two-dimensional code but may support reading of a one-dimensional code.

The settlement processing unit 1113 has a function of performing settlement processing based on information transmitted from the store POS system 40 or information transmitted from the terminal 20, by way of example and not limitation.

Fig. 4-2 is a diagram showing an example of information stored in the storage unit 15 of the server 10 according to the present embodiment.

The storage unit 15 stores, as a program, a settlement management processing program 151 that is read by the control unit 11 and executed as settlement management processing, not by way of limitation but by way of example.

Further, not limited to this, the storage unit 15 stores, as data, user registration data 153, store registration data 155, settlement management database 157, and code management database 159.

The user registration data 153 is registration data of the terminal 20 using the settlement service and the user of the terminal 20, and fig. 4 to 3 show an example of the data structure thereof.

By way of example and not limitation, in the user registration data 153, a user name, a terminal telephone number, a terminal mail address, an application ID, an authentication password, and other registration information are associated and stored.

The user name is the name of the user of the terminal 20 who uses the settlement service, and the name registered when the user of the terminal 20 uses the settlement service is stored.

The terminal telephone number is the telephone number of the terminal 20 of the user name, and the telephone number of the terminal 20 registered when the user of the terminal 20 uses the settlement application is stored.

The terminal mail address is the mail address of the terminal 20 of the user name, and stores the mail address of the terminal 20 registered when the user of the terminal 20 uses the settlement application.

The terminal telephone number and the terminal mail address are examples of identification information (hereinafter, referred to as "terminal identification information") for identifying the terminal 20.

The application ID is an account (account information) of the settlement application, and is an ID capable of identifying the terminal 20 or the user of the terminal 20. By way of example and not limitation, the application ID is set by the server 10 and stores a unique ID.

The authentication password is a password for authentication that the user is required to input when the terminal 20 of the user name performs an authentication process for settlement (hereinafter, simply referred to as "authentication process"), and the password set by the user is stored.

The authentication process for settlement is not necessarily required, and may not be performed. In this case, the authentication password does not need to be stored in the user registration data 153.

The other registration information is other registration information of the user name, and includes, by way of example and not limitation, a user icon image, which is image data of an icon used by the user in the settlement application, or a profile of the user, and the like.

The store registration data 155 is registration data of a store cooperating with an operator (operator of the server 10) who provides the settlement application. Fig. 4 to 4 show an example of a data structure of the store registration data 155A as an example of the store registration data 155.

In the store registration data 155A, not limited but an example, an industry type, a store name, store position information, store POS system information, and a store ID are associated and stored as store information.

The business type stores therein the business type of the store. These industries include, by way of example and not limitation, various industries such as "convenience stores," supermarkets, "" drug offices, "" wine houses, "" department stores, "" restaurants, "" bookstores, "and" clock stores.

In the store name, store names of stores included in (belonging to) stores of the industry type with respect to each industry type.

The store position information includes position information of the location of the store having the store name (hereinafter referred to as "store position information"). The store position information may indicate the location of the store by two-dimensional or three-dimensional position coordinates, or may indicate the location of the store by latitude and longitude (latitude, longitude, and optionally height).

The store POS system information stores information on the store POS systems 40 used in the stores. This store POS system information includes, by way of example and not limitation, information necessary for the server 10 to communicate with the store code reader device 50 or the store server 70.

The store POS system 40 executes processing in cooperation with the server 10, but is not limited to this and an example, and may acquire a software package for a settlement application provided (distributed) by the server 10 in advance, store the software package in the store reader device 50 or the store server 70, and use the software package by calling a program for settlement processing of the store. For example, using an Application Programming Interface (API) as an example, the store code reader device 50 initiates the API to effect transmission and reception of information to and from the server 10.

In addition, not limited to this but as an example, the server 10 may receive information such as the business type of the store, the store name, the store location information, and the store POS system information from the store server 70 of the store, and store it in the store registration data 155.

The store ID is an ID that functions as identification information for identifying the store of the store name. This shop ID is set by the server 10 for each shop and stores a unique ID, not by way of limitation, but as an example.

The store ID is an example of store identification information.

The settlement management database 157 is a database that cumulatively stores data for managing information related to settlement of the user of each terminal 20. Fig. 4 to 5 show an example of the structure of the settlement management database 157A as an example of the settlement management database 157.

The settlement management database 157A stores therein settlement management data generated for each terminal 20 or each user of the terminal 20.

Each settlement management data is not limited to the above, but stores, as an example, an application ID, a balance, a point, an upper limit daily set amount of money, an automatic charge setting, and settlement history data.

The application ID stored in the user registration data 153 is stored in the application ID.

A balance store associated with the application ID is stored in the balance.

Various services associated with the settlement application and points that can be accumulated at affiliated stores who cooperate with the operator of the payment application are stored in the points. By way of example and not limitation, points have a value of 1 cents, which corresponds to 1 yen, and may be redeemed in a settlement application for settlement, in addition to being redeemable for gift certificates or merchandise, etc.

The daily upper limit amount of the amount of money that the terminal 20 or the user of the terminal 20 having the application ID can use for settlement is stored in the daily upper limit setting amount.

The automatic charge setting is a setting of whether to automatically replenish (automatically charge) the electronic money when the balance becomes a remaining smaller amount of money (e.g., "500 yen") or "0 yen", and stores "ON" when the user of the terminal 20 sets the automatic charge and stores "OFF" in other cases. By way of example and not limitation, automatic recharge may be from a bank account or the like registered by the user of the terminal 20.

The settlement history data is data related to the history of settlement by the user of the application ID, and is not limited to this, but is an example, and for the application ID, a settlement date and time, a store ID, a settlement store name, and a settlement amount, which are the date and time at which settlement is performed by the server 10, the store ID, the name of the store at which settlement is performed, and the amount of settlement, which is the amount of settlement performed, are stored in chronological order in association with each other.

In addition, the above-mentioned settlement management data does not necessarily have to store all the above-mentioned information. Not limited to this, but as an example, some or all of the points, the daily upper limit set amount, and the automatic charge setting may not be stored in the settlement management data.

Further, the server 10 may not store the settlement history data by transmitting the information of the settlement history to the terminal 20 and storing the information in the terminal 20 every time the settlement is performed.

The code management database 159 is a database for managing codes (terminal display codes in the present embodiment), and an example of the data structure thereof is shown in fig. 4 to 6.

The code management database 159 stores, by way of example and not limitation, code management data generated for each application ID of the settlement application.

The application ID is stored in each code management data, and the code generation date and time, the code serial number, the settlement number, and the code expiration date are stored in chronological order in association with each other, by way of example and not limitation.

The date and time at which the terminal display code is generated based on the information clocked by the clock section 19 is stored in the code generation date and time.

A number for identifying the code is stored in the code serial number. For example, the code sequence numbers are set and stored in order from old to new.

The settlement number is stored with a settlement number issued when the terminal display code is generated.

The code expiration date is a date when the settlement using the terminal display code is valid, and is a date managed by the server 10 for each generated terminal display code.

For example, in the case where the date and time at which the terminal display code is generated by the server 10 is the "code generation date and time" and the valid time of the code set by the server 10 is the "code valid time", the code valid period management processing section 1115 sets and stores the "period from the code generation date and time to the elapse of the code valid time" as the code valid period, by way of example and not limitation.

The code expiration date is a date set by the server 10, and may be a date in which the terminal display code can be used to perform settlement.

Here, the code valid time may be appropriately changed, and may be set to, for example, a time such as "6 hours", "12 hours", "18 hours", and "24 hours", without limitation.

However, if an excessively long time is set as the code valid time, the time during which the terminal 20 or the user of the terminal 20 is associated (bound) with the code for terminal display becomes long, possibly resulting in the above-described problems. Therefore, the code validity time may be about 24 hours at the maximum.

The data of the terminal display code stored in the code management data is not limited to the above and may be deleted from the code management data after the settlement processing is performed by using the terminal display code.

Further, by way of example and not limitation, when the code expiration date associated with the terminal display code has passed, the data of the terminal display code may be deleted from the code management data.

Further, the data of the terminal display code that becomes unusable may be deleted from the code management data as described above, but the data is not limited to this and is an example, and the flag "usable/unusable" indicating whether or not the terminal display code is usable may be set in association with the data of the terminal display code. Therefore, the flag may be set to "unusable" or may not be set to the terminal display code that has become unusable.

In the above, for example, the code generation date and time may not be stored in the code management data.

Further, instead of or in addition to the application ID, terminal identification information such as a terminal telephone number stored in the user registration data 153 may be stored in the code management data, or not.

(2) Functional structure of terminal

Fig. 4 to 7 are diagrams showing an example of functions realized by the control unit 21 of the terminal 20 in the present embodiment.

The terminal 20 has a settlement application processing unit 211 as a function realized by the control unit 21.

The settlement application processing section 211 has a function of executing settlement application processing for performing processing relating to settlement based on the settlement application software 281 stored in the storage section 28.

The settlement application processing unit 211 includes, as a functional unit, a code display processing unit 2113, and the code display processing unit 2113 executes code display processing, by way of example and not limitation.

In the present embodiment, the processing related to the settlement is a concept including processing having some relation with the settlement, more specifically, the whole processing executed in the terminal 20 as processing related to the settlement, such as processing for acquiring the terminal display code from the server 10 (including processing for requesting the server 10 to generate the terminal display code and processing for receiving the generated terminal display code from the server 10), processing for storing the terminal display code acquired from the server 10, processing for displaying the stored terminal display code image (code display processing), processing for acquiring the terminal settlement completion notification from the server 10, and the like, and more specifically, as processing related to the settlement.

Fig. 4 to 8 are diagrams showing an example of information stored in the storage unit 28 of the terminal 20 in the present embodiment.

The storage unit 28 stores, as an example and not by way of limitation, the settlement application software 281 as application software obtained in advance by downloading or the like from the server 10.

The settlement application software 281 includes, by way of example and not limitation, a settlement application 282 and settlement application data 283.

The settlement application data 283 stores various data used in the settlement application software. The settlement application data 283 is not limited to this, but stores terminal display code storage data 2831, settlement data 2832, and store data 2833, as an example.

The terminal display code storage data 2831 is data in which a terminal display code acquired from the server 10 in an online state is stored. Fig. 4 to 9 show an example of a data structure of the terminal display code storage data 2831A as an example of this data.

In the terminal display code storage data 2831, a code reception date and time, a code serial number, code data, and a code expiration date are associated and stored, by way of example and not limitation.

The date and time of reception of the code is not limited to the above example, and the date and time of reception of the code for terminal display from the server 10 by the storage terminal 20 is stored.

The code serial number received by the terminal 20 from the server 10 together with the terminal display number is stored in the code serial number.

The code data is not limited to this, but is data of a code image of the code for terminal display received by the terminal 20 from the server 10 as an example.

The code expiration date is not limited to this, but is, for example, a code expiration date that is received by the storage terminal 20 from the server 10 together with the terminal display code and is set in association with the terminal display code.

The data of the terminal display code stored in the 1 st terminal display code storage data 2831A is not limited to this, but is an example, and the server 10 performs settlement processing using the terminal display code, and may delete the data from the 1 st terminal display code storage data 2831A after receiving a terminal settlement completion notification from the server 10 (in the case of performing offline settlement, the online state is restored and the terminal settlement completion notification is received from the server 10).

Further, by way of example and not limitation, when the expiration date of the code associated with the terminal display code has passed, the data of the terminal display code may be deleted from the 1 st terminal display code storage data 2831A.

Note that, instead of deleting the data of the terminal display code that becomes unusable from the 1 st terminal display code storing data 2831A as described above, the flag "usable/unusable" indicating whether the terminal display code is usable or not may be set in association with the data of the terminal display code, by way of example and not limitation. Therefore, the flag may be set to "unusable" or may not be set to the terminal display code that has become unusable.

In the above, for example, the code reception date and time or the code expiration date may not be stored in the 1 st terminal display code storage data 2831A.

In the present embodiment, the code expiration date associated with the code for terminal display is transmitted from the server 10 to the terminal 20, but in contrast to this, the code expiration date associated with the code for terminal display may not be transmitted from the server 10 to the terminal 20.

In this case, the 1 st terminal display code storage data 2831A may store the code expiration date and time, the code serial number, and the code data in association with each other, without limiting the storage to the code expiration date and time, but by way of example. This point will be explained later in a modification.

Further, instead of or in addition to the code reception date and time, the date and time at which the terminal display code received from the server 10 is stored in the 1 st terminal display code storage data 2831A (hereinafter, referred to as "code storage date and time") may be stored, not limited to this but an example.

In addition, the code data does not necessarily have to store data of a code image of the code for terminal display, and original information (in the present embodiment, a number for settlement) of the code for terminal display may be stored instead of or in addition to the data, or not. Details will be described later.

The settlement data 2832 is data for settlement stored in the terminal 20, and fig. 4 to 10 show a configuration of the settlement data 2832A as an example of the data.

The settlement data 2832A is not limited to this, but stores, as an example, an application ID, points, a balance, a daily upper limit set amount, an automatic charge setting, and settlement history data.

The control unit 21 associates and stores in chronological order, based on the terminal settlement completion notification received from the server 10 after the online state is restored, by way of example and not limitation, a settlement date and time, which is the date and time of settlement by the server 10, a store ID, which is the ID of a store settled by the server 10, a settlement store name, which is the name of the store ID, and a settlement amount, which is the amount of settlement by the server 10.

The store data 2833 is not limited to this, but is stored in various store information stored in the store registration data 155A of the server 10, by way of example.

By way of example and not limitation, the latest store information may be distributed from the server 10 to the terminal 20 at the timing of updating the settlement application 281, and the store data 2833 may be updated.

The storage unit 28 stores, by way of example and not limitation, terminal data 289.

The terminal data 289 is data related to the terminal 20, and includes, by way of example and not limitation, terminal identification information such as a terminal telephone number or a terminal mail address, and various setting information on the terminal 20 side.

< example of display Screen >

Fig. 4 to 11 are diagrams showing an example of the top page of the settlement application displayed on the display unit 24 of the terminal 20 in the present embodiment.

The configuration of the home page is the same as that in fig. 3-2, and here, a state in which the "code icon" is touched by the user of the terminal 20 is displayed.

Fig. 4 to 12 are diagrams showing an example of a code display screen displayed on the display unit 24 of the terminal 20 in the present embodiment. By way of example and not limitation, the code display screen is displayed by touching the "code icon" as shown in fig. 4-11 in an offline state.

In the code display screen, the terminal display code stored in the storage unit 28 of the terminal 20 is read, and as the code image, a one-dimensional 1 st terminal display code image represented by a barcode and a two-dimensional 1 st terminal display code image QC1 represented by a QR code are displayed in different areas on the display screen. Further, a settlement number indicated by a 12-digit number is displayed below the one-dimensional 1 st terminal display code image.

When performing offline settlement, the user of the terminal 20 presents the aforementioned code display screen to the store clerk at the code cash register 60, and the code image for terminal display is read by the store code reader device 50 to perform settlement. In this case, the store code reader device 50 transmits, as an example and not by way of limitation, settlement request information including information (in the present example, a settlement number) obtained by decoding the read terminal display code image and information on the time when the terminal display code image is read to the server 10, and causes the server 10 to perform settlement. Details will be described later.

Fig. 4 to 13 are views showing an example of a settlement result screen displayed on the display unit 24 based on the terminal settlement completion notification received from the server 10 after the return from the offline state to the online state.

On the settlement result screen, a message "you can confirm detailed information from the" settlement history "and a" confirmation icon "for confirming the settlement history are displayed in a pop-up form together with" settlement completion "text at the center portion of the code display screen shown in fig. 4 to 12.

In the above example of the display screen, since the user of the terminal 20 does not need to know whether the terminal is in the on-line state or the off-line state, the code display screen can be displayed by, for example, touching the code icon, so that the convenience of the user can be improved.

< treatment >

Fig. 4 to 14 are flowcharts showing an example of the flow of processing executed by each apparatus in the present embodiment. The 1 st settlement application process as an example of the settlement application process executed by the control unit 21 of the terminal 20, the 1 st shop settlement process as an example of the shop settlement process executed by the control unit 51 of the shop reader device 50, and the 1 st settlement management process as an example of the settlement management process executed by the control unit 11 of the server 10 are shown in this order from the left side.

The flowcharts of fig. 4 to 14 are partially rewritten the flowcharts of fig. 3 to 4. Compared with the flowcharts of fig. 3 to 4, the present invention is not limited to the above, but differs in steps a330 to a350, B360, C320, C330, C370, and the like.

In this process, identification information for identifying the terminal 20 or the user of the terminal 20 will be described as the application ID as an example.

After C110, the control unit 11 of the server 10 performs a terminal display code generation process (C320). Specifically, by way of example and not limitation, a random number of a predetermined number of bits (for example, a number of bits of about 10 to 12 bits) is generated as a number for settlement by using a method (algorithm) for generating a random number of a predetermined number of bits. Then, by way of example and not limitation, a code image for terminal display is generated in which at least the settlement number is included as the original information. More specifically, at least the calculation number is encoded (symbolized) and patterned (imaged) to generate a terminal display code image represented by an image of a two-dimensional code (e.g., QR code).

Then, the code generation date and time based on the time counting information of the clock unit 19, the set code serial number, the generated number for settlement, and the code expiration date set for the generated terminal display code are stored in association with the code management data of the application ID included in the received code generation request information in the code management database 159.

Then, by way of example and not limitation, the control unit 11 transmits the generated terminal display code (in this example, the code image) and the code expiration date set for the terminal display code to the terminal 20 via the communication I/F14 together with the code serial number (C330).

Next, when the terminal display code (in this example, the terminal display code image) and the code expiration date are received from the server 10 via the communication I/F22 (a330), the control unit 21 of the terminal 20 stores the received terminal display code (in this example, the terminal display code image) (a 340). Specifically, the code data of the received terminal display code and the expiration date of the received code are stored in association with the code reception date and time in the 1 st terminal display code storage data 2831A, by way of example and not limitation.

In the offline state, not limited to the above, but as an example, when a code display operation is performed by the user of the terminal 20, the code display processing unit 2113 performs code display processing (a 350). Specifically, by way of example and not limitation, the code data of the terminal display code stored in the 1 st terminal display code storage data 2831A is read, and the code display screen including the terminal display code image is displayed on the display unit 24.

Then, when the user of the terminal 20 presents the code image for terminal display displayed on the display unit 24 to a clerk or the like in the store, the control unit 51 controls the code reader 58 to read the code image for terminal display displayed on the display unit 24 of the terminal 20 (B350).

Then, the control unit 51 accesses the server 10 through the communication I/F54 by using the above-described application interface (API) or the like, and transmits settlement request information including at least a settlement number obtained by decoding the read terminal display code image, store identification information, a predetermined settlement amount, and a time at which the terminal display code image is read (hereinafter referred to as "code reading time") to the server 10 through the communication I/F54 (B360).

When the settlement request information is received from the store code reader device 50 via the communication I/F14 (C160), the control unit 11 performs the settlement process (C370).

Specifically, it is determined whether or not the settlement number included in the received settlement request information is stored in the code management database 159 in association with the application ID. When it is determined that the code is stored, it is determined whether or not the code reading time included in the received settlement request information is within the validity period of the code stored in association with the settlement number in the code management data of the application ID. Then, in the case where this condition is satisfied, "settlement is possible" is determined, and settlement is performed by subtracting a settlement predetermined amount from the balance in the settlement management data of this application ID stored in the settlement management database 157A.

The terminal display code stored in the terminal 20 can be used not only for off-line settlement but also for on-line settlement. That is, it is not necessary to determine (detect) whether or not the terminal 20 is in the offline state, and the settlement can be performed by using the terminal display code stored in the terminal 20 regardless of the online state or the offline state.

< code >

In the above-described processing, an example is shown in which the terminal 20 requests the server 10 to generate the code image for terminal display, and the code image for terminal display generated by the server 10 is transmitted to the terminal 20, but the present invention is not limited to this, and for example, the terminal 20 may request the server 10 to generate the original information (in the present example, the number for settlement) and may not transmit the original information generated by the server 10 to the terminal 20.

Specifically, in the processing of fig. 3-1, the control unit 21 transmits code generation request information for requesting the server 10 to generate the source information in a 110. Then, based on the code generation request information, the control unit 11 generates original information in C120, and transmits the generated original information to the terminal 20 in C130.

When the source information is received from the server 10 in a130, the control unit 21 generates a code image for terminal display based on the received source information. Then, the control unit 21 displays the generated code image for terminal display on the display unit 24.

Similarly, in the processing of fig. 3 to 4, when the original information is received from the server 10 in a130, the control unit 21 stores the received original information in the terminal display code storage data 2831 in a 240. Then, the control section 21 reads the stored original information from the terminal display code storage data 2831, and generates a terminal display code image based on the read original information. Then, in a250, the control unit 21 displays the generated code image for terminal display on the display unit 24.

Similarly, in the processing of fig. 4 to 14, when the source information and the code expiration date are received from the server 10 in a330, the control unit 21 stores the received source information and the received code expiration date in the 1 st terminal display code storage data 2831A in a 340. Then, when the user of the terminal 20 performs an operation of displaying the code in an off-line state, the control section 21 reads the stored original information from the 1 st terminal display code storage data 2831 and generates a terminal display code image based on the read original information. Then, in a350, the control unit 21 displays a code display screen including the generated code image for terminal display on the display unit 24.

Further, unlike the above, although the terminal 20 requests the server 10 to generate the code image for terminal display and the code image for terminal display generated by the server 10 is transmitted to the terminal 20, the terminal 20 may store not the code image for terminal display received from the server 10 but original information obtained by decoding the code image for terminal display received from the server 10, or may not store it.

< Effect of embodiment 1 >

According to embodiment 1, the terminal receives code information associated with the expiration date by the server from the server, and stores the received code information in the storage section. Further, offline settlement can be realized by executing processing relating to settlement based on the stored code information.

Specifically, in embodiment 1, the terminal 20 receives, from the server 10 via the communication I/F22, a code image for terminal display or a number for settlement (not limited, but an example of the 1 st validity period) associated with a code validity period (not limited, but an example of the 1 st validity period) by the server 10, and then the terminal 20 stores the received code image for terminal display or number for settlement in the storage unit 28 via the control unit 21.

The terminal 20 executes a code display process (not limited to, but an example of a process related to settlement) for displaying the terminal display code image on the display unit 24 via the control unit 21 based on the stored terminal display code image or the stored settlement number.

Further, embodiment 1 shows a configuration in which: the settlement is executed by the server 10 based on the code reading time (not limited, but an example of the time based on the processing related to the settlement) and the code expiration date, the code reading time being the time at which the code image for terminal display displayed in the code display processing is read by the shop code reader device 50.

As an example of the effect obtained by such a configuration, even when the communication environment or the communication state of the terminal is poor or unstable, the settlement can be appropriately executed by the server in accordance with the 1 st validity period and the timing based on the processing related to the settlement. Further, for example, since the settlement must be performed within the 1 st term of validity associated with the 1 st code information, it is possible to prevent the risk of being improperly used for the settlement due to the code information stored in the terminal being stolen by a hacker or the like, or when a code image corresponding to the code information stored in the terminal is displayed on the terminal, the code image being photographed by a camera or the like of the terminal of another user, or the like.

In embodiment 1, the terminal 20 includes a processor that reads a settlement application 282 (not limited to a specific example of a program) stored in a memory and executes settlement application processing by the settlement application 282.

The processor executes processing for receiving, from the server 10, a terminal display code image or a settlement number (not limited, but an example of the 1 st validity period) associated with the code validity period (not limited, but an example of the 1 st validity period) by the server 10, processing for storing the received terminal display code image or the settlement number in the memory, and code display processing (not limited, but an example of processing related to settlement) based on the stored terminal display code image or the settlement number.

In embodiment 1, the following configuration is shown: the settlement is executed by the server 10 based on the code reading time (not limited to, but an example of the time based on the processing related to the settlement) and the code expiration date, the code reading time being the time when the code image for terminal display displayed in the code display processing is read by the shop code reader device 50.

With this configuration, the same effects as described above can be obtained.

In embodiment 1, the terminal 20 receives the terminal display code and the code expiration date thereof (not limited to, but one example of information on the 1 st expiration date) from the server 10 via the communication I/F22. In embodiment 1, the control unit 21 stores the received code expiration date in association with the terminal display code in the terminal display code storage data 2831.

As an example of the effect obtained by such a configuration, the terminal side can grasp the 1 st expiration date associated with the 1 st code information by the server.

In embodiment 1, the server 10 stores the code image for terminal display or the number for settlement (not limited, an example of the 1 st code information) in association with the code expiration date (not limited, an example of the 1 st expiration date) in the code management data.

The server 10 transmits the terminal display code image or the settlement number to the terminal 20 that performs the code display processing via the communication I/F14, and receives the settlement number and the code reading time (not limited to, an example based on the time of the processing related to settlement) at which the terminal display code image displayed in the code display processing is read by the store code reader device 50 via the communication I/F14.

Further, in embodiment 1, the server 10 performs the settlement processing by the control unit 11 based on the code expiration date associated with the received settlement number and the received code reading time.

As an example of the effect obtained by such a configuration, even in a case where the communication state or communication environment of the terminal is not good, the server can properly execute the settlement based on the 1 st code information associated with the received 1 st code information and the timing based on the processing related to the settlement executed at the terminal.

In embodiment 1, the server 10 includes a processor that reads a settlement management processing program 151 (not limited to, but an example of a program) stored in a memory and executes settlement management processing based on the settlement management processing program 151.

In embodiment 1, the following configuration is shown, namely: the processor executes processing for associating and storing a code image for terminal display or a number for settlement (not limited, an example of the 1 st code information) with a code expiration date (not limited, an example of the 1 st expiration date) in code management data, processing for transmitting the code image for terminal display or the number for settlement to the terminal 20 that executes the code display processing and receiving the number for settlement and code reading timing (not limited, an example of timing based on processing related to settlement) at which the code image for terminal display displayed in the code display processing is read by the shop reader device 50, and settlement processing based on the code expiration date associated with the received number for settlement and the received code reading timing.

With such a configuration, the same effects as described above can be obtained.

< modification (1) > < 1 st modification

In embodiment 1, the period from the start of code display until the elapse of the code display time is defined as a "code display deadline", but the present invention is not limited to this.

By way of example, the time or date and time when the period from when the code is displayed to when the code display time elapses may be defined as a "code display deadline".

Similarly, in embodiment 1, the period from the code generation date and time to the elapse of the code validity time is defined as "code validity period", but the present invention is not limited to this.

By way of example, the time or date and time when the period from when the code is displayed to when the code display time elapses may be defined as the "code expiration date".

Further, the present invention is not limited to this, and the date and time when the server 10 transmits the code for terminal display to the terminal 20 (hereinafter referred to as "code transmission date and time") may be set as the date and time when the code validity period starts, instead of the code generation date and time being set as the date and time when the code validity period starts, as an example. That is, the "period from the date and time of code transmission until the code validity time elapses" may be the code validity period, or may not be the same. In this case, the server 10 stores the code expiration date in the code management data after transmitting the code for terminal display to the terminal 20.

< modification (2) > < 1 st

In embodiment 1, the code for terminal display (not limited, but an example of code information) and the code expiration date (not limited, but an example of information on the expiration date) are transmitted from the server 10 and received by the terminal 20, but the present invention is not limited thereto.

Specifically, the code validity time is stored in advance in the settlement application data 283 of the terminal 20, by way of example and not by way of limitation. Then, not limited to this but as an example, the code generation date and time (not limited but one example of information on the expiration date) may be transmitted from the server 10, and the terminal 20 may receive the code generation date and time from the server 10, or not. In this case, the terminal 20 may specify the code validity period based on the received code generation date and time and the code validity time stored in the settlement application data 283.

Further, as described above, the code transmission date and time may be the date and time at which the code valid period starts, and the same applies here. That is, the date and time at which the code validity period starts are transmitted from the server 10 to the terminal 20 as information relating to the validity period. Then, the terminal 20 can specify the code validity period based on the code validity time and the date and time at which the received code validity period starts.

In addition, the date and time when the code validity period ends is transmitted from the server 10 to the terminal 20 as information on the validity period, by way of example and not limitation. Then, the terminal 20 may determine the code valid period based on the code valid time and the date and time when the received code valid period ends.

< modification (3) > < 1 st modification

In embodiment 1, the code expiration date associated with the terminal display code is transmitted from the server 10 to the terminal 20, but the present invention is not limited thereto.

Specifically, by way of example and not limitation, the code expiration date associated with the code for terminal display may not be transmitted from the server 10 to the terminal 20, and the code expiration date set by the server 10 may not be known on the terminal 20 side. In this case, the terminal display code storage data 2831 (the 1 st terminal display code storage data 2831A or the 2 nd terminal display code storage data 2831B) may store the code expiration date in association with the code reception date and time, the code serial number, and the code data, without being limited thereto, but by way of example.

In this case, a temporary code expiration date (hereinafter, referred to as a "temporary code expiration date") may be set on the terminal 20 side, or may not be set. Specifically, the term "a period from the code reception date and time (or the code storage date and time) to the elapse of the code effective time" may be set as the temporary code effective period, or may not be set as such, as an example, without limitation. In this case, the terminal 20 may or may not execute the processing described in each embodiment and each modification using the set temporary code expiration date.

< modification (4) > < 1 st

Although one code acquired from the server 10 in the on-line state may be stored in the terminal display code storage data 2831 of the storage unit 28 of the terminal 20, a plurality (2 or more) of codes acquired from the server 10 in the on-line state may be stored.

Fig. 4 to 15 are diagrams showing an example of the terminal 2 nd display code storing data 2831B in this case.

The 2 nd terminal display code storage data 2831B stores data of a plurality of terminal display codes. Specifically, by way of example and not limitation, the code reception date and time, the code serial number, the code data, and the code expiration date are associated and stored in time series.

In this case, the control unit 21 of the terminal 20 may read code data of the oldest terminal display code among the terminal display codes stored in the 2 nd terminal display code storage data 2831B and display a code display screen including the terminal display code image on the display unit 24, in the code display process, not by way of limitation but by way of example.

Therefore, since a plurality of codes can be stored in the terminal 20, even if offline settlement needs to be performed a plurality of times, settlement can be immediately performed, and convenience of the user can be improved.

< modification (5) > < 1 st

In embodiment 1, the settlement number or the terminal display code image including the settlement number is used as the "code information" in the present disclosure, but the present invention is not limited thereto. For example, a token that is a kind of authentication information or a code image for terminal display that includes the token may also be used as "code information" in the present disclosure.

In this case, the settlement number is not included in the terminal display code image, but is not limited to this, and a token issued by using a method (algorithm) for generating a random token may be included in the terminal display code image, or may not be included. In this case, the identification information for identifying the terminal 20 or the user of the terminal 20 may be stored in the code management data of the code management database 159 of the storage unit 15 in association with the issued token on the server 10 side.

By way of example and not limitation, a "token" is one type of authentication information used by the server 10 to authenticate that the terminal 20 or the user of the terminal 20 is a legitimate terminal 20 or a legitimate user of the terminal 20. The "authentication information" is information issued by a certificate authority, and the above-mentioned token is used as authentication information issued by the server 10 as the certificate authority to authenticate the terminal 20 or the user of the terminal 20.

The token may be expressed as a "random token", an "access token", a "settlement token", or the like. Since the token is issued at random as described above, the token is different each time the code for terminal display is generated. Thus, the token can be said to act as a one-time password.

In addition to the settlement number and the token, the store code reader device 50 that has read the code image for terminal display may include information such as a URL (uniform Resource locator) for accessing a settlement web page provided by the access server 10, which is an example of access information for accessing a web site or a web page provided by the server 10, or may not.

< modification (6) > < 1 st modification

In the code display screen, the information of the code display period or the information of the code expiration period may be displayed in a region different from the region in which the code image for display by the display terminal is displayed, or may not be displayed.

The code display period is not limited to a specific one, but includes, as an example, information such as "code display period", "remaining time of code display period", "time or date and time at which the code display period ends", "code display time", and the like.

Further, the information on the code display period may be information related to the code display period.

Further, the information on the code validity period is not limited but includes, as an example, information such as "code validity period", "remaining time of code validity period", "time and date at which code validity period ends", "code validity time", and the like.

The information on the validity period of the code can be said to be information on the validity period of the code.

Fig. 4 to 16 are diagrams showing an example of a code display screen in the present modification.

The remaining time of the code display deadline is displayed below the two-dimensional 1 st-terminal-display code image QC1 on the code display screen, which is not limited to this but is an example.

The remaining time of the code display period is not limited, but is displayed and updated based on the time counted by the clock unit 29A with reference to the timing (timing of starting display) at which the code display screen is displayed, by way of example.

In the display example herein, the remaining time of the code display term is displayed in the same mode as in fig. 3 to 3 so as to be easily understood by the user. However, unlike this, the remaining time of the code display period may be displayed in a mode different from that of fig. 3 to 3, or may not be.

Fig. 4 to 17 are diagrams showing an example of a code display screen in the present modification.

The code display screen is not limited to this, but shows, as an example, the remaining time of the 1 st code expiration date associated with the 1 st terminal display code image, together with the hourglass mark (image), above the two-dimensional 1 st terminal display code image QC 1.

The remaining time of the 1 st code expiration date is displayed and updated based on, by way of example and not limitation, the code expiration date stored in association with the terminal display code among the terminal display codes stored in the terminal display code storage data 2831 and the time counted by the clock unit 29A.

Fig. 4 to 18 are diagrams showing an example of a code display screen in the present modification.

The code display screen is a combination of the code display screen of fig. 4 to 16 and the code display screen of fig. 4 to 17.

Specifically, by way of example and not limitation, the remaining time of the 1 st code valid period and the remaining time of the 1 st code display period are displayed above and below the 1 st terminal display code image QC1, respectively.

Fig. 4 to 19 are diagrams showing an example of a code display screen in the present modification.

The code display screen is basically the same as that of fig. 4 to 18, but the display of the information of the code expiration date is different.

Specifically, the information of the valid period of the code is displayed to indicate that the 1 st terminal display code is valid from the time when the valid period of the code starts until the valid period of the code elapses, and the display character "2019/06/10 is valid for 12 hours from 9: 00", for example, but not limited thereto.

The code display screens in fig. 4 to 16 to 4 to 19 may be code display screens displayed in an offline state or code display screens displayed in an online state.

Further, instead of displaying the information of the valid period of the code, the information of the valid period of the temporary code may be displayed, by way of example and not limitation.

< Effect of modification (6) 1 >

This modification shows the following configuration: the terminal 20 displays information (not limited, but an example of the 1 st validity period information) such as the validity period of the code or the remaining time of the validity period of the code in an area (not limited, but an example of the display area of the terminal) within the code display screen.

As an example of the effect obtained by such a configuration, the information of the 1 st term of validity may be notified to the user of the terminal.

In addition, the present modification shows the following configuration: the terminal 20 displays information such as the valid period of the code or the remaining time of the valid period of the code (not limited, but an example of the 1 st valid period information), a code image for terminal display stored in the terminal 20, and a number for settlement (not limited, but an example of the 1 st code information) in an area (not limited, but an example of a display area of the terminal) within the code display screen.

As an example of the effect obtained by such a configuration, the information on the 1 st expiration date and the 1 st code information can be notified to the user of the terminal, and the convenience of the user can be improved.

In addition, the present modification shows the following configuration: the terminal 20 displays information (not limited, but an example of the 1 st validity period information) such as the validity period of the code or the remaining time of the validity period of the code in an area (not limited, but an example of a display area of the terminal) in the code display screen in the offline state.

As an example of the effect obtained by such a configuration, information on the 1 st term of validity can be displayed in the display area of the terminal based on the communication state of the terminal. For example, even when the communication environment or the communication state of the terminal is not good or unstable, the information of the 1 st validity period can be displayed in the display area of the terminal, thereby improving the convenience of the user.

In addition, the present modification shows the following configuration: the terminal 20 displays a code image for terminal display or a number for settlement (not limited, an example of the 1 st code information) stored in the terminal 20 and information such as a code display term or a remaining time of the code display term (not limited, an example of a term which is different from the 1 st valid term and can use the 1 st code information) in an area within the code display screen.

As an example of the effect obtained by such a configuration, the 1 st code information and the date different from the 1 st expiration date by which the 1 st code information can be utilized can be notified to the user of the terminal.

< modification (7) > < 1 st

The display screen of the settlement application described in embodiment 1 is merely an example, and design changes can be appropriately made.

Fig. 4 to 20 are diagrams showing an example of the top page of the settlement application displayed on the display unit 24 of the terminal 20 in the present modification.

On the top page, in addition to the above-described "code icon", a "code (offline) icon" expressed as "code (offline)" is displayed.

In the present modification, "code icon" is an icon for displaying a code display screen in an online state, and "code (offline) icon" is an icon for displaying a code display screen in an offline state.

Fig. 4 to 21 are diagrams showing an example of a code display screen displayed on the display unit 24 of the terminal 20 in the present modification. The code display screen is displayed by touching a code (offline) icon on the above-described home page.

The code display screen displays "code (offline)" on the upper part of the screen, and displays the same information as the code display screen of fig. 4 to 10 on the lower part thereof.

In the example of the display screen, when the terminal 20 detects that it is in the off-line state, the stored terminal display code is displayed on the code display screen in accordance with the user operation. Then, off-line settlement can be performed by using the terminal display code.

< modification (8) > < 1 st modification

In a130 of the processes in fig. 3 to 4, the processes a240 and a250 may be performed and the terminal display code may be displayed on the display unit 24 at the timing when the terminal 20 receives the terminal display code from the server 10, or may not be performed.

In a330 of the processing in fig. 4 to 14, the processing in a340 and a350 may be performed and the terminal display code may be displayed on the display unit 24 at the timing when the terminal 20 receives the terminal display code and the code expiration date from the server 10, or may not be performed.

In this case, not limited to but as an example, when the code icon is touched in the top page (e.g., fig. 3-2) of the payment application, a code display screen on which the code for terminal display can be switched is displayed.

< modification (9) > < 1 st

In embodiment 1, the case where "the time based on the processing related to settlement" is the code reading time is described as an example, but the present invention is not limited to this.

First, instead of the code reading time, the code reading date and time including the date and time information may be "the time based on the processing related to the settlement", or may not be.

Note that the time at which the terminal display code stored in the terminal 20 is displayed on the terminal 20 (hereinafter, referred to as "code display time") or the date and time (hereinafter, referred to as "code display date and time") may be set as "the time based on the processing related to the settlement", or not.

However, since the server 10 communicates with the terminal 20 in the online state, it is possible to recognize that the code for terminal display is displayed on the terminal 20, and therefore the server 10 can specify the code display time or the code display date and time based on the time counting information of the clock section 19.

However, since the server 10 cannot communicate with the terminal 20 in an offline state, the server 10 cannot grasp whether or not a code for terminal display is displayed on the terminal 20, and cannot specify a code display time and a code display date and time.

Therefore, the following processing is performed, not by way of limitation, but by way of example.

Fig. 4 to 22 are flowcharts showing an example of the flow of processing executed by each apparatus in the present modification. The 2 nd settlement application process as an example of the settlement application process executed by the control unit 21 of the terminal 20, the 2 nd shop settlement process as an example of the shop settlement process executed by the control unit 51 of the shop reader device 50, and the 2 nd settlement management process as an example of the settlement management process executed by the control unit 11 of the server 10 are shown in order from the left side.

The flowcharts of fig. 4 to 22 are partially rewritten the flowcharts of fig. 3 to 4. In contrast to the flow diagrams of fig. 3-4, the processing steps in the offline state differ (e.g., a450, B460, C470) by way of example and not limitation.

After a240, in an offline state, not by way of limitation, but by way of example, when a code display operation is performed by the user of the terminal 20, the control unit 21 performs code generation processing for extended terminal display and the code display processing unit 2113 performs code display processing (a 450).

Here, the code for settlement processed (including processing, generation, display, and the like) on the terminal 20 side based on the terminal display code stored in a240 is referred to as "extended terminal display code", and a code image of the extended terminal display code is referred to as "extended terminal display code image".

The extended terminal display code is a code for settlement in the settlement type "terminal code display" as in the terminal display code, but is not limited to online settlement, and may be used for offline settlement.

Further, the extended terminal display code can be used not only for offline payment but also for online payment. That is, it is not necessary to determine (detect) whether or not the terminal 20 is in the offline state, and settlement can be performed by using the extended terminal display code regardless of the online state and the offline state.

In the expansion terminal display code generation process, the expansion terminal display code image is generated, not by way of limitation, but by way of example. Specifically, the extended terminal display code image is generated by encoding (symbolizing) and patterning (imaging) the settlement number obtained by decoding the terminal display code image stored in the terminal display code storage data 2831 or the settlement number stored in the terminal display code storage data 2831 and the time stamp information generated by the control unit 21.

Here, the time stamp information is information indicating the date and time, date, time, and the like of occurrence of a specific event (specific event), and information and data (here, extended terminal display code) associated with the time stamp information serve as an electronic time certificate for proving that the specific event has actually occurred at a certain time.

In this example, "the extended terminal display code image is displayed on the display unit 24 of the terminal 20" is taken as a specific item, and the control unit 21 of the terminal 20 generates time stamp information including a code display time at which the extended terminal display code image is displayed (display is started). The code display time and the time stamp information are an example of "time information" and are generated based on information clocked by the clock unit 29A of the terminal 20.

Some stores do not support reading of two-dimensional codes, but may support reading of one-dimensional codes. Here, in addition to the two-dimensional code (such as a QR code, as an example, without limitation), a code image for display of the expansion terminal represented by a one-dimensional code (such as a barcode, as an example, without limitation) may be generated, or not.

In addition, instead of the code display time, time stamp information including "code display date and time" including date information in addition to the time may be generated, or may not be.

In order to prevent a third party from decoding the original information, information obtained by encrypting the calculation number or the time stamp information may be encoded, or may not be encoded.

Further, instead of encoding the time stamp information, the code display time or the code display date and time itself may be encoded, or may not be encoded.

In the code display process, a code display screen including at least a code image for display in the expansion terminal is displayed on the display unit 24, by way of example and not limitation.

In addition, as described above, when the two-dimensional expansion terminal display code image is generated in the expansion terminal display code generation process, the two-dimensional expansion terminal display code image may be displayed, not by way of limitation, but by way of example.

In addition, when the code image for one-dimensional expansion terminal display is generated in the code generation process for expansion terminal display, the code image for one-dimensional expansion terminal display may be displayed in addition to the code image for two-dimensional expansion terminal display, by way of example and not limitation. In this case, the settlement number may be displayed simultaneously in the vicinity of the code image for display at the one-dimensional extension terminal, or may not be displayed.

Then, when the user of the terminal 20 presents the extended terminal display code image displayed on the display unit 24 to a clerk or the like in the store, the control unit 51 controls the control code reader 58 to read the extended terminal display code image displayed on the display unit 24 of the terminal 20 (B450).

The control unit 51 accesses the server 10 through the communication I/F54. Then, the control unit 51 transmits settlement request information including at least the settlement number and the time stamp information acquired by decoding, the store identification information, and the settlement amount to the server 10 through the communication I/F54 (B460).

When the communication I/F14 receives the settlement request information from the store code reader device 50 (C160), the control unit 11 performs the settlement processing (C470).

Specifically, it is determined whether or not the settlement number included in the received settlement request information is stored in the code management database 159 in association with the application ID. When it is determined that the code is stored in the code management database 159, it is determined whether or not the code display time specified by the time stamp information included in the received settlement request information is within the code expiration date stored in association with the settlement number in the code management data of the application ID. When this condition is satisfied, it is determined that settlement is possible, and settlement is performed by subtracting a predetermined amount of settlement from the balance in the settlement management data of the application ID stored in the settlement management database 157A.

Further, if it is determined whether or not the settlement is within the code display period, it is not limited to this, but by way of example, it is determined whether or not the settlement is within the code display period by comparing the code display time with the difference time between the time counted by the clock unit 19 of the server 10 and the code display time specified by the time stamp information included in the received settlement request information.

< embodiment 2 >

In embodiment 1, the server 10 is caused to perform settlement based on the code expiration date. However, the user of the terminal 20 is not necessarily able to process the procedure for causing the server 10 to perform settlement within the code validity period.

Further, in the case where the code expiration date has elapsed, the code for terminal display needs to be acquired again from the server 10, but this operation may be troublesome for some users.

The contents described in embodiment 2 can be applied to any of the other embodiments and the other modifications.

Note that the same components as those already present are denoted by the same reference numerals, and the description thereof will not be repeated.

Fig. 5-1 is a diagram showing an example of information stored in the storage unit 28 of the terminal 20 in the present embodiment.

In the present embodiment, the settlement application 282 includes, as an example and not by way of limitation, a terminal-side code update processing program 2821 as a subroutine, and the terminal-side code update processing program 2821 is executed as terminal-side code update processing.

< treatment >

Fig. 5-2 is a flowchart showing an example of the flow of processing executed by each apparatus of the present embodiment. The left side shows the terminal-side code update process executed by the control unit 21 of the terminal 20, and the right side shows the server-side code update process executed by the control unit 11 of the server 10. These processes are, by way of example and not limitation, processes executed (for example, in the background) as sub-processes of the above-described settlement application process of the terminal 20 and the above-described settlement management process of the server 10.

First, the control unit 21 performs a code update condition determination process (D110). Specifically, by way of example and not limitation, it is determined whether or not the time measured by the clock unit 29A of the terminal 20 (hereinafter referred to as "terminal measurement time") is a time before a set time from the time (date and time) at which the validity period of the code associated with the terminal display code stored in the terminal display code storage data 2831 has ended.

Not limited but as an example, the set time may be set based on the code valid time.

For example, when the code validity time is "12 hours", half of "6 hours" thereof may be set as the set time, and when the code validity time is "24 hours", half of "12 hours" thereof may be set as the set time. In order to update the terminal display code, a time having a certain margin is preferable.

Further, it is not limited to determining whether or not the time is before the set time from the time when the code validity period ends, but it may be determined whether or not the set time has elapsed from the code reception time (code date and time) or the code storage time (code storage date and time), or not.

That is, the time (reference time) that is a reference for determining the code update condition may be the time when the code expiration date ends, or may be the code reception time or the code storage time.

When the 1 st terminal display code storage data 2831A is applied, since 1 terminal display code is stored, the determination of D110 can be performed based on the code expiration date associated with the terminal display code, with the terminal display code being the target.

On the other hand, when the 2 nd terminal display code storing data 2831B is applied, since a plurality of terminal display codes are stored, the determination of D110 can be performed based on the code expiration dates associated with the respective terminal display codes with respect to the plurality of terminal display codes.

When the time is a time before the set time, the control unit 21 determines that the code update condition is established.

When it is determined that the code update condition is satisfied (yes in D120), the control unit 21 determines whether or not the online state is present (D130). Further, when it is determined that the terminal is in the online state (D130: yes), the control unit 21 transmits, by way of example and not limitation, code update request information including the application ID and the code serial number of the terminal display code requesting the update to the server 10 via the communication I/F22 (D160).

Here, the "code update request information" is information for requesting (may also be referred to as an application) an update (may also be referred to as a reacquisition) of the code for terminal display stored in the terminal 20, and may be a request for updating the code information.

The "code update request information" may be information requesting transmission of an updated terminal display code (new terminal display code).

The control unit 11 of the server 10 determines whether or not the code update request information is received from the terminal 20 (E110). If the reception is judged (E110: YES), a terminal display code updating process is executed (E120).

Specifically, by way of example and not limitation, the code management data of the application ID included in the received code update request information in the code management database 159 of the storage unit 15 is referred to. Then, whether or not the code management data includes the code serial number included in the received code update request information is determined, and if it is determined that the code serial number exists, the same processing as the terminal display code generation processing described above is executed to generate the terminal display code for update. Then, the code generation date and time, the settlement number, and the code expiration date stored in the code management data in association with the code serial number are updated. The terminal display code to be updated in this manner is hereinafter referred to as "updated terminal display code".

Then, the control unit 21 transmits the update terminal display code and the code expiration date thereof to the terminal 20 via the communication I/F14 (E170).

After that, the control unit 11 determines whether or not to end the process (E190), and if it is determined to continue the process (E190: NO), returns the process to E110. If it is determined that the process is to be ended (E190: yes), the server-side code update process is ended.

If the code update request information is not received from the terminal 20 (E110: no), the control unit 11 shifts the process to E190.

When the update terminal display code and the code expiration date thereof are received from the server 10 via the communication I/F22 (D170), the control unit 21 updates the code reception date and time, the code data, and the code expiration date stored in the terminal display code storage data 2831 in association with the corresponding code serial number (D180). By performing this update processing, the terminal display code to be updated (old terminal display code) becomes unusable (unusable).

In D180, the terminal display code to be updated (old terminal display code) may be disabled by performing processing such as storing the received update terminal display code and its code expiration date in the terminal display code storage data 2831 as separate data (new data) and setting an "unavailable" flag for the terminal display code to be updated, or the like.

After that, the control unit 21 determines whether or not to end the process (D190), and if it determines to continue the process (D190: no), returns the process to D110. When it is determined that the process is to be ended (D190: YES), the terminal-side code update process is ended.

When it is determined that the code update condition is not satisfied (no in D120) or it is determined that the device is not in the online state (no in D130), the control unit 11 shifts the process to D190.

In this process, when the terminal display code is updated, the terminal 20 may display information indicating that the terminal display code is updated (for example, a message indicating that the terminal display code is updated or an image indicating that the terminal display code is updated) on the display unit 24 by push notification, or may display the information on the settlement application screen of the display unit 24 when the settlement application is being executed.

< Effect of embodiment 2 >

The 2 nd embodiment shows the following constitution: the terminal 20 receives an update terminal display code (not limited, an example of the 2 nd code information) different from the terminal display code (not limited, an example of the 1 st code information) from the server 10 via the communication I/F22 based on a code expiration date (not limited, an example of the 1 st expiration date) associated with the terminal display code (not limited, an example of the 1 st code information) stored in advance in the terminal 20, and further, the update terminal display code is associated with a code expiration date (not limited, an example of the 2 nd expiration date) different from the code expiration date associated with the terminal display code by the server 10.

As an example of the effect obtained by such a configuration, since the 2 nd code information is received from the server based on the information on the 1 st term of validity, the 2 nd code information being code information associated with the 2 nd term of validity different from the 1 st term of validity by the server, the 2 nd code information can be acquired from the server before the 1 st term of validity passes, for example, and the convenience of the user can be improved.

In addition, embodiment 2 shows the following configuration: the terminal 20 receives the code for terminal display and its code expiration date (not limited to, but one example of information on the 1 st expiration date) from the server 10 via the communication I/F22, and further stores the received code expiration date in the code storage data 2831 for terminal display in association with the code for terminal display via the control unit 21.

In addition, embodiment 2 shows the following configuration: the terminal 20 transmits code update request information (not limited to, but an example of information requesting transmission of the 2 nd code information) to the server 10 via the communication I/F22 based on the code expiration date associated with the terminal display code stored in advance in the terminal 20.

As an example of the effect obtained by such a configuration, the server can be requested to transmit the 2 nd code information at an appropriate timing based on the information on the 1 st validity period.

The 2 nd embodiment shows the following constitution: before a code expiration date (not limited, but an example of the 1 st expiration date) associated with a terminal display code (not limited, an example of the 1 st code information) stored in advance in the terminal 20 passes, an updated terminal display code (not limited, but an example of the 2 nd code information) is received from the server 10 via the communication I/F22.

As an example of the effect obtained by such a configuration, the 2 nd code information can be received from the server before the 1 st term of validity has passed.

The 2 nd embodiment shows the following constitution: the terminal 20, upon receiving the update terminal display code, performs processing (not limited to, an example of processing for making the 1 st code information unusable) for updating the update target terminal display code and the code expiration date thereof, respectively, by the control unit 21, or performs processing (not limited to, an example of processing for making the 1 st code information unusable) for setting an "unusable" flag for the update target terminal display code.

As an example of the effect obtained by such a configuration, since the 1 st code information is made unusable by the reception of the update terminal display code, it is possible to prevent the old 1 st code information stored in advance in the storage section from being used for settlement.

< modification (1) > < 2 nd

In embodiment 2, whether or not the code update condition is established is determined based on the code expiration date of the terminal display code stored in advance in the terminal 20, but is not limited thereto. The setting of the code update condition can be changed as appropriate.

Fig. 5-3 are diagrams showing an example of information stored in the storage unit 28 of the terminal 20 in the present modification.

In the present modification, the settlement application data 283 includes, by way of example and not limitation, user schedule data 2834 and code update condition data 2835.

The user schedule data 2834 is data storing information of a schedule of a user of the terminal 20 (hereinafter, referred to as "user schedule information"). The user schedule information is set and updated according to the user's operation of the terminal 20.

The code update condition data 2835 is data in which a code update condition is set, and an example of the data structure thereof is shown in fig. 5 to 4.

In the code update condition data 2835, not limited but by way of example, a condition category, a condition serial number, and a code update condition are associated and set.

< Condition type "CK 1" >)

The condition category "CK 1" is a category of "time", and includes, by way of example and not limitation, code update conditions of condition serial numbers "CK 1-1" to "CK 1-3".

As the code update condition of the condition serial number "CK 1-1", the "terminal count time becomes the time before the 1 st set time from the time when the code validity period ends" is set.

This condition is the same as the code update condition determined in embodiment 2.

However, the 1 st setting time does not necessarily need to be half of the code effective time, and the setting can be changed as appropriate.

As the code update condition of the condition serial number "CK 1-2", the "terminal timer time becomes the set time (set time zone)" is set.

This condition indicates that the code update condition is determined to be satisfied when the terminal clock time becomes the set time or the terminal clock time becomes a time included in the set time zone.

The set time or the set time period may be changed as appropriate. For example, a time such as "midnight 0 o 'clock" or "early 6 o' clock" may be set as the set time, and a midnight time period or the like may be set as the set time period.

As the code update condition of the condition serial number "CK 1-3", the "2 nd set time elapsed since the code was updated last" is set.

This condition indicates that the code update condition is determined to be satisfied when the 2 nd set time has elapsed since the terminal display code stored in the terminal 20 was last updated.

The setting of the 2 nd setting time can be changed appropriately, but it is necessary to pay attention to setting a time shorter than the code effective time.

< Condition type "CK 2" >)

The condition category "CK 2" is a category of "users", and includes, by way of example and not limitation, code update conditions of condition serial numbers "CK 2-1" to "CK 2-2".

As the code update condition of the condition serial number "CK 2-1", the "existence of a code update request operation from a user" is set. This condition is that the code update condition is determined to be satisfied when an operation (hereinafter referred to as "code update request operation") for requesting update of the code for terminal display is performed by the user of the terminal 20.

The condition may also be referred to as a condition of a category of "user behavior".

As the code update condition of the condition serial number "CK 2-2", the "update recommendation timing based on the user schedule information (or settlement information)" is set. This condition indicates that the code update condition is determined to be satisfied when the update recommendation timing based on the user schedule information stored in the user schedule data 2834 comes.

For example, in the case where the user of the terminal 20 makes a purchase and settles the settlement in a shop located in a place where the communication condition is unstable at regular timing (for example, the day of the week or the day of the month), or in the case where the user of the terminal 20 regularly goes to a bar located underground for drinking and settles the settlement, the user of the terminal 20 is considered to be likely to use the same shop and settle the settlement at the next timing.

Therefore, the terminal 20 estimates the timing (time or date and time) at which the next settlement is possible based on the history of the schedule information of the user (for example, the history of the schedule information of the user included in the user schedule data 2834), and sets the timing before the timing (for example, the timing before the departure, the timing at the departure, or the timing before the arrival at the destination) as the update recommended timing so that the terminal display code can be updated at the timing.

Further, instead of estimating the timing at which the next settlement is possible based on the history of the schedule information of the user, or in addition to this, the timing at which the next settlement is possible may be estimated based on the settlement information of the user (for example, the settlement history data included in the settlement data 2832).

The condition may be referred to as a condition of the category of "schedule", "settlement", or "history".

< Condition type "CK 3" >)

The condition category "CK 3" is a category of "location", and includes, by way of example and not limitation, code update conditions of condition serial numbers "CK 3-1" to "CK 3-2". These conditions may also be referred to as conditions of the category "terminal location", "user location" or "location".

As the code update condition of the condition type "CK 3-1", it is determined that "the calculation terminal position is a position in the vicinity of the set shop". This condition indicates that the code update condition is determined to be satisfied when the position of the terminal 20 calculated based on the position calculation information detected by the position calculation information detection unit 29B (hereinafter referred to as "calculated terminal position") is a position in the vicinity of the set store.

Further, although the calculated terminal position is the calculated position of the terminal 20, the calculated position of the terminal 20 is the same as the position of the user of the terminal 20 if the user carries the terminal 20. That is, if it is assumed that the user carries the terminal 20, the position of the terminal 20 can be said to be substantially the same as the position of the user of the terminal 20.

The setting store is not limited to this, and may be set in advance by the terminal 20 side or the server 10 side. For example, a shop located in a place with poor communication environment such as the underground may be set as the setting shop on the terminal 20 side or may be set on the server 10 side according to an operation by the user of the terminal 20. In this case, the terminal display code can be updated at the timing when the terminal position approaches the set store.

As the code update condition of the condition serial number "CK 3-2", it is set that "the calculation terminal position is a position within the setting range". This means that the code update condition is determined to be satisfied when the calculation terminal position is a position within the set range.

For example, an event may be held, and a store supporting settlement by a settlement application may open a store at the event. It is likely that many people will go to an event venue for such an event and use the terminal 20 in the venue, and thus there is a possibility that the communication state deteriorates.

In addition, in the case where an event is held underground or the like, communication may not be possible.

Here, the terminal 20 side or the server 10 side is not limited to this, but by way of example, a predetermined range (for example, within 1km in radius) centered around an event venue for holding an event is set as the set range. In this case, the terminal display code can be updated at the timing when the terminal position enters the predetermined range (the timing when the user of the terminal 20 approaches the event venue).

< Condition type "CK 4" >)

The condition category "CK 4" is a category of "urgent", and includes, by way of example and not limitation, a code update condition of the condition serial number "CK 4-1". This condition may also be referred to as a condition of the category of "world situation".

As the code update condition of the condition serial number "CK 4-1", reception disaster information/disaster prevention information "is set. The condition indicates that the code update condition is determined to be satisfied when the terminal 20 receives disaster information and disaster prevention information such as earthquake disaster information, weather disaster information, flood information, and mud-flow disaster information.

If a disaster occurs, it may cause the terminal 20 to enter an offline state, assuming that the communication infrastructure or the like is inoperable. Here, when the terminal 20 receives the disaster information and disaster prevention information, the terminal display code is updated in advance.

In the present embodiment, the control unit 21 of the terminal 20 determines whether or not the code update condition is satisfied based on the code update condition data 2835 in D110 of the terminal-side code update process of fig. 5-2. By way of example and not limitation, when at least one code update condition is satisfied, it is determined that the code update condition is satisfied.

In the code update condition data 2835, priorities are set in advance in association with the respective code update conditions. Further, when at least one of the code update conditions in which a higher priority than a predetermined priority (a priority that becomes a threshold) is set in association with each other is satisfied, it may be determined that the code update condition is satisfied, or may not be satisfied.

Further, it may be preset on the terminal 20 side or the server 10 side which code update condition is to be applied among the code update conditions specified in the code update condition data 2835. In this case, when at least one of the set code update conditions is satisfied, the code update condition may be determined to be satisfied, or may not be satisfied.

< Effect of modification (1) of No. 2 >

This modification shows the following configuration: the terminal 20 receives, via the communication I/F22, the update terminal display code (not limited, but an example of the 3 rd code information) transmitted from the server 10 based on the set time and associated with the new code expiration date (not limited, but an example of the 3 rd expiration date) by the server 10.

As an example of the effect obtained by such a configuration, the terminal can receive, via the communication unit, the 3 rd code information transmitted from the server based on the set time, and the 3 rd code information is associated with the 3 rd validity period by the server.

In addition, the present modification shows the following configuration: the terminal 20 receives, via the communication I/F22, an update terminal display code (not limited, but an example of the 4 th code information) transmitted from the server 10 based on information (for example, user schedule information, settlement history of the user, location of the terminal 20 (user of the terminal 20), etc.) of the user of the terminal 20, and associated with a new code expiration date (not limited, but an example of the 4 th expiration date) via the server 10.

As an example of the effect obtained by such a configuration, the 4 th code information transmitted from the server based on the information of the user of the terminal can be received by the communication unit, and the 4 th code information is associated with the 4 th expiration date by the server.

In addition, the present modification shows the following configuration: the terminal 20 receives, via the communication I/F22, the update terminal display code (not limited, an example of the 5 th code information) transmitted from the server 10 based on the disaster information and associated with the new code expiration date (not limited, an example of the 5 th expiration date) by the server 10.

As an example of the effect obtained by such a configuration, the terminal can receive, through the communication section, the 5 th code information transmitted from the server based on the disaster-related information acquired through the server, the 5 th code information being associated with the 5 th expiration date through the server.

< modification (2) > < 2 nd

In embodiment 2, the terminal 20 requests the server 10 to update the terminal display code, but the present invention is not limited thereto. The terminal 20 may request the server 10 to extend the code expiration date associated with the stored terminal display code without requesting updating of the terminal display code.

Fig. 5 to 5 are flowcharts showing an example of the flow of processing executed by each apparatus in the present modification. The left side shows the terminal-side code expiration date extension processing executed by the control unit 21 of the terminal 20, and the right side shows the server-side code expiration date extension processing executed by the control unit 11 of the server 10. These processes are, by way of example and not limitation, processes executed in the background in the settlement application process of the terminal 20 and the settlement management process of the server 10.

First, the control unit 21 performs a code expiration date extension condition determination process (D210). The code expiration date extension condition is not limited to the example, and may be the same condition as the code update condition shown in fig. 5 to 4.

In addition, when the 1 st terminal display code storage data 2831A is applied, since 1 terminal display code is stored, the determination of D210 can be performed based on the code expiration date associated with the terminal display code, with the terminal display code being the target.

On the other hand, when the 2 nd terminal display code storing data 2831B is applied, since a plurality of terminal display codes are stored, the determination of D210 can be performed based on the code expiration dates associated with the respective terminal display codes for the plurality of terminal display codes.

When it is determined that the code validity period extension condition is satisfied (yes in D220), the control unit 21 determines whether or not the online state is present (D230). Further, when it is determined that the mobile terminal is in the online state (D230: YES), the control unit 21 performs an authentication process (D240).

Specifically, by way of example and not limitation, the authentication screen is displayed on the display unit 24, and the user is allowed to input an authentication password. Then, it is determined whether or not the input authentication password coincides with the authentication password registered in advance and stored in the settlement application data 283. Further, the authentication result is "OK" in the case of coincidence, and is "NG" in the case of non-coincidence.

If the authentication result is "OK" (D250: yes), the control unit 21 transmits, not by way of limitation but by way of example, code validity period extension request information including the application ID and the code serial number of the terminal display code requesting extension of the code validity period to the server 10 via the communication I/F22 (D260).

Here, the "code expiration date extension request information" is information requesting (applying) extension of the code expiration date associated with the terminal display code stored in the terminal 20, and may be a request for extension of the code expiration date.

The "code validity period extension request information" may be information requesting transmission of the extended code validity period.

The control unit 11 of the server 10 determines whether or not the code validity period extension request information is received from the terminal 20 (E210). If it is determined that the code is received (yes in E210), a code valid period extension process is performed (E220).

Specifically, by way of example and not limitation, the code management data of the application ID included in the received code validity period extension request information in the code management database 159 of the storage unit 15 is referred to. Then, it is determined whether or not the code management data stores the code serial number included in the received code validity period extension request information, and if it is determined that the code serial number is stored, the code validity period stored in association with the code serial number is extended and updated. The code validity period extended in this manner is hereinafter referred to as "extended code validity period".

Next, the control unit 21 transmits the extended code expiration date to the terminal 20 via the communication I/F14 (E270).

After that, the control unit 11 determines whether or not to end the process (E290), and if it is determined to continue the process (E290: NO), returns the process to E210. If it is determined to end the process (E290: yes), the server-side code expiration date extension process is ended.

If the code expiration date extension request information is not received from the terminal 20 (E210: no), the control unit 11 shifts the process to E290.

When the extended code expiration date is received from the server 10 via the communication I/F22 (D270), the control unit 21 updates the code expiration date stored in the terminal display code storage data 2831 in association with the corresponding code sequence number, with the received extended code expiration date (D280).

After that, the control unit 21 determines whether or not to end the process (D290), and if it is determined to continue the process (D290: NO), returns the process to D210. When it is determined that the process is to be ended (D290: YES), the terminal-side code expiration date extension process is ended.

If it is determined that the code validity period extension condition is not satisfied (D220: no), if it is determined that the terminal is not in the on-line state (D230: no), or if the authentication result is determined to be "NG" (D250: no), the control unit 11 shifts the process to D290.

In this process, when the extension code valid period is received from the server 10, the terminal 20 may display information indicating that the code valid period is extended (for example, a message indicating that the code valid period is extended or an image indicating that the code valid period is extended) on the display unit 24 by push notification, or may display the information on the settlement application screen of the display unit 24 when the settlement application is being executed.

In this process, the authentication process is not necessarily required, and may be omitted.

< Effect of modification (2) of No. 2 >

This modification shows the following configuration: the terminal 20 transmits the code validity period extension request information (not limited to, but an example of information requesting the server to extend the 1 st validity period) to the server 10 via the communication I/F22.

As an example of the effect obtained by such a configuration, the server can be requested to extend the 1 st validity period.

In addition, the present modification shows the following configuration: the terminal 20 performs a process of acquiring an extended code validity period from the server 10 (not limited, but an example of a process related to extension of the 1 st validity period) by the control unit 21 based on execution of an authentication process (not limited, an example of a process related to authentication of a user of the terminal).

As an example of the effect obtained by such a configuration, the control unit of the terminal performs the processing related to the extension of the 1 st validity period based on the execution of the processing related to the authentication of the user of the terminal, and thereby the security can be improved when the 1 st validity period is extended.

In the present modification, the terminal 20 receives the extended code expiration date transmitted from the server 10 via the communication I/F22. Further, information indicating that the valid period of the code is extended is displayed in the display area of the terminal 20.

As an example of the effect obtained by such a configuration, it is possible to notify the user of the terminal that the 1 st validity period is extended, and it is possible to improve the convenience of the user.

< modification (3) > < 2 nd

In embodiment 2, the server 10 may update the terminal display code and transmit it to the terminal 20 without a request from the terminal 20, or the server 10 may not update the terminal display code and transmit it to the terminal 20 without a request from the terminal 20.

In this specification, transmission of information or data by the server 10 to the terminal 20 without a request from the terminal 20 (i.e., transmission of information or data by the server 10 autonomously) is referred to as "push transmission".

In this case, the server 10 performs the terminal display code update process at a regular timing or a specific timing, by way of example and not limitation.

Alternatively, the server 10 determines whether or not the code update condition is satisfied at any time based on the same condition as the above-described code update condition, and performs the terminal display code update process when it is determined that the code update condition is satisfied.

Then, the server 10 pushes and transmits the update terminal display code and the code expiration date thereof to the terminal 20.

In modification 2 (2), the server 10 may not extend the code expiration date in response to the request from the terminal 20, but may extend the code expiration date and transmit it to the terminal 20 without a request from the terminal 20.

In this case, the server 10 performs the code expiration date extension processing at a regular timing or a specific timing, by way of example and not limitation.

Alternatively, the server 10 determines whether or not the code validity period extension condition is satisfied at any time based on the same condition as the above-described code validity period extension condition, and performs the code validity period extension process when determining that the code validity period extension condition is satisfied.

Then, the server 10 pushes and transmits the extended code expiration date to the terminal 20.

< modification (4) > < 2 nd

In embodiment 2, the process of updating the terminal display code is described, but the present invention is not limited to this. The process of generating a new terminal display code may or may not be a process of updating the terminal display code.

Specifically, by way of example and not limitation, new code generation request information requesting generation of a new terminal display code is transmitted from the terminal 20 to the server 10. The server 10 generates a new terminal display code by executing the same processing as the terminal display code generation processing described above based on the reception of the new code generation request information from the terminal 20, and stores the new terminal display code in the code management data together with information such as the code generation date and time, the settlement number, and the code expiration date. Then, the server 10 may transmit the generated new terminal display code and information on the expiration date of the code to the terminal 20.

< embodiment 3 >

The 3 rd embodiment is an embodiment related to a setting method of a code valid period (how to set a code valid period).

The contents described in embodiment 3 can be applied to any of the other embodiments and other modifications.

Fig. 6-1 is a diagram showing an example of information stored in the storage unit 15 of the server 10 in the present embodiment.

In the present embodiment, the storage unit 15 stores, by way of example and not limitation, an account-by-account management database 152, held event data 154, and code expiration date setting data 156.

The per-account management database 152 is management data for each account of the settlement application, and an example of a data structure thereof is shown in fig. 6-2.

The account management data for each account is stored in the account management database 152.

Each account-by-account management data is not limited to the above, but stores, by way of example, an application ID, a credit score, terminal position history data, user schedule data, settlement history data, and offline tendency data.

The credit score represents the social credit of the user of the terminal 20 by a numerical value, a rating, or the like.

The credit score, not limited but by way of example, is calculated based on actual payment records, age, mode of operation, annual income, etc. of the user of the terminal 20 and is updated over time.

By way of example and not limitation, the credit score may be quantified in a score from "0" to "100," with a credit score of "100" indicating the highest social credit for the user and a credit score of "0" indicating the lowest social credit for the user.

The terminal position history data stores a history of the position of the terminal (hereinafter referred to as "terminal position"). By way of example and not limitation, a terminal position (hereinafter referred to as "calculated terminal position") calculated by the terminal 20 by performing the position calculation process may be transmitted from the terminal 20 to the server 10 at a timing when the terminal position is calculated or at a regular timing, and the calculated terminal position may be stored as the terminal position in the terminal position history data at any time.

In contrast, when the code generation request information, the code update request information, or the code expiration date extension information described above is transmitted from the terminal 20 to the server 10, the latest terminal position may be transmitted from the terminal 20 to the server 10, or may not be transmitted.

The user schedule data is data of user schedule information of the terminal 20 storing the application ID. The user schedule data can be updated at any time in synchronization with the user schedule data 2834 (see fig. 5-3) stored in the storage section 28 of the terminal 20.

The settlement history data is the settlement history data included in the settlement management data of the application ID among the settlement management data stored in the settlement management database 157.

The offline tendency data is data obtained by analyzing a tendency of the terminal 20 of the application ID to enter an offline state. By way of example and not limitation, the server 10 may store a period during which communication with the terminal 20 was not possible in the past as a history in the offline trend data.

The held event data 154 is data related to an event that can be settled by using the terminal display code, and stores information such as the date and time of holding the event, the place of holding the event, and a store that opens a store at the event, by way of example and not limitation. Such information is acquired by the server 10 from the event host or the like in advance, and is stored in the event host data 154.

The code expiration date setting data 156 is used to set a code expiration date. The code expiration date setting data 156 is not limited to the above-described data, and examples thereof include a credit score, a position (terminal position, user position), a user schedule, a settlement history, and an offline tendency specified by the data included in the account-based management data, as determination items, and a method for setting a code expiration time is determined based on the determination items.

By way of example and not limitation, the set code expiration time is substantially synonymous with the set code expiration date, since the code expiration time is determined based on the code generation date and time and the code expiration time.

(1) Credit scoring

It can be said that the higher the credit score, the higher the social credit of the user.

Thus, by way of example and not limitation, the higher the credit score, the longer time may be set as the code validity time. For example, a plurality of threshold conditions based on a threshold value (ranking threshold value) for the credit score may be set in advance, and different code effective times may be set depending on which threshold condition the credit score satisfies.

For example, it may be previously specified that the code effective time is "reference code effective time × 1.2" if the credit score is "80 points or more", is "reference code effective time × 1.0" if the credit score is "60 points or more and less than 80 points", is "reference code effective time × 0.8" if the credit score is "less than 60 points", and the like.

The "reference code validity time" is a validity time set as a default by the server 10, not by way of limitation, but as an example.

Without limitation but as an example, the code valid time such as "6 hours", "12 hours", "18 hours", and "24 hours" described in embodiment 1 may be set in advance as the reference code valid time.

(2) Terminal position (user position)

By way of example and not limitation, a condition for setting the code expiration time based on the terminal position is set in the code expiration time setting data 156.

For example, a high-security location (accurate positioning, a certain area, or the like) and a low-security location are set in advance on the server 10 side.

The term "security" as used herein means that it is not easy to cause a risk by lengthening the code validity time.

As a place having high security, not limited but as an example, a place where the terminal 20 is unlikely to be stolen by others (a place where the user is unlikely to leave the terminal 20, or the like), for example, a position of a home of the user of the terminal 20 or an area in the vicinity thereof, or the like may be considered.

As an example of a low-security place, not limited to this, a place with a low possibility that the terminal 20 is stolen by another person (a place with a low possibility that the user leaves the terminal 20) may be considered, for example, a place of a restaurant store such as a wine house or an area near the place.

In this case, not limited but as an example, a longer time may be set as the code valid time in a case where the terminal position is included in the place of high security than in a case where the terminal position is included in the place of low security.

For example, it is possible to set in advance: when the terminal position is included in a high-security place, the code effective time is "reference code effective time × 1.2", and when the terminal position is included in a low-security place, the code effective time is "reference code effective time × 0.8".

(3) User schedules

The code expiration date setting data 156 is not limited to this, and is provided with a condition for setting the code expiration date based on the user schedule, by way of example.

For example, when the user plans to participate in a specific event within a predetermined time or within a predetermined number of days, there is a high possibility that settlement is performed using the terminal display code.

Thus, by way of example and not limitation, if the user of the terminal 20 plans to attend a particular event within a predetermined time or within a predetermined number of days, a time longer than the reference code validity time may be set as the code validity time.

(4) History of settlement

The code expiration date setting data 156 is not limited to the above and, as an example, sets a condition for setting the code expiration time based on the settlement history of the user of the terminal 20.

If it is known from the settlement history that the user of the terminal 20 tends to perform settlement at regular timing (for example, the day of the week or the day of the month), the user of the terminal 20 is likely to perform settlement at the next timing using the same shop.

Therefore, not by way of limitation, but as an example, when the user of the terminal 20 tends to perform settlement with the same store at regular timing, a time longer than the reference code valid time may be set as the code valid time.

The code validity time may be set based on the frequency or number of times the user of the terminal 20 makes settlement.

Specifically, the frequency (hereinafter referred to as "settlement frequency") or the number of times of settlement performed in a unit period (hereinafter referred to as "settlement number") is calculated based on the settlement history data associated with the application ID. Further, the higher the frequency of settlement or the larger the number of times of settlement, the longer time can be set as the code effective time.

(5) Off-line trending

The code expiration date setting data 156 is not limited to this, and a condition for setting the code expiration time based on the offline tendency is set, by way of example.

If the terminal 20 frequently enters the offline state, settlement may not be performed in an emergency unless the code validity time is set longer.

Here, the frequency (hereinafter, referred to as "off-line frequency") or the number of times (hereinafter, referred to as "off-line number") that the terminal 20 enters the off-line state in a unit period is calculated, not by way of limitation, but by way of example. Further, the higher the offline frequency or the more the number of times of offline, the longer time can be preset as the code effective time.

The above determination items are merely examples, and the setting can be appropriately changed.

For example, on the terminal 20 side, the user is allowed to select one code validity time from a plurality of candidates of code validity times. Then, the selected code validity time is transmitted from the terminal 20 to the server 10, and the code validity time received from the terminal 20 may be set on the server 10 side in association with the application ID of the terminal 20.

In the present embodiment, the control unit 11 of the server 10 performs, by way of example and not limitation, a code expiration date setting process before performing a code generation process for terminal display (C320 in fig. 4 to 14), a code update process for terminal display (E120 in fig. 5 to 2), or a code expiration date extension process (E220 in fig. 5 to 5).

In the code expiration date setting process, the control unit 11 may refer to the code expiration date setting data 156, may refer to at least one of the plurality of determination items, and may set the code expiration date based on the determination item, or may set the code expiration date by a combination of the determination items. For example, a user with a high credit score, a high offline frequency, or a large number of offline times may or may not have a longer expiration date than a user with the same credit score.

< Effect of embodiment 3 >

Example 3 shows the following configuration: the code expiration date is set by the server 10 based on information of the user of the terminal 20.

As an example of the effect obtained by such a configuration, the terminal can cause the server to perform settlement based on the 1 st term of validity appropriately set according to the information of the user of the terminal.

In addition, embodiment 3 shows the following configuration: the information of the user of the terminal 20 includes the credit score of the user.

As an example of the effect obtained by such a configuration, the terminal can cause the server to perform settlement based on the 1 st term of validity, which is appropriately set based on the credit score of the user of the terminal.

In addition, embodiment 3 shows the following configuration: the information of the user of the terminal 20 includes information of the location of the user or information of the location of the terminal.

As an example of the effect obtained by such a configuration, the terminal may cause the server to perform settlement based on a1 st validity period which is appropriately set based on information of the location of the user of the terminal or information of the location of the terminal.

In addition, embodiment 3 shows the following configuration: the information of the user of the terminal 20 includes user schedule information.

As an example of the effect obtained by such a configuration, the terminal can cause the server to perform settlement based on the 1 st term of validity, which is appropriately set based on the information of the schedule of the user of the terminal.

In addition, embodiment 3 shows the following configuration: the information of the user of the terminal 20 includes a settlement history based on the terminal display code or a settlement frequency (or a settlement count) of the user (not limited to, an example of the information of the settlement based on the code information of the user).

As an example of the effect obtained by such a configuration, the terminal may cause the server to perform settlement based on a1 st term of validity, the 1 st term of validity being set appropriately according to information of settlement based on the code information by the user of the terminal.

In addition, embodiment 3 shows the following configuration: the code expiration date is set based on the event information (not limited to, but an example of the information on the event) acquired by the server 10.

As an example of the effect obtained by such a configuration, the terminal may cause the server to perform settlement based on the 1 st validity period which is appropriately set based on the information on the event acquired by the server.

< example 4 >

The 4 th embodiment is an embodiment related to a countermeasure in the case where the code valid period has passed earlier than the code display period. In this case, since the code valid period passes before the code display period, the terminal display code displayed on the code display screen may not be usable.

The contents described in embodiment 4 can be applied to any of the other embodiments and other modifications.

Fig. 7-1 is a diagram showing an example of the flow of the 1 st code display processing in the present embodiment, and the 1 st code display processing is an example of the code display processing executed by the code display processing unit 2113 of the terminal 20 in the present embodiment.

First, the code display processing unit 2113 specifies a terminal display code to be displayed from the terminal display codes stored in the terminal display code storage data 2831 (F110).

In the case where 1 code acquired from the server 10 in the online state is stored in the terminal 20, the terminal display-use code stored in the 1 st terminal display-use code storage data 2831A (see fig. 4 to 9) is determined as the terminal display-use code as the display object.

On the other hand, in the case where a plurality of (2 or more) codes acquired from the server 10 in the on-line state are stored in the terminal 20, of the terminal display codes stored in the 2 nd terminal display code storage data 2831 (see fig. 4 to 15), the oldest terminal display code (the terminal display code closest to the valid period of the code) is determined as the terminal display code to be displayed, by way of example and not limitation.

Then, the code display processing unit 2113 determines whether or not the remaining time of the code expiration period is shorter than the code display time described above, based on the code expiration period stored in association with the terminal display code identified in F110 and the time counted by the clock unit 29A (F120).

If it is determined that the remaining time of the code expiration date is shorter than the code display time (F120: yes), the code display processing unit 2113 deletes the terminal display code specified in F110 from the terminal display code storage data 2831 (F130). Then, the code display processing unit 2113 displays an error screen including a message or the like indicating that the terminal display code cannot be displayed on the display unit 24, by way of example and not limitation (F140), and then ends the 1 st code display processing.

On the other hand, when it is determined that the remaining time of the code expiration date is not shorter than the code display time (F120: no), the code display processing unit 2113 displays, on the display unit 24, the 1 st code display screen including the code image of the terminal display code specified in F110 (F150). In this case, as described above, the information on the valid period of the code or the information on the display period of the code may be displayed on the 1 st code display screen, or may not be displayed. Then, the code display processing portion 2113 ends the 1 st code display processing.

In this process, when the remaining time of the code expiration date is shorter than the code display time, the terminal display code is deleted and is not displayed on the display unit 24.

In this process, when the remaining time of the code expiration date is shorter than the code display time, the terminal display code is deleted and is not displayed on the display unit 24, but the present invention is not limited to this.

Specifically, as a storage area for temporarily storing information, a buffer for securing a time for the amount of code display time is provided in the storage unit 28 of the terminal 20, not by way of limitation, but by way of example. For example, when the code display time is set to "5 minutes", a buffer for securing a time of "5 minutes" is provided.

In this case, since the time for the code display time period is secured in the buffer, the control unit 21 of the terminal 20 treats "the remaining time of the actual code display period + the code display time" as the remaining time of the code display period. Therefore, although the remaining time of the actual code validity period is shorter than the code display time, the control section 21 determines that the remaining time of the code validity period is equal to or longer than the code display time, thereby displaying a code display screen including the code for terminal display of the display object on the display section 24.

Fig. 7-2 is a diagram showing an example of the flow of the 2 nd code display processing in the present embodiment, and this 2 nd code display processing is another example of the code display processing executed by the code display processing portion 2113 of the terminal 20 in the present embodiment.

The same steps as those in the above-described processing are denoted by the same reference numerals, and the description thereof will be omitted.

This processing is processing in which steps F130 and F140 of the processing in fig. 7-1 are changed to steps F230 and F240, respectively.

After F110, if it is determined that the remaining time of the code expiration date is shorter than the code display time (F120: yes), the code display processing unit 2113 performs code display time limit change processing (F230). Specifically, the time equal to the remaining time of the valid code period is set as the code display time, not by way of limitation, but by way of example. That is, the code display period is shortened so that the code valid period and the code display period become the same.

Thereafter, the code display processing unit 2113 displays, on the display unit 24, the 2 nd code display screen including the code image of the terminal display code specified in F110 (F240). In this case, as described above, the information on the valid period of the code or the information on the changed code display period may be displayed on the 2 nd code display screen, or may not be displayed. Then, the code display processing portion 2113 ends the 2 nd code display processing.

In this process, when the remaining time of the code valid period is shorter than the code display time, the code display period is shortened so that the code valid period and the code display period become the same, and then the code display screen is displayed on the display section 24.

Fig. 7-3 are diagrams showing an example of the flow of the 3 rd code display processing in the present embodiment, and this 3 rd code display processing is another example of the code display processing executed by the code display processing portion 2113 of the terminal 20 in the present embodiment.

This processing is processing in which steps F110, F130, and F140 of the processing in fig. 7-1 are changed to steps F310, F330, and F340, respectively.

In this process, a plurality of (2 or more) codes acquired from the server 10 in an online state are stored in the terminal 20, that is, data of a plurality of terminal display codes are stored in the 2 nd terminal display code storage data 2831B.

First, the code display processing unit 2113 identifies the oldest terminal display code (the terminal display code closest to the expiration date of the code) as the terminal display code to be displayed, as an example, without limitation, among the terminal display codes stored in the 2 nd terminal display code storage data 2831B (F310).

Thereafter, when it is determined that the remaining time of the code expiration date is shorter than the code display time (F120: YES), the code display processing unit 2113 performs terminal display code change processing (F330). Specifically, by way of example and not limitation, the oldest terminal display code (terminal display code closest to the code expiration date) having a remaining time of the code expiration date equal to or longer than the code display time among the terminal display codes stored in the 2 nd terminal display code storage data 2831B is changed to the terminal display code to be displayed.

Thereafter, the code display processing unit 2113 displays a3 rd code display screen including the code image of the terminal display code changed in F330 on the display unit 24 (F340). In this case, as described above, the information on the valid period of the code or the information on the display period of the code may be displayed on the 3 rd code display screen or may not be displayed. Then, the code display processing portion 2113 ends the 3 rd code display processing.

In this process, when the remaining time of the code expiration date is shorter than the code display time, the code for terminal display having the remaining time of the code expiration date equal to or longer than the code display time is changed to a display target, and then the code display screen is displayed on the display unit 24.

In this process, the terminal display code to be displayed is changed before the code display screen is displayed, but the present invention is not limited to this.

Specifically, the code display processing unit 2113 determines whether or not the remaining time of the code expiration date is shorter than the code display time after displaying the code display screen including the terminal display code to be displayed. Further, when the condition is satisfied, the terminal display code changing process may be executed to change the terminal display code being displayed to a terminal display code whose remaining time of the code expiration date is equal to or longer than the code display time, and to reflect the terminal display code on the code display screen being displayed. That is, the terminal display code may be changed during the display of the display code display screen, or may not be changed.

In addition to the various processes described above, for example, not by way of limitation, the valid period of the code set in association with the terminal display code to be displayed may be extended when the remaining time of the valid period of the code is determined to be shorter than the code display time.

Specifically, by way of example and not limitation, when determining that the remaining time of the code validity period is shorter than the code display time, the control unit 21 extends the code validity period so that the time (date and time) at which the code validity period ends is the same as the time (date and time) at which the code display period ends.

Since the terminal 20 can communicate with the server 10 if it is in the on-line state, the server 10 can extend the code expiration date associated with the terminal display code to be displayed by communicating with the server 10 through the same processing as the above-described terminal-side code expiration date extension processing (see fig. 5 to 5).

However, in the offline state, the terminal 20 cannot communicate with the server 10. Therefore, in the offline state, the above-described processing is finally the processing for extending the code expiration date on the terminal 20 side.

In addition, not limited to the above, but as an example, as shown in fig. 4 to 17, 4 to 18, and 4 to 19, for example, information of the validity period of the code may be displayed on a code display screen displayed on the display section 24 of the terminal 20 in addition to the code image for terminal display and the number for settlement.

However, for example, as shown in fig. 4 to 16, the information of the code display period may be displayed on the code display screen, but the information of the code valid period may not be displayed.

In this case, as described above, not limited but as an example, the code display period may be shortened so that the code valid period and the code display period become the same, and then the information of the code display period may be displayed on the code display screen without displaying the information of the code valid period.

That is, by integrating the code expiration date and the code display period, the information of the code display period can be displayed without displaying the information of the code expiration date. In this case, the code valid period is substantially the same as the code display period.

< Effect of embodiment 4 >

Example 4 shows the following configuration: when information on the valid code period or the remaining time of the valid code period is displayed on the code display screen, the information is changed from the valid code period to a set period and displayed on the code display screen.

As an example of the effect obtained by such a configuration, when the 1 st validity period is displayed in the display area of the terminal, the 1 st validity period is changed to a set period and displayed in the display area, so that it is possible to cope with, for example, the 1 st validity period passing before the display period of the code information in the terminal, and it is possible to improve the convenience of the user.

< embodiment 5 >

If the code expiration date associated with the terminal display code is set by the server 10 for a long period of time, there is a risk that the security is low and the terminal display code stored in the terminal 20 is stolen by others.

In the present embodiment, the terminal 20 transmits code generation request information requesting generation of a plurality of (2 or more) terminal display codes to the server 10 via the communication I/F22. Upon receiving the code generation request information, the server 10 performs a terminal display code generation process.

In the present embodiment, in the terminal display code generation process, the control unit 11 of the server 10 generates a plurality of terminal display codes having different start times (or start dates and times) and end times (or end dates and times) of the code expiration dates. Then, the data of the plurality of generated terminal display codes is stored in the code management database 159.

Fig. 8 shows an example of the code management database 159 stored in the storage unit 15 of the server 10 according to the present embodiment.

The code management database 159 is similar to the code management database 159 shown in fig. 4 to 6, but the data of the terminal display code stored together with the application ID is partially different among the code management data.

Specifically, the code management data is not limited to the application ID and stores, as an example, two sets (four in total) of terminal display codes, one set of which is two terminal display codes and has the same code generation date and time but different start dates and times of the valid periods of the codes.

In this display example, four data of the code serial numbers "C-n 1" to "C-n 4" are stored as data of the code for terminal display having a code generation date and time of "9 hours 9 minutes 9 months 10 months 6 months 2019" for the terminal 20 to which the ID "U0001" is applied or the user of the terminal 20.

The 2 terminal display codes of the code serial numbers "C-n 1" and "C-n 2" are codes having a code expiration date of "00 min 00 s at 9.6.10.9.2019 to 14 h, 59 min 59 s at 10.6.10.2019". That is, the 2 terminal display codes are codes in which the start time of the code expiration date is the code generation time "9 hours 00 minutes" and the code expiration time is "6 hours".

On the other hand, the 2 terminal display codes of the code serial numbers "C-n 3" and "C-n 4" are codes having a code expiration date of "00 min 00 s at 15 h/10 d/15 in 2019, 6/10 d/20 min 59 s at 2019, 6/10 d". That is, the 2 terminal display codes are codes in which the start time of the code validity period is "15: 00" after 6 hours have elapsed from the code generation time and the code validity time is "6 hours".

Therefore, the 2 terminal display codes of the code serial numbers "C-n 1" and "C-n 2" and the 2 terminal display codes of the code serial numbers "C-n 3" and "C-n 4" differ in the start time of the valid period of the codes although the valid time of the codes is the same, and as a result, the valid periods of the codes differ.

In the present embodiment, the server 10 generates the plurality of terminal display codes as described above based on the code generation request information received from the terminal 20. Then, the generated plurality of terminal display codes are transmitted to the terminal 20 together with the respective code serial numbers and the respective code expiration dates, not by way of limitation, but by way of example.

The terminal 20 receives the plurality of terminal display codes transmitted from the server 10, the respective code serial numbers, and the respective code expiration dates. Then, the received information is stored in the terminal display code storage data 2831 of the storage unit 28.

< Effect of embodiment 5 >

In embodiment 5, request information (without limitation, an example of information related to the request for transmission of code information) is generated based on a code transmitted from the terminal 20, and the terminal 20 receives, via the communication I/F22, the 1 st terminal display code image or the 1 st settlement number (without limitation, an example of the 6 th code information) associated with the 1 st code expiration date by the server 10, and the 2 nd terminal display code image or the 2 nd settlement number (without limitation, an example of the 7 th code information) associated with the 2 nd code expiration date by the server 10. Wherein the start time of the 1 st code validity period is different from the start time of the 2 nd code validity period, and the end time of the 1 st code validity period is different from the end time of the 2 nd code validity period.

As an example of the effect obtained by such a configuration, it is possible to improve security and reduce the risk of stealing the terminal display code stored in the storage unit of the terminal by another person by receiving and storing a plurality of pieces of code information having different expiration dates at the start time and the end time of the expiration date by the terminal.

< modification 5 >

In embodiment 5, in the terminal display code generation process, the server 10 generates and transmits to the terminal 20a plurality of terminal display codes different in the start time (or start date and time) and end time (or end date and time) of the code expiration date, but the present invention is not limited thereto.

By way of example and not limitation, the server 10 may generate and transmit to the terminal 20a plurality of terminal display codes having different start times (or start dates and times) of the code validity period but the same end times (or end dates and times) of the code validity period, or may not. In this case, the code for terminal display may be generated by changing the code valid time so that the end time (end date and time) of the code valid period becomes the same.

Further, by way of example and not limitation, the server 10 may generate and transmit to the terminal 20a plurality of terminal display codes having different end times (or end dates and times) of the code validity period but having the same start time (start date and time) of the code validity period, or may not.

The number of terminal display codes having the same code expiration date (the number of terminal display codes in 1 group (1 set)) or the number of terminal display codes having different code expiration dates (the number of groups and the number of sets) may be set in any manner.

Description of the symbols

1 communication system

10 server

20 terminal

30 network

40 store POS system

50 shop code reader device

60 code cash register

70 store servers.

Claims

1. An information processing method of a terminal that performs processing related to settlement based on code information, the information processing method comprising:

receiving 1 st code information associated with 1 st expiration date by the server from the server via a communication part of the terminal;

storing the received 1 st code information in a storage part of the terminal by a control part of the terminal; and

executing processing relating to the settlement by the control section based on the 1 st code information,

the settlement is performed by the server according to the 1 st term of validity and a time based on processing related to the settlement.

2. The information processing method according to claim 1,

the information processing method further includes: receiving 2 nd code information different from the 1 st code information from the server via the communication section based on the information on the 1 st term of validity,

the 2 nd code information is associated with a2 nd validity period by the server, the 2 nd validity period being different from the 1 st validity period.

3. The information processing method according to claim 2,

the information processing method further includes: receiving information on the 1 st term of validity from the server via the communication unit; and

the control unit associates the 1 st expiration date with the 1 st code information and stores the associated information in the storage unit.

4. The information processing method according to claim 3,

the information processing method further includes: and transmitting, to the server via the communication unit, information requesting transmission of the 2 nd code information based on the information on the 1 st expiration date.

5. The information processing method according to any one of claims 2 to 4,

receiving the 2 nd code information from the server via the communication section before the 1 st term of validity elapses.

6. The information processing method according to any one of claims 2 to 5,

the information processing method further includes: the control unit performs a process of making the 1 st code information unusable based on the reception of the 2 nd code information.

7. The information processing method according to claim 1,

the information processing method further includes: transmitting information on extension of the 1 st validity period to the server via the communication unit.

8. The information processing method according to claim 6,

the information processing method further includes: the processing related to the extension of the 1 st validity period is performed by the control unit of the terminal based on the execution of the processing related to the authentication of the user of the terminal.

9. The information processing method according to any one of claims 6 to 8,

the information processing method further includes: receiving information on the extended 1 st term of validity transmitted from the server via the communication section; and

displaying information indicating that the 1 st validity period is extended in a display area of the terminal.

10. The information processing method according to claim 1,

the information processing method further includes: receiving, via the communication unit, 3 rd code information transmitted from the server based on the set time and associated with a3 rd validity period by the server.

11. The information processing method according to claim 1,

the information processing method further includes: receiving, via the communication unit, 4 th code information associated with a4 th expiration date by the server, transmitted from the server based on information of a user of the terminal.

12. The information processing method according to claim 1,

the information processing method further includes: receiving, via the communication unit, 5 th code information associated with a 5 th expiration date by the server, the 5 th code information being transmitted from the server based on information relating to a disaster.

13. The information processing method according to any one of claims 1 to 12, wherein

The 1 st expiration date is set by the server based on information of a user of the terminal.

14. The information processing method according to claim 13,

the information of the user of the terminal comprises a credit score of the user.

15. The information processing method according to claim 13 or 14,

the information of the user of the terminal includes information of a location of the user or information of a location of the terminal.

16. The information processing method according to any one of claims 13 to 15,

the information of the user of the terminal includes information of a schedule of the user.

17. The information processing method according to any one of claims 13 to 16,

the information of the user of the terminal includes information of the code information-based settlement of the user.

18. The information processing method according to any one of claims 1 to 17,

the 1 st term of validity is set based on information about an event acquired by the server.

19. The information processing method according to claim 1,

the information processing method further includes: and displaying the information of the 1 st validity period in a display area of the terminal.

20. The information processing method according to claim 18,

the information processing method further includes: and displaying the 1 st expiry date information and the 1 st code information in the display area.

21. The information processing method according to claim 19 or 20,

the 1 st expiration date information is displayed in the display area based on a communication state of the terminal.

22. The information processing method according to claim 20,

the information processing method further includes: and displaying the 1 st code information and a term which is different from the 1 st valid term and is available for the 1 st code information in the display area.

23. The information processing method according to claim 19 or 20,

the information processing method further includes:

when the 1 st valid period is displayed in the display area, the 1 st valid period is changed to a set period and displayed in the display area.

24. The information processing method according to claim 1,

the information processing method further includes: receiving, via the communication unit, 6 th code information associated with a 6 th expiration date by the server and 7 th code information associated with a 7 th expiration date by the server based on information related to the request for transmission of the code information transmitted from the terminal,

the start time of the 6 th validity period is different from the start time of the 7 th validity period,

the end time of the 6 th validity period is different from the end time of the 7 th validity period.

25. A program executed by a computer of a terminal that performs processing related to settlement based on code information, the program comprising:

storing the received 1 st code information in a storage unit of the terminal; and

performing processing relating to the settlement based on the 1 st code information,

26. A terminal that executes processing relating to settlement based on code information, the terminal comprising:

a communication unit that receives 1 st code information associated with 1 st expiration date from a server by the server; and

a control unit for controlling the storage unit of the terminal to store the received 1 st code information,

the control unit executes processing related to the settlement based on the 1 st code information,

27. A terminal for executing a process related to settlement based on code information, the terminal comprising a processor for reading a program stored in a memory and executing the process based on the program,

the processor performs:

a process of receiving 1 st code information associated with 1 st expiration date by the server from the server via a communication unit of the terminal;

a process of storing the received 1 st code information in the memory; and

processing related to the settlement based on the 1 st code information,

28. An information processing method which is an information processing method of a server that manages settlement based on code information, comprising:

storing the 1 st code information in association with the 1 st expiration date in a storage unit of the server by a control unit of the server;

transmitting the 1 st code information to a terminal performing processing related to the settlement via a communication unit of the server;

receiving, via the communication unit, the 1 st code information and information based on a time of processing related to the settlement performed based on the 1 st code information; and

the settlement processing is performed by the control unit based on the 1 st expiration date associated with the received 1 st code information and the received time based on the processing related to the settlement.

29. A program executed by a computer of a server that manages settlement based on code information, the program comprising:

a storage unit that associates and stores the 1 st code information with the 1 st expiration date in the server;

the settlement processing is performed based on the 1 st term of validity associated with the received 1 st code information and the received time based on the settlement-related processing.

30. A server for managing settlement based on code information, the server comprising:

a storage unit for storing the 1 st code information in association with the 1 st expiration date;

a communication unit that transmits the 1 st code information to a terminal that performs processing related to the settlement, and receives the 1 st code information and information based on a time of the processing related to the settlement, which is performed based on the 1 st code information; and

and a control unit that performs the settlement processing based on the 1 st expiration date associated with the received 1 st code information and the received time based on the processing related to the settlement.

31. A server for managing settlement based on code information, the server comprising a processor for reading a program stored in a memory and executing processing based on the program,

the processor performs:

a process of associating and storing 1 st code information with 1 st term of validity in the memory;

a process of transmitting the 1 st code information to a terminal performing the process related to the settlement based on the 1 st code information and receiving the 1 st code information and information based on a time of the process related to the settlement; and