JP7711533B2 - Information management server, information management method, and program - Google Patents

Description

The present invention relates to an information management server, an information management method, and a program.

Identity verification is performed in various procedures that are carried out in person or not in person (online) (see, for example, Patent Document 1). In particular, identity verification performed in not in person (online) procedures uses, for example, an image of a driver's license or electronic information obtained from a My Number card to confirm that the person performing the procedure is definitely the person in question. By performing identity verification, procedures that involve impersonation by a third party can be prevented, making the procedure safe.

JP 2002-24422 A

However, verifying identity every time a procedure is carried out places a heavy burden on users and the business carrying out the procedure. Businesses here include, for example, financial institutions and local governments. Users find it bothersome to be required to present official documents or their Individual Number card every time, even when there has been no change in their address or name. In addition, for business operators who outsource identity verification, verifying identity every time a procedure is carried out increases the costs paid to the outsourced company, placing a heavy economic burden on them.

One possible solution to this problem would be to reduce the burden on users and companies by conducting identity verification only during the first procedure and omitting identity verification during subsequent procedures. For example, if the official document used for identity verification during the first procedure, such as a driver's license or My Number card, is still valid, identity verification could be omitted during subsequent procedures. However, even if the official document is still valid, a user's address may change due to moving, etc. In this case, identity verification may be omitted during procedures after the move, even though it is necessary to conduct identity verification at the new address, resulting in the problem of questionable safety.

The present invention was made in consideration of these circumstances, and its purpose is to provide an information management server, information management method, and program that can carry out secure procedures while reducing the burden of identity verification performed during procedures.

In order to solve the above-mentioned problems, the information management server of the present invention comprises an acquisition unit that acquires a procedure execution request from a user terminal, which requests the execution of a procedure related to a user, a judgment unit that judges whether or not to perform identity verification of the user in the procedure requested in the procedure execution request, an identity verification execution unit that performs identity verification of the user based on the judgment result by the judgment unit, and a memory unit that stores user attribute information that is attribute information of the user including the user's date of birth , and the judgment unit judges the user's age based on the user's date of birth, and when the user's age is less than a threshold, performs identity verification of the user more frequently than when the user's age is equal to or greater than the threshold .

In addition, in order to solve the above-mentioned problems, the information management method of the present invention is an information management method performed by a computer having a memory unit that stores user attribute information, which is attribute information of the user including the user's date of birth , wherein an acquisition unit acquires a procedure execution request requesting the execution of a procedure related to the user from a user terminal, a judgment unit judges whether or not to perform identity verification of the user in the procedure requested in the procedure execution request, an identity verification execution unit performs identity verification of the user based on the judgment result by the judgment unit, the judgment unit judges the user's age based on the user's date of birth, and when the user's age is less than a threshold, identity verification of the user is performed more frequently than when the user's age is equal to or greater than the threshold .

In order to solve the above-mentioned problems, the present invention is a program for operating a computer as the information management server described above, and for causing the computer to function as each part of the information management server.

The present invention allows safe procedures to be carried out while minimizing the burden of identity verification during procedures.

A block diagram showing an example of the configuration of a procedural information linkage system 1 to which an information management server 20 relating to an embodiment is applied. FIG. 2 is a block diagram showing an example of the configuration of an information management server 20 according to the embodiment. FIG. 2 is a diagram showing an example of user attribute information 220 according to the embodiment. FIG. 2 is a diagram showing an example of user attribute information 220 according to the embodiment. FIG. 2 is a diagram showing an example of user attribute information 220 according to the embodiment. A figure showing an example of procedure type information 221 related to the embodiment. FIG. 2 is a diagram showing an example of identity verification history information 222 according to the embodiment. FIG. 2 is a diagram showing an example of determination condition information 223 according to the embodiment. 4 is a flowchart showing a flow of processing performed by the information management server 20 according to the embodiment.

One embodiment of the present invention will be described below with reference to the drawings.

<Configuration of procedural information linkage system 1>
The procedural information linkage system 1 is a system that provides procedural services. In the procedural services, various procedures such as member registration, account registration, account transfer, address change, name change, administrative procedures, procedures to update personal information, and membership applications are carried out at each business in response to a user's request.

Figure 1 is a block diagram showing an example configuration of a procedural information linkage system 1 to which an information management server 20 according to an embodiment is applied. The procedural information linkage system 1 includes, for example, a user terminal 10, an information management server 20, an authentication server 30, and an operator server 40. These components in the procedural information linkage system 1 (the user terminal 10, the information management server 20, the authentication server 30, and the operator server 40) are connected to be able to communicate with each other via a communication network NW.

The user terminal 10 is a computer with communication capabilities, such as a smartphone, a mobile phone, or a tablet terminal. The user terminal 10 is operated by a user. The user can use the procedure service by operating the user terminal 10.

