Card information management device, card information management system, card information management method, and card information management program

Abstract

This card information management device (1) comprises: a detection unit (11) that detects user behavior related to the use of a predetermined service; an issuing unit (12) that issues, on the basis of a service related to the detected behavior, card information corresponding to part of a plurality of types of card information having different characteristics defined; and a registration unit (13) that registers the issued card information as that of a card owned by the user involved in the detected behavior, and further comprises a notification means for notifying the terminal of the user of the issued card information.

Description

[Technical Field]

[0001] The present invention relates to a card information management device, system, method and program, and more particularly to a card information management device, system, method and program for managing card information issued to users. [Background technology]

[0002] Patent Document 1 discloses a technology relating to a gaming device that provides more entertainment, such as stimulating the desire to collect cards. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Laid-Open No. 2008-093169 Summary of the Invention [Problem to be solved by the invention]

[0004] Recently, there has been a demand for measures to increase the number of users of certain services.

[0005] In view of the above-mentioned problems, the purpose of the present disclosure is to provide a card information management device, system, method, and program for promoting the use of a service by issuing a card to a user who is the target of the service when that user uses the service. [Means for solving the problem]

[0006] A card information management device according to a first aspect of the present disclosure includes: A detection means for detecting user behavior related to the use of a predetermined service; an issuing means for issuing card information corresponding to a part of a plurality of types of card information having different characteristics defined therein based on the service related to the detected behavior; a registration means for registering the issued card information as a card owned by the user related to the detected behavior; Equipped with.

[0007] A card information management system according to a second aspect of the present disclosure includes: a detection device that detects user behavior related to the use of a predetermined service; a card information management device, The card information management device an issuing means for issuing card information corresponding to a part of a plurality of types of card information having different characteristics defined therein, based on the service related to the behavior detected by the detecting device; a registration means for registering the issued card information as a card owned by the user related to the detected behavior; Equipped with.

[0008] A card information management method according to a third aspect of the present disclosure includes: The computer Detecting user behavior related to the use of a given service; issuing card information corresponding to a part of a plurality of types of card information having different characteristics defined therein based on the service related to the detected behavior; The issued card information is registered as a card owned by the user related to the detected behavior.

[0009] A card information management program according to a fourth aspect of the present disclosure includes: A detection process for detecting user behavior related to the use of a predetermined service; an issuance process for issuing card information corresponding to a part of multiple types of card information having different characteristics defined based on the service related to the detected behavior; a registration process for registering the issued card information as a card owned by the user related to the detected behavior; to be executed by the computer. [Effects of the Invention]

[0010] The present disclosure makes it possible to provide a card information management device, system, method, and program for promoting the use of a service by issuing a card to a user to whom the service is provided when the user uses the service. [Brief explanation of the drawings]

[0011] [Figure 1] 1 is a block diagram showing a configuration of a card information management device according to a first embodiment. [Figure 2] 1 is a flowchart showing the flow of a card information management method according to the first embodiment. [Figure 3] FIG. 10 is a block diagram showing the overall configuration of a card information management system according to a second embodiment. [Figure 4] FIG. 10 is a block diagram showing the configuration of a user terminal according to the second embodiment. [Figure 5] FIG. 10 is a block diagram showing the configuration of an authentication terminal according to the second embodiment. [Figure 6] FIG. 10 is a block diagram showing the configuration of an authentication device according to a second embodiment. [Figure 7] 10 is a flowchart showing the flow of a face information registration process performed by the authentication device according to the second embodiment. [Figure 8] FIG. 10 is a block diagram showing the configuration of a card information management device according to a second embodiment. [Figure 9] FIG. 10 is a sequence diagram showing the flow of a card issuing process according to the second embodiment. [Figure 10] 10 is a flowchart showing the flow of face authentication processing by the authentication device according to the second embodiment. [Figure 11] 10 is a flowchart showing the flow of an issuance probability determination process according to the second embodiment. [Figure 12] FIG. 10 is a diagram showing an example of display of card information according to the second embodiment. [Figure 13] FIG. 10 is a diagram showing an example of displaying information on a plurality of cards according to the second embodiment. [Figure 14] FIG. 10 is a diagram showing an example of other card information according to the second embodiment. [Figure 15] FIG. 10 is a diagram showing an example of an airport tour plan according to the second embodiment. [Figure 16] FIG. 11 is a diagram showing an example of display of local area card information according to the second embodiment. [Figure 17] FIG. 10 is a diagram showing an example of other local area card information according to the second embodiment. [Figure 18] FIG. 10 is a sequence diagram showing the flow of card transfer processing according to the second embodiment. [Figure 19] FIG. 10 is a sequence diagram showing the flow of a card exchange process according to the second embodiment. [Figure 20] FIG. 10 is a sequence diagram showing the flow of card use processing according to the second embodiment. [Figure 21] FIG. 10 is a block diagram showing the overall configuration of a card information management system according to a third embodiment. [Figure 22] FIG. 11 is a sequence diagram showing the flow of a physical card issuing process according to the third embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0012] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the drawings. In each drawing, the same or corresponding elements are designated by the same reference numerals, and for clarity of explanation, duplicate explanations will be omitted as necessary.

[0013] <Embodiment 1> 1 is a block diagram showing the configuration of a card information management device 1 according to embodiment 1. The card information management device 1 is an information processing device for issuing card information corresponding to a service related to a user who has performed an action related to the use of the predetermined service, and for managing the issued card information.

[0014] The card information management device 1 includes a detection unit 11, an issuance unit 12, and a registration unit 13. The detection unit 11 detects user behavior related to the use of a predetermined service. Here, the user behavior related to the use of a predetermined service may be, for example, the launch of an application for using the service on a user terminal (not shown) operated by the user. Alternatively, the behavior may be the user terminal receiving radio waves from a wireless base station (not shown) installed at a specific location and establishing a connection. Alternatively, the behavior may be the user successfully authenticating themselves via an authentication terminal (not shown) installed at the specific location. Alternatively, the behavior may be the establishment of a connection between the authentication terminal installed at the specific location and the user terminal via short-range wireless communication. For example, the behavior may be the authentication terminal detecting that a user carrying the user terminal has passed through a specific location. Alternatively, the behavior may be the establishment of a connection between the user terminal and a staff terminal carried by a staff member of a service provider via short-range wireless communication. In the above case, the user terminal, the wireless base station, and the authentication terminal are assumed to be connected to the card information management device 1. When the user terminal, the wireless base station, and the authentication terminal detect the behavior, they notify the card information management device 1. As a result, the detection unit 11 detects the user's behavior based on the notification.

[0015] The issuing unit 12 issues card information corresponding to a portion of multiple types of card information, each having different characteristics, based on a service associated with the detected behavior. That is, the issuing unit 12 may issue one piece of card information, or two or more pieces of card information of the same or different types. It is assumed that each piece of card information issued is assigned unique identification information, even if it is of the same type. Here, the service associated with the detected behavior may be, for example, a service corresponding to a launched application or its operation, or a service provided at a specific location where a connection with a wireless base station is established or personal authentication via an authentication terminal is successful. Alternatively, the service associated with the detected behavior may be, for example, a service provided by a staff member carrying a staff terminal with which a connection is established via short-range wireless communication. The registration unit 13 registers the issued card information as a card owned by the user associated with the detected behavior.

[0016] 2 is a flowchart showing the flow of the card information management method according to the first embodiment. First, the detection unit 11 detects user behavior related to the use of a predetermined service (S11). Next, the issuance unit 12 issues card information corresponding to a portion of multiple types of card information having different characteristics defined therein, based on the service related to the detected behavior (S12). Thereafter, the registration unit 13 registers the issued card information as a card owned by the user related to the detected behavior (S13).

[0017] As described above, the card information management device 1 according to this embodiment issues any card information in response to a user's behavior related to the use of a predetermined service. This can motivate users to collect card information. As a result, it is possible to promote the use of a service by users who are the target of the service.

[0018] The card information management device 1 includes a processor, a memory, and a storage device (not shown). The storage device stores a computer program that implements the processing of the card information management method according to this embodiment. The processor then loads the computer program from the storage device into the memory and executes the computer program. This allows the processor to implement the functions of the detection unit 11, the issuance unit 12, and the registration unit 13.

[0019] Alternatively, each component of the card information management device 1 may be realized by dedicated hardware. Furthermore, some or all of the components of each device may be realized by general-purpose or dedicated circuits, processors, etc., or a combination of these. These may be configured by a single chip, or by multiple chips connected via a bus. Some or all of the components of each device may be realized by a combination of the above-mentioned circuits, etc., and programs. Furthermore, a CPU (Central Processing Unit), GPU (Graphics Processing Unit), FPGA (Field-Programmable Gate Array), quantum processor (quantum computer control chip), etc., may be used as the processor.

[0020] Furthermore, when some or all of the components of the card information management device 1 are realized by multiple information processing devices, circuits, etc., the multiple information processing devices, circuits, etc. may be centrally or decentralized. For example, the information processing devices, circuits, etc. may be realized as a client-server system, a cloud computing system, etc., in a form in which each is connected via a communication network. Furthermore, the functions of the card information management device 1 may be provided in a SaaS (Software as a Service) format.

[0021] <Embodiment 2> The present embodiment 2 is a specific example of the above-mentioned embodiment 1. Fig. 3 is a block diagram showing the overall configuration of a card information management system 1000 according to the present embodiment 2. The card information management system 1000 is an information system for managing card information issued in accordance with the use of each facility and equipment of the airport 600, various procedures at the airport 600, the use of aircraft, etc. Users U1, U2, and U3 are users of the airport 600.

[0022] An airport 600 is an example of a facility where various services are provided to users by airlines, airport operating companies, retailers, etc. The airport 600 includes regions (locations) such as areas 601 to 603. A wireless base station 300 is installed in area 601, and the area 601 is within its wireless communication range. The wireless base station 300 establishes a wireless communication connection with a wireless terminal (such as a user terminal) present within the range, and relays the wireless communication. For example, when a user U1 carrying a user terminal 100-1 moves near area 601, a wireless communication connection is established between the wireless base station 300 and the user terminal 100-1.

[0023] An authentication terminal 200 is also installed in the area 602. The authentication terminal 200 performs identity authentication (using the card information management device 400 or the authentication device 500) of a user U2 who uses the services provided in the area 602. The authentication terminal 200 may also establish a short-range wireless communication connection with a user terminal 100-2 carried by the user U2 who is present within a predetermined range.

[0024] Area 603 is an area where airport 600 and airline staff U4 are present. Staff U4 carries a staff terminal 100-4. Staff terminal 100-4 may establish a short-range wireless communication connection with a user terminal 100-3 carried by a user U3 present within a predetermined range.

[0025] The card information management system 1000 includes user terminals 100-1 to 100-3, a staff terminal 100-4, an authentication terminal 200, a wireless base station 300, a card information management device 400, and an authentication device 500. The user terminals 100-1 to 100-3, the staff terminal 100-4, the authentication terminal 200, the wireless base station 300, the card information management device 400, and the authentication device 500 are communicably connected via a network N. Here, the network N is a wired or wireless communication line or communication network, such as an airport LAN (Local Area Network), the Internet, a wireless communication network, or a mobile phone network. The network N does not care about the type of communication protocol. Note that the user terminal 100-1 may be connected to the network N via the wireless base station 300 when a wireless communication connection with the wireless base station 300 is established. Furthermore, when a wireless communication connection is established with a wireless base station (not shown) installed in area 602 or 603, user terminals 100-2 and 100-3 may also be connected to network N via each wireless base station. In the following, when there is no need to particularly distinguish between user terminals 100-1, 100-2, and 100-3, they will be collectively referred to simply as "user terminal 100."

