JP2019075146A - Method for providing reward to user, system, and mobile device - Google Patents

Abstract

To provide a method for automating provision of rewards.SOLUTION: A transaction system provides rewards to a user. A mobile device 20 transmits a reward request including a user ID to an ePOS 10. The ePOS 10 transmits transaction data, to the mobile device 20. The mobile device 20 transfers the transaction data to a server 30. The server 30 authenticates the transaction data and the server 30 transmits reward data to the mobile device 20. The mobile device 20 stores points.SELECTED DRAWING: Figure 1

Description

  The present invention relates to a method for providing a reward to a user.

  The customer loyalty program rewards in exchange for stamps, points and other quantifiable indicators of consumption / transactions. Its purpose is to gain repeat business and to gain insights and analysis on consumer spending trends. Some examples of these are physical point / stamp cards, brand-based / store-based credit cards and custom mobile applications.

  Existing methods to participate in and obtain rewards require additional actions before and after transactions by both vendors and customers. This reduces the probability that the customer will participate in the reward program. The present invention eliminates these friction points by automating the process through wireless communication between a POS system and transaction devices such as cash registers and vending machines and customer devices such as mobile phones.

  The main aspect of the present invention for solving the above-mentioned problems is a method for providing a reward to a user. The method comprises the steps of: transmitting data about a user from a mobile device to a transaction device; transmitting transaction data regarding a transaction performed on the transaction device from the transaction device to the mobile device; Transferring the transaction data to the server, authenticating the transaction data at the server, and transmitting reward data to the mobile device indicating that the reward has been granted to the user, if the transaction data is authenticated. Storing reward data on the mobile device.

  In the present invention, the transaction data can be encrypted by the transaction device and the server can be configured to decrypt the transaction data and authenticate the configuration data.

  In the present invention, it is possible that the transaction device and the server hold a common key, the transaction device encrypts transaction data using the key, and the server decrypts the transaction data using the key. .

  In the present invention, the method comprises the steps of: generating reward data on the mobile device based on the transaction data; transferring the reward data temporarily on the mobile device; and Storing the reward data permanently on the mobile device after the step of transmitting the reward data to the device.

  In the present invention, the method comprises the steps of: sending the exchange data from the mobile device to the server; authenticating the exchange data at the server; and generating the token according to the exchange data at the server if the exchange data is authenticated. The steps of: transmitting the token from the server to the mobile device; transferring the token from the mobile device to the transaction device; and performing the process of exchange at the transaction device Good.

  Another aspect of the invention is a system for providing a reward to a user. The system comprises a transaction device, a mobile device and a server. The mobile device includes a reward request transmission unit that transmits data about the user to the transaction device, and the transaction device includes a transaction data transmission unit that transmits transaction data regarding the transaction performed in the transaction device to the mobile device, The body device includes a transaction data transfer unit for transferring the transaction data to the server, and the server is a transaction authentication unit for authenticating the transaction data, and a reward indicating that the reward is given to the user when the transaction data is authenticated. And a reward data transmission unit that transmits data to the mobile device, the mobile device including a reward data reception unit that receives the reward data from the server and stores the reward data in the mobile device.

  Another aspect of the present invention is a mobile device. The mobile device transmits a reward request transmission unit that transmits data on the user to the transaction device, a transaction data transfer unit that transfers transaction data on the transaction performed on the transaction device from the transaction device to the server, and a reward is given to the user A reward data receiving unit for receiving reward data indicating that the payment has been made, wherein the reward data is a reward data receiving unit authenticated by the server, and a reward data receiving unit for receiving the reward data from the server and storing the reward data in the mobile device And.

  Other problems described in the present application and means for solving the problems appear in the description of the embodiments, the description of the drawings, and other parts.

FIG. 1 is a schematic view of a transaction system as an embodiment according to the present invention. FIG. 2 is an example of the hardware configuration of the POS 10. FIG. 3 is an example of the software configuration of the POS 10. FIG. 4 is an example of the hardware configuration of the mobile device 20. FIG. 5 is an example of the software configuration of the mobile device 20. FIG. 6 is an example of the configuration of transaction data held in the transaction storage 241. FIG. 7 shows an example of the configuration of the reward storage 242. FIG. 8 is an example of the configuration of the exchange storage 243. FIG. 9 is an example of the hardware configuration of the server 30. FIG. 10 is an example of the software configuration of the server 30. FIG. 11 is an example of transaction data held in the transaction database 341. FIG. 12 shows an example of the configuration of the customer database 342. FIG. 13 shows an example of the configuration of the exchange database 343. FIG. 14 is an outline of processing of the transaction system. FIG. 15 is a sequence diagram of session establishment. FIG. 16 is a sequence diagram of reward processing. FIG. 17 is a sequence diagram of the exchange process.