The information management server 20 is, for example, a computer such as a server, a cloud server, or a PC. The information management server 20 provides a procedure service. In the procedure service, the procedure is executed in response to a request from a user. The information management server 20 determines whether or not to perform identity verification when executing a procedure requested by a user. If the information management server 20 determines to perform identity verification, it requests, for example, the authentication server 30 to perform authentication required for identity verification and obtains the authentication result from the authentication server 30. If the information management server 20 confirms that the person who requested to execute the procedure is the person in question as a result of the identity verification, it notifies the business server 40 of the procedure content and the result of the identity verification. Alternatively, the information management server 20 may notify the business server 40 of information required for identity verification. In this case, the business server 40 performs identity verification based on the information received from the information management server 20 (information required for identity verification) and notifies the information management server 20 of the result.

The authentication server 30 is a computer such as a server, a cloud server, or a personal computer (PC). The authentication server 30 performs the authentication required for identity verification. For example, the authentication server 30 performs public personal authentication (JPKI, Japanese Public Key Infrastructure) using a My Number card. Alternatively, the authentication server 30 may be configured to perform identity verification using an identification card such as a driver's license.

The business operator server 40 is a computer such as a server, a cloud server, or a PC. The business operator server 40 executes various procedures at the business operator based on the procedure details notified by the user terminal 10 and the results of identity verification.

<Processing of procedural information linkage system 1>
In the procedure information linkage system 1, for example, official personal authentication using a My Number card is performed to verify the identity of the user. In the official personal authentication, the user's four basic pieces of information (name, date of birth, sex, and address) are obtained from the electronic certificate embedded in the My Number card. In addition, the authentication server 30 obtains the validity period of the electronic certificate embedded in the My Number card and checks its validity.

For example, a user logs in to the procedure service by operating the user terminal 10. When the user logs in to the procedure service, an authentication screen is provided from the information management server 20, and the authentication screen is displayed on the user terminal 10. The user enters the password set on the My Number card and performs a touch operation to bring the My Number card close to the user terminal 10 according to the guidance on the authentication screen. As a result, the user terminal 10 notifies the information management server 20 of information on the electronic certificate and the user's four basic information (name, date of birth, gender, address). The information management server 20 stores the four basic information of the user. The information management server 20 also notifies the authentication server 30 of information on the electronic certificate embedded in the My Number card and requests that the electronic certificate be confirmed as valid. The authentication server 30 acquires the validity period of the electronic certificate, confirms the validity of the electronic certificate based on the acquired validity period, and notifies the information management server 20 of the confirmation result. The confirmation result includes information indicating the validity period of the electronic certificate and the validity of the electronic certificate. The information management server 20 stores the validity period of the electronic certificate. Alternatively, the information management server 20 may be composed of multiple servers. For example, the information management server 20 may be composed of a first server having an acquisition function and a second server having a matching function. The acquisition function acquires information related to identity verification. The matching function performs identity verification based on the information acquired by the acquisition function. For example, the first server acquires information related to the electronic certificate embedded in the My Number card by a touch operation by the user, and outputs the acquired information to the second server. The second server notifies the authentication server 30 of the information acquired from the first server and requests that the validity of the electronic certificate be confirmed. The second server acquires the confirmation result of the confirmation of the validity of the electronic certificate from the authentication server 30, and outputs the acquired confirmation result to the first server.

Alternatively, in the procedure information linkage system 1, identity verification is performed using an identification card such as a driver's license. In this case, for example, the information management server 20 requests the authentication server 30 to verify the identity of the user using the identification card, and an authentication screen provided by the authentication server 30 is displayed on the user terminal 10. The authentication screen displays a guide for performing identity verification using the identification card. The user follows the guide on the authentication screen to capture an image of the driver's license or the user's own face. As a result, the user terminal 10 notifies the authentication server 30 of image information of the identity card and the user's own face. The authentication server 30 performs identity verification based on the image information acquired from the user terminal 10, and notifies the information management server 20 of the verification result. The verification result of the identity verification includes, for example, personal information such as the user's address, name, date of birth, etc., written on the identification card, the degree of match between the face photo on the identification card and the face image of the user himself, and information such as the validity period of the identification card. The information management server 20 acquires information indicating the verification result of the identity verification by the authentication server 30, and stores the acquired information. Alternatively, the information management server 20 may notify the business operator server 40 of the image information acquired from the user terminal 10. In this case, the business operator server 40 performs identity verification based on the image information received from the information management server 20 and notifies the information management server 20 of the result.

In conventional procedural information linkage systems, identity verification was performed in the following cases:
(1-1) When a user creates an account for a procedure service (1-2) When a procedure that requires identity verification is carried out (1-3) When the validity period of the electronic certificate embedded in the Individual Number Card has expired (1-4) When the validity period of an identification card has expired However, (3) is a case where identity verification is carried out using the official personal authentication with the Individual Number Card, and (4) is a case where identity verification is carried out using an identification card.

