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

Abstract

This invention provides a card information management device, a card information management system, a card information management method, and a card information management program to promote the use of services. [Solution] The 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 card information corresponding to a portion of a plurality of types of card information with different characteristics defined based on the service related to the detected behavior, and a registration unit 13 that registers the issued card information as the user's owned card related to the detected behavior, and further comprises a notification means for notifying the user's terminal of the issued card information.

Description

Technical Field

[0006] , , , ,

[0001] The present invention relates to a card information management apparatus, system, method, and program, and more particularly to a card information management apparatus, system, method, and program for managing card information issued to a user.

Background Art

[0002] Patent Document 1 discloses a technique related to a game apparatus for providing more entertainment such as arousing the desire to collect cards.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] Recently, measures for increasing the number of users of a predetermined service have been demanded.

[0005] In view of the above problems, an object of the present disclosure is to provide a card information management apparatus, system, method, and program for promoting the use of a service by issuing a card when a user who is a service target uses the service.

Means for Solving the Problems

[0006] The card information management apparatus according to the first aspect of the present disclosure is detection means for detecting a user's behavior related to the use of a predetermined service; issuing means for issuing card information corresponding to a part of a plurality of types of card information having different characteristics based on the service related to the detected behavior; A registration means for registering the issued card information as the card owned by the user related to the detected action, It is equipped with.

[0007] The card information management system relating to the second aspect of this disclosure is: A detection device that detects user behavior related to the use of a specified service, A card information management device is provided, The aforementioned card information management device is An issuing means for issuing card information corresponding to a portion of multiple types of card information with different characteristics defined based on the service related to the action detected by the detection device, A registration means for registering the issued card information as the card owned by the user related to the detected action, It is equipped with.

[0008] The card information management method relating to the third aspect of this disclosure is: Computers Detect user behavior related to the use of a specified service, Based on the services related to the detected behavior, card information corresponding to a portion of multiple types of card information with different characteristics is issued. The issued card information is registered as the card owned by the user associated with the detected action.

[0009] The card information management program relating to the fourth aspect of this disclosure is: A detection process that detects user behavior related to the use of a specified service, Based on the services related to the detected actions, an issuance process is performed to issue card information corresponding to a portion of multiple types of card information with different characteristics defined, A registration process to register the issued card information as the card owned by the user related to the detected action, Have the computer execute it. [Effects of the Invention]

[0010] According to the present disclosure, it is possible to provide a card information management device, a system, a method, and a program for promoting the use of a service by issuing a card when a user who is the target of the service uses the service.

Brief Description of the Drawings

[0011] [Figure 1] It is a block diagram showing the configuration of the card information management device according to Embodiment 1. [Figure 2] It is a flowchart showing the flow of the card information management method according to Embodiment 1. [Figure 3] It is a block diagram showing the overall configuration of the card information management system according to Embodiment 2. [Figure 4] It is a block diagram showing the configuration of the user terminal according to Embodiment 2. [Figure 5] It is a block diagram showing the configuration of the authentication terminal according to Embodiment 2. [Figure 6] It is a block diagram showing the configuration of the authentication device according to Embodiment 2. [Figure 7] It is a flowchart showing the flow of the face information registration process by the authentication device according to Embodiment 2. [Figure 8] It is a block diagram showing the configuration of the card information management device according to Embodiment 2. [Figure 9] It is a sequence diagram showing the flow of the card issuance process according to Embodiment 2. [Figure 10] It is a flowchart showing the flow of the face authentication process by the authentication device according to Embodiment 2. [Figure 11] It is a flowchart showing the flow of the issuance probability determination process according to Embodiment 2. [Figure 12] It is a diagram showing an example of the display of card information according to Embodiment 2. [Figure 13] It is a diagram showing an example of the display of a plurality of card information according to Embodiment 2. [Figure 14] It is a diagram showing an example of other card information according to Embodiment 2. [Figure 15] This figure shows an example of an airport sightseeing plan according to this second embodiment. [Figure 16] This figure shows an example of how local card information is displayed according to this second embodiment. [Figure 17] This figure shows an example of other local card information according to this second embodiment. [Figure 18] This is a sequence diagram showing the flow of the card transfer process according to this second embodiment. [Figure 19] This is a sequence diagram showing the flow of the card exchange process according to this second embodiment. [Figure 20] This is a sequence diagram showing the flow of the card usage process according to this second embodiment. [Figure 21] This is a block diagram showing the overall configuration of the card information management system according to this third embodiment. [Figure 22] This is a sequence diagram showing the flow of the physical card issuance process according to this third embodiment. [Modes for carrying out the invention]

[0012] Embodiments of the present disclosure will be described in detail below with reference to the drawings. In each drawing, the same or corresponding elements are denoted by the same reference numerals, and redundant explanations will be omitted where necessary for clarity.

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

[0014] The card information management device 1 comprises a detection unit 11, an issuance unit 12, and a registration unit 13. The detection unit 11 detects user actions related to the use of a predetermined service. Here, user actions related to the use of a predetermined service may, for example, be the launch of an application for using the service on a user terminal (not shown) operated by the user. Alternatively, the action 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 action may be the user successfully authenticating themselves via an authentication terminal (not shown) installed at a specific location. Alternatively, the action may be the establishment of a connection between an authentication terminal installed at a specific location and a user terminal via short-range wireless communication. For example, the action may be the authentication terminal detecting that a user possessing a user terminal has passed through a specific location. Alternatively, the action may be the establishment of a connection between a staff terminal possessed by a staff member of a service provider company and a user terminal via short-range wireless communication. In the above cases, the user terminal, wireless base station, and authentication terminal are assumed to be connected to the card information management device 1. Furthermore, the user terminal, wireless base station, and authentication terminal shall notify the card information management device 1 of the detected action. The detection unit 11 shall then detect the user's action based on this notification.

[0015] The issuing unit 12 issues card information corresponding to a portion of multiple types of card information, each with different characteristics defined based on the service related to the detected action. In other words, the issuing unit 12 may issue one piece of card information, or it may issue two or more pieces of card information of the same or different types. Each piece of card information, even if of the same type, is assigned unique identification information each time it is issued. Here, the service related to the detected action may be, for example, a launched application or a service corresponding to its operation, or a service provided at a specific location where connection to a wireless base station has been established or user authentication via an authentication terminal has been successfully completed. Alternatively, the service related to the detected action may be, for example, a service provided by a staff member holding a staff terminal connected via short-range wireless communication. The registration unit 13 registers the issued card information as the user's owned card related to the detected action.

[0016] Figure 2 is a flowchart illustrating the flow of the card information management method according to this embodiment 1. First, the detection unit 11 detects user behavior related to the use of a predetermined service (S11). Next, the issuing unit 12 issues card information corresponding to a portion of a plurality of card information types, each with different characteristics defined, based on the service related to the detected behavior (S12). Subsequently, the registration unit 13 registers the issued card information as the card owned by the user related to the detected behavior (S13).

[0017] Thus, the card information management device 1 according to this embodiment issues arbitrary card information in response to actions taken by the user related to the use of a predetermined service. Therefore, it can stimulate the user's desire to collect card information. As a result, it can promote the use of the service by users who are the target of the service.

[0018] The card information management device 1 includes a processor, memory, and storage device (not shown in the diagram). 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 it. In this way, the processor realizes 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 implemented with dedicated hardware. Furthermore, some or all of the components of each device may be implemented by general-purpose or dedicated circuits, processors, etc., or combinations thereof. These may be composed of a single chip or multiple chips connected via a bus. Some or all of the components of each device may be implemented by a combination of the aforementioned circuits, etc., and programs. Additionally, a CPU (Central Processing Unit), GPU (Graphics Processing Unit), FPGA (Field-Programmable Gate Array), quantum processor (quantum computer control chip), etc., can be used as the processor.

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

[0021] <Embodiment 2> This second embodiment is a specific example of the first embodiment described above. Figure 3 is a block diagram showing the overall configuration of the card information management system 1000 according to this second embodiment. The card information management system 1000 is an information system for managing card information issued in accordance with the use of various facilities and equipment at airport 600, various procedures at airport 600, and the use of aircraft. Users U1, U2, and U3 are users of airport 600.

