JP7559905B2 - Management server, management system, control method and storage medium - Google Patents

Description

The present invention relates to updating member information.

A system is known as a product sales system for customers who visit a store to purchase products, in which the customer uses a mobile terminal such as a smartphone owned by the customer to read the barcode of the product, register the product, and make the payment. For example, Patent Document 1 discloses a self-shopping system that includes a mobile terminal that acquires product information of the product to be purchased and transmits payment information including all the acquired product information to a management server, and a management server that generates and outputs sorted detailed information that lists the names of products in descending order of price based on the product information included in the payment information.

Patent document 2 also discloses a system that awards points accrued in past payments made with credit cards or electronic money to customers who use services using point cards, based on payment identification information that identifies the payment and card identification information that identifies the point card.

JP 2013-41354 A JP 2018-055564 A

In recent years, there have been systems that provide services that link a dedicated application with a membership card such as a point card. This type of service has the advantage that the points owned can be checked using the dedicated application, but if the membership card is lost, the application must be uninstalled and the membership must be registered again. Patent Document 2 discloses a method for smoothly adding points later, but does not disclose any method for re-registering a membership card such as a point card when it is lost.

The object of the present invention is to provide a management server, a management system, a control method, and a storage medium that enable smooth re-registration of membership cards.

One aspect of the management server is a management server,
a receiving means for receiving a registration request including a card number of a membership card and user identification information for identifying a user of the terminal device from the terminal device used by the member;
an extracting means for extracting member information corresponding to the member from a member information database based on the user identification information ;
an updating means for not updating the member information when a card number identical to the card number included in the registration request is registered in the member information, and for updating the member information with the card number included in the registration request when the card number indicated by the member information differs from the card number included in the registration request;
has.

One aspect of the control method includes:
A control method executed by a management server, comprising:
receiving a registration request from a terminal device used by a member, the registration request including a card number of the member card and user identification information for identifying a user of the terminal device ;
Extracting member information corresponding to the member from a database of member information based on the user identification information ;
If the same card number as the card number included in the registration request is registered in the member information, the member information is not updated, and if the card number indicated by the member information differs from the card number included in the registration request, the member information is updated with the card number included in the registration request.

One aspect of the program is
a receiving means for receiving a registration request including a card number of a membership card and user identification information for identifying a user of the terminal device from the terminal device used by the member;
an extracting means for extracting member information corresponding to the member from a member information database based on the user identification information ;
If the same card number as the card number included in the registration request is registered in the member information, the member information is not updated, and if the card number indicated by the member information differs from the card number included in the registration request, the computer functions as an update means for updating the member information using the card number included in the registration request.

According to the present invention, it is possible to smoothly re-register a membership card by utilizing existing membership information.

1 shows a configuration of a management system according to a first embodiment. 2 shows a schematic configuration of a POS server. 2 shows a schematic configuration of a management server. 2 shows a schematic configuration of a mobile terminal. 2 shows a schematic configuration of a member server. 1 shows the schematic configuration of an accounting machine. 13 is a flowchart of a product purchasing process. 13 is a flowchart of a store entry process. 13 is a flowchart of a product selection process. 13 is a display example of a purchase product list screen. 13 is a flowchart of an accounting process. 13 is a display example of a payment method selection screen. 13 is an example of a display screen of a cashier. 1 shows an example of a data structure of a member information database. 1 shows an example of a data structure of a card information database. 13 is a display example of a membership card registration screen. 13 is an example of a flowchart illustrating a procedure for a card number registration process. 13 shows a schematic configuration of a management server according to a second embodiment.

The following describes a preferred embodiment of the present invention with reference to the drawings.

First Embodiment
(1) Management system configuration
1 shows the configuration of a management system 100 according to this embodiment. The management system 100 mainly comprises a POS server 1, a management server 2, a mobile terminal 3, a member server 4, and a payment machine 5. In the management system 100, a customer using a mobile terminal 3 registers a product to be purchased (also called a "purchased product") by reading a product barcode 7 attached to the product in a store 8 where the product is sold, and then settles the payment using the payment machine 5 in the store 8 or by electronic payment.

The POS server 1 is a server that manages various sales information such as product information including prices and stock status of products sold at the store 8, and sales information of the store 8. The POS server 1 is capable of communicating with the management server 2 and the accounting machine 5 via a network or the like. The POS server 1 may be one that collectively manages the sales information of multiple affiliated stores, or it may be one that exists for each store and manages only the sales information of that store.

The management server 2 is a server device that controls the mobile terminal 3 and the payment machine 5, and is capable of communicating with the mobile terminal 3, the member server 4, and the payment machine 5 via a network or the like. The management server 2 obtains from the POS server 1 and stores information necessary for display control of the mobile terminal 3. The management server 2 transmits display information for the mobile terminal 3 to display various screens. The various screens mentioned above include a screen (also called the "purchased item list screen") that displays a list of purchased items (called the "purchased item list") registered by the mobile terminal 3 by reading the product barcode 7, together with the selling price. The management server 2 also obtains information about members from the member server 4, and transmits information to the member server 4 to update the information stored in the member server 4.

The management server 2 may be composed of multiple server devices. For example, the management server 2 may be composed of a server device that mainly performs interface operations with the mobile terminal 3, such as sending and receiving data to and from the mobile terminal 3, and a server device that stores and manages various information such as information obtained from the POS server 1 and a list of purchased items. In this case, the former server device functions as a so-called application server, and the latter server device functions as a so-called database server. In this case, these server devices send and receive information required to execute the processes assigned to them via a network, etc.

