Terminal device, person authentication system, and person authentication method

Abstract

This invention provides a highly secure and convenient technique for personal authentication via a portable terminal. The terminal device (200) of this invention includes: a positioning unit (271) that measures the position of the terminal device (200) at predetermined time intervals and accumulates the measurement results as position information; a movement history generation unit (272) that generates movement history using the position information for a predetermined period and stores it as movement history information; a registration processing unit (276) that sends the movement history information to a personal authentication device for registration; and an authentication request unit (279) that uses the movement history information sent by the registration processing unit (276) to the personal authentication device (310) to request authentication from the personal authentication device (310).

Description

Technical Field

[0001] This invention relates to personal authentication technology. In particular, it relates to a technology for personal authentication using historical information about a user collected from a user-owned terminal. Background Technology

[0002] There are technologies that use location information obtainable via a portable terminal for identity authentication. For example, Patent Document 1 discloses a technology that "receives the current location information of a user's portable communication device and collects information about the device's movement history. Then, it generates a question about the content of that history and prompts the user. It compares the answer received from the user with the historical content, and if the consistency between the two is confirmed, it determines that the user is the person in question (excerpt from the abstract)."

[0003] Existing technical documents

[0004] Patent documents

[0005] Patent Document 1: Japanese Patent Application Publication No. 2014-149811 Summary of the Invention

[0006] The problem that the invention aims to solve

[0007] In the technology disclosed in Patent Document 1, a method is used to verify whether the mobile history information obtained from the terminal belongs to the user. This method involves the system generating a question and the user answering it. Because the credentials used for authentication change automatically, both convenience and security are high. However, selecting an answer requires button operation, which is somewhat inconvenient for the user.

[0008] The present invention is based on the above circumstances and aims to provide a technology that is both highly secure and convenient for personal authentication via a portable terminal.

[0009] Technical solutions for solving the problem

[0010] To address the aforementioned issues, the present invention provides a terminal device, characterized in that it comprises: a positioning unit that measures the location of the terminal device at predetermined time intervals and accumulates the measurement results as location information; a movement history generation unit that generates movement history using the location information within a predetermined period and stores it as movement history information; a registration processing unit that sends the movement history information to a personal authentication device for registration; and an authentication request unit that uses the movement history information already sent to the personal authentication device by the registration processing unit to request authentication from the personal authentication device.

[0011] Furthermore, the present invention provides a personal authentication system comprising a terminal device, an authentication interface device, and a personal authentication device, characterized in that: the terminal device comprises: a positioning unit that measures the location of the terminal device at predetermined time intervals and accumulates the measurement results as location information; a movement history generation unit that generates movement history using the location information within a predetermined period and stores it as movement history information; a registration processing unit that sends the movement history information to the personal authentication device for registration; and an authentication request unit that uses the movement history information already sent to the personal authentication device by the registration processing unit to make an authentication request to the personal authentication device via the authentication interface device, wherein the personal authentication device comprises: a storage processing unit for storing the movement history information sent from the terminal device; and an authentication unit that, upon receiving the authentication request from the terminal device via the authentication interface device, performs authentication by determining whether the movement history included in the authentication request has been stored by the storage processing unit, and returns an authentication result.

[0012] This invention provides a method for personal authentication in a personal authentication system comprising a terminal device, an authentication interface device, and a personal authentication device. The method includes: an initial registration step, in which mobile history information is stored in the terminal device and sent to the personal authentication device, whereby the mobile history information is stored as authentication information; an authentication step, in which the mobile history information is sent as an authentication request to the personal authentication device via the authentication interface device, and the authentication information is used in the personal authentication device to accept authentication; and an authentication information update step, in which newly generated mobile history information is sent to the personal authentication device via the authentication interface device, and the mobile history information replaces the authentication information stored in the personal authentication device.

[0013] Invention Effects

[0014] According to the present invention, a technology that provides high security and convenience in personal authentication via a portable terminal can be provided. Other issues, structures, and effects beyond those described above will be explained through the following description of embodiments. Attached Figure Description

[0015] Figure 1 This is an overall structural diagram of the self-authentication system in the first implementation method.

[0016] Figure 2 This is a hardware structure diagram of the terminal device according to the first embodiment.

[0017] Figure 3 This is a functional block diagram of the terminal device in the first embodiment.

[0018] Figure 4(a) and (b) are respectively the functional block diagram and hardware structure diagram of the personal authentication device of the first embodiment, and (c) is the hardware structure diagram of the shop equipment of the first embodiment.

[0019] Figure 5 (a) is a flowchart of the self-authentication process of the first embodiment, and (b) is an explanatory diagram for illustrating the initial registration process of the first embodiment.

[0020] Figure 6 (a) is an illustration of the store authentication process of the first embodiment, and (b) is an explanatory diagram for illustrating the authentication information update process of the first embodiment.

[0021] Figure 7 (a) is the registration process of the first embodiment, and (b) is a flowchart of the store authentication process and authentication information update process of the first embodiment.

[0022] Figure 8 (a) to (c) are explanatory diagrams for illustrating the data flow of the initial registration process, store authentication process, and authentication information update process in the first embodiment.

[0023] Figure 9 Figures (a) to (d) are explanatory diagrams for illustrating the self-authentication process of the first embodiment.

[0024] Figure 10 (a) is an explanatory diagram of the data structure of the terminal ID in the first embodiment, (b) is an explanatory diagram of the movement history in the first embodiment, and (c) is an explanatory diagram of the biometric information in the first embodiment.

[0025] Figure 11 Figures (a) to (d) are explanatory diagrams for illustrating the motion history generation process using the feature information of the first embodiment.

[0026] Figure 12 (a) and (b) are respectively a flowchart and a timing diagram of the mobile history generation process in the first embodiment.

[0027] Figure 13 This is an overall structural diagram of the self-authentication system in the second implementation method.

[0028] Figure 14 (a) and (b) are respectively the functional modules and hardware structure diagrams of the personal authentication device in the second embodiment.

[0029] Figure 15 This is an explanatory diagram illustrating the data flow during authentication in the second embodiment.

[0030] Figure 16(a) is a functional block diagram of the terminal device of the third embodiment, and (b) is a functional block diagram of the personal authentication device of the third embodiment.

[0031] Figure 17 (a) is a diagram illustrating the reference information acquisition process of the third embodiment, and (b) is an explanatory diagram illustrating the authentication process.

[0032] Figure 18 This is a flowchart of the authentication process in the third implementation method. Detailed Implementation

[0033] Hereinafter, embodiments of the present invention will be described with reference to the accompanying drawings. In this specification, unless otherwise specified, parts having the same function will be given the same reference numerals, and repeated descriptions will be omitted.

[0034] <<First Implementation>>

[0035] The first embodiment of the present invention will be described. In the personal authentication system of this embodiment, personal authentication is performed using information from a terminal device such as a mobile terminal or wearable terminal held by the user. Specifically, the user's location information is collected within a specified period, and mobile history information (hereinafter referred to as mobile history) is generated based on the collected information and shared with the personal authentication device (server). Then, the shared mobile history is used as authentication information for authentication. At this time, the mobile history is generated based on the location information obtained during the period when the legitimate user holds the terminal device. In addition, the authentication information is updated at a specified time.

[0036] First, let me explain the overall structure of the self-authentication system 100 in this embodiment. Figure 1 This is an overall structural diagram of the self-authentication system 100 of this embodiment. The self-authentication system 100 includes a terminal device 200 and a provider system 300.

[0037] The provider system 300 includes a personal authentication device 310 for the provider, store equipment 330 in each store, and an internal network (N / W) 320 for data transmission and reception between the personal authentication device 310 and the store equipment 330. Additionally, although not shown, it may also include a settlement server, etc.

