Information terminals and their programs

The portable information terminal system allows users to easily access and be notified of store promotions at their favorite stores, enhancing shopping decisions by providing remote access to sales promotion information.

JP7844263B2Active Publication Date: 2026-04-13TOSHIBA TEC KK
View PDF 5 Cites 0 Cited by

Patent Information

Authority / Receiving Office
JP · JP
Patent Type
Patents
Current Assignee / Owner
TOSHIBA TEC KK
Filing Date
2022-06-03
Publication Date
2026-04-13

AI Technical Summary

Technical Problem

Users of information terminals cannot easily access sales promotion information from multiple stores before entering a store, limiting their ability to determine which store to shop at based on available promotions.

Method used

A portable information terminal with a setting unit to designate favorite stores, a first acquisition unit to gather data on store promotions, and a notification unit to inform users of relevant promotions via wireless communication, utilizing a server system and POS system for data management and notification.

Benefits of technology

Enables users to grasp store promotion information remotely, allowing informed shopping decisions based on available sales promotions at their favorite stores.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 0007844263000001
    Figure 0007844263000001
  • Figure 0007844263000002
    Figure 0007844263000002
  • Figure 0007844263000003
    Figure 0007844263000003
Patent Text Reader

Abstract

To provide an information terminal and a program thereof that enable a user to easily grasp information or the like related to sales promotions of a store using the information terminal before entering the store.SOLUTION: In a self-product registration system including an information terminal that accesses a server system using a mobile phone communication network, a server system that enables two-way data communication through a network that uses Internet protocols, and a POS system, an information terminal 40 includes a setting unit 411, a first acquisition unit 412, and a notification unit 414. The setting unit 411 sets a user's favorite store from among a plurality of stores. The first acquisition unit 412 acquires data indicating whether each of a plurality of stores has information to be notified to consumers from a server by wireless communication. The notification unit 414 notifies the user on the basis of the data acquired by the first acquisition unit 412 when the user's favorite store has information that should be notified to the consumers.SELECTED DRAWING: Figure 8
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0002]

[0001] Embodiments of the present invention relate to an information terminal and a program thereof.

Background Art

[0002] A self-product registration system in which a customer inputs data necessary for registering purchased products using an information terminal such as a smartphone or a tablet terminal has been put into practical use in stores such as supermarkets. In this type of self-product registration system, when a customer uses an information terminal in a store, information related to sales promotion such as information on special offers in the store and information on coupons that can be used in the store is displayed on the display device of the information terminal, and a technique for enhancing the sales promotion effect is already known.

[0003] However, in order to obtain information related to store sales promotion from an information terminal, a customer has to go to the store. Therefore, it is not possible to determine the store to go shopping by grasping in advance information related to sales promotion of multiple stores on the information terminal.

Prior Art Documents

Patent Documents

[0004]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0005] The problem to be solved by the embodiments of the present invention is to enable a user of an information terminal used as a product registration terminal of a self-product registration system to easily grasp information related to sales promotion of the store on the information terminal before entering the store.

Means for Solving the Problems

[0006] In one embodiment, the information terminal is a portable information terminal for users to self-input data necessary for registering purchased items at a store. The information terminal comprises a setting unit, a first acquisition unit, and a notification unit. The setting unit sets the user's favorite stores from among multiple stores. The first acquisition unit acquires data from a server via wireless communication indicating whether or not each of the multiple stores has information that should be notified to the consumer. Based on the data acquired by the first acquisition unit, the notification unit notifies the user if their favorite store has information that should be notified to the consumer. [Brief explanation of the drawing]

[0007] [Figure 1] Figure 1 is a block diagram showing a schematic configuration of a self-service product registration system according to one embodiment. [Figure 2] Figure 2 is a schematic diagram showing the main components of the member data stored in the member data file. [Figure 3] Figure 3 is a schematic diagram showing the main components of the store data stored in the store data file. [Figure 4] Figure 4 is a schematic diagram showing the main components of the distribution data stored in the distribution data file. [Figure 5] Figure 5 is a block diagram showing the main circuit configuration of the support server. [Figure 6] Figure 6 is a schematic diagram showing the main data sets stored in the transaction file. [Figure 7] Figure 7 is a schematic diagram showing the main data sets stored in the store list. [Figure 8] Figure 8 is a block diagram showing the main circuit configuration of an information terminal. [Figure 9] Figure 9 is a flowchart showing the main steps of the primary information processing performed by the information terminal's processor. [Figure 10] Figure 10 is a flowchart showing the main steps of the primary information processing performed by the processor of an information terminal. [Figure 11] Figure 11 is a flowchart showing the main steps of the primary information processing performed by the processor of an information terminal. [Figure 12] Figure 12 is a flowchart showing the main steps of the primary information processing performed by the information terminal's processor. [Figure 13] Figure 13 is a flowchart showing the main steps of the primary information processing performed by the processor of an information terminal. [Figure 14] Figure 14 is a flowchart showing the main steps of the primary information processing performed by the information terminal's processor. [Figure 15] Figure 15 is a flowchart showing the main steps of the primary information processing performed by the processor of an information terminal. [Figure 16] Figure 16 is a flowchart showing the main steps of the primary information processing performed by the processor of an information terminal. [Figure 17] Figure 17 is a flowchart showing the main steps of the primary information processing performed by the processor of an information terminal. [Figure 18] Figure 18 is a flowchart showing the essential steps of the startup notification command reception process executed by the support server's processor. [Figure 19] Figure 19 is a flowchart showing the essential steps of the timer interrupt processing performed by the support server's processor. [Figure 20] Figure 20 is a flowchart showing the essential steps of the termination notification command reception process executed by the support server's processor. [Figure 21] Figure 21 is a flowchart showing the essential steps of the favorite notification command reception process executed by the support server's processor. [Figure 22] Figure 22 is a flowchart showing the essential steps of the release notification command reception process executed by the support server's processor. [Figure 23] Figure 23 is a flowchart showing the essential steps of the notification request command reception process executed by the support server's processor. [Figure 24] Figure 24 is a flowchart showing the essential steps of the check-in request command reception process executed by the support server's processor. [Figure 25] Figure 25 is a flowchart showing the essential steps of the registration request command reception process executed by the support server's processor. [Figure 26] Figure 26 is a flowchart showing the main procedure of the settlement request command reception process executed by the processor of the support server. [Figure 27] Figure 27 is a schematic diagram showing an example of the display of the top screen displayed on the touch panel of the information terminal. [Figure 28] Figure 28 is a schematic diagram showing an example of the display of the franchise store list screen displayed on the touch panel of the information terminal. [Figure 29] Figure 29 is a schematic diagram showing an example of the display of the favorite screen displayed on the touch panel of the information terminal. [Figure 30] Figure 30 is a schematic diagram showing an example of the display of the notification store screen displayed on the touch panel of the information terminal. [Figure 31] Figure 31 is a schematic diagram showing an example of the display of the notification screen displayed on the touch panel of the information terminal. [Figure 32] Figure 32 is a schematic diagram showing an example of the display of the reading screen displayed on the touch panel of the information terminal. [Figure 33] Figure 33 is a schematic diagram showing an example of the display of the registration screen displayed on the touch panel of the information terminal. [Figure 34] Figure 34 is a schematic diagram showing an example of the display of the accounting screen displayed on the touch panel of the information terminal.

Embodiments for Carrying Out the Invention

[0008] Hereinafter, an embodiment will be described with reference to the drawings. In this embodiment, a user of an information terminal used as a product registration terminal of a self-service product registration system can easily grasp information related to the promotion of a store using the information terminal before entering the store. In the following description, the user of the information terminal may be referred to as a consumer, a customer, a member, or an operator.

[0009] [Description of the Configuration of the Self-Service Product Registration System] First, the configuration of the self-service product registration system will be described. Figure 1 is a block diagram illustrating the schematic configuration of the self-service product registration system 100 according to this embodiment. The self-service product registration system 100 includes a server system 10 utilizing cloud computing and a POS (Point of Sales) system 20 built in a store. The store is a retail store such as a supermarket, where the sales area where goods are displayed and the checkout area (cash register) for payment are separated. The store is, for example, a franchisee that has entered into a franchise agreement with a company that operates the server system 10. The number of franchisees is not limited to one store. The self-service product registration system 100 is composed of the POS systems 20 of one or more franchisees and the server system 10.

[0010] The server system 10 and the POS system 20 enable bidirectional data communication through a network 30 that utilizes the Internet Protocol. Network 30 is a wide-area network that uses public or dedicated lines as a relay network and access networks such as wired LAN (Local Area Network), wireless LAN, mobile communication network, and cell phone communication network.

[0011] The self-service product registration system 100 requires an information terminal 40 that functions as a product registration terminal. The information terminal 40 is a portable wireless communication terminal that can access the server system 10 using, for example, a mobile phone communication network. The information terminal 40 is used by the user to input the data necessary for registering purchased products at a participating store. For example, a smartphone or tablet owned by an ordinary consumer can serve as the information terminal 40.

[0012] The server system 10 comprises a support server 11 and a router 12, which are connected by a communication line 13. The router 12 is also connected to the network 30 and serves as a relay point for data communication between the support server 11 and the POS system 20 using the network 30.

[0013] The support server 11 is a computer that assists customers visiting a participating store in self-registration operations, where they use an information terminal 40 to input the data necessary to register their purchased items. To provide this assistance, the support server 11 has at least the following two functions. The first function is to generate transaction data with the customer using the information terminal 40, based on the data necessary to register purchased items entered on the information terminal 40. The second function is to provide the POS system 20 with the data necessary to settle the transaction with the customer using the information terminal 40, in response to accounting instructions from the information terminal 40.

[0014] Furthermore, the support server 11 has a third function: the ability to distribute notification information to the information terminal 40. Notification information is information that member stores should notify consumers of. For example, information related to sales promotions such as information on special offers, new products, campaigns, and time sales constitutes notification information. The notification information distributed to the information terminal 40 is displayed on a display device, for example, to notify the consumer who is the user of the information terminal 40.

[0015] The support server 11 has at least a member data file 14, a store data file 15, and a distribution data file 16 in order to realize the third function. The member data file 14 is a collection of member data 141 (see Figure 2) created for each member. The store data file 15 is a collection of store data 151 (see Figure 3) created for each affiliated store. The distribution data file 16 is a collection of distribution data 161 (see Figure 4) created for each announcement information.