The mobile terminal 3 is used by customers who shop at the store 8, and has functions such as reading product barcodes 7 attached to products, and acquiring and displaying various screens such as a purchased product list screen by communicating with the management server 2. Note that for the sake of convenience, only one mobile terminal 3 is shown in FIG. 1, but in reality there are as many mobile terminals as there are customers in the store 8.

The member server 4 stores information about members and information about member cards to be issued to members. The member server 4 is capable of communicating with the management server 2 via a network or the like. The management server 2 may also function as the member server 4. In this case, the management server 2 stores information about members and member cards stored by the member server 4, etc.

The accounting machine 5 is a payment machine (a so-called self-payment machine) that allows a customer to settle a bill using a mobile terminal 3. The accounting machine 5 can communicate with the management server 2, and exchanges various information required for settlement with the management server 2 and, if necessary, with the POS server 1. The accounting machine 5 is equipped with a barcode reader 56 for reading a billing barcode (described later) from the customer's mobile terminal 3, and a light 57 for calling a store clerk.

(2) Device configuration
Next, the configuration of the POS server 1, management server 2, mobile terminal 3, member server 4 and payment machine 5 will be described with reference to FIGS.

(2-1) POS Server Fig. 2 shows the schematic configuration of the POS server 1. The POS server 1 mainly comprises a memory unit 13, a communication unit 14 for data communication, and a control unit 15. These elements are interconnected by a bus line 10.

The storage unit 13 is composed of a memory such as a hard disk or a flash memory. The storage unit 13 stores the programs executed by the control unit 15, and information necessary for the control unit 15 to execute a predetermined process by executing the programs. In this embodiment, the storage unit 13 includes selling price change information 17, a product information DB (database) 18, and sales information 19, which is information related to product sales. Note that the storage unit 13 may store various types of sales-related information other than the selling price change information 17, the product information DB 18, and the sales information 19.

Product information DB18 is a database of information about products handled at store 8 or affiliated stores including store 8. Product information DB18 includes various information such as product price, information for identifying products such as JAN (Japanese Article Number) code (also referred to as "product identification information"), product classification information, and product inventory status.

The selling price change information 17 is information related to a change in selling price. Specifically, the selling price change information 17 includes at least one of any discount information or discount information such as category discount information, bundle discount information, set discount information, total amount discount information, category discount information, bundle discount information, set discount information, and total amount discount information.

The control unit 15 includes a CPU (Central Processing Unit), a ROM (Read Only Memory), and a RAM (Random Access Memory), all of which are not shown, and performs various controls on the components within the POS server 1. For example, the control unit 15 updates the sales information 19 by communicating with the accounting machine 5 via the communication unit 14. The control unit 15 also communicates with the management server 2 via the communication unit 14, sending information about price change information 17 and the product information DB 18 to the management server 2.

(2-2) Management Server Fig. 3 shows a schematic configuration of the management server 2. The management server 2 mainly comprises a storage unit 23, a communication unit 24, and a control unit 25. These elements are connected to each other via a bus line 20.

The storage unit 23 is composed of a memory such as a hard disk or a flash memory. The storage unit 23 stores the programs executed by the control unit 25 and information necessary for the control unit 25 to execute a predetermined process by executing the programs. In this embodiment, the storage unit 23 stores selling price change information 27, a product information DB 28, and a purchased product list DB 29.

Similar to price change information 17, price change information 27 is information relating to changes in price resulting from a discount or reduction. Based on the control of control unit 25, price change information 27 is updated periodically or irregularly so as to be synchronized with price change information 17 stored in POS server 1. Similar to product information DB 18, product information DB 28 is a database of information relating to products. Based on the control of control unit 25, product information DB 28 is updated periodically or irregularly so as to be synchronized with product information DB 18 stored in POS server 1.

The purchased item list DB29 is a database of purchased item lists for each mobile terminal 3 of customers who are shopping at the store 8. The purchased item list is a list that includes, for example, item identification information indicating the items to be purchased and the planned purchase quantity of the items, and is associated with information that identifies the mobile terminal 3 or the customer who uses the mobile terminal 3 (also referred to as "customer identification information"). The purchased item list is updated each time a purchased item is added, deleted, or the quantity is changed based on the operation of the mobile terminal 3.

The communication unit 24 communicates with the POS server 1, the mobile terminal 3, and the payment machine 5 via wired or wireless communication. The control unit 25 includes a CPU, ROM, RAM, etc. (not shown), and performs various controls on each component in the management server 2. The processing executed by the control unit 25 will be described later.

(2-3) Portable Terminal Fig. 4 shows a schematic configuration of the portable terminal 3. The portable terminal 3 mainly includes a display unit 31, an input unit 32, a storage unit 33, a communication unit 34, a control unit 35, and a reading unit 36. These elements are connected to each other via a bus line 30.

The display unit 31 displays various information such as a list of purchased items and an accounting barcode under the control of the control unit 35. The input unit 32 is an interface that accepts user input, and may be, for example, a touch panel, a button, or a voice input device.

The storage unit 33 is composed of a memory such as a hard disk or a flash memory. The storage unit 33 stores the programs executed by the control unit 35, and information necessary for the control unit 35 to execute a predetermined process by executing the programs. For example, the storage unit 33 stores an application program (hereinafter also referred to as a "dedicated app") provided by the store 8 or the company (organization) that manages the store 8. The dedicated app is launched when shopping at the store 8, and controls the display of various screens such as a purchase item list screen.

The communication unit 34 communicates with the management server 2 via wireless communication. The control unit 35 includes a CPU, ROM, RAM, etc. (not shown), and performs various controls on the components within the mobile terminal 3. The controls performed by the control unit 35 will be described later.

The reading unit 36 is an optical device such as a camera, which reads the product barcode 7 attached to the product and supplies the read information to the control unit 35. In this embodiment, the control unit 35 obtains product identification information such as a JAN code from the product barcode 7 attached to the product based on the information output by the reading unit 36.

