Information acquisition terminal, information acquisition method, and information acquisition program

Abstract

[Problem] To provide an information acquisition terminal capable of acquiring information from a device in proximity regardless of whether the device is an IC card or a user terminal. [Solution] An information acquisition terminal 1 for acquiring personal information from each of an IC card 2 and a user terminal 3. The information acquisition terminal 1 comprises: communication devices 46, 47; and a processor 41 that determines whether the device in proximity is an IC card or a user terminal, correspondingly performs communication, and acquires personal information from the device. The processor transmits a read request to the device in proximity from the communication devices requesting reading of specific area information stored in the IC card, and determines that the device is the IC card if reading of the specific area information is successful and determines that the device is the user terminal if reading of the specific area information fails.

Description

Information Acquisition Terminal, Information Acquisition Method, and Information Acquisition Program

[0001] The present invention relates to an information acquisition terminal, an information acquisition method, and an information acquisition program for acquiring personal information from each of an IC card and a user terminal.

[0002] User terminals such as smartphones are equipped with digital wallets that enable electronic payments such as ticket issuance and payments using credit cards, electronic money, etc.

[0003] However, there is a possibility that a user terminal equipped with a digital wallet may be misused by someone who is not the owner of the user terminal. Therefore, user identification information indicating the name of the digital wallet is stored in the user terminal, and based on this user identification information, it is determined whether the person attempting to receive the service (hereinafter, service user) is appropriate (see Patent Document 1).

[0004] Japanese Patent Publication No. 2022-508773

[0005] As described in Patent Document 1, a service provider acquires personal information of a service user at the time of service provision and determines whether to provide the service.

[0006] As a method of acquiring personal information of a service user, it is conceivable to have the service user present an identity card. When using an IC card (Integrated Circuit Card) such as a My Number card or a driver's license as the identity card, by having the service user bring the IC card close to a card reader, it becomes possible to acquire identity card data (hereinafter, identity card data) including personal information from the IC card.

[0007] On the other hand, international standards (ISO / IEC 18013, ISO / IEC 23220, etc.) are being developed for storing and using identity data such as driver's licenses and national IDs in digital wallets (also called digital identity wallets or digital ID wallets) installed on user terminals. These standards define the data format for identity data stored in digital wallets and protocols for accessing identity data in digital wallets from devices outside the user terminal. In such cases, it is desirable to determine whether the device presented by the service user is a user terminal or an IC card, perform the appropriate processing, and obtain the personal information stored in each.

[0008] Therefore, the main objective of the present invention is to provide an information acquisition terminal, an information acquisition method, and an information acquisition program that can acquire information from a nearby device, whether the nearby device is an IC card or a user terminal.

[0009] The information acquisition terminal of the present invention is an information acquisition terminal for acquiring personal information from an IC card storing personal information and a user terminal, respectively, and comprises a communication device for short-range communication with the IC card and the user terminal, and a processor that communicates with a nearby device via the communication device, determines whether it is the IC card or the user terminal, performs corresponding communication based on the determination result, and acquires the personal information from the device, wherein the processor transmits a read request from the communication device to the nearby device requesting the reading of specific area information stored in the IC card, determines that the device is the IC card when the reading of the specific area information is successful, and determines that the device is the user terminal when the reading of the specific area information fails.

[0010] Furthermore, the information acquisition program of the present invention is an information acquisition program for acquiring personal information from an IC card and a user terminal, respectively, which store personal information, and is executed by an information acquisition terminal comprising: a communication device for short-range communication with the IC card and the user terminal; and a processor that communicates with a nearby device via the communication device, determines whether it is the IC card or the user terminal, performs corresponding communication based on the determination result, and acquires the personal information from the device, wherein the processor transmits a read request from the communication device to the nearby device requesting the reading of specific area information stored in the IC card, and determines that the device is the IC card when it succeeds in acquiring the specific area information, and determines that the device is the user terminal when it fails to acquire the specific area information.

[0011] Furthermore, the present invention provides an information acquisition method for acquiring personal information from an IC card and a user terminal, respectively, which store personal information, and is executed by an information acquisition terminal comprising: a communication device for short-range communication with the IC card and the user terminal; and a processor that communicates with a nearby device via the communication device, determines whether it is the IC card or the user terminal, performs corresponding communication based on the determination result, and acquires the personal information from the device. The processor transmits a read request from the communication device to the nearby device requesting the reading of specific area information stored in the IC card, and determines that the device is the IC card when the reading of the specific area information is successful, and determines that the device is the user terminal when the reading of the specific area information fails.

[0012] According to the present invention, it is possible to provide an information acquisition terminal, an information acquisition method, and an information acquisition program that can acquire information from a nearby device, whether the nearby device is an IC card or a user terminal.

[0013] Overall configuration diagram of a system (check-in system) equipped with an information acquisition terminal according to the present invention Block diagram showing the configuration of an IC card, user terminal and information acquisition terminal Functional block diagram of the information acquisition terminal Flowchart of the information acquisition process according to the first embodiment Flowchart of the IC card reading process Flowchart of the digital wallet identity card data reading process Example of proximity request screen Example of consent / verification number acquisition screen Example of completion notification screen Example of failure notification screen Example of consent acquisition screen Sequence diagram showing the flow of the information acquisition process when an IC card is in close proximity Sequence diagram showing the flow of the information acquisition process when a user terminal is in close proximity Flowchart of the information acquisition process according to the second embodiment Flowchart of the information acquisition process My Number data acquisition process Flowchart of the mobile driver's license data acquisition process Flowchart of the My Number card reading process Flowchart of the driver's license reading process In the second embodiment, the user terminal 3 that stores My Number data is in close proximity to the information acquisition terminal 1 Sequence diagram of the information acquisition process in the second embodiment, the user terminal 3 that stores My Number data is not stored, and instead mobile Sequence diagram of information acquisition process when a user terminal 3 storing driver's license data is close to the information acquisition terminal 1 In the second embodiment, sequence diagram of information acquisition process when a My Number Card 2A is close to the information acquisition terminal 1 In the second embodiment, sequence diagram showing the first half of the information acquisition process when a driver's license 2B is close to the information acquisition terminal 1 In the second embodiment, sequence diagram showing the second half of the information acquisition process when a driver's license 2B is close to the information acquisition terminal 1 Flowchart of information acquisition process according to the third embodiment Sequence diagram of information acquisition process when a user terminal storing My Number data is close to the information acquisition terminal In the third embodiment, sequence diagram of information acquisition process when a user terminal storing My Number data is close to the information acquisition terminal In the fourth embodiment, sequence diagram of information acquisition process when a user terminal storing My Number data is close to the information acquisition terminalSequence diagram of the information acquisition process when a user terminal storing mobile driver's license data is in close proximity to an information acquisition terminal; flowchart showing a first modified example of the information acquisition process according to the second embodiment; flowchart showing a second modified example of the information acquisition process according to the second embodiment; flowchart showing a third modified example of the information acquisition process according to the second embodiment.

[0014] The first invention made to solve the aforementioned problems is an information acquisition terminal for acquiring personal information from an IC card storing personal information and a user terminal, respectively, comprising: a communication device for short-range communication with the IC card and the user terminal; and a processor that communicates with a nearby device via the communication device, determines whether it is the IC card or the user terminal, performs corresponding communication based on the determination result, and acquires the personal information from the device, wherein the processor transmits a read request from the communication device to the nearby device requesting to read specific area information stored in the IC card, determines that the device is the IC card when it succeeds in acquiring the specific area information, and determines that the device is the user terminal when it fails to acquire the specific area information.

[0015] According to this, the processor requests a nearby device to transmit specific area information stored in the IC card and determines whether the device is an IC card or a user terminal. As a result, the processor can perform the appropriate communication based on the determination result, thus providing an information acquisition terminal that can read personal information from both IC cards and user terminals that store information containing personal information.

[0016] Furthermore, the second invention is configured such that the communication device includes a first communication device for communicating with the IC card and a second communication device for communicating with the user terminal, and the processor is configured to acquire the personal information from the device via the first communication device when it succeeds in acquiring the specific area information, and to acquire the personal information from the device via the second communication device when it fails to acquire the specific area information.

[0017] According to this, the processor can communicate with the IC card and the user terminal, respectively, via the corresponding communication device.

[0018] Furthermore, the third invention is configured such that the specific area information is the remaining number of times until reading the IC card is prohibited.

[0019] According to this, specific area information can be appropriately set so that it is possible to determine whether the device is an IC card or a user terminal.

[0020] Furthermore, the fourth invention is configured such that the personal information includes at least one of the four basic pieces of information, which consist of the name, address, date of birth, and gender of the corresponding individual.

[0021] According to this, personal information can be set in a way that allows for easy comparison with service reservation information, application information, eligibility information, or conditions for receiving services (such as age and place of residence).

[0022] Furthermore, the fifth invention is an information acquisition program for acquiring personal information from an IC card and a user terminal, respectively, which stores personal information, and is executed by an information acquisition terminal comprising: a communication device for short-range communication with the IC card and the user terminal; and a processor that communicates with a nearby device via the communication device, determines whether it is the IC card or the user terminal, performs corresponding communication based on the determination result, and acquires the personal information from the device, wherein the processor transmits a read request from the communication device to the nearby device requesting the reading of specific area information stored in the IC card, and determines that the device is the IC card when the reading of the specific area information is successful, and determines that the device is the user terminal when the reading of the specific area information fails.

[0023] According to this, the processor requests a nearby device to transmit specific area information stored in the IC card and determines whether the device is an IC card or a user terminal. As a result, the processor can perform the appropriate communication based on the determination result, and thus it is possible to provide an information retrieval program that can read personal information from both the IC card and the user terminal, which store information including personal information.

[0024] Furthermore, the sixth invention is an information acquisition method for acquiring personal information from an IC card and a user terminal, respectively, which store personal information, and is executed by an information acquisition terminal comprising: a communication device for short-range communication with the IC card and the user terminal; and a processor that communicates with a nearby device via the communication device, determines whether it is the IC card or the user terminal, performs corresponding communication based on the determination result, and acquires the personal information from the device, wherein the processor transmits a read request from the communication device to the nearby device requesting the reading of specific area information stored in the IC card, and determines that the device is the IC card when the reading of the specific area information is successful, and determines that the device is the user terminal when the reading of the specific area information fails.

[0025] According to this, the processor requests a nearby device to transmit specific area information stored in the IC card and determines whether the device is an IC card or a user terminal. As a result, the processor can perform the appropriate communication based on the determination result, thus providing an information acquisition method that can read personal information from both IC cards and user terminals that store information containing personal information.

[0026] Hereinafter, embodiments of the present invention will be described with reference to the drawings.

[0027] <<First Embodiment>> The information acquisition terminal according to the present invention is operated by a service provider that intends to provide a service. Figure 1 shows an example of the configuration of a service system S to which the information acquisition terminal 1 according to the present invention is applied. The services referred to here may include the use of facilities such as hotels and offices, reservations for medical institutions and sports gyms, and identity verification when making payments using electronic money or credit cards (including age verification when purchasing age-restricted products).

[0028] To prove that the person seeking to use these services (service user) is a legitimate service user, they are required to present identification. Examples of commonly used identification include My Number Card 2A, driver's license 2B, residence card, and passport. These identification documents are provided as IC cards 2 that store the personal information of the cardholder.

[0029] On the other hand, in user terminals 3 (for example, smartphones 3A, tablet terminals 3B, smartwatches 3C, etc.) equipped with applications such as digital wallets, or after certain procedures have been completed, data included in the identification document (identification document data) is stored (remembered) in the storage or other location.

