Management system and management method

Abstract

To reduce the number of various cards and applications carried.SOLUTION: The present invention relates to a management system 100 for centrally managing use qualifications for multiple services, the system is characterized to comprise a storage part 40 that stores the credentials assigned to a user for each of the services in association with the user, an acquisition part 10 that acquires the biometric information before the provision of the services, an identification part 21 that identifies the user based on the acquired biometric information, and a transmission part 40 that transmits the credential information corresponding to the identified user stored in the storage part to the business system.SELECTED DRAWING: Figure 9

Description

Technical Field

[0001] The present invention relates to a management system and a management method for managing the eligibility to use various services.

Background Art

[0002] Conventionally, services have been provided using membership cards and point cards. Membership cards and point cards are issued for each group or organization and prove the eligibility of members who have joined the group or organization to use services. Examples of membership cards include various types such as rental shop membership cards, karaoke shop membership cards, and training gym membership cards, and the presentation of a membership card is required when using these stores. A point card is a service that gives points calculated according to the purchase amount of goods or services or the number of visits to the store to customers, and the presentation of a point card is required when receiving the service.

[0003] In addition to the above-mentioned membership cards and point cards, there are also various cards such as medical examination tickets, stamp cards, credit cards, cash cards, insurance certificates, my number cards, and driver's licenses, and it is necessary to carry a large number of cards in daily life.

[0004] Here, Patent Document 1 describes a point management system that centrally manages multiple types of points issued by administrative agencies and different stores. The point management system includes an administrative server managed by an administrative agency. The administrative server manages the administrative points issued by the administrative agency to customers by associating them with the customer's my number, and also manages by converting the purchase points issued by the store to the customer into administrative points. Furthermore, the administrative server converts administrative points into purchase points according to the customer's request. According to such a point management system, it becomes possible to convert and manage multiple types of points issued by administrative agencies and different stores into points of one's preference and use them.

Prior Art Documents

[0005] [Patent Document 1] Japanese Patent Publication No. 2022-060429 [Overview of the project] [Problems that the invention aims to solve]

[0006] However, the management system described in the above patent document required users to carry multiple cards corresponding to administrative points and purchase points in order to earn and use these points. In recent years, management apps for managing points, which are installed on smart devices (smartphones and tablet terminals), have emerged. However, since these management apps are provided by each company, it is necessary to install multiple management apps. Furthermore, because multiple management apps are installed, it becomes troublesome to find the appropriate app when using them.

[0007] Therefore, the present invention aims to provide a management system that can reduce the number of cards and applications that need to be carried around. [Means for solving the problem]

[0008] To achieve the above objective, the present invention provides a management system for centrally managing eligibility to use multiple services, comprising: a storage unit that stores eligibility information assigned to a user for each service in association with the user; an acquisition unit that acquires biometric information prior to the provision of the service; an identification unit that identifies the user based on the acquired biometric information; and a transmission unit that transmits the eligibility information stored in the storage unit and corresponding to the identified user to a business system.

[0009] Furthermore, the user's biometric information is characterized by including the user's facial image.

[0010] Furthermore, the transmitting unit is characterized by transmitting credentials related to a specific service.

[0011] Furthermore, the system includes a selection unit for selecting the service to be provided, wherein the specific service is the selected service.

[0012] Furthermore, the system is characterized by receiving credential information to be stored in the storage unit, and biometric information for identifying the user, from a smart device owned by the user.

[0013] The present invention is a management method for centrally managing eligibility to use multiple services, comprising: a storage step of storing eligibility information assigned to a user for each service in association with the user; an acquisition step of acquiring biometric information prior to providing the service; an identification step of identifying the user based on the acquired biometric information; and a transmission step of transmitting the eligibility information stored in the storage unit and corresponding to the identified user to a business system. [Effects of the Invention]

[0014] According to the present invention, the number of cards and apps that need to be carried can be reduced. [Brief explanation of the drawing]

[0015] [Figure 1] Hardware configuration diagram of the management system according to the first embodiment of the present invention [Figure 2] (a) Diagram showing the point management table of the point management server, (b) Diagram showing the card management table of the acquirer server, (c) Diagram showing the alternate code table of the acquirer server, (d) Diagram showing the eligibility management table for point services of the eligibility management server, (e) Diagram showing the eligibility management table for credit payment services of the eligibility management server [Figure 3](a) Hardware configuration diagram of the smart device of this embodiment, (b) Hardware configuration diagram of the eligibility management server 120 of this embodiment [Figure 4] Flowchart showing the application process for point services [Figure 5] In the application process for point services, (a) Diagram showing the display screen of the service selection process, (b) Diagram showing the display screen of the card selection process, (c) Diagram showing the display screen of the input process [Figure 6] Flowchart showing the application process for credit payment services [Figure 7] In the application process for credit payment services, (a) Diagram showing the display screen of the service selection process, (b) Diagram showing the display screen of the store selection process, (c) Diagram showing the display screen of the input process [Figure 8] Flowchart when using services [Figure 9] Functional block diagram of the management system in this embodiment