== System Configuration ==
FIG. 1 shows a schematic view of a transaction system as an embodiment according to the present invention. The transaction system comprises a POS (Point Of Sale), a mobile device 20, and a server 30. The POS is capable of wireless communication, and provides the reward program of the present embodiment (hereinafter referred to as "ePOS 10"). The following matters are assumed in this embodiment. A point reward program is provided, the ePOS 10 issues points to the user according to the purchase amount at the store, the mobile device 20 manages the number of points in its storage, and the server 30 exchanges rewards and points Certify.

  The ePOS 10 is a transaction device, which performs transactions such as trading, detection of services and arrival of users. The ePOS 10 may be a computer such as a POS cash register or an interactive kiosk. When a transaction occurs, the ePOS 10 rewards the user.

  The mobile device 20 is a computer such as a smartphone, a tablet computer, a mobile phone, a PDA (Personal Digital Assistant), a notebook computer, etc., and is carried by the user. Mobile device 20 executes a computer program. This computer program realizes management of the reward to the user and transmission / reception / transfer of data to / from the ePOS 10 and the server 30.

  The ePOS 10 and the mobile device 20 are connected to each other via a wireless channel 41. In the present embodiment, it is assumed that the ePOS 10 and the mobile device 20 communicate with each other using Bluetooth (registered trademark) LE (Low Energy). Mobile device 20 and server 30 are connected to each other via a wireless channel 42. In the present embodiment, it is assumed that the mobile device 20 and the server 30 communicate with each other according to the TCP / IP protocol using WiFi or any mobile telephone communication protocol (3G, 4G, LTE, etc.). Of course, Bluetooth®, WiFi, Near Field Communication (NFC), or other wireless communication technologies may be used for communication via the wireless channels 41 and 42.

== ePOS10 ==
FIG. 2 shows an example of the hardware configuration of the ePOS 10. As illustrated in FIG. 2, the ePOS 10 includes a CPU 101, a RAM (Random Access Memory) 102, a storage device 103, an input interface 104, an output interface 105, a printer interface 106, and a Bluetooth (registered trademark) unit 107. And. The storage device 103 is, for example, a hard disk drive, a solid state drive, a flash memory, etc., and holds data and programs. The CPU 101 acquires a program held in the storage device 103, provides the program to the RAM 102, and executes the program to realize various functions. The input interface 104 is an interface for connecting to the scanner 11. The input interface 104 acquires data such as, for example, EAN (European (International) Article Number) code, JAN (Japanese Article Number) code, GTIN (Global Trade Item Numbers) code or the like conforming to USB (Universal Serial Bus). The output interface 105 is an interface for connecting to the display 12. The output interface 105 may be an analog interface that outputs RGB signals or a digital interface that outputs digital image data according to the display 12. The printer interface 106 is an interface for connecting to the printer 13. The ePOS 10 may print the receipt via the printer interface and the printer 13. The Bluetooth® unit 107 transmits / receives data to / from the channel 41 using Bluetooth® LE technology.