[0030] The information acquisition terminal 1 is a terminal of the service provider and may consist of a desktop PC, tablet terminal, dedicated terminal, etc. The information acquisition terminal 1 is used to acquire personal information used for determining whether a person intending to use the service is a suitable service user. The information acquisition terminal 1 may consist of, for example, a payment terminal 1A for electronic money or credit cards, a check-in terminal 1B for registering and confirming the intention to use a facility or service, or an ATM terminal 1C for withdrawing, depositing, checking balances, and making transfers using a bank card. With the permission of the service user, the information acquisition terminal 1 acquires necessary personal information from the IC card 2, which is the person's identification card, or from the user terminal 3, which stores the person's identification card data.

[0031] In the following, we will explain in detail an example where the information acquisition terminal 1 is installed in a service system S (hereinafter referred to as the check-in system 10) for check-in, which registers and confirms the user's intention to use a facility or service.

[0032] The check-in system 10 comprises a user terminal 3, an IC card 2, an information acquisition terminal 1, and a service provider server 11. The information acquisition terminal 1 and the service provider server 11 are each connected to a network 12 such as the Internet, and can communicate with each other via that network 12.

[0033] The IC card 2 (also called a physical card) constitutes an identification document that proves the identity of its owner (i.e., the cardholder), and is a card-shaped device with a built-in IC chip 13. The IC card 2 is configured to communicate with the information acquisition terminal 1, and the information acquisition terminal 1 functions as a reader / writer for the IC card 2.

[0034] The IC chip 13 stores the identity data of the holder of the IC card 2. The identity data includes various personal information, such as the four basic pieces of information consisting of name, address, date of birth, and gender.

[0035] In this embodiment, IC card 2 is a so-called My Number Card 2A, and IC chip 13 stores basic four pieces of information and an electronic certificate as identity data. The electronic certificate includes a signature electronic certificate and a user authentication electronic certificate. The signature electronic certificate is used to prove that an electronic document is genuine and was created by the cardholder, and is used for various online applications. The user authentication electronic certificate contains the cardholder's personal information and is used when logging into a portal site.

[0036] The IC chip 13 stores a verification number (PIN code, etc.). Based on a request from the information acquisition terminal 1, the IC chip 13 verifies the identity of the user by comparing the verification number transmitted from the information acquisition terminal 1 with the verification number it has previously stored. When identity verification is complete, the IC chip 13 extracts the personal information (basic four pieces of information) of the user from the identification data it stores and transmits it to the information acquisition terminal 1.

[0037] As illustrated in Figure 1, the user terminal 3 can be composed of various electronic devices such as a smartphone 3A, a tablet terminal 3B, or a smartwatch 3C.

[0038] In this embodiment, a digital wallet is installed on the user terminal 3. The digital wallet is an application for centrally managing credit cards, electronic money, boarding passes, tickets, point cards, etc. When an identification card provided as an IC card 2 is added to the digital wallet, the identification card can also be managed by the digital wallet, and the IC card 2 can be emulated by the user terminal 3. When an identification card is added to the digital wallet, it is confirmed that the name on the identification card and the owner of the user terminal 3 are the same person.

[0039] When an identification document is added to the digital wallet, the user terminal 3 stores the identification document data (basic four pieces of information and an electronic certificate) of the person whose name is on that document (i.e., the owner of user terminal 3). When it is confirmed that the person operating user terminal 3 is the owner of user terminal 3, user terminal 3 extracts the information required by information acquisition terminal 1 based on a request from information acquisition terminal 1 and transmits it to information acquisition terminal 1.

[0040] When it is confirmed that the person operating User Terminal 3 is the owner of User Terminal 3, User Terminal 3 extracts the personal information to be transmitted from the identification document data and transmits it to Information Acquisition Terminal 1. The personal information transmitted to Information Acquisition Terminal 1 may consist of four basic pieces of information, such as the name, address, date of birth, and gender of the person whose name is on the identification document (i.e., the owner of User Terminal 3).

[0041] The user terminal 3 may use biometric authentication to verify whether the person operating the user terminal 3 is the owner of the user terminal 3. In some cases, the digital wallet application may be launched when biometric authentication confirms that the person operating the user terminal 3 is the owner of the user terminal 3. In such cases, the user terminal 3 may be configured to verify whether the person operating the user terminal 3 is the owner of the user terminal 3 based on whether the digital wallet application is running (in active mode). For example, the user terminal 3 may be configured to consider the digital wallet application as running (in active mode) for a predetermined period of time after it has been launched, and to determine that the person operating the user terminal 3 is the owner of the user terminal 3. The user terminal 3 may also be configured to acquire a facial image of the person operating the user terminal 3 using an imaging device such as a camera, and to verify that the person operating the user terminal 3 is the owner of the user terminal 3 (i.e., the person whose name is on the identification document) by comparing the acquired facial image with the facial image of the person whose name is on the identification document included in the identification document data.

[0042] Even if identity data is stored in the digital wallet of the user terminal 3, there is information in the identity data that is stored on the IC card 2 but is not stored on the user terminal 3 (or cannot be retrieved from the user terminal 3). This information is called specific area information. An example of specific area information is the remaining number of IC lock attempts. The remaining number of IC lock attempts is the number of times an incorrect verification number can be entered when accessing the data stored on the IC card 2 using various devices, that is, the number of attempts until reading the IC card 2 is prohibited. In this embodiment, the specific area information is set to the remaining number of IC lock attempts.

[0043] The information acquisition terminal 1 is installed at a location where the check-in service is provided (for example, the hotel lobby, etc.). The information acquisition terminal 1 functions as a check-in terminal 1B, and the service user can perform the operations necessary for check-in on the screen displayed on the information acquisition terminal 1 during check-in.

[0044] The information acquisition terminal 1 requests the person attempting to check in (hereinafter referred to as the user applicant) to bring close a device (IC card 2 or user terminal 3) that stores the identity card as a procedure required for check-in. The information acquisition terminal 1 acquires the personal information of the user applicant from the device brought close (IC card 2 or user terminal 3) and transmits it to the business operator server 11.

[0045] Based on the personal information acquired by the information acquisition terminal 1 and the reservation information of the corresponding facility, the business operator server 11 determines whether check-in is possible and transmits the determination result to the information acquisition terminal 1. When the information acquisition terminal 1 acquires the determination result of whether check-in is possible from the business operator server 11, it performs processing (for example, screen display) based on the determination result. By setting the personal information acquired by the information acquisition terminal 1 as the basic four information composed of name, address, date of birth, and gender, it becomes easier to compare with the content described in the facility reservation information, and it is possible to appropriately determine whether to provide the check-in service.

[0046] Thus, the information acquisition terminal 1 requests the user applicant to bring close a device that stores the identity card and acquires personal information from the identity card. However, since the identity card can be stored not only in the IC card 2 but also in the user terminal 3 equipped with a digital wallet, the information acquisition terminal 1 is required to determine whether the device brought close is either the IC card 2 or the user terminal 3, perform communication based on the determination result with the device brought close, and acquire personal information.

[0047] Hereinafter, the configuration of the information acquisition terminal 1 for determining whether the device brought close is either the user terminal 3 or the IC card 2 and acquiring personal information from the device will be described in detail while also touching on the configurations of the IC card 2 and the user terminal 3.

[0048] Figure 2 shows a block diagram illustrating the configurations of the IC card 2, the user terminal 3, and the information acquisition terminal 1, and Figure 3 shows a functional block diagram of the information acquisition terminal 1.

[0049] As shown in Figure 2, the IC card 2 includes a processor 21, a memory 22, an antenna 23, a power supply module 24, and a security module 25.

[0050] The processor 21 is composed of a CPU or the like and functions as a central arithmetic processing unit within the IC card 2. The processor 21 performs various processes such as input / output to the security module 25 and communication control with external devices.

[0051] The memory 22 stores various data necessary for the processes executed by the processor 21. The memory 22 may include a non-volatile memory (ROM), a volatile memory (RAM), and a program memory. The non-volatile memory stores basic information, data such as an electronic certificate, and verification numbers. The volatile memory stores data and calculation results that are temporarily required for the processes performed by the processor 21. The program memory stores firmware executed by the processor 21 and programs for the security module 25.

[0052] The antenna 23 is embedded in the IC card 2 as a coiled conductor. The antenna 23 receives an electromagnetic wave transmitted from the information acquisition terminal 1 (reader / writer) and converts it into an electrical signal, and transmits an electromagnetic wave based on the output of the processor 21. Thereby, the processor 21 can perform communication based on the Near Field Communication (NFC) standard via the antenna 23.

[0053] The power supply module 24 supplies the power necessary for the operation of the IC card 2. Specifically, the power supply module 24 receives an electromagnetic wave transmitted from the information acquisition terminal 1 with the antenna 23, converts it into power, and supplies it to the processor 21, the memory 22, the security module 25, and the like.

[0054] The security module 25 includes an authentication module. The authentication module verifies the user's identity (user authentication) by comparing the data obtained via the NFC tag with a verification number stored in the memory 22. The security module 25 may also include an encryption engine that performs encryption and decryption processing, an intrusion detection module that detects unauthorized access or tampering, etc.

[0055] The user terminal 3 comprises a processor 31, memory 32, storage 33, a touch panel display 34, an NFC module 35, and a BLE module 36.

[0056] The processor 31, comprised of a CPU and other components, functions as the central processing unit responsible for controlling the entire user terminal 3. Based on inputs acquired from the touch panel display 34, the processor 31 processes data stored in the memory 32 and storage 33, and controls the touch panel display 34 and other modules. In addition, the processor 31 communicates with external devices (in this case, the information acquisition terminal 1) via the NFC module 35 and the BLE module 36.

[0057] Memory 32 stores various data necessary for the processing performed by the processor 31. Memory 32 includes non-volatile memory (ROM) and volatile memory (RAM).

[0058] The storage 33 is mainly composed of flash memory and stores various programs and data. The programs stored in the storage 33 include programs (software) for realizing the digital wallet function.

[0059] The touch panel display 34 has a screen and accepts input from the user of the user terminal 3.

[0060] The NFC module 35 mediates near-field communication (NFC) between the processor 31 and other devices (for example, the information acquisition terminal 1).

[0061] The BLE module 36 mediates wireless communication (BLE communication) between the processor 31 and other devices (e.g., the information acquisition terminal 1) based on the Bluetooth® Low Energy (BLE) standard.

[0062] Furthermore, communication based on the BLE standard requires the device itself to transmit wireless signals (electromagnetic waves). Therefore, devices that perform communication based on the BLE standard must be equipped with a power source (battery or external power) that supplies the power necessary for communication. Consequently, passive devices that receive power from a reader (for example, IC card 2) cannot perform communication based on the BLE standard.

[0063] As shown in Figure 2, the information acquisition terminal 1 comprises a processor 41, memory 42, storage 43, display device 44, input device 45, NFC module 46, and BLE module 47. In addition, the information acquisition terminal 1 may also include a network adapter (not shown) for communicating with the operator server 11.

[0064] The processor 41, composed of a CPU and the like, functions as the central processing unit responsible for controlling the entire information acquisition terminal 1. Based on the input acquired by the input device 45, the processor 41 processes based on programs and data stored in the memory 42 and storage 43, and displays various screens on the display device 44.

[0065] Furthermore, the processor 41 communicates with a nearby device via the NFC module 46 to determine whether that device is an IC card 2 or a user terminal 3.

[0066] When the adjacent device is IC card 2, the processor 41 performs near-field communication (NFC) via the NFC module 46 to obtain personal information (in this case, basic four pieces of information) of the cardholder of IC card 2 from IC card 2. Obtaining personal information from IC card 2 is possible only if the verification number entered in the input device 45 matches the verification number stored in IC card 2 and it is determined that the information can be provided by IC card 2.