Mode for Carrying Out the Invention

[0016] Hereinafter, a management system according to an embodiment of the present invention will be described with reference to the drawings. As shown in FIG. 1, the management system 100 according to this embodiment is a system that centrally manages the eligibility for using services such as point services and credit payment services, and is capable of communicating with each system that provides these services. Hereinafter, after explaining the point system 2 that provides point services, the credit payment system 3 that provides credit payment services, and the POS system 1 of the store that can receive these services (hereinafter, these systems are collectively referred to as "service providing system 10"), the management system 100 of this embodiment will be described.

[0017] <Point System>

[0018] The point service is a service that gives points calculated under certain conditions to members (hereinafter also referred to as "users") according to, for example, the purchase amount of goods and services in its affiliated stores, and a point card is issued to the members. Members can use the points as part of the purchase price of goods and services or exchange them for goods. The point system 2 that provides the point service is communicable with the POS system 1 installed in the affiliated store and includes a server (hereinafter referred to as the "point management server") that manages the points of members.

[0019] As shown in FIG. 2(a), the point management server includes a point management table that manages points in association with member information. FIG. 2(a) shows, for example, a point management table provided in the point system 2 provided by Company T. Each time a point card is issued to a member, a record related to the member is added to this point management table. The point management table includes a card number field, a personal information field, and a held points field. In the card number field, the card number of the point card issued to the member is registered. The card number is a number uniquely issued to each member to identify the member. The personal information field includes, for example, a name field in which the name of the member is registered, an address field in which the address of the member is registered, and a phone number field in which the phone number of the member is registered. In the held points field, the points held by the member are registered. The points are updated each time the point information calculated by the POS system 1 of the affiliated store is received.

[0020] <Credit Settlement System>

[0021] As shown in Figure 1, the credit card payment system 3, which provides credit card payment services, is configured to communicate with the POS system 1 installed at a merchant managed by the acquirer. This credit card payment system 3 includes a server managed by the acquirer (hereinafter referred to as the "acquirer server"). The acquirer server executes payment processing for the merchant based on the payment information received from the POS system 1. The acquirer server includes a card management table and multiple alternate code tables.

[0022] As shown in Figure 2(b), the card management table is a table that manages information on credit cards issued to members (hereinafter also referred to as "users"), and a record related to the member is added each time a credit card is issued to the member. The card management table has a card information field and a personal information field. The card information field contains the same information as that written on the credit card issued to the member, and includes a card number field, a cardholder name field, and an expiration date field. The card number field registers the credit card number. The cardholder name field registers the member's name. The expiration date field registers the credit card's expiration date. The personal information field includes a name field where the member's name is registered, an address field where the member's address is registered, and a telephone number field where the member's telephone number is registered.

[0023] As shown in Figure 2(c), the alternate code table is a table that manages alternate codes. An alternate code is a code that replaces a member's credit card number and is determined to be unique for each member's credit card number. When a member applies to use the credit payment service at a merchant (see the application flow described later), the merchant requests the acquirer server to issue an alternate code for that member, and the acquirer server issues the code to the requesting merchant based on that request. Therefore, an alternate code is not issued to merchants to which the member has not applied. If a user applies to use the credit payment service at multiple merchants, alternate codes will be issued to all of those merchants, but different alternate codes will be issued for each merchant. Such alternate codes are registered in the alternate code field, and the card number of the credit card corresponding to the alternate code is registered in the card number field.

[0024] <POSシステム>

[0025] As shown in Figure 1, the POS system 1 of a merchant participating in the above-mentioned point service and credit payment service includes a reader (not shown) that reads the product code of the product purchased by the customer (hereinafter also referred to as "user"), a register terminal (not shown) that obtains the product name and amount based on the read product code and calculates payment information, and a server (not shown) that manages product sales and inventory. The POS system 1 is able to communicate with the point system 2 and credit payment system 3, as well as the management system 100 of this embodiment, via an internet communication line. The POS system 1 transmits points and payment information generated by transactions with customers to the point system 2 and the credit payment system 3. As described above, the POS system 1 requests the credit payment system 3 (acquirer server) to issue an alternative code based on an application for use of the credit payment service from a customer who is a member of the credit payment service, and receives the alternative code transmitted from the credit payment system 3. The received alternative code is then forwarded to the management system 100.

[0026] <Management System>

[0027] As shown in Figure 1, the management system 100 of this embodiment is capable of communicating with the POS system 1 and the user terminal 130 described later, and includes a smart device 110 (hereinafter referred to as "merchant terminal 110") installed at the merchant and a qualification management server 120. Users who can use the management system 100 are members of either the point service or the credit payment service, or both, and prior to using the credit payment service, it is necessary that an alternative code has been issued as described above.