FIG. 3 shows an example of the software configuration of the ePOS 10. As shown in FIG. 3, the ePOS 10 includes a session establishment unit 111, a reward unit 112, an exchange unit 113, a POS unit 114, and a key storage 115.
The reward unit 112, the exchange unit 113, and the POS unit 114 are realized, for example, by the CPU 101 acquiring a program held in the storage device 103, giving the program to the RAM 102, and executing the program. The key storage 115 is realized, for example, as a storage area provided by the RAM 102 and / or the storage device 103.

  The session establishment unit 111 establishes a session between the ePOS 10 and the mobile device 20. The session establishment unit 111 broadcasts connection information. The connection information is, for example, data indicating that the ePOS 10 can reward the user, that is, in the present embodiment, the ePOS 10 provides a point reward program. The connection information may be a pairing request if Bluetooth® technology is used. The session establishing unit 111 receives the reply from the mobile device 20 and establishes a session with the mobile device 20 according to a known communication technology. The session establishing unit 111 may establish pairing by exchanging a pass-key with the mobile device 20 when Bluetooth (registered trademark) technology is used. The session establishing unit 111 transmits, to the mobile device 20, brand information such as a store name, a service name, and device information indicating the capability of the ePOS 10.

  Key storage 115 holds keys for encryption / decryption data. In this embodiment, a common key is used for both encryption and decryption. However, it is also possible for the key storage 115 to hold the public key and the secret key using the public key and the secret key of the public key cryptography.

  The reward unit 112 executes processing for rewarding the user. The reward unit 112 includes a reward request receiving unit 121, a transaction data acquisition unit 122, a reward generation unit 123, and a transaction data transmission unit 124.

  The reward request receiving unit 121 receives, from the mobile device 20, a request for rewarding the user (hereinafter, referred to as a “reward request”). The reward request includes an identifier of the user (hereinafter referred to as "user ID").

  The transaction data acquisition unit 122 acquires, from the POS unit 114, data related to the transaction made by the POS unit 114 (hereinafter, this data is referred to as "transaction data"). In the present embodiment, transaction data includes the timestamp of the transaction. Transaction data may include various information about the transaction, such as the amount of goods purchased.

  The reward generation unit 123 generates a reward based on the transaction data. In the present embodiment, the reward generation unit 123 may generate the number of points to be given to the user based on the purchase amount included in the transaction data.

  The transaction data transmission unit 124 transmits, to the mobile device 20, the transaction data to which the reward (the number of points) is attached. The transaction data transmission unit 124 encrypts transaction data using the key held in the key storage 115, and attaches the number of points to the encrypted transaction data before transmission.

  The exchange unit 113 executes a process for using the reward. The exchange unit 113 includes a token reception unit 131, a token authentication unit 132, an exchange processing unit 133, and a completion data transmission unit 134.

  The token acceptance unit 131 receives a token from the mobile device 20. The token is issued by the server 30 to indicate that the exchange is available. As described below, the token is generated and encrypted by the server 30 and transferred by the mobile device 20 to the ePOS 10. In the present embodiment, the token includes the number of points exchanged.

  The token authentication unit 132 authenticates the token received from the mobile device 20. The token authentication unit 132 decrypts the token using the key held in the key storage 115. The token authentication unit 132 may determine that the token is valid when the decryption of the token is successful. In addition, token authenticator 132 may use a common data verification technique, such as calculating the hash code of the token and comparing it to the hash code attached to the token. In the present embodiment, the token includes the issue date and time, and the token authentication unit 132 determines whether the token is valid or not by checking whether the date and time is within a predetermined period. If authentication of the token is successful, return to the user is permitted.

  The exchange processing unit 133 executes a process related to the exchange. For example, the exchange processing unit 133 may display on the display 12 that the user should be rewarded, and as a result, a clerk of a store equipped with the ePOS 10 may give a gift to the user. Furthermore, for example, the exchange processing unit 133 may display the number of points to be exchanged on the display 12, and as a result, the store clerk may view the number and discount. Furthermore, for example, the exchange processing unit 133 may transmit a discount command including the number of points to the POS unit 114, and as a result, the POS unit 114 may perform the discount according to the number of points.

  The completion data transmission unit 134 transmits data (hereinafter referred to as “completion data”) indicating that the point has been used. At the time of transmission, the completion data transmission unit 134 sets the brand information and the number of used points in the completion data, and encrypts the completion data using the key held in the key storage 115.

  The POS unit 114 executes various processes associated with the POS system. Since the process executed by the POS unit 114 is assumed to be a known process performed in a general POS system, the detailed description of the POS unit 114 is omitted.

== Mobile device 20 ==
FIG. 4 shows an example of the hardware configuration of the mobile device 20. As shown in FIG. As shown in FIG. 4, the mobile device 20 includes a CPU 201, a RAM 202, a flash memory 203, a communication device 204, a Bluetooth (registered trademark) unit 205, and a touch panel display 206. The flash memory 203 holds data and programs. The CPU 201 acquires a program held in the flash memory 203, provides the program to the RAM 202, and executes the program to realize various functions. Wireless communication device 204 is a device for wireless communication using channel 42. The wireless communication device 204 may be a WiFi communication device, a wireless transmitter, a communication device for mobile phones, or the like. The Bluetooth® unit 205 transmits / receives data to / from the channel 41 using Bluetooth® LE technology. The touch panel display 206 inputs / outputs data to / from the user.