[0038] Figure 1 The example shown illustrates a scenario where store equipment 330 includes both store equipment 331 and store equipment 332, but the number of store equipment 330s is not limited to this. Furthermore, in the following description, unless otherwise specified, store equipment 330 will be used to represent each of store equipment 331 and 332.

[0039] Terminal device 200 and personal authentication device 310 can directly send and receive data via network 101.

[0040] [Hardware Structure of Terminal Devices]

[0041] First, let's explain the terminal device 200. Figure 2 The figure shows the hardware structure of terminal device 200. As shown in this figure, terminal device 200 has a CPU (Central Processing Unit) 201, a system bus 202, a storage device 210, a communicator 220, an expansion I / F 227, an operator 230, a video processor 240, an audio processor 250, and a sensor 260.

[0042] CPU 201 is a microprocessor unit that controls the terminal device 200 as a whole. System bus 202 is a data communication path used for data transmission and reception between CPU 201 and various action modules within the terminal device 200.

[0043] The storage device 210 has a ROM (Read Only Memory) 211, a RAM (Random Access Memory) 212 and an external memory interface (I / F) 213.

[0044] ROM 211 is a memory that stores basic operating programs such as the operating system and other operating programs. ROM 211 can be, for example, a rewritable ROM such as EEPROM (Electrically Erasable and Programmable Read Only Memory) or flash memory ROM. It also stores the operating settings of the aforementioned programs, as well as various programs and data required to implement the functions of this embodiment.

[0045] The external memory I / F213 is an interface for sending and receiving data by connecting to a memory card or other memory media.

[0046] RAM212 is the working area for executing basic action programs and other action programs.

[0047] ROM211 and RAM212 can also be integrated with CPU201.

[0048] Furthermore, the various operating programs stored in ROM211 can be updated and have their functions expanded, for example, by downloading them from various distribution servers on the network.

[0049] The communicator 220 includes a LAN (Local Area Network) communicator 221, a telephone network communicator 222, and an inter-terminal communicator 223.

[0050] The LAN communicator 221 connects to the network 101 via an access point (AP) device using a wireless connection such as Wi-Fi (registered trademark) to send and receive data with other devices on the network 101.

[0051] Telephone network communicator 222 performs voice calls and data transmission and reception through wireless communication with the base station of the mobile phone communication network.

[0052] Inter-terminal communicator 223 is an I / F (inter-device communication unit) that enables communication between terminal device 200 and store device 330. Communication methods used include, for example, Near Field Communication (NFC) and Bluetooth. NFC enables bidirectional communication between devices equipped with NFC chips over extremely short distances of a few centimeters to about one meter. For example, it can be used for contactless IC chip services such as electronic payment in terminal device 200. Bluetooth enables simple information exchange between information devices over distances of several meters to tens of meters using radio signals.

[0053] LAN communicator 221, telephone network communicator 222, and inter-terminal communicator 223 each have encoding and decoding circuits, antennas, etc. Additionally, communicator 220 may also include a communicator for infrared communication or other communicators.

[0054] The extended I / F227 is an interface group used to expand the functionality of the terminal device 200. In this embodiment, it includes video / audio I / F, USB (Universal Serial Bus) I / F, etc. The video / audio I / F handles inputting video / audio signals from external video / audio output devices and outputting video / audio signals to external video / audio input devices. The USB I / F connects to other devices such as a PC (Personal Computer) for data transmission and reception. It can also connect to a keyboard or other USB devices.

[0055] The operator 230 accepts input of operation instructions for the terminal device 200. In this embodiment, it has a touch panel arranged overlapping the display 241 and operation buttons with push-button switches. Alternatively, either one may be used. Alternatively, the terminal device 200 may be operated using a keyboard or the like connected to the expansion I / F 227. Alternatively, the terminal device 200 may be operated using another device connected via wired or wireless communication. Furthermore, the touch panel function may also be provided by the display 241.

[0056] The video processor 240 includes a display 241, an image signal processor 242, and a camera 243.

[0057] The display 241 is a display device such as an LCD panel, which displays image data processed by the image signal processor 242 and provides it to the user of the terminal device 200. The image signal processor 242 has a video RAM (not shown) and drives the display 241 based on the image data input to the video RAM. In addition, the image signal processor 242 performs format conversion, menu processing, and overlay processing of other OSD (On-Screen Display) signals as needed. The camera 243 is a shooting device that uses electronic devices such as CCD (Charge-Coupled Device) or CMOS (Complementary Metal Oxide Semiconductor) sensors to convert light input from a lens into electrical signals and acquire image data of the surroundings or objects.

[0058] The audio processor 250 includes a speaker 251, a sound signal processor 252, and a microphone 253. The speaker 251 provides the user of the terminal device 200 with the sound signal processed by the sound signal processor 252. The microphone 253 converts the user's voice, etc., into sound data and inputs it.

[0059] Sensor 260 is a sensor group used to detect the status of terminal device 200. In this embodiment, it includes, for example, a GPS (Global Positioning System) receiver 261, a gyroscope sensor 262, a geomagnetic sensor 263, an accelerometer 264, an illuminance sensor 265, a proximity sensor 266, and a bio-information sensor 267.

[0060] GPS receiver 261 receives signals from GPS satellites and other positioning satellites to calculate location information. Accelerometer 264 detects the acceleration of terminal device 200. In this embodiment, the acceleration along the x, y, and z axes of the device coordinate system set in terminal device 200 is detected. The detected values ​​are in units of [G] based on gravitational acceleration (1.0G is approximately 9.8 m / s²). 2 Bio-information sensors 267, for example, detect bio-information of the user 209 such as pulse wave and heart rate.

[0061] These sensor sets are used to detect the position, tilt, orientation, movement, ambient brightness, and biometric information of the user 209, etc., of the terminal device 200. Additionally, the terminal device 200 may also include pressure sensors such as barometric pressure sensors and other sensors. Furthermore, as mentioned above, location information is acquired by the GPS receiver 261. However, in locations where GPS radio signals are difficult to access, location information can also be acquired by the LAN communicator 221 using a Wi-Fi access point, or similarly by the telephone network communicator 222 using a method that utilizes the location information of a base station and the transmission delay of telephone communication signals. Furthermore, not all of these sensor sets may be included.

[0062] in addition, Figure 2 The illustrated terminal device 200 includes various structures that are not essential to this embodiment, and the absence of these structures will not impair the effectiveness of this embodiment. Furthermore, structures not shown, such as digital broadcast receiving functionality or electronic currency settlement functionality, can be added.

[0063] [Functional Structure of Terminal Equipment]

[0064] Next, the functional structure of the terminal device 200 in this embodiment will be described. Here, the description will mainly focus on the function of the personal authentication processing in this embodiment.

[0065] Figure 3 This is a functional block diagram of the terminal device 200 according to this embodiment. The terminal device 200 of this embodiment includes a location measurement unit 271, a movement history generation unit 272, a comparison unit 273, a feature information collection unit 274, a communication unit 275, a registration processing unit 276, and an authentication request unit 279. Additionally, it includes a location information storage unit 281, a movement history storage unit 282, a reference feature information storage unit 283, and a terminal ID storage unit 284, which are used by these units to perform processing or to store data obtained as processing results.

[0066] The positioning unit 271 processes the signal from the sensor 260 and calculates the location information of the terminal device 200. The calculated location information is stored in the location information storage unit 281. The location information is stored, for example, in association with the time when the signal from the sensor 260 is acquired. In this embodiment, for example, the location information received from the GPS receiver 261, which is the sensor 260, is directly stored in the location information storage unit 281. The location information is stored at predetermined time intervals.

