JP7212840B2 - Information processing device, information processing method and program - Google Patents

Description

The present invention relates to an information processing device, an information processing method, and a program.

In Patent Document 1, by reading a medium that records personal information such as a member's card and communicating with a server that manages information on public utility charges, it is possible to determine whether or not there is uncollected charge data for a user specified by the medium. A system for confirming is disclosed.

JP 2002-086865 A

The system described in Patent Literature 1 issues a bill when there is uncollected charge data. However, this system requires access to an external server to perform personal authentication when issuing a bill, which complicates the system configuration.

SUMMARY OF THE INVENTION The present invention has been made in view of the above problems, and provides an information processing apparatus, an information processing method, and a program capable of notifying customers of information related to bills without accessing an external server. With the goal.

According to one aspect of the present invention, an identification unit that identifies a customer in the store, and an acquisition unit that acquires payment history information including the type of the first invoice for which the customer has paid and the payment date of the price. a prediction unit that predicts the type and payment deadline of the second invoice to be paid based on the payment date trend for each type in the payment history information of the customer; and and a notification unit that notifies the customer of the type and payment deadline .

According to another aspect of the present invention, the steps of identifying a customer in the store and acquiring payment history information including the type of first invoice paid by the customer and the date of payment of the price. predicting the type and payment term of the second bill to be paid based on the tendency of the payment date for each of the types in the payment history information of the customer; and the type of the second bill. and notifying the customer of the payment deadline .

According to still another aspect of the present invention, a computer stores payment history information including the step of identifying a customer in the store and the type of the first invoice for which the customer has already paid and the date of payment of the price. predicting the type and payment term of the second bill to be paid based on the tendency of the payment date for each of the types in the payment history information of the customer; and notifying said customer of said type of document and said payment deadline .

According to the present invention, bill information can be notified to customers without accessing an external server.

It is a block diagram of a store system in a 1st embodiment. 1 is an overview diagram of a POS terminal in the first embodiment; FIG. 1 is a block diagram of a POS terminal in the first embodiment; FIG. It is a figure which shows an example of the customer information in 1st Embodiment. It is a figure which shows an example of payment history information in 1st Embodiment. It is a flow chart showing operation of a store system in a 1st embodiment. 4 is a sequence chart representing the operation of the store system in the first embodiment; FIG. 4 is a diagram showing an example of display of information on bills in the first embodiment; FIG. 4 is a flow chart showing the operation of the POS terminal in the first embodiment; It is a block diagram of a store system in a 2nd embodiment. It is a sequence chart showing operation of a store system in a 2nd embodiment. FIG. 11 is a diagram showing an example of display of information on bills in the second embodiment; It is a block diagram of a store system in a 3rd embodiment. It is a figure which shows an example of purchase history information in 3rd Embodiment. It is a sequence chart showing operation of a store system in a 3rd embodiment. It is a figure which shows an example of a display of the information which proposes product purchase in 3rd Embodiment. FIG. 12 is a block diagram of an information processing system according to a fourth embodiment; FIG. It is a sequence chart showing operation of an information processing system in a 4th embodiment. FIG. 11 is a block diagram of an information processing device according to a fifth embodiment; FIG.

Hereinafter, embodiments of the present invention will be described with reference to the drawings.

[First Embodiment]
FIG. 1 is a block diagram of a store system 1 according to this embodiment. A store system 1 is installed in a retail store, restaurant, service providing office, service counter, etc., and includes a POS (Point Of Sales) terminal 10, a store server 11, a wireless LAN (Local Area Network) 12, and a wired LAN 13. processing system.

The POS terminal 10 functions as an information processing device and is used for accounting processing of charges for products or services and settlement processing for various charges. The POS terminal 10 may be a cash register terminal primarily used by store clerks, or a self-checkout terminal or multi-function terminal primarily used by customers. The POS terminal 10 is provided, for example, at each checkout counter in a store. The number of POS terminals 10 is not particularly limited, and can be arbitrarily installed according to the scale of the store. The POS terminal 10 constitutes a POS system together with the store server 11 .

The store server 11 is provided, for example, in the backyard of the store and connected to a plurality of POS terminals 10 via a wired LAN 13 . The store server 11 manages various information required for store operation, such as product information, inventory information, order information, display information, sales results, customer information, and employee information of products sold at the store. That is, the store server 11 has a function as a POS server. The store server 11 may be a computer system including a CPU (Central Processing Unit), memory, communication interface, display, keyboard, and the like. The wireless LAN 12 is typically a wireless communication base station conforming to the WiFi communication standard, and is capable of wireless communication with the POS terminal 10 inside the store.

FIG. 2 is an overview diagram of the POS terminal 10 in this embodiment. The POS terminal 10 includes a main unit 100 , an operator display 110 , a customer display 120 , a scanner 130 , a keyboard 140 , a printer 150 , a cash drawer 160 , an NFC (Near Field Communication) reader 170 and a card processor 180 . Main unit 100 is configured by a computer system including a CPU, memory, and the like.

Operator display 110 is provided on top of main unit 100 . Operator display 110 is used by operators such as store clerks, salespeople, and workers. Operator display 110 includes a display using a liquid crystal or an organic light-emitting device, and a touch panel provided on the display. The customer display 120 is provided on the back side of the operator display 110 , and the display surface of the customer display 120 faces in the opposite direction to the display surface of the operator display 110 . Like the operator display 110, the customer display 120 includes a display and a touch panel, and can be operated by the customer.

The imaging unit 123 is provided on the upper part of the customer display 120 and is capable of imaging a customer's face image. In addition, the imaging unit 123 may acquire not only the customer's face image but also images such as iris and fingerprint as biometric information.