FIG. 5 shows an example of the software configuration of the mobile device 20. As shown in FIG. As shown in FIG. 5, the mobile device 20 includes a session establishment unit 211, a reward unit 212, an exchange unit 213, a transaction storage 241, a reward storage 242, and a replacement storage 243.
The session establishing unit 211, the reward unit 212, and the exchange unit 213 are realized, for example, by the CPU 201 acquiring a program held in the flash memory 203, providing the program to the RAM 202, and executing the program. The transaction storage 241, the reward storage 242, and the exchange storage 243 are realized as, for example, storage areas provided by the RAM 102 and / or the flash memory 203.

  The session establishing unit 211 establishes a session between the ePOS 10 and the mobile device 20. The session establishing unit 211 detects connection information notified by the ePOS 10. The session establishing unit 211 determines that the ePOS 10 provides a point reward program based on the connection information.

  The transaction storage 241 holds the history of transaction data. FIG. 6 shows an example of the configuration of transaction data held in the transaction storage 241. As shown in FIG. 6, transaction data includes a date and time column, a brand column, and a transaction column. The date and time column is the date and time when the transaction was performed. The brand column is brand information notified by the ePOS 10 when the connection is established. The transaction column is information on transactions made by the ePOS 10. In the example of FIG. 6, the column shows that the purchase of 1000 yen in Japanese yen was made by ePOS 10. By referring to the transaction storage 241, the mobile device 20 can display the history of transactions to the user.

  The reward storage 242 holds the reward given to the user. FIG. 7 shows an example of the configuration of the reward storage 242. In the present embodiment, the reward storage 242 holds the number of points as shown in FIG.

  The reward unit 212 executes processing for rewarding the user. The reward unit 212 includes a reward request transmission unit 221, a transaction data transfer unit 222, and a reward data reception unit 223.

  The reward request transmission unit 221 transmits a reward request. When the session establishing unit 211 detects that the ePOS 10 provides the point reward program, and the user does not input a command for using the point, the reward request transmission unit 221 transmits a reward request to the ePOS 10. The reward request transmission unit 221 sets a user ID indicating a user who is using the mobile device 20 as a reward request.

  When the transaction data transfer unit 222 receives transaction data from the ePOS 10, the transaction data transfer unit 222 transfers the transaction data to the server 30. The transaction data transfer unit 222 temporarily stores the number of points attached to the transaction data in the RAM 202 and / or the flash memory 203. At the time of transfer, the transaction data transfer unit 222 attaches a user ID and a personal password to transaction data. As described below, if transaction data is authenticated at server 30 and reward data is received from server 30, this temporary number of points will be permanently stored in reward storage 242.

  The reward data receiving unit 223 receives, from the server 30, data (hereinafter, referred to as “reward data”) indicating that the user has been given a reward. As described below, reward data is sent by server 30 when server 30 authenticates transaction data. The reward data receiving unit 223 adds the number of temporary points held in the RAM 202 to the number of points held in the reward storage 242. As a result, temporary points are permanently stored. In the present embodiment, the server 30 transmits the decrypted transaction data together with the reward data. The reward data accepting unit 223 receives transaction data, and stores the transaction data in the transaction storage 241.

  The exchange storage 243 holds data on rewards given to the user (hereinafter referred to as “exchange data”). FIG. 8 shows an example of the configuration of exchange data held in the exchange storage 243. As shown in FIG. 8, the reward data includes a date and time column, a brand column, and a point column. The date and time column is when points are used. The brand column is brand information notified by the ePOS 10 when the connection is established. The column of points is the number of points used.

  The exchange unit 213 executes a process for using the reward. Exchange unit 213 includes an exchange request transmission unit 231, a token transfer unit 232, a completion data transfer unit 233, and an exchange data reception unit 234.

  When the user inputs a command for point use, the exchange request transmitter 231 transmits a request for using the point (hereinafter, referred to as “exchange request”) to the server 30. The exchange request transmission unit 231 sets the user ID and the number of points to be used in the exchange request.

  When the token transfer unit 232 receives the token issued from the server 30, the token transfer unit 232 transfers the token to which the user ID is added to the ePOS 10.

  When the completion data transfer unit 233 receives the completion data from the ePOS 10, the completion data transfer unit 233 transfers the completion data to the server 30.

  The exchange data accepting unit 234 receives exchange data from the server 30. As described later, the server 30 issues exchange data when the server 30 authenticates the completion data. The exchange data includes brand information and the number of points used (in this context, the exchange data may be the same as the completion data). The exchange data receiving unit 234 subtracts the number of used points included in the exchange data from the number of points held in the reward storage 242.