[0016] Figure 2 is a schematic diagram showing the main components of member data 141. As shown in the figure, member data 141 includes member ID, number of favorite stores k, store IDs for those k stores, and an active flag Fa.

[0017] A Member ID is a unique code assigned to each member to identify them. A member is a consumer who has registered to input the data necessary for registering purchased items using the information terminal 40. Consumers who wish to self-register at a participating store must register as a member in advance. Member registration is performed by installing a dedicated application software, the self-registration program, on the information terminal 40. When a consumer who is a user of the information terminal 40 registers as a member, that consumer is assigned a unique Member ID.

[0018] The number of favorite stores k is the number of affiliated stores that a member, identified by their member ID, has set as a favorite store. A member can set one or more affiliated stores as favorite stores. When a member sets an affiliated store as a favorite store, the store ID of that store is included in the member's member data 141. The store ID is a unique code assigned to each affiliated store to identify it individually.

[0019] The "Running" flag Fa is a 1-bit data value used to identify whether the self-registration program is running on an information terminal 40 whose user is a member identified by a member ID. In this embodiment, the "Running" flag Fa is set to "1" to indicate that the program is running, and the "Running" flag Fa is set to "0" to indicate that the program is not running. That is, when the self-registration program is started on an information terminal 40, the "Running" flag Fa of the member data 141, which describes the member ID of the member who is the user of that information terminal 40, becomes "1". Subsequently, when the self-registration program terminates, the "Running" flag Fa becomes "0".

[0020] Figure 3 is a schematic diagram showing the main components of store data 151. As shown in the figure, store data 151 includes store ID, store name, and number of distributed data n. As mentioned above, the store ID is a unique code assigned to each member store to identify each store individually. The store name is the unique name of the member store identified by the store ID. The number of distributed data n is the number of currently valid announcements among the announcements held by that member store. As will be described later, announcements have a defined distribution period. Currently valid announcements are those whose current date and time fall within the distribution period. Announcements whose current date and time fall outside the distribution period are invalid.

[0021] Figure 4 is a schematic diagram showing the main components of the distribution data 161. As shown in the figure, the distribution data 161 includes a data ID, a store ID, a distribution start date and time, a distribution end date and time, a distribution in progress flag Fb, and notification information. As mentioned above, the notification information is information that the merchant should notify consumers of. The data ID is a unique code assigned to each data to individually identify the distribution data 161 stored in the distribution data file 16. The store ID is the store ID of the merchant that has the notification information. The distribution start date and time and the distribution end date and time are the start and end dates and times of the distribution period for the notification information. The distribution in progress flag Fb is a 1-bit data that identifies whether the current date and time is within the distribution period of the notification information. In this embodiment, the distribution in progress flag Fb is set to "1" to indicate the distribution period from the distribution start date and time to the distribution end date and time, and the distribution in progress flag is set to "0" to indicate outside the distribution period, either before the distribution start date and time or after the distribution end date and time.

[0022] Returning to the explanation of Figure 1. The POS system 20 includes a store server 21, a monitoring terminal 22, a POS terminal 23, and a dedicated cashier 24, which are connected via an in-store network 25. The POS system 20 also connects a router 26 to the in-store network 25, and connects to network 30 via this router 26. Furthermore, the POS system 20 connects an access point 27 to the in-store network 25, enabling wireless LAN data communication with the information terminal 40 via this access point 27.

[0023] The store server 21 is a computer that manages sales information, product inventory information, and order information for a merchant based on transaction information settled at the merchant where the POS system 20 is installed.

[0024] The monitoring terminal 22 is a terminal for monitoring customers who are using the information terminal 40 to self-register their purchased items. The monitoring terminal 22 is equipped with a monitor that displays the customer's behavior within the store, data related to the customer's purchased items, etc.

[0025] POS terminal 23 is an accounting machine that processes settlements for transactions with customers who do not use information terminal 40. POS terminal 23 is operated by a store employee. POS terminal 23 may be a semi-self-service system, separated into a registration machine and a payment machine, with the registration machine operated by a store employee and the payment machine operated by the customer. Alternatively, POS terminal 23 may be a fully self-service system, operated by the customer.

[0026] The dedicated accounting machine 24 is an accounting machine that processes settlements for transactions with customers using the information terminal 40. The dedicated accounting machine 24 is operated by the customer. The dedicated accounting machine 24 has a function to scan the accounting barcode displayed on the information terminal 40, a payment processing function that supports various payment methods such as electronic money, credit cards, and cash, and an electronic money charging function.

[0027] Note that the POS system 20 shown in Figure 1 is just one example. The configuration of the POS system 20 may differ for each participating store.

[0028] [Support Server Configuration Description] Next, we will describe the configuration of the support server 11. Figure 5 is a block diagram showing the main circuit configuration of the support server 11. The support server 11 comprises a processor 111, main memory 112, auxiliary storage device 113, clock 114, communication interface 115, and system transmission line 116. The system transmission line 116 includes an address bus, data bus, control signal lines, etc. The support server 11 connects the processor 111, main memory 112, auxiliary storage device 113, clock 114, and communication interface 115 to the system transmission line 116. In the support server 11, the computer is composed of the processor 111, main memory 112, auxiliary storage device 113, clock 114, and communication interface 115, and the system transmission line 116 connecting them.

[0029] The processor 111 corresponds to the central part of the computer described above. The processor 111 controls various parts in order to realize various functions as a support server 11 according to the operating system or application program (application software). The processor 111 is, for example, a CPU (Central Processing Unit).

[0030] Main memory 112 corresponds to the main memory portion of the computer described above. Main memory 112 includes a non-volatile memory area and a volatile memory area. In the non-volatile memory area of ​​main memory 112, the operating system or application programs are stored. In the volatile memory area of ​​main memory 112, data necessary for the processor 111 to perform processing to control each part is stored. This data may also be stored in the non-volatile memory area. Main memory 112 uses the volatile memory area as a work area where data is rewritten as needed by the processor 111. The non-volatile memory area is, for example, ROM (Read Only Memory). The volatile memory area is, for example, RAM (Random Access Memory).

[0031] The auxiliary storage device 113 corresponds to the auxiliary storage portion of the computer described above. For example, an EEPROM (Electric Erasable Programmable Read-Only Memory), an HDD (Hard Disc Drive), or an SSD (Solid State Drive) can be the auxiliary storage device 113. The auxiliary storage device 113 stores data used by the processor 111 in performing various processes, or data created by the processing performed by the processor 111. The auxiliary storage device 113 may also store the application program described above.

[0032] Clock 114 measures the date and time. Support server 11 obtains the date and time measured by clock 114 as the current date and time.

[0033] The communication interface 115 is a circuit for sending and receiving data with each device connected via the network 30, in accordance with a predetermined communication protocol.

[0034] The support server 11 uses a portion of the volatile area in its main memory 112 as storage for transaction files 51 and store lists 52. Both transaction files 51 and store lists 52 are data sets created for each user of the information terminal 40, and therefore the storage area has enough capacity to store multiple transaction files 51 and multiple store lists 52.

[0035] Figure 6 is a schematic diagram showing the main data sets stored in the transaction file 51. As shown in the figure, the transaction file 51 stores the member ID, store ID, number of item data (m), item data for that number of items (m), total number of items, total amount, accounting code, etc. This data is necessary for settling transactions. In other words, in the transaction file 51, the member ID functions as a transaction identification code to identify transactions with customers. The transaction identification code does not have to be the member ID. The transaction identification code may also be a code to identify the information terminal 40, for example, the device ID of the information terminal 40, a mobile phone number, etc., can be the transaction identification code. The transaction identification code may also be a transaction number to identify a transaction, or it may be a combination of the transaction number with the store ID, date and time information such as the date and time of entry, etc.

[0036] The store ID is the store ID of the affiliated store where the customer, identified by the member ID, self-registers purchased items using the information terminal 40. The product details data includes items such as the product code, product name, price, number of items sold, and sales amount for the purchased items. The total number of items is the sum of the number of items sold for each of the m item details. The total amount is the sum of the sales amounts for each of the m item details. The sales amount is calculated by multiplying the price by the number of items sold. The accounting code is the code used by the customer, identified by the member ID, when making a payment at that store.

[0037] Figure 7 is a schematic diagram showing the main data sets stored in the store list 52. As shown in the figure, the store list 52 stores member IDs. In addition, list data describing the store name, favorite flag Fc, and number of distributed data n are stored in association with the store ID of each affiliated store. In the list data, the favorite flag Fc is a 1-bit data that identifies whether the member identified by the member ID has registered the affiliated store identified by the associated store ID as a favorite store. In this embodiment, the favorite flag Fc is set to "1" when the store is registered as a favorite store, and to "0" when it is not. The number of distributed data n is, as mentioned above, the number of currently valid announcements among the announcement information held by the affiliated store identified by the associated store ID.

[0038] [Description of the information terminal configuration] Next, we will describe the configuration of the information terminal 40. Figure 8 is a block diagram showing the main circuit configuration of the information terminal 40. The information terminal 40 includes a processor 41, internal memory 42, external memory 43, touch panel 44, camera 45, wireless unit 46, and system transmission line 47. The system transmission line 47 includes an address bus, data bus, control signal lines, etc. The information terminal 40 connects the processor 41, internal memory 42, external memory 43, touch panel 44, camera 45, and wireless unit 46 to the system transmission line 47. In the information terminal 40, the computer is composed of the processor 41, internal memory 42, external memory 43, and the system transmission line 47 connecting them.

[0039] The processor 41 corresponds to the central part of the computer described above. The processor 41 controls various parts in order to realize various functions as an information terminal 40 according to the operating system or application program (application software). The processor 41 is, for example, a CPU.

[0040] The internal memory 42 corresponds to the main memory portion of the computer described above. The internal memory 42 includes a non-volatile memory area and a volatile memory area. The internal memory 42 stores the operating system or application programs in the non-volatile memory area. The internal memory 42 stores data necessary for the processor 41 to perform processing to control each part in the volatile memory area. The internal memory 42 also uses the volatile memory area as a work area where data is rewritten as needed by the processor 41. The non-volatile memory area is, for example, ROM. The volatile memory area is, for example, RAM.