The scanner 130 can optically read bar codes, QR codes (registered trademark), and the like attached to products, cards, and documents. Scanner 130 shown in FIG. 2 is detachable from main unit 100 , but may be fixed to main unit 100 . For example, a transparent window may be embedded in the housing of main device 100, and scanner 130 may be provided inside the window.

Keyboard 140 is provided on the upper portion of main device 100 and includes numeric keys, keys representing transaction types, and the like. The operator can use the scanner 130 to read the bar code of the product and operate the keyboard 140 to execute desired transaction processing. A printer 150 is connected to the main device 100 and can print receipts, invoices, and the like. Printer 150 shown in FIG. 2 is detachably connected to main unit 100 as a peripheral device, but may be provided as part of main unit 100 . Cash drawer 160 is provided at the bottom of main unit 100 and can accommodate banknotes and coins. Although not shown, an automatic change mechanism that automatically calculates and dispenses change may be provided.

The NFC reader 170 uses short-range wireless communication to communicate with a card or terminal owned by a customer, and can read payment information and authentication information from the card or terminal. The card processing unit 180 is connected to the main unit 100 and has a card reader for reading information from a card-shaped medium such as a credit card, and an operation button for inputting a personal identification number. The NFC reader 170 and the card processing unit 180 are used not only for payment processing of the product price, but also for acquiring authentication information other than biometric information.

FIG. 3 is a block diagram of the POS terminal 10 according to this embodiment. The POS terminal 10 includes a CPU (Central Processing Unit) 101, a ROM (Read Only Memory) 102, a RAM (Random Access Memory) 103, a HDD (Hard Disc Drive) 104, an audio processing section 105, and a wireless I/F (Interface) 107. , LAN I/F 108 , operator display 110 , customer display 120 , NFC reader 170 and card processing unit 180 . Each unit described above is interconnected via a bus 190 .

The CPU 101 controls the overall operation of the POS terminal 10 according to a predetermined application program. The ROM 102, like a mask memory or a non-volatile memory, continues to retain its memory contents even after the power is turned off. The ROM 102 is written with a boot program and the like when the power is turned on. A RAM 103 is used as a work area for the operation of the CPU 101 . The HDD 104 can store the aforementioned application programs, operating system, database for commercial transactions, customer information, and the like.

The audio processing unit 105 includes a digital/analog conversion circuit that converts audio data into an analog signal, and an amplifier circuit that amplifies the analog signal and drives a speaker. The voice processing unit 105 can output not only guide voices related to the operation of the POS terminal 10 but also music, warning sounds, and the like.

The wireless I/F 107 includes a transmitting/receiving circuit and an antenna for wireless LAN communication, and is capable of wireless communication with the wireless LAN 12 of the shop server 11 . Also, the wireless I/F 107 may wirelessly communicate with a terminal owned by a customer. LAN I/F 108 is a wired network interface and is connected to store server 11 by a network cable.

Operator display 110 includes touch panel 111 and display 112 . The display 112 is typically a liquid crystal display or an organic light emitting display, and includes driving circuitry and image processing circuitry. The touch panel 111 includes a touch sensor that detects capacitance change or resistance change. The customer display 120 also has a touch panel 121 and a display 122 in the same manner. The customer display 120 is further provided with an imaging unit 123 . The imaging unit 123 includes an area sensor such as a CMOS (Complementary Metal Oxide Semiconductor) sensor or a CCD (Charge Coupled Device) sensor, an analog/digital conversion circuit, and an image processing circuit.

The scanner 130 includes a CMOS sensor or CCD sensor, an LED (Light Emitting Diode) light source, an analog/digital conversion circuit, and an image processing circuit. The CMOS sensor and CCD sensor may be line sensors or area sensors.

The keyboard 140 is typically composed of a plurality of switches having electrical contacts, but may be virtual switches displayed on a touch panel. The printer 150 includes a roll paper ejection mechanism, an inkjet mechanism, and a drive circuit. The cash drawer 160 has an electronic lock driven by an electromagnetic solenoid, and the electronic lock can be opened and closed by commands from the CPU 101 .

The NFC reader 170 includes a transmission/reception antenna, a high-frequency circuit, and a decoding circuit, and transmits/receives data to/from the card, tag, and mobile terminal 15 . Note that the NFC reader 170 may perform wireless power supply. The card processing unit 180 includes a card reader 181 and operation buttons 182 . A card reader 181 reads information from a magnetic stripe or an IC chip. Operation buttons 182 include numeric keys and symbol keys for entering a personal identification number.

Note that the hardware configuration shown in FIG. 3 is an example, and devices other than these may be added, and some devices may not be provided. Also, some devices may be replaced by other devices having similar functions. Furthermore, part of the functions of this embodiment may be provided by another device via a network, and the functions of this embodiment may be implemented by being distributed to multiple devices. For example, the HDD 104 may be replaced with an SSD (Solid State Drive) using semiconductor memory, or may be replaced with a cloud storage.

Next, information stored in the store server 11 will be described with reference to FIGS. 1, 4 and 5. FIG. As shown in FIG. 1, the shop server 11 in this embodiment comprises a customer information database 11a and a payment history information database 11b. Note that the database provided in the store server 11 is not limited to that shown in FIG. Also, the data items and data contents shown in FIGS. 4 and 5 are merely examples, and the present invention is not limited to these.