== server 30 = =
FIG. 9 shows an example of the hardware configuration of the server 30. As shown in FIG. 9, the server 30 includes a CPU 301, a RAM 302, a storage device 303, a communication device 304, an input device 305, and an output device 306. The storage device 303 is, for example, a hard disk drive, a solid state drive, a flash memory, etc., and holds data and programs. The CPU 301 acquires a program held in the storage device 303, provides the program to the RAM 302, and executes the program to realize various functions. Communication device 304 is a device for communication using channel 42. The communication device 304 performs communication via the channel 42, and is an adapter of Ethernet (registered trademark), a modem for communication via a telephone line, a WiFi communication device, a wireless transmitter, a communication device for mobile phones, etc. May be The input device 305 receives data input from the user, and may be, for example, a keyboard, a mouse, a microphone, a touch panel, or the like. The output device 306 outputs data to the user, and may be, for example, a display device or a speaker.

  FIG. 10 shows an example of the software configuration of the server 30. As shown in FIG. 10, the server 30 includes a reward unit 311, an exchange unit 312, a transaction database 341, a customer database 342, an exchange database 343, and a key storage 344.

  The transaction database 341 maintains a history of transaction data for each user. FIG. 11 shows an example of transaction data held in the transaction database 341. As compared with the transaction storage 241 shown in FIG. 6, in the transaction database 341, transaction data is held together with the user ID.

  The customer database 342 holds information on users (hereinafter referred to as "customer data"). The customer data includes the reward (the number of points) given to each user. FIG. 12 shows an example of the configuration of the customer database 342. As shown in FIG. 12, the customer data includes the user ID, the user's name (user name), the password of the user who may be encrypted, and the number of points. Customer data may include further items about the user, such as age, address, interest, etc.

  The reward unit 311 executes a process for rewarding the user. The reward unit 311 includes a transaction data reception unit 321, a transaction data authentication unit 322, and a reward data transmission unit 323.

  The transaction data accepting unit 321 receives from the mobile device 20 the transaction data transmitted by the ePOS 10 and transferred by the mobile device 20.

  The transaction data authentication unit 322 authenticates the transaction data received from the mobile device 20. As described above, transaction data is encrypted at the ePOS 10. The transaction data authentication unit 322 decrypts transaction data using the key held in the key storage 344. When the transaction data authentication unit 322 succeeds in decoding the transaction data, it may determine that the transaction data is valid. In addition, transaction data verifier 322 may use common data verification techniques, such as calculating a hash code of the transaction data and comparing it to the hash code attached to the transaction data. The transaction data authentication unit 322 stores the decrypted transaction data in the transaction database 341 together with the user ID attached to the transaction data. The transaction data authentication unit 322 adds the number of points attached to the transaction data to the number of points corresponding to the user ID included in the transaction data among the number of points held in the customer database 342.

  The reward data transmission unit 323 transmits the reward data to the mobile device 20 when the transaction data authentication is successful. In the present embodiment, the reward data transmission unit 323 transmits the decrypted transaction data to the mobile device 20 together with the reward data. If the transaction data authentication is successful, the reward data transmission unit 323 adds the number of points attached to the transaction data to the number of points in the customer database 342 corresponding to the user ID attached to the transaction data. Do. Furthermore, the reward data transmission unit 323 stores the decrypted transaction data together with the user ID attached to the transaction data. If authentication of the transaction data fails, the reward data transmission unit 323 transmits an error to the mobile device 20.

  The exchange storage 243 holds exchange data. FIG. 13 shows an example of the configuration of exchange data held in the exchange storage 243. As shown in FIG. 13, the exchange data includes a user ID column, a date and time column, a brand column, and a point column. The column of user ID is an identifier of the user who used the point. The date and time column is when points are used. The brand column is brand information notified by the ePOS 10 when the connection is established. The column of points is the number of points used.

  The exchange unit 312 executes a process for using the reward. Exchange unit 312 includes exchange request reception unit 331, exchange authentication unit 332, token generation unit 333, token transmission unit 334, completion data reception unit 335, and exchange data transmission unit 336.

  The exchange request accepting unit 331 receives an exchange request from the mobile device 20.

  The exchange authentication unit 332 authenticates the exchange request. The exchange authentication unit 332 acquires the number of points corresponding to the user ID attached to the exchange request from the customer database 342, compares the acquired number of points with the number of points to be used attached to the exchange request, and It is determined whether the number of points is equal to or greater than the number of points used. If the acquired number of points is equal to or more than the number of points to be used, the exchange authentication unit 332 determines that the exchange request is valid.

  The token generation unit 333 issues a token when it is determined that the exchange request is valid. The token generation unit 333 sets the current date and time, the valid period, and the number of points to be used in the token. The token generation unit 333 encrypts the token using the key held in the key storage 344.

  The token transmitter 334 transmits the encrypted token to the mobile device 20.

  The completion data reception unit 335 receives, from the mobile device 20, the completion data transmitted by the ePOS 10 and transferred by the mobile device 20. The completion data authentication unit 335 decrypts the completion data using the key held in the key storage 344. The completion data accepting unit 335 invalidates the token. The completion data reception unit 335 stores the used points, that is, the completion data reception unit 335 subtracts the number of points used from the number of points corresponding to the user ID in the customer database 342. The completion data accepting unit 335 generates exchange data including the brand information and the number of points used, both of which are included in the completion data, and stores the exchange data in the exchange database 343.

  The exchange data transmission unit 336 transmits the generated exchange data to the mobile device 20.