[0067] On the other hand, when the adjacent device is the user terminal 3, the processor 41 performs short-range wireless communication (BLE communication) via the BLE module 47 and obtains personal information (in this case, basic four pieces of information) of the holder of the IC card 2 added to the digital wallet from the user terminal 3. Note that obtaining personal information from the user terminal 3 is only possible if it is determined that the user terminal 3 is able to provide it. Alternatively, instead of this determination, the system may be configured so that personal information from the user terminal 3 is possible when the digital wallet application is running (active mode).

[0068] Memory 42 stores various data necessary for the processing performed by the processor 41. Memory 42 includes non-volatile memory (ROM) and volatile memory (RAM).

[0069] The display device 44 is composed of a touch panel display 48 and has a screen for displaying various information related to the check-in procedure. The input device 45 is composed of the touch panel display 48 that makes up the display device 44 and acquires input to the screen provided by the display device 44.

[0070] The NFC module 46 is a communication device for performing near-field communication (NFC), and mediates near-field communication (NFC) between the processor 41 and other devices (for example, the IC card 2 and the user terminal 3).

[0071] The BLE module 47 is a communication device for performing communication based on the Bluetooth® Low Energy (BLE) standard, and mediates short-range wireless communication (BLE communication) based on the BLE standard between the processor 41 and other devices (for example, the user terminal 3).

[0072] As shown in Figure 3, the information acquisition terminal 1 includes, as functional units, a short-range communication unit 51, a BLE communication unit 52, a display unit 53, an input unit 54, a storage unit 55, and a control unit 56. The information acquisition terminal 1 may also include a network communication unit (not shown) for communicating with the carrier server 11.

[0073] The short-range communication unit 51 is comprised of an NFC module 46 and mediates short-range communication (NFC) between the control unit 56 and other devices (for example, the user terminal 3 and the IC card 2).

[0074] The BLE communication unit 52 is composed of a BLE module 47 and mediates BLE standard-based communication (BLE communication) between the control unit 56 and other devices (e.g., user terminal 3).

[0075] The display unit 53 is composed of a display device 44 (i.e., a touch panel display 48) and displays information related to the check-in procedure.

[0076] The input unit 54 is comprised of an input device 45 (i.e., a touch panel display 48) that receives input from a person attempting to check in.

[0077] The storage unit 55 consists of a memory 42 and a storage device 43, and stores various programs and data required for processing by the control unit 56.

[0078] The control unit 56 is configured by the processor 41 executing an information acquisition program stored in the memory unit 55. The control unit 56 performs information acquisition processing according to an information acquisition method for acquiring personal information, and acquires personal information by communicating with a device brought in close by the person attempting to check in.

[0079] The control unit 56 includes an information acquisition unit 57 and a user interface processing unit (hereinafter referred to as the UI processing unit 58).

[0080] The information acquisition unit 57 communicates with a nearby device and performs processing to acquire personal information of the person who is trying to receive the service (the person who is trying to check in). The information acquisition unit 57 may be configured by the processor 41 executing a predetermined application. If identity verification is performed using the acquired personal information, this application may also be called an identity verification application.

[0081] The UI processing unit 58 controls the display unit 53 based on instructions from the information acquisition unit 57 and performs various processes to accept input at the input unit 54. The UI processing unit 58 may be configured by having the processor 41 execute an application that controls the touch panel display 48.

[0082] Next, the details of the information acquisition process performed by the control unit 56 (processor 41) will be described. Figure 4 shows a flowchart of the information acquisition process. Figure 5 shows a flowchart of the IC card reading process performed by the control unit 56 (processor 41) when the nearby device is the IC card 2. Figure 6 shows a flowchart of the digital wallet identity data reading process performed by the control unit 56 (processor 41) when the nearby device is the user terminal 3. As shown in Figure 4, the IC card reading process and the digital wallet identity data reading process are both included in the information acquisition process.

[0083] As shown in Figure 4, when the control unit 56 (processor 41) starts the information acquisition process, it first displays a proximity request screen 61 to the person who wants to check in (i.e., the prospective user) requesting them to bring the user terminal 3 or IC card 2 close to the information acquisition terminal 1 (ST101).

[0084] Figure 7 shows an example of a proximity request screen 61. The proximity request screen 61 may include text prompting the user to bring their IC card 2 or user terminal 3 close to the device. In the example shown in Figure 7, the proximity request screen 61 includes the text 61A "Please hold your My Number Card or electronic device over the device."

[0085] Once the display of the proximity request screen 61 is complete, the control unit 56 (processor 41) activates the short-range communication unit 51 (NFC module 46) (ST102).

[0086] Once the short-range communication unit 51 has finished starting up, the control unit 56 (processor 41) determines whether short-range communication (NFC) has been established with the nearby device (ST103).

[0087] If it is determined that short-range communication has not been established (No in ST103), the control unit 56 (processor 41) waits until short-range communication is established.

[0088] If it is determined that short-range communication has been established (Yes in ST103), the control unit 56 (processor 41) sends a read request (also called a read trial request) from the short-range communication unit 51 (NFC module 46) to the nearby device requesting it to read the specific area information stored in the IC card 2 (ST104).

[0089] When IC card 2 receives a read request, it transmits specific area information to information acquisition terminal 1 (control unit 56). When user terminal 3 receives a read request, it transmits a signal to information acquisition terminal 1 (control unit 56) indicating that it failed to acquire the specific area information. Alternatively, when IC card 2 receives a read request, it may transmit to information acquisition terminal 1 whether it succeeded or failed to acquire the specific area information.

[0090] The control unit 56 (processor 41) determines whether or not it has succeeded in reading specific area information in the adjacent device based on the signal from the adjacent device (ST105).

[0091] Next, when the control unit 56 (processor 41) determines that it has successfully read specific area information from a nearby device (Yes in ST105), it determines that the nearby device is IC card 2, performs communication (NFC communication) corresponding to IC card 2, and executes IC card reading processing (ST106) to acquire personal information (basic four pieces of information) stored in IC card 2. Once the IC card reading processing is complete, the control unit 56 finishes the information acquisition processing.

[0092] When the control unit 56 (processor 41) determines that it has failed to read specific area information from a nearby device (No in ST105), it determines that the nearby device is the user terminal 3, performs communication (BLE communication) corresponding to the user terminal 3, and executes the digital wallet identity data reading process (ST107) to acquire personal information (basic four pieces of information) stored in the user terminal 3. Once the digital wallet identity data reading process is completed, the control unit 56 finishes the information acquisition process.

[0093] Next, referring to Figure 5, we will describe the details of the IC card reading process that the control unit 56 (processor 41) executes when it determines that the nearby device is IC card 2.

[0094] As shown in Figure 5, the control unit 56 (processor 41) first displays the consent / verification number acquisition screen 62 during the IC card reading process (ST201).

[0095] Figure 8 shows an example of the consent and verification number acquisition screen 62. In the example shown in Figure 8, the consent and verification number acquisition screen 62 includes an input field 62A for the verification number, a consent button 62B that accepts input indicating consent to the provision of personal information (basic four pieces of information), and a completion button 62C that indicates that the input has been completed.

[0096] If no input is made to the consent button 62B, or if no input is made to the input field 62A (No in ST202), the control unit 56 displays the consent / verification number acquisition screen 62 on the display unit 53 and waits until input is made to the consent button 62B and input field 62A.

[0097] When the consent button 62B is pressed, the verification number is entered in the input field 62A, and the completion button 62C is pressed (i.e., consent and the acquisition of the verification number are complete) (Yes in ST202), the control unit 56 sends a request to the nearby device to transmit personal information (basic four pieces of information) (ST203). Along with the request to transmit personal information, the control unit 56 encrypts the acquired verification number as appropriate and transmits it to the nearby device.

[0098] When the processor 21 of the nearby device (IC card 2) receives a request to transmit personal information, it uses the acquired verification number to retrieve the corresponding personal information from the memory 22. If the acquisition of personal information is successful, the processor 21 of the nearby device transmits the acquired personal information (in this case, the four basic pieces of information) to the information acquisition terminal 1 (control unit 56). If the acquisition of personal information fails, the processor 21 of the nearby device transmits a signal to the information acquisition terminal 1 (control unit 56) indicating that the acquisition of personal information failed. An example of a failure to acquire personal information is when an incorrect verification number is entered.

[0099] When the control unit 56 receives a response from a nearby device to a request to transmit personal information, it determines whether the nearby device has successfully obtained the personal information (i.e., whether the personal information has been transmitted) (ST204).

[0100] When the control unit 56 determines that it has successfully acquired personal information from a nearby device (Yes in ST204), it causes the display unit 53 to display a completion notification screen 63 indicating that the acquisition of personal information has been completed (ST205). Once the display of the completion notification screen 63 is complete, the control unit 56 finishes the IC card reading process.

[0101] Figure 9 shows an example of a completion notification screen 63. In the example shown in Figure 9, the completion notification screen 63 includes text 63A indicating that the acquisition of personal information has been completed.

[0102] When the control unit 56 determines that it has failed to acquire personal information from a nearby device (No in ST204), it causes the display unit 53 to display a failure notification screen 64 indicating that the acquisition of personal information has failed (ST206). Once the display of the failure notification screen 64 is complete, the control unit 56 finishes the IC card reading process.

[0103] Figure 10 shows an example of a failure notification screen 64. In the example shown in Figure 10, the failure notification screen 64 includes text 64A indicating that the acquisition of personal information failed.

[0104] Next, referring to Figure 6, we will explain the details of the digital wallet identity data reading process that the control unit 56 (processor 41) executes when it determines that the nearby device is the user terminal 3.

[0105] As shown in Figure 6, the control unit 56 (processor 41) first activates the BLE communication unit 52 (BLE module 47) in the digital wallet identity data reading process (ST301).

[0106] Once the BLE communication unit 52 has finished starting up, the control unit 56 (processor 41) displays the consent acquisition screen 65 (ST302).

[0107] Figure 11 shows an example of a consent acquisition screen 65. In the example shown in Figure 11, the consent acquisition screen 65 includes a consent button 65A that accepts input of consent to provide personal information (basic four pieces of information), and a completion button 65B that indicates that the input of consent has been completed.

[0108] If no input is made to the consent button 65A and consent to the provision of personal information has not been obtained (No in ST303), the control unit 56 displays the consent acquisition screen 65 on the display unit 53 and waits until input is made to the consent button 65A.

[0109] If the consent button 65A is pressed and consent to the provision of personal information is obtained, and the completion button 65B is pressed (Yes in ST303), the control unit 56 sends a request to transmit personal information (in this case, basic four pieces of information) to the nearby device (user terminal 3) via the BLE communication unit 52 (ST304).

[0110] The processor 31 of the nearby device (user terminal 3) determines that the person who brought the device close is the owner of the digital wallet identity data, and then retrieves the requested personal information and transmits the retrieved personal information (in this case, the four basic pieces of information) to the information retrieval terminal 1. The processor 31 of the nearby device (user terminal 3) does not transmit the personal information (the four basic pieces of information) if it has not confirmed that the person operating the device (the person who brought the device close) is the owner of user terminal 3.

[0111] The processor 31 of the nearby device (user terminal 3) may, for example, when launching a digital wallet application, verify through biometric authentication that the person operating the device is the owner of user terminal 3, determine whether the person who brings the device close is the owner of user terminal 3 (i.e., whether they are the holder of the identification document stored as digital wallet identification data on user terminal 3) based on whether the application is active or not. Alternatively, user terminal 3 may acquire a facial image of the person operating user terminal 3 using an imaging device such as a camera, and determine whether the person operating user terminal 3 is the owner of user terminal 3 (i.e., the holder of the digital wallet identification data) by comparing the acquired facial image with the facial image of the holder of the identification document included in the digital wallet identification data.