FIG. 4 is a diagram showing an example of information stored in the customer information database 11a in this embodiment. The customer information is, for example, information registered in advance in the procedure for issuing a store membership card to the customer, and it is preferable that the customer's consent to the purpose of use of the customer information has been obtained. Here, customer ID, face image, face feature amount, name, etc. are exemplified as data items of customer information. For example, the customer with the customer ID "0001" has a facial feature amount of "[facial feature amount D1]" and a name of "[name N1]". It should be noted that the facial feature amount may be, for example, an amount indicating facial features such as the positions of characteristic parts such as eyes, nose, mouth, and ears. Known extraction techniques such as SIFT (Scale-Invariant Feature Transform), SURF (Speeded up robust features), and ORB (Oriented FAST and Rotated Brief) can be used as methods for extracting facial features.

FIG. 5 is a diagram showing an example of information stored in the payment history information database 11b in this embodiment. Here, a customer ID, an invoice item, a payment date, a payment amount, etc. are exemplified as data items of the payment history information. According to FIG. 5, it can be seen that the customer with the customer ID “0001” made payments for three types of expense items (water charge/electricity charge/gas charge) in each month from July to September 2017. .

Next, operations and effects of the store system 1 according to the present embodiment will be described with reference to FIGS. 6 to 9. FIG.

First, the operation of the store system 1 in this embodiment will be briefly described. FIG. 6 is a flow chart showing the operation of the store system 1 in this embodiment.

When the store system 1 identifies a person who has visited the store based on a predetermined authentication method (step S11), it acquires the bill payment history of the identified person from the database it holds (step S12).

Next, the store system 1 analyzes the payment history acquired in step S12, and predicts/specifies the bill payment date and bill payment deadline of the person (step S13). For example, if five payment histories related to electricity charges are analyzed and the past payment dates are the 25th, 27th, 30th, and 31st, the store system 1 selects the 31st, which is the latest date. Predict payment date. In addition, if the payment history includes information on the payment due date of the bill (for example, the last day of each month), the store system 1 can also specify the date of the payment due date of the bill.

Next, the store system 1 determines the payment date or a predetermined period before the payment due date as the notification period for the bill information (step S14). It is possible to arbitrarily select which of the payment date and the payment deadline should be used as the reference date in setting the notice period. For example, if the payment date is earlier than the payment due date, the notification period can be set to a predetermined period before the payment date.

Then, the store system 1 determines whether or not the latest payment date in the payment history is outside the notification period (step S15). Here, if the store system 1 determines that the most recent payment date is outside the notification period (step S15: YES), the store system 1 sends information on the invoice to the person identified in step S11. notification (step S16), and the process of FIG. 6 is terminated.

On the other hand, if the store system 1 determines that the most recent payment date is within the notification period (step S15: NO), the person specified in step S11 corresponds to a person who does not require notification. 1 ends the processing of FIG.

The above-described operation of FIG. 6 is performed, for example, as follows, by cooperation between the POS terminal 10 and the store server 11 that constitute the store system 1. FIG. FIG. 7 is a sequence chart showing the operation of the store system 1 in this embodiment. It is assumed that a customer puts desired products in a shopping basket at a store and goes to the POS terminal 10 for checkout. When the POS terminal 10 detects that the customer has approached the terminal for checkout, the imaging unit 123 captures the face image of the customer (step S101).

Next, the POS terminal 10 transmits the image signal to the shop server 11 (step S102). Next, the store server 11 performs image processing on the image signal received from the POS terminal 10, and then extracts facial features (step S103). In the shop server 11, the customer's face image and face feature amount are registered in advance in the customer information database 11a (see FIGS. 1 and 4). Therefore, the store server 11 identifies the customer by searching the customer information database 11a for the customer having the facial feature amount closest to the extracted facial feature amount (step S104).

When the customer is identified (specified) by the image recognition process, the shop server 11 searches the payment history information database 11b for the customer's bill payment history (step S105), (step S106). On the other hand, in parallel with the processing of steps S103 to S106 in the shop server 11, the POS terminal 10 reads the barcode of the product in the shopping basket or the barcode of the invoice received from the customer according to the operation by the store clerk. is read by the scanner 130 (step S107), the process proceeds to step S108.

Next, the POS terminal 10 refers to the search result and determines whether or not the payment history for the bill of the customer at the checkout counter exists in the payment history information database 11b (step S108). Here, if the POS terminal 10 determines that there is a payment history for the invoice (step S108: YES), it analyzes the payment history (step S109) and determines the reminder information notification period for the customer. (Step S110). On the other hand, if the POS terminal 10 determines that there is no bill payment history (step S108: NO), the process proceeds to step S111.

The “reminder information” in the present embodiment means information for reminding/confirming the payment of the invoice to the customer, and is an example of information related to the invoice. Details of the processing of steps S109 and S110 will be described later.

Next, when the POS terminal 10 executes settlement processing for the product and the invoice (step S111), it transmits purchase information of the product and payment information for the invoice to the store server 11 (step S112). Store server 11 registers the purchase information and payment information received from POS terminal 10 in the database as purchase history information and payment history information, respectively (step S113).

Next, the POS terminal 10, in parallel with the processing of step S113 in the shop server 11, performs control processing regarding notification of reminder information. First, the POS terminal 10 determines whether the current date and time are within the notification period determined in step S110 (step S114). If the POS terminal 10 determines that the current date is within the notification period (step S114: YES), the process proceeds to step S115.

On the other hand, if the POS terminal 10 determines that the current date and time are not within the notification period (step S114: NO), the process of FIG. 7 ends. Note that the corresponding case of "the current date and time is not within the notification period" includes not only the case where the current date and time is before or after the notification period, but also (A) the processing of step S110 is performed because there is no payment history. (B) In the analysis of the payment history, it is determined that the current month is not the payment month.