== processing ==
The processing performed by the transaction system of the present embodiment is outlined below. FIG. 14 shows an outline of processing of the transaction system. As shown in FIG. 15, first, a session between the ePOS 10 and the mobile device 20 is established (S501). The exchange request transmission unit 231 of the mobile device 20 checks whether the number of points held in the reward storage 242 is equal to or more than a predetermined minimum number of points for exchange (S502). If the number of points is equal to or more than the minimum number of points (S502: YES), the exchange request transmission unit 231 inquires the user whether the user desires to use the points (S503). For example, the exchange request transmission unit 231 may display a pop-up dialog on the touch panel display 206, and may receive an input from the user when the point is to be used. The exchange request transmitter 231 may beep, sound, and / or drive the transducer to draw the user's attention. The exchange request transmission unit 231 may determine that the user does not use the point if there is no input from the user.

  If the number of points is smaller than the minimum number of points (S502: NO) or if the user does not want to use the points (S503: NO), the reward process shown in FIG. 16 is executed (S504). Otherwise (S503: YES), the exchange process shown in FIG. 17 is executed (S505).

== session establishment ==
FIG. 15 is a sequence diagram of session establishment.
The session establishing unit 111 of the ePOS 10 broadcasts connection information (S521). The session establishing unit 211 of the mobile device 20 detects connection information notified by the ePOS 10 (S522), and transmits a response to the ePOS 10 (S523). The session establishment unit 111 transmits the brand information and the device information to the mobile device 20 in response to the response transmitted from the mobile device 20 (S524).
The session establishing unit 211 determines that the ePOS 10 provides a point reward program based on the brand information and the device information (S525). If the session establishment unit 211 determines that the point reward program is not provided by the ePOS 10, the session establishment unit 211 may end the process. If the session establishment unit 211 determines that the point reward program is provided, the reward request transmission unit 221 of the mobile device 20 transmits a reward request to the ePOS 10 (S526). The session establishing unit 111 and the session establishing unit 211 perform some negotiations in accordance with a general technique for establishing a communication session in order to establish a session (S527).
As described above, a session is established between the ePOS 10 and the mobile device 20, and the ePOS 10 and the mobile device 20 transmit and receive data via the session.

== Reward processing = =
FIG. 16 is a sequence diagram of reward processing.
The transaction data acquisition unit 122 waits for a transaction to be performed by the POS unit 114 (S 542), and acquires transaction data from the POS unit 114 (S 543). The transaction data acquisition unit 122 sets the user ID received from the mobile device 20 as transaction data. The reward generation unit 123 generates the number of points to be granted based on the transaction data (S544). For example, the reward generation unit 123 may calculate the number of points based on the purchase amount included in the transaction data. The transaction data transmission unit 124 encrypts transaction data using the key held in the key storage 115 (S545). The transaction data transmission unit 124 attaches the number of points to be provided to the encrypted transaction data, and transmits the encrypted transaction data accompanied by the number of points to the mobile device 20 (S546).

  The transaction data transfer unit 222 receives the transaction data, and temporarily stores the number of points to be attached which is attached to the transaction data (S547). The transaction data transfer unit 222 transfers transaction data including the number of points to the server 30 (S548).

  The transaction data accepting unit 321 of the server 30 receives the transaction data from the mobile device 20, and the transaction data authenticating unit 322 decrypts the transaction data (S549). The transaction data authentication unit 322 authenticates the transaction data (S550). The transaction data authentication unit 322 stores the decrypted transaction data in the transaction database 341 (S551). If the transaction data authentication is successful, the user ID included in the transaction data among the number of points held in the customer database 342 The number of points attached to the transaction data is added to the number of points corresponding to (S552). The reward data transmission unit 323 transmits the reward data and the decrypted transaction data to the mobile device 20 (S553).

  The reward data receiving unit 223 of the mobile device 20 receives the reward data and the decrypted transaction data, stores the transaction data in the transaction storage 241 (S554), and stores the temporary point number held in the RAM 202 as the reward storage. It is added to the number of points held in 242 (S555).

  As described above, according to the transaction system according to the present embodiment, the mobile device 20 can automatically detect the ePOS 10 providing the point reward program, and also automatically handles the reward processing using Bluetooth (registered trademark) LE technology. Can be Thus, no user action is required to participate in the reward program.