[0041] External memory 43 corresponds to the auxiliary storage portion of the computer described above. For example, an SD memory card, USB memory, etc., can serve as external memory 43. External memory 43 stores data used by the processor 41 in performing various processes, or data created by the processing performed by the processor 41. External memory 43 may also store the application programs described above.

[0042] The touch panel 44 is a device that combines a display unit as a display unit and a touch sensor as a detection unit. The display unit has a screen for displaying various images. The touch sensor detects the position on the screen touched by the operator. The touch panel 44 acquires data input by the operator from the position on the screen detected by the touch sensor and the image information displayed at that position. Thus, the touch panel 44 is an example of both a display device and an example of an input device.

[0043] Camera 45 is an imaging device built into the information terminal 40. Processor 41 functions as a reader that reads codes such as barcodes and two-dimensional codes from images captured by camera 45. Many products have a barcode attached to them that represents the product code of the product in a predetermined barcode system. Processor 41 obtains the product code of the purchased product by reading the barcode attached to the product from the image captured by camera 45. In this way, camera 45 functions as an input device for the information terminal 40.

[0044] The wireless unit 46 is a communication device that performs data communication with the access point 27 in accordance with the wireless LAN communication protocol.

[0045] In the information terminal 40 with this configuration, a self-registration program is installed in the internal memory 42 or external memory 43. The method of installing the self-registration program in the internal memory 42 or external memory 43 is not particularly limited. The self-registration program can be installed in the internal memory 42 or external memory 43 by recording it on a removable recording medium or by distributing the self-registration program via communication over a network. The recording medium can take any form as long as it can store a program and is readable by the device, such as an SD memory card or USB memory.

[0046] In an information terminal 40 with the self-registration program installed, a portion of the external memory 43 is designated as the member ID area 431. In addition, a portion of the internal memory 42 is designated as the store list area 421, the number of favorite stores k area 422, the total number of notifications N area 423, and the notification information area 424. At least one of each area 421, 422, 423, and 424 may be formed in the external memory 43.

[0047] In an information terminal 40 on which a self-registration program is installed, the processor 41 has the functions of a setting unit 411, a first acquisition unit 412, a second acquisition unit 413, a notification unit 414, an output unit 415, a notification unit 416, and a specific unit 417.

[0048] The setting unit 411 has the function of setting the consumer's favorite store from among multiple affiliated stores. The setting unit 411 can be rephrased as the setting means. The first acquisition unit 412 has the function of acquiring data from the support server 11 via wireless communication that indicates whether or not each of the multiple affiliated stores has information to notify the consumer, that is, valid notification information. Such data is the data of the store list 52. The first acquisition unit 412 can be rephrased as the first acquisition means. The second acquisition unit 413 has the function of acquiring information that the user's favorite store has to notify the consumer from the support server 11 via wireless communication. The second acquisition unit 413 can be rephrased as the second acquisition means. The notification unit 414 has the function of notifying the user if the user's favorite store has information to notify the consumer based on the data acquired by the first acquisition unit 412. The notification unit 414 also has the function of notifying the user each time the information that the user's favorite store has to notify the consumer is updated. The notification unit 414 can be rephrased as the notification means. The output unit 415 has the function of outputting the information acquired by the second acquisition unit 413. The output unit 415 can be rephrased as an output means. The notification unit 416 has the function of notifying the support server 11 of the favorite stores specified by the user from among the favorite stores that have been notified by the notification unit 414 to have notification information. The identification unit 417 has the function of identifying the affiliated store that the user has entered. The notification unit 416 also has the function of notifying the support server 11 of the favorite store if the affiliated store identified by the identification unit 417 is a favorite store. The notification unit 416 can be rephrased as a notification means. The identification unit 417 can be rephrased as an identification means. These functions 411 to 417 are realized by the processor 41 performing various information processing according to the self-registration program.

[0049] [Explanation of the operation of the self-service product registration system] Next, the operation of the self-service product registration system will be explained based on the information processing procedures performed by the processor 41 of the information terminal 40 and the information processing procedures performed by the processor 111 of the support server 11. Figures 9 to 17 are flowcharts showing the main information processing steps performed by the processor 41 of the information terminal 40 in accordance with the self-registration program. Figures 18 to 26 are flowcharts showing the main information processing steps performed by the processor 111 of the support server 11 in cooperation with the information terminal 40. Figures 27 to 34 are examples of various screens displayed on the touch panel 44 of the information terminal 40. Note that the information processing procedures and contents described below are examples only. The procedures or contents can be changed as appropriate if similar effects can be achieved. Also, the layout, images, text, etc. of each screen are not limited to those shown.

[0050] When the self-registration program is started on the information terminal 40, the processor 41 begins information processing according to the procedure shown in the flowcharts in Figures 9 to 17. First, the processor 41 obtains the member ID from area 431 as ACT1 in Figure 9. Then, the processor 41 controls the wireless unit 46 to send a startup notification command as ACT2. This control causes the wireless unit 46 to wirelessly transmit the startup notification command. The startup notification command is sent to the support server 11 via the network 30, which uses the mobile phone communication network as its access network. The startup notification command includes the member ID obtained in ACT1.

[0051] Upon receiving the startup notification command, the processor 111 of the support server 11 begins the information processing procedure shown in the flowchart of Figure 18, which is the so-called startup notification command reception processing. The processor 111 obtains the member ID from the startup notification command as ACT201. Then, the processor 111 searches the member data file 14 as ACT202 and changes the operational flag Fa of the member data 141 containing the obtained member ID from "0" to "1".

[0052] Processor 111 reads member data 141, including the member ID obtained as ACT203, from member data file 14. Processor 111 also reads store data 151 for all member stores from store data file 15 as ACT204. Then, as ACT205, processor 111 saves the member ID obtained from the startup notification command and creates a store list 52 using the store data 151 for all member stores read from store data file 15 as list data. At this time, as ACT206, processor 111 sets all favorite flags Fc in the list data to "0".

[0053] Having finished creating the store list 52, processor 111 resets the increment counter P to "0" as ACT207. Next, processor 111 increments the increment counter P by "1" as ACT208. Then, processor 111 checks as ACT209 whether the increment counter P has exceeded the maximum value Pmax. The maximum value Pmax is the total number of store data 151 stored in the store data file 15.

[0054] If the increment counter P does not exceed the maximum value Pmax, the processor 111 proceeds from ACT209 to ACT210. The processor 111 retrieves the P-th store ID from the store list 52 as ACT210. The P-th "P" is the count value of the increment counter P. The P-th store ID is the P-th store ID from the beginning of the list data in the store list 52.

[0055] If the P-th store ID is obtained, the processor 111 compares it with the member data 141 read from the member data file 14 as ACT211. Hereinafter, the member data 141 read from the member data file 14 will be referred to as the target member data 141. The processor 111 checks whether the target member data 141 contains the P-th store ID as ACT212. If the target member data 141 contains the P-th store ID, that is, if the affiliated store identified by the P-th store ID is a favorite store of the member identified by the member ID, the processor 111 proceeds from ACT212 to ACT213. As ACT213, the processor 111 changes the favorite flag Fc associated with the P-th store ID from the beginning of the list data in the store list 52 from "0" to "1". After that, the processor 111 returns to ACT208. In contrast, if the P-th store ID does not exist in the target member data 141, that is, if the affiliated store identified by the P-th store ID is not a favorite store of the member identified by the member ID, the processor 111 skips the processing of ACT213 and returns to ACT208.

[0056] The processor 111, having returned to ACT208, executes the processing of ACT208 through ACT213 in the same manner as described above until the increment counter P exceeds the maximum value Pmax. That is, the processor 111 increments the increment counter P by "1" each time, and each time it obtains the P-th store ID from the beginning of the list data and checks whether that store ID is included in the target member data 141. If it is included, the processor 111 changes the favorite flag Fc associated with the P-th store ID from the beginning of the list data from "0" to "1".

[0057] When the summation counter P exceeds the maximum value Pmax, the processor 111 proceeds from ACT209 to ACT214. The processor 111 saves the store list 52 to the main memory 112 as ACT214. The processor 111 also controls the communication interface 115 to send the store list 52 to the information terminal 40 that sent the startup notification command as ACT215. Through this control, the data of the store list 52 is wirelessly transmitted to the information terminal 40 that sent the startup notification command via the network 30. With this, the processor 111 finishes processing the reception of the startup notification command.

[0058] In this way, when the support server 11 receives the startup notification command, a store list 52 containing the member IDs included in the startup notification command is created and stored, and the store list 52 is sent to the information terminal 40 that sent the startup notification command. The store list 52 is data that includes information identifying whether or not it is a favorite store of the member identified by the member ID, i.e., a favorite flag Fc, and the number of currently valid announcements among the announcement information held by the affiliated store, i.e., the number of distributed data n.

[0059] By the way, the number of currently valid notification information items, i.e., the number of distributed data items n, is updated as time passes. Therefore, the support server 11 has the function of updating the created store list 52 in accordance with the update of the number of distributed data items n, and sending the updated store list 52 to the information terminal 40 to which the member ID of the store list 52 is set. This update is achieved by the timer interrupt processing described next.

[0060] Figure 19 is a flowchart showing the essential steps of the timer interrupt processing performed by the processor 111 of the support server 11. The processor 111 starts the timer interrupt processing each time it receives a timer interrupt signal. The timer interrupt signal is generated, for example, each time a predetermined period of time has elapsed, as measured by the clock 114. The predetermined period is preferably 1 minute, if the distribution start date and time and distribution end date and time are in minutes.

[0061] When processor 111 starts timer interrupt processing, it resets the increment counter Q to "0" as ACT221. Next, processor 111 increments the increment counter Q by "1" as ACT222. Then, processor 111 checks as ACT223 whether the increment counter Q has exceeded the maximum value Qmax. The maximum value Qmax is the number of distribution data 161 stored in the distribution data file 16.

[0062] If the addition counter Q does not exceed the maximum value Qmax, the processor 111 reads the Qth distribution data 161 from the distribution data file 16 as ACT224. The Qth "Q" is the count value of the addition counter Q. The Qth distribution data 161 is the Qth distribution data 161 from the beginning among the distribution data 161 stored in the distribution data file 16.