In conventional procedural information linkage systems, when a procedure is performed that does not require identity verification each time the procedure is performed (for example, a procedure for direct debit), the procedure is executed without identity verification. However, this assumes that the identity of the user is verified, for example, when creating an account for a procedural service, and that the procedure is performed within the validity period of the electronic certificate or identification used for identity verification. In the procedural information linkage system, the personal information of the user used for identity verification, such as the address and name, is registered in the information management server 20 as the latest personal information of the user. If identity verification is omitted in a procedure, the opportunity to update the user's personal information is lost. In the following explanation, the electronic certificate or identification used for identity verification may be collectively referred to as "official document."

The validity period of official documents is often set at around five years. If identity verification is not performed until the validity period of the official document has expired, the user's personal information will not be updated for a maximum of approximately five years. Consider a case in which the user's personal information, such as their address, changes during this time due to moving. If a procedure requiring identity verification is performed via a procedure service after the move, identity verification is performed during the procedure and the user's new address after the move can be registered as the user's latest personal information. However, if a procedure that does not require identity verification is performed, or if a procedure is performed without the user declaring that their personal information has been updated of their own volition, the procedure itself will be performed, but it will be performed in a state that is not consistent with the user's latest personal information, and as a result, the safety of the procedure may be questionable.

Or, even if the procedure is carried out safely, there is a possibility that adverse effects may occur due to the user's personal information not being updated. For example, if a user's address changes due to moving, it may become impossible to contact the user after the move. For example, if procedural information regarding a procedure that is about to expire is sent by mail, the mail may not reach the user's address after the move, making it difficult to provide appropriate procedural services.

In addition, depending on the business, there may be a problem if the user's personal information is not updated. When a procedure requiring identity verification is performed, the information management server 20 notifies the business server 40 of the details of the procedure as well as the results of the identity verification, so the business can keep track of the user's latest personal information. However, when a procedure not requiring identity verification is performed, the results of the identity verification are not notified, so although the procedure itself can be performed without problems, the business cannot keep track of the user's latest personal information. As a result, for example, even if a notice such as the expiration of a contract period or information about a new product is sent by mail to the user, there is a possibility that the mail will not arrive at the user's address after moving, resulting in an opportunity loss.

To address this issue, the procedural information linkage system 1 has completed a mechanism for setting the timing for checking whether a user's personal information is up to date for each user and procedure.

Specifically, the information management server 20 sets a flag for each user and procedure based on various conditions. The various conditions here are, for example, the type of procedure, the degree to which the user's personal information needs to be up to date, and the possibility that the user's personal information will change. The flag here is a variable that indicates whether or not identity verification will be performed; for example, when the flag is set to 1, it indicates that the user's personal information will be checked to see if it is up to date, and when the flag is set to 0 (zero), it indicates that the user's personal information will not be checked to see if it is up to date. In this case, the flag for procedures for which identity verification is mandatory is always set to 1.

The information management server 20 checks whether the user's personal information is up to date, depending on the setting value of the flag. When the user's personal information is updated, the information management server 20 stores the latest user's personal information. This updates the user's personal information and keeps the personal information up to date. The information management server 20 may also notify the business server 40 of the latest user's personal information. This allows the latest user's personal information to be linked to the business.

Here, possible methods for checking whether a user's personal information is up to date include forcibly verifying the user's identity using official documentation, or by questioning the user.

A method of confirming whether the user's personal information is up to date by asking the user a question will be described. The information management server 20 sends a notification to the user terminal 10 asking whether the user's personal information has changed. The user terminal 10 displays the question received from the information management server 20. In this case, the user terminal 10 displays a message such as "Has this content changed?" along with the user's personal information obtained at the previous identity verification. In addition, buttons such as "Yes" and "No" are displayed as selectable answers to the message. The user operates the screen to select the "Yes" or "No" button. When either button is selected, the user terminal 10 transmits an answer corresponding to the selection result to the information management server 20. Alternatively, the information management server 20 may ask whether the user's personal information has changed on a screen presented in the procedure service. In this case, the information management server 20 displays a question screen on the user terminal 10 asking whether the user's personal information has changed. The user operates the screen to select the "Yes" or "No" button displayed along with a message such as "Has this content changed?". When one of the buttons is selected, the answer corresponding to the selection is notified to the information management server 20.

When the information management server 20 receives a response from the user terminal 10 indicating that the user's personal information has been changed, it sends a notification to the user terminal 10 asking whether it is possible to present an official document that can certify the changed contents. The user terminal 10 sends a response to the question to the information management server 20. The response indicates whether it is possible to present an official document that can certify the changed contents.

If the response received from the user terminal 10 indicates that there is an official document that can certify the contents of the changes, the information management server 20 performs identity verification using the official document. If the identity verification confirms that the user is the actual person, the information management server 20 notifies the business server 40 of the procedure and the results of the identity verification.