[0067] The feature information collection unit 274 collects the signal from the sensor 260 as feature information for the user 209 and transmits it to the comparison unit 273. Furthermore, as an initial processing step described later, feature information is collected within a specified period as reference feature information for comparison, according to the instructions from the user 209, and stored in the reference feature information storage unit 283. In this embodiment, for example, information calculated based on the acceleration detected by the accelerometer 264 is used as feature information. Alternatively, pulse waves, heart rate, etc., detected by the bio-information sensor 267 may also be used.

[0068] When the comparison unit 273 receives feature information from the feature information collection unit 274, it compares it with the reference feature information storage unit 283 and outputs the comparison result to the mobile history generation unit 272.

[0069] The movement history generation unit 272 generates movement history using the location information stored in the location information storage unit 281. The movement history information is generated synchronously with the timing of receiving a result indicating a successful comparison from the comparison unit 273. Details of the generation will be described later. The generated movement history is stored in the movement history storage unit 282.

[0070] The communication unit 275 transmits and receives data with external devices via the communicator 220. In this embodiment, at a predetermined time, a combination of the mobile history stored in the mobile history storage unit 282 and the terminal identification information (terminal ID) stored in the terminal ID storage unit 284 is sent as authentication information. Additionally, authentication results and other information are received from external sources. Furthermore, the terminal ID is unique identification information for each terminal device 200 and is pre-assigned to each terminal device 200.

[0071] In this embodiment, the authentication information can be sent to the personal authentication device 310 for registration or for authentication. When the authentication information is sent for registration, the registration processing unit 276 notifies the communication unit 275 of this message.

[0072] Upon receiving notification, the communication unit 275 generates header information in a manner that confirms the transmission is for registration purposes, and appends it to the transmission data. Thereafter, the authentication information transmitted for registration purposes is referred to as registration authentication information. Furthermore, the registration processing unit 276 determines whether the transmission is for registration purposes based on the transmission timing or on instructions from the user 209 via the operator 230 or display 241.

[0073] Furthermore, the registration processing unit 276 may notify the communications unit 275 of the message if the transmission is not for registration purposes but for authentication purposes, or it may choose not to make any notification.

[0074] The authentication request unit 279 uses the mobile history stored in the mobile history storage unit 282 to make an authentication request to the personal authentication device 310 via the store device 330. The authentication request is executed, for example, when inter-terminal communication with the store device 330 is initiated.

[0075] These functions are implemented by the CPU 201 loading a program pre-saved in ROM 211 into RAM 212 and executing it. Additionally, a location information storage unit 281, a movement history storage unit 282, a reference feature information storage unit 283, and a terminal ID storage unit 284 are provided in, for example, ROM 211 or external memory. Furthermore, data required for each function's execution, intermediate data generated during execution, and data generated as a result of execution are also stored in ROM 211 or external memory.

[0076] [Personal Authentication Device]

[0077] Next, I will explain the hardware structure and functional modules of my authentication device 310.

[0078] Figure 4 Figure (a) is a functional block diagram of the self-authentication device 310. As shown in this figure, the self-authentication device 310 includes a communication unit 311, a storage and processing unit 312, and an authentication unit 313. In addition, it also includes an authentication information storage unit 314 for storing authentication information.

[0079] Figure 4 (b) is a hardware structure diagram of the self-authentication device 310. The self-authentication device 310 is an information processing device having a CPU 321, a memory 322, a storage device 323, and a communicator 324. In this embodiment, for example, a LAN communicator 325 is used as the communicator 324. The LAN communicator 325 enables communication via the internal network 320 and the network 101.

[0080] The communication unit 311 controls the transmission and reception of data with external devices via the communicator 324. Furthermore, in this embodiment, it determines whether the received authentication information is registration authentication information. This determination is made using the header information of the received data. If it is determined to be registration authentication information, it is transmitted to the storage processing unit 312. Otherwise, it is transmitted to the authentication unit 313.

[0081] The storage and processing unit 312 stores the registration and authentication information sent from each terminal device 200, namely the combination of mobile history and terminal ID, as authentication information in the authentication information storage unit 314.

[0082] When the authentication unit 313 receives an authentication request from the store device 330 via the communication unit 311, it performs authentication and replies with an authentication result to the store device 330 that made the request. In this embodiment, the authentication request is received from the store device 330 as a combination of mobile history and terminal ID. The authentication unit 313 compares the received combination of mobile history and terminal ID with the authentication information stored in the authentication information storage unit 314 and performs authentication. If both match, the authentication is considered successful; if they do not match, the authentication is considered unsuccessful.

[0083] The functions of the personal authentication device 310 are implemented by the CPU 321 loading the program stored in the storage device 323 into the memory 322 and executing it. In addition, the authentication information storage unit 314 is provided in the storage device 323, for example.

[0084] [Shop Equipment]

[0085] Next, the shop equipment 330 in the shop of this embodiment will be described. When the shop equipment 330 receives authentication information as an authentication request from the terminal device 200, it sends it to the personal authentication device 310 and accepts authentication. The shop equipment 330, as... Figure 4 As shown in (c), it comprises an information processing device having a CPU 341, a memory 342, a storage device 343, and a communicator 344. The communicator 344 includes a LAN communicator 345 and an inter-terminal communicator 346.

[0086] The LAN communicator 340 enables communication with the personal authentication device 310 via the internal network 320. Additionally, the inter-terminal communicator 346 enables the sending and receiving of data with the terminal device 200.

[0087] [Personal verification process]

[0088] Next, the process of personal authentication in this embodiment will be explained. Figure 5 (a) is a schematic diagram of the personal authentication process in this embodiment.

[0089] As shown in this figure, the initial registration process is performed during the user authentication process (step S1001). Afterwards, authentication is performed at the store, etc., via the store device 330 (step S1002), and authentication is accepted. During the store authentication process, if authentication is successful (step S1003; Yes), an authentication information update process is performed to update the authentication information (step S1004). Conversely, if authentication fails in step S1003, for example, the terminal device 200 notifies the user 209 of this message, and the process ends. Each process will be described in detail below.

[0090] Initial registration process such as Figure 5Figure (b) shows the process of registering authentication information from terminal device 200 to personal authentication device 310. The initial registration process is performed before the authentication process. As shown in this figure, firstly, in terminal device 200, the mobility history generation unit 272 generates mobility history 5a based on the location information 4a stored in the location information storage unit 281. Then, according to the instruction of registration processing unit 276, the generated mobility history 5a and the terminal ID 1a are combined as registration authentication information and sent to personal authentication device 310 via network 101.

[0091] In the personal authentication device 310 that has received the registration and authentication information, the storage and processing unit 312 registers the mobile history 5a and the terminal ID 1a as authentication information to the authentication information storage unit 314.

[0092] Furthermore, once the initial registration is completed, the positioning unit 271 will continue to collect location information as long as the user 209 does not give a termination instruction.

[0093] Store certification processing, such as Figure 6 As shown in (a), this is the authentication process for user 209 in a store device 330 (331) in a store or similar establishment. User 209 requests authentication by presenting a terminal device 200, which has undergone initial registration, to the store device 331 or similar establishment. Here, the authentication request unit 279 sends the mobile history 5a and terminal ID 1a as authentication information to the store device 331. The transmission is performed, for example, using inter-terminal communication such as near-field communication.

[0094] When the communicator 344 of the store device 331 receives authentication information, it transmits it to the personal authentication device 310 via the internal network 320. Then, in the personal authentication device 310, the authentication unit 313 performs authentication using the authentication information registered in the authentication information storage unit 314 and returns a result to the store device 331. In addition, the store device 331 replies with the authentication result to the sending terminal device 200.

[0095] The authentication information update process involves updating the authentication information stored in the personal authentication device 310 upon successful authentication via the store device 331. Here, a new movement history 5b is generated using the previously collected location information 4b. Then, along with the terminal ID 1a, it is sent via the store device 331 as new registration authentication information to the personal authentication device 310, thus updating the authentication information.