(2-4) Member Server Fig. 5 shows a schematic configuration of the member server 4. The member server 4 mainly comprises a memory unit 43, a communication unit 44, and a control unit 45. These elements are connected to each other via a bus line 40.

The memory unit 43 is composed of a memory such as a hard disk or a flash memory. The memory unit 43 stores the programs executed by the control unit 45 and information necessary for the control unit 45 to execute a predetermined process by executing the programs. In this embodiment, the memory unit 43 mainly stores a member information DB 47 and a card information DB 48.

The member information DB47 is a database of member information for each member who has completed the membership procedure. The member information includes general attribute information such as name, sex, and date of birth, as well as member-specific attribute information such as card number, member rank, and number of accumulated points. The card number is an identification number for the member card, and the member card is a point card that is given to a member by applying to become a member at a counter or the like provided in the store 8. In addition, in order to be given a member card, the applicant is required to fill out an application form in which personal information such as name is written. The member card has the card number assigned to the card and a PIN code for determining the validity of the card number printed on it. In addition, there are main members who are normal members who are not subordinate to other members, and family members who are subordinate to the main member, and the member cards include main member cards given to main members and family cards given to family members. The main member and family members share points given according to shopping, etc.

Card information DB48 is a database related to member cards. For example, card information DB48 contains a combination of a card number assigned to a member card that may be issued and a PIN number for verifying the validity of the card number. Card information DB48 also contains information regarding the validity of each member card. In addition, the card number of a family card that may be issued is associated with the card number of a main member card that shares points with the family card.

The communication unit 44 communicates with the management server 2 etc. via wired or wireless communication. The control unit 45 includes a CPU, ROM, RAM, etc. (not shown), and performs various controls on each component in the member server 4.

(2-5) Payment Machine Fig. 6 shows the schematic configuration of the payment machine 5. The payment machine 5 mainly comprises a display unit 51, an input unit 52, a memory unit 53, a communication unit 54, a control unit 55, a barcode reader 56, a light 57, and a speaker 58. These elements are connected to each other via a bus line 50.

The display unit 51 displays various information such as a payment method selection screen and a closing screen under the control of the control unit 55. The input unit 52 is an interface that accepts customer input, and includes, for example, a touch panel and buttons.

The storage unit 53 is composed of a memory such as a hard disk or a flash memory. The storage unit 53 stores the programs executed by the control unit 55, and information necessary for the control unit 55 to execute a predetermined process by executing the programs. For example, the storage unit 53 stores a dedicated application program that operates when a customer makes a payment and performs accounting processing.

The control unit 55 includes a CPU, ROM, and RAM (not shown), and performs various controls on each component within the payment machine 5. The controls performed by the control unit 55 will be described later. The barcode reader 56 reads the payment barcode displayed on the customer's mobile terminal 3 at the time of payment, and supplies the read information to the control unit 55. The light 57 turns on when a malfunction occurs in the payment machine 5 or when a store clerk needs to be called. The speaker 58 outputs operation sounds and voice messages to call attention as necessary.

(3) Product purchase processing
Next, an overview of the product purchase process by the management system 100 will be described. The product purchase process is a process in which a customer purchases a product in the store 8 using the mobile terminal 3. FIG. 7 is a flowchart showing an overview of the product purchase process. The product purchase process is broadly divided into a store entry process S100, a product selection process S200, and a checkout process S300. The product purchase process is mainly realized by the management server 2, the mobile terminal 3, and the checkout machine 5 each executing a program prepared in advance.

(3-1) Store Entry Processing First, the store entry processing will be described. The store entry processing is a process that is performed when a customer enters the store 8 and prior to purchasing a product, and corresponds to preparation for purchasing a product. Fig. 8 is a flowchart showing an example of the store entry processing. This processing is performed by the mobile terminal 3 and the management server 2.

First, when a customer enters the store 8, they read the store barcode using the mobile terminal 3 (step S101). The store barcode is attached to a predetermined location within the store 8, for example, a wall near the store entrance or on a card used for shopping. When the customer reads the store barcode, the mobile terminal 3 obtains the store ID from the read store barcode and sends it to the management server (step S102). When sending the store ID, the mobile terminal 3 also sends customer identification information that identifies the mobile terminal 3 or the customer using the mobile terminal 3. Note that in the product selection process and checkout process described below, the mobile terminal 3 basically sends customer identification information to identify itself when sending any information to the management server 2.

The management server 2 receives the store ID from the mobile terminal 3 and obtains the selling price list of that store from the product information DB 28 (step S104). This is because the selling prices of products differ from store to store. The management server 2 then transmits store information including the store name and sales information of that store to the mobile terminal 3 (step S105), and the mobile terminal 3 receives the store information (step S106). As a result, the current store name and sales information of that store are displayed on the display unit 31 of the mobile terminal 3, and the customer is ready to start shopping. The store information transmitted by the management server 2 includes information indicating the transaction status of the customer at that store, and when a new purchase is started at that store, the transaction status becomes new. On the other hand, if the customer stops shopping at that store for some reason, a purchased product list screen corresponding to the previous transaction status is displayed on the mobile terminal 3.

(3-2) Product Selection Process Next, the product selection process will be described. The product selection process is a process in which a customer reads a product barcode attached to a product using the mobile terminal 3 and registers the product in a purchased product list. Fig. 9 is a flowchart of the product selection process. This process is executed by the mobile terminal 3 and the management server 2.