[0028] The merchant terminal 110 is a well-known smartphone or tablet terminal, and as shown in Figure 3(a), it is equipped with a memory 111 for storing a program, a CPU 112 for executing the program, and various devices controllable by the CPU 112. Typical devices include a touch panel display 113, a camera module 114, an internet communication module 115, and a Bluetooth® module 116. The touch panel display 113 functions as an input receiving unit that receives touch input from the user of the management system 100. The camera module 114 functions as an imaging unit that captures the user's face and generates a face image. The input receiving unit and the imaging unit constitute the acquisition unit 10 (Figure 9) of the present invention. The internet communication module 116 functions as an internet communication unit that sends and receives information with the credential management server 120 via an internet communication line. The Bluetooth® module 115 functions as a short-range wireless communication unit that sends and receives information with the POS register 1.

[0029] As shown in Figure 3(b), the credential management server 120 includes a memory 121 for storing programs, a CPU 122 for executing said programs, and an internet communication module 123 that is controllable by the CPU 122. The internet communication module 123 functions as an internet communication unit that sends and receives information between the above-mentioned merchant terminal 110 and the smart device 130 owned by the user (hereinafter referred to as "user terminal 130") via an internet communication line.

[0030] The user terminal 130 is a well-known smartphone or tablet device, and has the same hardware as the merchant terminal 110 described above.

[0031] Here, the above configuration of the management system 100 functions as an authentication unit 20 (Figure 9) that authenticates users based on their facial image and password when using point services and credit payment services. Furthermore, the above configuration of the management system 100 (merchant terminal 110) functions as a transmission unit 50 (Figure 9) that transmits qualification information indicating the user's eligibility to use various services to the service provision system 10 via the POS system 1. A detailed explanation follows below.

[0032] As shown in Figure 9, the authentication unit 20 includes a user identification unit 21 and a matching unit 22 that verifies the password of the identified user. These are configured by the credential management server 120 provided in the management system 100 shown in Figure 1. The credential management server 120 has a trained model that functions as the user identification unit 21, which identifies the user included in the face image received from the merchant terminal 110. This trained model is generated by machine learning using multiple face images received from the user terminal 130 as training data. These multiple face images, which serve as training data, are captured and generated by the user terminal 130 at the time the user applies for service. Note that user identification (user identification unit 21) is not limited to identification by machine learning. For example, feature points may be detected based on the user's face image received from the user terminal 130 at the time of application, and the user may be identified by comparing these feature points with the face image received from the merchant terminal 110.

[0033] The credential management server 120, which functions as a verification unit 22, verifies the password received from the merchant terminal 110 against the password received from the user terminal 130 when the user applies for service. The password received from the user terminal 130 is stored in the credential management table along with the credential information.

[0034] The qualification management table is a table located in the memory 121 of the qualification management server 120 that manages qualification information, and a separate table is provided for each service. In this embodiment, as an example, a qualification management table for T Company's point service and a qualification management table for the credit payment service at merchant A are provided.

[0035] The qualification management table for Company T's point service has a record for each user. This record is generated when a user applies to the qualification management server 120 to use the point service, based on the various information included in the application. Specifically, this qualification management table has a User ID field, a Card Number field, a Cardholder Name field, and a Password field. The User ID field registers a unique User ID for each user. This User ID is issued to the user when they apply to use the service. The Card Number field registers the card number (qualification information) of the point card issued to the user. The Cardholder Name field registers the name of the point cardholder. The Password field registers the password used for the above verification. This password is specified by the user in the application, as described above.

[0036] The credentials management table for the credit payment service at merchant A has a record for each user. This record is generated when a user applies to the credentials management server 120 to use the credit payment service, based on the various information included in the application and the alternative code issued by the acquirer based on the application. Specifically, this credentials management table has a user ID field where the user ID is registered, an alternative code field where the alternative code (credential information) issued by the acquirer is registered, and a password field where the password specified by the user is registered. Thus, the credentials management table provided in the memory 121 of the credentials management server 120 functions as a storage unit 40 (Figure 9) that stores the credentials and passwords assigned to each user for each service, associating them with the user (user ID).

[0037] The following describes the operation flow of the management system 100 of this embodiment.

[0038] First, we will explain the flow of the application process that takes place prior to using the management system 100 of this embodiment. The application process begins when the CPU of the user terminal 130 launches an application stored in its memory. In this embodiment, it is assumed that identification information for identifying the user (applicant) (hereinafter referred to as "user ID") is predefined in the application. However, the user ID may also be issued to the user terminal 130 from the qualification management server 120 when the application is launched for the first time.

[0039] <Application for Point Service>

[0040] When applying to use the points service, the user terminal 130 executes the application process, as shown in Figure 4. In the application process, the following steps are executed in this order: selection process (s30), input process (s31), imaging process (s32), and transmission process (s33).

[0041] The selection process (s30) includes a service selection process and a card selection process. The service selection process is a process that allows the user, who is the applicant, to select the service to be applied for. The CPU of the user terminal 130 displays a GUI on the touch panel display that allows the user to select a service, as shown in Figure 5(a). In this embodiment, buttons for selecting a point service and a credit payment service are displayed. When a point service is selected, the card selection process is executed. The card selection process is a process that allows the user to select the point card to be applied for. The CPU of the user terminal 130 displays a GUI on the touch panel display that allows the user to select the point card to be applied for, as shown in Figure 5(b). In this embodiment, buttons for selecting a P card issued by Company P, a T card issued by Company T, an R card issued by Company R, and a D card issued by Company D are displayed. When a T card is selected by the user, card identification information that identifies the T card is stored in memory.