[0112] Furthermore, if biometric authentication for the person operating the device has not been completed, the processor 31 of the nearby device (user terminal 3) may send a signal to the information acquisition terminal 1 indicating that it failed to acquire personal information.

[0113] When the control unit 56 (processor 41) receives a response from a nearby device (user terminal 3) to a request to transmit personal information, it determines whether the nearby device has successfully obtained the personal information (whether the personal information has been transmitted) (ST305).

[0114] When the control unit 56 (processor 41) determines that it has successfully acquired personal information from a nearby device (Yes in ST305), it causes the display unit 53 to display a completion notification screen 63 indicating that the acquisition of personal information has been completed (ST306). Once the display of the completion notification screen 63 is complete, the control unit 56 finishes the digital wallet identity data reading process.

[0115] When the control unit 56 (processor 41) determines that it has failed to acquire personal information from a nearby device (No in ST305), it causes the display unit 53 to display a failure notification screen 64 indicating that the acquisition of personal information has failed (ST307). Once the display of the failure notification screen 64 is complete, the control unit 56 finishes the digital wallet identity data reading process.

[0116] In this embodiment, the information acquisition terminal 1 transmits the acquired personal information to the service provider server 11, and the service provider server 11 determines whether check-in is permitted by comparing it with the reservation information. The service provider server 11 transmits the result of the check-in permission determination to the information acquisition terminal 1, and upon receiving the determination result, the information acquisition terminal 1 performs various processes based on that determination result.

[0117] Next, the information acquisition process when a person attempting to check in (i.e., a prospective user) provides personal information using IC card 2 will be explained with reference to the diagrams. Figure 12 shows a sequence diagram illustrating the information acquisition process when a prospective user provides personal information using IC card 2. Note that if a process in the sequence diagram shown in Figure 12 is the same as a process shown in Figures 4 to 6, the process in the sequence diagram shown in Figure 12 is denoted by the same reference numeral as the process shown in Figures 4 to 6.

[0118] When the information acquisition process is started, the UI processing unit 58 (processor 41) of the information acquisition terminal 1 displays a proximity request screen 61 (see also Figure 7) on the display unit 53 (touch panel display 48) (ST101, see also Figure 4). When the display of the proximity screen is complete, the UI processing unit 58 outputs a notification to the information acquisition unit 57 indicating that the display is complete (display completion notification) (ST351).

[0119] When the information acquisition unit 57 (processor 41) receives a display completion notification, it activates the short-range communication unit 51 (NFC module 46) (ST102). This establishes NFC communication between the nearby device (IC card 2) and the information acquisition terminal 1 (ST352).

[0120] Once the short-range communication unit 51 has finished starting up, the information acquisition unit 57 (processor 41) sends a read request to the nearby device (IC card 2) requesting it to read the specific area information stored in the IC card 2 (ST104).

[0121] When a nearby device (IC card 2) receives a read request, it performs the reading of specific area information and notifies the information acquisition unit 57 (processor 41) of the result (that the reading was successful and the specific area information that was read) (ST353).

[0122] When the information acquisition unit 57 receives notification of the reading result of a specific area, it confirms whether the reading of the information in the specific area was successful (ST105) and notifies the UI processing unit 58 that the reading was successful (i.e., that the nearby device is IC card 2) (ST354).

[0123] When the UI processing unit 58 (processor 41) receives notification that the reading was successful, it displays the consent / verification number acquisition screen 62 (see also Figure 8) on the display unit 53 (touch panel display 48) (ST201, see also Figure 5). When the UI processing unit 58 (processor 41) receives consent for the acquisition of personal information (i.e., provision to the service provider) and a verification number for accessing the personal information from the input unit 54, it notifies the information acquisition unit 57 that consent and the verification number have been acquired (acquisition completion notification) (ST355).

[0124] When the information acquisition unit 57 receives notification that consent and the acquisition of the verification number have been completed, it sends a request to transmit personal information, including the verification number, to the nearby device (IC card 2) and requests the transmission of personal information (ST203).

[0125] When a nearby device (IC card 2) receives a request to transmit personal information, it compares the verification number it stores with the transmitted verification number to determine whether or not to provide the personal information (ST356). Subsequently, if the nearby device (IC card 2) can compare (match) the verification number it stores with the transmitted verification number, it determines that it can provide the personal information, acquires the personal information of the IC card holder (in this case, the four basic pieces of information), and transmits it to the information acquisition unit 57 (ST357). When the information acquisition unit 57 acquires the personal information, it notifies the UI processing unit 58 that the acquisition of personal information is complete (ST358), and the UI processing unit 58 (processor 41) displays a completion notification screen 63 on the display unit 53 (touch panel display 48) (ST205).

[0126] Next, we will explain the information acquisition process when a person attempting to check in (i.e., a prospective user) provides personal information using the user terminal 3, with reference to the diagram. Figure 13 shows a sequence diagram illustrating the information acquisition process when a prospective user provides personal information using the user terminal 3.

[0127] In this case as well, similar to when a user provides personal information using IC card 2, the UI processing unit 58 displays the proximity request screen 61 on the display unit 53 (touch panel display 48) (ST101) and outputs a display completion notification to the information acquisition unit 57 (ST351). When the information acquisition unit 57 receives the display completion notification, it activates the short-range communication unit 51 (NFC module 46) (ST102). As a result, NFC communication is established between the nearby device (user terminal 3) and the information acquisition terminal 1 (ST352).

[0128] Once the short-range communication unit 51 has finished starting up, the information acquisition unit 57 (processor 41) sends a read request to the nearby device (user terminal 3) requesting it to read the specific area information stored in the IC card 2 (ST104).

[0129] The user terminal 3 notifies the user terminal of the result of reading the specific area information (ST353). Since the user terminal 3 is unable to read the specific area information, it sends a notification to the information acquisition unit 57 (processor 41) indicating that it failed to read the specific area information.

[0130] When the information acquisition unit 57 receives notification of the reading result for a specific area and confirms that it failed to read the specific information (ST105), it activates the BLE communication unit 52 (ST301) and establishes BLE communication with the nearby device (user terminal 3) (ST360). Subsequently, the information acquisition unit 57 notifies the UI processing unit 58 that the reading failed (i.e., that the nearby device is user terminal 3) (ST361).

[0131] When the UI processing unit 58 (processor 41) receives notification that reading has failed, it displays a consent acquisition screen 65 (see also Figure 11) on the display unit 53 (touch panel display 48) (ST302, see also Figure 6). When the UI processing unit 58 (processor 41) obtains consent for the acquisition of personal information (i.e., provision to service providers) at the input unit 54, it notifies the information acquisition unit 57 that consent has been obtained (acquisition completion notification) (ST362).

[0132] When the information acquisition unit 57 receives notification that consent has been obtained, it sends a request to transmit personal information to the nearby device (user terminal 3) and requests the transmission of personal information (ST304). When the nearby device (user terminal 3) receives the request to transmit personal information, it determines whether or not to provide personal information by determining whether the digital wallet application is active (ST363). If the digital wallet application is active, the user terminal 3 determines that it can provide personal information, acquires the personal information of the account holder (in this case, the four basic pieces of information) stored as digital wallet identity data, and transmits it to the information acquisition unit 57 (ST364). When the information acquisition unit 57 acquires the personal information, it notifies the UI processing unit 58 that the acquisition of personal information is complete (ST365), and the UI processing unit 58 (processor 41) displays a completion notification screen 63 on the display unit 53 (touch panel display 48) (ST306).

[0133] As shown in Figures 12 and 13, the information acquisition terminal 1 can acquire personal information regardless of whether the user brings the IC card 2 or the user terminal 3 close to it. The information acquisition terminal 1 transmits the acquired personal information to the service provider server 11, and if the service provider server 11 determines that check-in is possible, it performs the check-in process.

[0134] Therefore, users can check in using either the IC card 2 or the user terminal 3, thereby improving the convenience of the check-in system 10.

[0135] While the personal information acquired by the information acquisition terminal 1 from a nearby device (IC card 2 or user terminal 3) consisted of the four basic pieces of information, any information that can be used to determine whether or not to provide the service may be used. For example, the personal information acquired by the information acquisition terminal 1 may include at least one of the four basic pieces of information consisting of the name, address, date of birth, and gender of the person whose name is on the identification card.

[0136] For example, if the information acquisition terminal 1 is used in a payment service at a store selling age-restricted products (such as alcoholic beverages and tobacco products), the information acquisition terminal 1 may be configured to acquire only the date of birth information for age verification from the nearby device. However, if the four basic pieces of information are transmitted all at once (for example, if the nearby device is a My Number Card 2A and verification is performed using the verification number), the information acquisition terminal 1 may be configured to immediately delete all information except the date of birth from the four basic pieces of information acquired from the nearby device. In addition, the information acquisition terminal 1 may be configured to acquire only the necessary information (date of birth information) from the nearby device (for example, a smartphone 3A) by communicating in accordance with a protocol defined in international standards, etc.