First, when a customer finds an item they wish to purchase, they switch the mobile terminal 3 to item reading mode and use the mobile terminal 3 to read the item barcode attached to the item (step S201: Yes). The mobile terminal 3 sends the item identification information of the read item to the management server 2 (step S202). At this time, the item quantity is automatically set to "1". When the management server 2 receives the item identification information from the mobile terminal 3 (step S203), it updates the purchased item list and sends it to the mobile terminal 3 (step S204). The mobile terminal 3 receives the updated purchased item list and displays it on the display unit 31 (step S205). As a result, the newly added item and its quantity are added to the purchased item list and displayed on the mobile terminal 3.

Next, if necessary, the customer operates the mobile terminal 3 to change the quantity of the product, and the mobile terminal 3 acquires the changed quantity (step S206: Yes). When the product barcode is first read, the quantity of that product is automatically set to "1", but if the customer purchases multiple copies of the same product, the quantity can be changed by operating the mobile terminal 3. Once the changed quantity is set, the mobile terminal 3 transmits the product identification information of the product to be changed and the changed quantity to the management server 2 (step S207).

When the management server 2 receives the product identification information and the changed quantity from the mobile terminal 3 (step S208), it updates the purchased product list and sends it to the mobile terminal 3 (step S209). The mobile terminal 3 receives the updated product list and displays it on the display unit 31 (step S210). This causes the quantity change to be reflected in the purchased product list.

The mobile terminal 3 then determines whether or not the customer has pressed the payment button (step S211). The payment button is the button that the customer presses when they finish shopping. If the payment button has not been pressed (step S211: No), the process returns to step 201. In this way, the customer can continue shopping by adding products or changing the quantity until the payment button is pressed. Then, when the payment button is pressed (step S211: Yes), the product selection process ends.

Figure 10 shows an example of a purchased item list screen displayed on the mobile device 3. In this example, the purchased item list screen has a product read button 90, a list display field 91, a subtotal display field 92, a total amount display field 93, a home screen transition button 94, a payment button 95, and a transaction cancellation button 96.

When the mobile terminal 3 detects that the product reading button 90 has been selected by a tapping operation or the like, it switches the display on the display unit 31 to the product reading screen. On the product reading screen, the mobile terminal 3 displays images and the like acquired from the activated reading unit 36. This allows the customer to move the product or the mobile terminal 3 so that the product barcode 7 is within the reading range of the reading unit 36, and read the product barcode 7.

In the list display field 91, the name, quantity, and price of each purchased item are displayed. In addition, a quantity decrease button 97 and a quantity increase button 98 are displayed for each purchased item in the list display field 91. Then, when the mobile terminal 3 accepts a change in the quantity of a purchased item using the quantity decrease button 97 or quantity increase button 98, it transmits, for example, the product identification information of the purchased item whose quantity has been changed and the changed quantity to the management server 2.

The subtotal display field 92 displays the subtotal of the sales prices of all items in the purchased item list excluding tax, and the total amount display field 93 displays the total of the sales prices of all items in the purchased item list including tax. The management server 2 calculates these subtotals or total amounts based on the prices of the purchased items registered in the product information DB 28, specifically, the sales price list of the store obtained by the store entry process.

When the mobile terminal 3 detects that the home screen transition button 94 has been selected, it sends a request to display the home screen to the management server 2, and displays a specific home screen based on the display information received in response. The home screen may display information about discounts and discounts at the store 8, registration information for the customer of the mobile terminal 3, etc.

When the mobile terminal 3 detects that the payment button 95 has been selected, it sends a payment request to the management server 2, and displays a payment screen including a payment barcode screen, which will be described later, based on the display information received in response. In addition, when the mobile terminal 3 detects that the transaction cancellation button 96 has been selected, it sends information to the management server 2 notifying the cancellation of the transaction. In this case, the management server 2 deletes the purchased item list corresponding to the mobile terminal 3.

(3-3) Payment Processing Next, the payment processing will be described. The payment processing is a process for making payment for the products selected by the customer in the product selection process. Fig. 11 is a flowchart of the payment processing. This process is executed by the mobile terminal 3, management server 2, and payment machine 5.

First, when the payment button 95 is pressed, the mobile terminal 3 sends a payment request to the management server 2 (step S301). When the management server 2 receives the payment request (step S302), it calculates the payment amount based on the current purchase item list (step S303). Furthermore, the management server 2 generates a payment barcode (step S304). The payment barcode is information that uniquely identifies the purchase indicated by the current purchase item list. In one example, the payment barcode can be a random code that is uniquely associated with the purchase at that time. In this case, the payment barcode serves as an inquiry number for payment information. The management server 2 sends a payment screen including the payment amount calculated in step S303 and the payment barcode generated in step S304 to the mobile terminal 3 (step S305).

The mobile device 3 displays the received payment screen on the display unit 31. Figure 12 is an example of the payment screen. In this example, the payment screen includes a billing barcode 37, a total amount field 38, and a done button 39. The customer moves to the billing machine 5 with the mobile device 3 displaying the payment screen and reads the billing barcode with the barcode reader 56 (step S307). The billing machine 5 displays a payment method selection screen based on the read billing barcode (step S308). Specifically, the billing machine 5 sends the inquiry number indicated by the billing barcode to the management server 2 and acquires payment information. The payment information includes the total amount and details such as the IDs and quantities of all items in the purchase item list. The billing machine 5 displays the payment method selection screen based on the acquired payment information.

Figure 13 (A) shows an example of the payment method selection screen. The payment method selection screen includes a total amount field 61, a cash button 62, and a credit button 63. The customer looks at the payment method selection screen, confirms the payment amount, and presses either the cash button 62 or the credit button 63 to make the payment. This completes the settlement of the purchase price (step S309). Specifically, if the customer selects to pay with cash, the accounting machine 5 prompts the customer to insert cash into the cash slot, and once the cash has been inserted, gives change as necessary. Also, if the customer selects to pay with credit, the accounting machine 5 prompts the customer to insert a card, and as necessary, prompts the customer to enter a PIN number or the like, and completes the credit settlement.