[0042] The input process (s31) is a process that allows the user to input the information displayed on the card (hereinafter referred to as "card display information"). As shown in Figure 5(c), the CPU of the user terminal 130 displays an input form on the touch panel display. The input form in this embodiment is a form that allows the user to input the name of the cardholder and the card number displayed on the T-card they possess. The user may also be able to enter a password if necessary. The information entered into the above input form is stored in memory.

[0043] The imaging process (s32) involves capturing the applicant user's face multiple times to generate multiple face images (training data). In this imaging process (s32), the CPU of the user terminal 130 activates the camera module. The camera module captures the user's face multiple times and inputs the generated multiple face images to the CPU. The CPU stores the multiple face images input from the camera module in memory. Note that if machine learning based on the user's face image has already been performed in an application for another point service or credit payment service, this imaging process (s32) may be omitted.

[0044] The transmission process (s33) is the process of sending the information stored in memory during each of the above processes, namely card identification information, card display information, password, multiple facial images, and user ID, to the credential management server 120. In this transmission process (s33), the CPU of the user terminal 130 inputs the information stored in memory into the internet communication module. The internet communication module transmits the input information to the credential management server 120 via the internet communication line.

[0045] The credential management server 120 executes the following processes in this order: receiving process (s40), learning process (s41), registration process (s42), and notification process (s43).

[0046] The receiving process (s40) is the process of receiving information from the user terminal 130. In this receiving process (s40), the Internet communication module 123 of the credential management server 120 receives card identification information, card display information, password, multiple facial images, and user ID from the user terminal 130, and inputs the received information to the CPU 122.

[0047] The learning process (s41) generates a trained model by performing machine learning using multiple facial images as training data. In this machine learning process, the trained model is generated in association with the received user ID. Note that if machine learning based on the user's facial image has already been performed in the application for use of other point services or credit payment services, this learning process may be omitted.

[0048] The registration process (s42) is the process of registering the card display information and password in a table, associating them with the user ID. Specifically, the CPU of the user terminal 130 identifies the table corresponding to the received card identification information and registers the card display information and password in that table.

[0049] The notification process (s43) is a process that notifies the user of completion information indicating that the above registration process has been completed. The CPU 122 of the credential management server 120 sends the completion notification to the user terminal 130 via the internet communication module 123. The CPU of the user terminal 130 displays the received completion information on the touch panel display. Although this explanation uses T Company's point service as an example, if a user uses a point service from another company or store, the above process will be executed based on the notation on the point card of that other company or store.

[0050] <Application for use of credit card payment service>

[0051] When applying to use the credit payment service, the user terminal 130 performs a selection process (s50) as shown in Figure 6. The selection process (s50) includes a service selection process and a merchant selection process. The service selection process is the same as the application for the point service described above, and as shown in Figure 7(a), a button to select the point service and a button to select the credit payment service are displayed. When the credit payment service is selected, the merchant selection process is executed. The merchant selection process is the process of selecting a store (company) to use the credit payment service, and the CPU of the user terminal 130 displays a GUI on the touch panel display that allows the user to select a store (company) to use, as shown in Figure 7(b). When a store (company) is selected by the user, merchant identification information that identifies the selected store (company) is stored in memory. After the merchant selection process is executed, the user terminal 130 performs a connection process.

[0052] The connection process (s51) is the process of connecting to the credential management server 120. The CPU of the user terminal 130 accesses the credential management server 120 via the internet communication module and inputs the merchant identification information and user ID stored in memory to the credential management server 120. The credential management server 120 connects to the POS system 1 of the store (company) corresponding to the merchant identification information (connection process (s60)) and inputs that there is an application to use the credit payment service. Based on the application, the POS system 1 requests the credit payment system 3 (acquirer server) to issue an alternative code (issuance request process (s70)). If the credential management server 120 manages the merchant identification information in association with the acquirer server to which the store (company) corresponding to the merchant identification information belongs, the credential management server 120 may directly request the acquisition server to issue an alternative code without going through the POS system 1.

[0053] The credit payment system 3 determines whether the merchant identification information received from the POS system 1 corresponds to a merchant. If it does, it sends an input form to the user terminal 130 prompting the user to enter the information necessary to issue an alternative code, as shown in Figure 7(c) (s80). The user terminal 130 then displays the input form on its screen (display processing (s52)). This input form prompts the user to enter the information displayed on their credit card. In this embodiment, it includes input boxes for the user to enter the name on the credit card, the credit card number, the credit card expiration date, and the credit card security code. In this embodiment, an input box for entering a password is also included in the input form. The user terminal 130 receives the card information and password entered in the input form (input reception processing (s53)) and sends this information to the credit payment system (transmission processing (s54)).