[0063] If the Qth distribution data 161 is read from the distribution data file 16, the processor 111 checks, as ACT225, whether the Qth distribution data 161 is within the distribution period. The processor 111 determines that the distribution period is in effect if the current date and time, measured by the clock 114, falls within the period from the distribution start date and time to the distribution end date and time of the distribution data 161. The processor 111 determines that the distribution period is outside the distribution period if the current date and time is before the distribution start date and time or after the distribution end date and time.

[0064] If the Qth data distribution 161 is outside the distribution period, processor 111 proceeds from ACT225 to ACT226. Processor 111 checks the distribution flag Fd of the Qth data distribution 161 as ACT226. If the distribution flag Fd is "0", processor 111 returns from ACT226 to ACT222. Then processor 111 executes the processing from ACT222 onward in the same manner as described above.

[0065] If the distribution flag Fd is "1", processor 111 proceeds from ACT226 to ACT227. Processor 111 changes the distribution flag Fd of the Qth distribution data 161 from "1" to "0" as ACT227. Processor 111 also obtains the store ID from the Qth distribution data 161 as ACT228. Then, as ACT229, processor 111 reduces the number of distribution data n of the store data 151 stored in the store data file 15 that includes the store ID obtained in the process of ACT228 by "1".

[0066] On the other hand, if the Qth data distribution 161 is within the distribution period in ACT225, processor 111 proceeds from ACT225 to ACT230. Processor 111 checks the distribution flag Fd of the Qth data distribution 161 as ACT230. If the distribution flag Fd is "1", processor 111 returns from ACT230 to ACT222. Then processor 111 executes the processing from ACT222 onward in the same manner as described above.

[0067] If the distribution flag Fd is "0", processor 111 proceeds from ACT230 to ACT231. Processor 111 changes the distribution flag Fd of the Qth distribution data 161 from "0" to "1" as ACT231. Processor 111 also obtains the store ID from the Qth distribution data 161 as ACT232. Then, as ACT233, processor 111 increases the number of distribution data n of the store data 151 stored in the store data file 15 that includes the store ID obtained in the process of ACT232 by "1".

[0068] In ACT229 or ACT233, processor 111, having updated the number of distributed data n for store data 151, proceeds to ACT234. Processor 111 detects members who have designated a member store identified by the store ID obtained from the Qth distributed data 161 as their favorite store in ACT234. Specifically, processor 111 detects the member ID of member data 141 stored in member data file 14 that includes the store ID obtained from the Qth distributed data 161. Hereinafter, members with the detected member ID will be referred to as favorite members.

[0069] Once all favorite members have been detected, processor 111 proceeds to ACT235. In ACT235, processor 111 extracts all favorite members from among the favorite members whose information terminal 40's self-registration program is running, i.e., favorite members whose running flag Fa stored in member data 141 is "1". In ACT236, processor 111 updates the number of distribution data n in store list 52, which includes the member IDs of the extracted favorite members. Specifically, if the number of distribution data n in store data 151 is decreased by "1" in ACT229, the number of distribution data n in store list 52 is decreased by "1". If the number of distribution data n in store data 151 is increased by "1" in ACT233, the number of distribution data n in store list 52 is increased by "1".

[0070] Once the number of distribution data points n for the store list 52, which includes the member IDs of favorite members, has been updated, the processor 111 controls the communication interface 115 to send the updated store list 52 with the updated number of distribution data points n to the information terminal 40, which is configured with the member IDs stored in the store list 52, as ACT237. Through this control, the updated store list 52 is sent to the information terminal 40, which is configured with the member IDs of the store list 52 with the updated number of distribution data points n.

[0071] After completing the transmission of the updated store list 52 with the number of distributed data points n, processor 111 returns to ACT222. Processor 111 then executes the processing from ACT222 onward in the same manner as described above. Thus, when the increment counter Q exceeds the maximum value Qmax in ACT223, processor 111 terminates the timer interrupt processing.

[0072] In this way, the store list 52, which is created in response to the startup notification command and sent to the information terminal 40 that sent the startup notification command, is resent in real time to the information terminal 40 that sent the startup notification command every time the number of distributed data n is updated.

[0073] Returning to the explanation of Figure 9. The processor 41 of the information terminal 40 that sent the startup notification command waits for the store list 52 as ACT3. When the processor 41 receives the store list 52 via the wireless unit 46, it proceeds from ACT3 to ACT4. As ACT4, the processor 41 stores the store list 52 in memory 421.

[0074] Processor 41 counts the number S of store IDs in the store list 52 whose favorite flag Fc is set to "1" as ACT5. If the number S is "0", that is, if the user of the information terminal 40 has not set a favorite store, Processor 41 proceeds from ACT5 to ACT6. Processor 41 sets the number of favorite stores k in area 422 to "0" as ACT6. Also, Processor 41 sets the total number of notifications N in area 423 to "0" as ACT7.

[0075] In contrast, if the number S is 1 or greater, that is, if the user of the information terminal 40 has set a favorite store, the processor 41 proceeds from ACT5 to ACT8. In ACT8, the processor 41 sets the number k of favorite stores in area 422 as the number S. In ACT9, the processor 41 retrieves all the number n of distribution data described in the store list 52, associated with the store IDs for which the favorite flag Fc is set to "1". Then, in ACT10, the processor 41 sets the sum of the retrieved number n of distribution data as the total number N of notifications in area 423.

[0076] After completing the processing of ACT6 and ACT7 or ACT8 through ACT10, the processor 41 proceeds to ACT11. As ACT11, the processor 41 displays the top screen SCa (see Figure 27) on the touch panel 44.

[0077] Figure 27 is a schematic diagram showing one example of the display of the top screen SCa. As shown in the figure, the top screen SCa has various soft keys: the Shopping Start button BTa, the Store Search button BTb, the Favorites button BTc, the Notifications button BTd, and the Exit button BTe. The Shopping Start button BTa is a soft key that the user of the information terminal 40 inputs when entering a store and starting self-registration of purchased items. The Store Search button BTb is a soft key that the user inputs when searching for a store. The user can set a desired store from the searched stores as a favorite store. The Favorites button BTc is a soft key that the user inputs when checking the stores that have been set as favorite stores. The user can remove the favorite status of the favorite stores that have been checked. The Notifications button BTd is a soft key that the user inputs when checking notification information of a favorite store. The total number of notifications N stored in area 423 is displayed on the Notifications button BTd. The total number of notifications N is displayed, for example, enclosed in a circle in the upper right corner of the Notifications button BTd. If the total number of notifications N is "0", the total number of notifications N may or may not be displayed. Also, the display format for the total number of notifications N is not limited to that shown in Figure 27. In short, any display format that allows the user to know the total number of notifications N is acceptable. The exit button BTe is a soft key that the user inputs when they want to exit the self-registration program.

[0078] The processor 41 of the information terminal 40 displaying the top screen SCa checks whether it has received the updated store list 52 as ACT12. If it has not received the updated store list 52, the processor 41 proceeds from ACT12 to ACT13. The processor 41 checks whether any of the soft keys located on the top screen SCa have been pressed as ACT13. If no soft keys have been pressed, the processor 41 returns to ACT12. In this way, the processor 41 waits for either the updated store list 52 to be received in ACT12 and ACT13, or for a soft key on the top screen SCa to be pressed.

[0079] When the processor 41 receives the updated store list 52 while in the waiting state for ACT12 and ACT13, it proceeds from ACT12 to ACT14. As ACT14, the processor 41 updates the store list 52 in area 421 with the updated store list 52. After that, the processor 41 returns to ACT5 and executes the processing from ACT5 onwards in the same way as described above. Thus, the new number of favorite stores k and the total number of notifications N are derived from the updated store list 52, and the values ​​in areas 422 and 423 are updated. The total number of notifications N displayed on the top screen SCa is also changed to the updated value. Then the processor 41 returns to the waiting state for ACT12 and ACT13.

[0080] Here, the processor 41 performs the processing of ACT3 and ACT4, and further the processing of ACT12 and ACT14, thereby realizing its function as the first acquisition unit 412. The processor 41 also performs the processing of ACT5 to ACT11 in cooperation with the touch panel 44, thereby realizing its function as the notification unit 414.

[0081] In this way, when a user of the information terminal 40 starts the self-registration program, the touch panel 44 screen becomes the top screen SCa. The notification button BTd on the top screen SCa displays the total number of notifications N. The total number of notifications N is the number of currently valid notifications from the affiliated stores that the user has set as their favorite stores. Therefore, the user can easily check whether or not there are currently valid notifications simply by starting the self-registration program.

[0082] If either soft key is pressed while in the standby state of ACT12 or ACT13, the processor 41 proceeds from ACT13 to ACT15. The processor 41 checks whether the soft key pressed as ACT15 is the exit button BTe. If the exit button BTe soft key is pressed, the processor 41 proceeds from ACT15 to ACT16. The processor 41 controls the wireless unit 46 to send an exit notification command as ACT16. This control causes the wireless unit 46 to wirelessly transmit the exit notification command. The exit notification command is sent to the support server 11 via the network 30, which uses the mobile phone communication network as its access network. The exit notification command includes the member ID. After sending the exit notification command, the processor 41 terminates the information processing according to the self-registration program.

[0083] Upon receiving a termination notification command, the processor 111 of the support server 11 begins the information processing procedure shown in the flowchart of Figure 20, which is the so-called termination notification command reception processing. The processor 111 obtains the member ID from the termination notification command as ACT251. Hereinafter, the member ID obtained from the termination notification command will be referred to as the obtained member ID. The processor 111 deletes the store list 52 containing the obtained member ID from the main memory 112 as ACT252. The processor 111 also resets the operational flag Fa of the member data containing the obtained member ID to "0" as ACT253. With this, the processor 111 terminates the termination notification command reception processing.

[0084] Thus, when a user of the information terminal 40 touches the exit button BTe on the top screen SCa, the self-registration program stops. In addition, the store list 52 related to that user, which was stored in the main memory 112 of the support server 11, is cleared.