When the payment is completed, the payment machine 5 displays a payment completion screen. FIG. 13(B) shows an example of the payment completion screen. In this example, the payment completion screen includes a payment information field 64, a receipt button 65, and an end button 66. Note that FIG. 13(B) shows an example in which the customer selects credit card payment, and the payment information field 64 displays information such as the payment amount and the payment method. The receipt button 65 is a button for printing out a receipt. The end button 66 is a button for the customer to confirm that the payment process has been completed. When the customer presses the end button 66, the payment machine 5 reports to the management server 2 that the payment has been completed, and returns the display of the display unit 51 to the main menu. Note that the completion button 39 is also displayed on the payment screen shown in FIG. 12, and when the payment process is completed, the customer presses the completion button 39 on the payment screen. When the completion button 39 is pressed, the mobile terminal 3 reports to the management server 2 that the payment has been completed, and returns the display unit 31 to the main menu.

In the above example, the accounting barcode is simply an inquiry number for payment information, and the accounting machine 5 uses this inquiry number to obtain payment information from the management server 2. Alternatively, the accounting barcode may include payment information. That is, the management server 2 generates an accounting barcode using the total amount and details of purchased items based on the contents of the purchase item list at that time. In this case, the accounting machine 5 can obtain payment information by reading and decrypting the accounting barcode, so there is no need to communicate with the management server 2 to obtain payment information. That is, the accounting machine 5 simply extracts the total amount from the reading accounting barcode and displays the payment method selection screen.

(4) Re-registering your membership card
Next, the process for re-registration of a membership card in the management system of the first embodiment will be described. In summary, when the management server 2 receives a request to register the card number of a membership card from a mobile terminal 3 used by a member whose card number has already been registered, the management server 2 updates the member information with the card number specified in the registration request. This allows the management server 2 to utilize the existing member information when reissuing a membership card to a member who has lost their membership card, suitably simplifying the process of re-registering the member information.

(4-1) Data Structure Fig. 14 shows an example of the data structure of member information DB 47 in embodiment 1. Member information DB 47 is a database that records member information for each member, and mainly has the following items: "card number,""membertype,""memberrank,""name,""gender,""accumulatedpoints,""previous card number,""related card number," and "app ID."

"Card number" indicates the card number assigned to the membership card given to the target member. "Member type" indicates whether the target member is a primary member or a family member. "Member rank" indicates the rank (status) of the target member. Note that the member rank is the standard for determining the point award rate and discount rate that are awarded to each member when they purchase products at store 8, and is determined, for example, by the amount of purchases over a specified period (e.g., yearly or monthly). "Name" and "Gender" indicate the name and gender, respectively, of the target member.

"Accumulated points" indicates the number of points accumulated by the target member. In the example of FIG. 14, the family member shares points with the primary member linked to the family member, and the accumulated points of the family member are aggregated into the accumulated points of the primary member linked to the family member. For example, the accumulated points of the family member "Dainippon Hanako" are aggregated into the accumulated points of the primary member "Dainippon Taro" to whom the family member is subordinate, so there is no record of accumulated points in the "Accumulated points" item for "Dainippon Hanako". In place of this recording method, the management server 2 may synchronize the contents of the "Accumulated points" of the family member so that they are the same as the contents of the "Accumulated points" of the primary member to whom the family member is subordinate. In this case, when there is a change in the "Accumulated points" of either the family member or the primary member, the management server 2 also changes the "Accumulated points" of the other to be the same.

"Previous card number" indicates the card number assigned to a member card previously held by the target member. In other words, "previous card number" indicates the card number recorded in the "card number" field before it is updated with the card number of the reissued member card. For example, if a member loses a member card and re-registers the member card, the management server 2 overwrites the "card number" with the card number of the newly registered member card, and records the card number of the member card recorded in the member information DB 47 until just before in "previous card number". In the example of Figure 14, "Suzuki Hajime" lost his member card with card number "10003", and is re-registering his member card with card number "11347". In this case, the card number "11347" of the re-registered member card is recorded in "card number", and the card number "10003" of the lost member card is recorded in "previous card number". In addition, the membership card with card number "10003" registered in "Previous Card Number" becomes an invalid membership card that cannot be used at store 8.

"Related card number" indicates the card number of a family member subordinate to the target member, or of the primary member to which the target member is subordinate if the target member is a family member. For example, the "related card number" of primary member "Dainippon Taro" records the card number "10004" of related family member "Dainippon Hanako". On the other hand, the "related card number" of family member "Dainippon Hanako" records the card number "10001" of related primary member "Dainippon Taro". In this case, for example, when the management server 2 registers the record of the family member to whom a family card has been issued in member information DB 47, it updates the "related card number" item of the primary member to which the family member is subordinate.

The "app ID" is identification information for the dedicated app installed on the mobile device 3 used by the target member. The app ID is identification information that is different for each mobile device 3 on which the dedicated app is installed.

Here, a supplementary explanation will be given on the registration process of the "app ID". The management server 2 communicates with the mobile terminal 3 that has started the dedicated app, and when the management server 2 first associates the member using the mobile terminal 3 with a record in the member information DB 47, it registers the app ID received from the mobile terminal 3 in the "app ID" field. In this case, for example, based on information sent from the terminal of the store 8 when applying for a membership card, the management server 2 registers a record of member information including the card number of the member card to be issued and application information such as name in the member information DB 47. After that, when the mobile terminal 3 of the customer to whom the membership card is issued is connected to the management server 2 by the dedicated app, the management server 2 extracts a record of member information corresponding to the member using the mobile terminal 3 from the member information DB 47 based on information such as the card number supplied from the mobile terminal 3. The management server 2 then registers the app ID obtained from the mobile terminal 3 in the extracted record.