[0054] The credit card payment system 3 receives information from the user terminal 130 (s81), compares the received card information with the information registered in the card management table (matching process (s82)), and if they match, issues an alternative code corresponding to the credit card number contained in the card information. This alternative code is associated with the corresponding credit card number and registered in the alternative code table. The issued alternative code and the received password are also sent to the POS system 1 (transmission process (s83)). The POS system 1 forwards the alternative code and password received from the credit card payment system 3 to the credential management server 120 (s71).

[0055] The credential management server 120 associates the received alternative code and password with the user ID and registers them in the credential management table (registration process (s61)).

[0056] Next, the user terminal 130 performs an imaging process (s55) to capture the applicant user's face multiple times and generate multiple face images (training data), and then transmits the generated multiple face images and user ID to the credential management server 120. Note that if machine learning based on the user's face image has already been performed in the application for the point service or other credit payment service, the imaging process (s55) may be omitted.

[0057] The credential management server 120 performs machine learning using multiple facial images received from the user terminal 130 as training data to generate a trained model (training process (s62)). In this machine learning process, a trained model is generated that is associated with the received user ID. Note that if machine learning based on the user's facial image has already been performed in the application for use of other point services or credit payment services, this training process may be omitted. Once the training process is complete, the credential management server 120 notifies the user terminal 130 of completion information indicating that the application has been completed (notification process (s63)).

[0058] <Processing when using the service>

[0059] Next, we will explain the process when a user uses a points service or credit payment service. As shown in Figure 8, the process when using the service includes an acquisition process performed by the merchant terminal 110 installed at the merchant, and an authentication and extraction process performed by the credential management server 120.

[0060] The acquisition process is the process of acquiring the user's face image and password, and includes an image capture process (s10), an input process (s11), and a transmission process (s12). The image capture process (s10) is the process of capturing an image of the user and generating a face image that includes the user's face, with the CPU 112 of the merchant terminal 110 activating the camera module 114. The camera module 114 captures the user's face and generates a face image, and temporarily stores the generated face image in memory 111. The input process (s11) is the process of having the user enter a password, with the CPU 112 of the merchant terminal 110 displaying an input form on the touch panel display 113 and temporarily storing the password entered in the input form in memory 111.

[0061] After performing the input process (s11) described above, the CPU 112 of the merchant terminal 110 performs the transmission process (s12). The transmission process (s12) is the process of sending the information acquired in the imaging process (s10) and the input process (s11) to the credential management server 120. Here, the memory of the merchant terminal 110 stores store identification information indicating the merchant where the terminal is installed, and the CPU 112 of the merchant terminal 110 inputs the face image, password, and store identification information stored in memory 111 to the internet communication module 116. The internet communication module 116 transmits the input face image, password, and store identification information to the credential management server 120 via the internet communication line.

[0062] Next, the authentication and extraction process of the credential management server 120 will be described. This authentication and extraction process includes receiving (s20), authentication (s21), extraction (s23), and sending (s24).

[0063] The receiving process (s20) is the process of receiving a facial image, password, and store identification information from the merchant terminal 110, with the Internet communication module 123 of the credential management server 120 receiving the facial image, password, and store identification information. The Internet communication module 123 then inputs the received facial image, password, and store identification information to the CPU 122.

[0064] The CPU 122 of the credential management server 120 performs an authentication process (s21) after performing a receiving process (s20). The authentication process (s21) performs a identification process and a matching process in that order. The identification process is a process that identifies a user based on a facial image, and in this embodiment, the facial image is input to a trained model to identify the user (user ID) corresponding to the facial image. In this way, the credential management server 120 functions as an identification unit 21 that identifies a user based on a facial image.

[0065] The verification process is the process of verifying the user's password. In this embodiment, the password corresponding to the user ID identified in the specific process is extracted from the credentials management table, and the extracted password is compared with the password received in the receiving process. Here, if the user uses the points service, the password is extracted from the credentials management table for the points service. If the user uses the credit payment service, the store used is identified based on the store identification information received in the receiving process, and the password is extracted from the credentials management table for the credit payment service corresponding to that store. Then, the extracted password is compared with the received password. In this way, the credentials management server 120 functions as the verification unit 22. If these passwords do not match (s22:NO), information indicating that authentication failed is sent to the merchant terminal 110 in the transmission process (s24) described later. On the other hand, if the passwords match (s22:YES), the extraction process (s23) is executed.

[0066] The extraction process (s23) is a process for extracting credential information corresponding to the user ID, and the CPU 122 of the credential management server 120 extracts the credential information by referring to the credential management table. For example, when a user uses a points service, the CPU 122 extracts the card number corresponding to the user ID from the credential management table for the points service. Also, when a user uses a credit payment service, the CPU 122 identifies the credit payment credential management table for the store (for example, Company A) corresponding to the store identification information received in the above receiving process. Then, it extracts an alternative code from the identified credential management table. In this way, the CPU 122 of the credential management server 120 functions as an extraction unit 30 (Figure 9).