Next, the POS terminal 10 determines the most recent payment date for the bill based on the payment history and settlement processing details (step S115). This is because the "most recent payment date" may change depending on whether or not the invoice has been paid during the above-described payment processing (step S111). For example, when settlement processing is performed only for products, the latest payment date is the last payment date in the customer's payment history. On the other hand, if the invoice is paid in the settlement process, the current date is the most recent payment date.

Next, the POS terminal 10 determines whether or not the latest payment date is outside the notification period (step S116). Here, if the POS terminal 10 determines that the latest payment date is outside the notification period (step S116: YES), the invoice reminder information is printed on the receipt issued upon completion of the payment process. and output (step S117). On the other hand, if the POS terminal 10 determines that the latest payment date is within the notification period (step S116: NO), the customer has already paid and there is no need to notify the reminder information. The processing of 7 ends.

FIG. 8 is a diagram showing an example of display of information on bills in this embodiment. Here, an example is shown in which the reminder information regarding the invoice is displayed together with the product transaction information on the receipt issued upon completion of the settlement process. In the lower area of the receipt, the title "Notice to Customers" and a message reminding and confirming the payment of the bill to the customer ("Have you already paid the bill below? Please contact our checkout counter. Please use it.") and a list of invoices expected to be paid by the customer and information on the date of the last payment. As shown in FIG. 8, the reminder information preferably includes at least one of bill type (expenditure item), bill payment timing, and payment history information.

FIG. 9 is a flow chart showing the operation of the POS terminal 10 in this embodiment. This processing is an example of processing corresponding to steps S109 and S110 in FIG. 7 described above.

The POS terminal 10 classifies the payment history for each expense item (step S201), and then extracts the payment history for the same expense item (step S202). Next, the POS terminal 10 determines whether or not there are multiple extracted payment histories (step S203). If the POS terminal 10 determines that there are multiple payment histories (step S203: YES), the process proceeds to step S204. On the other hand, if the POS terminal 10 determines that there are no multiple payment histories (step S203: NO), the process proceeds to step S208.

In step S204, the POS terminal 10 analyzes the payment history of the same expense item and predicts payment trends. Specifically, monthly or yearly payment cycle (once a month / once every two months / four times in January, June, August, October, etc.), payment date date distribution (between 1st and 5th of each month/between 25th and 31st of each month, etc.) as payment trends.

Next, the POS terminal 10 determines whether or not the current month corresponds to the payment month based on the predicted payment trend (step S205). Here, if the POS terminal 10 determines that the current month corresponds to the payment month (step S205: YES), the process proceeds to step S206. On the other hand, when the POS terminal 10 determines that the current month does not correspond to the payment month (step S205: NO), the processing proceeds to step S210 because the billing expense item does not require notification.

In step S206, the POS terminal 10 determines whether or not payment dates are distributed over a plurality of dates in a plurality of payment histories for the same expense item. If the POS terminal 10 determines that the payment dates are distributed over a plurality of dates (step S206: YES), the process proceeds to step S207. On the other hand, when the POS terminal 10 determines that the payment dates are the same date (step S206: NO), the process proceeds to step S208.

In step S207, the POS terminal 10 predicts the date of the latest payment among the plurality of payment histories as the date of payment. For example, if the analysis of the 5 payment histories obtained shows a payment trend that is distributed once a month and the payment dates are on the 25th, 27th, 30th, and 31st, The POS terminal 10 predicts that the next payment date will be the 31st, the latest date. Other dates such as the earliest date may be used as the payment date.

On the other hand, in step S208, the POS terminal 10 predicts the payment date of one payment history as a future payment date. For example, if the payment history has only one payment date "27th", the POS terminal 10 predicts that the payment date will be the 27th.

In step S209, the POS terminal 10 sets a predetermined period before the predicted payment date or payment deadline as the notification period. For example, by analyzing three payment histories, the POS terminal 10 obtains a common payment trend in which the payment date is once a month on the 27th. The period can be set to a predetermined period (for example, 10 days) earlier than 27 days. The past payment date was, for example, the 31st, but if that date does not exist in the current month, the payment date is shifted forward to the last day of the current month, and the notification period is shifted forward, such as 10 days before the last day. do it. Alternatively, a predetermined period prior to the payment date may be set as the notice period, and the start date of the notice period may be arbitrarily earlier than the past payment date.

Then, the POS terminal 10 determines whether or not all classified expense items have been processed for the customer's payment history (step S210). Here, when the POS terminal 10 determines that all the expense items have been processed (step S210: YES), the process proceeds to step S111 in FIG. On the other hand, when the POS terminal 10 determines that all the expense items have not been processed (step S210: YES), the process returns to step S202.

As described above, according to the present embodiment, the POS terminal 10 issues receipts issued upon completion of payment processing for products and services at timing based on the customer's bill payment tendency predicted from the payment history. It can be used to notify customers of reminder information. As a result, the customer can easily notice the presence of the bill to be paid in the near future, thereby preventing the customer from forgetting to pay and improving customer satisfaction. In addition, since there is no need to access an external server such as a public institution or a company that actually manages invoice information, the system does not become complicated. Furthermore, since a local database installed in the store is sufficient, there is also the advantage of preventing the spread of personal information.

Further, the POS terminal 10 can identify the customer based on the customer's face image captured at the checkout counter, that is, the biometric information acquired about the customer. A customer can be identified without requiring an input operation from the customer or a medium on which customer information is recorded.

Also, the POS terminal 10 can set a payment notice period based on the payment tendency obtained by analyzing the payment history information, and output reminder information during the payment notice period. As a result, it is possible to remind and confirm the payment of the bill to the customer at an appropriate timing according to the customer's payment cycle.

Further, as shown in the flowchart of FIG. 9, the POS terminal 10 can set the payment notification period for each bill type (expenditure item). This makes it possible to notify at appropriate timing for each bill type (expenditure item).