[0096] like Figure 6As shown in (b), firstly, in terminal device 200, the mobile history generation unit 272 generates mobile history 5b based on the location information 4b stored in the location information storage unit 281. Then, according to the instruction of the registration processing unit 276, the generated mobile history 5b and the terminal ID 1a are combined as new registration authentication information and sent to the store device 331. The sending is performed, for example, through inter-terminal communication.

[0097] In addition, as described above, if a new mobile history 5b is sent via the same store device 330 after successful authentication, the registration processing unit 276 determines that the transmission is for registration purposes and notifies the communications unit 275.

[0098] The store device 331 will send the new registration and authentication information received to the personal authentication device 310 via the internal network 320.

[0099] In the personal authentication device 310 that receives the registered authentication information, the storage processing unit 312 updates the authentication information by registering the mobile history 5b as authentication information associated with the terminal ID 1a to the authentication information storage unit 314. For example, the storage processing unit 312 retrieves the authentication information registered with the same terminal ID 1a and replaces the retrieved authentication information with the newly sent authentication information.

[0100] exist Figure 7 (a) shows the processing flow for the initial registration process.

[0101] The positioning unit 271 collects location information 4a within a specified period (step S1101) and stores it in the location information storage unit 281.

[0102] Then, the movement history generation unit 272 generates movement history 5a based on the generated location information 4a (step S1102) and stores it in the movement history storage unit 282.

[0103] Following the instructions from user 209, registration processing unit 276 instructs communication unit 275 to send mobile history 5a and terminal ID 1a together as registration authentication information to personal authentication device 310 (step S1103). At this time, communication unit 275 adds header information indicating that it is registration authentication information to the transmitted data.

[0104] In the personal authentication device 310, the storage processing unit 312 stores the received registration authentication information (mobility history 5a and terminal ID 1a) in the authentication information storage unit 314 (step S1201).

[0105] exist Figure 7 (b) shows the processing flow for store authentication and authentication information update.

[0106] As described above, the positioning unit 271 continues to collect position information 4b (step S1301).

[0107] Independent of the collection of location information 4b, when user 209 arrives at the store, authentication request unit 279 sends authentication information (mobility history 5a and terminal ID 1a) from terminal device 200 to store device 330 (step S1302). Here, the mobile history 5a sent is data stored in mobile history storage unit 282 during initial registration. Furthermore, the sending is performed, for example, using inter-terminal communicator 223.

[0108] In the store device 330, authentication information (mobility history 5a and terminal ID 1a) is received via the inter-terminal communicator 346 and sent to the personal authentication device 310 via the LAN communicator 345 (step S1401). The transmission from the store device 330 to the personal authentication device 310 is, for example, via the internal network 320.

[0109] When the authentication information (mobile history 5a and terminal ID 1a) is received from the store device 330 (step S1501), the authentication unit 313 in the personal authentication device 310 compares the authentication information stored in the authentication information storage unit 314 and performs authentication (step S1502).

[0110] Then, the authentication result is sent to the store device 330 via the communication unit 311 (step S1503). The sent authentication result is either authentication success or authentication failure.

[0111] When the authentication result is received, the authentication result is sent to the terminal device in the store device 330 (step S1402).

[0112] Terminal device 200 receives the authentication result (step S1303). Here, if authentication is successful, the process proceeds to the settlement process, for example. On the other hand, if authentication fails, the user is notified of the message. The user is notified, for example, by displaying the message on display 241.

[0113] Next, in terminal device 200, if the result received in step S1303 is successful authentication, the mobile history generation unit 272 uses the location information 4b collected before that moment to generate mobile history 5b (step S1304). Then, the newly generated mobile history 5b is stored in the mobile history storage unit 282 and sent to the store device 330 (step S1305). Mobile history 5b is sent to the store device 330 along with terminal ID 1a as new registration and authentication information. The transmission is performed via inter-terminal communicators 223 and 246.

[0114] In the store device 330, the newly received registration and authentication information (mobile history 5b and terminal ID 1a) is sent to the personal authentication device 310 (step S1404).

[0115] In the personal authentication device 310, the storage processing unit 312 updates the authentication information stored in the authentication information storage unit 314 with the newly received registration authentication information (step S1504). At this time, the storage processing unit 312 extracts the authentication information with the same terminal ID1a and replaces (overwrites) it with the newly sent authentication information.

[0116] Afterwards, the terminal device 200 returns to step S1301 to continue collecting location information.

[0117] exist Figure 8 (a)~ Figure 8 (c) shows the data flow of the initial registration process, store authentication process and authentication information update process described above.

[0118] like Figure 8 As shown in (a), during the initial registration process, the registration authentication information (mobility history 5a and terminal ID 1a) is directly sent to the personal authentication device 310.

[0119] In the subsequent processing after initial registration, namely store authentication and authentication information update, such as Figure 8 (b) and Figure 8 As shown in (c), authentication information (mobile history 5a and terminal ID 1a) or registration authentication information (mobile history 5b and terminal ID 1a) is sent to the personal authentication device 310 via the store device 330.

[0120] For the personal authentication process in this embodiment, along the movement of user 209, use Figure 9 (a)~ Figure 9 (d) will be explained. Assume that each store has store equipment 331, 332, 333, and 334.

[0121] First, user 209, Figure 9 As shown in (a), an initial registration process is performed before the personal authentication process of this embodiment is performed in a store or similar location. The initial registration process is performed, for example, at user 209's home or similar location.

[0122] When the initial registration process ends, user 209... Figure 9 As shown in (b), the terminal device 200, which has undergone initial registration, is taken to a store. Then, the terminal device 200 is presented to the store device 331. As a result, the terminal device 200 sends its stored mobile history 5a and terminal ID 1a as authentication information to the store device 331 to request authentication.

[0123] In addition, such as Figure 9 As shown in (b), user 209 continued to collect location information until arriving at the certified store.

[0124] Shop device 331 sends authentication information to personal authentication device 310 for authentication. Upon successful authentication, terminal device 200... Figure 9 As shown in (c), a new mobile history 5b is generated based on the location information accumulated after the previous mobile history was generated. Then, the new mobile history 5b is stored in its own mobile history storage unit 282 and sent to the store device 331 along with the terminal ID 1a as registration and authentication information.

[0125] The store device 331 transmits the new registration and authentication information (mobile history 5b and terminal ID 1a) to the personal authentication device 310. Then, the authentication information registered in association with terminal ID 1a is updated in the personal authentication device 310.

[0126] Subsequently, if user 209 visits another store, in that store's equipment 332, such as... Figure 9 As shown in (d), the newly stored mobile history 5b in the mobile history storage unit 282 is used to perform authentication requests, updates of authentication information, etc.

[0127] In addition, before the store authentication process, the authentication request unit 279 can also verify the legitimacy of user 209. That is, the terminal device 200 also has a user verification unit, which verifies whether user 209 is the pre-registered user 209, and performs store authentication processing after confirming that it is the user.

[0128] In this case, the identity verification performed by the identity verification department can utilize biometric information such as fingerprints. Alternatively, it can utilize knowledge information such as passwords.

[0129] Furthermore, in the above example, it is recorded that the terminal device 200 generates a movement history after receiving the authentication result, but the timing of generating the movement history is not limited to this. The generation of the movement history can also be performed independently of the authentication process. For example, it can also be configured, as described later, to determine the legitimacy of location information whenever it is collected, and if it is legitimate, to store it as movement information.

[0130] In this case, the authentication information, the mobile history already registered to the personal authentication device 310, and the newly generated mobile history scheduled for the next registration (update mobile history) are stored in the mobile history storage unit 282 in a distinguishable manner.

[0131] [Data Structures]

[0132] This section describes the structure of the data sent from terminal device 200 to personal authentication device 310 and store device 330.