[0067] The CPU 122 of the credential management server 120 performs an extraction process (s23) followed by a transmission process (s24). The transmission process (s24) involves sending credential information to the merchant terminal 110, and the CPU 122 inputs the extracted credential information into the internet communication module 123. The internet communication module 123 transmits the input credential information to the merchant terminal 110 via the internet communication line.

[0068] When the merchant terminal 110 executes the above transmission process (s12), it waits for a response from the credential management server 120 and then executes the reception process (s13). The reception process (s13) is the process of receiving the authentication / extraction result from the credential management server 120, in which the internet communication module 116 receives the authentication / extraction result and inputs the received authentication / extraction result to the CPU 112. If the authentication / extraction result indicates an authentication failure (s14: NO), the above acquisition process is executed again. On the other hand, if the authentication / extraction result contains credential information (s14: YES), the transmission process (s15) is executed. The transmission process (s15) is the process of sending the credential information to the POS system 1, in which the CPU 112 inputs the credential information to the Bluetooth® module 115. The Bluetooth® module 115 transmits the input credential information to the POS system 1. In this way, the merchant terminal 110 functions as a transmission unit 50 that transmits credential information to the POS system 1.

[0069] POS system 1 performs accounting processing and transmits the credentials received from the merchant terminal to service provision system 10, thereby providing the specified service.

[0070] According to the management system 100 of this embodiment, in the accounting process, the credential management server 120 authenticates the customer's eligibility to use the service based on the customer's facial image and password obtained by the merchant terminal 110. The credential information output from the credential management server 120 is then transmitted to the service provision system 10 via the merchant terminal 110. In this way, the service provision system 10 can provide services (point services and credit payment services) by obtaining the customer's credential information, i.e., card number and alternative code, without reading the customer's point card or credit card. Therefore, customers can reduce the number of cards they carry. Furthermore, the risk of card loss or theft can also be reduced.

[0071] Although embodiments of the present invention have been described, the above embodiments may also be modified as follows.

[0072] [Example 1] In the above embodiment, the user is identified based on a facial image, but the user may also be identified based on biometric information such as fingerprints, iris, veins, ear, voiceprint, or palm print. In such a modified embodiment, the merchant terminal 110 and the user terminal 130 are equipped with sensors to acquire the biometric information and transmit the acquired biometric information to the credential management server 120. Furthermore, the user may be identified by combining multiple types of biometric information. For example, identification based on facial and fingerprint biometric information, identification based on facial and iris biometric information, or identification based on facial and palm print biometric information can be employed.

[0073] [Differentiation 2] In the above embodiment, the password is verified during the authentication process (s21), but this verification process may be omitted. Furthermore, the password may be a word known only to the user, such as a parent's maiden name or a pet's name. By verifying with a password or word in this way, it becomes possible to identify a user even in cases where it is difficult to identify a user solely by their face, such as in the case of identical twins. Also, while password registration is optional in the above embodiment, it may be made mandatory in applications requiring high security, such as credit card payment services.

[0074] [Difference 3] In the above embodiment, the password is verified in the authentication process (s21), but instead of the password, information about a symbol worn by the user (hereinafter referred to as "symbol information") may be verified. Symbol information is information issued by the management server when the user applies to use the service, and the qualification management table of the qualification management server 120 is provided with a symbol information field for registering the symbol information issued to the user. When using the service, the user wears a head covering or clothing with the symbol attached. In the imaging process (s10), the merchant terminal 110 captures an image of the user, generating an image that includes the user's face and symbol. Then, it executes the transmission process (s12) and sends the image to the qualification management server 120. The qualification management server 120 identifies the user based on the face image contained in the received image. The qualification management server 120 also analyzes the symbol image contained in the received image to obtain symbol information and verifies this symbol information against the symbol information registered in the management table.

[0075] [Differentiation Example 4] Users may freely combine the above embodiments and variations 1 to 3 in any manner they choose, depending on the service they are using, to perform user authentication.

[0076] [Difference 5] In the above embodiment, when a user is authenticated by the credential management server 120, the credential information corresponding to that user is extracted and sent to the merchant terminal 110. However, the manner in which the credential information is extracted and sent may be as follows.

[0077] [Variation 5-1] For example, if the services available at a merchant are predetermined, the merchant terminal 110 transmits a service code indicating the available services along with a facial image and password during the transmission process. The credential management server 120 performs authentication based on the received facial image and password, and in the extraction process, extracts only the credential information corresponding to the received service code and transmits that credential information to the merchant terminal 110.

[0078] [Modification 5-2] Another variation is that the user specifies the service to be used, and only the credentials corresponding to the specified service are extracted and sent to the merchant terminal 110. For example, in the acquisition process, the merchant terminal 110 performs a selection process. The selection process is a process in which the user selects a service, and the CPU 112 of the merchant terminal 110 displays a list of multiple available services (point service and credit payment service) on the touch panel display 113. The user selects the service they want to use from the displayed list. The touch panel display 113 then inputs the service code indicating the selected service to the CPU 112. Then, in the transmission process, the service code is sent to the credential management server 120 along with the facial image and password. The credential management server 120 performs an authentication process based on the received facial image and password, and in the extraction process, extracts only the credentials corresponding to the received service information and sends the credential information to the merchant terminal 110. The list displayed in the above selection process may also display the type of credit company to be used.