[0085] Returning to the explanation of Figure 9. If, during the standby state of ACT12 and ACT13, a soft key other than the exit button BTe located on the top screen SCa is pressed, the processor 41 proceeds from ACT15 to ACT21 in Figure 10. The processor 41 checks whether the soft key pressed as ACT21 is the shopping start button BTa. If it is not the shopping start button BTa, the processor 41 checks whether the soft key pressed as ACT22 is the store search button BTb. If it is not the store search button BTb either, the processor 41 checks whether the soft key pressed as ACT23 is the favorites button BTc. If it is not the favorites button BTc either, the processor 41 checks whether the soft key pressed as ACT24 is the notification button BTd. If it is not the notification button BTd either, the processor 41 executes another process as ACT25. Other processing refers to the process executed when any of the buttons not shown are pressed, assuming that the top screen SCa has buttons other than the Start Shopping button BTa, Store Search button BTb, Favorites button BTc, Notification button BTd, and Exit button BTe. After completing the other processing, the processor 41 returns to the waiting state of ACT12 and ACT13 in Figure 9.

[0086] When the store search button BTb is pressed while ACT12 and ACT13 are in standby mode, the processor 41 proceeds from ACT22 to ACT31 in Figure 11. For ACT31, the processor 41 sets the touch panel 44 screen to the merchant list screen SCb (see Figure 28).

[0087] Figure 28 is a schematic diagram showing one example of the display of the merchant list screen SCb. As shown in the figure, the merchant list screen SCb displays the names of all merchants stored in the store list 52 in order. The soft key for the close button BTf is also displayed. Furthermore, for merchants whose favorite flag Fc is set to "1", a mark MAa indicating that it is a favorite store is displayed. For merchants whose favorite flag Fc is set to "0", a mark MAb indicating that it is not a favorite store is displayed. Note that the form of marks MAa and MAb is not limited to those shown in Figure 28. The point is that the user of the information terminal 40 should be able to distinguish between merchants that have been set as favorite stores and those that have not.

[0088] To add a new favorite store, a user who has viewed the merchant list screen (SCb) should touch the store name displaying the MAb mark. To close the merchant list screen (SCb), the user should touch the close button (BTf).

[0089] Returning to the explanation of Figure 11. The processor 41 of the information terminal 40 displaying the merchant list screen SCb waits for either the close button BTf to be pressed (ACT32) or for one of the merchant names to be selected by touch operation (ACT33). If a merchant name is selected during the waiting state of ACT32 and ACT33, the processor 41 proceeds from ACT33 to ACT34. As ACT34, the processor 41 checks the favorite flag Fc stored in the merchant list 52 in association with the merchant ID of the selected merchant name. If the favorite flag Fc is "1", that is, if the user has selected the name of a merchant that is a favorite store, the processor 41 returns to the waiting state of ACT32 and ACT33.

[0090] In contrast, if the favorite flag Fc is "0", that is, if the user selects the name of a member store that is not a favorite store, the processor 41 proceeds from ACT34 to ACT35. The processor 41 controls the wireless unit 46 to send a favorite notification command as ACT35. This control causes the favorite notification command to be transmitted wirelessly from the wireless unit 46. The favorite notification command is sent to the support server 11 via the network 30, which uses the mobile phone communication network as the access network. The favorite notification command includes the member ID, as well as the store ID described in the store list 52 in association with the selected store name.

[0091] Upon receiving a favorite notification command, the processor 111 of the support server 11 begins the information processing procedure shown in the flowchart in Figure 21, which is the so-called favorite notification command reception processing. The processor 111 obtains the member ID and store ID from the favorite notification command as ACT261. Hereinafter, the member ID obtained from the favorite notification command will be referred to as the obtained member ID. Similarly, the store ID obtained from the favorite notification command will be referred to as the obtained store ID.

[0092] Processor 111 detects member data 141 containing the acquired member ID from member data file 14 as ACT262. Then, as ACT263, processor 111 adds the acquired store ID to member data 141 containing the acquired member ID. Also, as ACT264, processor 111 increments the number of favorite stores k in member data 141 containing the acquired member ID by "1".

[0093] Processor 111 detects the store list 52 containing the acquired member ID as ACT265. Then, as ACT266, Processor 111 changes the favorite flag Fc associated with the acquired store ID in the store list 52 containing the acquired member ID from "0" to "1". Subsequently, as ACT267, Processor 111 controls the communication interface 115 to send the store list 52 with the changed favorite flag Fc to the information terminal 40 that sent the favorite notification command. This control causes the data of the store list 52 with the changed favorite flag Fc to be wirelessly transmitted to the information terminal 40 that sent the favorite notification command via the network 30. This completes the process of receiving the favorite notification command.

[0094] Returning to the explanation of Figure 11. The processor 41, which controls the sending of the favorite notification command, returns to the waiting state for ACT32 and ACT33. In this waiting state, if another store name is selected, the processor 41 executes the processing of ACT34 and ACT35 as described above. Therefore, each time a store name of a member store that is not a favorite store is selected from the store names displayed on the member store list screen SCb, the processor 41 sends a favorite notification command to the support server 11, including the store ID and member ID of that member store. In response, the support server 11 executes the favorite notification command reception processing described using Figure 21. As a result, the favorite flag associated with the store ID in the store list 52, which includes the member ID, is updated from "0" to "1", and the updated store list 52 is sent to the information terminal 40 that sent the favorite notification command.

[0095] If the close button BTf is pressed while ACT32 and ACT33 are in standby mode, the processor 41 returns to the standby mode of ACT12 and ACT13 as shown in Figure 9. Therefore, when the processor 41 receives the updated store list 52 with the favorite flag Fc changed from the support server 11, it changes the store list 52 in area 421 to the updated store list 52.

[0096] If the favorite button BTc is pressed while in the waiting state of ACT12 and ACT13, the processor 41 proceeds from ACT23 to ACT26 in Figure 10. In ACT26, the processor 41 checks whether the number of favorite stores k in area 422 is "1" or greater. If the number of favorite stores k is "0", that is, if the user has not set any favorite stores, the processor 41 returns to the waiting state of ACT12 and ACT13 in Figure 9.

[0097] If the number of favorite stores k is "1" or greater, the processor 41 proceeds from ACT26 to ACT51 in Figure 12. As ACT51, the processor 41 detects the store ID and store name of affiliated stores whose favorite flag Fc is set to "1" from the store list 52 stored in area 421. In other words, the processor 41 detects the store ID and store name of affiliated stores that the user of the information terminal 40 has set as a favorite store. Then, as ACT52, the processor 41 sets the screen of the touch panel 44 as the favorite screen SCc (see Figure 29).

[0098] Figure 29 is a schematic diagram showing one example of the display of the Favorites screen SCc. As shown in the figure, the Favorites screen SCc displays the names of the stores detected from the store list 52, i.e., the names of the favorite stores, in order. The soft key for the close button BTg is also displayed. Furthermore, a mark MAa indicating that it is a favorite store is displayed next to each store name.

[0099] To remove a favorite store from a user's favorites screen (SCc), the user touches the store's name. To close the favorites screen (SCc), the user touches the close button (BTf).

[0100] Returning to the explanation of Figure 12. The processor 41, which controls the display of the favorites screen SCc, waits for either the close button BTg to be pressed as ACT53, or for one of the store names to be selected by touch operation as ACT54. If a store name is selected during the waiting state of ACT53 and ACT54, the processor 41 proceeds to ACT55. As ACT55, the processor 41 displays a confirmation screen on the touch panel 44 to ask the user whether or not to remove the favorites status. The confirmation screen is, for example, a screen with a confirmation message such as "Do you want to remove the favorite store?" along with "Yes" and "No" buttons. The confirmation screen is displayed as a pop-up, for example, on top of the favorites screen SCc.

[0101] Processor 41 checks whether a command to cancel the favorite status is issued as ACT56. If the "No" button is touched, processor 41 recognizes that the cancellation has been canceled. Processor 41 returns to the waiting state for ACT53 and ACT54.

[0102] If the "Yes" button is touched, the processor 41 recognizes that a command to remove the favorite has been issued. The processor 41 proceeds to ACT 57. The processor 41 controls the wireless unit 46 to send a removal notification command as ACT 57. This control causes the wireless unit 46 to wirelessly transmit the removal notification command. The removal notification command is sent to the support server 11 via the network 30, which uses the mobile phone communication network as its access network. The removal notification command includes the member ID and the store ID of the merchant whose favorite has been removed.

[0103] Upon receiving the cancellation notification command, the processor 111 of the support server 11 begins the information processing procedure shown in the flowchart in Figure 22, which is the so-called cancellation notification command reception processing. The processor 111 obtains the member ID and store ID from the cancellation notification command as ACT271. Hereinafter, the member ID obtained from the cancellation notification command will be referred to as the obtained member ID. Similarly, the store ID obtained from the cancellation notification command will be referred to as the obtained store ID.

[0104] Processor 111 detects member data 141 containing the acquired member ID from member data file 14 as ACT272. Then, as ACT273, processor 111 removes the acquired store ID from member data 141 containing the acquired member ID. Also, as ACT274, processor 111 reduces the number of favorite stores k in member data 141 containing the acquired member ID by "1".

[0105] Processor 111 detects a store list 52 containing the acquired member ID as ACT275. Processor 111 changes the favorite flag Fc associated with the acquired store ID in the store list 52 containing the acquired member ID from "1" to "0" as ACT276. Then, processor 111 controls the communication interface 115 to send the store list 52 with the changed favorite flag Fc to the information terminal 40 that sent the release notification command as ACT277. This control causes the data of the store list 52 with the changed favorite flag Fc to be wirelessly transmitted to the information terminal 40 that sent the release notification command via the network 30. This completes the process of receiving the release notification command.

[0106] Returning to the explanation of Figure 12. The processor 41, which controlled the sending of the cancellation notification command, returns to the waiting state for ACT53 and ACT54. In this waiting state, if another store name is selected, the processor 41 executes the processing of ACT56 to ACT57 in the same manner as described above. Therefore, each time a store name is selected from the store names displayed on the favorites screen SCc and a command to cancel the favorite is issued, the processor 41 sends a cancellation notification command to the support server 11, which includes the store ID and member ID of the affiliated store of that store name. In response, the support server 11 executes the receiving process for the cancellation notification command as described using Figure 22. As a result, the favorite flag associated with the store ID in the store list 52, which includes the member ID, is updated from "1" to "0", and the updated store list 52 is sent to the information terminal 40 that sent the cancellation notification command.