In this way, member information DB47 includes items indicating general attribute information including "name" and "gender", as well as items indicating member-specific attribute information including "card number", "member type", "member rank", "accumulated points", "previous card number", "related card number", "app ID", etc.

The data structure of member information DB47 shown in FIG. 14 is an example, and various modifications may be made to this data structure. For example, member information DB47 may include items indicating various general attribute information such as "name" and "gender", as well as date of birth, address, telephone number, email address, family structure, occupation, etc. Furthermore, information equivalent to "previous card number" and "related card number" may be included in card information DB48 instead of member information DB47. Furthermore, member information DB47 may include an item for recording identification information (e.g., terminal ID) related to the mobile terminal 3 used by the target member, instead of "app ID".

Figure 15 shows an example of the data structure of card information DB48. Card information DB48 is a database that records information for each member card, and mainly has the following fields: "card number," "PIN code," "card type," and "status."

"Card number" indicates the card number assigned to the target member card. "PIN code" indicates the PIN code assigned to the target member card, and is written, for example, on the back of the target member card or on a paper enclosed with the member card. "Card type" indicates the type of the target member card, specifically, whether it is a main member card or a family member card. "Status" indicates the status of the target member card. For example, the card number recorded in "Card number" in the member information DB 47 of FIG. 14 is set to "valid state". On the other hand, the card number linked to the member as "previous card number" in the member information DB 47 of FIG. 14 is set to "invalid state". A member card set to "invalid state" cannot accumulate or use points for shopping, etc., or newly link the card number to member information. In addition to "valid" and "invalid", a state such as "pre-issued" indicating that the member card is not yet issued may be specified for "status".

(4-2) Specific Example Next, the operation of the portable terminal 3 for re-registration of a membership card will be described with reference to an example of a display screen of the portable terminal 3 in FIG.

Figure 16 is an example of a member card registration screen that the mobile terminal 3 displays based on the display information received from the management server 2. The member card registration screen includes a card number input field 71, a PIN code input field 72, and a complete button 73.

First, a customer who is the user of the mobile terminal 3 loses his/her issued membership card and goes through a prescribed procedure at the store 8 (including filling out an application form with personal information) to obtain a new membership card. In this case, the customer launches a dedicated app on the mobile terminal 3 and selects a prescribed menu on the mobile terminal 3, causing the mobile terminal 3 to display the membership card registration screen shown in FIG. 16. In this case, after launching the dedicated app, the mobile terminal 3 displays the membership card registration screen based on user input and accepts input of a card number in the card number input field 71 and input of a PIN code (personal identification number) in the PIN code input field 72. The card number and PIN code to be entered in the card number input field 71 and the PIN code input field 72 are written on the back of the reissued membership card, for example.

When a request to display the member card registration screen is received, the mobile terminal 3 may activate the reading unit 36 attached to the mobile terminal 3 and display an image or the like generated by the reading unit 36 on the member card registration screen, instead of displaying the card number input field 71 and the PIN code input field 72. In this case, for example, the member card may have a one-dimensional or two-dimensional barcode indicating the card number attached thereto, and the mobile terminal 3 may obtain the card number by reading the barcode based on the information generated by the reading unit 36. In this case, after recognizing the card number, the mobile terminal 3 displays the member card registration screen with the read card number displayed in the card number input field 71.

When the mobile terminal 3 detects the selection of the complete button 73 with the card number and PIN code entered in the card number input field 71 and the PIN code input field 72, it transmits a signal (also called a "card number registration request") requesting the registration of the card number to the management server 2. In this case, the card number registration request includes information for the management server 2 to identify the user who uses the mobile terminal 3 (also called "user identification information") in addition to the card number and PIN code entered in the card number input field 71 and the PIN code input field 72. This user identification information may be an application ID, or any member information registered in the member information DB 47 such as a name or date of birth, or a combination thereof. When the management server 2 receives a card number registration request from the mobile terminal 3, it authenticates the card number included in the card number registration request and updates the member information DB 47 with the card number. Details of the process executed by the management server 2 based on the card number registration request will be described in detail with reference to the process flow of FIG. 17.

(4-3) Processing flow
FIG. 17 is an example of a flowchart showing a procedure of a card number registration process.

First, when a user of the mobile terminal 3 is issued a membership card by the store 8 and has the membership card in hand, the user launches a dedicated app on the mobile terminal 3 and causes the mobile terminal 3 to display a membership card registration screen such as that shown in FIG. 17 based on a menu selection operation in the dedicated app. The mobile terminal 3 then accepts input of the card number of the issued membership card and a personal identification number such as a PIN code for authenticating the card number on the membership card registration screen. Note that instead of accepting user input, the mobile terminal 3 may read at least one of the card number and personal identification number of the membership card using the reading unit 36.

Then, the mobile terminal 3 transmits a card number registration request including the input information input in step S401 to the management server 2 (step S402). In this case, the mobile terminal 3 may include user identification information such as an app ID in the card number registration request. Note that if the management server 2 authenticates the mobile terminal 3 immediately after the dedicated app is launched, and thus the management server 2 already recognizes the record in the member information DB 47 corresponding to the user of the mobile terminal 3, the card number registration request does not need to include user identification information.

When the management server 2 receives a card number registration request from the mobile terminal 3, the management server 2 refers to the card information DB 48 and authenticates the card number included in the card number registration request using the PIN included in the card number registration request (step S411). In this case, for example, the management server 2 refers to the card information DB 48 and determines whether the card number included in the card number registration request is valid and whether the above-mentioned PIN is correct. Note that if the authentication in step S411 is not successful (i.e., the card number is invalid or the PIN is incorrect), the management server 2 proceeds to step S414 and sends a response to the mobile terminal 3 indicating that the authentication was not successful.