[0079] [Modification 6] In the above embodiment, the point system 2 that provides the point service is not limited to one, but may be multiple types of point systems. In this modified embodiment, the identification information (member number) assigned by each point system is registered in the management table of the qualification management server 120.

[0080] [Difference 7] The point service in the above embodiment is a service that awards customers points calculated according to certain conditions based on the purchase amount of goods or services, but it may also be a visit point service that awards points (hereinafter referred to as "visit points") to customers each time they visit a participating store. In this embodiment, the participating store terminal 110 can be installed near the entrance of the store. In this modified embodiment, the participating store terminal 110 can capture the faces of all users who visit the store and award visit points to those users, thereby encouraging users to visit the store and, as a result, increasing opportunities for purchasing goods.

[0081] [Differentiation 8] In the above embodiment, we have described an example of managing eligibility to use a point system 2 that provides point services and a credit payment system 3 that provides credit payment services. However, as shown in the modified example below, it may also be a management system that manages eligibility to use various services and transmits eligibility information to systems used for various services provided to users (such systems are collectively referred to as "business systems").

[0082] [Variation 8-1] For example, the management system of this embodiment may also be a system that manages entry and exit qualifications for buildings such as office buildings and apartment buildings. In this modified embodiment, an automatic door (business system) is installed at the main gate of the building, and the smart device 110 is provided to communicate with the automatic door. The qualification management table of the qualification management server 120 has an entry / exit ID field, and the entry / exit ID assigned to users of the building (hereinafter also referred to as "users") is registered in this field.

[0083] When a user attempts to enter the building through the main gate, the smart device 110 performs an acquisition process. This process acquires the user's facial image and password, and sends them to the credential management server 120. The credential management server 120 performs an authentication and extraction process. As a result, the credential management server 120 identifies the user based on the facial image received from the smart device 110, extracts the corresponding entry / exit ID from the credential management table, and sends the entry / exit ID to the smart device 110. The smart device 110 inputs the received entry / exit ID into the automatic door. If the entered entry / exit ID is correct, the automatic door controls the opening and closing of the door.

[0084] In the above modified example 8-1, the smart device 110 may also be installed at the entrances to each room within the building. In this modified embodiment, an auto-lock (business system) is installed on the door of each room, and the smart device 110 is installed to communicate with the auto-lock. When a user attempts to enter a room, the smart device 110 performs an acquisition process. This process acquires the user's facial image and password, and transmits them to the credential management server 120. The credential management server 120 performs an authentication and extraction process based on the facial image and password received from the smart device 110. Through this process, the credential management server 120 identifies the user (user ID) attempting to enter the room, extracts the entry / exit ID corresponding to the identified user from the credential management table, and transmits the extracted entry / exit ID to the smart device 110. The smart device 110 inputs the received entry / exit ID into the auto-lock. If the entered entry / exit ID is correct, the auto-lock controls the opening and closing of the lock.

[0085] Although the above variation 8-1 uses entry and exit to an office or building as an example, it could also be a management system for managing entry and exit privileges to a private residence.

[0086] [Modification 8-2] Furthermore, the management system of this embodiment may also be a system for managing eligibility to use rental services such as CDs and DVDs. In this modified embodiment, a rental system is provided at a rental shop that provides rental services. The rental system comprises a POS register installed at the accounting counter and a rental management server that manages rental products. The rental management server manages rental products in association with the card number (eligibility information) of the membership card issued to members (hereinafter also referred to as "users") who use the rental service.

[0087] Here, the credential management table of the credential management server 120 has a card number field, and the card number printed on the membership card is registered in this card number field. The smart device 110 is installed on the accounting counter so that it can communicate with the POS register. Before a user uses the rental service, the smart device 110 performs an acquisition process. Through this process, the user's facial image and password are acquired and sent to the credential management server 120. The credential management server 120 performs an authentication and extraction process based on the facial image and password received from the smart device 110. Through this process, the credential management server 120 identifies the user (user ID) using the rental service, extracts the card number corresponding to the identified user from the credential management table, and sends the extracted card number to the smart device 110. The smart device 110 inputs the received card number into the POS register. The POS register sends the card number and information on the rental item to the rental management server, and the rental management server performs rental item management processing based on the received card number and item information.

[0088] [Modification 8-3] Furthermore, the management system of this embodiment may also be a system for managing eligibility to use parking services in a parking lot. In this modified embodiment, the parking system is provided in multiple affiliated parking lots. The parking system comprises a gate device provided in each parking lot, and a parking management server provided to communicate with each gate device and to manage parking lot usage. The parking management server issues a user ID (qualification information) to users of the parking lot (hereinafter also referred to as "user") and manages parking usage in association with the user ID.