[0133] exist Figure 10 Figure (a) shows an example of the data structure for terminal ID1a. As shown in this figure, terminal ID1a has model information 411 and a serial number 412 that identify the terminal model. However, terminal ID1a is not limited to these. Any information that can uniquely identify each terminal device 200 is acceptable. In addition, terminal ID1a can also be inserted as header information into the transmitted data, for example.

[0134] exist Figure 10 Example of the data structure for movement history 5a is shown in (b). Movement history 5a is, for example, time-series data of location information obtained during a specified period. That is, movement history 5a includes a specified number of location information. As shown in this figure, for each piece of location information, movement history 5a includes a number 421 identifying the location information, a date and time 422 of acquiring the location information, and location information 423.

[0135] Furthermore, the movement history 5a is not limited to this. For example, a hash value for each location information can be calculated, which is time-series data of that hash value. Additionally, from a privacy perspective, the order of the transfers of the location information obtained from positioning can be rearranged based on prescribed rules to form the movement history.

[0136] [Movement History Generation Processing]

[0137] The mobile history generation process of this embodiment is described here. In this embodiment, the mobile history generation unit 272 generates mobile history based on the location information collected by the positioning unit 271 during a predetermined period. At this time, in this embodiment, only the location information collected during the period when the legitimate user 209 of the terminal device 200 holds the terminal device 200 is used in the mobile history generation.

[0138] In this embodiment, whether a user 209 is legitimate is determined using pre-registered user characteristic information. In this embodiment, the characteristic information includes, for example, information about walking such as the user's gait frequency, stride length, and walking speed. This information is calculated, for example, based on acceleration information acquired by the accelerometer 264 over a predetermined period.

[0139] The pace is calculated based on the changes in the acceleration waveform of user 209 during walking. Furthermore, the step length is calculated by combining the calculated pace with the position information acquired by the positioning unit 271.

[0140] use Figure 11 (a)~ Figure 11(c) provides an overview of the mobile history generation process using feature information in this embodiment.

[0141] In this embodiment, such as Figure 11 As shown in (a), firstly, as an initial process, the feature information collection unit 274 collects predetermined feature information and registers it in the reference feature information storage unit 283 as reference feature information 50a for comparison.

[0142] Here, in Figure 10 Figure (c) shows the data structure of the registered reference feature information 50a. As shown in this figure, the reference feature information 50a includes, for example, pace frequency 431, step length 432, and walking speed 433. Alternatively, the reference feature information 50a can also be, for example, waveform data itself.

[0143] After registering reference feature information 50a, the mobile history generation unit 272 generates a mobile history using the location information obtained during the period held by the legitimate user 209.

[0144] like Figure 11 (b) Figure 11 As shown in (c), the feature information collection unit 274 acquires feature information at predetermined time intervals. Then, the comparison unit 273 compares the acquired feature information with the reference feature information 50a stored in the reference feature information storage unit 283 to determine whether there is consistency.

[0145] That is, if there is consistency, it is determined that the legitimate user 209 is holding the terminal device 200; if there is no consistency, it is determined that the illegitimate user 208 is holding the terminal device 200.

[0146] The movement history generation unit 272 calculates the movement history using the comparison results from the comparison unit 273.

[0147] The following describes the process of generating mobile history in this embodiment. Figure 12 (a) is the processing flow of the movement history generation process in this embodiment. This process is executed at a predetermined time interval Δt. In addition, during this period, the positioning unit 271 collects location information at time intervals shorter than Δt and stores it in the location information storage unit 281 in association with the collection time.

[0148] First, the feature information collection unit 274 collects feature information (step S1601). Then, the comparison unit 273 compares the collected feature information with the reference feature information 50a stored in the reference feature information storage unit 283 (step S1602).

[0149] If the collected feature information is substantially consistent with the reference feature information 50a, the comparison unit 273 determines that it is currently held by a legitimate user 209. Then, it compares the result with the previous comparison result to determine whether the comparison result has changed (step S1603). If the result has changed compared with the previous comparison result, the mobile history generation unit 272 is notified (step S1604).

[0150] Upon receiving notification of a change in the comparison results, the mobile history generation unit 272 reverses the state of mobile history generation (step S1605), stores the current comparison results, and ends the process. That is, if mobile history is being generated, the generation of mobile history is stopped; if mobile history generation has already stopped, the generation of mobile history begins.

[0151] Thus, in this embodiment, if the mobile history generation unit 272 determines that the mobile history is held by a legitimate user 209, it continues to generate mobile history until the next determination that the mobile history is not held by a legitimate user 209. Conversely, if the mobile history is determined to be not held by a legitimate user 209, it stops generating mobile history until the next determination that the mobile history is held by a legitimate user 209. That is, as explained in step S1605 above, the state of mobile history generation and non-generation is reversed corresponding to the reversal of the comparison result.

[0152] The generation and non-generation of the aforementioned movement history are illustrated using specific timing diagrams. Figure 12 (b) is a timeline diagram showing the changes in the control sequence (conducting control, not conducting control), control results (consistent, inconsistent), movement history generation, and non-generation states of the control unit 273.

[0153] As described above, the comparison unit 273 compares the acquired feature information with the reference feature information at predetermined time intervals Δt. Then, if the comparison result changes, the movement history generation unit 272 is notified.

[0154] Figure 12 In example (b), the first and second comparison results are consistent, showing no change compared to the previous comparison result. Therefore, the comparison unit 273 does not notify the motion history generation unit 272 of the comparison results. Because there is no notification, the motion history generation unit 272 maintains this state. For example, it continues to generate motion history while it is being generated. On the other hand, it remains in a stopped state even when motion history generation has stopped.

[0155] Here, during the third comparison, the comparison results are inconsistent. In this case, the comparison result has changed compared to the consistent second comparison result, so the comparison unit 273 notifies the motion history generation unit 272. The motion history generation unit 272 accepts the notification and reverses the state. That is, in this case, the generation of motion history, which was previously being generated, is stopped.

[0156] In the fourth comparison, the comparison results were consistent. In this case, the comparison results have changed compared to the inconsistent third comparison results, therefore the comparison unit 273 notifies the motion history generation unit 272. The motion history generation unit 272 accepts the notification and determines the status. That is, in this case, motion history generation, which had previously been stopped, begins to be generated.

[0157] Figure 12 In example (b), it was determined that the property was held by the legitimate user 209 until the third comparison, and from the third comparison until the fourth comparison, it was determined that the property was not held by the legitimate user 209.

[0158] In this embodiment, the movement history generation unit 272 generates movement history based on location information only during the period determined to be held by a legitimate user 209. Therefore, it is possible to collect the movement history of the legitimate user 209 with high accuracy.

[0159] Furthermore, in the above embodiment, information calculated based on the output of the accelerometer 264 is used as feature information, but the feature information is not limited to this. For example, if the terminal device 200 is a watch-type device, such as Figure 11 As shown in (d), it could also be a pulse wave signal, for example. Regarding the pulse wave signal, for example, a pulse wave sensor is provided as a bio-information sensor 267, and the pulse wave signal is acquired using this pulse wave sensor.

[0160] As explained above, according to this embodiment, the movement history generated based on location information, and the movement history pre-registered by user 209, is used for user 209's personal authentication. Therefore, personal authentication can be performed using the inherent information of the terminal holder. In addition, since there is no process of generating and answering questions, the burden on the personal authentication device 310 is reduced, and the burden and trouble for the user 209 operating the terminal device 200 are also reduced.

[0161] Furthermore, this mobile history is registered in the personal authentication device 310 in association with the identification information (terminal ID) of the terminal device 200. Therefore, for example, even if the mobile history information is simply copied and sent from another terminal, authentication will not succeed. Thus, security is high.