Further, as shown in the flowchart of FIG. 9, the POS terminal 10 can set whether to output reminder information for each type of bill. This makes it possible to provide notifications limited to only the types (expenditure items) of bills that are expected to be paid in the near future.

Also, the POS terminal 10 can predict the payment due date for the invoice based on the payment history information and the type of the invoice, and set a predetermined period before the payment due date as the payment notification period. This allows for notification during periods when payment is not expected to be due.

Also, the POS terminal 10 can output reminder information on a receipt issued with the payment of goods or services. As a result, the customer can visually recognize the reminder information when confirming the details of the transaction printed on the receipt, thereby enabling effective notification. In addition, since the receipt is a medium managed by the customer after the transaction is completed, it is possible to prevent private information from being known to other customers.

[Second embodiment]
Next, the store system 2 in this embodiment will be described. Reference numerals common to the reference numerals given in the drawings of the first embodiment indicate the same objects. In the following, descriptions of parts common to the first embodiment will be omitted, and descriptions will focus on configurations and operations that differ from the first embodiment.

FIG. 10 is a block diagram of the store system 2 in this embodiment. The store system 2 further includes an imaging device 14 . Also, the store server 11 is connected to the base station 20 via the communication network NW. A base station 20 is a node for public wireless communication, and is installed for each macrocell or microcell.

The imaging device 14 is, for example, a camera installed at the entrance of the store. Note that the imaging device 14 can be installed anywhere as long as it can capture the face image of the customer. For example, it may be installed on a store ceiling, a store parking lot, a checkout counter, or the like. The mobile terminal 15 is a wireless communication terminal such as a mobile phone, a smart phone, or a tablet computer owned and managed by the customer.

Next, actions and effects of the store system 2 according to the present embodiment will be described with reference to FIGS. 11 and 12. FIG. FIG. 11 is a sequence chart representing the operation of the store system 2 in this embodiment.
First, when the image pickup device 14 detects that the customer is positioned near the entrance of the store, the image pickup device 14 takes an image of the face of the customer (step S301).

Next, the imaging device 14 transmits an image signal to the store server 11 (step S302). Next, the store server 11 performs image processing on the image signal received from the POS terminal 10, and then extracts facial feature amounts (step S303). In the shop server 11, the customer's face image and face feature amount are registered in advance in the customer information database 11a. Therefore, the store server 11 identifies the customer by searching the customer information database 11a for the customer having the facial feature amount closest to the extracted facial feature amount (step S304).

Next, when the customer is identified (specified) by the image recognition process, the store server 11 searches the payment history for the invoice of the customer from the payment history information database 11b (step S305).

Next, the store server 11 determines whether or not the payment history for the bill of the customer at the checkout counter exists in the payment history information database 11b based on the search results (step S306). Here, if the store server 11 determines that there is a payment history for the invoice (step S306: YES), it analyzes the payment history (step S307) and sets a reminder information notification period for the customer. (Step S308), and the process proceeds to step S309. On the other hand, if the store server 11 determines that there is no payment history for the invoice (step S306: NO), the process of FIG. 11 ends.

In step S309, the store server 11 determines whether the current date and time are within the notification period set in step S308. If the store server 11 determines that the current date and time is within the notification period (step S309: YES), the process proceeds to step S310.

On the other hand, if the store server 11 determines that the current date and time are not within the notification period (step S309: NO), the process of FIG. 11 ends. Note that the corresponding case of "the current date and time is not within the notification period" includes not only the case where the current date and time is before or after the notification period, but also (A) the processing of step S308 is performed because there is no payment history. (B) the payment history analysis did not determine that the current month was not the payment month;

In step S310, the store server 11 determines whether or not the latest payment date is outside the notification period. In this embodiment, the payment date of the customer's last payment history corresponds to the most recent payment date. Here, if the store server 11 determines that the latest payment date is outside the notification period (step S310: YES), the store server 11 refers to the customer information, etc., and checks the mobile terminal 15 owned by the customer. is specified, and invoice reminder information is transmitted to the mobile terminal 15 via the communication network NW (step S311). Then, the mobile terminal 15 displays the reminder information received from the store server 11 on the screen (step S312). On the other hand, if the store server 11 determines that the latest payment date is within the notification period (step S316: NO), the process of FIG. 11 ends because notification of reminder information is unnecessary.

FIG. 12 is a diagram showing an example of display of information on bills in this embodiment. Here, an example is shown in which reminder information regarding bills is displayed on the screen of the portable terminal 15 owned by the customer. On the screen, the title "Notice to Mr. ○○" and a message reminding and confirming the payment for the bill to the customer ("Have you already paid for the bill below? You can pay, so please use it.") and a list of invoices expected to be paid by the customer and information on the date of the last payment. In addition, it is preferable that the payment history for the expense items of each bill can be referred to other than the previous payment.

As described above, according to the present embodiment, the shop server 11 can notify reminder information to the portable terminal 15 owned by the customer during the notification period based on the customer's bill payment tendency predicted from the payment history. Unlike the first embodiment, since the information is displayed on the mobile terminal 15 carried by the customer, it is possible to notify the customer not only at the time of payment for products but also at any timing such as when entering the store. In addition, since the mobile terminal 15 is a terminal managed by the customer, it is possible to prevent private information from being known to other customers.

[Third embodiment]
Next, the store system 3 in this embodiment will be described. Reference numerals that are common to the reference numerals given in the drawings of the first and second embodiments indicate the same objects. In the following, descriptions of portions common to the first and second embodiments will be omitted, and descriptions will focus on configurations and operations that differ from those of the first and second embodiments.