[0137] Furthermore, the specific area information is not limited to the number of remaining reads until reading of IC card 2 is prohibited, and the specific area information may be any information that is not stored in the user terminal 3 (or cannot be obtained from the user terminal 3) and is stored only in IC card 2. In addition, when the information acquisition terminal 1 establishes communication with a nearby device via NFC for the first time (when it becomes Yes in ST103 in Figure 4), it may acquire the type of identification document stored in the nearby device (such as My Number Card 2A or driver's license 2B) and set the specific area information based on that type.

[0138] When the information acquisition terminal 1 requests to read specific area information, the IC card 2 may transmit either a signal indicating successful reading or the read specific area information to the information acquisition terminal 1. If the IC card 2 transmits a signal indicating successful reading, the information acquisition terminal 1 is configured to determine that the nearby device is the IC card 2 when it receives a signal indicating successful reading from the nearby device. If the IC card 2 transmits the read specific area information, the information acquisition terminal 1 is configured to determine that the nearby device is the IC card 2 when it receives the specific area information.

[0139] Furthermore, in the above embodiment, the information acquisition terminal 1 was configured to send a request to a nearby device to read specific area information stored only in the IC card 2, and to determine the type of device based on the success or failure of the request. However, the information acquisition terminal 1 may also be configured to send a request to a nearby device to read at least a portion of the digital wallet identity data (hereinafter referred to as "specific information") according to the digital wallet identity data reading procedure, and to determine the type of device based on the success or failure of the request. Specifically, the information acquisition terminal 1 may be configured to send a request to a nearby device from a communication device (NFC module 46) to read specific information from the digital wallet identity data, determine that the nearby device is a user terminal 3 storing the digital wallet identity data when the reading of the specific information is successful, and determine that the nearby device is an IC card 2 when the reading of the specific information fails.

[0140] Furthermore, connection of the information acquisition terminal 1 to the service provider's server 11 is not mandatory. In other words, the information acquisition terminal 1 may not be connected to the service provider's server 11 and may be configured as an information acquisition device that performs the above-mentioned information acquisition process to acquire personal information from nearby devices and displays the personal information to the service provider.

[0141] <<Second Embodiment>> The information acquisition terminal 1 according to the second embodiment has a configuration that is generally the same as that of the first embodiment and can acquire personal information from both the IC card 2 and the user terminal 3. However, the information acquisition terminal 1 according to the second embodiment differs in that it can determine whether the IC card 2 is a My Number Card 2A (hereinafter also referred to as MyNa Card) or a driver's license 2B and read the corresponding data from each. Furthermore, the information acquisition terminal 1 according to the second embodiment differs from the first embodiment in that it can read the data of at least one of MyNa data and mobile driver's license data if the user terminal 3 stores at least one of them as digital wallet identification data.

[0142] However, My Number Data is the same type of data as the personal information stored in the IC chip 13 of the My Number Card 2A, and is stored in the user terminal 3 in a specific format (mdoc format) for storage in the user terminal 3. The difference is that the IC chip 13 of the My Number Card 2A cannot output the four basic pieces of information individually in response to external requests (i.e., it can only output the four basic pieces of information as a whole), whereas the user terminal 3 can output the personal information contained in the My Number Data individually in response to external requests.

[0143] The mobile driver's license data is similar to the personal information stored in the driver's license 2B, and is stored in the user terminal 3 in a specific format (mDL format) for storage in the user terminal 3. Similarly, the IC chip 13 of the driver's license 2B cannot output the basic four pieces of information individually in response to external requests (i.e., it can only output the basic four pieces of information as a whole), whereas the user terminal 3 differs in that it can output the personal information contained in the mobile driver's license data individually in response to external requests.

[0144] Furthermore, My Number Card 2A and Driver's License 2B have different folder (also called directory; hereinafter the same) structures for the data stored on the IC chip 13. Therefore, the information acquisition terminal 1 can determine whether a nearby device is a My Number Card 2A or a Driver's License 2B by making a read request to the folder specific to each. The read request may be made, for example, by requesting the nearby device to search a predetermined folder (in detail, by executing a SELECT command).

[0145] Figure 14 shows a flowchart of the information acquisition process performed by the information acquisition terminal 1 according to the second embodiment. The information acquisition terminal 1 performs the information acquisition process at predetermined intervals.

[0146] As shown in Figure 14, in the information acquisition process, the information acquisition terminal 1 first displays a proximity request screen 61 on the touch panel display 48, similar to that of the first embodiment (ST401).

[0147] The proximity request screen 61 may include text instructing the person bringing the device close to launch the digital wallet app on the user terminal 3. Note that, through biometric authentication or other means used when launching the digital wallet app, the digital wallet app can only be launched if the person bringing the device (user terminal 3) close is the owner of that user terminal 3.

[0148] Once the proximity request screen 61 is displayed, the information acquisition terminal 1 performs device engagement processing on the nearby device (ST402). Device engagement processing is a process defined in ISO 23220, and specifically involves establishing an NFC data communication channel, a BLE data communication channel, or a Wi-Fi data communication channel by connecting with the user terminal 3 via NFC. When establishing a data communication channel, the information acquisition terminal 1 may display a two-dimensional code containing the information necessary to establish the NFC data communication channel, a BLE data communication channel, or a Wi-Fi data communication channel, and the user terminal 3 may establish one of these data communication channels by reading this two-dimensional code. Alternatively, the user terminal 3 may display a two-dimensional code containing the information necessary to establish one of the data communication channels on its screen, and the information acquisition terminal 1 may read it to establish the data communication channel.

[0149] This device engagement process establishes a connection (communication) between the nearby device and the information acquisition terminal 1 when the nearby device is a user terminal 3 such as a smartphone. On the other hand, when the nearby device is not a user terminal 3 such as a smartphone, but a physical card (such as a My Number Card 2A or a driver's license 2B), a connection is not established between the nearby device and the information acquisition terminal 1. In this case, it is preferable that the device engagement process is configured such that at least one of My Number data or mobile driver's license data is stored in the user terminal 3, and a connection is established between the information acquisition terminal 1 and the user terminal 3 when predetermined conditions (hereinafter referred to as connection conditions) are met.

[0150] The connection condition may be that the person who brings the user terminal 3 close to it is confirmed to be the owner of the user terminal 3. Specifically, the connection condition may be, for example, that the digital wallet app is running on the user terminal 3. Alternatively, the connection condition may be that authentication is performed, such as biometric authentication, to allow the provision of at least one of the My Number data or mobile driver's license data stored in the user terminal 3 to the other terminal. In this case, even if the digital wallet app is not running on the user terminal 3, the connection between the information acquisition terminal 1 and the user terminal 3 is established, improving user convenience.

[0151] In the device engagement process, the information acquisition terminal 1 may first send a device engagement start request to the nearby device. In this case, the information acquisition terminal 1 may determine that a connection has been established (i.e., the device engagement process has been successful) when it receives a device engagement completion notification from that device within a predetermined time after sending the device engagement start request.

[0152] On the other hand, in the device engagement process, if the information acquisition terminal 1 does not receive a device engagement completion notification from a nearby device within a predetermined time after transmission, it is preferable to determine that the connection was not established (the device engagement process failed).

[0153] After executing the device engagement process, the information acquisition terminal 1 determines whether a connection has been established (i.e., whether the device engagement process was successful) (ST403).

[0154] If the information acquisition terminal 1 has successfully completed the device engagement process and determined that a connection has been established with the nearby device (Yes in ST403), it sends a request to read the My Number data to the nearby device (i.e., user terminal 3) and determines whether or not the My Number data can be read (ST404).

[0155] The determination of whether or not My Number data can be read may be performed by the information acquisition terminal 1 sending a read request to a nearby device (user terminal 3) requesting the reading of at least a portion of the My Number data, and then obtaining the corresponding data and whether or not the My Number data can be read from the nearby device.

[0156] If the information acquisition terminal 1 determines that it is capable of reading My Number data (Yes in ST404), it executes the My Number data acquisition process (hereinafter referred to as the My Number data acquisition process) (ST405).

[0157] If the information acquisition terminal 1 determines that it cannot read the My Number data (No in ST404), it sends a request to read the mobile driver's license data to the nearby device (user terminal 3) and determines whether or not the mobile driver's license data can be read (ST406).

[0158] The determination of whether or not mobile driver's license data can be read may be performed by the information acquisition terminal 1 sending a read request to a nearby device (user terminal 3) requesting the reading of at least a portion of the mobile driver's license data, and then obtaining the corresponding data and whether or not the mobile driver's license data can be read from the nearby device.

[0159] If the information acquisition terminal 1 determines that it can read the mobile driver's license data (Yes in ST406), it executes a process to acquire the mobile driver's license data (hereinafter referred to as the mobile driver's license data acquisition process) (ST407). If the information acquisition terminal 1 determines that it cannot read the mobile driver's license data (No in ST406), it executes an error process to notify the person who has brought the device close to it by displaying a message on the touch panel display 48 that the data relating to personal information could not be acquired (ST408). Note that the error process (for example, a screen display for error notification) is not mandatory, and the information acquisition process may be completed without performing any error processing.

[0160] If the information acquisition terminal 1 determines that the device engagement process has failed and that a connection with the nearby device could not be established (No in ST402), it sends a My Number Card reading request to the nearby device (i.e., IC card 2) and determines whether or not it can be read (ST409).

[0161] The My Number Card reading request referred to here may be made by a SELECT command that requests a search for a unique folder stored in the IC chip 13 of the My Number Card 2A. When the nearby device is a My Number Card 2A, the IC chip 13 of the My Number Card 2A sends a response to the information acquisition terminal 1 indicating that the search was successful. Upon receiving the response indicating that the search was successful, the information acquisition terminal 1 determines that it was possible to read the My Number Card 2A (that the reading was successful).

[0162] If the information acquisition terminal 1 determines that it is possible to read the My Number Card 2A (Yes in ST409), it executes a My Number Card reading process to read personal information (in this case, the four basic pieces of information) from the nearby device (specifically, the IC chip 13 of the My Number Card 2A) (ST410).

[0163] If the information acquisition terminal 1 determines that it cannot read the My Number Card 2A (No in ST409), it sends a request to read the driver's license and determines whether it can be read (ST411).

[0164] The request to read the driver's license, as used here, may be made by a SELECT command that requests a search for a unique folder stored in the IC chip 13 of the My Number Card 2A. When the nearby device is a driver's license 2B, the IC chip 13 of the driver's license 2B sends a response to the information acquisition terminal 1 indicating that the search was successful. Upon receiving the response indicating that the search was successful, the information acquisition terminal 1 determines that it was possible to read the driver's license 2B (that the reading was successful).

[0165] If the information acquisition terminal 1 determines that the driver's license 2B is readable (Yes in ST411), it executes a process to read the data stored in the IC chip 13 of the driver's license 2B (hereinafter referred to as the driver's license reading process) (ST412).

[0166] If the information acquisition terminal 1 determines that it cannot read the driver's license 2B (No in ST411), it performs error processing to notify the person who has brought the device close to it via a screen display on the touch panel display 48 that it was not possible to acquire data related to personal information (ST413).

[0167] Next, we will explain the details of the My Number data acquisition process. The My Number data acquisition process is the process by which the information acquisition terminal 1 acquires My Number data from the user terminal 3, and Figure 15 shows the flowchart of this My Number data acquisition process.

[0168] The My Number data acquisition process is executed when the connection conditions are met. Depending on the connection conditions, it may be confirmed before the My Number data acquisition process that the person who brings user terminal 3 close to the device is the owner of user terminal 3.

[0169] In the My Number data acquisition process, the information acquisition terminal 1 first displays a consent acquisition screen 65 on the touch panel display 48 that accepts input whether or not the user consents to the provision of personal information (ST501).

[0170] Next, the information acquisition terminal 1 determines on the consent acquisition screen 65 whether it has completed acquiring the input indicating consent to the provision of personal information (hereinafter referred to as consent input) (ST502). If it determines that consent input has been acquired (Yes in ST502), the information acquisition terminal 1 sends a My Number data acquisition request to the nearby device (i.e., user terminal 3) (ST503). Subsequently, the information acquisition terminal 1 acquires My Number data (specifically, at least a part of the My Number data) from the nearby device (ST504), displays on the touch panel display 48 that My Number data has been acquired and information related to the acquired My Number data (ST505), and ends the My Number data acquisition process. If consent input could not be acquired (No in ST502), the information acquisition terminal 1 displays an end message on the touch panel display 48 indicating that consent input could not be confirmed, and ends the My Number data acquisition process.

[0171] The items (also called types) of My Number Data that the information acquisition terminal 1 requests in the My Number Data acquisition request can be set as needed or by user input. For example, the information acquisition terminal 1 may display the items of personal information data included in My Number Data on the consent acquisition screen 65 and accept the user's selection of items to which they consent to the provision. The information acquisition terminal 1 may also be configured to display selection input fields on the consent acquisition screen 65 for items to be provided, such as consenting to provide all information including name, address, gender, and date of birth, or consenting to provide only the date of birth (or information on whether the user is 20 years of age or older, etc.), and accept the user's consent input regarding the provision. In this case, the personal information data that the information acquisition terminal 1 requests in the My Number Data acquisition request ST 503 is limited to those for which consent has been obtained regarding provision, and the My Number Data (user's personal information) acquired by the information acquisition terminal 1 in ST 504 is limited to only the items for which consent has been obtained regarding provision.

[0172] Next, we will explain the details of the mobile driver's license data acquisition process. Figure 16 shows a flowchart of the mobile driver's license data acquisition process.

[0173] The mobile driver's license data acquisition process is executed when the digital wallet app is running (i.e., when biometric authentication has been completed on user terminal 3). Therefore, before the mobile driver's license data acquisition process is initiated, it is already confirmed that the person who brings user terminal 3 close to the device is the owner of user terminal 3.

[0174] As shown in Figures 15 and 16, the mobile driver's license data acquisition process differs from the My Number data acquisition process in two ways. First, in the My Number data acquisition process (Figure 15), the information acquisition terminal 1 sends a My Number data acquisition request to a nearby device (ST503), whereas in the mobile driver's license data acquisition process (Figure 16), the information acquisition terminal 1 sends a mobile driver's license data reading request to a nearby device (ST603). Second, in the My Number data acquisition process (Figure 15), the information acquisition terminal 1 acquires My Number data from a nearby device (ST504), whereas in the mobile driver's license data acquisition process (Figure 16), the information acquisition terminal 1 acquires mobile driver's license data (specifically, at least a portion of the mobile driver's license data) from a nearby device (ST604). In all other respects, the mobile driver's license data acquisition process is the same as the My Number data acquisition process.

[0175] Furthermore, the mobile driver's license data requested by the information acquisition terminal 1 in the mobile driver's license data reading request may be set as necessary or by user input, similar to the My Number data items (also called types) requested in the My Number data acquisition request. Similar to the My Number data acquisition process, in the mobile driver's license data acquisition process, the information acquisition terminal 1 may be configured to display the items of personal information included in the mobile driver's license data on the consent acquisition screen 65, accept input regarding consent for provision, and acquire only the items for which consent for provision has been obtained.

[0176] Next, we will explain in detail the process for reading data stored in the My Number Card 2A (specifically, the IC chip 13 of the My Number Card 2A) (hereinafter referred to as the My Number Card reading process). Figure 17 shows a flowchart of the My Number Card reading process.

[0177] Therefore, in the My Number Card reading process, the information acquisition terminal 1 first sends a My Number Card basic four information reading request (hereinafter referred to as the My Number Card reading request) to the nearby device, instructing it to read the My Number Card 2A in a manner that reads the basic four information (ST701).

[0178] When the nearby device is a My Number Card 2A, a My Number Card reading request is sent, and the My Number Card 2A sends a PIN code input request to the information acquisition terminal 1, requesting the input of a PIN code.

[0179] When the information acquisition terminal 1 receives a PIN input request, it displays a PIN code input screen on the touch panel display 48 to accept PIN code input and transmits the entered PIN code to a nearby device (ST702).

[0180] When the nearby device is a My Number Card 2A, the nearby device (My Number Card 2A) obtains a PIN code from the information acquisition terminal 1 and then transmits the basic four pieces of information to the information acquisition terminal 1.

[0181] After the information acquisition terminal 1 transmits a PIN code to the nearby device, it determines whether the four basic pieces of information were acquired within a predetermined time (i.e., whether the My Number Card 2A was successfully read) (ST703).

[0182] If the four basic pieces of information are obtained, the information acquisition terminal 1 extracts only the necessary information required for subsequent processing from the obtained four basic pieces of information and deletes the information other than the necessary information (ST704). After that, the information acquisition terminal 1 displays the obtained necessary information on the touch panel display 48 (ST705) and finishes the My Number Card reading process. If the four basic pieces of information cannot be obtained, the information acquisition terminal 1 displays on the touch panel display 48 that data acquisition failed (ST706) and finishes the My Number Card reading process.

[0183] During the My Number Card reading process, the data acquired consists of four basic pieces of information, and it is not possible to select and acquire any of these pieces of data. Therefore, any information from the four basic pieces of information that is not needed for subsequent processing is promptly deleted from the information acquisition terminal 1.

[0184] Furthermore, there is no process to verify whether the person holding the My Number Card 2A close to the card is the owner of the My Number Card 2A (the person corresponding to the personal information stored on the IC chip of the My Number Card 2A) before the My Number Card reading process is completed. Therefore, when the PIN code is entered (ST702), the four basic pieces of information are acquired (ST703-705).

[0185] Next, we will explain in detail the process for reading the driver's license 2B (more specifically, the data stored in the IC chip 13 of the driver's license 2B) (hereinafter referred to as the driver's license reading process). Figure 18 shows a flowchart of the driver's license reading process.

[0186] As shown in Figures 17 and 18, in the My Number Card reading process (Figure 17), the information acquisition terminal 1 transmits a request to read the four basic pieces of information to the nearby device by reading the My Number Card 2A (ST701). On the other hand, in the driver's license reading process (Figure 18), the information acquisition terminal 1 transmits a request to read the four basic pieces of information of the driver's license 2B by reading the driver's license 2B, instructing the device to read the four basic pieces of information (ST801). The rest of the configuration for the driver's license reading process is the same as for the My Number Card reading process.

[0187] In the driver's license reading process, the data acquired consists of four basic pieces of information, and it is not possible to select and acquire any of these pieces of data. Therefore, any information from the four basic pieces of information that is not needed for subsequent processing is promptly deleted from the information acquisition terminal 1 (ST704).

[0188] Figure 19 shows a sequence diagram of the information acquisition process in the second embodiment, when the user terminal 3 that stores the minor data is in close proximity to the information acquisition terminal 1. In Figure 19, processes similar to those in Figures 14 to 18 are illustrated with the same step numbers.

[0189] As shown in Figure 19, when the information acquisition process is started, the UI processing unit 58 (processor 41) of the information acquisition terminal 1 displays a proximity request screen 61 on the touch panel display 48 (ST401). The proximity request screen 61 may include text requesting the launch of a digital wallet application, such as "If reading a smartphone, please launch the digital wallet application." The proximity request screen 61 may also include text requesting the provision of My Number data and mobile driver's license data, such as "Please configure the provision settings for My Number data and mobile driver's license data on your smartphone."

[0190] Once the display of the proximity request screen 61 is complete, the UI processing unit 58 notifies the information acquisition unit 57 (processor 41) of the information acquisition terminal 1 that the display of the proximity request screen 61 is complete (ST801).

[0191] When the information acquisition unit 57 receives a display completion notification, it executes device engagement processing (ST402). This establishes a communication path (NFC, BLE, or Wi-Fi) between the information acquisition terminal 1 and the user terminal 3.

[0192] When the information acquisition unit 57 determines that a communication channel has been established with the user terminal 3 (device engagement processing has been successful) (ST403), it requests to read the My Number data and performs a determination of whether or not the My Number data can be read (ST404).

[0193] In determining whether My Number data can be read, the information acquisition unit 57 first sends a My Number data reading request (ST404A) to the nearby device (user terminal 3). If the user terminal 3 that received the My Number data reading request has My Number data stored in it, the user terminal 3 sends information indicating that the My Number data can be read to the information acquisition terminal 1 (specifically, the information acquisition unit 57) (ST404B). When the information acquisition unit 57 obtains the information indicating that the My Number data can be read, it determines that the My Number data can be read (ST404C).

[0194] The information indicating that My Number data can be read may be data indicating whether or not the reading of My Number data was successful, or it may be at least a part of the My Number data itself (for example, the name, date of birth, or information on whether or not the person is 20 years of age or older included in the My Number data).

[0195] If the information acquisition unit 57 determines that it is possible to read the My Number data, it requests the UI processing unit 58 to obtain consent (ST802). When the UI processing unit 58 receives the consent request from the information processing unit, it displays the consent acquisition screen 65 and accepts input indicating consent to provide the information (ST501). Once it receives input indicating consent (ST502), the UI processing unit 58 notifies the information acquisition unit 57 that consent acquisition has been completed (ST803). As a result, the information acquisition unit 57 sends a My Number data acquisition request to the user terminal 3 (ST503) and acquires the corresponding My Number data from the nearby device (user terminal 3) (ST504).

[0196] Once the acquisition of My Number data is complete, the information acquisition unit 57 outputs the acquired information to the UI processing unit 58 (ST804), and the UI processing unit 58 displays the acquired information on the touch panel display 48. The My Number data acquired by the UI processing unit 58 is used in various services such as business applications and age and address verification (ST505).

[0197] Figure 20 shows a sequence diagram of the information acquisition process in the second embodiment, where a user terminal 3 that does not store My Number data but instead stores mobile driver's license data is in close proximity to the information acquisition terminal 1. In Figure 20, the same processes as in Figures 14 to 19 are illustrated with the same step numbers.

[0198] As in the case shown in Figure 19, when the information acquisition process is started, the UI processing unit 58 (processor 41) displays the proximity request screen 61 (ST401) and notifies the information acquisition unit 57 (processor 41) that the display of the proximity request screen 61 has been completed (ST801).

[0199] When the information acquisition unit 57 receives a display completion notification, it executes device engagement processing (ST402). This establishes a communication path (NFC or BLE) between the information acquisition terminal 1 and the user terminal 3.

[0200] When the information acquisition unit 57 determines that a communication path has been established with the user terminal 3 (device engagement processing has been successful) (ST403), it performs a determination of whether or not the minor data can be read (ST404), similar to the case shown in Figure 19. Since the nearby device (user terminal 3) does not have any minor data stored in it, the determination of whether or not the minor data can be read determines that reading the minor data has failed (ST404C).

[0201] If it is determined that reading the My Number data has failed, the information acquisition unit 57 performs a determination of whether or not the mobile driver's license data can be read (ST405).

[0202] In determining whether mobile driver's license data can be read, the information acquisition unit 57 first sends a request to read mobile driver's license data (ST405A) to the nearby device (user terminal 3). If the user terminal 3, which has received the request to read mobile driver's license data, has mobile driver's license data stored, the user terminal 3 sends information to the information acquisition terminal 1 (specifically, the information acquisition unit 57) indicating that the mobile driver's license data can be read (ST405B). When the information acquisition unit 57 obtains the information indicating that the mobile driver's license data can be read, it determines that it is possible to read the mobile driver's license data (ST405C).

[0203] If the information acquisition unit 57 determines that it is possible to read the mobile driver's license data, it requests the UI processing unit 58 to obtain consent (ST802). When the UI processing unit 58 receives the consent request from the information processing unit, it displays the consent acquisition screen 65 and accepts input indicating consent to provide the information (ST501). Once it receives input indicating consent (ST502), the UI processing unit 58 notifies the information acquisition unit 57 that consent acquisition has been completed (ST803). As a result, the information acquisition unit 57 sends a request to the user terminal 3 to acquire mobile driver's license data (ST603) and acquires the corresponding mobile driver's license data from the user terminal 3 (ST604).

[0204] Once the acquisition of mobile driver's license data is complete, the information acquisition unit 57 outputs the acquired information to the UI processing unit 58 (ST804), and the UI processing unit 58 displays the acquired information on the touch panel display 48. The mobile driver's license data acquired by the UI processing unit 58 is used in various services such as business applications and age and address verification (ST505).

[0205] Figure 21 shows a sequence diagram of the information acquisition process when the My Number Card 2A is brought close to the information acquisition terminal 1 in the second embodiment. In Figure 21, processes similar to those in Figures 14 to 20 are shown with the same step numbers.

[0206] As in the case shown in Figure 19, when the information acquisition process is started, the UI processing unit 58 (processor 41) displays the proximity request screen 61 (ST401) and notifies the information acquisition unit 57 (processor 41) that the display of the proximity request screen 61 has been completed (ST801).

[0207] When the information acquisition unit 57 receives the display completion notification, it executes the device engagement process (ST402). Because the nearby device is a My Number Card 2A (IC card 2), a communication path cannot be established between the information acquisition terminal 1 and the user terminal 3, and the information acquisition unit 57 determines that the device engagement process has failed (ST403).

[0208] If the device engagement process is determined to have failed, the information acquisition unit 57 performs a determination of whether the My Number Card can be read (ST409). Specifically, the information acquisition unit 57 first sends a My Number Card reading request to the nearby device (ST409A). The My Number Card reading request may use a command (SELECT command) that causes the device to search a predetermined folder stored in the IC chip 13 of the My Number Card 2A. Upon receiving the My Number Card reading request, the nearby device (My Number Card 2A) sends information to the information acquisition unit 57 indicating that it can be read (ST409B). Upon receiving this information indicating that it can be read, the information acquisition unit 57 determines that the My Number Card 2A can be read (reading was successful) (ST409C).

[0209] When the information acquisition unit 57 determines that the My Number Card 2A is readable, it sends a request to the nearby device to read the four basic pieces of information (ST701). When the nearby device receives the request to read the four basic pieces of information, it sends a PIN code request to the information acquisition unit 57 requesting the PIN code necessary to read the four basic pieces of information (ST901).

[0210] When the information acquisition terminal 1 receives a PIN code request from a nearby device, it executes a PIN code acquisition notification process (ST702). In the PIN code acquisition notification process, the information acquisition terminal 1 first outputs a PIN code reception request to the UI processing unit 58 (ST702A). When the UI processing unit 58 receives the PIN code reception request, it displays a PIN code input screen on the touch panel display 48 (ST702B). When a PIN code is entered into the touch panel display 48, the UI processing unit 58 notifies the information acquisition unit 57 of the entered PIN code (ST703C), and the information processing unit transmits the notified PIN code to the nearby device (My Number Card 2A).

[0211] The nearby device uses the acquired PIN code to obtain basic information and transmits it to the information acquisition terminal 1 (information acquisition unit 57) (ST902).

[0212] When the information acquisition terminal 1 (information acquisition unit 57) acquires the four basic pieces of information from a nearby device, it extracts the necessary information from the four basic pieces of information that is required for subsequent processing and deletes the information that is not necessary (ST704).

[0213] Specifically, the information acquisition unit 57 first notifies the UI processing unit 58 that it has completed acquiring the four basic pieces of information (ST704A). The UI processing unit 58 requests the information acquisition unit 57 to extract the necessary items from the four basic pieces of information that are required for subsequent processing (ST704B). Upon receiving the extraction request, the information acquisition unit 57 extracts the necessary information corresponding to the required items from the four basic pieces of information and deletes the information other than the necessary information from the four basic pieces of information (stored in memory) (ST704C). After that, the information acquisition unit 57 outputs the extracted necessary information to the UI processing unit 58 (ST704D).

[0214] When the UI processing unit 58 acquires the necessary information, it displays the acquired information on the touch panel display 48 (ST705). The necessary information acquired by the UI processing unit 58 is used in various services such as business applications and age and address verification.

[0215] Figures 22 and 23 show sequence diagrams of the information acquisition process when the driver's license 2B is brought close to the information acquisition terminal 1 in the second embodiment. In Figures 22 and 23, processes similar to those in Figures 14 to 21 are shown with the same step numbers. Figure 23 shows the flow of processes that follow the process shown in Figure 22.

[0216] As shown in Figure 22, when the information acquisition terminal 1 starts the information acquisition process, just as in Figure 21, it displays the proximity request screen 61 and executes the device engagement process (ST402). Since the nearby device is the driver's license 2B, the information acquisition terminal 1 (information acquisition unit 57) determines that the device engagement process has failed, just as in Figure 21 (ST403).

[0217] If the device engagement process is determined to have failed, the information acquisition unit 57 performs a determination of whether or not the My Number Card can be read (ST409). Since the device in close proximity to the information acquisition terminal 1 is a driver's license 2B, the information acquisition unit 57 determines that reading the My Number Card 2A has failed (cannot be read) (ST409C).

[0218] If the information acquisition unit 57 determines that it has failed to read the My Number Card 2A, it performs a determination on whether the driver's license can be read (ST411). Specifically, the information acquisition unit 57 first sends a driver's license reading request to the nearby device (ST411A). The driver's license reading request may use a command (SELECT command) that causes the device to search a predetermined folder stored in the IC chip 13 of the driver's license 2B. Upon receiving the driver's license reading request, the nearby device (driver's license 2B) sends information to the information acquisition unit 57 indicating that it can be read (ST411B). When the information acquisition unit 57 receives the information indicating that it can be read, it determines that the driver's license 2B can be read (reading was successful) (ST411C).

[0219] The processing after it is determined that the driver's license 2B can be read is the same as in the case of Figure 21. Specifically, as shown in Figure 23, the information acquisition unit 57 sends a request to read the four basic pieces of information to the nearby device (driver's license 2B) (ST701). When the nearby device receives the read request, it requests the PIN code from the information acquisition terminal 1 (ST901).

[0220] When the information acquisition terminal 1 receives a request for a PIN code from a nearby device, it performs the same processing as shown in Figure 21, acquires the PIN code, and transmits it to the nearby device (driver's license 2B) (ST702). As a result, the nearby device (driver's license 2B) transmits the basic 4 information, and the information acquisition terminal 1 acquires the basic 4 information (ST902).

[0221] When the information acquisition terminal 1 acquires the four basic pieces of information, it performs the same processing as shown in Figure 21, extracting the necessary information required for subsequent processing from the four basic pieces of information and deleting the unnecessary information (ST704), and displays the acquired necessary information on the touch panel display 48 (ST705).

[0222] <<Third Embodiment>> Figure 24 shows a flowchart of the information acquisition process executed by the information acquisition terminal 1 according to the third embodiment. As shown in Figure 24, the information acquisition process according to the third embodiment differs from that of the second embodiment in that it differs in the process related to reading My Number data and mobile driver's license data stored in the user terminal 3 (user terminal reading process), but the process related to reading the physical card (My Number card 2A or driver's license 2B) (physical card reading process) and other processes and configurations are the same. Therefore, the user terminal reading process according to the third embodiment will be described below, and the explanation of other processes and configurations will be omitted.

[0223] As shown in Figure 24, the information acquisition terminal 1 displays a proximity request screen 61 on the touch panel display 48, similar to the second embodiment (ST401), and performs device engagement processing (ST402). Subsequently, when the information acquisition terminal establishes a connection with the nearby device during the device engagement processing (i.e., the nearby device was the user terminal 3), it performs user terminal reading processing.

[0224] In the user terminal reading process, first, the information acquisition terminal 1 sends a My Number data reading request to the user terminal 3, instructing it to read the My Number data and, if successful, to send the read data. When the information acquisition terminal 1 receives the My Number data (specifically, the My Number data that the user has agreed to provide) from the user terminal 3, it determines that the reading of the My Number data was successful (Yes in ST1101) and terminates the information acquisition process.

[0225] If the information acquisition terminal 1 is unable to receive My Number data from the user terminal 3 (i.e., fails to read My Number data) (No in ST1101), the information acquisition terminal 1 sends a mobile driver's license data reading request to the user terminal 3, instructing it to read the mobile driver's license data and, if successful, to send the read data. When the information acquisition terminal 1 receives the mobile driver's license data (specifically, the mobile driver's license data that the user has agreed to provide) from the user terminal 3, it determines that it has successfully read the mobile driver's license data (Yes in ST1102) and terminates the information acquisition process.