On the other hand, if the response received from the user terminal 10 indicates that there is no official document that can certify the changed content, the information management server 20 notifies the user terminal 10 that the procedure cannot be carried out without identity verification. This prevents wasteful situations in which identity verification is carried out using old information before the change, resulting in the effort and cost of identity verification and ultimately making it impossible to carry out the procedure.

In the following explanation, checking whether a user's personal information is up to date will be referred to simply as "performing identity verification."

The information management server 20 performs user identity verification at the following frequency, for example.
(2-1) Frequency according to the score based on the results of a questionnaire administered to the user; (2-2) Frequency according to the user's age group; (2-3) Frequency according to the number of procedures the user performed in a specified period (e.g., one year); (2-4) Frequency according to the need to keep the user's personal information up to date

(2-1) will be explained. The information management server 20 conducts a questionnaire to the user and stores the results (answer history of the user attribute information 220 described later). The questionnaire here is a questionnaire about financial transactions and crime risks. In this questionnaire, questions are asked about whether the user has remitted money overseas from the perspective of anti-money laundering measures, for example. The information management server 20 conducts a questionnaire, for example, when the user creates an account for the procedure service and periodically after the account is created. The information management server 20 calculates a score based on the answers to the questionnaire. Alternatively, the information management server 20 may calculate the score using external information in addition to the answers to the questionnaire. Specifically, the information management server 20 may monitor the transaction status of the user's account, and if there is a difference between the answers to the questionnaire by the user and the actual transaction status, the score may be changed. The score here is an index that indicates the possibility that the safety of a procedure that the user may perform may be suspect if identity verification is omitted.

In the following, an example will be described in which the higher the score, the higher the security, and the lower the score, the lower the security. For example, if a user is sending remittances overseas, there is a possibility that the procedure for sending remittances overseas may be used for money laundering. For this reason, if identity verification is omitted in the procedure for sending remittances overseas, the security of the procedure may be called into question. For this reason, the information management server 20 calculates a low score when the user is sending remittances overseas. On the other hand, if the user is not sending remittances overseas, the procedure for sending remittances overseas is not executed, and therefore a high score is calculated.

The information management server 20 performs identity verification at a frequency that corresponds to the calculated score. For procedures performed by users with low scores, the information management server 20 sets the frequency of identity verification high and performs identity verification frequently (for example, once a year). This ensures the security of the procedures and makes it possible to update the user's personal information to the latest information.

(2-2) will now be described. In the initial identity verification, the information management server 20 stores the date of birth included in the user's personal information (personal information in user attribute information 220, described below). Based on the acquired user's date of birth, the information management server 20 categorizes the user into age groups and performs identity verification at a frequency according to the age group. For example, the information management server 20 categorizes users into younger age groups (e.g., up to 30s) and other age groups (e.g., 40s or older).

In general, the younger generation is more likely to live in rented housing compared to other age groups. Therefore, if a user is young, there is a high possibility that the user lives in rented housing, and there is a possibility that the user's address will change due to moving when it is time to renew the rental housing contract. For this reason, the information management server 20 sets the frequency of identity verification high for users who are young, and performs identity verification frequently (for example, once a year).

If the frequency of identity verification is set to once a year, the information management server 20 will perform identity verification, for example, the first time the user accesses the procedural service after the user's birthday each year.

The expiration date of official documents is often set based on the user's birthday. Therefore, by setting the timing of identity verification based on the user's birthday, it is possible to ensure an average validity period. For example, it is possible to avoid a situation in which the validity period of an official document expires immediately after identity verification is performed once a year, and identity verification must be performed using an updated official document shortly after identity verification is performed.

(2-3) will be explained. The information management server 20 stores the history of procedures performed by the user (identification history information 222, described later). When the information management server 20 receives a request from a user to perform a procedure, it acquires the history of procedures performed in the past by that user. Based on the acquired history, the information management server 20 calculates the number of procedures performed by the user this year. If the user has performed a procedure multiple times this year, the information management server 20 performs identity verification every predetermined number of times (for example, when the number of times is a multiple of three). This makes it possible to perform identity verification about once every multiple times when the user performs a procedure many times, ensuring the security of the procedure and updating the user's personal information to the latest information.

(2-4) will be explained. The information management server 20 stores information (procedure type information 221) indicating the conditions for identity verification for each procedure. The information management server 20 also stores the history of identity verification performed on the user (identity verification history information 222). When the information management server 20 receives a request from a user to perform a procedure, it acquires the conditions for identity verification in the procedure requested by the user, and determines whether identity verification is a condition for performing the procedure based on the acquired conditions. The information management server 20 also determines the degree of necessity for the user's personal information to be up to date. For example, if the business operator at the procedure destination is a business operator that notifies the user by mail, the information management server 20 determines that the degree of necessity for the user's personal information to be up to date is high. On the other hand, if the business operator at the procedure destination is a business operator that does not notify the user by mail, the information management server 20 determines that the degree of necessity for the user's personal information to be up to date is low.