[0089] Here, the credential management table of the credential management server 120 has a user ID field, and the user ID assigned by the parking system is registered in this user ID field. The smart device 110 is configured to communicate with each gate device. When a user uses the parking service (before entering the parking lot), the smart device 110 performs an acquisition process. This process acquires the user's facial image and password, and the facial image and password are sent to the credential management server 120. The credential management server 120 performs an authentication and extraction process based on the facial image and password received from the smart device 110. Through this process, the credential management server 120 identifies the user (user ID) using the parking service, extracts the user ID corresponding to the identified user from the credential management table, and sends the extracted user ID to the smart device 110. The smart device 110 inputs the received user ID into the gate device. The gate device sends the user ID to the parking management server, and the parking management server manages parking usage based on the received user ID.

[0090] [Modification 8-4] Furthermore, the management system of this embodiment may be a system for managing eligibility to participate in events such as concerts. In this modified example, there exists an event system having a reception department that accepts reservations for participation in events and a management department that manages participants, and the management department issues admission eligibility information to event participants.

[0091] Here, the credential management table of the credential management server 120 has an entry qualification field, and the entry qualification information granted by the event system is registered in this entry qualification field. The smart device 110 is installed at the entrance of the event venue so that it can communicate with the event system. When a participant enters the event venue, the smart device 110 performs an acquisition process. This process acquires the participant's face image and password, and sends the face image and password to the credential management server 120. The credential management server 120 performs an authentication and extraction process based on the face image and password received from the smart device 110. Through this process, the credential management server 120 identifies the participant (user ID) participating in the event, extracts the entry qualification information corresponding to the identified participant from the credential management table, and sends the extracted entry qualification information to the smart device 110. The smart device 110 displays on its touch panel display that authentication was successful along with the received entry qualification information, and also sends the entry qualification information to the event system. The event system performs participant reconciliation based on the received entry qualification information.

[0092] [Modification 9-1] In the above embodiment, the user terminal 130 may function as a storage unit that stores the user's facial image by running the application. The application performs an imaging process to capture the user's face and generate a facial image, and a storage process to store the generated facial image. By storing the facial image in this way, the stored facial image can be sent to the qualification management server 120 when applying to use the service, eliminating the need to perform the imaging process each time an application is made.

[0093] [Modification 9-2] Furthermore, in the modified example 9-1 described above, the application on the user terminal 130 may perform a transmission process to send the stored face image along with the user ID to the credential management server 120 each time it stores the user's face image. In this modified embodiment, the credential management server 120 performs machine learning each time it receives a face image from the user terminal 130 and updates the trained model for that user. According to this modified embodiment, face images can be sent to the credential management server 120 in accordance with the user's growth, thus preventing a decrease in identification accuracy due to changes in the user's face as they grow. In addition, user face registration and service usage applications can be performed separately.

[0094] [Example 10] The merchant terminal 110 is not limited to a smart device; it may also be a dedicated terminal capable of acquiring biometric information and passwords. Furthermore, the merchant terminal 110 may be a device installed in a POS register within a POS system.

[0095] [Example 11] In the application for the use of the credit payment service, the POS system 1 forwards the alternative code received from the acquirer server to the credential management server 120 (s71), but is not limited to this configuration. For example, the POS system 1 may issue a new code corresponding to the received alternative code (hereinafter referred to as the "corresponding code"), store the alternative code and the corresponding code in association, and then send the corresponding code to the credential management server 120. In this modified configuration, the corresponding code will be registered as credential information in the credential management table of the credential management server 120. [Explanation of Symbols]

[0096] 10 Acquisition Department 20. Authentication Department 21 Specific section 22 Verification section 30 Extraction part 40 Storage section 50 Transmitter 100 Management Systems s10 Image acquisition process s11 Input processing (acquisition processing) s12 Transmission process (acquisition process) s15 Transmission process s21 Authentication process s23 Extraction process s41,s62 Learning process s42, s61 Registration process

Claims

1. A management system for centrally managing qualification information used for a plurality of services provided to a user, comprising: a communication unit that communicates with a service providing system that provides the service; a storage unit that stores, in association with the user, the qualification information assigned to the user for each service; an acquisition unit that acquires biometric information of the user prior to the provision of the service; an identification unit that identifies the user based on the acquired biometric information; wherein the communication unit transmits qualification information corresponding to the identified user to the service providing system.

2. The management system according to claim 1, wherein the biometric information of the user includes a face image of the user.

3. The management system according to claim 1, wherein the communication unit transmits qualification information regarding a specific service.

4. comprising a selection unit that selects the service to receive, wherein the specific service is the selected service.

5. The management system according to claim 1, wherein the qualification information to be stored in the storage unit and the biometric information for identifying the user are received from a smart device owned by the user.

6. A management method for centrally managing qualification information used for a plurality of services provided to a user, comprising: a communication step in which a communication unit communicates with a service providing system that provides the service; a storage step in which a storage unit stores, in association with the user, the qualification information assigned to the user for each service; an acquisition step in which an acquisition unit acquires biometric information of the user prior to the provision of the service; an identification step in which an identification unit identifies the user based on the biometric information acquired from the terminal; wherein in the communication step, qualification information corresponding to the identified user is transmitted to the service providing system.

Images