[0226] If the information acquisition terminal 1 is unable to receive mobile driver's license data from the user terminal 3 (i.e., fails to read the mobile driver's license data) (No in ST1102), it performs error processing (ST408) and terminates the information acquisition process, similar to the second embodiment.

[0227] Next, with reference to Figures 25 to 27, the processing flow in the third embodiment, from the time the information acquisition terminal 1 acquires My Number data or mobile driver's license data from the user terminal 3, will be described in detail.

[0228] Figure 25 shows a sequence diagram of the information acquisition process when a user terminal 3 that stores My Number data is in close proximity to the information acquisition terminal 1. As shown in Figure 25, the information acquisition unit 57 performs device engagement processing (ST402), and when it determines that the device engagement processing was successful (Yes in ST403), the information acquisition unit 57 sends a My Number data read request to the user terminal 3 (ST1101A). The My Number data read request may include information related to the items of My Number data to be acquired by the user terminal 3.

[0229] When user terminal 3 receives a My Number data read request, it determines whether or not it can read My Number data from storage 33. At this time, if the My Number data read request includes information relating to items of My Number data, user terminal 3 may also determine whether or not it can read the corresponding My Number data from storage 33. In this case, since readable My Number data is stored in user terminal 3, it is determined that the My Number data can be read (ST1101B).