== Exchange processing ==
FIG. 17 is a sequence diagram of the exchange process.

  The exchange request transmission unit 231 receives an input of the number of points to be used from the user (S561), and transmits an exchange request including the user ID and the input number of points to the server 30 (S562).

  The exchange request receiving unit 331 of the server 30 receives the exchange request, and the exchange authentication unit 332 authenticates the exchange request (S563). When the authentication of the exchange request is successful, the token generation unit 333 issues a token including the current date and time, the validity period, and the number of points to be used, and encrypts the token using the key held in the key storage 344. (S564). The token transmitter 334 transmits the token to the mobile device 20 (S565).

  The token transfer unit 232 receives the token and transfers the token to the ePOS 10 (S566).

  The token accepting unit 131 of the ePOS 10 receives the token, and the token authenticating unit 132 decrypts the token using the key stored in the key storage 115 (S567). The exchange processing unit 133 executes the process related to the exchange (S568). For example, the exchange processing unit 133 may transmit a discount command including the number of points to be used to the POS unit 114. As a result, the POS unit 114 may perform the discount according to the number of points. The completion data transmission unit 134 generates completion data including brand information and the number of points used, encrypts the completion data using a key held in the key storage 115, and encrypts the encrypted completion data as a mobile device It transmits to 20 (S569).

  The completion data transfer unit 233 of the mobile device 20 receives the completion data from the ePOS 10, and transfers the completion data to the server 30 (S570).

  The completion data acceptance unit 335 of the server 30 receives the completion data, decodes the completion data (S571), and invalidates the token (S572). Completion data accepting unit 335 generates exchange data including brand information and the number of points used, both of which are included in the completion data, stores the exchange data in exchange database 343, and corresponds to the user ID in reward database 342. The number of points used is subtracted from the number of points (S573). The exchange data transmission unit 336 transmits the exchange data to the mobile device 20 (S574).

  The exchange data receiving unit 234 of the mobile device 20 receives the exchange data, and subtracts the number of used points included in the exchange data from the number of points held in the reward storage 242 (S575).

  As mentioned above, since the mobile device 20 transfers transaction data, tokens and completion data between the POS 10 and the server 30, the POS 10 needs to be connected with a wide area network such as the Internet to communicate with the server 30 Absent. Therefore, the security problems caused by connecting to the Internet can be reduced for the POS 10. In addition, stores equipped with POS 10 do not need to be equipped with communication facilities. The transaction system according to the present embodiment is applicable to a stand-alone store that does not have a communication facility.

== Modifications ==
In the present embodiment, the transaction system includes a single ePOS 10, but it is needless to say that a plurality of ePOSs 10 may be provided.
Furthermore, although the transaction system includes a single mobile device 20 in the present embodiment, a plurality of mobile devices 20 may be connected to the ePOS 10. In this case, the ePOS 10 may calculate the distance to each of the mobile devices 20, transmit connection information only to the closest mobile device 20, and establish a session only with the closest device. The ePOS 10 may transmit connection information only when the distance is equal to or less than a predetermined value.

  Furthermore, in the present embodiment, the ePOS 10 includes the Bluetooth (registered trademark) unit 107 that can communicate using Bluetooth (registered trademark) LE technology, but the ePOS 10 is not the Bluetooth (registered trademark) unit 107 but another A wireless communication unit may be provided that can communicate using wireless communication technology. In the wireless communication unit, it is preferable to use lightweight communication technology.

  Furthermore, although ePOS 10 is realized by a single computer device, ePOS 10 may be realized by a plurality of devices. For example, the ePOS 10 may be implemented by a legacy POS device and a reward device. The reward device is connected to the legacy POS device, can control the legacy POS device, and transmits / receives data to / from the legacy POS device. The reward device may be a computer including a CPU, a memory, a storage device, and a wireless communication unit, and the functions other than the POS unit 114 described in the present embodiment may be realized by the reward device. This makes it possible to use a legacy POS device that does not have a communication unit for rewarding users in the method described in the present embodiment.

  Furthermore, although a smartphone device is assumed as the mobile device 20 in the present embodiment, the mobile device 20 may be any portable device that can wirelessly communicate with both the ePOS 10 and the server 30. For example, the mobile device 20 may be a mobile phone having no touch panel display or a notebook computer.

  Furthermore, although a point of sale device is assumed as a transaction device in the present embodiment, other devices related to transactions may be assumed. For example, a vending machine may be used instead of the ePOS 10.

  Furthermore, in the present embodiment, the mobile device 20 stores the number of points in the reward storage 242 and the server 30 stores the number of points in the customer database 342, but the mobile device 20 and / or the server 30 stores the number of points. It may not be stored, and the number of points may be calculated from transaction data and exchange data.

  Furthermore, in the present embodiment, the number of points to be given to the user is calculated according to, for example, the purchase amount, but the transaction data may be data not related to an economical transaction. Points may be awarded to the user for the fact that they are connected.

  Furthermore, in the present embodiment, the exchange request transmission unit 231 first checks whether the user wants to use points, but the exchange request transmission unit 231 may automatically execute reward processing.

  The transaction data may further include information on the store or ePOS 10, such as inventory information. Thus, the server 30 can obtain inventory information using the mobile device 20 of the customer, using the reward as a compensation. Therefore, acquisition of inventory information from the ePOS 10 is facilitated. This is particularly effective when a vending machine is used instead of the ePOS 10. By using the connection capability to the wide area network such as the Internet which the mobile device 20 of the customer has, inventory information can be easily acquired from the vending machine without connecting the vending machine to the wide area network.

  As noted above, while the description of the embodiments of the present invention has been given, the above-described embodiments are intended to facilitate an understanding of the present invention, and the present invention is embodied herein. It should not be construed as limited to The present invention can be modified and improved without departing from the scope of the present invention, and equivalents of the present invention are also encompassed by the present invention.