Next, if the authentication in step S411 is successful, the management server 2 extracts from the member information DB 47 the member information corresponding to the user of the mobile terminal 3 that made the card number registration request, based on the user identification information, etc., included in the card number registration request. The management server 2 then determines whether a card number different from the card number specified in the card number registration request has already been registered in the member information DB 47 (step S412). That is, the management server 2 determines whether the card number indicated by the member information extracted from the member information DB 47 is different from the card number specified in the card number registration request.

If a card number different from the card number specified in the card number registration request has already been registered in the member information DB 47 (step S412; Yes), the management server 2 updates the member information in the member information DB 47 corresponding to the user of the mobile terminal 3 with the card number specified in the card number registration request (step S413). For example, if the member information DB 47 has the data structure shown in FIG. 14, the management server 2 records the card number specified in the card number registration request in "card number", and records the card number that was previously recorded in "card number" in "previous card number".

Preferably, management server 2 also considers the card number (previous card number) that was recorded in member information DB 47 until just before to be the card number of the lost member card, and registers information to the effect that the member card with that card number is invalid in card information DB 48. This makes it possible to preferably prevent a third party who finds a lost member card from using the member card to register as a member or make purchases, etc.

On the other hand, if a card number different from the card number specified in the card number registration request has not been registered in the member information DB 47 (step S412; No), the management server 2 proceeds to step S414. For example, when a card number identical to the card number specified in the card number registration request is registered in the member information corresponding to the user of the mobile terminal 3, the management server 2 assumes that the card number has not changed and does not update the member information DB 47. In another example, if card number information is not registered in the member information corresponding to the user of the mobile terminal 3, the management server 2 adds the card number specified in the card number registration request to the target member information.

Then, the management server 2 transmits a response signal to the card number registration request to the mobile terminal 3 that is the sender of the card number registration request (step S414). In this case, when the management server 2 executes step S413, it transmits display information to the mobile terminal 3 to display information that the card number of the reissued member card has been registered in the member information DB 47. Also, when the management server 2 determines in step S412 that the same card number has already been registered in the member information DB 47, it transmits display information to the mobile terminal 3 to display a warning that the card number is the same as the already registered card number. Also, when the management server 2 adds a card number to the member information corresponding to the user of the mobile terminal 3 in a state where the card number has not been registered in the member information, it transmits display information to the mobile terminal 3 to display information that the card number has been registered. After that, the mobile terminal 3 displays the result of the card number registration request based on the response signal transmitted from the management server 2 in step S414 (step S403).

In this way, when a user of mobile terminal 3 reissues a membership card, the user can inherit the membership information already linked to the target user in membership information DB 47 by sending the card number etc. written on the membership card to management server 2 via mobile terminal 3. In this case, the user of mobile terminal 3 does not need to reinstall the dedicated app and/or re-register the user's personal information due to loss of the membership card, and can conveniently inherit benefits based on purchasing history such as accumulated points.

(5) Modifications
Next, preferred modifications of the above-described embodiment will be described. The following modifications may be applied to the above-described embodiment in any combination.

(Variation 1)
The processing executed by management server 2 in the flowchart of Fig. 17 may be executed by member server 4 instead. In this case, management server 2 transfers the card number registration request sent from mobile terminal 3 to member server 4, and member server 4 executes the processing of steps S411 to S414 in Fig. 17 instead of management server 2. Even in this embodiment, member server 4 can appropriately reflect the card number of the reissued member card in member information DB 47 based on the card number registration request.

(Variation 2)
In the member card registration screen shown in Fig. 16 and step S401 in the flowchart of Fig. 17, the mobile terminal 3 requests input of a secret number such as a PIN code in addition to the card number. Alternatively, the mobile terminal 3 may transmit a card number registration request including at least the card number to the management server 2 without requesting input of such a secret number.

Second Embodiment
18 shows a schematic configuration of a management server 2A in the second embodiment. The management server 2A has a receiving unit 81, an extracting unit 82, and an updating unit 83.

The receiving unit 81 receives a registration request "S1" including the card number of the member card from the terminal device 3A used by the member. The terminal device 3A is, for example, the mobile terminal 3 in the first embodiment. The extracting unit 82 extracts member information corresponding to the target member from a database of member information for each member. The above-mentioned registration request S1 is, for example, a card number registration request in the first embodiment, and the above database is, for example, the member information DB 47 in the first embodiment. If the card number indicated by the extracted member information differs from the card number included in the registration request S1, the updating unit 83 updates the member information with the card number included in the registration request S1. The receiving unit 81, the extracting unit 82, and the updating unit 83 can be the control unit 25 of the management server 2 in the first embodiment.

In this way, when the management server 2A according to the second embodiment receives a registration request S1 specifying a new card number from a terminal device 3A used by a member, it can update the card number while inheriting the member information of that member.

In addition, some or all of the above embodiments (including modified examples, the same applies below) can be described as, but are not limited to, the following notes.

[Appendix 1]
a receiving unit that receives a registration request including a card number of a membership card from a terminal device used by the member;
an extraction unit that extracts member information corresponding to the member from a database of member information for each member;
an update unit that updates the member information with the card number included in the registration request when the card number indicated by the member information is different from the card number included in the registration request;
A management server having

[Appendix 2]
the membership card is a reissued membership card for the member,
A management server as described in Appendix 1, wherein the card number indicated by the member information before the update is the card number of the member card issued to the member before the member card.