[0162] Furthermore, the mobile history is generated using location information collected during the period when the terminal device 200 is determined to be held by a legitimate user 209. Therefore, the mobile history used in personal authentication has high credibility.

[0163] Furthermore, the system continuously generates movement history and updates it as authentication information in the personal authentication device 310 at predetermined times. Therefore, it provides a system that prevents authentication information leakage.

[0164] Furthermore, in the above embodiments, particularly in the store device 330, the authentication information is updated after authentication. Therefore, the transmission and reception of data during the update are performed via inter-terminal communication. Compared to transmission and reception via a general network, inter-terminal communication offers higher security. Because such highly secure communication is used to update the authentication information, the overall security of the system is also high.

[0165] Thus, in this embodiment, personal authentication is performed using a movement history generated based on highly accurate location information of the individual. Furthermore, this movement history, along with information from the identification terminal device 200, is pre-registered in the personal authentication device 310. The authentication information is then updated at predetermined times. Therefore, according to this embodiment, a system that balances security and convenience can be achieved.

[0166] Furthermore, in this embodiment, the movement history is updated using the store device 330 after the user authenticates themselves at the store, but this is not a limitation. For example, it could also be configured to send authentication information to the user authentication device 310 via the network 101 at a predetermined time to update the data. The predetermined time could be, for example, a pre-determined time interval, or whenever a predetermined amount of movement history is generated. In this case, prescribed security measures such as encryption are implemented during transmission.

[0167] Alternatively, a movement history can be generated whenever a predetermined amount of location information (legitimate location information) obtained during the period held by a legitimate user 209 accumulates. In this case, only the most recent movement history can be stored as the update movement history.

[0168] Furthermore, as described above, when inter-terminal communication with the store device 330 is possible, and a movement history is generated periodically, a predetermined amount of valid location information may be obtained, including the location information used when the movement history was last generated. For example, this may be in cases where the period since the last movement history generation is short, and a sufficient amount of valid location information has not been accumulated. Additionally, if a sufficient amount of valid location information has not been accumulated, a new movement history may not be generated, and the movement history stored in the authentication information in the personal authentication device 310 may not be updated.

[0169] Furthermore, in the above embodiment, the terminal ID is sent along with the mobile history as authentication information, and the terminal ID1a is also stored in the personal authentication device 310, but this is not a limitation. Alternatively, only the mobile history may be stored in the authentication information storage unit 314 of the personal authentication device 310. In this case, regardless of the sender's terminal device 200, as long as the sent mobile history is stored in the authentication information storage unit 314, the authentication unit 313 considers the authentication successful.

[0170] <<Second Implementation>>

[0171] Next, a second embodiment of the present invention will be described. In the first embodiment, each store independently possesses a personal authentication device. In contrast, in this embodiment, each store or each group of stores possesses a personal authentication device. Furthermore, the authentication information used in personal authentication is distributed and shared among multiple personal authentication devices.

[0172] Hereinafter, the personal authentication system 102 of this embodiment will be described with a focus on its structure, which differs from that of the first embodiment.

[0173] exist Figure 13 The overall structure of the personal authentication system 102 of this embodiment is shown. The personal authentication system 102 of this embodiment includes a terminal device 200 and a provider system 302. Furthermore, the provider system 302 includes personal authentication devices 350 (351, 352, 353) configured in each store. The personal authentication devices 350 are connected to each other via an internal network 320. Additionally, when it is not necessary to specifically distinguish between the personal authentication devices 351, 352, and 353, they are referred to as personal authentication device 350.

[0174] The terminal device 200 of this embodiment has a structure that is substantially the same as that of the terminal device 200 of the first embodiment, so the description is omitted here.

[0175] Figure 14 (a) is a functional block diagram of the self-authentication device 350 of this embodiment. Additionally, Figure 14 (b) is a hardware structure diagram of the self-authentication device 350 of this embodiment.

[0176] like Figure 14 As shown in (b), the personal authentication device 350 of this embodiment, in addition to the structure of the personal authentication device 310 of the first embodiment, includes an inter-terminal communicator 326. The inter-terminal communicator 326 has the same structure as the device with the same name as the terminal device 200. In this embodiment, it is used to send and receive data with the terminal device 200 in a store.

[0177] Furthermore, the personal authentication device 350 in this embodiment, such as Figure 14As shown in (a), it has a shared processing unit 315 in addition to the same functional structure as the first embodiment.

[0178] In this embodiment, as described above, multiple personal authentication devices 350 are provided. Furthermore, authentication information is shared among all personal authentication devices 350. Additionally, in this embodiment, authentication is performed using multiple personal authentication devices 350 corresponding to one authentication request. Then, if a predetermined proportion, for example, more than half, of the personal authentication devices 350 determines that authentication is successful, the system as a whole determines that authentication is successful.

[0179] To achieve this, the sharing processing unit 315 determines the sender of the received authentication information after the communication unit 311 determines whether the authentication information has been registered. Here, it determines whether the sender is the terminal device 200 or another personal authentication device 350. Whether the sender is the terminal device 200 or another personal authentication device 350 is determined, for example, based on the header information of the transmitted and received data.

[0180] Then, if the sender of the received authentication information or registration authentication information is the terminal device 200, the communication unit 311 is instructed to transmit the received authentication information or registration authentication information not only to the storage processing unit 312 or the authentication unit 313, but also to all other personal authentication devices 350. On the other hand, if the sender of the received authentication information or registration authentication information is another personal authentication device 350, similar to the first embodiment, the information is transmitted to the storage processing unit 312 or the authentication unit 313 according to the determination result of whether or not to register authentication information.

[0181] Furthermore, when authentication information is received from another personal authentication device 350, the sharing processing unit 315 causes the authentication unit 313 to perform authentication, and causes the communication unit 311 to send the authentication result to the sender's personal authentication device 350.

[0182] Furthermore, when receiving authentication results from other personal authentication devices 350 via the communication unit 311, it determines whether the authentication results, including those from the authentication unit 313 of this device, are successfully authenticated in more than half of the personal authentication devices 350. If more than half are successfully authenticated, it is considered successful, and the result is sent from the communication unit 311 to the sending terminal device 200. On the other hand, if less than half of the authentication results are successful, it is considered a failure, and the result is sent from the communication unit 311 to the sending terminal device 200.

[0183] The following describes the process of personal authentication in this implementation method.

[0184] In this embodiment, similar to the first embodiment, the terminal device 200 first performs an initial registration process for the personal authentication device 350, registering authentication information. This initial registration process, like in the first embodiment, is performed by sending registration authentication information to a specific personal authentication device 350 via the network 101.

[0185] At this time, the personal authentication device 350 that received the registration and authentication information not only stores the received authentication information (mobile history 5a and terminal ID 1a) in its own authentication information storage unit 314, but also sends it to other personal authentication devices 350. Then, the other personal authentication devices 350 also store the received registration and authentication information in their authentication information storage units 314.

[0186] Therefore, the registration and authentication information (mobility history 5a and terminal ID 1a) of the terminal device 200 is shared among all personal authentication devices 350.

[0187] use Figure 15 This embodiment describes the data flow during authentication. As shown in the figure, when a user 209 holding a terminal device 200 goes to a specific store and requests authentication from the self-authentication device 352, that is, when the authentication request is received from the terminal device 200, the self-authentication device 352 performs authentication within the device.

[0188] Additionally, the self-authentication device 352 sends authentication information (mobility history 5a and terminal ID 1a) to other self-authentication devices 351 and 353 via the internal network 320. Authentication is performed in the other self-authentication devices 351 and 353 respectively, and the authentication results are replied to the sending self-authentication device 352 via the internal network 320.

[0189] In the self-authentication device 352, the final authentication result is determined by using its own authentication result and the authentication results received from other self-authentication devices 351 and 353, and a response is given to the terminal device 200 of the requesting source.