[0107] If the close button BTg is pressed while ACT53 and ACT54 are in standby mode, the processor 41 returns to the standby mode of ACT12 and ACT13 as shown in Figure 9. Therefore, when the processor 41 receives the updated store list 52 with the favorite flag Fc changed from the support server 11, it changes the store list 52 in area 421 to the updated store list 52.

[0108] Here, the processor 41 performs the processing of ACT31 to ACT35 in Figure 11 and the processing of ACT51 to ACT57 in Figure 12, thereby realizing the function of a setting unit 411.

[0109] In this way, when a user of the information terminal 40 presses the store search button BTb on the top screen SCa, the touch panel 44 screen changes to the affiliated store list screen SCb. This affiliated store list screen SCb allows the user to view a list of affiliated stores where they can self-register purchased items using the information terminal 40. Furthermore, the user can distinguish between affiliated stores they have set as favorites and those they have not. To set a new favorite store, the user touches the store name displayed on the affiliated store list screen SCb along with the mark MAb. This operation registers the touched affiliated store as the user's favorite store in the support server 11. Therefore, the user can easily set their desired affiliated store as a favorite.

[0110] On the other hand, when the user presses the Favorites button BTc on the top screen SCa, the touch panel 44 screen changes to the Favorites screen SCc. This Favorites screen SCc allows the user to see the affiliated stores they have set as favorites. To remove an affiliated store from the favorites list, the user touches the store name displayed on the Favorites screen SCc along with the mark MAa. This operation causes the support server 11 to manage the touched affiliated store as no longer being one of the user's favorites. Therefore, the user can remove an affiliated store from the favorites list with a simple operation.

[0111] If the notification button BTd is pressed while in the standby state of ACT12 and ACT13, the processor 41 proceeds from ACT24 to ACT27 in Figure 10. In ACT27, the processor 41 checks whether the total number of notifications N in area 423 is "1" or greater. If the total number of notifications N is "0", that is, if there is no valid notification information at the moment, the processor 41 returns to the standby state of ACT12 and ACT13 in Figure 9.

[0112] If the total number of notifications N is "1" or greater, the processor 41 proceeds from ACT27 to ACT61 in Figure 13. As ACT61, the processor 41 detects the store ID and store name of member stores from the store list 52 stored in area 421 where the favorite flag Fc is set to "1" and the number of distributed data n is "1" or greater. In other words, the processor 41 detects the store ID and store name of member stores that are favorite stores of the user and currently have one or more valid notification items. As ACT62, the processor 41 sets the screen of the touch panel 44 to the notification store screen SCd (see Figure 30).

[0113] Figure 30 is a schematic diagram showing one example of the display of the Notification Stores screen SCd. As shown in the figure, the Notification Stores screen SCd displays the names of stores detected from the store list 52, that is, the names of member stores that are favorite stores and currently have one or more active notification items, in order. A soft key for the close button BTh is also displayed. Furthermore, the number of distributed data n, that is, the number of currently active notification items, is displayed for each store name, for example, by a circled number.

[0114] A user who has viewed the Store Notifications screen (SCd) can touch the name of their favorite store to view the notification information for that store. To close the Store Notifications screen (SCd), the user touches the close button (BTh).

[0115] Returning to the explanation of Figure 13. The processor 41, which controls the display of the notification store screen SCd, waits for either the close button BTh to be pressed as ACT63, or for one of the store names to be selected as ACT64. If a store name is selected during the waiting state of ACT63 or ACT64, the processor 41 proceeds to ACT65. The processor 41 controls the wireless unit 46 to send a notification request command as ACT65. This control causes the notification request command to be transmitted wirelessly from the wireless unit 46. The notification request command is sent to the support server 11 via the network 30, which uses the mobile phone communication network as the access network. The notification request command includes the member ID and the store ID of the affiliated store of the selected store name.

[0116] Upon receiving a notification request command, the processor 111 of the support server 11 begins the information processing procedure shown in the flowchart in Figure 23, which is the so-called notification request command reception processing. The processor 111 obtains the member ID and store ID from the notification request command as ACT281. Hereinafter, the member ID obtained from the notification request command will be referred to as the obtained member ID. Similarly, the store ID obtained from the notification request command will be referred to as the obtained store ID.

[0117] Processor 111 resets the count counter r to "0" as ACT282. Processor 41 detects the distribution data 161 stored in the distribution data file 16 as ACT283. Then, processor 111 checks as ACT284 whether or not it was able to detect the distribution data 161.

[0118] If no undetected distribution data 161 is stored in the distribution data file 16, distribution data 161 cannot be detected. If undetected distribution data 161 is stored in the distribution data file 16 and it can be detected, processor 111 proceeds from ACT284 to ACT285. Hereinafter, the detected distribution data 161 will be referred to as detected distribution data 161. Processor 111 checks whether the store ID of the detected distribution data 161 matches the acquired store ID as ACT285. If the two store IDs do not match, processor 111 returns to ACT283. Processor 41 detects the undetected distribution data 161 from the distribution data file 16.

[0119] If the store ID of the detected distribution data 161 matches the acquired store ID, processor 111 proceeds to ACT286. Processor 111 checks the distribution flag Fb of the detected distribution data 161 as ACT286. If the distribution flag Fb is "0", that is, if the detected distribution data 161 is distribution data 161 containing notice information outside the distribution period, processor 111 returns to ACT283. Processor 41 detects undetected distribution data 161 from the distribution data file 16.

[0120] If the distribution flag Fb of the detected distribution data 161 is "1", that is, if the detected distribution data 161 is distribution data 161 containing notification information within the distribution period, the processor 111 proceeds to ACT287. The processor 111 stores the detected distribution data in a temporary memory area as ACT287. The processor 111 also increments the count counter r by "1" as ACT288. The temporary memory area is, for example, part of the volatile memory area of ​​the main memory 112. After that, the processor 111 returns to ACT283. The processor 41 detects the undetected distribution data 161 from the distribution data file 16.

[0121] In this manner, the processor 111 repeatedly executes the processes of ACT285 to ACT288 each time it detects a distribution data 161 from the distribution data file 16. After detecting all the distribution data 161, the processor 111 proceeds from ACT284 to ACT289. As ACT289, the processor 111 controls the communication interface 115 to send a response command to the information terminal 40 that sent the notification request command. The response command includes r items of detected distribution data 161 stored in the temporary memory area. With this, the processor 111 terminates the notification request command reception process. The detected distribution data 161 stored in the temporary memory area is cleared after the processing of ACT290.

[0122] Returning to the explanation of Figure 13. The processor 41 of the information terminal 40 that sent the notification request command is waiting for a response command as ACT66. When it receives a response command from the store server 21, the processor 41 stores the notification information for r detected and distributed data included in the response command in area 424 as ACT67. Then, the processor 41 displays the notification screen SCe (see Figure 31) on the touch panel 44 as ACT68.

[0123] Figure 31 is a schematic diagram showing one example of the display on the notification screen SCe. As shown in the figure, the notification screen SCe displays the store name selected on the notification store screen SCd and the text of the notification information stored in area 424. A close button BTi is also displayed. Furthermore, the notification screen SCe displays the number of detected distribution data items r in a circled number along with the store name. This number r matches the circled number that was displayed in association with the store name selected on the notification store screen SCd.

[0124] Returning to the explanation of Figure 13. The processor 41 of the information terminal 40, which is displaying the notification screen SCe, waits for the close button BTi to be input as ACT69. When the close button BTi is input, the processor 41 proceeds to ACT70. As ACT70, the processor 41 clears the notification information stored in area 424. After that, the processor 41 returns to ACT62. That is, the processor 41 returns the screen of the touch panel 44 from the notification screen SCe to the notification store screen SCd. Then the processor 41 enters a waiting state for ACT63 and ACT64.

[0125] If the close button BTh of the notification store screen SCd is pressed while ACT63 and ACT64 are in standby mode, the processor 41 returns to the standby mode of ACT12 and ACT13 as shown in Figure 9.

[0126] Here, the processor 41 realizes the function of a notification unit 416 by executing the processes of ACT61 to ACT65 in Figure 13. The processor 41 also realizes the function of a second acquisition unit 413 by executing the processes of ACT66 and ACT67. Furthermore, the processor 41 realizes the function of an output unit 415 by working in cooperation with the touch panel 44 to execute the process of ACT68 in Figure 13.

[0127] In this way, when a user of the information terminal 40 presses the notification button BTd on the top screen SCa, the touch panel 44 screen changes to the notification store screen SCd. This notification store screen SCd allows the user to see the number of currently valid notification messages for each member store they have set as their favorite store.

[0128] Furthermore, when a user touches any of the store names displayed on the notification store screen SCd, the touch panel 44 screen changes to the notification screen SCe. This notification store screen SCd allows the user to see the content of currently valid notification information from the participating stores of the selected store name. Therefore, with simple operations, the user can check the currently valid notification information for each of their favorite stores. In this way, the user can find out in advance about promotional information such as information on special offers, new products, campaigns, and sales promotions at their favorite stores, and decide which store to go shopping at.

[0129] Now, when a user arrives at their favorite store, they press the "Start Shopping" button BTa on the top screen SCa. When the "Start Shopping" button BTa is pressed, the processor 41 of the information terminal 40 proceeds from ACT21 in Figure 10 to ACT71 in Figure 14. The processor 41 then reads the screen of the touch panel 44 as the reading screen SCf (see Figure 32).

[0130] Figure 32 is a schematic diagram showing one example of the display of the reading screen SCf. As shown in the figure, the reading screen SCf has a frame CM that indicates the code reading area, along with guidance that directs the scanning of the entry code. The entry code is provided, for example, at the entrance of the store. The entry code is a two-dimensional code system that encodes the store's configuration information. The configuration information includes the store ID, in-store LAN data, mobile communication data, etc. The in-store LAN data is the SSID, password, security information, etc., necessary for the information terminal 40 to connect to the access point 27 using wireless LAN. The mobile communication data is the timeout period, number of retries, etc., necessary for the information terminal 40 to communicate with each device of the self-service product registration system 100.

[0131] When a user holds the camera 45 of the information terminal 40 over the entry code so that the entry code fits within the frame CM of the reading screen SCf, the camera 45 reads the entry code. This operation of holding the camera 45 of the information terminal 40 over the entry code is called a check-in operation. After the user has confirmed the reading screen SCf, they perform the check-in operation before starting their shopping.