[0026] In the following description, "personal authentication information" refers to information used for authentication of personal identity (personal authentication, personal identification processing, etc.) and is information for uniquely identifying (identifying) a person. In the second embodiment, personal authentication is defined as facial authentication, which is an example of biometric authentication, and personal authentication information (personal identification information) is defined as facial feature information, which is an example of biometric information. However, other technologies using captured images can be applied to biometric authentication and biometric information. For example, biometric information may be data (features) calculated from physical features unique to an individual, such as fingerprints, voiceprints, veins, retinas, irises, and palm patterns. Instead of biometric authentication, other personal authentication methods may be applied, and biometric information may also be other personal authentication information. Examples of personal authentication information include, but are not limited to, a combination of an ID and a password, the contents of an identification card such as a My Number or a driver's license (such as an identification number or password), an electronic certificate, and code information. The code information may be a two-dimensional code, such as a QR Code (registered trademark).

[0027] The user terminal 100 is, for example, an information terminal such as a mobile phone terminal, a smartphone, or a tablet terminal. The user terminal 100 is assumed to have installed thereon an application (software program) for using various services related to the airport 600. The user terminal 100 uses the application to perform login processing by the user, accepts requests for use of various services, and displays and stores card information received from the card information management device 400. Furthermore, the user terminal 100 may transmit a transfer request, exchange request, or use request for the stored card information to the card information management device 400 in response to a user operation. At that time, the user terminal 100 may read code information of card information displayed on another user terminal 100.

[0028] The user terminal 100 communicates with the card information management device 400 and the authentication device 500 via the network N. The user terminal 100 may also establish a wireless communication connection with the wireless base station 300 and communicate with the wireless base station 300 via the network N. The user terminal 100 may also establish a short-range wireless communication connection with the authentication terminal 200 and the staff terminal 100-4.

[0029] FIG. 4 is a block diagram showing the configuration of a user terminal 100 according to the second embodiment. The user terminal 100 includes a camera 110, a storage unit 120, a memory 130, a communication unit 140, an input / output unit 150, and a control unit 160. The camera 110 is an imaging device that takes images under the control of the control unit 160. The storage unit 120 is an example of a storage device such as a flash memory. The storage unit 120 stores a program 121 and card information 122. The program 121 is a computer program that implements processes including the above-mentioned applications. The card information 122 is card information issued by the card information management device 400. The card information 122 only needs to include at least a card ID. The card information 122 may also include characteristic information (such as card type, card contents (name, rarity, image), etc.) described below.

[0030] The memory 130 is a volatile storage device such as a RAM (Random Access Memory), and is a storage area for temporarily storing information when the control unit 160 is operating. The communication unit 140 is a communication interface with the network N. In particular, the communication unit 140 performs wireless communication. For example, the communication unit 140 establishes a connection with the wireless base station 300 or other wireless communication base stations and performs communication. The communication unit 140 may also establish a short-range wireless communication connection with the authentication terminal 200 or the staff terminal 100-4 and perform communication. The communication unit 140 may also communicate with a GPS (Global Positioning System) satellite to acquire location information. The input / output unit 150 includes a display device (display unit) such as a screen and an input device. The input / output unit 150 is, for example, a touch panel. The control unit 160 is a processor that controls the hardware of the user terminal 100. The control unit 160 loads the program 121 from the storage unit 120 into the memory 130 and executes it. As a result, the control unit 160 realizes the functions of a wireless processing unit 161, a card processing unit 162, and a display control unit 163.

[0031] The wireless processing unit 161 processes wireless communication using the communication unit 140. Specifically, when the wireless processing unit 161 receives wireless radio waves from the wireless base station 300 or the like, it establishes a wireless communication connection with the wireless base station 300 and performs wireless communication via the wireless base station 300. The wireless radio waves from the wireless base station 300 or the like may be compatible with Wi-Fi (registered trademark), for example. The wireless processing unit 161 may also establish a short-range wireless communication connection with the authentication terminal 200 or the staff terminal 100-4, and perform data communication with the authentication terminal 200 or the staff terminal 100-4 with which the connection has been established. Here, the short-range wireless communication may be compatible with the Bluetooth (registered trademark) standard, for example.

[0032] The card processing unit 162 receives card information from the card information management device 400, outputs the card information to the display control unit 163, and stores the card information in the storage unit 120. The card processing unit 162 may transmit a transfer request or an exchange request for the stored card information to the card information management device 400 in response to a user operation. For example, the card processing unit 162 may read code information of card information displayed on the screen of another user terminal via the camera 110 and analyze the code information to identify card information to be transferred or exchanged to itself. Alternatively, the card processing unit 162 may exchange (transmit / receive) card information with another user terminal via short-range wireless communication. In this way, the card processing unit 162 may identify the received card information. Then, the card processing unit 162 may transmit a transfer request for the identified card information to itself or a request to exchange the identified card information for card information owned (stored) by itself to the card information management device 400. The card processing unit 162 may also transmit a use request to the card information management device 400 based on the card information and usage content specified by the user. The usage includes, for example, exchanging card information for electronic value information such as points, but is not limited to this.

[0033] The display control unit 163 displays the received card information on the input / output unit 150. Furthermore, the display control unit 163 reads out card information 122 from the storage unit 120 and displays it on the input / output unit 150 in response to a user instruction.

[0034] The authentication terminal 200 is an information terminal that authenticates a user when using a service. The authentication terminal 200 identifies the user through biometric authentication or other personal authentication methods described above, and provides the user with a service tailored to the user. For example, the authentication terminal 200 photographs the face of the user U2 and performs facial authentication on the facial image using the authentication device 500 via the card information management device 400. If the facial authentication is successful, the authentication terminal 200 provides a predetermined service to the user U2. The authentication terminal 200 may be, for example, a processing terminal at the airport 600, a lounge entrance terminal, a payment terminal at a convenience store, digital signage, or the like, but is not limited to these. The processing at the airport 600 may be, for example, check-in (boarding procedures), baggage drop-off, security screening, immigration, and passenger verification for an aircraft. In the case of passenger verification, the authentication terminal 200 may be, for example, a terminal installed at a boarding gate.

[0035] 5 is a block diagram showing the configuration of the authentication terminal 200 according to the second embodiment. The authentication terminal 200 includes a camera 210, a storage unit 220, a memory 230, a communication unit 240, an input / output unit 250, and a control unit 260. The camera 210 is an imaging device that takes images under the control of the control unit 260. The storage unit 220 is an example of a storage device such as a hard disk or flash memory. The storage unit 220 stores a program 221. The program 221 is a computer program that implements processes including an authentication request process for starting the provision of a service. For example, the program 221 includes a client application corresponding to the card information management device 400.

[0036] The memory 230 is a volatile storage device such as RAM (Random Access Memory), and is a storage area for temporarily storing information when the control unit 260 is operating. The communication unit 240 is a communication interface with the network N. The communication unit 140 may establish a short-range wireless communication connection with the user terminal 100-2 and perform communication. The input / output unit 250 includes a display device (display unit) such as a screen and an input device. The input / output unit 250 is, for example, a touch panel. The control unit 260 is a processor that controls the hardware of the authentication terminal 200. The control unit 260 loads the program 221 from the storage unit 220 into the memory 230 and executes it. As a result, the control unit 260 realizes the functions of a display control unit 261, an authentication request unit 262, and a processing control unit 263.

[0037] The display control unit 261 causes the input / output unit 250 to display a screen generated by execution of the program 221. When the authentication terminal 200 is a check-in terminal, the display control unit 261 displays a message prompting the user to take a face photograph for face authentication, an explanation regarding check-in, a menu, etc. When the authentication terminal 200 is an entrance terminal for a lounge, the display control unit 261 displays a message prompting the user to take a face photograph to confirm entry to the lounge, etc. When the authentication terminal 200 is a store terminal, the display control unit 261 displays a message regarding payment for a product the user is attempting to purchase at a convenience store, etc. Furthermore, the display control unit 261 may cause the input / output unit 250 to display an authentication result in response to an authentication request from the authentication request unit 262 (described later). Furthermore, the display control unit 261 may cause the input / output unit 250 to display card information received from the card information management device 400.

[0038] The authentication request unit 262 extracts a facial area of ​​a person detected from an image captured by the camera 210 as a facial image, and transmits an authentication request including the facial image, terminal location information, and time information to the card information management device 400. The authentication request does not have to include time information. The authentication request unit 262 may transmit a facial authentication request including the facial image to the authentication device 500 and receive a facial authentication result from the authentication device 500. Then, if the facial authentication result indicates success, the authentication request unit 262 may extract a user ID included in the facial authentication result and transmit information including the user ID, terminal location information, and time information to the card information management device 400.

[0039] The authentication request unit 262 may acquire biometric information or other personal authentication information from the user in addition to or instead of a facial image, and include the acquired personal authentication information in the authentication request. For example, the authentication request unit 262 may acquire personal authentication information by reading code information printed on an airline ticket or code information of an airline ticket displayed on the user terminal 100. Alternatively, the authentication request unit 262 may read personal authentication information from a magnetic code on a membership card of the airline ticket or a built-in IC (Integrated Circuit) chip.

[0040] The process control unit 263 controls processes specific to each authentication terminal. For example, if the authentication terminal 200 is a check-in terminal, the process control unit 263 performs a specified check-in process in response to successful user authentication. At this time, the process control unit 263 may communicate with the information systems of the airport 600 or each airline, as necessary. If the authentication terminal 200 is an entrance terminal for a lounge, the process control unit 263 controls the gate device at the entrance to the lounge to unlock when the user is successful in user authentication and meets the conditions for using the lounge. If the authentication terminal 200 is a store terminal, the process control unit 263 performs settlement and payment processes for the products to be purchased.

[0041] Returning to FIG. 3, the explanation continues. The authentication device 500 is an information processing device that manages facial feature information of users and performs facial authentication. In response to a facial authentication request received from the outside, the authentication device 500 compares the facial image or facial feature information included in the request with the facial feature information of each user and returns the comparison result (authentication result) to the request source.

[0042] FIG. 6 is a block diagram showing the configuration of an authentication device 500 according to the second embodiment. The authentication device 500 includes a face information DB 510, a face detection unit 520, a feature point extraction unit 530, a registration unit 540, and an authentication unit 550. The face information DB 510 stores a user ID 511 and facial feature information 512 for the user ID in association with each other. The facial feature information 512 is a collection of feature points extracted from a facial image. The authentication device 500 may delete the facial feature information 512 from the facial feature DB 510 in response to a request from a user or the like corresponding to the facial feature information 512. Alternatively, the authentication device 500 may delete the facial feature information 512 after a certain period of time has elapsed since registration.

[0043] The face detection unit 520 detects a face area included in a registration image for registering face information, and outputs the detected face area to the feature point extraction unit 530. The feature point extraction unit 530 extracts feature points from the face area detected by the face detection unit 520, and outputs face feature information to the registration unit 540. The feature point extraction unit 530 also extracts feature points included in a face image received from the card information management device 400 or the like, and outputs the face feature information to the authentication unit 550.