[0190] Alternatively, in this embodiment, initial registration can also be performed using inter-terminal communication in specific stores equipped with the personal authentication device 350. With this configuration, authentication information during the initial registration process can be sent and received via inter-terminal communication. This further enhances security.

[0191] According to this embodiment, multiple personal authentication devices 350 having the same structure as in the first embodiment are included. Therefore, according to this embodiment, the same effects as in the first embodiment can be obtained. Furthermore, in this embodiment, multiple personal authentication devices 350 share authentication information. Thus, during authentication, multiple devices reach a consensus and perform mutual verification, thereby improving reliability.

[0192] Furthermore, in this embodiment, authentication is considered successful when more than half of the personal authentication devices 350 successfully authenticate. However, the proportion of successfully authenticated personal authentication devices 350 at the time of authentication is not limited to this and can be freely set. For example, it may be configured so that authentication is considered successful only when all personal authentication devices 350 successfully authenticate.

[0193] Furthermore, the above embodiment was described using the case where the self-authentication device 350 is configured in each store as an example, but it is not limited to this structure. For example, the self-authentication device 350 may also be configured for each of several store groups.

[0194] Furthermore, various modifications of the first embodiment can also be applied in this embodiment.

[0195] <<Third Implementation Method>>

[0196] Next, a third embodiment of the present invention will be described. In this embodiment, the location information of a third party is used to verify the legality of the movement history.

[0197] In this embodiment, the location information is obtained from a third party, such as the location information of a mobile phone network base station 105. Hereinafter, this embodiment will be described primarily with regard to a structure different from the first embodiment.

[0198] The overall structure of the self-authentication system 100 in this embodiment is basically the same as that in the first embodiment. Furthermore, the hardware structure and functional modules of each component are also basically the same as in the first embodiment. However, the terminal device 200 has a structure for acquiring the location information of a third party. Additionally, the self-authentication device 310 has a structure for determining the legality of the third party's location information.

[0199] Figure 16 (a) is a functional module of the terminal device 203 of this embodiment. As shown in this figure, the terminal device 203 of this embodiment has a reference information acquisition unit 277 in addition to the structure of the first embodiment. The reference information acquisition unit 277 acquires reference position information at the time when the positioning unit 271 acquires position information and stores it in the position information storage unit 281. Then, in association with the position information acquired at the same time as the positioning unit 271, it is stored as reference information in the reference information storage unit 285.

[0200] In this embodiment, the reference location information acquired by the reference information acquisition unit 277 is, for example, the information of the base station 105 as described above.

[0201] The reference information acquisition unit 277 acquires information about the base station 105 used for communication via the telephone network communicator 222 in the communicator 220 as reference location information. The acquired reference location information may be, for example, the location information of the base station 105 itself, or identification information (base station ID) that identifies the base station.

[0202] like Figure 17 As shown in (a), the reference information acquisition unit 277 stores the set of position information 2a and reference position information 40a acquired at the same time as reference information 500a in the reference information storage unit 285.

[0203] Furthermore, the reference information 500 is repeatedly generated at predetermined times. Thus, multiple sets of reference information 500, including location information 2 and reference location information 40, are generated and stored in the reference information storage unit 285. Here, an example is shown where reference information 500a (40a, 2a), reference information 500b (40b, 2b), and reference information 500c (40c, 2c) are registered.

[0204] In this embodiment, during authentication, such as Figure 17 As shown in (b), the authentication request unit 279 sends the reference information 500 to the store device 330 in addition to the authentication information (mobile history 5a and terminal ID 1a) in the first embodiment. Then, the store device 330 sends the received authentication information and reference information 500 to the personal authentication device 310.

[0205] Furthermore, the personal authentication device 319 in this embodiment is as follows: Figure 16 As shown in (b), in addition to the structure of the first embodiment, a reference information verification unit 316 is also provided. The reference information verification unit 316 verifies the legality of the reference information 500.

[0206] That is, the reference information verification unit 316 verifies whether the relationship between the location information 2 in the received reference information 500 and the associated registered reference location information 40 is reasonable. For example, if the reference location information 40a is the location information of the base station 105, it verifies whether the location information 2a is within the coverage area of ​​the base station 105 specified by the reference location information 40a.

[0207] In addition, if the reference location information 40a is the base station ID of base station 105, it is verified whether the location is within the coverage area of ​​base station 105 specified by that ID.

[0208] In addition, the personal authentication device 310 can obtain the location information and / or base station ID of each base station 105 and the corresponding information of the coverage area.

[0209] Then, the person is considered to have successfully authenticated only if the baseline information verification result indicates that they are within the coverage area.

[0210] along Figure 18 The process of authentication processing in the self-authentication device 310 of this embodiment is explained.

[0211] First, similar to the first embodiment, the authentication unit 313 compares the received authentication information with the authentication information stored in the authentication information storage unit 314 (step S3101).

[0212] Then, if there is an inconsistency, it is considered an authentication failure, and the sending terminal device 200 replies with a message indicating authentication failure (step S3106), and the process ends.

[0213] On the other hand, if the information is consistent, the reference information verification unit 316 analyzes each reference information 500 and verifies its legality (step S3103). Here, it is determined whether the location information 2 is within the coverage area of ​​the base station 105 specified by the reference location information 40, as described above. Then, if all reference information 500 are within the coverage area, it is determined to be legal (step S3104).

[0214] If the authentication is deemed valid in step S3104, the terminal device 200 of the sender will reply with a message indicating successful authentication (step S3105), and the process will end.

[0215] On the other hand, if it is not determined to be legal, proceed to step S3106.

[0216] Furthermore, in this embodiment, the location information of the mobile phone base station 105 is used as the reference information, but the reference information is not limited to this. Any information that can be obtained by the terminal device 200, such as the location information of other landmarks, and whose legality can be determined by the personal authentication device 310, is acceptable.

[0217] In this embodiment, the terminal device 200 and the personal authentication device 310 each have the same structure as in the first embodiment. Therefore, the same effect as in the first embodiment can be obtained. Furthermore, in this embodiment, the terminal device 200 collects reference information and sends it to the personal authentication device 310 along with authentication information. Then, the personal authentication device 310 also determines the legality of the reference information. For example, the location information of a third party can be used as the reference information.

[0218] Therefore, according to this embodiment, it is possible to determine whether the movement history sent from the terminal device 200 was actually obtained due to the movement of the user 209, and whether it is not spoofed. This further improves reliability.

[0219] Furthermore, various modifications of the first embodiment can also be applied in this embodiment.

[0220] In the above embodiment, authentication information is generated based on the location information obtained by the positioning unit 271, but the authentication information is not limited to this. For example, purchase history can also be used. Purchase history may include, for example, store information, product information, and purchase amount information.

[0221] This invention is not limited to the embodiments described above, and includes various modifications. For example, the embodiments described above are for ease of understanding and illustration of the invention, and are not limited to having all the structures described. Furthermore, a portion of the structure of one embodiment can be replaced with a structure of another embodiment, and a structure of another embodiment can be added to the structure of one embodiment. Additionally, for a portion of the structure of each embodiment, other structures can be added, deleted, or replaced.

[0222] Furthermore, the aforementioned structures, functions, processing units, and processing modules can be partially or entirely implemented in hardware, for example, through design in integrated circuits.

[0223] In addition, the control lines and information lines shown are those deemed necessary for the description, but do not necessarily represent all control lines and information lines on the product. In fact, it can be assumed that almost all structures are interconnected.

[0224] Explanation of reference numerals in the attached figures

[0225] 1a: Terminal ID, 2: Location Information, 2a: Location Information, 4a: Location Information, 4b: Location Information, 5a: Movement History, 5b: Movement History, 40: Reference Location Information, 40a: Reference Location Information, 50a: Reference Feature Information