10 POS
Reference Signs List 20 mobile device 30 server 111 session establishment unit 112 compensation unit 113 exchange unit 114 POS unit 115 key storage 121 reward request reception unit 122 transaction data acquisition unit 123 reward generation unit 124 transaction data transmission unit 131 token reception unit 132 token authentication unit 133 Exchange processing unit 134 Completion data transmission unit 211 Session establishment unit 212 Compensation unit 213 Exchange unit 221 Remuneration request transmission unit 222 Transaction data transfer unit 223 Remuneration data reception unit 231 Exchange request transmission unit 232 Token transfer unit 233 Completion data transfer unit 234 Exchange data Reception unit 241 Transaction storage 242 Remuneration storage 243 Exchange storage 311 Remuneration unit 312 Exchange unit 321 Transaction data reception unit 3 2 transaction data authentication portion 323 reward data transmission unit 331 exchange request receiving unit 332 exchanging authentication unit 333 token generation unit 334 token transmission unit 335 completes the data reception unit 336 exchange data transmission unit 341 transaction database 342 customer database 343 switching database 344 Key Storage

Claims (10)

A method for providing rewards to users,
Sending data about the user from the mobile device to the transaction device;
Sending from the transaction device to the mobile device transaction data relating to a transaction performed in the transaction device;
Forwarding the transaction data to a server by the mobile device;
Authenticating the transaction data at the server;
Sending reward data to the mobile device indicating that the reward has been granted to the user if the transaction data is authenticated;
Storing reward data on the mobile device.   The method of claim 1, further comprising storing the transaction data on the mobile device.   The method of claim 2, wherein the transaction data may include inventory data. The transaction data is encrypted by the transaction device,
The method of claim 1, wherein the server decrypts the transaction data and authenticates the transaction data. The transaction device and the server hold a common key,
The transaction device encrypts the transaction data using the key;
5. The method of claim 4, wherein the server decrypts the transaction data using the key. Generating reward data at the mobile device based on the transaction data prior to the transaction data transfer step;
Temporarily storing the reward data on the mobile device;
The method of claim 1, further comprising: permanently storing the reward data on the mobile device after the step of transmitting certified reward data from the server to the mobile device. Sending exchange data from the mobile device to the server;
Authenticating the exchange data at the server;
Generating the token according to the exchange data at the server if the exchange data is authenticated;
Sending the token from the server to the mobile device;
Forwarding the token to the transaction device by the mobile device;
Performing the process of the exchange at the transaction device. Sending completion data from the transaction device indicating completion of the exchange by the transaction device;
Forwarding the completion data to the server by the mobile device;
Invalidating the token by the server;
Sending the completion data from the server to the mobile device. A system for providing compensation to a user, the system comprising a transaction device, a mobile device and a server,
The mobile device includes a reward request transmission unit for transmitting data about the user to the transaction device,
The transaction apparatus includes a transaction data transmission unit that transmits transaction data related to a transaction performed in the transaction apparatus to the mobile apparatus.
The mobile device includes a transaction data transfer unit for transferring the transaction data to the server,
The server is a transaction authentication unit that authenticates the transaction data, and a reward data transmission unit that transmits, when the transaction data is certified, reward data indicating that the reward is given to the user, to the mobile device. And, and
The system wherein the mobile device receives the reward data from the server and stores the reward data in the mobile device. A reward request transmission unit that transmits data on the user to the transaction apparatus;
A transaction data transfer unit for transferring transaction data related to a transaction performed in the transaction apparatus from the transaction apparatus to a server;
A reward data receiving unit that receives reward data indicating that the reward is given to the user, and the reward data is a reward data receiving unit that is authenticated by the server;
A reward data receiving unit that receives the reward data from the server and stores the reward data in the mobile device.

Images