[0044] The registration unit 540 issues a new user ID 511 when registering facial feature information. The registration unit 540 associates the issued user ID 511 with facial feature information 512 extracted from the registered image and registers the associated user ID 511 in the facial information DB 510. The authentication unit 550 performs facial authentication using the facial feature information 512. Specifically, the authentication unit 550 compares the facial feature information extracted from the facial image with the facial feature information 512 in the facial information DB 510. If the comparison is successful, the authentication unit 550 identifies the user ID 511 associated with the compared facial feature information 512. The authentication unit 550 returns a match of the facial feature information to the request source as a facial authentication result. The match of the facial feature information corresponds to the success or failure of authentication. Note that the facial feature information matches (matches) when the degree of match is equal to or greater than a threshold. If the facial authentication is successful, the facial authentication result includes the identified user ID.

[0045] FIG. 7 is a flowchart showing the flow of face information registration processing by the authentication device 500 according to the second embodiment. First, the authentication device 500 receives a face information registration request (S201). For example, the authentication device 500 receives the face information registration request from the card information management device 400 via the network N. Next, the face detection unit 520 detects a face area from the face image included in the face information registration request (S202). Then, the feature point extraction unit 530 extracts feature points (facial feature information) from the face area detected in step S202 (S203). Then, the registration unit 540 issues a user ID 511 (S204). Then, the registration unit 540 associates the extracted facial feature information 512 with the issued user ID 511 and registers them in the face information DB 510 (S205). Thereafter, the registration unit 540 returns the issued user ID 511 to the request source (for example, the card information management device 400) (S206). The authentication device 500 may perform face information registration processing in response to a face information registration request received from an arbitrary information registration terminal. For example, the information registration terminal may be an information processing device such as a personal computer, a smartphone, or a tablet terminal. The information registration terminal may also be the user terminal 100.

[0046] Returning to FIG. 3, the explanation continues. The card information management device 400 is an information processing device that dynamically determines an issuance probability according to predetermined conditions for a user who has performed an action related to the use of a predetermined service, and manages card information issued according to the issuance probability. The card information management device 400 also performs card issuance processing, card transfer processing, card exchange processing, card use processing, etc. The card information management device 400 is an example of the above-mentioned card information management device 1. The card information management device 400 may be redundantly configured with multiple servers, and each functional block may be realized by multiple computers.

[0047] 8 is a block diagram showing the configuration of a card information management device 400 according to the second embodiment. The card information management device 400 includes a storage unit 410, a memory 420, a communication unit 430, and a control unit 440. The storage unit 410 is an example of a storage device such as a hard disk or a flash memory. The storage unit 410 stores a program 411, card definition information 412, user information 413, a card information history 414, and card use conditions 415. The program 411 is a computer program that implements processes including a card issuance process, a card transfer process, a card exchange process, and a card use process according to the second embodiment.

[0048] The card definition information 412 is information that defines the characteristics of each type of card information. The card definition information 412 is information that associates a card definition ID 4121, characteristic information 4122, and a standard issuance probability 4123. The card definition ID 4121 is identification information for the type of card information. The characteristic information 4122 is information that indicates the characteristics corresponding to the type of card information. The characteristic information 4122 includes a card type 41221, card details 41222, issuance conditions 41223, and usage details 41224.

[0049] Card type 41221 is information that uniquely identifies the type of card information. Card content 41222 is the name of the card information, a description, a rarity indicating the degree of rarity, an image, etc. Rarity may be a name indicating a numerical value or a level. Rarity may be text information or a level value, such as normal, rare, super rare, or hyper rare. Note that rarity may be changed when various conditions are met. In that case, the rarity included in card content 41222 may be a reference value.

[0050] The issuance condition 41223 is a combination (association) of the user's detected behavior and the increase / decrease value of the issuance probability. The detected behavior includes the content of the behavior, the location where the behavior was detected, how it was detected, and the service used in conjunction with the behavior (the service that motivated the user's behavior). The content of the behavior includes, but is not limited to, the launch of an application to use various services, the user's movement to a specific location (area), close-range interaction with a specific staff member, and personal authentication for procedures. The location where the behavior was detected includes, but is not limited to, a specific location (various procedures location) within the airport 600, inside an aircraft, a specific airport, etc. The detection method includes, for example, a notification of the launch of a specific application, a notification of the establishment of communication with a wireless base station at a specific location, a notification of successful personal authentication from an authentication terminal, and a determination of successful authentication in response to an authentication request from the authentication terminal. The detection method also includes, but is not limited to, a notification of the establishment of a short-range wireless communication connection with the user terminal from an authentication terminal or a staff terminal. The services used in conjunction with the behavior include, but are not limited to, check-in (boarding procedures), entry to a lounge, payment, etc. The increase / decrease value of the issuance probability is a value that is increased or decreased from the base issuance probability when the corresponding detected behavior, etc. is detected. Therefore, the issuance condition 41223 can also be said to be a probability increase condition. Therefore, the probability increase condition includes at least one of the following: the detected behavior is performed at a specific location, or the service level provided to the user related to the detected behavior is equal to or higher than a predetermined level. The probability increase condition also includes successful identity authentication of the user via an authentication terminal installed at the specific location.

[0051] The usage content 41224 may be converted (exchanged) into points or other electronic value information, converted (exchanged) into special benefit information such as the usage fee, discount rate, or discount amount of a product or service, or improved service level (such as upgrading an airplane seat). Here, electronic value information is electronic data indicating economic value. Points are an example of electronic value information having pseudo-monetary value that can be exchanged for products or services. Note that the value information may be electronic coupons, electronic money, crypto assets, electronic tickets, etc., in addition to points. In other words, it is electronic data indicating economic value, and includes those having monetary value equivalent to currency and those having pseudo-monetary value. Therefore, a user can use their card information by exchanging it for the number of points according to the usage content 41224. Furthermore, the user can exchange their card information for products or services according to the usage content 41224.

[0052] The standard issuance probability 4123 is a standard value of the issuance probability for the corresponding card type. The standard issuance probability 4123 may be based on rarity.

[0053] The user information 413 is information for managing a user to whom card information has been issued. The user information 413 is information in which a user ID 4131, personal information 4132, membership rank 4133, owned points 4134, and owned card information 41351 to 4135n (n is an integer of 1 or more) are associated with each other. The user ID 4131 is user identification information. The user ID 4131 is information corresponding to the user ID 511 in the face information DB 510 described above. The user ID 4131 is an example of personal authentication information. The user ID 4131 may be a login ID for the application described above.

[0054] The personal information 4132 is information including the user's name, address, telephone number, payment information, notification destination, etc. The notification destination is identification information (terminal ID) of the user terminal owned by the user, the user's login ID, email address, SNS (Social Networking Service) account, etc. The personal information 4132 may also include information regarding airline tickets reserved by the user (departure and arrival dates and times, flight number, seat, etc.). The member rank 4133 is information corresponding to the level of services that can be received as a member (such as the grade of aircraft seats). The owned points 4134 are an example of benefit information or electronic value information that can be used to pay for the use of provided services, etc.

[0055] The owned card information 41351, etc., is card information issued to a user. For example, the owned card information 41351 is information that associates a card ID 41361, a card definition ID 41362, and a status 41363. The card ID 41361 is identification information for issued card information. The card definition ID 41362 is information corresponding to the card definition ID 4121 described above. The status 41363 is information indicating the status of the card information. For example, the status 41363 is owned, used, transferred, etc. "Owned" indicates a state in which card information (card ID) has been issued and stored in the user terminal 100. "Used" indicates a state in which the card information has been used according to the above-described usage details, that is, a state in which the user does not own the card and cannot use it in the future. "Transferred" indicates a state in which the card information has become "owned" by another user. Note that the status 41363 may be "not owned" or the like without distinguishing between used and transferred. Alternatively, the owned card information 41351 etc. may be deleted or a deletion flag may be set when the user transfers, exchanges, uses, etc. the card information.

[0056] The card information history 414 is information for managing the history of card information processing (issuance or possession, transfer, exchange, or use). The card information history 414 is information that associates a date and time 4141, a processing type 4142, a user ID 4143, and card IDs 41441 to 4144m (m is an integer of 1 or more). The date and time 4141 is the date and time when the card information was processed. The processing type 4142 indicates the type of processing, which is issuance or possession, transfer, exchange, or use of the card information. The user ID 4143 indicates the identification information of the user corresponding to the processing of the card information. For example, when the processing type 4142 is issue or possession, the user ID 4143 is the identification information of the card information. It is the ID of the user who became the owner of the card (the card information is stored in the user terminal 100). Furthermore, if the processing type 4142 is transfer or exchange, the user ID 4143 is the user ID of the transferee or exchangeee of the card information. If the processing type 4142 is use, the user ID 4143 is the ID of the user who used the card information. The card ID 41441, etc. is a collection (combination) of card information processed for a combination of the date and time 4141 and processing type 4142. For example, if multiple cards are used together, the card ID 41441, etc. is the combination of the cards. Furthermore, the card information history 414 may be a history for each card ID.

[0057] Note that the owned card information 41351, etc. may include a rarity level separately from the card definition ID 41362. Alternatively, the card information history 414 may include a rarity level corresponding to the card ID 41441, etc. In particular, if the (standard) rarity level defined in the card contents 41222 of the card definition information 412 differs from the rarity level at the time of issuance, the owned card information 41351, etc. and the card information history 414 will include the rarity level at the time of issuance.

[0058] The card use conditions 415 are information that defines the conditions for using card information. The card use conditions 415 include an exchange definition 4151 and a combination definition 4152. The exchange definition 4151 is information that defines the exchange destination, card type, value information to be exchanged, etc. when exchanging card information for electronic value information. Alternatively, the exchange definition 4151 may define rarity instead of card type. Alternatively, the exchange definition 4151 may define rarity together with card type. This is because rarity may differ even for the same card type. The exchange destination is, for example, the type of electronic value information or a financial institution, etc., as described above. For example, when card information is exchanged for points 4134 held in the user information 413, the exchange destination is an organization that manages the points. The value information to be exchanged is the value of value information (e.g., the number of points) that serves as a basis when exchanging card information of the corresponding card type. Furthermore, the combination definition 4152 is information that defines the combination of card types when using multiple card information together, the usage content, etc. The combination definition 4152 may further include information about benefits granted by use (number of points, available services, service level upgrades, etc.).

[0059] The memory 420 is a volatile storage device such as a RAM, and is a storage area for temporarily storing information during operation of the control unit 440. The communication unit 430 is a communication interface with the network N.

[0060] The control unit 440 is a processor, that is, a control device, that controls each component of the card information management device 400. The control unit 440 loads the program 411 from the storage unit 410 into the memory 420 and executes the program 411. As a result, the control unit 440 realizes the functions of a registration unit 441, an authentication control unit 442, an identification unit 443, a determination unit 444, an issuance unit 445, and a notification unit 446.

[0061] The registration unit 441 registers and updates the user information 413 and the card information history 414. For example, when the registration unit 441 receives a user registration request including a face image of a new user from the user terminal 100 or the like, the registration unit 441 transmits a face information registration request for the face image included in the user registration request to the authentication device 500 and acquires a user ID as a registration result. The registration unit 441 initially registers the acquired user ID 4131 and personal information 4132 included in the user registration request in association with each other in the user information 413.

[0062] Furthermore, the registration unit 441 is an example of the above-mentioned registration unit 13. When new card information (card ID) is issued by the issuance unit 445, the registration unit 441 associates owned card information 41351 including the issued card ID 41361 etc. with the user ID 4131 for which face authentication has succeeded, and registers the associated information in the user information 413. Additionally, the registration unit 441 registers an issuance history relating to the issued card ID in the card information history 414.