FIG. 13 is a block diagram of the store system 3 in this embodiment. As shown in FIG. 13, in the store system 3 in this embodiment, the store server 11 is provided with a purchase history information database 11c. As a result, the store system 3, in place of the payment history information on the bills, uses the past purchase history of the products or services stored in the purchase history information database 11c to provide This differs from the second embodiment in that information (hereinafter referred to as "recommendation information") is notified.

FIG. 14 is a diagram showing an example of information stored in the purchase history information database 11c in this embodiment. Here, customer ID, product name, product type, purchase date, purchase amount, etc. are exemplified as data items of the purchase history information. According to FIG. 14, it can be seen that the customer with the customer ID "0099" purchased the product A1 of the product type "drinking water" and the products B1 and B2 of the product type "rice" at the end of each month. .

Next, operations and effects of the store system 3 according to this embodiment will be described with reference to FIGS. 15 and 16. FIG. FIG. 15 is a sequence chart representing the operation of the store system 3 in this embodiment.
First, when the image pickup device 14 detects that the customer is positioned near the entrance of the store, the image pickup device 14 takes an image of the face of the customer (step S401).

Next, the imaging device 14 transmits the image signal to the shop server 11 (step S402). Next, the store server 11 performs image processing on the image signal received from the POS terminal 10, and then extracts facial features (step S403). In the shop server 11, the customer's face image and face feature amount are registered in advance in the customer information database 11a. Therefore, the store server 11 identifies the customer by searching the customer information database 11a for the customer having the facial feature amount closest to the extracted facial feature amount (step S404).

Next, when the customer is identified (specified) by image recognition processing, the store server 11 searches the customer's purchase history from the purchase history information database 11c (step S405).

Next, the store server 11 determines whether or not the purchase history of the customer who visited the store is in the purchase history information database 11c (step S406). Here, if the shop server 11 determines that there is a purchase history (step S406: YES), it analyzes the purchase history (step S407), and sets a notification period of recommendation information to the customer (step S408). ). Then, the process moves to step S409. On the other hand, if the store server 11 determines that there is no purchase history (step S406: NO), the process of FIG. 15 ends.

In step S409, the store server 11 determines whether the current date and time are within the notification period set in step S408. If the store server 11 determines that the current date and time is within the notification period (step S409: YES), the process proceeds to step S410.

On the other hand, if the store server 11 determines that the current date and time are not within the notification period (step S409: NO), the process of FIG. 15 ends. It should be noted that the relevant cases of "current date and time are not within the notification period" include not only cases where the current date and time are before or after the notification period, but also cases in which the processing of step S408 is not performed because there is no purchase history, and notification is made. A case where the period is not set is also included.

In step S410, the store server 11 determines whether or not the most recent purchase date is outside the notification period. In this embodiment, the purchase date in the customer's last purchase history corresponds to the most recent purchase date. Here, if the store server 11 determines that the most recent purchase date is outside the notification period (step S410: YES), the store server 11 refers to the customer information, etc., and is specified, and product recommendation information is transmitted to the portable terminal 15 via the communication network NW (step S411). Then, the portable terminal 15 displays the recommendation information received from the shop server 11 on the screen (step S412). On the other hand, if the shop server 11 determines that the most recent purchase date is within the notification period (step S410: NO), the process of FIG. 15 is terminated because notification of recommendation information is unnecessary.

FIG. 16 is a diagram showing an example of display of information suggesting product purchase in this embodiment. Here, an example is shown in which product recommendation information is displayed on the screen of the portable terminal 15 carried by the customer. On the screen, the title of "recommended product information", a message suggesting the purchase of the product to the customer ("Today, the following products are very affordable"), product images, product information such as bargain prices, etc. is displayed. The products and services included in the recommendation information are not limited to the products and services purchased by the customer in the past. For example, it may be advertisement information related to products of the same product type (category), products expected to be purchased at the same time, or arbitrary products recommended to be purchased by the store.

As described above, according to the present embodiment, when there is a product that the customer regularly purchases, the sales of the same/similar products and related products can be improved by notifying the recommendation information at an appropriate timing. and prevent loss of sales opportunities.

[Fourth embodiment]
Next, the information processing system 4 in this embodiment will be described. It should be noted that the same reference numerals as those given in the drawings of the first to third embodiments indicate the same objects. In the following, descriptions of portions common to the first to third embodiments will be omitted, and descriptions will focus on configurations and operations that are different from those of the first to third embodiments.

FIG. 17 is a block diagram of the information processing system 4 in this embodiment. The information processing system 4 includes a center server 40 and a plurality of store systems 1 . In this embodiment, a plurality of store systems 1 will be described as computer systems provided in affiliated stores such as "A store/B store of XX store". Note that the number of store systems 1 included in the information processing system 4 is not limited, and any number of store systems 1 can be connected to the center server 40 .

The center server 40 is connected to a plurality of store servers 11 via the communication network NW, manages sales data aggregated by the store servers 11, and can manage customer information, payment history information, purchase history information, and the like. . The center server 40 is composed of a computer system and can include a CPU, memory, communication interface, display, keyboard, and the like. In FIG. 17, the center server 40 has a customer information database 40a and a payment history information database 40b as databases. The customer information database 40a and the payment history information database 40b are the same databases as the customer information database 11a and the payment history information database 11b of the first embodiment, but differ in that information on a plurality of stores is centrally managed. ing. Note that the center server 40 may be composed of a plurality of servers such as a company server that manages stores, a server that manages customer information, and a server that manages credit information.

Next, actions and effects of the information processing system 4 in this embodiment will be described with reference to FIG. 18 . FIG. 18 is a sequence chart showing the operation of the information processing system 4 in this embodiment.