When the information management server 20 determines that it is highly necessary for the user's personal information to be up to date, it refers to the history of identity verification performed on the user and obtains the date of the previous identity verification performed on the user. If a predetermined period (e.g., three years) has passed since the date of the previous identity verification, the information management server 20 determines to perform identity verification even if identity verification is not a condition for performing the procedure. Alternatively, the information management server 20 may change the predetermined period (e.g., three years) based on the user's age group, the results of a questionnaire response, or the history of the procedure. For example, if the user is a young person, the information management server 20 may determine to perform identity verification even if identity verification is not a condition for performing the procedure if a predetermined period (e.g., one year) has passed since the date of the previous identity verification. This makes it possible to update the user's personal information to the latest information according to the degree of necessity.

By checking whether the user's personal information is up to date at the frequencies shown in (2-1) to (2-4), the user's personal information can be updated at an appropriate time. This makes it possible to maintain the currency of the user's personal information without imposing an excessive burden on the user and without increasing the expenses and processing costs associated with identity verification.

It is not necessary to set a uniform frequency (how often to check whether a user's personal information is up to date) for each procedure and user. The frequency may be set arbitrarily for each procedure and user, depending on the number of identity verifications a user performs within a specified period, the cost required for each identity verification, the importance of identity verification in the procedure the user performs, etc.

For example, even if the procedure is the same type, identity verification may not be performed when one user performs the procedure, but may be performed when a different user performs the procedure. Also, even if the same user performs the same type of procedure, identity verification has previously been performed once a year, but from the next time onwards, it may be performed once a month.

<Configuration of information management server 20>
Here, the configuration of the information management server 20 will be described with reference to Fig. 2. Fig. 2 is a block diagram showing the configuration of the information management server 20 according to the embodiment. The information management server 20 includes, for example, a communication unit 21, a storage unit 22, and a control unit 23. The communication unit 21 communicates with the user terminal 10, the authentication server 30, and the business server 40.

The storage unit 22 is configured with a storage medium, for example, a hard disk drive (HDD), a flash memory, an electrically erasable programmable read only memory (EEPROM), a random access read/write memory (RAM), a read only memory (ROM), or any combination of these storage media. The storage unit 22 stores programs for executing various processes of the information management server 20, and temporary data used when performing various processes. The storage unit 22 stores, for example, user attribute information 220, procedure type information 221, identity verification history information 222, and judgment condition information 223.

User attribute information 220 is attribute information about a user. User attribute information includes, for example, the user's personal information, questionnaire response history, and procedure history. Figures 3 to 5 are diagrams showing examples of user attribute information 220 in an embodiment. User attribute information 220 is generated for each user. Note that user attribute information may also include information other than the information shown in Figures 3 to 5, such as the transaction status of the user's account.

Figure 3 shows an example of a user's personal information as user attribute information 220A. As shown in Figure 3, the personal information stores information corresponding to items such as name, date of birth, gender, and address. This personal information is, for example, information obtained from official documents when verifying the identity of the user.

Figure 4 shows an example of a survey response history as user attribute information 220B. As shown in Figure 4, the survey response history stores information corresponding to items such as the date the survey was conducted, the survey content, and a score calculated based on the survey responses. These response histories are created, for example, each time a survey is conducted on a user.

Figure 5 shows an example of a procedure history as user attribute information 220C. As shown in Figure 5, the procedure history stores information corresponding to items such as the date the procedure was performed, the contents of the procedure, and whether or not identity verification was performed during the procedure. These procedure histories are created, for example, each time a procedure is performed.

Procedure type information 221 is information indicating the conditions for carrying out a procedure at a business operator for each type of procedure. FIG. 6 is a diagram showing an example of procedure type information 221 according to an embodiment. Procedure type information 221 stores information corresponding to items such as the name of the procedure and whether or not identity verification is required. Procedure type information 221 is created, for example, for each business operator, and indicates whether or not identity verification is required for each of the various procedures carried out by the business operator.

The identity verification history information 222 is information showing the history of identity verification. The identity verification history information 222 is created for each user, for example. FIG. 7 is a diagram showing an example of the identity verification history information 222 according to the embodiment. The identity verification history information 222 stores information corresponding to items such as the implementation date, verification motivation, verification method, and expiration date. The implementation date stores information indicating the date on which identity verification was performed. The verification motivation stores information indicating the motivation that triggered identity verification. The verification method stores information indicating the type of official document used for identity verification, for example, a My Number card, a driver's license, or other document. The verification method may also include information indicating whether identity verification was performed using a public personal authentication (JPKI) or an image of an official document. The expiration date stores information indicating the expiration date of an official document such as an electronic certificate or an identification card used for identity verification.

The judgment condition information 223 is information indicating the judgment criteria for determining whether or not to perform identity verification. FIG. 8 is a diagram showing an example of the judgment condition information 223 according to the embodiment. The judgment condition information 223 stores information corresponding to items such as target users and implementation conditions. The target users store information indicating users who may be targets for identity verification. The implementation conditions indicate the conditions for identity verification. In the example of FIG. 8, it is shown that identity verification is performed once a year for young users. It is also shown that identity verification is performed when the number of procedures is a multiple of three for users who have performed a specified procedure (procedure A) three or more times in a year. It is also shown that identity verification is performed for users whose score in questionnaire A is equal to or less than a specified value (A3) every time they perform a procedure. It is also shown that identity verification is performed for users whose score in questionnaire B is equal to or less than a specified value (B2) every six months.

Returning to FIG. 2, the control unit 23 controls each component of the information management server 20. The control unit 23 is realized, for example, by the CPU (Central Processing Unit) of the information management server 20 executing a program pre-stored in the storage unit 22. The control unit 23 may also be realized as an integrated circuit such as an ASIC (Application Specific Integrated Circuit). The control unit 23 includes, for example, an acquisition unit 230, a determination unit 231, an identity verification execution unit 232, an information linkage unit 233, and a device control unit 234.

The acquisition unit 230 acquires various types of information. The acquisition unit 230 acquires various types of information notified from the user terminal 10, the authentication server 30, and the business server 40 via the communication unit 21. The acquisition unit 230 outputs the acquired information to functional units (the determination unit 231, the identity verification execution unit 232, the information linkage unit 233, and the device control unit 234) that perform processing using the information.

The acquisition unit 230 acquires a procedure execution request notified from the user terminal 10. The procedure execution request is a notification requesting to execute a procedure using a procedure service. The procedure execution request includes, for example, information indicating the content of the procedure requested by the user, and personal information such as the user's name and address.

The determination unit 231 acquires a procedure execution request from the acquisition unit 230, and determines whether or not identity verification is to be performed in the procedure requested in the procedure execution request. The determination unit 231 identifies the type of procedure requested by the user based on the procedure request information, and acquires procedure type information 221 including the identified procedure from the storage unit 22. The determination unit 231 determines whether or not identity verification is required for the procedure requested by the user based on the acquired procedure type information 221, and if it is required, determines that identity verification will be performed. Furthermore, if a condition for performing identity verification in the procedure requested by the user (e.g., performing identity verification if more than three months have passed since the previous procedure) is indicated based on the acquired procedure type information 221, the determination unit 231 determines whether or not the condition is satisfied, and if the condition is satisfied, determines that identity verification will be performed.

The determination unit 231 also identifies the user requesting the procedure based on the procedure request information, and acquires the user attribute information 220 and identity verification history information 222 of the identified user from the storage unit 22. The determination unit 231 determines whether the user is a user subject to the determination condition information 223 based on the user attribute information 220, identity verification history information 222, and determination condition information 223. If the user is a user subject to the determination condition information 223, the determination unit 231 acquires the implementation condition. The determination unit 231 determines whether the acquired implementation condition (for example, performing identity verification once a year) is satisfied, and if the condition is satisfied, determines to perform identity verification.

The identity verification execution unit 232 performs identity verification according to the result of the determination by the determination unit 231. When the determination unit 231 determines that identity verification should be performed, the identity verification execution unit 232 transmits to the user terminal 10, for example, an authentication screen for performing JPKI using a My Number card. Alternatively, the identity verification execution unit 232 asks a question to confirm whether the user's personal information has changed before performing identity verification, and performs identity verification after confirming that the personal information has not changed. Alternatively, if the personal information has changed, the identity verification execution unit 232 asks whether the user can present an official document that certifies that the personal information has changed, and if the changed official document can be presented, performs identity verification using the changed official document. If the changed official document is not presented, the identity verification execution unit 232 notifies the user terminal 10 that the procedure cannot be performed without performing identity verification.

The information linking unit 233 notifies the business server 40 of the contents of the procedure in response to the procedure execution request notified by the user terminal 10, and, if identity verification has been performed, the results of that identity verification.

The device control unit 234 performs integrated control of the information management server 20. For example, the device control unit 234 controls the communication unit 21 to output information received by the communication unit 21 from the user terminal 10, the authentication server 30, and the business server 40 to the acquisition unit 230.

<Processing flow>
Here, a description will be given of the flow of processing performed by the information management server 20. Fig. 9 is a flowchart showing the flow of processing performed by the information management server 20 according to the embodiment.

The information management server 20 receives a procedure execution request from the user terminal 10 (step S10). Based on the procedure request information, the information management server 20 acquires procedure type information 221 including the procedure requested by the user (step S11). The information management server 20 determines whether the conditions for identity verification in the procedure requested by the user are met (step S12). For example, if identity verification is mandatory in the procedure, or if the conditions for identity verification in the procedure (e.g., implementation if more than three months have passed since the previous procedure) are met, the information management server 20 determines that the conditions for identity verification in the procedure are met. If the information management server 20 determines that the conditions for identity verification in the procedure are met, it sets a flag (identity verification flag) to 1 (step S15).

On the other hand, if the information management server 20 determines in step S12 that the conditions for identity verification in the procedure requested by the user are not met, it acquires the user attribute information 220 and identity verification history information 222 of the user requesting the procedure. The information management server 20 determines whether the user meets the conditions for identity verification based on the user attribute information 220, identity verification history information 222, and judgment condition information 223 (step S14).

The information management server 20 determines that the conditions for identity verification are met, for example, when the age group of the user meets the conditions for identity verification indicated in the judgment condition information 223. The information management server 20 determines that the conditions for identity verification are met, for example, when the number of procedures performed by the user in a year meets the conditions for identity verification indicated in the judgment condition information 223. The information management server 20 determines that the conditions for identity verification are met, for example, when the score of a questionnaire administered to the user meets the conditions for identity verification indicated in the judgment condition information 223.

If the information management server 20 determines that the user meets the conditions for identity verification, it sets the flag (identity verification flag) to 1 (step S15). On the other hand, if the information management server 20 determines that the user does not meet the conditions for identity verification, it sets the flag (identity verification flag) to 0 (zero) (step S16).

As described above, the information management server 20 of the embodiment includes an acquisition unit 230, a determination unit 231, an identity verification execution unit 232, and a storage unit 22. The acquisition unit 230 acquires a procedure execution request notified from the user terminal 10. The procedure execution request is a notification requesting the execution of a procedure related to the user. The determination unit 231 determines whether or not to perform identity verification of the user in the procedure requested by the procedure execution request. The identity verification execution unit 232 performs identity verification of the user based on the determination result by the determination unit. The storage unit 22 stores user attribute information 220, which is attribute information of the user. The determination unit 231 determines whether or not to perform identity verification of the user based on the possibility that the user's personal information will be changed and the safety of the procedure based on the user attribute information 220. As a result, the information management server 20 of the embodiment can omit identity verification when the possibility that the user's personal information will be changed and the safety of the procedure is not suspected even if identity verification is not performed, making it possible to reduce the burden of identity verification. In addition, if there is a high possibility that a user's personal information will be changed, or if the safety of the procedure is in doubt, identity verification can be performed, enabling safe procedures to be carried out. Therefore, safe procedures can be carried out while minimizing the burden of identity verification.

In the information management server 20 of the embodiment, the user attribute information 220 includes personal information including the user's date of birth. The determination unit 231 determines the user's age based on the user's date of birth. When the user's age is less than a threshold, the determination unit 231 determines that identity verification should be performed more frequently than when the user's age is equal to or greater than the threshold. This makes it possible to take into account the possibility that the user's address will change due to moving at times such as when it is time to renew the rental property, in cases where the user is a young person who is likely to live in rental housing, and to carry out the procedure with the user's personal information up to date, thereby increasing the safety of the procedure.

In the information management server 20 of the embodiment, the user attribute information 220 includes the response results to a questionnaire regarding procedures. The determination unit 231 determines, based on the response results to the questionnaire, that if a specific procedure is included in the procedures that the user can perform, identity verification will be performed more frequently than if the specific procedure is not included. As a result, when a user is sending remittances overseas, identity verification can be performed frequently in consideration of the possibility that overseas remittance procedures that may be used for money laundering are being performed, and the user's personal information can be kept up to date when the procedure is performed, thereby increasing the safety of the procedure.

In the information management server 20 of the embodiment, the user attribute information 220 includes a procedure execution history. The determination unit 231 determines, based on the procedure execution history, that if the number of times the procedure has been performed within a specified period (e.g., one year) is equal to or greater than a threshold, to perform identity verification more frequently than if the number of times the procedure has been performed within the specified period is less than the threshold. As a result, if a user performs a procedure repeatedly, identity verification can be performed once every several times (e.g., three times), and the user's personal information can be kept up to date during the procedure, thereby increasing the security of the procedure.

In the information management server 20 of the embodiment, when performing identity verification, the identity verification execution unit 232 may send a first notification to the user terminal 10 inquiring whether the user's personal information has changed. When the identity verification execution unit 232 receives a response to the first notification indicating that the user's personal information has changed, the identity verification execution unit 232 sends a second notification to the user terminal 10 inquiring whether the user can present an official document that can prove that the user's personal information has changed. When the identity verification execution unit 232 receives a response to the second notification indicating that the user cannot present an official document that can prove that the user's personal information has changed, the identity verification execution unit 232 does not perform identity verification of the user and notifies the user terminal 10 that the procedure cannot be performed. This makes it possible to prevent waste such as the time and cost required for identity verification being incurred as a result of performing identity verification using old information before the change, resulting in the procedure not being able to be performed.

The procedural information linkage system 1 and the information management server 20 in the above-mentioned embodiment may be realized in whole or in part by a computer. In that case, a program for realizing this function may be recorded in a computer-readable recording medium, and the program recorded in the recording medium may be read into the computer system and executed to realize the function. Note that the term "computer system" here includes hardware such as an OS and peripheral devices. Furthermore, the term "computer-readable recording medium" refers to portable media such as flexible disks, optical magnetic disks, ROMs, and CD-ROMs, and storage devices such as hard disks built into the computer system. Furthermore, the term "computer-readable recording medium" may include a medium that dynamically holds a program for a short period of time, such as a communication line when transmitting a program via a network such as the Internet or a communication line such as a telephone line, and a medium that holds a program for a certain period of time, such as a volatile memory inside a computer system that is a server or client in such a case. Furthermore, the above-mentioned program may be a program for realizing a part of the above-mentioned function, or may be a program that can realize the above-mentioned function in combination with a program already recorded in the computer system, or may be a program that is realized using a programmable logic device such as an FPGA (Field Programmable Gate Array).

The above describes an embodiment of the present invention in detail with reference to the drawings, but the specific configuration is not limited to this embodiment, and includes designs that do not deviate from the gist of the present invention.

1...Procedure information linkage system, 10...User terminal, 20...Information management server, 21...Communication unit, 22...Storage unit, 220...User attribute information, 221...Procedure type information, 222...Personal identification history information, 223...Determination condition information, 23...Control unit, 230...Acquisition unit, 231...Determination unit, 232...Personal identification execution unit, 233...Information linkage unit, 234...Device control unit, 30...Authentication server, 40...Business server

Claims (7)

an acquisition unit that acquires a procedure execution request from a user terminal, the procedure execution request requesting execution of a procedure related to a user;
a determination unit that determines whether or not to perform identity verification of the user in the procedure requested in the procedure execution request;
an identity verification execution unit that performs identity verification of the user based on a result of the determination by the determination unit;
A storage unit for storing user attribute information, which is attribute information of the user including the date of birth of the user ;
Equipped with
the determination unit determines an age of the user based on the user's date of birth, and when the user's age is less than a threshold, performs identity verification of the user more frequently than when the user's age is equal to or greater than the threshold;
Information management server. an acquisition unit that acquires a procedure execution request from a user terminal, the procedure execution request requesting execution of a procedure related to a user;
a determination unit that determines whether or not to perform identity verification of the user in the procedure requested in the procedure execution request;
an identity verification execution unit that performs identity verification of the user based on a result of the determination by the determination unit;
A storage unit that stores user attribute information, which is attribute information of the user including a response result of a questionnaire regarding a procedure ;
Equipped with
The survey included a question about whether or not the person remits money overseas.
the determination unit, when it is determined from the response result that the user is likely to carry out an overseas remittance procedure, performs identity verification of the user more frequently than when it is determined that the user is not likely to carry out an overseas remittance procedure.
Information management server. The user attribute information includes a procedure execution history,
the determination unit determines, based on the execution history, that when the number of times the user has performed a procedure within a specified period is equal to or greater than a threshold, to perform identity verification more frequently than when the number of times the user has performed a procedure within a specified period is less than the threshold.
3. The information management server according to claim 1 or 2. the identity verification execution unit sends a first notification to the user terminal inquiring whether or not there has been a change in the personal information of the user, and when a response to the first notification is received indicating that the personal information of the user has changed, sends a second notification to the user terminal inquiring whether or not an official document capable of proving that the personal information of the user has changed can be presented, and when a response to the second notification is received indicating that an official document capable of proving that the personal information of the user has changed cannot be presented, does not verify the identity of the user.
The information management server according to any one of claims 1 to 3 . 1. An information management method performed by a computer having a storage unit that stores user attribute information, which is attribute information of a user including a user's date of birth, comprising:
an acquisition unit acquires, from a user terminal, a procedure execution request for requesting execution of a procedure related to the user ;
a determination unit that determines whether or not to perform identity verification of the user in the procedure requested in the procedure execution request;
an identity verification execution unit performs identity verification of the user based on the determination result by the determination unit;
the determination unit determines an age of the user based on the user's date of birth, and when the user's age is less than a threshold, performs identity verification of the user more frequently than when the user's age is equal to or greater than the threshold;
Information management method. An information management method performed by a computer having a storage unit that stores user attribute information, which is attribute information of a user including a response result of a questionnaire regarding a procedure , comprising:
an acquisition unit acquires, from a user terminal, a procedure execution request for requesting execution of a procedure related to the user;
a determination unit that determines whether or not to perform identity verification of the user in the procedure requested in the procedure execution request;
an identity verification execution unit performs identity verification of the user based on the determination result by the determination unit;
The survey included a question about whether or not the person remits money overseas.
the determination unit, when it is determined from the response result that the user is likely to carry out an overseas remittance procedure, performs identity verification of the user more frequently than when it is determined that the user is not likely to carry out an overseas remittance procedure.
Information management method. 5. A program for causing a computer to operate as the information management server according to claim 1 , the program causing the computer to function as each unit included in the information management server.