[0063] Furthermore, the registration unit 441 updates the status 41363 of a specific user's owned card in response to a transfer request, exchange request, or use request. At the same time, the registration unit 441 updates the history related to the updated card information. Specifically, when the registration unit 441 receives a transfer request to transfer a owned card from a first user to a second user, the registration unit 441 marks the owned card of the first user as used and registers the owned card in association with the second user. For example, the registration unit 441 receives a transfer request transmitted when a owned card displayed on a first terminal of the first user is read by a second terminal of the second user.

[0064] Furthermore, when the registration unit 441 receives a request to exchange a first owned card of a first user with a second owned card of a second user, it processes the request as if it had received the following first and second transfer requests. That is, the first transfer request is a transfer request to transfer the first owned card from the first user to the second user, and the second transfer request is a transfer request to transfer the second owned card from the second user to the first user. Furthermore, the registration unit 441 registers the usage details determined in response to the use request in association with the user of the owned card, and updates the owned card of the user as used. Furthermore, when a combination of multiple owned cards registered in association with a user satisfies a benefit condition, the registration unit 441 may register predetermined benefit information in association with the user.

[0065] The authentication control unit 442 controls face authentication, which is an example of biometric authentication, as identity authentication. However, the authentication control unit 442 may also control other biometric authentication or other identity authentication. The authentication control unit 442 controls face authentication for a face image included in an authentication request. That is, the authentication control unit 442 controls authentication using identity authentication information for registration and authentication. Specifically, the authentication control unit 442 transmits a face authentication request including a face image to the authentication device 500 and receives a face authentication result from the authentication device 500. Note that the authentication control unit 442 may detect the user's face area from the face image and include an image of the face area in the face authentication request. Alternatively, the authentication control unit 442 may extract facial feature information from the face area and include the facial feature information in the face authentication request.

[0066] The identification unit 443 determines whether or not face authentication is successful based on the face authentication result by the authentication control unit 442. If it is determined that face authentication is successful, the identification unit 443 identifies user information 413 corresponding to the user ID included in the face authentication result. Furthermore, the identification unit 443 identifies the current location of the successfully authenticated user from the terminal location information included in the authentication request. That is, the identification unit 443 identifies the location where the user's behavior was detected. Furthermore, the identification unit 443 may identify the user's behavior and a service related to the behavior based on a notification of the launch of a specific application, a notification of the establishment of communication with the wireless base station 300 at a specific location, or a notification of successful personal authentication from the authentication terminal 200, in addition to the authentication request. Furthermore, the identification unit 443 may identify the user's behavior, a service related to the behavior, a staff member corresponding to the service, etc., based on a notification of the establishment of a short-range wireless communication connection with the user terminal 100 from the authentication terminal 200 or the staff terminal 100-4, etc. Furthermore, the identification unit 443 may identify the current location of the user based on, other than an authentication request, a notification of the start of a specific application, a notification of the establishment of communication with the wireless base station 300 at a specific location, or a notification of successful personal authentication from the authentication terminal 200. Alternatively, the identification unit 443 may identify the current location of the user based on, other than an authentication request, a notification of the establishment of a short-range wireless communication connection with the user terminal 100 from the authentication terminal 200 or the staff terminal 100-4. Alternatively, the identification unit 443 may identify the current location of the user based on, other than an authentication request, the detected behavior of the user, a service related to the behavior, a staff member corresponding to the service, etc.

[0067] Therefore, the authentication control unit 442 and the identification unit 443 can be said to be an example of the above-mentioned detection unit 11. Therefore, when the user's identity is successfully authenticated via an authentication terminal installed at a specific location, the detection unit according to the second embodiment can be said to detect this as a user behavior related to the use of a predetermined service.

[0068] The determination unit 444 determines the issuance probability for each of multiple types of card information, each having different characteristics defined, based on the service associated with the detected behavior. That is, the determination unit 444 determines the issuance probability for each card type when face authentication is successful or when the user's behavior is detected. For example, the determination unit 444 acquires the standard issuance probability 4123 and the issuance conditions 41223 from the card definition information 413 for a specific card type 41221. Then, the determination unit 444 determines the issuance probability based on the detected behavior, the specific location, the specified service, the card type, the standard issuance probability, and the issuance conditions. Here, the issuance probability may be between 0% and 100%. Specifically, the determination unit 444 determines the issuance probability by increasing or decreasing the probability relative to the standard issuance probability in accordance with the detected behavior, the specific location, the specified service, and the card type in accordance with the issuance conditions. For example, when the detected behavior satisfies the probability increase condition (the issuance condition 41223), the determination unit 444 determines the issuance probability of specific card information to be higher than that of other card information based on the characteristics (the card type and other conditions).

[0069] The determination unit 444 may determine the issuance probability based on the user's attributes in addition to the detected behavior, the specific location, the specified service, etc. For example, even for the same behavior (check-in), the probability of issuing the same type of card information may be different for an individual check-in and a family check-in. This allows different card information to be assigned depending on whether the check-in process is for an individual or a family check-in. The determination unit 444 may also determine the issuance probability based on the number or combination of cards owned by the user in addition to the detected behavior, the specific location, the specified service, etc. For example, a user who owns a predetermined number of cards with relatively low rarity may be more likely to be issued a card with a relatively high rarity. Alternatively, the determination unit 444 may determine the service to be provided based on the number or combination of cards owned by the user in addition to the detected behavior, the specific location, the specified service, etc. For example, a service may be provided by collecting (obtaining) a predetermined number or more of cards with relatively low rarity. This can contribute to an increase in the repeat rate for the service.

[0070] The determination unit 444 may also determine that specific card information can be issued at a rarity different from the standard rarity defined in the card definition information 412, depending on the detected behavior, the specific location, the specified service, or the like. That is, the determination unit 444 can change the rarity based on the type of airport (e.g., Haneda, Osaka, etc.), the location within the airport, the detected behavior, the detected service, or the like. For example, the determination unit 444 may determine a low issuance probability or rarity for general procedures performed at each authentication terminal 200 before boarding, and a high issuance probability or rarity for interactions with specific staff, purchases at shops, lounges, etc. Here, general boarding includes, but is not limited to, check-in, baggage drop-off, immigration, boarding gates, etc. For example, the determination unit 444 may determine a high issuance probability or rarity for procedures such as check-in using facial authentication via the authentication terminal 200, compared to procedures using a paper ticket. This can contribute to increasing the number of people who register facial information for facial authentication and use facial authentication procedures. Furthermore, the determination unit 444 may determine the rarity level according to the usage status of the service (for example, reservation status) in addition to the detected behavior, the specific location, or the specified service. For example, during the off-season of the service (a period with few reservations), the determination unit 444 may determine the rarity level to be higher than usual. This may contribute to attracting customers to the service.

[0071] Furthermore, in response to a use request for a owned card, the determination unit 444 determines the use content based on the characteristics (use content 41224, etc.) defined for the owned card. In response to a use request specifying two or more owned cards, the determination unit 444 determines the use content based on a combination of characteristics defined for the specified owned cards. Specifically, the determination unit 444 determines the use content based on the combination definition 4152. In response to a use request for converting a owned card into electronic value information (points, etc.), the determination unit 444 determines the value information (number of points, etc.) after conversion into the electronic value information as the use content based on the characteristics defined for the owned card. In response to a use request for changing a service level using a owned card, the determination unit 444 determines the changed service level as the use content based on the characteristics defined for the owned card. In addition, the determination unit 444 may determine the use content based on a standard rarity defined for the owned card or a rarity at the time of issuance determined by the determination unit 444. For example, the determination unit 444 may determine a higher number of points or a higher service level as the rarity increases. In other words, the higher the rarity, the higher the return rate may be. Furthermore, in response to a use request for a owned card, the determination unit 444 may determine the usage content based on the rarity determined by the determination unit 444 in addition to the characteristics defined for the owned card.

[0072] The issuing unit 445 is an example of the issuing unit 12 described above. The issuing unit 445 issues one or more pieces of card information based on the determined issuance probability. Specifically, the issuing unit 445 determines whether or not card information needs to be issued for each card type based on the issuance probability, and issues a new card ID corresponding to the card type determined to need issuance. Furthermore, when the determination unit 444 determines the rarity of card information, the issuing unit 445 sets the determined rarity as the rarity of the card information to be issued. In other words, even if the type of card information is the same, card information of different rarities may be issued depending on the detected behavior, the specified location, the specified service, etc. For example, in a location that is used less frequently by users (is less popular), by setting the rarity at the time of issuance higher than the reference rarity, it becomes easier to guide users to the location.

[0073] The notification unit 446 notifies the terminal of the user involved in the detected behavior of the issued card information. Specifically, the notification unit 446 transmits the issued card information to the notification destination included in the identified user information 413.

[0074] 9 is a sequence diagram showing the flow of card issuing processing according to embodiment 2. It is assumed that user U2 carrying user terminal 100-2 is present in front of authentication terminal 200 in area 602.

[0075] At this time, the authentication terminal 200 photographs the face of user U2 (S301). Then, the authentication terminal 200 transmits an authentication request including the photographed face image and terminal position information to the card information management device 400 via the network N (S302). In response to this, the authentication control unit 442 of the card information management device 400 receives the authentication request from the authentication terminal 200 via the network N. Then, the authentication control unit 442 extracts a face image from the authentication request, and transmits a face authentication request including the face image to the authentication device 500 via the network N (S303). In response to this, the authentication device 500 performs face authentication processing (S304).

[0076] FIG. 10 is a flowchart showing the flow of face authentication processing by the authentication device according to the second embodiment. First, the authentication device 500 receives a face authentication request from the card information management device 400 via the network N (S211). The authentication device 500 may also receive a face authentication request from the user terminal 100, the authentication terminal 200, or the like. Next, the authentication device 500 extracts face feature information from the face image included in the face authentication request, similar to steps S202 and S203 described above. Then, the authentication unit 550 of the authentication device 500 compares the face feature information extracted from the face image included in the face authentication request with the face feature information 512 in the face information DB 510 (S212) and calculates the degree of match. Then, the authentication unit 550 determines whether the degree of match is equal to or greater than a threshold (S213). If the face feature information matches, that is, if the degree of match of the face feature information is equal to or greater than a threshold, the authentication unit 550 identifies the user ID 511 associated with the face feature information 512 (S214). Then, the authentication unit 550 returns the face authentication result, including the fact that the face authentication was successful and the identified user ID 511, to the card information management device 400 via the network N (S215). If the degree of match is less than the threshold in step S213, the authentication unit 550 returns the face authentication result, including the fact that the face authentication was unsuccessful, to the card information management device 400 via the network N (S216).

[0077] Returning to FIG. 9, the explanation will be continued. The authentication control unit 442 of the card information management device 400 receives the face authentication result from the authentication device 500 via the network N (S305). Here, the face authentication result includes a message indicating that face authentication was successful and the user ID. The identification unit 443 determines whether face authentication was successful or not based on the face authentication result. If the face authentication result indicates that face authentication was unsuccessful, the notification unit 446 returns a message indicating that authentication was unsuccessful to the authentication terminal 200 via the network N.

[0078] Here, the description will be continued assuming that face authentication is successful. Therefore, the identification unit 443 identifies the user information, the detection behavior, the detection location, and the service (S306). Specifically, the identification unit 443 identifies the user information 413 corresponding to the user ID 4131 included in the face authentication result. The identification unit 443 may also identify the membership rank 4133 included in the identified user information 413. The identification unit 443 also identifies the location where the user behavior was detected (detection location) from the terminal location information included in the authentication request. For example, the identification unit 443 identifies the area 602 where the user U2 is staying (detection location), the service provided in the area 602, and the behavior for using the service (detection behavior) from the location information of the authentication terminal 200. The detection behavior in this example is the behavior of performing face authentication in order to use the service provided in the area 602.