It is assumed that a customer puts desired products in a shopping basket at a store and goes to the POS terminal 10 for checkout. The POS terminal 10 reads card information such as a member's card or a credit card according to an operation by a store clerk or the like (step S501).

Next, the POS terminal 10 transmits the card information to the center server 40 via the store server 11 (step S502). Next, the center server 40 refers to the customer information database 40a based on the card information and identifies the customer (step S503).

When the customer is identified (specified) by image recognition processing, the center server 40 searches the payment history for the customer's invoice from the payment history information database 40b (step S504), (step S505). On the other hand, in parallel with the processing of steps S503 to S505 in the center server 40, the POS terminal 10 reads the barcode of the product in the shopping basket or the barcode of the invoice received from the customer according to the operation by the store clerk. is read by the scanner 130 (step S506). Then, the process moves to step S507.

In step S507, the POS terminal 10 refers to the search result and determines whether or not the payment history information database 40b has a payment history for the invoice of the customer at the checkout counter. Here, if the POS terminal 10 determines that there is a payment history for the invoice (step S507: YES), it analyzes the payment history (step S508) and determines the reminder information notification period for the customer. (Step S509). On the other hand, if the POS terminal 10 determines that there is no payment history for the invoice (step S507: NO), the process proceeds to step S510.

At step S510, the POS terminal 10 executes settlement processing for the product and bill. Then, the POS terminal 10 transmits the product purchase information and bill payment information to the center server 40 (step S511). Accordingly, the center server 40 registers the purchase information and payment information received from the POS terminal 10 in the database (step S512).

The POS terminal 10 performs control processing related to notification of reminder information in parallel with the processing of step S512 in the center server 40 . First, the POS terminal 10 determines whether or not the current date and time are within the notification period determined in step S509 (step S513). If the POS terminal 10 determines that the current date and time is within the notification period (step S513: YES), the process proceeds to step S514.

On the other hand, if the POS terminal 10 determines that the current date and time are not within the notification period (step S513: NO), the process of FIG. 18 ends. Note that the corresponding case of "the current date and time is not within the notification period" includes not only cases where the current date and time are before or after the notification period, but also (A) because there is no payment history, the processing of step S510 is performed. (B) the payment history analysis determined that the current month was not the payment month;

Next, the POS terminal 10 determines the most recent payment date for the bill based on the payment history and settlement processing details (step S514). This is because the "latest payment date" varies depending on whether or not the invoice has been paid in the above-described settlement processing (step S510). For example, when settlement processing is performed only for products, the latest payment date is the last payment date in the customer's payment history. On the other hand, if the invoice is paid in the settlement process, the current date is the most recent payment date.

Next, the POS terminal 10 determines whether or not the latest payment date is outside the notification period (step S515). Here, if the POS terminal 10 determines that the latest payment date is outside the notification period (step S515: YES), the reminder information for the invoice is added to the receipt issued upon completion of the payment process. Print and output (step S516). On the other hand, if the POS terminal 10 determines that the latest payment date is within the notification period (step S515: NO), the process of FIG. 18 is terminated because notification of reminder information is unnecessary.

As described above, the information processing system 4 in the present embodiment shares the payment history information on the center server 40, so that reminder information can be sent not only for each store but also for each region, affiliated store, affiliated group, etc. I can notify you. For example, if information is shared on an affiliated store basis, the customer can receive notifications at both affiliated stores near his/her home and near his company, thereby improving the service level.

[Fifth Embodiment]
FIG. 19 is a block diagram of the information processing device 50 in this embodiment. The information processing device 50 includes a specification unit 51 that specifies a customer, an acquisition unit 52 that acquires payment history information for the customer's bills, and a prediction unit that predicts bills to be paid based on the customer's payment history information. A unit 53 and an output unit 54 for outputting information on the bill. The information processing device 50 according to the present embodiment can notify the customer of information regarding bill payment without accessing an external server.

[Modified embodiment]
The present invention is not limited to the above-described embodiments, and can be modified as appropriate without departing from the gist of the present invention.

In the first embodiment described above, the case where the recommendation information is printed on a receipt has been described, but the output destination of the recommendation information is not limited to the receipt. For example, recommendation information can be displayed on the customer display 120 . Also, when paying for a product, only the fact that there is a charge item is displayed on the customer display 120 of the POS terminal 10, and the details are printed on the receipt only when there is an instruction from the customer on the customer display 120. - 特許庁Also good. When the information is displayed on the customer display 120, by restricting the display content of the information, it is possible to prevent private information from being known to other customers.

In the above-described second embodiment, a case has been described in which a customer is specified at the timing when the customer enters the store and the reminder information is notified to the mobile terminal 15. Not limited to store hours. For example, when the mobile terminal 15 detects that the mobile terminal 15 is approaching the store by GPS information or when the customer logs into the application provided by the store from the mobile terminal 15, the reminder information may be output to the mobile terminal 15. good.

Further, in the above-described embodiment, a case has been described in which a customer is specified by face authentication or acquisition of card information at a store, but the means for specifying a customer is not limited to these. For example, the store can use authentication information (including biometric information) stored in the mobile terminal 15 to identify the customer.

Further, in the above-described embodiment, a configuration has been described in which forgetting to pay is prevented by setting a predetermined period of time before the past payment date or payment deadline date as the notification period. However, notification may be made when the latest payment date or the payment deadline included in the payment history has passed. This allows notification only if the customer forgets to pay. Also, the content of the notification message may be changed depending on whether the current date is before or after the payment deadline.