[0022] Airport 600 is an example of a facility where various services are provided to users by airlines, airport operators, retailers, etc. Airport 600 includes areas (locations) such as Area 601 to 603. Area 601 is equipped with a radio base station 300 that extends the radio communication range of Area 601. The radio base station 300 establishes radio communication connections with radio terminals (user terminals, etc.) within its range and relays radio communications. For example, when user U1, who possesses user terminal 100-1, moves near Area 601, a radio communication connection is established between the radio base station 300 and user terminal 100-1.

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

[0024] Area 603 is also the area where airport 600 and airline staff U4 are located. Staff U4 possesses staff terminal 100-4. Staff terminal 100-4 may establish a short-range wireless communication connection with user terminal 100-3 possessed by user U3, which is located within a predetermined range.

[0025] The card information management system 1000 comprises user terminals 100-1 to 100-3, staff terminal 100-4, authentication terminal 200, wireless base station 300, card information management device 400, and authentication device 500. Each of the user terminals 100-1 to 100-3, staff terminal 100-4, authentication terminal 200, wireless base station 300, card information management device 400, and authentication device 500 is connected to communicate via network N. Here, 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. Network N is not limited by the type of communication protocol. User terminal 100-1 may be connected to network N via wireless base station 300 if a wireless communication connection with wireless base station 300 is established. Furthermore, user terminals 100-2 and 100-3 may also be connected to network N via each wireless base station (not shown) if wireless communication connections are established with wireless base stations installed within area 602 or 603. In the following, unless there is a need to 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 explanation, "personal authentication information" refers to information used for authentication (personal authentication, personal identification processing, etc.) to verify identity, and is information used to uniquely identify (distinguish) a person. In this embodiment 2, personal authentication is defined as facial recognition, 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 that utilize captured images can be applied to biometric authentication and biometric information. For example, biometric information may include data (feature quantities) calculated from physical characteristics unique to an individual, such as fingerprints, voiceprints, veins, retina, iris of the pupil, and palm patterns. In addition, other personal authentication methods may be applied instead of biometric authentication, and biometric information may also be other personal authentication information. For example, personal authentication information may include, but is not limited to, a combination of ID and password, the contents of identification documents such as My Number or driver's license (identification number, etc., and password), electronic certificates, and code information. The code information may also be a two-dimensional code, such as a QR code (registered trademark).

[0027] User terminal 100 is an information terminal such as a mobile phone, smartphone, or tablet. User terminal 100 is assumed to have an application (software program) installed for using various services related to airport 600. User terminal 100 uses this application to perform user login processing, accept requests for use of various services, and display and store card information received from card information management device 400. In addition, user terminal 100 may send requests for transfer, exchange, or use of stored card information to card information management device 400 in response to user operations. At that time, user terminal 100 may also read the card information code displayed on other user terminals 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. Furthermore, the user terminal 100 may establish a short-range wireless communication connection with the authentication terminal 200 and the staff terminal 100-4.

[0029] Figure 4 is a block diagram showing the configuration of a user terminal 100 according to this 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 a camera that takes pictures according to the control of the control unit 160. The storage unit 120 is an example of a storage device such as flash memory. The storage unit 120 stores a program 121 and card information 122. The program 121 is a computer program that implements the processing including the application described above. 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. In addition, the card information 122 may also include characteristic information (card type, card content (name, rarity, image), etc.) which will be described later.

[0030] Memory 130 is a volatile storage device such as RAM (Random Access Memory) and is a storage area for temporarily holding information when the control unit 160 is operating. Communication unit 140 is a communication interface with network N. In particular, communication unit 140 performs wireless communication. For example, communication unit 140 establishes a connection with wireless base station 300 or other wireless communication base stations and performs communication. Communication unit 140 may also establish a short-range wireless communication connection with authentication terminal 200 or staff terminal 100-4 and perform communication. Communication unit 140 may also communicate with GPS (Global Positioning System) satellites to obtain location information. Input / Output unit 150 includes a display device (display unit) such as a screen and an input device. Input / Output unit 150 is, for example, a touch panel. Control unit 160 is a processor that controls the hardware of user terminal 100. Control unit 160 loads program 121 from storage unit 120 into memory 130 and executes it. As a result, the control unit 160 implements the functions of the wireless processing unit 161, the card processing unit 162, and the 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 radio waves from a 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 radio waves from the wireless base station 300 or the like may be, for example, compatible with Wi-Fi (registered trademark). The wireless processing unit 161 may also establish a short-range wireless communication connection with the authentication terminal 200 or staff terminal 100-4 and perform data communication with the authentication terminal 200 or staff terminal 100-4 with which the connection has been established. Here, the short-range wireless communication may be, for example, compatible with the Bluetooth (registered trademark) standard.