[0230] If the user terminal 3 determines that it can read the My Number data, it displays a consent screen 70 on the touch panel display 34. Figure 26 shows an example of the consent screen 70.

[0231] As shown in Figure 26, the consent screen 70 may include an input field 72 for identifying the items of My Number Data that the user consents to have read from the user terminal 3 and provided to the information acquisition terminal 1. In the example shown in Figure 27, a check box is used as the input field 72. In addition, the consent screen 70 may include a provide button 74 for the user to input when they consent to the provision and a cancel button 76 for the user to input when they do not consent to the provision. Alternatively, in another implementation, the consent screen 70 may not have an input field 72, and instead only display the items of information requested from the information acquisition terminal 1, with a "Consent to provision" button 74 and a "Do not consent to provision" button 76.

[0232] As shown in Figure 25, when the user terminal 3 receives input indicating consent to the provision of data on the provision consent screen 70 (ST1101D), the user terminal 3 reads the minor data of the items for which consent has been given from the storage 33 and transmits it to the information acquisition unit 57 (ST1101E).

[0233] When the information acquisition unit 57 receives My Number data from the user terminal 3, it determines that it has successfully read the My Number data and, as in the second embodiment, outputs the information (My Number data) acquired from the user terminal 3 to the UI processing unit 58 (ST804). When the UI processing unit 58 acquires My Number data from the information acquisition unit 57, it displays on the touch panel display 48 that My Number data has been acquired and information related to the acquired My Number data (ST505), and then completes the information acquisition process.

[0234] Figure 27 shows a sequence diagram of the information acquisition process in the third embodiment, when a user terminal 3, which does not store My Number data but instead stores mobile driver's license data, is in close proximity to the information acquisition terminal 1.

[0235] In this case as well, similar to the case shown in Figure 25, the information acquisition unit 57 performs device engagement processing (ST402), and if it determines that the device engagement processing was successful (Yes in ST403), the information acquisition unit 57 sends a request to read the minus data to the user terminal 3 (ST1101A).

[0236] When user terminal 3 receives a request to read My Number data, it determines that it does not have My Number data stored in storage 33 (ST1101G) and sends a notification to information acquisition unit 57 indicating that it failed to read the My Number data (ST1101H). When information acquisition unit 57 receives this notification, it determines that it failed to read the My Number data (ST1101I).

[0237] If it determines that reading the My Number data has failed, the information acquisition unit 57 performs a determination on whether or not it is possible to read the mobile driver's license data (ST1102).

[0238] Specifically, the information acquisition unit 57 first sends a request to read mobile driver's license data to the user terminal 3 (ST1102A). The request to read mobile driver's license data may include information related to the items of mobile driver's license data to be acquired by the user terminal 3.

[0239] When user terminal 3 receives a request to read mobile driver's license data, it determines that the mobile driver's license data is stored in storage 33 and can be read (ST1102B), and displays a consent screen 70 on the touch panel (ST1102C). The consent screen 70 is a screen for receiving confirmation from the user whether or not to provide the mobile driver's license data, and may be similar to the screen shown in Figure 26. If the request to read mobile driver's license data includes information related to the items of the mobile driver's license data to be acquired, user terminal 3 may set the input fields 72 displayed on the consent screen 70 based on the information related to those items.

[0240] When the user enters an indication of consent to the provision of information on the consent screen 70 (ST1102D), the user terminal 3 reads the mobile driver's license data for the items for which consent has been given from the storage 33 and transmits it to the information acquisition unit 57 (ST1102E).