A processing method in which a program for operating the configuration of the embodiment is recorded in a storage medium so as to realize the functions of the above-described embodiment, the program recorded in the storage medium is read out as a code, and the computer executes the program. included in the category. That is, a computer-readable storage medium is also included in the scope of each embodiment. Further, each embodiment includes not only the storage medium in which the above-described program is recorded, but also the program itself. Also, one or more of the components included in the above-described embodiments may be circuits such as ASICs, FPGAs, etc. configured to implement the functions of each component.

As the storage medium, for example, a floppy (registered trademark) disk, hard disk, optical disk, magneto-optical disk, CD (Compact Disk)-ROM, magnetic tape, nonvolatile memory card, and ROM can be used. In addition, the program is not limited to the one that executes the process by itself, which is recorded in the storage medium, but the one that operates on the OS (Operating System) in cooperation with other software and the function of the expansion board to execute the process. are also included in the scope of each embodiment.

The services realized by the functions of the above-described embodiments can also be provided to users in the form of SaaS (Software as a Service).

It should be noted that the above-described embodiments are merely examples of specific implementations of the present invention, and the technical scope of the present invention should not be construed to be limited by these. That is, the present invention can be embodied in various forms without departing from its technical concept or main features.

Some or all of the above-described embodiments can also be described as the following additional remarks, but are not limited to the following.

(Appendix 1)
an identification part that identifies a customer;
an acquisition unit that acquires payment history information for the customer's bill;
a prediction unit that predicts the bill to be paid based on the payment history information of the customer;
an output unit that outputs information about the invoice;
Information processing device.

(Appendix 2)
The identification unit identifies the customer based on biometric information acquired about the customer located in the store.
The information processing device according to appendix 1.

(Appendix 3)
The prediction unit sets a payment notice period based on the payment history information,
wherein the output unit outputs the information during the payment notification period;
The information processing device according to appendix 1 or 2.

(Appendix 4)
The prediction unit sets the payment notice period for each type of the bill.
The information processing device according to appendix 3.

(Appendix 5)
The prediction unit sets whether or not to output the information for each type of the bill.
The information processing device according to appendix 3.

(Appendix 6)
The prediction unit predicts a payment deadline for the invoice based on the payment history information and the type of the invoice, and sets a predetermined period prior to the payment deadline as the payment notification period.
The information processing device according to appendix 3.

(Appendix 7)
The output unit outputs the information to a receipt issued with payment for the product or service;
7. The information processing apparatus according to any one of Appendices 1 to 6.

(Appendix 8)
The information includes at least one of the expense item of the bill, the payment time for the bill, and the payment history information,
8. The information processing apparatus according to any one of Appendices 1 to 7.

(Appendix 9)
identifying a customer;
obtaining payment history information for the customer's bill;
predicting the bills to be paid based on the payment history information of the customer;
outputting information about the invoice;
An information processing method comprising:

(Appendix 10)
to the computer,
identifying a customer;
obtaining payment history information for the customer's bill;
predicting the bills to be paid based on the payment history information of the customer;
outputting information about the invoice;
program to run.

1, 2, 3 store system (information processing system)
4 information processing system 10 POS terminal (information processing device)
11 store server (information processing device)
12 Wireless LAN
13 Wired LAN
14 Imaging device 15 Mobile terminal 20 Base station 40 Center server 50 Information processing device 51 Identification unit 52 Acquisition unit 53 Prediction unit 54 Output unit 100 Main unit 101 CPU
102 ROMs
103 RAM
104 HDDs
105 Audio processing unit 107 Wireless I/F
108 LAN I/F
110 operator displays 111, 121 touch panels 112, 122 display 120 customer display 123 imaging unit 130 scanner 140 keyboard 150 printer 160 cash drawer 170 NEC reader 180 card processing unit 181 card reader 182 operation buttons

Claims (8)

an identification unit that identifies a customer in the store ;
an acquisition unit that acquires payment history information including the type of the first invoice paid by the customer and the date of payment of the price;
a prediction unit that predicts the type and payment deadline of the second bill to be paid based on the tendency of the payment date for each type in the payment history information of the customer;
a notification unit that notifies the customer of the type and payment deadline of the second bill;
Information processing device. The identification unit obtains biometric information from the customer at the store and identifies the customer based on biometric authentication using the biometric information.
The information processing device according to claim 1 . The prediction unit predicts the payment due date for each type of the second invoice based on the tendency of the payment date for each type of the first invoice and the type of the second invoice. , automatically setting a predetermined period prior to the payment deadline as a payment notice period for the second invoice ;
The notification unit notifies the type and the payment deadline of the second invoice in the payment notification period.
The information processing apparatus according to claim 1 or 2. The prediction unit determines whether notification of the type of the second invoice and the payment deadline is necessary based on the current time and the payment notification period .
The information processing apparatus according to claim 3. The notification unit outputs a receipt stating the type and the payment deadline of the second invoice when the payment for the product or service is completed .
The information processing apparatus according to any one of claims 1 to 4 . The notification unit further notifies the payment history information of the first invoice whose type is the same as that of the second invoice .
The information processing apparatus according to any one of claims 1 to 5 . a computer identifying a customer in the store ;
a step in which the computer acquires payment history information including the type of the first invoice paid by the customer and the payment date of the payment ;
a step in which the computer predicts the type and due date of the second bill to be paid based on the trend of the payment date for each type in the payment history information of the customer;
said computer notifying said customer of said type and said payment due date of said second invoice;
An information processing method comprising: to the computer,
identifying customers in the store ;
a step of obtaining payment history information including the type of the first invoice paid by the customer and the payment date of the price ;
predicting the type and payment due date of the second bill to be paid based on the trend of the payment date for each type in the payment history information of the customer;
informing the customer of the type and the due date of the second invoice;
program to run.

Images