[0226] 100: Personal authentication system, 101: Network, 102: Personal authentication system, 105: Base station.

[0227] 200: Terminal device, 201: CPU, 202: System bus, 203: Terminal device, 208: Unauthorized user, 209: Authorized user, 210: Storage device, 211: ROM, 212: RAM, 213: External memory I / F, 220: Communicator, 221: LAN communicator, 222: Telephone network communicator, 223: Inter-terminal communicator, 227: Extended I / F, 230: Operator, 240: Video processor, 241: Display, 242: Image signal processor, 243: Camera, 246: Inter-terminal communicator, 250: Audio processor, 251: Speaker, 252: Sound signal processor, 25 3: Microphone; 260: Sensor; 261: GPS Receiver; 262: Gyroscope Sensor; 263: Geomagnetic Sensor; 264: Accelerometer Sensor; 265: Illuminance Sensor; 266: Proximity Sensor; 267: Biometric Sensor; 271: Position Measurement Unit; 272: Motion History Generation Unit; 273: Comparison Unit; 274: Feature Information Collection Unit; 275: Communication Unit; 276: Registration Processing Unit; 277: Reference Information Acquisition Unit; 279: Authentication Request Unit; 281: Location Information Storage Unit; 282: Motion History Storage Unit; 283: Reference Feature Information Storage Unit; 284: Terminal ID Storage Unit; 285: Reference Information Storage Unit.

[0228] 300: Provider System; 302: Provider System; 310: Personal Authentication Device; 311: Communication Department; 312: Storage and Processing Department; 313: Authentication Department; 314: Authentication Information Storage Department; 315: Sharing and Processing Department; 316: Reference Information Verification Department; 319: Personal Authentication Device; 320: Internal Network; 321: CPU; 322: Memory; 323: Storage Device; 324: Communicator; 325: LAN Communicator; 326: Terminal Inter-terminal communicator; 330: Shop equipment; 331: Shop equipment; 332: Shop equipment; 333: Shop equipment; 334: Shop equipment; 340: LAN communicator; 341: CPU; 342: Memory; 343: Storage device; 344: Communicator; 345: LAN communicator; 346: Inter-terminal communicator; 350: Personal authentication device; 351: Personal authentication device; 352: Personal authentication device; 353: Personal authentication device.

[0229] 411: Model information, 412: Serial number, 422: Date and time, 423: Location information, 431: Pace frequency, 432: Step length, 433: Walking speed.

[0230] 500: Baseline information, 500a: Baseline information, 500b: Baseline information, 500c: Baseline information.

Claims

1. A terminal device, characterized in that, include: A positioning unit that measures the position of the terminal device at specified time intervals and accumulates the measurement results as position information. A mobile history generation unit that uses the location information within a specified period to generate a mobile history and stores it as mobile history information; In order to register the aforementioned mobile history information, it is sent to the registration processing unit of the personal authentication device; The authentication request unit uses the mobile history information that the registration processing unit has sent to the personal authentication device to make an authentication request to the personal authentication device. Feature information collection unit for collecting feature information representing the characteristics of the user of the terminal device; and The comparison unit compares the collected feature information with reference feature information, which is pre-saved feature information of legitimate users, and outputs the comparison result. The movement history generation unit uses the position information obtained during the period indicated by the comparison unit's output of information showing that the feature information is consistent with the reference feature information as the comparison result to generate the movement history. The characteristic information is the output of an accelerometer that detects the acceleration of the terminal device during a specified period, or the output of a pulse wave sensor that detects the pulse wave of the user during a specified period.

2. The terminal device as described in claim 1, characterized in that: The registration processing unit will uniquely identify the terminal device and send the mobile history information together with the terminal device to the personal authentication device. The authentication request made by the authentication request unit includes the terminal identification information and the mobile history information.

3. The terminal device as described in claim 1, characterized in that: After being authenticated according to the authentication request from the authentication request unit, the registration processing unit sends the latest mobile history information to the personal authentication device.

4. The terminal device as described in claim 1, characterized in that: It also includes a reference information acquisition unit that obtains the location information of a third party as reference information. The authentication request made by the authentication request unit also includes the reference information.

5. The terminal device as described in claim 1, characterized in that: The authentication request is made using short-range wireless communication.

6. A personal authentication system comprising a terminal device, an authentication interface device, and a personal authentication device, characterized in that: The terminal device includes: A positioning unit that measures the position of the terminal device at specified time intervals and accumulates the measurement results as position information. A mobile history generation unit that uses the location information within a specified period to generate a mobile history and stores it as mobile history information; In order to register the aforementioned mobile history information, it is sent to the registration processing unit of the personal authentication device; The authentication request unit uses the mobile history information that the registration processing unit has sent to the personal authentication device to make an authentication request to the personal authentication device via the authentication interface device. A feature information collection unit for collecting feature information representing the characteristics of the user of the terminal device; and The comparison unit compares the collected feature information with reference feature information, which is pre-saved feature information of legitimate users, and outputs the comparison result. The movement history generation unit uses the position information obtained during the period indicated by the comparison unit's output of information showing that the feature information is consistent with the reference feature information as the comparison result to generate the movement history. The personal authentication device includes: A storage and processing unit for storing the mobile history information sent from the terminal device; and The authentication department, upon receiving the authentication request from the terminal device via the authentication interface device, performs authentication by determining whether the mobile history included in the authentication request has been stored by the storage and processing department, and returns the authentication result. The characteristic information is the output of an accelerometer that detects the acceleration of the terminal device during a specified period, or the output of a pulse wave sensor that detects the pulse wave of the user during a specified period.

7. The personal authentication system as described in claim 6, characterized in that: Whenever the storage and processing unit receives new mobile history information from the terminal device, it overwrites the already stored mobile history information with the latest mobile history information.

8. The personal authentication system as described in claim 6, characterized in that: Includes multiple of the aforementioned personal authentication devices, Each of the aforementioned personal authentication devices has a shared processing unit. The shared processing unit sends the mobile history information and the authentication request sent from the terminal device to other personal authentication devices, and receives the authentication results corresponding to the authentication requests from the other personal authentication devices respectively. Based on the received authentication results and the authentication results obtained by its own authentication unit, it determines whether the authentication is successful.

9. A method for personal authentication in a personal authentication system, wherein the personal authentication system includes a terminal device, an authentication interface device, and a personal authentication device, and the personal authentication method is characterized by comprising: The initial registration step involves storing the mobile history information in the terminal device and sending the mobile history information to the personal authentication device, where it is stored as authentication information. The authentication process involves sending the mobile history information as an authentication request to the personal authentication device via the authentication interface device, and then using the authentication information to accept authentication in the personal authentication device. The authentication information update step involves sending the newly generated mobile history information to the personal authentication device via the authentication interface device, and replacing the authentication information stored in the personal authentication device with the mobile history information. and The mobile history information generation step generates the mobile history information before sending it from the terminal device to either the authentication interface device or the personal authentication device. The steps for generating the mobile history information include: The steps for obtaining the location information of the terminal device; A legality determination step involves collecting feature information representing the characteristics of the user of the terminal device and comparing it with reference feature information, which is used as pre-saved feature information of legitimate users, to determine the legitimacy of the user of the terminal device; and The location information obtained when it is deemed legal in the legality judgment step is used as the movement history information in the movement history decision step. The characteristic information is the output of an accelerometer that detects the acceleration of the terminal device during a specified period, or the output of a pulse wave sensor that detects the pulse wave of the user during a specified period.

10. The personal authentication method as described in claim 9, characterized in that: The authentication information also includes terminal identification information, which is the identification information of the sender's terminal device. In the authentication step, the authentication request includes the terminal identification information of the terminal device of the sender of the authentication request.

Images