[0132] The processor 41 of the information terminal 40, which displays the reading screen SCf, waits for a check-in operation to be performed as ACT72. When a check-in operation is performed in this waiting state and the entry code is read by the camera 45, the processor 41 proceeds to ACT73. The processor 41 controls the wireless unit 46 to send a check-in request command as ACT73. With this control, the wireless unit 46 connects to the access point 27 via wireless LAN based on the in-store LAN data obtained from the entry code. After connecting to the access point 27, the wireless unit 46 wirelessly transmits the check-in request command. The check-in request command is received by the access point 27 and sent to the support server 11 via the router 26 of the POS system 20. The check-in request command includes the member ID set in the information terminal 40. The store ID obtained from the entry code is also included in the check-in request command.

[0133] Upon receiving a check-in request command, the processor 111 of the support server 11 begins the information processing procedure shown in the flowchart in Figure 24, which is the so-called check-in request command reception processing. The processor 111 obtains the member ID from the check-in request command as ACT301. The processor 111 also obtains the store ID from the check-in request command as ACT302. Then, as ACT303, the processor 111 creates a new transaction file 51 in the main memory 112 and saves the member ID and store ID obtained from the check-in request command. After that, the processor 111 sends an acceptance response command as ACT304 to the information terminal 40 that sent the check-in request command. With this, the processor 111 terminates the check-in request processing.

[0134] Returning to the explanation of Figure 14. The processor 41, which controls the transmission of the check-in request command, waits for an acceptance response command as ACT74. Upon receiving the acceptance response command via the wireless unit 46, the processor 41 proceeds to ACT75. As ACT75, the processor 41 sets the screen of the touch panel 44 as the registration screen SCg (see Figure 33).

[0135] Processor 41 then obtains the store ID from the entry code as ACT76. Processor 41 then searches the store list 52 stored in area 421 as ACT77 and checks whether the favorite flag Fc associated with the store ID obtained from the entry code is "1". If the favorite flag Fc is "1", meaning the entered store is the user's favorite store, Processor 41 proceeds to ACT78. Processor 41 searches the store list 52 as ACT78 and checks whether the number of distributed data n associated with the store ID obtained from the entry code is "1" or greater.

[0136] If the favorite flag Fc associated with the store ID obtained from the entry code is "1" and the number of data points n is "1" or greater, the processor 41 proceeds to ACT79. As ACT79, the processor 41 adds the notification button BTj (see Figure 33) soft key to the registration screen SCg. If the favorite flag Fc associated with the store ID obtained from the entry code is "0", or the number of data points n is "0", the processor 41 skips the ACT79 process. Therefore, the notification button BTj soft key is not added to the registration screen SCg.

[0137] Figure 33 is a schematic diagram showing one example of the display of the registration screen SCg with the addition of a notification button BTj soft key. As shown in the figure, the registration screen SCg has a scan button BTk, a barcode-less button BTm, and a payment button BTn in addition to the notification button BTj. The registration screen SCg also has a total transaction display area ARa in part of the screen and a detailed list display area ARb for the purchased items in the remaining part. The detailed list display area ARb is divided into, for example, five detail areas and can display information for up to five purchased items, such as product name, tax category, sales amount, and number of items sold. If there are more than six purchased items, the product names, etc., will be removed from the detailed list display area ARb in order of oldest registered purchased items. However, by swiping the detailed list display area ARb up or down, for example, information for older registered purchased items can be displayed in the detailed list display area ARb. The sales amount is calculated by multiplying the price by the number of items sold.

[0138] The notification button BTj is an operator that instructs the user to check notification information. The scan button BTk is an operator that instructs the user to scan the barcode attached to the product. The no-barcode button BTm is an operator that instructs the user to register a product that does not have a barcode. The payment button BTn is an operator that instructs the user to pay the transaction price.

[0139] After confirming the registration screen SCg, the user of the information terminal 40 begins shopping. When the user finds an item to purchase in the store, they check whether the item has a barcode. If the item has a barcode, the user touches the scan button BTk. Touching the scan button BTk changes the screen of the touch panel 44 to the scan screen. The scan screen is a screen with a frame indicating the barcode reading area. The user holds the camera 45 of the information terminal 40 over the item so that the barcode of the item is inside the frame. The barcode is then read by the reading unit of the information terminal 40. Thus, the registration operation for the item with a barcode is performed.

[0140] On the other hand, if the purchased item does not have a barcode, the user touches the "No Barcode" button BTm. Touching the "No Barcode" button BTm displays a list of items without barcodes on the touch panel 44. The user then selects the item they wish to purchase from the list screen. This registers the item that does not have a barcode.

[0141] Additionally, if a user wants to check notification information during their shopping, they touch the notification button BTj. When they finish shopping and want to proceed to checkout, they touch the payment button BTn.

[0142] Returning to the explanation of Figure 14. The processor 41 of the information terminal 40 displaying the registration screen SCg waits for a product registration operation to be performed by touching the scan button BTk or the no-barcode button BTm as ACT80, or by touching the payment button BTn as ACT81, or by touching the notification button BTj as ACT82. If the processing of ACT79 is skipped and the notification button BTj has not been added to the registration screen SCg, the processing of ACT82 is omitted.

[0143] When the aforementioned product registration operation is performed, the product code is entered into the information terminal 40. Upon receiving the product code, the processor 41 proceeds to ACT91 in Figure 15. The processor 41 controls the wireless unit 46 to send a registration request command as ACT91. This control causes the wireless unit 46 to wirelessly transmit the registration request command. The registration request command is received by the access point 27 and sent to the support server 11 via the router 26 of the POS system 20. The registration request command includes the product code, which is the identification information of the purchased product. The registration request command also includes the member ID.

[0144] Upon receiving a registration request command, the processor 111 of the support server 11 begins the information processing procedure shown in the flowchart of Figure 25, which is the so-called registration request command reception processing. The processor 111 obtains the member ID from the registration request command as ACT311. Then, the processor 111 selects the transaction file 51 in which the member ID is stored as ACT312. Hereafter, the selected transaction file will be referred to as the target transaction file 51.

[0145] Processor 111 obtains the product code of the purchased product included in the registration request command as ACT313. Then, as ACT314, Processor 111 obtains product data including the price that is pre-set and associated with the product code. As ACT315, Processor 111 creates product detail data based on the product data and saves it to the target transaction file 51. At this time, Processor 111 increments the number of detail data m in the target transaction file 51 by "1" and calculates the total number of items and the total amount.

[0146] After completing the processing of ACT315, the processor 111 sends an acceptance response command as ACT316 to the information terminal 40 that sent the registration request command. The acceptance response command includes product detail data for m items stored in the target transaction file 51, along with the total number of items and the total amount. With this, the processor 111 finishes processing the information received when the registration request command was received.

[0147] Returning to the explanation of Figure 15. The processor 41, which controls the transmission of the registration request command, waits for the acceptance response command as ACT92. Upon receiving the acceptance response command via the wireless unit 46, the processor 41 proceeds to ACT93. As ACT93, the processor 41 updates the registration screen SCg with the product detail data, total points, total amount, etc., for several m items of detail data included in the acceptance response command. Specifically, the processor 41 displays the total points and total amount in the total display unit ARa. The processor 41 also displays the product name, tax category, sales amount, number of items sold, etc., of the purchased products in each detail area of ​​the detail list display unit ARb. After updating the registration screen SCg, the processor 41 returns to ACT77 in Figure 14. The processor 41 then executes the processing from ACT77 onward in the same manner as described above.

[0148] In the waiting states of ACT80, ACT81, and ACT82 in Figure 14, if the payment button BTn is pressed, the processor 41 proceeds to ACT101 in Figure 16. The processor 41 controls the wireless unit 46 to make a payment request as ACT101. This control causes the wireless unit 46 to wirelessly transmit a payment request command. The payment request command is received by the access point 27 and transmitted to the support server 11 via the router 26 of the POS system 20. The payment request command includes the member ID.

[0149] Upon receiving a settlement request command, the processor 111 of the support server 11 begins the information processing procedure shown in the flowchart in Figure 26, which is the so-called settlement request command reception processing. The processor 111 obtains the member ID from the settlement request command as ACT321. Then, the processor 111 selects the target transaction file 51 in which the member ID is stored as ACT322. The processor 111 creates a unique accounting code as ACT323. Then, the processor 111 saves the accounting code as ACT324 in the target transaction file 51. After that, the processor 111 sends an acceptance response command as ACT325 to the information terminal 40 that sent the settlement request command. The acceptance response command includes the accounting code.

[0150] Returning to the explanation of Figure 16. The processor 41, which controls the transmission of the payment request command, waits for an acceptance response command as ACT102. Upon receiving an acceptance response command via the wireless unit 46, the processor 41 proceeds to ACT103. The processor 41 then sets the screen of the touch panel 44 as the accounting screen SCh (see Figure 34) as ACT013.

[0151] Figure 34 is a schematic diagram showing one example of the accounting screen SCh. As shown in the diagram, the accounting code included in the acceptance response command is displayed as a barcode BC on the accounting screen SCh. A back button BTp is also provided.

[0152] After the customer checks the accounting screen SCh, they scan the barcode BC on the accounting screen SCh using the scanner on the dedicated accounting machine 24. The dedicated accounting machine 24 then sends a payment command to the support server 11. The payment command includes the data from barcode BC, which is the accounting code.

[0153] Upon receiving the settlement command, the processor 111 of the support server 11 retrieves the accounting code from the settlement command. The processor 111 then sends the data from the transaction file 51, in which the accounting code is stored, to the dedicated accounting machine 24 that sent the settlement command. As a result, the transaction details are displayed on the display of the dedicated accounting machine 24, and the user of the information terminal confirms the details and makes the payment. Once the payment is complete, the dedicated accounting machine 24 sends a settlement completion command to the support server.

[0154] After transmitting the data from transaction file 51 to the dedicated accounting machine 24, the processor 111 waits for a settlement completion command. Upon receiving the settlement completion command, the processor 111 sends a settlement termination command to the information terminal 40, which is set with the member ID from transaction file 51.

[0155] Returning to the explanation of Figure 16. The processor 41 of the information terminal 40 displaying the accounting screen SCh waits for a settlement completion command as ACT104. Upon receiving the settlement completion command via the wireless unit 46, the processor 41 proceeds to ACT105. The processor 41 clears the accounting screen SCh as ACT105. After that, the processor 41 returns to ACT5 in Figure 9. Then the processor 41 executes the processing from ACT5 onward in the same manner as described above.