[0241] When the information acquisition unit 57 receives mobile driver's license data from the user terminal 3, it determines that it has successfully read the mobile driver's license data (ST1102F), and, as in the second embodiment, outputs the information (mobile driver's license data) acquired from the user terminal 3 to the UI processing unit 58 (ST804). When the UI processing unit 58 acquires the mobile driver's license data from the information acquisition unit 57, it displays on the touch panel display 48 that it has acquired the mobile driver's license data and information related to the acquired mobile driver's license data (ST505), and then completes the information acquisition process.

[0242] <<Fourth Embodiment>> Figure 28 shows a flowchart of the information acquisition process performed by the information acquisition terminal 1 according to the fourth embodiment. As shown in Figure 28, the information acquisition process according to the fourth embodiment differs from that of the second embodiment in that it differs in the process related to reading My Number data and mobile driver's license data stored in the user terminal 3 (user terminal reading process), but the process related to reading physical cards (My Number card and driver's license) (physical card reading process) and other processes and configurations are the same. Therefore, the user terminal reading process according to the fourth embodiment will be described below, and the explanation of other processes and configurations will be omitted.

[0243] As shown in Figure 28, the information acquisition terminal 1 displays a proximity request screen 61 on the touch panel display 48, similar to the second embodiment (ST401), and performs device engagement processing (ST402). Subsequently, when the information acquisition terminal establishes a connection with the nearby device during the device engagement processing (i.e., the nearby device was the user terminal 3), it performs user terminal reading processing.

[0244] In the user terminal reading process, the information acquisition terminal 1 sends a personal information reading request to the user terminal 3, instructing the user terminal 3 to read personal information and send it back to the information acquisition terminal 1 (ST1201). If the storage 33 has My Number data stored in it, when the user terminal 3 receives the personal information reading request, it retrieves (reads) the My Number data from the storage 33 and sends it back to the information acquisition terminal 1. If the storage 33 does not have My Number data stored in it but has mobile driver's license data stored in it, when the user terminal 3 receives the personal information reading request, it retrieves (reads) the mobile driver's license data and sends it back to the information acquisition terminal 1. If the user terminal 3 does not have either My Number data or mobile driver's license data, it notifies the information acquisition terminal 1 that it does not have personal information.

[0245] If the information acquisition terminal 1 receives personal information (My Number data) or mobile driver's license data from the user terminal 3, that is, if the user terminal 3 has successfully read the personal information (Yes in ST1201), the information acquisition terminal 1 terminates the information acquisition process. If the information acquisition terminal 1 is notified by the user terminal 3 that it does not possess either My Number data or mobile driver's license data, that is, if the user terminal 3 has failed to read the personal information (No in ST1201), the information acquisition terminal 1 executes the same error processing (ST408) as in the first embodiment and terminates the information acquisition process.

[0246] Next, with reference to Figures 29 and 30, the process flow of how the information acquisition terminal 1 acquires personal information in the fourth embodiment will be described in detail.

[0247] Figure 29 shows a sequence diagram of the information acquisition process in the fourth embodiment when a user terminal 3 storing My Number data is in close proximity to the information acquisition terminal 1. As shown in Figure 29, the information acquisition unit 57 performs device engagement processing (ST402), and when it determines that the device engagement processing was successful (Yes in ST403), the information acquisition unit 57 sends a personal information read request to the user terminal 3 (ST1201A). The personal information read request may include information relating to items of personal information (My Number data and mobile driver's license data) to be acquired by the user terminal 3.

[0248] When user terminal 3 receives a request to read personal information, the My Number data is stored in storage 33, and a My Number data readability determination is performed to determine whether or not it can be read (ST1201B). In the example shown in Figure 29, the My Number data is stored in user terminal 3, and it is determined that it can be read. Subsequently, user terminal 3 displays a provision consent screen 70 on the touch panel display 34, similar to that in Figure 26 (ST1201C). At this time, if the request to read personal information includes information related to an item, user terminal 3 should set the input field 72 displayed on the provision consent screen 70 based on the information related to that item. When user terminal 3 accepts input indicating consent to provision on the provision consent screen 70, that is, determines that consent to provision has been given (ST1201D), it transmits the read personal information (My Number data) to information acquisition terminal 1 via the information acquisition unit 57 (ST1201E).

[0249] When the information acquisition unit 57 receives personal information (My Number data) from the user terminal 3, it determines that it has successfully read the personal information (ST1201F) and, as in the third embodiment, outputs the information (My Number data) acquired from the user terminal 3 to the UI processing unit 58 (ST804). When the UI processing unit 58 acquires My Number data from the information acquisition unit 57, it displays on the touch panel display 48 that personal information has been acquired and information related to the acquired personal information (ST505), and then completes the information acquisition process.

[0250] Figure 30 shows a sequence diagram of the information acquisition process in the fourth embodiment, when a user terminal 3, which does not store My Number data but instead stores mobile driver's license data, is in close proximity to the information acquisition terminal 1.

[0251] In this case as well, similar to the case shown in Figure 29, the information acquisition unit 57 performs device engagement processing (ST402), and if it determines that the device engagement processing was successful (Yes in ST403), the information acquisition unit 57 sends a request to read personal information to the user terminal 3 (ST1201A).

[0252] When user terminal 3 receives a request to read personal information, the My Number data is stored in storage 33, and a My Number data readability determination is performed to determine whether or not it can be read (ST1201B). In the example shown in Figure 30, since the My Number data is not stored in user terminal 3, it is determined that it cannot be read.

[0253] Since it is determined that My Number data is not stored, the user terminal 3 performs a mobile driver's license data readability determination to determine whether the mobile driver's license data is stored in the storage 33 and can be read (ST1201G). In the example shown in Figure 30, it is determined that the mobile driver's license data is stored in the user terminal 3 and can be read. Subsequently, the user terminal 3 displays a consent screen 70 on the touch panel display 34 similar to that in Figure 26 (ST1201C). At this time, if the personal information reading request includes information related to an item, the user terminal 3 should set the input field 72 displayed on the consent screen 70 based on the information related to that item. The user terminal 3 accepts input indicating consent to the provision on the consent screen 70 and determines that consent to the provision has been given (ST1201D), and then transmits the read personal information (mobile driver's license data) to the information acquisition terminal 1 via the information acquisition unit 57 (ST1201E).

[0254] When the information acquisition unit 57 receives personal information (mobile driver's license data) from the user terminal 3, it determines that it has successfully read the personal information (ST1201F) and, as in the third embodiment, outputs the information acquired from the user terminal 3 (mobile driver's license data) to the UI processing unit 58 (ST804). When the UI processing unit 58 acquires My Number data from the information acquisition unit 57, it displays on the touch panel display 48 that personal information has been acquired and information related to the acquired personal information (ST505), and then completes the information acquisition process.

[0255] As illustrated in Figure 31, in the second to fourth embodiments, the information acquisition process may be configured such that, after error handling (ST410, 413), the information acquisition terminal 1 does not terminate the information acquisition process but resumes from displaying the proximity request screen 61 (ST401).

[0256] Furthermore, in the second and third embodiments, when it was determined that the mobile driver's license could not be read (No in ST406), the system was configured to perform error processing (ST408). However, as illustrated in Figure 32, instead of error processing, the system may be configured to determine whether the My Number Card can be read (execute step ST409). In that case as well, as illustrated in Figure 33, after error processing (ST413), the information acquisition terminal 1 may be configured to resume from displaying the proximity request screen 61 (ST401) without ending the information acquisition process.

[0257] In the above embodiment, examples were given where the digital identity data is a My Number Card 2A or a driver's license 2B. However, the digital identity data may also be digital residence card data or digital passport data (which is internationally standardized by the International Civil Aviation Organization ICAO and is also called a Digital Transport Certificate). Furthermore, in the above embodiment, examples were given where the physical card is a My Number Card or a driver's license. However, the physical card may also be a residence card or an IC passport.

[0258] As described above, embodiments have been explained as examples of the technology disclosed in this application. However, the technology in this disclosure is not limited to these embodiments and can be applied to embodiments that have been modified, replaced, added, or omitted. Furthermore, it is possible to create new embodiments by combining the components described in the above embodiments.

[0259] The information acquisition terminal, information acquisition method, and information acquisition program according to the present invention are useful as information acquisition terminals, information acquisition methods, and information acquisition programs that can acquire information from a device, regardless of whether the nearby device is an IC card or a user terminal.

[0260] 1: Information acquisition terminal 1A: Payment terminal 1B: Check-in terminal 1C: ATM terminal 2: IC card 2A: My Number card 2B: Driver's license 3: User terminal 3A: Smartphone 3B: Tablet terminal 3C: Smartwatch 10: Check-in system 11: Operator server 12: Network 13: IC chip 21: Processor 22: Memory 23: Antenna 24: Power supply module 25: Security module 31: Processor 32: Memory 33: Storage 34: Touch panel display 35: NFC module 36: BLE module 41: Processor 42: Memory 43: Storage 44: Display device 45: Input device 46: NFC module (communication device, example of first communication device) 47 :BLE module (communication device, example of a second communication device) 48: Touch panel display 51: Short-range communication unit 52: BLE communication unit 53: Display unit 54: Input unit 55: Storage unit 56: Control unit 57: Information acquisition unit 58: UI processing unit 61: Proximity request screen 61A: Text 62: Consent / verification number acquisition screen 62A: Input field 62B: Consent button 62C: Complete button 63: Completion notification screen 63A: Text 64: Failure notification screen 64A: Text 65: Consent acquisition screen 65A: Consent button 65B: Complete button 70: Provision consent screen 72: Input field 74: Provision button 76: Cancel button S: Service system

Claims

1. An information acquisition terminal for acquiring personal information from an IC card and a user terminal, respectively, which store personal information, comprising: a communication device for short-range communication with the IC card and the user terminal; and a processor that communicates with a nearby device via the communication device, determines whether it is the IC card or the user terminal, performs corresponding communication based on the determination result, and acquires the personal information from the device, wherein the processor transmits a read request from the communication device to the nearby device requesting the reading of specific area information stored in the IC card, determines that the device is the IC card when the reading of the specific area information is successful, and determines that the device is the user terminal when the reading of the specific area information fails.

2. The information acquisition terminal according to claim 1, wherein the communication device includes a first communication device for communicating with the IC card and a second communication device for communicating with the user terminal, and the processor acquires the personal information from the device via the first communication device when it has succeeded in acquiring the specific area information, and acquires the personal information from the device via the second communication device when it has failed to acquire the specific area information.

3. The information acquisition terminal according to claim 1, wherein the specified area information is the number of remaining reads until the reading of the IC card is prohibited.

4. The information acquisition terminal according to claim 1, wherein the personal information includes at least one of the four basic pieces of information, which consist of the name, address, date of birth, and gender of the corresponding individual.

5. An information acquisition program for acquiring personal information from an IC card and a user terminal, respectively, which store personal information, the program being executed by an information acquisition terminal comprising: a communication device for short-range communication with the IC card and the user terminal; and a processor that communicates with a nearby device via the communication device, determines whether it is the IC card or the user terminal, performs corresponding communication based on the determination result, and acquires the personal information from the device, wherein the processor transmits a read request from the communication device to the nearby device requesting the reading of specific area information stored in the IC card; determines that the device is the IC card when the reading of the specific area information is successful; and determines that the device is the user terminal when the reading of the specific area information fails.

6. An information acquisition method for acquiring personal information from an IC card and a user terminal, respectively, which store the personal information, the method being executed by an information acquisition terminal comprising: a communication device for short-range communication with the IC card and the user terminal; and a processor that communicates with a nearby device via the communication device, determines whether it is the IC card or the user terminal, performs corresponding communication based on the determination result, and acquires the personal information from the device, wherein the processor transmits a read request from the communication device to the nearby device requesting the reading of specific area information stored in the IC card; determines that the device is the IC card when the reading of the specific area information is successful; and determines that the device is the user terminal when the reading of the specific area information fails.

Images