[0079] As described above, the method for detecting user behavior is not limited to facial authentication. That is, the authentication request may be other biometric authentication or personal authentication. Furthermore, when the user terminal 100 launches a specific application, the user terminal 100 may notify the card information management device 400 of the launch via the network N. In response to the notification, the identification unit 443 detects, as a user behavior, that the specific application has been launched in order to use the service of the specific application. Alternatively, in response to the notification, the identification unit 443 detects the service of the specific application as a service that the user U1 intends to use.

[0080] Furthermore, when user U1 moves near area 601 to use a specific service, user terminal 100-1 establishes a connection with wireless base station 300. At this time, either wireless base station 300 or user terminal 100-1 may transmit a connection establishment notification including the base station ID of wireless base station 300 and the terminal ID of user terminal 100-1 to card information management device 400. In response to this notification, identification unit 443 detects that user U1 has moved near area 601 and that the service user U1 is attempting to use is a service provided in area 601. Furthermore, identification unit 443 identifies area 601 where user U1 is staying from the base station ID included in the notification. Furthermore, identification unit 443 can identify the user ID from the terminal ID included in the notification by referring to user information 413. Therefore, identity authentication is possible even in the case of this notification. Wireless base station 300 may be installed in an aircraft. In this case, the identifying unit 443 can detect from the base station ID included in the notification that the user U1 has passed through the boarding gate and that the specific location is inside the aircraft.

[0081] Alternatively, the authentication terminal 200 and the user terminal 100-2 may establish a connection via near field communication. At this time, either the authentication terminal 200 or the user terminal 100-2 may transmit a connection establishment notification to the card information management device 400, including the terminal location information of the authentication terminal 200 and the terminal ID of the user terminal 100-2. In response to this notification, the identification unit 443 detects that the user U2 has moved near the authentication terminal 200 and that the service that the user U2 is attempting to use is a service provided by the authentication terminal 200. The identification unit 443 also identifies the area 602 where the user U2 is staying from the terminal location information of the authentication terminal 200 included in the notification. The identification unit 443 can also identify the user ID from the terminal ID included in the notification by referring to the user information 413. Therefore, personal authentication is possible even in the case of this notification.

[0082] Furthermore, the staff terminal 100-4 and the user terminal 100-3 may establish a connection via near-field wireless communication. At this time, either the staff terminal 100-4 or the user terminal 100-3 may transmit a connection establishment notification to the card information management device 400, including the terminal IDs and location information of the staff terminal 100-4 and the user terminal 100-3. In response to this notification, the identification unit 443 detects that user U3 received customer service (behavior) from staff U4 and that the service (customer service) used by user U3 was provided by staff U4. Furthermore, the identification unit 443 identifies the area 603 where user U3 is staying from the location information included in the notification. Furthermore, the identification unit 443 can identify the user ID from the terminal ID included in the notification by referring to the user information 413. Therefore, identity authentication is possible even in the case of this notification.

[0083] Returning to FIG. 9, the explanation will be continued. Then, the determination unit 444 performs an issuance probability determination process (S307). Fig. 11 is a flowchart showing the flow of the issuance probability determination process according to the second embodiment. The issuance probability determination process determines the issuance probability for each type of card for each of the multiple pieces of card definition information (card types) defined in the card definition information 412. Note that, as described above, it is assumed here that the card definition information 412 includes one or more pieces of card definition information.

[0084] First, the determination unit 444 selects an unselected card type from the card definition information 412 (S321). That is, the determination unit 444 selects the first card type for which the issuance probability is to be determined. Note that, depending on the detection behavior, detection location, and detection service, the issuance probability may be determined for only some of the card types in the card definition information 412. In this case, the determination unit 444 selects the card type for which the issuance probability is to be determined according to the detection behavior, etc.

[0085] Next, the determination unit 444 acquires the standard issuance probability 4123 and the issuance conditions 41223 associated with the selected card type 41221 (or card definition ID 4121) (S322). Then, the determination unit 444 determines the issuance probability based on the detection behavior, the detection location, the detection service, the card type, the standard issuance probability, and the issuance conditions (S323). For example, if the detection behavior, the detection location, the detection service, etc. match the issuance conditions, the determination unit 444 determines the issuance probability by adding an increase / decrease value included in the issuance conditions to the standard issuance probability of the card type. On the other hand, if the detection behavior, the detection location, the detection service, etc. do not match the issuance conditions, the determination unit 444 determines the issuance probability by subtracting an increase / decrease value included in the issuance conditions from the standard issuance probability of the card type. For example, if the issuance conditions are limited to a specific behavior, a specific location, or a specific service, the determination unit 444 may determine the issuance probability of the card type to 0. Note that the determination unit 444 may also take the user's membership rank into account when determining the issuance probability.

[0086] Thereafter, the determination unit 444 determines whether there are any unselected card types (S324). If there are any unselected card types (NO in S324), the process returns to step S321, where the determination unit 444 selects one of the unselected card types. That is, the determination unit 444 selects the second or subsequent card types (S321), and determines the issuance probability for the selected card types in steps S322 and S323. On the other hand, if there are no unselected card types (YES in S324), that is, if issuance probabilities have been determined for all card definition information in the card definition information 412, the process proceeds to step S308 in FIG. 9. Note that, in terms of implementation, the issuance probability determination process may first perform the determination in step S324, and then execute steps S321 to S323 if there are any unselected card types (NO in S324). That is, FIG. 11 is merely one example of an algorithm for the issuance probability determination process.

[0087] Returning to FIG. 9, the explanation will be continued. The issuing unit 445 issues one or more pieces of card information based on the determined issuance probability (S308). The issuing unit 445 issues a new card ID corresponding to the card type determined to be required for issuance based on the issuance probability. Then, the identifying unit 443 may identify the contact information (destination information of the user terminal 100-2) of the user U2 whose face authentication was successful from the personal information 4132 included in the user information 413 identified in step S306. Then, the notifying unit 446 notifies the user terminal 100-2 of the card information including the issued card ID, the card type, card contents (image, etc.), etc. via the network N (S309).

[0088] Thereafter, the registration unit 441 registers the card information issued in step S308 as a card owned by user U2 (S310). Specifically, the registration unit 441 associates and registers owned card information 41351 including the issued card ID 41361 and the like in the user information 413. At the same time, the registration unit 441 updates the card information history (S311). Specifically, the registration unit 441 sets the date and time 4141 to the authentication date and time or the detection date and time, sets the process type 4142 to issue or possession, sets the user ID 4143 to the user ID of user U2, and sets the card ID 41441 to the card ID issued in step S308. Then, the registration unit 441 associates and registers the date and time 4141, the process type 4142, the user ID 4143, and the card ID 41441 in the card information history 414. If two or more pieces of card information are issued in step S308, the registration unit 441 registers each piece of card information in the user information 413 and the card information history 414.

[0089] After step S309, the user terminal 100-2 receives the card information from the card information management device 400 via the network N and displays the card information on the screen (S312). Then, the user terminal 100-2 stores the received card information in the storage unit 120 (S313).

[0090] In this way, card information issued to a certain user can be appropriately registered and managed. In particular, card information in the user terminal can be appropriately synchronized with information on owned cards managed by the card information management device 400.

[0091] 12 is a diagram showing an example of displaying card information according to the second embodiment. Here, an example is shown in which user U2 has been checked in after successfully passing face authentication at the check-in terminal (authentication terminal 200), and card information 801 has been issued. An example is shown in which the user terminal 100 displays card information 801 on the card information display screen 71. The card information 801 indicates that the rarity is normal.

[0092] FIG. 13 is a diagram showing an example of displaying multiple pieces of card information according to the second embodiment. Here, an example is shown in which user U3 inquires about and is served by staff member U4, resulting in the issuance of two pieces of card information 802 and 803. An example is shown in which the user terminal 100 displays card information 802 and 803 on the card information display screen 72. Card information 802 is a card corresponding to staff member U4, and indicates that its rarity is rare. Card information 803 indicates that its rarity is super rare, and was issued as a result of an increase in the issuance probability following the service.

[0093] FIG. 14 is a diagram showing other examples of card information according to the second embodiment. Card information 804 is a card that is issued by any action, and indicates that its rarity is rare. Card information 805 is a card that is issued with an increased probability of being issued by being served by an excellent flight attendant, and indicates that its rarity is super rare. Card information 806 is a card that is issued with a low probability for normal actions, locations, etc., but is issued with an increased probability of being issued under special issuance conditions, and indicates that its rarity is extremely rare.

[0094] Next, an example of a service that applies the card issuance process will be described. First, the user's detection location, which is one of the conditions for issuing card information, is set to various airports. Then, general passengers board a scenic flight conducted to maintain the aircraft's performance, and at each airport visited on the scenic flight, local card information unique to the airport is issued and provided to the user. Scenic flight services may also be provided by charter flights. Furthermore, users may disembark from the aircraft at each airport and use the services available at the airport. This increases the opportunities for users to access various services provided by airports and airlines.