[Appendix 3]
the registration request includes user identification information for identifying a user of the terminal device;
The management server according to claim 1 or 2, wherein the extraction unit extracts the member information based on the user identification information.

[Appendix 4]
The management server described in Appendix 3, wherein the user identification information is identification information regarding an application provided by the issuer of the membership card and installed on the terminal device.

[Appendix 5]
A management server described in any one of Appendices 1 to 4, wherein when the update unit updates the member information using the card number included in the registration request, the update unit includes information of the card number indicated in the member information before the update in the member information as information of the previously used member card.

[Appendix 6]
A management server described in any one of appendices 1 to 5, wherein when the update unit updates the member information using the card number included in the registration request, the update unit sets the card number indicated in the member information before the update to invalid.

[Appendix 7]
A management server described in any one of appendices 1 to 6, wherein the member information includes at least one of the number of points held by the member and the card number of a family card issued to the member's family.

[Appendix 8]
A management server according to any one of appendices 1 to 7;
A management system having a terminal device used by a member,
The terminal device includes an acquisition unit that acquires at least a card number of a membership card held by the member;
a transmission unit that transmits a registration request including at least the card number to the management server;
A management system having:

[Appendix 9]
The management system of claim 8, wherein the acquisition unit acquires the card number by reading a barcode on the membership card.

[Appendix 10]
The acquiring unit acquires the card number and a PIN number attached to the membership card,
the transmission unit transmits the registration request, which includes the card number and the PIN, to the management server;
The management server includes:
10. The management system according to claim 8 or 9, further comprising an authentication unit that authenticates the card number based on the card number and the PIN.

[Appendix 11]
A control method executed by a management server, comprising:
receiving a registration request including a membership card number from a terminal device used by the member;
Extracting member information corresponding to the member from a database of member information for each member;
A control method for updating the member information with the card number included in the registration request when the card number indicated by the member information differs from the card number included in the registration request.

[Appendix 12]
a receiving unit that receives a registration request including a card number of a membership card from a terminal device used by the member;
an extraction unit that extracts member information corresponding to the member from a database of member information for each member;
A program that causes a computer to function as an update unit that updates the member information using the card number included in the registration request when the card number indicated by the member information differs from the card number included in the registration request.

Although the present invention has been described above with reference to the embodiments, the present invention is not limited to the above-mentioned embodiments. Various modifications that a person skilled in the art can understand can be made to the configuration and details of the present invention within the scope of the present invention. In other words, the present invention naturally includes various modifications and amendments that a person skilled in the art could make in accordance with the entire disclosure, including the scope of the claims, and the technical ideas. In addition, the disclosures of the above cited patent documents and the like are incorporated into this document by reference.

1 POS server 2 Management server 3 Mobile terminal 4 Member server 5 Accounting machine 100, 100A Management system

Claims (13)

a receiving means for receiving a registration request including a card number of a membership card and user identification information for identifying a user of the terminal device from the terminal device used by the member;
an extracting means for extracting member information corresponding to the member from a member information database based on the user identification information ;
an updating means for not updating the member information when a card number identical to the card number included in the registration request is registered in the member information, and for updating the member information with the card number included in the registration request when the card number indicated by the member information differs from the card number included in the registration request;
A management server having 2. The management server according to claim 1 , wherein, when a card number identical to a card number included in said registration request has been registered , said management server transmits display information for displaying a warning to said terminal device. the membership card is a reissued membership card for the member,
3. The management server according to claim 1, wherein the card number indicated by the pre-update member information is the card number of a member card issued to the member prior to the update of the member card. 4. The management server according to claim 1 , wherein the user identification information is identification information relating to an application provided by an issuer of the membership card and installed on the terminal device. A management server according to any one of claims 1 to 4, wherein when the update means updates the member information using the card number included in the registration request, the update means includes information of the card number indicated by the member information before the update in the member information as information of the previously used member card. The management server according to any one of claims 1 to 5 , wherein the update means, when updating the member information with the card number included in the registration request, sets the card number indicated in the member information before the update to invalid. The management server according to any one of claims 1 to 6 , wherein the member information includes at least one of the number of points held by the member and a card number of a family card issued to a family member of the member. further comprising an authentication means for authenticating the member based on the registration request;
8. The management server according to claim 1, wherein, if the authentication is successful, the extraction means extracts the member information from the database. A management server according to any one of claims 1 to 8 ;
A management system having a terminal device used by a member,
The terminal device includes an acquisition means for acquiring at least a card number of a membership card held by the member;
a transmission means for transmitting a registration request including at least the card number to the management server;
A management system having: The management system according to claim 9 , wherein the acquiring means acquires the card number by reading a barcode on the membership card. The acquiring means acquires the card number and a personal identification number attached to the membership card,
the transmitting means transmits the registration request including the card number and the PIN to the management server;
The management server includes:
11. The management system according to claim 9 , further comprising an authentication unit that authenticates the card number based on the card number and the personal identification number. A control method executed by a management server, comprising:
receiving a registration request from a terminal device used by a member, the registration request including a card number of the member card and user identification information for identifying a user of the terminal device ;
Extracting member information corresponding to the member from a database of member information based on the user identification information ;
if the same card number as the card number included in the registration request is registered in the member information, the member information is not updated, and if the card number indicated by the member information is different from the card number included in the registration request, the member information is updated with the card number included in the registration request.
Control methods. a receiving means for receiving a registration request including a card number of a membership card and user identification information for identifying a user of the terminal device from the terminal device used by the member;
an extracting means for extracting member information corresponding to the member from a member information database based on the user identification information ;
A program that causes a computer to function as an update means that does not update the member information if a card number identical to the card number included in the registration request is registered in the member information, and updates the member information using the card number included in the registration request if the card number indicated in the member information differs from the card number included in the registration request.

Images