[0156] In the standby states of ACT80, ACT81, and ACT82 in Figure 14, if the notification button BTj is pressed, the processor 41 proceeds to ACT111 in Figure 17. The processor 41 controls the wireless unit 46 to send a notification request command as ACT111. This control causes the wireless unit 46 to wirelessly transmit the notification request command. The notification request command is received by the access point 27 and sent to the support server 11 via the router 26 of the POS system 20. The notification request command includes the member ID set in the information terminal 40. The store ID obtained from the entry code is also included in the notification request command.

[0157] Upon receiving the notification request command, the processor 111 of the support server 11 executes the notification request command reception process shown in the flowchart of Figure 23, as described above. Specifically, the processor 111 obtains the member ID and store ID from the notification request command. The processor 111 then detects the distribution data 161 from the distribution data file 16 in which the store ID matches the store ID obtained from the notification request command and the distribution in progress flag Fb is "1". The processor 111 then controls the communication interface 115 to send a response command containing the detected distribution data 161 to the information terminal 40 that sent the notification request command.

[0158] Returning to the explanation of Figure 17. The processor 41 of the information terminal 40 that sent the notification request command is waiting for a response command as ACT112. When it receives a response command from the store server 21, the processor 41 stores the notification information of the distribution data 161 included in the response command in area 424 as ACT113. Then, the processor 41 displays the notification screen SCe (see Figure 31) on the touch panel 44 as ACT114.

[0159] The processor 41 of the information terminal 40, which is displaying the notification screen SCe, waits for the close button BTh to be input as ACT115. When the close button BTh is input, the processor 41 proceeds to ACT116. The processor 41 clears the notification screen SCe as ACT116. After that, the processor 41 returns to ACT77 in Figure 14. The processor 41 executes the processing from ACT77 onwards in the same manner as described above.

[0160] Here, the processor 41 realizes its function as a identification unit 417 by executing the processes of ACT71 to ACT76 in Figure 14. The processor 41 also realizes its function as a notification unit 416 by executing the processes of ACT77 to ACT79 in Figure 14 and the process of ACT111 in Figure 17, which notifies the support server 11 of the favorite store if the store identified by the identification unit 417 is a favorite store. The processor 41 also realizes its function as a second acquisition unit 413 by executing the processes of ACT112 and ACT113 in Figure 17, which acquires currently valid notification information from the support server among the notification information of the favorite store notified by the notification unit 416. Furthermore, the processor 41 works in cooperation with the touch panel 44 to execute the process of ACT114 in Figure 17, which enables it to function as an output unit 415 that outputs the information acquired by the second acquisition unit 413.

[0161] Thus, when a user of the information terminal 40 goes to a participating store and performs a check-in operation, the registration screen SCg is displayed on the touch panel. At this time, if the store is a favorite store and there is currently valid notification information available from that store, the notification button BTj is displayed on the registration screen SCg. Therefore, the user can easily know that the favorite store they have entered has currently valid notification information because the notification button BTj is displayed on the registration screen SCg.

[0162] When a user touches the notification button BTj, a notification screen SCe, which displays the currently valid notification information, is displayed on the touch panel 44. The notification information displayed on this notification screen SCe is the notification information of the affiliated store the user is currently in. Therefore, users can easily check the currently valid notification information of the affiliated store they are visiting. As a result, they can obtain promotional information such as information on special offers, new products, campaigns, and time sales in real time, which increases the user's willingness to buy and, consequently, enhances the store's sales promotion effect.

[0163] [Differentiation] The above embodiment illustrates how to remove a favorite store from the favorites screen SCc. The method for removing a favorite store is not limited to this. For example, on the merchant list screen SCb, touch the store name displayed with the mark MAa. This merchant is a favorite store. When the store name displayed with the mark MAa is selected by touch, the processor 41 controls the wireless unit 46 to send a removal notification command. By adopting this configuration, the favorite store can be removed from the merchant list screen SCb.

[0164] The notification information is not limited to information related to sales promotion. For example, information regarding the availability of products searched by category, or information regarding the retrieval of pre-ordered products, may be notified to the user of the information terminal 40 as notification information.

[0165] The list of member stores displayed on the member store list screen SCb does not have to be a list of all stores stored in the store data file 15. For example, it may be a list of member stores located near the user using the GPS function of the information terminal 40, or a list of member stores found through keyboard search.

[0166] You could also make it so that touching the notification information displayed on the notification screen SCe will display more detailed information. For example, if the notification information displayed on the notification screen SCe is "New products have arrived," touching this notification information may display a list of the newly arrived products.

[0167] In the above embodiment, an example was given in which the information terminal 40 connects to the in-store network 25 via the access point 27 within the store, and further communicates with the support server 11 of the server system 10 via the communication network 30. In this regard, even within the store, the information terminal 40 may communicate directly with the support server 11 via the communication network 30.

[0168] In addition, several embodiments of the present invention have been described, but these embodiments are presented as examples and are not intended to limit the scope of the invention. These novel embodiments can be carried out in various other forms, and various omissions, substitutions, and modifications can be made without departing from the spirit of the invention. These embodiments and their variations are included within the scope of the invention, as well as within the scope of the invention and its equivalents as described in the claims. The invention described in the original claims of this application is listed below. [1] A portable information terminal for a user to self-input data necessary for registering purchased products at a store, comprising: a setting unit for setting the user's favorite store from among multiple stores; a first acquisition unit for wirelessly acquiring data from a server indicating whether or not each of the multiple stores has information that should be notified to the consumer; and a notification unit for notifying the user's favorite store if, based on the data acquired by the first acquisition unit, the store has information that should be notified to the consumer. [2] An information terminal as described in Appendix [1], further comprising: a second acquisition unit that wirelessly acquires information that the user's favorite stores have that should be notified to the consumer from the server; and an output unit that outputs the information acquired by the second acquisition unit. [3] An information terminal as described in Appendix [2], further comprising: a notification unit that notifies the server of a favorite store designated by the user from among the favorite stores that the notification unit has notified that have information to be notified to the consumer, the second acquisition unit that acquires from the server the information to be notified to the consumer that the favorite stores notified by the notification unit have. [4] An information terminal as described in Appendix [3], further comprising an identification unit that identifies the store entered by the user, and the notification unit further notifies the server of the favorite store if the store identified by the identification unit is the favorite store. [5] The notification unit is an information terminal as described in any one of the appendices [1] to [4], which notifies whenever information that the user's favorite store has to notify the consumer is updated. [6] A program to cause a portable information terminal computer, which allows a user to self-input data necessary for registering purchased items in a store, to function as a setting means for setting a user's favorite store from among several stores, a first acquisition means for wirelessly acquiring data from a server indicating whether or not each of the multiple stores has information that should be notified to the consumer, and a notification means for notifying the user's favorite store if, based on the data acquired by the first acquisition means, the store has information that should be notified to the consumer. [Explanation of symbols]

[0169] 10...Server system, 11...Support server, 14...Member data file, 15...Store data file, 16...Distribution data file, 20...POS system, 21...Store server, 22... Monitoring terminal, 23... POS terminal, 24... Dedicated accounting machine, 27... Access point, 30... Network, 40... Information terminal, 41... Processor, 42... Internal memory, 43... External memory, 44... Touch panel, 45... Camera, 46... Wireless unit, 47... System transmission path 51...Transaction file, 52...Store list, 100...Self-service product registration system, 411...Setting unit, 412...First acquisition unit, 413...Second acquisition unit, 414...Notification unit, 415...Output unit, 416...Notification unit, 417...Specification unit.

Claims

1. A portable information terminal for users to self-enter data necessary for registering purchased items in a store, A settings section where the user can select their favorite store from among multiple stores, A first acquisition unit acquires data from a server via wireless communication that indicates whether or not each of the aforementioned multiple stores has information that should be notified to consumers. A display control unit that displays a screen on a display device which has a first operator for confirming information that the user's favorite store should notify the consumer of, Based on the data acquired by the first acquisition unit, if the user's favorite store has information that should be notified to the consumer, the notification unit notifies by displaying the number of pieces of information to be notified on the first operator; An information terminal equipped with the following features.

2. The information terminal according to claim 1, wherein the display control unit arranges a second operator for deselecting the user's favorite stores together with the first operator on the same screen and displays them on the display device.

3. A second acquisition unit acquires information that the user's favorite store should notify the consumer from the server via wireless communication, An output unit that outputs the information acquired by the second acquisition unit, The information terminal according to claim 1, further comprising:

4. The system further comprises a notification unit that notifies the server of the favorite stores designated by the user from among the favorite stores that the notification unit has notified the consumer that they have information to be notified to the consumer, The information terminal according to claim 3, wherein the second acquisition unit acquires from the server information that the favorite store, notified by the notification unit, has to notify the consumer.

5. A special unit that identifies the store that the aforementioned user entered, Furthermore, it is equipped with, The information terminal according to claim 4, wherein the notification unit further notifies the server of the favorite store if the store identified by the identification unit is the favorite store.

6. The information terminal according to any one of claims 1 to 5, wherein the notification unit notifies whenever information that the user's favorite store has to notify the consumer is updated.

7. A portable information terminal computer that allows users to self-enter data necessary for registering purchased items in stores. A setting method for users to select their favorite store from among multiple stores. A first acquisition means that acquires data from a server via wireless communication indicating whether or not each of the aforementioned multiple stores has information that should be notified to consumers. A display control means that causes a display device to display a screen on which a first operator is placed for confirming information that the user's favorite store should notify the consumer of, and A notification means that, based on the data acquired by the first acquisition means, notifies the user if their favorite store has information that should be notified to the consumer by displaying the number of pieces of information to be notified on the first operator. A program designed to function as such.

Citation Information

Patent Citations

  • User terminal device, information processing device, display control method, information processing method, and program

    JP2017068313A

  • Terminal management apparatus and program therefor

    JP2019153088A

  • Information processing device, information processing system, information processing method and information processing program

    JP2021051510A

  • Product sales data processing device, product sales data processing system, and program

    JP2021120797A

  • Store system, notification method, and program

    JP2022045611A