[0095] FIG. 15 is a diagram showing an example of an airport tour plan according to the second embodiment. The airport tour plan connects airports where the scenic flight service takes off, lands, or passes through. For example, after boarding the aircraft, the user terminal of a passenger (passenger) using the scenic flight service establishes a wireless communication connection with the wireless communication base station on board. That is, the wireless communication base station on board can obtain a terminal ID or user ID, etc., from the passenger's user terminal. Then, after taking off from Haneda Airport, the aircraft providing the scenic flight service lands at Sendai Airport. At this time, the wireless communication base station on board establishes a wireless communication connection with the wireless communication base station at Sendai Airport. Then, the wireless communication base station on board notifies the card information management device 400 (via the airport's wireless communication base station) of the location information of Sendai Airport, the terminal ID or user ID of the user terminal with which the connection has been established, and the fact that the scenic flight service is being provided. In response to this, the card information management device 400 determines the probability of issuing local card information corresponding to Sendai Airport to be 100%, issues the local card information to the passenger, and notifies the user terminal of the local card information. The probability of issuing local card information is not limited to 100% and may be higher than usual. Furthermore, from the perspective of infectious disease prevention, the scenic flight service may not land at each airport along the way, but may fly over the vicinity of each airport before returning to the airport from which it took off. In this case, when flying over the vicinity of each airport, the wireless communication base station on the aircraft establishes a wireless communication connection with each airport. The wireless communication base station on the aircraft then notifies the card information management device 400 (via the airport's wireless communication base station) of the airport's location information, the terminal ID or user ID of the user terminal with which the connection has been established, and the fact that the scenic flight service is being offered. As a result, local card information corresponding to the airports passed through is issued to the passenger, as described above.

[0096] 16 is a diagram showing an example of displaying local card information according to the present embodiment 2. Here, an example is shown in which the user terminal 100 displays card information 807 on the card information display screen 73. The card information 807 is an example of local card information for the Tohoku area to which Sendai Airport belongs, and indicates that the rarity is extremely rare.

[0097] After that, the aircraft for the sightseeing flight service takes off from Sendai Airport, then takes off and lands at airports in New Chitose (Hokkaido area), Fukuoka (Kyushu area), Kochi (Shikoku area), Okayama (Chugoku area), Kansai (Kansai area), and Chubu (Chubu area), before landing at Haneda Airport. Then, each time the aircraft lands at an airport, the card information management device 400 issues local card information corresponding to that airport and notifies the user terminal of the local card information.

[0098] FIG. 17 is a diagram showing other examples of local card information according to the second embodiment. Card information 808 is an example of local card information for the Hokkaido area to which New Chitose Airport belongs, and indicates that the rarity is rare. Card information 809 is an example of local card information for the Kyushu area to which Fukuoka Airport belongs, and indicates that the rarity is rare. Card information 810 is an example of local card information for the Kansai area to which Kansai International Airport (Kansai Airport) belongs, and indicates that the rarity is super rare. Card information 811 is an example of local card information for the Chubu area to which Chubu Centrair International Airport belongs, and indicates that the rarity is rare.

[0099] The card information management device 400 may grant additional bonus information when a combination of multiple owned cards registered to a specific user satisfies a predetermined condition. For example, points may be awarded when local card information for all airports where the user takes off and lands in the above-mentioned sightseeing flight service is owned. In other words, when a specific combination of card information is acquired (collected), special points may be awarded as a complete set. This will motivate users to collect various types of card information, further promoting use of the service. Rare card information may be issued as bonus information.

[0100] Next, the card transfer process will be described. As a premise, it is assumed that card X has been registered as a card owned by user U1, and that card information has also been saved in user terminal 100-1. An example will be described in which user U1 then attempts to assign (transfer) card X to user U2.

[0101] 18 is a sequence diagram showing the flow of card transfer processing according to the second embodiment. First, the user terminal 100-1 displays the card information of the card X designated by the user U1 on the screen (S331). Here, the card information includes the code information of the card X, or includes the code information even if it is not displayed. The code information includes identification information such as the card ID, as described above.

[0102] Then, the user terminal 100-2 acquires the code information of card X from the user terminal 100-1 (S332). For example, if the code information of card X is displayed, the user terminal 100-2 takes a picture of the code information of card X displayed on the user terminal 100-1 with a camera by the operation of the user U2. The user terminal 100-2 then identifies the area of ​​the code information from the captured image, analyzes the code information, and identifies the information of card X (such as a card ID) (S333). Note that if the code information of card X is not displayed, the user terminals 100-1 and 100-2 may establish a connection via near-field wireless communication, and the code information of card X may be transferred from the user terminal 100-1 to the user terminal 100-2. In this way, the user terminal 100-2 may acquire the code information of card X from the user terminal 100-1.

[0103] Then, the user terminal 100-2 transmits a transfer request including the information on card X and the user ID of the transfer destination user U2 to the card information management device 400 via the network N (S334).

[0104] In response to this, the card information management device 400 receives a transfer request from the user terminal 100-2 via the network N. Then, the card information management device 400 identifies the user U1 who owns the card X based on the information on the card X included in the transfer request (S335). Specifically, the identification unit 443 identifies the user ID associated with the owned card information including the card ID of the card X from the user information 413.

[0105] Then, the card information management device 400 updates the status of card X of user U1 to used (S336). Also, the card information management device 400 registers card X as a card owned by user U2 (S337). Also, the card information management device 400 updates the card information history 414 (S338). For example, the registration unit 441 sets the date and time 4141 to the date and time of reception of the transfer request, the process type 4142 to "transfer", the user ID 4143 to the user ID of user U2 who is the transfer destination, and the card ID 41441 to the card ID of card X. Then, the registration unit 441 registers a record associating these in the card information history 414.

[0106] After that, the card information management device 400 may transmit a transfer process completion notification to the user terminal 100-1, which is the transfer source of the card information, and the user terminal 100-2, which is the transfer destination of the card information. In response to this, the user terminal 100-1 deletes the card information 122 of the card X from the storage unit 120, and the user terminal 100-2 saves the card information 122 of the card X in the storage unit 120.

[0107] In this way, the transfer process of a user's owned card (card information) to another user can be appropriately controlled. In particular, the card information in the user terminal and the owned card information managed by the card information management device 400 can be appropriately synchronized.

[0108] Next, the card exchange process will be described. As a premise, it is assumed that card X has been registered as a card owned by user U1, and that card information has also been saved in user terminal 100-1. It is also assumed that card Y has been registered as a card owned by user U2, and that card information has also been saved in user terminal 100-2. An example will be described in which users U1 and U2 attempt to exchange cards X and Y.

[0109] 19 is a sequence diagram showing the flow of the card exchange process according to the second embodiment. First, the user terminal 100-1 accepts designation of card X, which is the object of exchange, from user U1 (S341). Furthermore, the user terminal 100-2 accepts designation of card Y, which is the object of exchange, from user U2 (S342). Then, the user terminal 100-1 transmits information about card X to the user terminal 100-2 (S343). Furthermore, the user terminal 100-2 transmits information about card Y to the user terminal 100-1 (S344).

[0110] For example, as described above, the user terminals 100-1 and 100-2 may establish a short-range wireless communication connection. In this case, the code information of card X may be transferred from the user terminal 100-1 to the user terminal 100-2, and the code information of card Y may be transferred from the user terminal 100-2 to the user terminal 100-1. In other words, the card information to be exchanged may be exchanged between the user terminals through direct communication between the user terminals. Alternatively, the user terminal 100-2 may transmit the code information of card Y to the user terminal 100-1 in response to receiving the code information of card X from the user terminal 100-1.

[0111] Alternatively, when the code information of the card is displayed, the user terminal 100-2 takes a picture of the code information of card X displayed on the user terminal 100-1 with a camera in response to an operation by the user U2. Similarly, the user terminal 100-1 may take a picture of the code information of card Y displayed on the user terminal 100-2 with a camera in response to an operation by the user U1.

[0112] Then, user terminal 100-1 transmits an exchange request including information on cards X and Y to card information management device 400 via network N (S345). For example, user terminal 100-1 performs step S345 after transmitting card X to user terminal 100-2 and receiving card Y from user terminal 100-2. Note that user terminal 100-2 may also perform step S345. In that case, step S344 may be omitted.

[0113] In response to this, the card information management device 400 receives an exchange request from the user terminal 100-1 via the network N. Then, the card information management device 400 identifies the user U1 who owns the card X and the user U2 who owns the card Y based on the information on the cards X and Y included in the exchange request (S346). Specifically, the identification unit 443 identifies, from the user information 413, the user ID associated with the owned card information including the card ID of the card X and the user ID associated with the owned card information including the card ID of the card Y.

[0114] Then, the card information management device 400 converts the received exchange request into a first transfer request and a second transfer request (S347). Specifically, the card information management device 400 generates a first transfer request for transferring card X from user U1, the current owner, to user U2, the exchange destination. At the same time, the card information management device 400 generates a second transfer request for transferring card Y from user U2, the current owner, to user U1, the exchange destination.

[0115] Thereafter, the card information management device 400 processes this as a first transfer request (S348). That is, the card information management device 400 updates the status of card X of user U1 to used, and registers card X as a card owned by user U2. Also, the card information management device 400 processes this as a second transfer request (S349). That is, the card information management device 400 updates the status of card Y of user U2 to used, and registers card Y as a card owned by user U1.

[0116] Further, the card information management device 400 updates the card information history 414 (S350). For example, the registration unit 441 sets the date and time 4141 to the date and time of receiving the exchange request, the process type 4142 to "exchange", the user ID 4143 to the user ID of the user U2 who is the exchange destination, and the card ID 41441 to the card ID of card X. Then, the registration unit 441 registers a record associating these in the card information history 414. Similarly, the registration unit 441 sets the date and time 4141 to the date and time of receiving the exchange request, the process type 4142 to "exchange", the user ID 4143 to the user ID of the user U1 who is the exchange destination, and the card ID 41441 to the card ID of card Y. Then, the registration unit 441 registers a record associating these in the card information history 414.

[0117] Thereafter, card information management device 400 may transmit a completion notification of the exchange process to user terminals 100-1 and 100-2, which are the card information exchange terminals. In response to this, user terminal 100-1 deletes card information 122 of card X from storage unit 120, and stores card information 122 of card Y in storage unit 120. Similarly, user terminal 100-2 deletes card information 122 of card Y from storage unit 120, and stores card information 122 of card X in storage unit 120.

[0118] In this way, the exchange process of owned cards (card information) between users can be appropriately controlled. In particular, the card information in the user terminal can be appropriately synchronized with the owned card information managed by the card information management device 400. Furthermore, by converting one exchange request into a combination of two transfer requests and applying the transfer request processing twice, the unique processing of the exchange request can be reduced and the system can be implemented efficiently.

[0119] Next, the card use process will be described. As a premise, it is assumed that card Z and card W have been registered as cards owned by user U1, and that the card information has also been saved in user terminal 100-1. In this case, an example will be described in which user U1 uses a combination of cards Z and W for point exchange.

[0120] 20 is a sequence diagram showing the flow of card use processing according to the second embodiment. First, the user terminal 100-1 accepts designation of cards Z and W to be used from user U1 (S351). Next, the user terminal 100-1 accepts designation of point exchange as the card use content from user U1 (S352). In response to this, the user terminal 100-1 transmits a use request including point exchange as the use content and cards Z and W as the card use objects to the card information management device 400 via the network N (S353).

[0121] In response to this, the card information management device 400 receives a use request from the user terminal 100-1 via the network N. Then, the card information management device 400 identifies the user U1 who owns the cards Z and W based on the information on the cards Z and W included in the use request (S354). Specifically, the identification unit 443 identifies the user ID associated with the combination of the owned card information including the card ID of the card Z and the owned card information including the card ID of the card W from the user information 413.

[0122] Then, the card information management device 400 determines the number of points to be exchanged based on the combination of cards Z and W (S355). Specifically, the determination unit 444 specifies a reference value for the number of points to be exchanged based on the exchange definition 4151 of the card use conditions 415. Furthermore, the determination unit 444 determines an increment in the number of points corresponding to the combination of cards Z and W based on the combination definition 4152 of the card use conditions 415. Then, the determination unit 444 determines the number of points to be exchanged by adding the increment in the number of points to the specified reference value of the number of points. For example, in the case of a combination of cards with low rarity, the number of points to be exchanged is the reference value. On the other hand, in the case of a combination of cards with high rarity, the number of points to be exchanged is the reference value plus a larger increment. Note that a multiplier may be used instead of the increment.

[0123] Then, the card information management device 400 adds the determined number of points to the owned points 4134 of user U1 (S356). At the same time, the card information management device 400 updates the status of cards Z and W of user U1 to used (S357). The card information management device 400 also updates the card information history 414 (S358). For example, the registration unit 441 sets the date and time 4141 to the date and time of reception of the use request, the process type 4142 to "used", the user ID 4143 to the user ID of user U1 who is the user, the card ID 41441 to the card ID of card Z, and the card ID 41442 to the card ID of card W. Then, the registration unit 441 registers a record associating these in the card information history 414.

[0124] After that, the card information management device 400 may transmit a notification of completion of the use process (point exchange) to the user terminal 100-1, which is the terminal for using the card information. In response to this, the user terminal 100-1 deletes the card information 122 of cards Z and W from the storage unit 120.

[0125] In this way, it is possible to appropriately control the usage process (point exchange) of a user's owned card (card information). In particular, it is possible to appropriately synchronize the card information in the user terminal with the owned card information managed by the card information management device 400.

[0126] In addition, the above-described card transfer process, card exchange process, and card use process preferably require the user's approval and passcode, etc., in addition to the transfer request, exchange request, and use request. This is to prevent unauthorized transfer, exchange, and use of card information. For example, in the above-described card transfer process, the user terminal 100-2 acquires a passcode from the user terminal 100-1 of the transfer source user U1 and includes the passcode in the transfer request. If the transfer request at S334 in FIG. 18 includes the passcode of the transfer source user U1, the card information management device 400 may perform the transfer process from S335 onwards. Also, in the card exchange process, the user terminal 100-1 acquires a passcode from the user terminal 100-2 of the exchange target user U2 and includes the passcode in the exchange request. If the exchange request at S345 in FIG. 19 includes the passcode of the exchange target user U2, the card information management device 400 may perform the exchange process from S346 onwards. In addition, in the card use processing, the user terminal 100-1 acquires a passcode from the point exchanger user U1 and includes the passcode in the use request. If the use request at S353 in FIG. 20 includes the passcode of the point exchanger user U1, the card information management device 400 may perform the use processing from S354 onwards. Alternatively, in the card transfer processing or card exchange processing, the card information management device 400 may, upon receiving a transfer request or exchange request, transmit an approval request for the request to the other user terminal, and, upon receiving approval, perform the card transfer processing or card exchange processing. In addition, in the card use processing, the card information management device 400 may, upon receiving a use request, transmit an approval request for the request to the user terminal of the user who is the point exchanger, and, upon receiving approval, perform the card use processing.

[0127] Recently, with the spread of infectious diseases, the use of public transportation by ordinary passengers, such as families, has decreased. Therefore, measures to increase the number of users of certain services are needed. However, simply issuing cards randomly when using a service, as in Patent Document 1, is insufficient as a measure to increase the number of users of the service. Therefore, in this second embodiment, users can obtain various types of card information based on behavior related to the use of the service. Therefore, users may fly for reasons such as collecting cards or exchanging them for miles. This can revitalize the aviation industry, including airlines. In particular, in this second embodiment, the probability of issuing card information is determined based on services identified from detected user behavior. Unlike random issuance probability, the probability of issuing card information varies to some extent depending on user behavior. On the other hand, even for the same location or behavior, different card information may be issued. This further motivates users to collect card information. Furthermore, the card information issuance service may be provided to employees and their families of airline partner companies. Furthermore, since the higher the rarity, the better the points and services earned, which encourages users to seek out rarer cards, further revitalizing the service.

[0128] In the second embodiment, the services provided to the user are exemplified by services provided by transportation means such as public transport. Examples of transportation means include, but are not limited to, airplanes, trains, buses, taxis, ships, etc. Therefore, the detection unit according to the second embodiment can be said to detect user behavior related to the use of services by transportation means. However, the services provided to the user are not limited to these.

[0129] <Embodiment 3> The third embodiment is a modification of the second embodiment described above. In the third embodiment, a physical card is issued as the card information. Here, the physical card is not an electronic medium, but a paper medium or a plastic card on which card information is printed or displayed, or a card with a plastic-coated IC chip on which card information is electronically recorded.

[0130] Physical cards have a significant effect of encouraging users to collect cards and promoting service use. However, it is necessary to take measures to prevent the resale of physical cards and unauthorized use by people other than the card owner. Therefore, the card information management device 400 needs to properly manage the physical cards issued to and owned by each user in the user information 413.

[0131] Fig. 21 is a block diagram showing the overall configuration of a card information management system 1000a according to the third embodiment. Compared to the above-described Fig. 3, the card information management system 1000a further includes a card issuance terminal 301 installed in area 602, and the card information management device 400 is replaced with a card information management device 400a. A physical card 820 is a card issued by the card issuance terminal 301 in response to an issuance instruction from the card information management device 400a. Note that Fig. 21 does not illustrate area 603. The other configuration is the same as that of the above-described Fig. 3, and therefore, in the following explanation, illustrations and explanations of overlapping parts will be omitted as appropriate.

[0132] Card issuance terminal 301 is an information terminal connected to network N. Alternatively, card issuance terminal 301 may be connected to authentication terminal 200. Card issuance terminal 301 issues physical card 820 in response to an issuance instruction from card information management device 400a. Card issuance terminal 301 may print card information 821 included in the issuance instruction on a paper medium or a plastic card to create physical card 820. Alternatively, card issuance terminal 301 may record card information 821 included in the issuance instruction on a card with an IC chip embedded in advance to create physical card 820. A card with an embedded IC chip may be, for example, a contactless IC card.

[0133] User U2 receives a physical card 820 issued by the card issuing terminal 301. In response to an operation by user U2, user terminal 100-2 may read code information from the issued physical card 820, analyze the code information, and store the identified card information 122 in the storage unit 120. Furthermore, user terminal 100-2 may transmit a registration request including card information 821 printed or recorded on the physical card 820 and user U2's user ID, etc., to the card information management device 400a. In other words, user terminal 100-2 may transmit the registration request in response to user U2's user terminal 100-2 reading card information 821 recorded on the physical card 820 issued by the card issuing terminal 301 in response to an issuance instruction.

[0134] The issuing unit 445 of the card information management device 400a transmits an issuance instruction for the issued card information to the card issuing terminal 301 installed at the location where the detected behavior was performed. The issuance instruction may include an instruction to readably record the issued card information as the physical card 720 described above.

[0135] In response to the above-mentioned registration request, the registration unit 441 of the card information management apparatus 400a registers the issued card information as a card owned by the user.

[0136] 22 is a sequence diagram showing the flow of the physical card issuance process according to the third embodiment. Here, it is assumed that a behavior related to the use of a service has been detected for user U2 staying in area 602. First, after step S308 in FIG. 9 described above, the issuing unit 445 of the card information management device 400a transmits an instruction to issue a physical card on which the issued card information is readably recorded to the card issuing terminal 301 installed in area 602 (S401).

[0137] In response to this, the card issuance terminal 301 receives an issuance instruction from the card information management device 400a via the network N. Then, in response to the received issuance instruction, the card issuance terminal 301 issues a physical card P having card information 821 recorded on an IC chip (S402).

[0138] Then, in response to an operation by user U2, user terminal 100-2 reads code information from physical card P using a camera or a contactless IC card reader (not shown) (S403). User terminal 100-2 analyzes the read code information and stores the identified card information 122 in storage unit 120 (S404). Furthermore, user terminal 100-2 transmits a registration request including the read card information 821 (card P) and user U2's user ID, etc., to card information management device 400a via network N (S405).

[0139] In response to this, the card information management device 400a receives a registration request from the user terminal 100-2 via the network N. Then, the card information management device 400a identifies the card P included in the registration request and the user U2 corresponding to the user ID. Then, the card information management device 400a registers the card P as a card owned by the user U2 (S406). In addition, the card information management device 400a updates the card information history 414 (S407).

[0140] In this way, also in this embodiment 3, it is possible to appropriately register and manage card information of a physical card issued to a certain user. In particular, it is possible to appropriately synchronize the card information of a physical card actually possessed by the user, the card information in the user terminal, and the information of the possessed card managed by the card information management device 400a.

[0141] Therefore, even if another user attempts to use a physical card other than the one owned by the user without properly performing the card transfer process, the card information management device 400a can prevent the use. For example, assume that user U1 reads the code information of a physical card P that he obtained illegally using the user terminal 100-1. At this time, the user terminal 100-1 analyzes the read code information to obtain card information, and after steps S351 and S352 of FIG. 20 described above, transmits a use request for the physical card P to the card information management device 400a. In this case, the card information management device 400a identifies user U2 who owns card P based on the information on card P included in the received use request. Therefore, the card information management device 400a determines that user U1 is not the owner of card P because user U1 included in the received use request and the identified user U2 are different. Therefore, the card information management device 400a replies to the user terminal 100-1 via the network N to the effect that the use request is not permitted and does not perform the use process. This also applies to transfer requests and exchange requests. Therefore, even for physical cards, unauthorized use, transfer, and exchange can be prevented. As with the second embodiment described above, it is desirable that the card transfer process, card exchange process, and card use process require the approval of the relevant user, a passcode, etc., in addition to the transfer request, exchange request, and use request.

[0142] <Other embodiments> In the above-mentioned second and third embodiments, the card information management device 400 and the authentication device 500 have been described as separate information processing devices, but they may be the same. For example, the card information management device 400 may further associate and register facial feature information with the user ID 4131 of the user information 413. In this case, the control unit 440 may further include the functions of the face detection unit 520, feature point extraction unit 530, registration unit 540, and authentication unit 550 in FIG. 6.

[0143] In the above examples, the program includes instructions (or software code) that, when loaded into a computer, cause the computer to perform one or more functions described in the embodiments. The program may be stored on a non-transitory computer-readable medium or a tangible storage medium. By way of example and not limitation, computer-readable medium or tangible storage medium includes random-access memory (RAM), read-only memory (ROM), flash memory, solid-state drive (SSD) or other memory technology, CD-ROM, digital versatile disc (DVD), Blu-ray® disc or other optical disk storage, magnetic cassette, magnetic tape, magnetic disk storage or other magnetic storage device. The program may also be transmitted on a transitory computer-readable medium or communication medium. By way of example and not limitation, transitory computer-readable medium or communication medium includes electrical, optical, acoustic, or other forms of propagated signals.

[0144] The present disclosure is not limited to the above-described embodiments, and may be modified as appropriate without departing from the spirit and scope of the present disclosure. In addition, the present disclosure may be implemented by appropriately combining the respective embodiments.

[0145] Some or all of the above embodiments can be described as, but are not limited to, the following supplementary notes. (Appendix 1) A detection means for detecting user behavior related to the use of a predetermined service; an issuing means for issuing card information corresponding to a part of a plurality of types of card information having different characteristics defined therein based on the service related to the detected behavior; a registration means for registering the issued card information as a card owned by the user related to the detected behavior; A card information management device comprising: (Appendix 2) The card issuing device further includes a notification unit for notifying the user's terminal of the issued card information. 2. A card information management device according to claim 1. (Appendix 3) The detection means When the user is successfully authenticated via an authentication terminal installed at a specific location, the behavior is detected as the behavior. 3. A card information management device according to claim 1 or 2. (Appendix 4) further comprising a determination means for determining an issuance probability of each of the plurality of types of card information based on the service related to the detected behavior; The issuing means issues card information corresponding to a part of the plurality of types of card information based on the determined issuance probability. A card information management device according to any one of appendices 1 to 3. (Appendix 5) The determining means When the detected behavior satisfies a probability increase condition, the issuance probability is determined to be higher for specific card information compared to other card information based on the characteristics. 5. A card information management device according to claim 4. (Appendix 6) The probability increasing condition is: The detected behavior includes at least one of the following: the behavior was performed at a specific location; or the service level provided to the user related to the behavior detected is equal to or higher than a predetermined level. 6. A card information management device according to claim 5. (Appendix 7) The probability increasing condition is: This includes successful authentication of the user via an authentication terminal installed at a specific location. 7. A card information management device according to claim 5 or 6. (Appendix 8) The determining means In response to a request for use of the owned card, determining the content of use based on the characteristics defined in the owned card; The registration means The determined usage details are registered in association with the user of the card, and the card of the user is updated as used. A card information management device according to any one of appendixes 4 to 7. (Appendix 9) The determining means determining the content of use based on a combination of characteristics defined in each of the designated owned cards in response to the use request specifying two or more of the owned cards; The registration means The determined usage details are registered in association with the user of the owned card, and each of the designated owned cards of the user is updated as used. 9. A card information management device according to claim 8. (Appendix 10) The determining means In response to the use request for converting the owned card into electronic value information, the value information after conversion into the electronic value information is determined as the use content based on the characteristics defined in the owned card. 10. A card information management device according to claim 8 or 9. (Appendix 11) The determining means In response to the usage request for changing the service level using the owned card, the changed service level is determined as the usage content based on the characteristics defined in the owned card. A card information management device according to any one of appendixes 8 to 10. (Appendix 12) The registration means When a transfer request for transferring the owned card from a first user to a second user is received, the owned card of the first user is marked as used, and the owned card is registered in association with the second user. A card information management device according to any one of appendixes 1 to 11. (Appendix 13) The registration means receiving the transfer request transmitted by the owned card displayed on the first terminal of the first user being read by the second terminal of the second user; 13. A card information management device according to claim 12. (Appendix 14) The registration means When receiving a request to exchange a first owned card of a first user with a second owned card of a second user, process the request as if a first transfer request for transferring the first owned card from the first user to the second user and a second transfer request for transferring the second owned card from the second user to the first user have been received. 14. A card information management device according to claim 12 or 13. (Appendix 15) The issuing means transmits an instruction to issue a physical card on which the issued card information is readably recorded to a card issuing terminal installed at the location where the action was performed; The registration means The card information recorded on the physical card issued by the card issuing terminal in response to the issuance instruction is read by the user's terminal, and in response to a registration request transmitted, the issued card information is registered as a card owned by the user. A card information management device according to any one of appendices 1 to 14. (Appendix 16) The registration means If a combination of a plurality of owned cards registered in association with the user satisfies a benefit condition, predetermined benefit information is registered in association with the user. A card information management device according to any one of appendixes 1 to 15. (Appendix 17) The detection means Detecting user behavior related to the use of transportation services A card information management device according to any one of appendixes 1 to 16. (Appendix 18) The service is a service related to at least one of use of facilities or equipment at an airport, procedures at the airport, or use of an aircraft, The detection means The system detects as the user's behavior at least one of the following: an application for using the service has been launched on a user terminal operated by the user; the user terminal has received radio waves from a wireless base station installed at a specific point in the airport and established a connection; the user has successfully authenticated themselves via an authentication terminal installed at a specific point in the airport; a connection has been established between the authentication terminal and the user terminal via short-range wireless communication; the authentication terminal has detected that the user carrying the user terminal has passed through the specific point in the airport; or a connection has been established between a staff terminal carried by a staff member of the airport or airline and the user terminal via short-range wireless communication. A card information management device according to any one of appendixes 1 to 17. (Appendix 19) The services include services relating to at least one of the procedures at the airport, such as boarding procedures, baggage check-in, security check, immigration control, or passenger confirmation for an aircraft. A card information management device according to any one of appendixes 1 to 18. (Appendix 20) a detection device that detects user behavior related to the use of a predetermined service; a card information management device, The card information management device an issuing means for issuing card information corresponding to a part of a plurality of types of card information having different characteristics defined therein, based on the service related to the behavior detected by the detecting device; a registration means for registering the issued card information as a card owned by the user related to the detected behavior; A card information management system comprising: (Appendix 21) The card information management device The card issuing device further includes a notification unit for notifying the user's terminal of the issued card information. 20. A card information management system as described in Appendix 20. (Appendix 22) The computer Detecting user behavior related to the use of a given service; issuing card information corresponding to a part of a plurality of types of card information having different characteristics defined therein based on the service related to the detected behavior; registering the issued card information as a card owned by the user related to the detected behavior; How to manage card information. (Appendix 23) A detection process for detecting user behavior related to the use of a predetermined service; an issuance process for issuing card information corresponding to a part of multiple types of card information having different characteristics defined based on the service related to the detected behavior; a registration process for registering the issued card information as a card owned by the user related to the detected behavior; A non-transitory computer-readable medium storing a card information management program that causes a computer to execute the above.

[0146] Although the present invention has been described above with reference to the embodiments (and examples), the present invention is not limited to the above-described embodiments (and examples). Various modifications that can be understood by those skilled in the art can be made to the configuration and details of the present invention within the scope of the present invention. [Explanation of symbols]

[0147] 1. Card information management device 11 Detection unit 12 Publishing Department 13 Registration Department 1000 Card Information Management System 1000a Card Information Management System U1 user U2 users U3 users U4 Staff N Network 100 user terminals 100-1 User terminal 100-2 User terminal 100-3 User terminal 100-4 Staff terminal 110 Camera 120 Storage section 121 Programs 122 Card Information 130 memory 140 Communications Department 150 Input / output section 160 control section 161 Radio Processing Unit 162 Card Processing Unit 163 Display control unit 200 Authentication Terminals 210 Camera 220 Storage section 221 Program 230 memory 240 Communications Department 250 Input / output section 260 Control Unit 261 Display control unit 262 Authentication Request Section 263 Processing Control Unit 300 wireless base stations 301 Card issuing terminal 400 Card information management device 400a Card information management device 410 Storage section 411 Program 412 Card definition information 4121 Card Definition ID 4122 Characteristics Information 41221 Card Type 41222 Card contents 41223 Issue conditions 41224 Usage details 4123 Standard issue probability 413 User Information 4131 User ID 4132 Personal Information 4133 Membership rank 4134 points held 41351 Card Ownership Information 41361 Card ID 41362 Card Definition ID 41363 Status 4135n Card Ownership Information 414 Card Information History 4141 Date and Time 4142 Processing Type 4143 User ID 41441 Card ID 4144m Card ID 415 Card Usage Conditions 4151 Exchange definition 4152 Combination Definition 420 memory 430 Communications Department 440 Control Unit 441 Registration Department 442 Authentication control unit 443 Specific part 444 Decision Section 445 Publishing Department 446 Notification Department 500 Authentication Device 510 Face Information DB 511 User ID 512 facial feature information 520 Face detection unit 530 Feature Point Extraction Unit 540 Registration Department 550 Authentication Department 600 airports 601 Area 602 Area 603 Area 71 Card information display screen 72 Card information display screen 73 Card information display screen 801 Card Information 802 Card Information 803 Card Information 804 Card Information 805 Card Information 806 Card Information 807 Card Information 808 Card Information 809 Card Information 810 Card Information 811 Card Information 820 Physical Card 821 Card Information

Claims

1. An issuing means for issuing card information corresponding to a part of multiple types of card information having different characteristics defined based on a service provider who has provided a service to a user; a registration means for registering the issued card information as a card owned by the user in association with a rarity level related to the service provider; A card information management device comprising:

2. The card issuing device further includes a notification unit for notifying the user's terminal of the issued card information. The card information management device according to claim 1 .

3. The system further comprises a detection means for detecting user behavior related to the use of the service as the user behavior, The detection means When the user is successfully authenticated via an authentication terminal installed at a specific location, the behavior is detected as the behavior.

3. The card information management device according to claim 1.

4. Further comprising: a determination means for determining an issuance probability of each of the plurality of types of card information based on the service; the service is a service related to the detected behavior, The issuing means issues card information corresponding to a part of the plurality of types of card information based on the determined issuance probability. The card information management device according to claim 3.

5. The determining means When the detected behavior satisfies a probability increase condition, the issuance probability is determined to be higher for specific card information compared to other card information based on the characteristics.

5. The card information management device according to claim 4.

6. The probability increasing condition is: The detected behavior includes at least one of the following: the behavior was performed at a specific location; or the service level provided to the user related to the behavior detected is equal to or higher than a predetermined level. The card information management device according to claim 5.

7. The probability increasing condition is: This includes successful authentication of the user via an authentication terminal installed at a specific location.

7. The card information management device according to claim 5 or 6.

8. The determining means In response to a request for use of the owned card, determining the content of use based on the characteristics defined in the owned card; The registration means The determined usage details are registered in association with the user of the card, and the card of the user is updated as used. The card information management device according to any one of claims 4 to 7.

9. The determining means determining the content of use based on a combination of characteristics defined in each of the designated owned cards in response to the use request specifying two or more of the owned cards; The registration means The determined usage details are registered in association with the user of the owned card, and each of the designated owned cards of the user is updated as used. The card information management device according to claim 8.

10. The determining means In response to the use request for converting the owned card into electronic value information, the value information after conversion into the electronic value information is determined as the use content based on the characteristics defined in the owned card.

10. The card information management device according to claim 8 or 9.

11. The determining means In response to the usage request for changing the service level using the owned card, the changed service level is determined as the usage content based on the characteristics defined in the owned card. The card information management device according to any one of claims 8 to 10.

12. The registration means When a transfer request for transferring the owned card from a first user to a second user is received, the owned card of the first user is marked as used, and the owned card is registered in association with the second user. The card information management device according to any one of claims 1 to 11.

13. The registration means The transfer request is received when the owned card displayed on the first terminal of the first user is read by the second terminal of the second user. The card information management device according to claim 12.

14. The registration means When a request for exchanging a first owned card of a first user with a second owned card of a second user is received, the request is processed as if a first transfer request for transferring the first owned card from the first user to the second user and a second transfer request for transferring the second owned card from the second user to the first user have been received. The card information management device according to claim 12 or 13.

15. The issuing means transmits an instruction to issue a physical card on which the issued card information is readably recorded to a card issuing terminal installed at the location where the action was performed; The registration means The card information recorded on the physical card issued by the card issuing terminal in response to the issuance instruction is read by the user's terminal, and in response to a registration request transmitted, the issued card information is registered as a card owned by the user. The card information management device according to any one of claims 3 to 11.

16. The registration means If a combination of a plurality of owned cards registered in association with the user satisfies a benefit condition, predetermined benefit information is registered in association with the user. The card information management device according to any one of claims 1 to 15.

17. The detection means Detecting user behavior related to the use of transportation services 16. The card information management device according to claim 3.

18. The service is a service related to at least one of use of facilities or equipment at an airport, procedures at the airport, or use of an aircraft, The detection means The system detects as the user's behavior at least one of the following: an application for using the service has been launched on a user terminal operated by the user; the user terminal has received radio waves from a wireless base station installed at a specific point in the airport and established a connection; the user has successfully authenticated themselves via an authentication terminal installed at a specific point in the airport; a connection has been established between the authentication terminal and the user terminal via short-range wireless communication; the authentication terminal has detected that the user carrying the user terminal has passed through the specific point in the airport; or a connection has been established between a staff terminal carried by a staff member of the airport or airline and the user terminal via short-range wireless communication.

18. The card information management device according to claim 3, wherein the card information management device is a card information management device.

19. The services include services relating to at least one of the procedures at the airport, such as check-in procedures, baggage check-in, security check-in, immigration control, or passenger confirmation for an aircraft. The card information management device according to any one of claims 1 to 18.

20. A detection device for detecting user behavior related to the use of a service; a card information management device, The card information management device an issuing means for issuing card information corresponding to a part of a plurality of types of card information having different characteristics defined therein, based on a service provider who has provided the service to the user related to the behavior detected by the detecting device; a registration means for registering the issued card information as a card owned by the user in association with a rarity level related to the service provider; A card information management system comprising:

21. The card information management device The card issuing device further includes a notification unit for notifying the user's terminal of the issued card information. The card information management system according to claim 20.

22. The computer issuing card information corresponding to a part of a plurality of types of card information having different characteristics defined therein based on a service provider that has provided a service to the user; registering the issued card information as a card owned by the user in association with a rarity level related to the service provider; How to manage card information.

23. An issuing process for issuing card information corresponding to a part of multiple types of card information having different characteristics defined based on a service provider that has provided a service to a user; a registration process for registering the issued card information as a card owned by the user in association with a rarity level related to the service provider; A card information management program that causes a computer to execute the above.

Images