[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. Depending on user operations, the card processing unit 162 may send a transfer request or exchange request for stored card information to the card information management device 400. For example, the card processing unit 162 may read the code information of the card information displayed on the screen of another user terminal via the camera 110 and analyze the code information to identify the card information to be transferred to or exchanged with itself. Alternatively, the card processing unit 162 may exchange (send and 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. The card processing unit 162 may then send a transfer request or an exchange request for card information it owns (stores) to the card information management device 400 regarding the identified card information. Furthermore, the card processing unit 162 may send a usage request to the card information management device 400 based on the card information and usage details specified by the user. Usage includes, for example, exchanging card information for electronic value information such as points. However, usage is not limited to these.

[0033] The display control unit 163 displays the received card information on the input / output unit 150. The display control unit 163 also reads the card information 122 from the storage unit 120 and displays it on the input / output unit 150, according to user specifications.

[0034] The authentication terminal 200 is an information terminal that authenticates users when they use the service. The authentication terminal 200 identifies the user through biometric authentication or other personal authentication methods described above, and then provides a service corresponding to that user. For example, the authentication terminal 200 takes a picture of user U2's face and performs facial authentication on the facial image via the card information management device 400 to the authentication device 500. If facial authentication is successful, the authentication terminal 200 provides the user U2 with a predetermined service. The authentication terminal 200 is, for example, a procedure terminal at an airport 600, a terminal at the entrance of a lounge, a payment terminal at a shop, digital signage, etc., but is not limited to these. Procedures at the airport 600 include, for example, check-in (boarding procedures), baggage drop-off, security screening, immigration control, and passenger verification for aircraft. In the case of passenger verification, for example, the authentication terminal 200 may be a terminal installed at the boarding gate.

[0035] Figure 5 is a block diagram showing the configuration of the authentication terminal 200 according to this 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 pictures in accordance with 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 processing including authentication request processing for initiating the provision of a service. For example, the program 221 includes a client application corresponding to the card information management device 400.

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

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

[0038] The authentication request unit 262 extracts the face region of the person detected from the image captured by the camera 210 as a face image, and sends an authentication request including the face image, terminal location information, and time information to the card information management device 400. Note that the authentication request does not necessarily have to include time information. Alternatively, the authentication request unit 262 may send a face authentication request including the face image to the authentication device 500 and receive a face authentication result from the authentication device 500. If the face authentication result indicates success, the authentication request unit 262 may extract the user ID included in the face authentication result and send information including the user ID, terminal location information, and time information to the card information management device 400.

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

[0040] The processing control unit 263 controls processing specific to each authentication terminal. For example, if authentication terminal 200 is a check-in terminal, the processing control unit 263 performs the prescribed check-in processing upon successful authentication of the user. At this time, the processing control unit 263 may communicate with the airport 600 or the information systems of each airline as needed. If authentication terminal 200 is a lounge entrance terminal, the processing control unit 263 controls the gate device at the entrance of the lounge to unlock if the user has successfully authenticated themselves and meets the conditions for using the lounge. If authentication terminal 200 is a store terminal, the processing control unit 263 performs the settlement and payment processing for the purchased goods.

[0041] Returning to Figure 3, we continue the explanation. The authentication device 500 is an information processing device that manages user facial feature information and performs facial authentication. In response to a facial authentication request received from an external source, 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 requester.

[0042] Figure 6 is a block diagram showing the configuration of the authentication device 500 according to this second embodiment. The authentication device 500 comprises 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 user IDs 511 and face feature information 512 associated with those user IDs. Face feature information 512 is a set of feature points extracted from a face image. The authentication device 500 may delete face feature information 512 from the face feature DB 510 in response to a request from a user or the like corresponding to the face feature information 512. Alternatively, the authentication device 500 may delete face feature information 512 after a certain period of time has elapsed since registration.

[0043] The face detection unit 520 detects the face region included in the registration image for registering face information and outputs it to the feature point extraction unit 530. The feature point extraction unit 530 extracts feature points from the face region 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 the face image received from the card information management device 400, etc., and outputs 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 the facial feature information 512 extracted from the registered image and registers it 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 face 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 matched facial feature information 512. The authentication unit 550 returns the result of the facial authentication to the requester, indicating whether or not the facial feature information matches. Whether or not the facial feature information matches corresponds to the success or failure of authentication. Note that "match" means that the degree of matching is above a threshold. In addition, if facial authentication is successful, the facial authentication result will include the identified user ID.

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

[0046] Returning to Figure 3, we continue the explanation. The card information management device 400 is an information processing device for dynamically determining the issuance probability according to predetermined conditions for users who have performed actions related to the use of a predetermined service, and for managing the issued card information according to the issuance probability. The card information management device 400 also performs card issuance processing, card transfer processing, card exchange processing, and card usage processing. The card information management device 400 is an example of the card information management device 1 described above. The card information management device 400 may be redundantly implemented on multiple servers, and each functional block may be implemented on multiple computers.

[0047] Figure 8 is a block diagram showing the configuration of the card information management device 400 according to this second embodiment. The card information management device 400 comprises 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 flash memory. The storage unit 410 stores a program 411, card definition information 412, user information 413, card information history 414, and card usage conditions 415. The program 411 is a computer program that implements processes including card issuance processing, card transfer processing, card exchange processing, and card usage processing according to this second embodiment.

[0048] Card definition information 412 is information that defines the characteristics of each type of card information. Card definition information 412 is information that associates card definition ID 4121, characteristic information 4122, and standard issuance probability 4123. Card definition ID 4121 is identification information of the type of card information. Characteristic information 4122 is information that indicates the characteristics corresponding to the type of card information. Characteristic information 4122 includes card type 41221, card content 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 includes the name of the card information, a description, a rarity level indicating its scarcity, an image, etc. Rarity may be a numerical value or a name indicating a level. Rarity may also be text information such as Normal, Rare, Super Rare, Hyper Rare, etc., or a level value. Furthermore, rarity may be changed if various conditions are met. In that case, the rarity included in card content 41222 should be set to the standard value.

[0050] Issuance condition 41223 is a combination (correspondence) of detected user behavior and the increase / decrease value of the issuance probability. Detected behavior includes the content of the behavior, the location where the behavior was detected, the method of detection, and the services used in conjunction with the behavior (services that motivated the user's behavior). Content of the behavior includes, but is not limited to, launching applications to use various services, the user's movement to a specific location (area), close-range interaction with specific staff, and identity authentication for procedures. Locations where behavior is detected include, but are not limited to, specific locations within airport 600 (various procedure locations), on an aircraft, and specific airports. Methods of detection include, for example, notifications of launching a specific application, notifications of establishing communication with a wireless base station at a specific location, notifications of successful identity authentication from an authentication terminal, and determination of successful authentication in response to an authentication request from an authentication terminal. Alternatively, methods of detection include, but are not limited to, notifications of establishing a short-range wireless connection between an authentication terminal or staff terminal and the user terminal. Services used in conjunction with the behavior include, but are not limited to, check-in (boarding procedures), lounge entry, and payment. The increase or decrease in the issuance probability is the value that is added or subtracted from the baseline issuance probability when a corresponding detection action occurs. Therefore, issuance condition 41223 can also be called a probability increase condition. Accordingly, the probability increase condition includes at least one of the following: the detected action was performed at a specific location, or the service level provided to the user related to the detected action is at or above a predetermined level. Furthermore, the probability increase condition also includes successful authentication of the user via an authentication terminal installed at a specific location.

[0051] Usage details 41224 include conversion (exchange) for points and other electronic value information, conversion (exchange) for benefit information such as usage fees, discount rates, and discount amounts for goods or services, and improvement of service levels (such as airline seat upgrades). Here, electronic value information refers to electronic data that represents economic value. Points are an example of electronic value information that has pseudo-monetary value that can be exchanged for goods or services. In addition to points, value information may also include electronic coupons, electronic money, crypto assets, or electronic tickets. In other words, it is electronic data that represents economic value and includes those that have monetary value equivalent to currency or those that have pseudo-monetary value. Therefore, users can use their card information by exchanging it for a number of points according to usage details 41224. Users can also exchange their card information for goods and services according to usage details 41224.

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

[0053] User information 413 is information that manages the user to whom card information has been issued. User information 413 is information that associates User ID 4131, personal information 4132, membership rank 4133, points held 4134, and owned card information 41351~4135n (where n is an integer of 1 or greater). User ID 4131 is user identification information. User ID 4131 is the information that corresponds to User ID 511 in the facial information DB 510 mentioned above. User ID 4131 is an example of personal authentication information. User ID 4131 may also be the login ID for the application mentioned above.

[0054] Personal information 4132 includes information such as the user's name, address, telephone number, payment information, and notification recipients. Notification recipients include the user's device identification information (device ID), user login ID, email address, and SNS (Social Networking Service) account. Personal information 4132 may also include information about the user's booked airline tickets (departure and arrival dates and times, flight number, seat, etc.). Membership rank 4133 is information corresponding to the level of service that a member can receive (e.g., aircraft seat grade). Points held 4134 are an example of reward information or electronic value information that can be used to pay for services provided.

[0055] The owned card information 41351, etc., is the card information issued to the user. For example, owned card information 41351 is information that associates card ID 41361, card definition ID 41362, and status 41363. Card ID 41361 is the identification information of the issued card information. Card definition ID 41362 is the information corresponding to the card definition ID 4121 mentioned above. Status 41363 is information that indicates the status of the card information. For example, status 41363 can be owned, used, transferred, etc. "Owned" indicates the state in which the card information (card ID) has been issued and stored on the user terminal 100. "Used" indicates the state in which the card information has been used according to the usage details described above, that is, the user no longer owns it and it cannot be used in the future. "Transferred" indicates the state in which the card information has become "owned" by another user. Note that status 41363 may not distinguish between used and transferred and may be expressed as "not owned," etc. Alternatively, the owned card information 41351, etc., may be deleted or a deletion flag may be set when the user transfers, exchanges, or uses the card information.

[0056] Card information history 414 is information that manages the history of processing (issuance or ownership, transfer, exchange, or use) of card information. Card information history 414 is information that associates date and time 4141, processing type 4142, user ID 4143, and card IDs 41441~4144m (where m is an integer of 1 or more). Date and time 4141 is the date and time when the card information was processed. Processing type 4142 indicates the type of processing, such as issuance or ownership, transfer, exchange, or use of card information. User ID 4143 indicates the identification information of the user corresponding to the processing of the card information. For example, if processing type 4142 is issuance or ownership, then user ID 4143 is the user corresponding to the card information This is the user ID of the user who became the owner (the user ID of the card information stored on user terminal 100). Also, if the processing type 4142 is transfer or exchange, user ID 4143 is the user ID of the recipient of the transfer or exchange of the card information. If the processing type 4142 is use, user ID 4143 is the user ID of the user who used the card information. Card ID 41441, etc., is the set (combination) of card information processed in the combination of date and time 4141 and processing type 4142. For example, if multiple cards are used together, card ID 41441, etc., will be the combination of those cards. Note that the card information history 414 may be a history for each card ID.

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

[0058] Card usage conditions 415 define the conditions for using card information. Card usage conditions 415 include exchange definitions 4151 and combination definitions 4152. Exchange definitions 4151 define the exchange destination, card type, and value information to be exchanged when exchanging card information for electronic value information. Alternatively, exchange definitions 4151 may define rarity instead of card type. Alternatively, exchange definitions 4151 may define rarity together with card type, because cards of the same type may have different rarities. The exchange destination is, for example, the type of electronic value information or financial institution mentioned above. For example, when exchanging card information for points 4134 held in user information 413, the exchange destination is the organization that manages those points. The value information to be exchanged is the value of the value information that serves as the standard when exchanging card information of the corresponding card type (for example, the number of points). Combination definitions 4152 define the combination of card types and usage details when using multiple card information together. The combination definition 4152 may further include information about benefits granted by use (such as the number of points, the services that become available, and service level upgrades).

[0059] Memory 420 is a volatile memory device such as RAM, and is a storage area for temporarily holding information when the control unit 440 is operating. Communication unit 430 is a communication interface with network N.

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

[0061] The registration unit 441 registers and updates user information 413 and card information history 414. For example, when the registration unit 441 receives a user registration request from a user terminal 100 or the like that includes a new user's face image, it sends a face information registration request to the authentication device 500 for the face image included in the user registration request and obtains a user ID as a result of the registration. The registration unit 441 then registers the obtained user ID 4131 and the personal information 4132 included in the user registration request in the user information 413.

[0062] Furthermore, the registration unit 441 is an example of the registration unit 13 described above. When new card information (card ID) is issued by the issuance unit 445, the registration unit 441 associates the owned card information 41351, including the issued card ID 41361, etc., with the user ID 4131 that successfully obtained facial recognition and registers it in the user information 413. At the same time, the registration unit 441 registers the issuance history of the issued card ID in the card information history 414.

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

[0064] Furthermore, when the registration unit 441 receives an exchange request for the first owned card of the first user and the second owned card of the second user, it processes it 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. The registration unit 441 also registers the usage details determined in response to the usage request, associating them with the user of the owned card, and updates the owned card for that user to be used. In addition, if a combination of multiple owned cards registered as associated with a user satisfies the benefit conditions, the registration unit 441 may also register predetermined benefit information as associated with the user.

[0065] The authentication control unit 442 controls facial recognition, which is an example of biometric authentication, as a method of authentication for the user. However, the authentication control unit 442 may also control other biometric authentication methods or other methods of authentication for the user. The authentication control unit 442 controls facial recognition for the facial image included in the authentication request. In other words, the authentication control unit 442 controls authentication using registration and authentication information for the user. Specifically, the authentication control unit 442 sends a facial recognition request including a facial image to the authentication device 500 and receives the facial recognition result from the authentication device 500. The authentication control unit 442 may also detect the user's facial region from the facial image and include an image of the facial region in the facial recognition request. Alternatively, the authentication control unit 442 may extract facial feature information from the facial region and include the facial feature information in the facial recognition request.

[0066] The identification unit 443 determines whether or not facial recognition was successful based on the facial recognition result from the authentication control unit 442. If it determines that facial recognition was successful, the identification unit 443 identifies user information 413 corresponding to the user ID included in the facial recognition result. The identification unit 443 also identifies the current location of the authenticated user from the terminal location information included in the authentication request. In other words, the identification unit 443 identifies the location where the user's actions were detected. In addition to the authentication request, the identification unit 443 may also identify the user's actions and related services through notifications of the launch of a specific application, the establishment of communication with a wireless base station 300 at a specific location, or the successful authentication of the user from the authentication terminal 200. Furthermore, the identification unit 443 may also identify the user's actions, related services, and staff corresponding to those services through notifications of the establishment of short-range wireless communication connections between the authentication terminal 200 or staff terminal 100-4 and the user terminal 100. Furthermore, the identification unit 443 may determine the user's current location not only through authentication requests, but also through notifications of the launch of a specific application, the establishment of communication with a wireless base station 300 at a specific location, or the successful authentication of the user from the authentication terminal 200. Alternatively, the identification unit 443 may determine the user's current location not only through authentication requests, but also through notifications of the establishment of short-range wireless communication connections between the authentication terminal 200 or staff terminal 100-4 and the user terminal 100. Alternatively, the identification unit 443 may determine the user's current location not only through authentication requests, but also through detected user actions, services related to those actions, staff corresponding to those services, etc.

[0067] Therefore, the authentication control unit 442 and the identification unit 443 can be considered examples of the detection unit 11 described above. Thus, the detection unit according to this embodiment 2 can be said to detect user behavior related to the use of a predetermined service when user authentication is successful via an authentication terminal installed at a specific location.

[0068] The decision unit 444 determines the issuance probability for each of several types of card information, each with different characteristics defined, based on the service related to the detected behavior. That is, the decision unit 444 determines the issuance probability for each card type in response to successful facial recognition or the detection of the user's behavior as described above. For example, the decision unit 444 obtains the standard issuance probability 4123 and issuance conditions 41223 from the card definition information 413 for a specific card type 41221. Then, the decision unit 444 determines the issuance probability based on the detected behavior, specific location, specified service, card type, standard issuance probability, and issuance conditions. Here, the issuance probability may be between 0% and 100%. Specifically, the decision unit 444 determines the issuance probability by increasing or decreasing the probability relative to the standard issuance probability, in accordance with the issuance conditions, based on the detected behavior, specific location, specified service, and card type. For example, if the detected behavior satisfies the probability increase condition (issuance condition 41223), the decision unit 444 determines a higher issuance probability for the specific card information compared to other card information based on its characteristics (card type and other conditions).

[0069] Furthermore, the decision unit 444 may determine the issuance probability based on user attributes in addition to detected behavior, specific locations, or specified services. For example, even for the same behavior (check-in), the issuance probability of the same type of card information may differ depending on whether the check-in is performed by an individual or a family. This allows the assigned card information to be changed depending on whether the check-in process is performed by an individual or a family. In addition, the decision unit 444 may determine the issuance probability based on the number and combination of cards owned by the user, in addition to detected behavior, specific locations, or specified services. For example, a user who owns a predetermined number of cards with relatively low rarity may be more likely to be issued cards with relatively high rarity. Alternatively, the decision unit 444 may determine the services to be offered based on the number and combination of cards owned by the user, in addition to detected behavior, specific locations, or specified services. For example, there may be services offered by collecting (acquiring) a predetermined number or more of cards, even if they have relatively low rarity. These measures can contribute to increasing the repeat rate for services.

[0070] Furthermore, the decision unit 444 may determine that specific card information can be issued with a rarity different from the standard rarity defined in the card definition information 412, depending on the detected behavior, specific location, or specified service. In other words, the decision unit 444 can change the rarity based on the type of airport (Haneda, Osaka, etc.), location within the airport, detected behavior, detected service, etc. Also, for example, the decision unit 444 may determine that the issuance probability and rarity are low for general procedures at each authentication terminal 200 up to boarding, and high for interactions with specific staff or purchases at shops or lounges, etc. Here, general boarding includes, but is not limited to, check-in, baggage drop-off, immigration control, boarding gate, etc. Also, for example, the decision unit 444 may determine that the issuance probability and rarity are higher for procedures such as check-in that correspond to facial recognition via the authentication terminal 200 compared to procedures using paper tickets. This can contribute to increasing the registration of facial information for facial recognition and the number of users of facial recognition procedures. Furthermore, the determination unit 444 may determine the rarity level not only based on detected behavior, specific locations, or identified services, but also based on the usage status of the service (e.g., reservation status). For example, during off-peak seasons for the service (periods with few reservations), the determination unit 444 may set the rarity level higher than usual. This can contribute to attracting customers to the service.

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

[0072] The issuing unit 445 is an example of the issuing unit 12 described above. The issuing unit 445 issues one or more card information based on the determined issuance probability. Specifically, for each card type, the issuing unit 445 determines whether or not to issue card information based on the issuance probability, and issues a new card ID corresponding to the card type for which issuance has been determined to be necessary. Furthermore, if the rarity of the card information has been determined by the determination unit 444, the issuing unit 445 sets the determined rarity as the rarity of the card information to be issued. In other words, depending on the detected behavior, specific location, or specified service, card information of the same type but with different rarity levels may be issued. For example, in locations where user frequency is low (unpopular), increasing the rarity level at the time of issuance above the standard rarity level makes it easier to guide users to those locations.

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

[0074] Figure 9 is a sequence diagram showing the flow of the card issuance process according to this second embodiment. As a prerequisite, it is assumed that user U2, who possesses user terminal 100-2, is in front of authentication terminal 200 in area 602.

[0075] At this time, the authentication terminal 200 takes a picture of the user U2's face (S301). The authentication terminal 200 then sends an authentication request, including the captured face image and terminal location information, to the card information management device 400 via the network N (S302). In response, 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. The authentication control unit 442 then extracts the face image from the authentication request and sends a face authentication request, including the face image, to the authentication device 500 via the network N (S303). In response, the authentication device 500 performs face authentication processing (S304).

[0076] Figure 10 is a flowchart showing the flow of facial recognition processing by the authentication device according to this embodiment 2. First, the authentication device 500 receives a facial recognition request from the card information management device 400 via the network N (S211). The authentication device 500 may also receive facial recognition requests from user terminals 100 and authentication terminals 200, etc. Next, the authentication device 500 extracts facial feature information from the facial image included in the facial recognition request, in the same manner as steps S202 and S203 described above. Then, the authentication unit 550 of the authentication device 500 compares the facial feature information extracted from the facial image included in the facial recognition request with the facial feature information 512 in the facial information DB 510 (S212) and calculates the degree of match. Then, the authentication unit 550 determines whether the degree of match is above a threshold (S213). If the facial feature information matches, that is, if the degree of match of the facial feature information is above a threshold, the authentication unit 550 identifies the user ID 511 associated with the facial feature information 512 (S214). Then, the authentication unit 550 sends back the facial recognition result, including the identified user ID 511 and the fact that facial recognition was successful, to the card information management device 400 via the network N (S215). If the degree of match in step S213 is less than the threshold, the authentication unit 550 sends back the facial recognition result, including the fact that facial recognition failed, to the card information management device 400 via the network N (S216).

[0077] Returning to Figure 9, we continue the explanation. The authentication control unit 442 of the card information management device 400 receives the facial recognition result from the authentication device 500 via the network N (S305). Here, the facial recognition result includes a statement that facial recognition was successful and the user ID. The identification unit 443 determines whether or not facial recognition was successful based on the facial recognition result. If the facial recognition result indicates that facial recognition failed, the notification unit 446 sends a message to the authentication terminal 200 via the network N indicating that authentication failed.

[0078] Here, we will continue the explanation assuming that facial recognition was successful. The identification unit 443 then identifies user information, detected behavior, detection location, and service (S306). Specifically, the identification unit 443 identifies user information 413 corresponding to user ID 4131 included in the facial recognition result. The identification unit 443 may also identify the membership rank 4133 included in the identified user information 413. Furthermore, the identification unit 443 identifies the location where the user's 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 user U2 is staying (detection location), the service provided in area 602, and the behavior to use that service (detected behavior) from the location information of the authentication terminal 200. In this example, the detected behavior is the behavior of performing facial recognition in order to use the service provided in area 602.

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

[0080] Furthermore, if user U1 moves to the vicinity of area 601 in order to use a specific service, user terminal 100-1 establishes a connection with the wireless base station 300. At this time, either the wireless base station 300 or user terminal 100-1 may send a notification of connection establishment to the card information management device 400, including the base station ID of the wireless base station 300 and the terminal ID of user terminal 100-1. In response to this notification, the identification unit 443 detects that user U1 has moved to the vicinity of area 601 and that the service that user U1 intends to use is a service provided in area 601. The identification unit 443 also identifies area 601 where user U1 is staying from the base station ID included in the notification. The identification unit 443 can also identify the user ID by referring to user information 413 from the terminal ID included in the notification. Therefore, user authentication is possible even in the case of this notification. The wireless base station 300 may be installed inside an aircraft. In this case, the identification unit 443 can detect from the base station ID included in the notification that 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 short-range wireless connection. In this case, either the authentication terminal 200 or the user terminal 100-2 may send a notification of connection establishment, including the terminal location information of the authentication terminal 200 and the terminal ID of the user terminal 100-2, to the card information management device 400. In response to this notification, the identification unit 443 detects that user U2 has moved near the authentication terminal 200 and that the service that user U2 intends to use is a service provided by the authentication terminal 200. The identification unit 443 also identifies the area 602 where user U2 is staying from the terminal location information of the authentication terminal 200 included in the notification. Furthermore, the identification unit 443 can identify the user ID by referring to the user information 413 from the terminal ID included in the notification. Therefore, authentication is possible even in the case of this notification.

[0082] Alternatively, the staff terminal 100-4 and the user terminal 100-3 may establish a short-range wireless communication connection. In this case, either the staff terminal 100-4 or the user terminal 100-3 may send a notification of connection establishment, including the terminal IDs and location information of both the staff terminal 100-4 and the user terminal 100-3, to the card information management device 400. In response to this notification, the identification unit 443 detects that user U3 received customer service from staff U4 (action) and that the service used by user U3 (customer service) was provided by staff U4. The identification unit 443 also 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 by referring to the user information 413 from the terminal ID included in the notification. Therefore, user authentication is possible even in the case of this notification.

[0083] Returning to Figure 9, we continue the explanation. Then, the determination unit 444 performs the issuance probability determination process (S307). Figure 11 is a flowchart showing the flow of the issuance probability determination process according to this second embodiment. The issuance probability determination process determines the issuance probability for each of the multiple card definition information (card types) defined in the card definition information 412. Here, it is assumed that the card definition information 412 contains one or more card definition information, as described above.

[0084] First, the decision unit 444 selects an unselected card type from the card definition information 412 (S321). In other words, the decision unit 444 selects the first card type for which the issuance probability will be determined. Depending on the detection action, 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 that case, the decision unit 444 will select the card type for which the issuance probability will be determined according to the detection action, etc.

[0085] Next, the decision unit 444 obtains the standard issuance probability 4123 and issuance conditions 41223 associated with the selected card type 41221 (or card definition ID 4121) (S322). Then, the decision unit 444 determines the issuance probability based on the detected behavior, detected location, detected service, card type, standard issuance probability, and issuance conditions (S323). For example, if the detected behavior, detected location, detected service, etc. match the issuance conditions, the decision unit 444 determines the issuance probability by adding the increase / decrease value included in the issuance conditions to the standard issuance probability of the card type. On the other hand, if the detected behavior, detected location, detected service, etc. do not match the issuance conditions, the decision unit 444 determines the issuance probability by subtracting the increase / decrease value included in the issuance conditions to 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 decision unit 444 may determine the issuance probability of the card type to be 0. The decision unit 444 may also take the user's membership rank into consideration when determining the issuance probability.

[0086] Subsequently, the decision unit 444 determines whether or not there are any unselected card types (S324). If there are unselected card types (NO in S324), the process returns to step S321, and the decision unit 444 selects one of the unselected card types. In other words, the decision unit 444 selects the second and subsequent card types (S321), and in steps S322 and S323, determines the issuance probability for the selected card type. 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 Figure 9. Note that, in terms of implementation, the issuance probability determination process may also be performed by first making the determination in step S324, and then executing steps S321 to S323 if there are unselected card types (NO in S324). In other words, Figure 11 is merely one example of an algorithm for the issuance probability determination process.

[0087] Returning to Figure 9, we continue the explanation. The issuing unit 445 issues one or more 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 issued based on the issuance probability. The identification unit 443 may then identify the contact information (destination information of user terminal 100-2) of user U2 who succeeded in facial recognition from the personal information 4132 included in the user information 413 identified in step S306. The notification unit 446 then notifies user terminal 100-2 via network N of the card information, including the issued card ID, card type, and card contents (image, etc.) (S309).

[0088] Subsequently, 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 the owned card information 41351, including the issued card ID 41361, etc., with 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 as the authentication date and time or detection date and time, the processing type 4142 as issued or owned, the user ID 4143 as the user ID of user U2, and the card ID 41441 as the card ID issued in step S308. Then, the registration unit 441 associates the date and time 4141, the processing type 4142, the user ID 4143, and the card ID 41441 with the card information history 414. Furthermore, if more than one card is issued in step S308, the registration unit 441 registers each card in the user information 413 and the card information history 414.

[0089] Furthermore, after step S309, the user terminal 100-2 receives card information from the card information management device 400 via the network N and displays the card information on the screen (S312). The user terminal 100-2 then saves the received card information to the storage unit 120 (S313).

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

[0091] Figure 12 shows an example of card information display according to this second embodiment. Here, we show an example where card information 801 is issued after user U2 successfully checks in by performing facial recognition at the check-in terminal (authentication terminal 200). We show an example where the user terminal 100 displays card information 801 on the card information display screen 71. Card information 801 indicates that the rarity is normal.

[0092] Figure 13 shows an example of displaying multiple card information according to this second embodiment. Here, we show an example in which two card information items 802 and 803 are issued as a result of user U3 making an inquiry to staff member U4 and receiving customer service. This shows an example in which user terminal 100 displays card information items 802 and 803 on the card information display screen 72. Card information item 802 is the card corresponding to staff member U4 and indicates that its rarity is rare. Card information item 803 is issued because the issuance probability increased in response to customer service and indicates that its rarity is super rare.

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

[0094] Next, I will explain an example of a service that applies the card issuance process. First, one of the conditions for issuing card information is to set the user's detection location to various airports. Then, general passengers are allowed to board sightseeing flights conducted to maintain aircraft performance, and at each airport visited on these sightseeing flights, airport-specific local card information is issued and provided to the users, exclusively for those on sightseeing flights. The sightseeing flight service may also be provided by charter flights. Furthermore, users may disembark at each airport and use the services available at the airports. This increases the opportunities for users to interact with various services provided by airports and airlines.

[0095] Figure 15 shows an example of an airport sightseeing plan according to this second embodiment. The airport sightseeing plan connects the airports from which the sightseeing flight service departs, lands, or transits. For example, after boarding the aircraft, the user terminal of a passenger using the sightseeing flight service establishes a wireless communication connection with the onboard wireless communication base station. In other words, the onboard wireless communication base station can obtain the terminal ID or user ID from the passenger's user terminal. The sightseeing flight service aircraft then takes off from Haneda Airport and lands at Sendai Airport. At that time, the onboard wireless communication base station establishes a wireless communication connection with the wireless communication base station at Sendai Airport. The onboard wireless communication base station then 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 connected user terminal, and the fact that it is a sightseeing flight service. In response, the card information management device 400 determines the probability of issuing local card information corresponding to Sendai Airport to 100%, issues the local card information to the passenger, and notifies the user terminal of the local card information. Furthermore, the probability of issuing local souvenir card information is not limited to 100%, and may be higher than usual. Also, from the perspective of infectious disease control, the sightseeing flight service may not land at any of the intermediate airports, but instead pass over the vicinity of each airport and return to the airport from which the aircraft took off. In that case, when passing over the vicinity of each airport, the onboard radio communication base station will establish a radio communication connection with each airport. The onboard radio communication base station will then notify the card information management device 400 (via the airport's radio 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 it is a sightseeing flight service. As a result, local souvenir card information corresponding to the airport passed over will be issued to the passenger, as described above.

[0096] Figure 16 shows an example of displaying local card information according to this second embodiment. Here, an example is shown in which the user terminal 100 displays card information 807 on the card information display screen 73. Card information 807 is an example of local card information for the Tohoku area, to which Sendai Airport belongs, and indicates that it is extremely rare.

[0097] Subsequently, the sightseeing flight service aircraft takes off from Sendai Airport and then takes off and lands at the following airports: 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. 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] Figure 17 shows examples of other local card information according to this 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 it is rare. Card information 809 is an example of local card information for the Kyushu area, to which Fukuoka Airport belongs, and indicates that it is rare. Card information 810 is an example of local card information for the Kansai area, to which Kansai International Airport (KIX) belongs, and indicates that it is extremely 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 it is rare.

[0099] Furthermore, the card information management device 400 may grant additional reward information if a combination of multiple cards registered to a particular user meets predetermined conditions. For example, points may be awarded if the user possesses local card information for all airports from which the sightseeing flight service took off and landed. In other words, special points may be awarded for completing a specific combination of card information. This will stimulate the user's motivation to collect various types of card information and further promote the use of the service. In addition, rare card information may be issued as reward information.

[0100] Next, we will explain the card transfer process. As a prerequisite, we assume that card X is already registered as owned by user U1, and that the card information is also stored in user terminal 100-1. In this case, we will explain an example where user U1 attempts to transfer (transfer) card X to user U2.

[0101] Figure 18 is a sequence diagram showing the flow of the card transfer process according to this second embodiment. First, the user terminal 100-1 displays the card information of card X specified by user U1 on the screen (S331). Here, the card information is assumed to include the code information of card X, or to contain 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, user terminal 100-2 obtains the code information of card X from user terminal 100-1 (S332). For example, if the code information of card X is displayed, user terminal 100-2 uses the camera to capture the code information of card X displayed on user terminal 100-1 at the operation of user U2. Then, user terminal 100-2 identifies the area of ​​the code information from the captured image and analyzes the code information to identify the information of card X (card ID, etc.) (S333). If the code information of card X is not displayed, user terminals 100-1 and 100-2 may establish a short-range wireless communication connection and transfer the code information of card X from user terminal 100-1 to user terminal 100-2. In this way, user terminal 100-2 may obtain the code information of card X from user terminal 100-1.

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

[0104] In response, the card information management device 400 receives a transfer request from the user terminal 100-2 via the network N. The card information management device 400 then identifies the user U1 who owns card X based on the information of 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 card X, from the user information 413.

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

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

[0107] In this way, the process of transferring one user's owned cards (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, we will explain the card exchange process. As a prerequisite, assume that card X is registered as owned by user U1, and that the card information is also stored in user terminal 100-1. Also, assume that card Y is registered as owned by user U2, and that the card information is also stored in user terminal 100-2. We will now explain an example where users U1 and U2 attempt to exchange card X and card Y.

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

[0110] For example, as described above, 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 user terminal 100-1 to user terminal 100-2, and the code information of card Y may be transferred from user terminal 100-2 to user terminal 100-1. In other words, the card information to be exchanged may be exchanged between the user terminals through direct communication. Alternatively, user terminal 100-2 may transmit the code information of card Y to user terminal 100-1 in response to receiving the code information of card X from user terminal 100-1.

[0111] Alternatively, if card code information is displayed, user terminal 100-2 may, at the operation of user U2, capture the code information of card X displayed on user terminal 100-1 using its camera. Similarly, user terminal 100-1 may, at the operation of user U1, capture the code information of card Y displayed on user terminal 100-2 using its camera.

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

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

[0114] The card information management device 400 then 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 to transfer card X from the current owner, user U1, to the exchange destination, user U2. At the same time, the card information management device 400 generates a second transfer request to transfer card Y from the current owner, user U2, to the exchange destination, user U1.

[0115] Subsequently, 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 user U1's card X to used and registers card X as a card owned by user U2. The card information management device 400 also processes this as a second transfer request (S349). That is, the card information management device 400 updates the status of user U2's card Y to used and registers card Y as a card owned by user U1.

[0116] Furthermore, 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 as the date and time the exchange request was received, the processing type 4142 as "exchange", the user ID 4143 as the user ID of the exchange destination user U2, and the card ID 41441 as the card ID of card X. The registration unit 441 then registers a record associating these in the card information history 414. Similarly, the registration unit 441 sets the date and time 4141 as the date and time the exchange request was received, the processing type 4142 as "exchange", the user ID 4143 as the user ID of the exchange destination user U1, and the card ID 41441 as the card ID of card Y. The registration unit 441 then registers a record associating these in the card information history 414.

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

[0118] In this way, the process of exchanging owned cards (card information) between users 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. Furthermore, by converting one exchange request into a combination of two transfer requests and applying the transfer request processing twice, the unique processing of exchange requests can be reduced, and implementation can be carried out efficiently.

[0119] Next, we will explain the card usage process. As a prerequisite, we assume that cards Z and W are already registered as owned by user U1, and that the card information is also stored in user terminal 100-1. In this case, we will explain an example in which user U1 uses the combination of cards Z and W for point exchange.

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

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

[0122] The card information management device 400 then determines the number of points to be exchanged based on the combination of cards Z and W (S355). Specifically, the determination unit 444 identifies a reference value for the number of points to be exchanged based on the exchange definition 4151 of the card usage conditions 415. The determination unit 444 also determines the increase in the number of points corresponding to the combination of cards Z and W based on the combination definition 4152 of the card usage conditions 415. The determination unit 444 then determines the number of points to be exchanged by adding the increase in the number of points to the identified reference value. For example, if the combination of cards is of low rarity, the number of points to be exchanged will be the reference value plus a larger increase. A multiple may be used instead of an increase.

[0123] Then, the card information management device 400 adds the determined number of points to the points held by user U1 4134 (S356). At the same time, the card information management device 400 updates the status of user U1's cards Z and W 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 as the date and time the usage request was received, the processing type 4142 as "used", the user ID 4143 as the user ID of user U1, the card ID 41441 as the card ID of card Z, and the card ID 41442 as the card ID of card W. The registration unit 441 then registers a record associating these in the card information history 414.

[0124] Furthermore, the card information management device 400 may then send a notification of completion of the usage process (point exchange) to the user terminal 100-1, which is the terminal that uses the card information. In response, the user terminal 100-1 deletes the card information 122 of cards Z and W from the storage unit 120.

[0125] In this way, the usage process (point exchange) of a user's owned cards (card information) 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.

[0126] Furthermore, in addition to the transfer request, exchange request, and usage request, it is desirable that the above-mentioned card transfer process, card exchange process, and card usage process also require the user's approval or passcode. This is to prevent the unauthorized transfer, exchange, and use of card information. For example, in the above-mentioned card transfer process, user terminal 100-2 shall obtain the passcode from user terminal 100-1 of user U1, the source user, and include that passcode in the transfer request. Then, if the card information management device 400 includes the passcode of user U1, the source user, in the transfer request at S334 in Figure 18, it is advisable to proceed with the transfer process from S335 onwards. Similarly, in the card exchange process, user terminal 100-1 shall obtain the passcode from user terminal 100-2 of user U2, the exchange partner user, and include that passcode in the exchange request. Then, if the card information management device 400 includes the passcode of user U2, the exchange partner user, in the exchange request at S345 in Figure 19, it is advisable to proceed with the exchange process from S346 onwards. Furthermore, in the card usage process, user terminal 100-1 obtains a passcode from user U1, the point exchanger, and includes the passcode in the usage request. The card information management device 400 then performs the usage processing from S354 onwards if the usage request in S353 of Figure 20 includes the passcode of user U1, the point exchanger. Alternatively, in the card transfer or card exchange process, when the card information management device 400 receives a transfer or exchange request, it may send an approval request for the request to the other party's user terminal, and perform the card transfer or card exchange process if approval is received. In addition, in the card usage process, when the card information management device 400 receives a usage request, it may send an approval request for the request to the user terminal of the point exchanger, and perform the card usage process if approval is received.

[0127] In recent years, the use of public transportation by general passengers, such as families, has decreased due to the spread of infectious diseases. Therefore, measures to increase the number of users of a particular service are needed. However, simply issuing cards randomly, as in Patent Document 1, is insufficient as a measure to increase the number of users of the service. In this embodiment 2, users can obtain various types of card information as a result of actions related to the use of the service. Therefore, users may use airplanes for motivations such as collecting cards or exchanging them for miles. This can revitalize the aviation industry, including airlines. In particular, in this embodiment 2, the probability of issuing card information is determined based on the service identified from the detected user's actions. In this case, unlike random issuance probabilities, the probability of issuing card information fluctuates to some extent depending on the user's actions. On the other hand, even at the same location or with the same actions, the issued card information may differ. Therefore, this can further stimulate the user's motivation to collect card information. Furthermore, the card information issuance service may also be provided to employees of partner companies of airlines and their families. In addition, since points and services are added for cards with higher rarity, users will seek out rarer cards, which can contribute to further revitalization of the service.

[0128] In this second embodiment, the services provided to the user are exemplified by services provided by transportation companies, etc. Examples of transportation include, but are not limited to, aircraft, trains, buses, taxis, and ships. Therefore, the detection unit in this second embodiment can be said to detect user behavior related to the use of services provided by transportation. However, the services provided to the user are not limited to these.

[0129] <Embodiment 3> This third embodiment is a modification of the second embodiment described above. This third embodiment issues a physical card as card information. Here, a physical card refers to a card that is not an electronic medium, but rather a card made of paper or plastic with card information printed or displayed on it, or a card in which an IC chip on which card information is electronically recorded is coated with plastic.

[0130] Physical cards have a significant effect in increasing users' desire to collect them and promoting service usage. On the other hand, measures must be taken to prevent the resale of physical cards and fraudulent use by persons other than the cardholder. Therefore, the card information management device 400 needs to appropriately manage the physical cards issued to and owned by each user within the user information 413.

[0131] Figure 21 is a block diagram showing the overall configuration of the card information management system 1000a according to this third embodiment. Compared to Figure 3 described above, the card information management system 1000a has an additional card issuing terminal 301 installed in area 602, and the card information management device 400 has been replaced by the card information management device 400a. The physical card 820 is a card issued by the card issuing terminal 301 in response to an issuance instruction from the card information management device 400a. Note that area 603 is not shown in Figure 21. The other configurations are the same as in Figure 3 described above, so in the following description, redundant explanations will be omitted as appropriate.

[0132] The card issuing terminal 301 is an information terminal connected to the network N. Alternatively, the card issuing terminal 301 may be connected to the authentication terminal 200. The card issuing terminal 301 issues a physical card 820 in response to an issuance instruction from the card information management device 400a. The card issuing terminal 301 may print the card information 821 included in the issuance instruction onto a paper or plastic card to create the physical card 820. Alternatively, the card issuing terminal 301 may record the card information 821 included in the issuance instruction onto a card that already has an IC chip embedded in it to create the physical card 820. The 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. User terminal 100-2 may, in response to user U2's operation, 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. Alternatively, user terminal 100-2 may send a registration request to the card information management device 400a, including the card information 821 printed or recorded on the physical card 820 and user U2's user ID, etc. In other words, user terminal 100-2 may send the registration request when the card information 821 recorded on the physical card 820 issued by the card issuing terminal 301 in response to an issuance instruction is read by user U2's user terminal 100-2.

[0134] The issuing unit 445 of the card information management device 400a transmits an issuance instruction for issued card information to the card issuing terminal 301 installed at the location where the detected action occurred. The issuance instruction may also include an instruction to record the issued card information in a readable format as the physical card 720 described above.

[0135] The registration unit 441 of the card information management device 400a registers the issued card information as a card owned by the user in response to the registration request described above.

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

[0137] In response, the card issuing 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 issuing terminal 301 issues a physical card P on which the card information 821 is recorded on an IC chip (S402).

[0138] Then, in response to user U2's operation, user terminal 100-2 reads code information from the physical card P using a camera and 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 the storage unit 120 (S404). User terminal 100-2 also transmits a registration request, including the read card information 821 (card P) and user U2's user ID, etc., to the card information management device 400a via the network N (S405).

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

[0140] In this way, in this embodiment 3 as well, the card information of a physical card issued to a user can be appropriately registered and managed. In particular, the card information of the physical card actually possessed by the user, the card information in the user terminal, and the information of owned cards managed by the card information management device 400a can be appropriately synchronized.

[0141] Therefore, even if the card transfer process is not performed properly and another user attempts to use a physical card other than the one they own, the card information management device 400a can prevent its use. For example, suppose user U1 has illegally obtained a physical card P and read the code information of that card using user terminal 100-1. At this time, user terminal 100-1 analyzes the read code information to obtain card information and, after steps S351 and S352 in Figure 20 described above, sends a request to use 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 of card P included in the received 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 request is different from the identified user U2. Accordingly, the card information management device 400a replies to user terminal 100-1 via network N that the request is unavailable and does not perform the usage process. This also applies to transfer requests and exchange requests. Therefore, even with physical cards, unauthorized use, transfer, and exchange can be deterred. Furthermore, as with Embodiment 2 described above, it is desirable that the card transfer process, card exchange process, and card usage process require separate authorization from the user or a passcode, in addition to the transfer request, exchange request, and usage request.

[0142] <Other Embodiments> In the embodiments 2 and 3 described above, the card information management device 400 and the authentication device 500 were 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 that 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 shown in Figure 6.

[0143] In the examples described above, the program includes a set of instructions (or software code) that, when loaded into a computer, cause the computer to perform one or more of the functions described in the embodiments. The program may be stored on a non-temporary computer-readable medium or a physical storage medium. Examples, but not limited to, include random-access memory (RAM), read-only memory (ROM), flash memory, solid-state drive (SSD) or other memory technologies, CD-ROM, digital versatile disc (DVD), Blu-ray® disc or other optical disc storage, magnetic cassette, magnetic tape, magnetic disk storage or other magnetic storage devices. The program may be transmitted over a temporary computer-readable medium or a communication medium. Examples, but not limited to, include temporary computer-readable medium or a communication medium that includes electrically, optically, acoustically or otherwise propagating signals.

[0144] This disclosure is not limited to the embodiments described above, and may be modified as appropriate without departing from its spirit. Furthermore, this disclosure may be implemented by combining the respective embodiments as appropriate.

[0145] Some or all of the above embodiments may also be described as follows, but are not limited to the following: (Note 1) A detection means for detecting user behavior related to the use of a specified service, An issuing means for issuing card information corresponding to a portion of multiple types of card information with different characteristics defined based on the service related to the detected action, A registration means for registering the issued card information as the card owned by the user related to the detected action, A card information management device equipped with the following features. (Note 2) The system further includes a notification means for notifying the user's terminal of the issued card information. The card information management device described in Appendix 1. (Note 3) The detection means is The action is detected when the user's identity is successfully authenticated via an authentication terminal installed at a specific location. The card information management device described in Appendix 1 or 2. (Note 4) The system further comprises a determination means for determining the issuance probability of each of the multiple types of card information based on the services related to the detected behavior, The issuing means issues card information corresponding to a portion of the multiple types of card information based on the determined issuance probability. A card information management device as described in any one of the items 1 to 3 of the appendix. (Note 5) The aforementioned determination means is If the detected behavior satisfies the probability increase condition, the issuance probability of a specific card is determined to be higher than that of other card information based on the characteristics. The card information management device described in Appendix 4. (Note 6) The aforementioned probability increase condition is, The detected action was performed at a specific location, or the service level provided to the user related to the detected action is at least at a predetermined level. The card information management device described in Appendix 5. (Note 7) The aforementioned probability increase condition is, This includes successfully authenticating the user's identity via an authentication terminal installed at a specific location. The card information management device described in Appendix 5 or 6. (Note 8) The aforementioned determination means is In response to a request to use the aforementioned owned card, the usage details are determined based on the characteristics defined for that owned card. The registration means is, The determined usage details are registered in association with the user of the card, and the user's record of the card is updated to show as used. A card information management device as described in any one of the items 4 to 7 of the appendix. (Note 9) The aforementioned determination means is In response to the usage request specifying two or more owned cards, the usage details are determined based on the combination of characteristics defined for each specified owned card. The registration means is, The determined usage details are registered in association with the user of the owned card, and each of the designated owned cards for that user is updated to be marked as used. The card information management device described in Appendix 8. (Note 10) The aforementioned determination means is In response to the usage request for converting the owned card into electronic value information, the value information after conversion to electronic value information is determined as the usage content based on the characteristics defined for the owned card. The card information management device described in Appendix 8 or 9. (Note 11) The aforementioned determination means is In response to the usage request to change the service level using the owned card, the modified service level is determined as the usage content based on the characteristics defined for the owned card. A card information management device as described in any one of the items 8 to 10 of the appendix. (Note 12) The registration means is, When a transfer request is received to transfer the aforementioned owned card from the first user to the second user, the owned card is marked as used by the first user, and the owned card is registered in association with the second user. A card information management device as described in any one of the items 1 to 11 of the appendices. (Note 13) The registration means is, 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 described in Appendix 12. (Note 14) The registration means is, When a request is received to exchange a first-owned card of a first user for a second-owned card of a second user, the system processes this request as if it had received a first transfer request to transfer the first-owned card from the first user to the second user, and a second transfer request to transfer the second-owned card from the second user to the first user. The card information management device described in Appendix 12 or 13. (Note 15) The issuing means is, A command to issue a physical card containing the issued card information, which is readably recorded, is transmitted to a card issuing terminal installed at the location where the aforementioned action was performed. The registration means is, In response to a registration request transmitted when the card information recorded on the physical card issued by the card issuing terminal in accordance with the issuance instruction is read by the user's terminal, the issued card information is registered as a card owned by the user. A card information management device as described in any one of the items 1 through 14 of the appendix. (Note 16) The registration means is, If a combination of multiple owned cards registered in association with the aforementioned user meets the reward conditions, the specified reward information is registered in association with the aforementioned user. A card information management device as described in any one of the items 1 to 15 of the appendix. (Note 17) The detection means is Detecting user behavior related to the use of services via means of transportation. A card information management device as described in any one of the items 1 through 16 of the appendix. (Note 18) The aforementioned services relate to at least one of the following: the use of airport facilities or equipment, procedures at said airport, or the use of aircraft. The detection means is The system detects at least one of the following actions of the user: that an application for using the service is launched on the user terminal operated by the user; that the user terminal receives radio waves from a radio base station installed at a specific location in the airport and a connection is established; that the user successfully authenticates themselves via an authentication terminal installed at a specific location in the airport; that a connection is established between the authentication terminal and the user terminal via short-range wireless communication; that the authentication terminal detects that the user possessing the user terminal has passed through a specific location in the airport; or that a connection is established between a staff terminal possessed by airport or airline staff and the user terminal via short-range wireless communication. A card information management device as described in any one of the items 1 through 17 of the appendix. (Note 19) The aforementioned services include services related to at least one of the following procedures at the airport: check-in, baggage drop-off, security screening, immigration procedures, or passenger verification for the aircraft. A card information management device as described in any one of the items 1 through 18 of the appendix. (Note 20) A detection device that detects user behavior related to the use of a specified service, A card information management device is provided, The aforementioned card information management device is An issuing means for issuing card information corresponding to a portion of multiple types of card information with different characteristics defined based on the service related to the action detected by the detection device, A registration means for registering the issued card information as the card owned by the user related to the detected action, A card information management system equipped with this feature. (Note 21) The aforementioned card information management device is The system further includes a notification means for notifying the user's terminal of the issued card information. The card information management system described in Appendix 20. (Note 22) Computers Detect user behavior related to the use of a specified service, Based on the services related to the detected behavior, card information corresponding to a portion of multiple types of card information with different characteristics is issued. The issued card information is registered as the card owned by the user whose actions were detected. Card information management methods. (Note 23) A detection process that detects user behavior related to the use of a specified service, Based on the services related to the detected actions, an issuance process is performed to issue card information corresponding to a portion of multiple types of card information with different characteristics defined, A registration process to register the issued card information as the card owned by the user related to the detected action, A non-temporary, computer-readable medium containing a card information management program that causes a computer to execute a program.

[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 embodiments (and examples). Various modifications to the structure and details of the present invention can be made, which can be understood by those skilled in the art 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 User U3 User 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 Unit 161 Wireless Processing Unit 162 Card Processing Unit 163 Display Control Unit 200 Authentication Terminals 210 Cameras 220 Storage section 221 Programs 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 Programs 412 Card Definition Information 4121 Card Definition ID 4122 Characteristic Information 41221 Card Types 41222 Card Contents 41223 Issuance Conditions 41224 Usage details 4123 Standard Issuance Probability 413 User Information 4131 User ID 4132 Personal Information 4133 Member Rank 4134 points held 41351 Owned Card Information 41361 Card ID 41362 Card Definition ID 41363 Status 4135n Owned Card 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 Devices 510 Face Information Database 511 User ID 512 Facial feature information 520 Face detection unit 530 Feature point extraction unit 540 Registration Department 550 Certification Department 600 airports Area 601 Area 602 Area 603 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 cards 821 Card Information

Claims

1. An output means that outputs card information whose rarity is defined based on the user's location information and facility usage status, from among multiple types of card information with different characteristics defined. A registration means for registering the output card information as a card owned by the user, A card information management device equipped with the following features.

2. The output means outputs card information whose rarity is defined such that the rarity increases as the number of users of the facility decreases. The card information management device according to claim 1.

3. The output means outputs higher points as the number of users at the facility decreases, based on the location information of the service provider who provided the service to the user at the facility and the facility's usage status. The card information management device according to claim 1 or 2.

4. The system further includes a notification means for notifying the user's terminal of the outputted card information. The card information management device according to claim 1 or 2.

5. The system further includes detection means for detecting user behavior related to the use of services provided at the facility, as described above. The detection means is The action is detected when the user's identity is successfully authenticated via an authentication terminal installed at a specific location. The card information management device according to claim 1 or 2.

6. The system further comprises a determination means for determining the output probability of each of the multiple types of card information based on the aforementioned service, The aforementioned service is a service related to the detected behavior, The output means outputs card information corresponding to a portion of the multiple types of card information based on the determined output probability. The card information management device according to claim 5.

7. A detection device that detects user behavior related to the use of facilities where services are provided, A card information management device is provided, The aforementioned card information management device is An output means that outputs card information whose rarity is defined based on the user's location information and the facility usage status related to the actions detected by the detection device, from among multiple types of card information with different characteristics defined. A registration means for registering the output card information as a card owned by the user, A card information management system equipped with this feature.

8. The output means outputs card information whose rarity is defined such that the rarity increases as the number of users of the facility decreases. The card information management system according to claim 7.

9. Computers Among multiple types of card information with defined different characteristics, the system outputs card information whose rarity is defined based on the user's location information and facility usage status. The output card information is registered as a card owned by the user. Card information management methods.

10. An output process that outputs card information whose rarity is defined based on the user's location information and facility usage status, from among multiple types of card information with different characteristics defined. The above-mentioned output card information is registered as a card owned by the user, and A card information management program that causes a computer to execute a command.

Images