JP6979979B2 - Account management device, account management method and account management program - Google Patents

Description

The present invention relates to an account management device, an account management method, and an account management program.

Conventionally, there is known an account management device that recovers an account of a user created when using a predetermined service when the account of the user expires. For example, the account management device has a technique for executing recovery by verifying the identity based on the user's behavior history (see, for example, Patent Document 1).

Japanese Patent No. 634205

However, with the conventional technology, there is room for improvement in terms of performing recovery that is highly convenient for the user. Specifically, in the prior art, since it is premised that a plurality of terminal devices are possessed, it cannot be said that the convenience is high depending on the user who has only one terminal device.

In addition, if the user himself suddenly dies in an unexpected accident, or if a relative performs account closing processing such as suspending the use of the user's account on behalf of the user, the authenticity of whether or not the user is a relative is determined. It was not easy to implement and was not very convenient.

The present application has been made in view of the above, and an object of the present invention is to provide an account management device, an account management method, and an account management program that can improve the convenience of a user regarding account procedures.

The account management device according to the present application includes a reception unit and an approval unit. The reception unit receives a request for execution of an account procedure possessed by the first user in a predetermined service. When the execution request is received by the reception unit, the approval unit makes an approval request for the procedure to a second user who has a kinship relationship with the first user estimated based on genetic information.

According to one aspect of the embodiment, there is an effect that the convenience of the user can be improved with respect to the procedure of the account.

FIG. 1 is a diagram showing an example of an account recovery process according to an embodiment. FIG. 2 is a diagram showing a configuration of a management system according to an embodiment. FIG. 3 is a block diagram showing a configuration example of the account management device according to the embodiment. FIG. 4 is a diagram showing an example of user information. FIG. 5 is a diagram showing an example of account information. FIG. 6 is a diagram showing an example of kinship information. FIG. 7 is a diagram showing the processing contents of the approval unit. FIG. 8 is a flowchart showing a procedure of processing executed by the management system according to the embodiment. FIG. 9 is a hardware configuration diagram showing an example of a computer that realizes the function of the account management device according to the embodiment.

Hereinafter, the account management device, the account management method, and the embodiment for implementing the account management program (hereinafter referred to as “the embodiment”) according to the present application will be described in detail with reference to the drawings. Note that this embodiment does not limit the account management device, account management method, and account management program according to the present application. Further, in each of the following embodiments, the same parts are designated by the same reference numerals, and duplicate explanations are omitted.

First, an example of an account recovery process realized by the account management program according to the embodiment will be described with reference to FIG. FIG. 1 is a diagram showing an example of an account recovery process according to an embodiment. FIG. 1 describes a recovery process (an example of an account procedure) in which a recovery approval request for an account is made to a second user who has a relative relationship with the first user when the account of the first user expires.

The state in which the account expires is a state in which the corresponding account cannot be used temporarily, for example, when the password input is mistaken for a specified number of times or more when logging in to the service.

As shown in FIG. 1, the account management device according to the embodiment first receives a genetic test request from a first user and a second user (S1). The genetic test is performed, for example, by collecting saliva, a part of the skin, hair, etc. from the user and using a dedicated test terminal.

The account management device according to the embodiment generates genetic information for each user as the analysis result of the genetic test (S2). The genetic information includes, for example, information on the health risk of the user, information on the constitution of the user, and the like. The genetic information may include, for example, information related to the genetic code such as a user's base sequence or amino acid sequence. The account management device may acquire the genetic information generated by another laboratory.

Subsequently, the account management device according to the embodiment estimates the kinship relationship between the first user and the second user based on the genetic information, and generates the kinship information (S3). The kinship estimation process may be performed in advance, or may be performed at the timing when the recovery request from the user is received.

Here, it is assumed that the account management device according to the embodiment receives a recovery request (an example of an execution request) requesting recovery of the account from the first user whose account has expired (S4). Upon receiving the recovery request, the account management device according to the embodiment identifies a second user who has a kinship relationship with the first user based on the kinship information (S5).

Then, the account management device according to the embodiment makes an approval request to the second user who has a relative relationship with the first user to approve the execution of the recovery of the account owned by the first user (S6).

Then, when the second user receives a response to approve the recovery in response to the approval request (S7), the account management device according to the embodiment executes the recovery (S8).

Then, after the recovery is completed, the account management device according to the embodiment gives a recovery notification indicating the completion of the recovery to the first user (S9).

As described above, the account management device according to the embodiment makes a recovery approval request to the relatives of the first user estimated based on the genetic information, and when executing the recovery, as in the prior art. , Does not require multiple terminal devices.

Therefore, according to the account management method according to the embodiment, it is possible to perform recovery that is highly convenient for the user. Further, the account management method according to the embodiment can be applied not only to account recovery but also to perform other procedures such as closing processing. That is, according to the account management method according to the embodiment, it is possible to improve the convenience of the user regarding the procedure of the account.

In addition, by targeting the recovery approval request to a relative, the approval request can be sent to the second user who is trusted by the first user whose account has expired, so that the satisfaction level of the service of the first user can be improved. can.

In addition, since the kinship relationship is estimated based on the genetic information, it is possible to reduce the mistaken transmission of the recovery approval request to a user other than the kinship person, and thus it is possible to reduce the leakage of the user's account to a stranger third party. ..

Next, the system configuration of the management system according to the embodiment will be described with reference to FIG. FIG. 2 is a diagram showing a configuration of a management system according to an embodiment.

As shown in FIG. 2, the management system S according to the embodiment includes an account management device 1, a plurality of terminal devices 10-1 to 10-n, and a plurality of service servers 100-1 to 100-m. The account management device 1, the plurality of terminal devices 10-1 to 10-n, and the plurality of service servers 100-1 to 100-m are connected to each other via a network N so as to be communicable with each other by wire or wirelessly. The network N is, for example, a LAN (Local Area Network) or a WAN (Wide Area Network) such as the Internet. The terminal devices 10-1 to 10-n are operated by the users U-1 to Un.

In the following, when each of the terminal devices 10-1 to 10-n is shown without distinction, it is referred to as a terminal device 10. Further, when each of the service servers 100-1 to 100-m is shown without distinction, it is described as service server 100, and when each of users U-1 to Un is shown without distinction, it is described as user U. do.

The terminal device 10 is a terminal device of the user U, and is a smart device (communication terminal) such as a smartphone, a tablet terminal, a PDA (Personal Digital Assistant), or a personal computer. The terminal device 10 can execute a browser, various applications, and the like. The terminal device 10 can access the service server 100 from a browser or an application via the network N and use the service provided by the service server 100. Further, the terminal device 10 can transmit various information such as a recovery request and an approval response to the account management device 1 according to the operation of the user U.

The service server 100 is a server device that provides a predetermined service. The service provided by the service server 100 includes, for example, a search service, a shopping service, an information providing service (for example, a news service and a weather forecast service) and the like.

The plurality of service servers 100-1 to 100-m may be managed by one business operator, or may be managed by a plurality of different business operators.

Further, the account management device 1 may be one server device that centrally manages the accounts of each of the plurality of service servers 100-1 to 100-m, and may be a plurality of server devices corresponding to each of the plurality of service servers 100. It may be a server device.

Next, the configuration of the account management device 1 according to the embodiment will be described with reference to FIG. FIG. 3 is a block diagram showing a configuration example of the account management device 1 according to the embodiment.

As shown in FIG. 3, the account management device 1 includes a communication unit 2, a control unit 3, and a storage unit 4.

The communication unit 2 is realized by, for example, a NIC (Network Interface Card) or the like. The communication unit 2 is connected to the network N by wire or wirelessly, and transmits / receives information to / from the terminal device 10 and the service server 100 via the network N.

The storage unit 4 is realized by, for example, a semiconductor memory element such as a RAM (Random Access Memory) or a flash memory (Flash Memory), or a storage device such as a hard disk or an optical disk. As shown in FIG. 3, the storage unit 4 stores the user information DB 40, the account information DB 41, and the kinship information DB 42.

The user information DB 40 includes user information which is information of the user U. FIG. 4 is a diagram showing an example of user information. The user information is, for example, information input by the user when creating an account.

As shown in FIG. 4, the user information includes items such as "user ID", "attribute", and "genetic information". The "user ID" is identification information that identifies the user U. The "attribute" is information about the attribute of the user U, and includes, for example, a demographic attribute and a psychographic attribute. The "genetic information" is, for example, information about the gene of the user U extracted by collecting saliva of the user U, for example, information about the health risk of the user U, information about the constitution of the user U, and information about the user U. Contains information on the genetic code such as base sequences and amino acid sequences. The genetic information may include genetic information generated by another laboratory.

The user information shown in FIG. 4 is an example, and may include, for example, image information of the user acquired at the time of a recovery request described later.

The account information DB 41 includes account information regarding the account of the user who uses the service. FIG. 5 is a diagram showing an example of account information. As shown in FIG. 5, the account information includes items such as "user ID", "account ID", "password", "account status", and "approval status".

The "account ID" is identification information issued by the service server 100 for each user U, and is a login ID for logging in to the service. The "account ID" may be a "user ID".

The "password" is a password for logging in to the service. The "password" may be specified by the user U or may be specified by the service server 100. "Account status" is the current status of the account. "Valid" indicates that it is available, "Valid" indicates that it is temporarily unavailable and can be restored to "Valid", and "Stop" indicates that it is "Valid". Indicates that the state cannot be restored. The "stop" is, for example, a state in which recovery approval has not been obtained from the second user, or a state in which the service has not been used for a certain period of time or longer.

The "approval status" indicates the status related to the approval of the recovery by the second user, and includes the "request presence / absence" and the "requester ID". "Presence / absence of request" is information indicating whether or not a recovery approval request has been made to the second user. The "requester ID" is the identification information (user ID) of the second user who has made the recovery approval request.

The kinship information DB 42 includes kinship information indicating a kinship relationship between users U. FIG. 6 is a diagram showing an example of kinship information. The kinship information is kinship-related information estimated by the estimation unit 31 described later. As shown in FIG. 6, the kinship information includes items such as "user ID", "kinship ID", and "kinship relationship". The “kinship ID” is the identification information (user ID) of the relatives. The "kinship relationship" is a diagram showing a kinship relationship with a kinship person.

The control unit 3 is a controller, and for example, various programs stored in a storage device inside the account management device 1 by a CPU (Central Processing Unit), an MPU (Micro Processing Unit), or the like have a RAM as a work area. It is realized by executing as. Further, the control unit 3 is, for example, a controller, and is realized by an integrated circuit such as an ASIC (Application Specific Integrated Circuit) or an FPGA (Field Programmable Gate Array).

The acquisition unit 30 acquires various types of information. For example, the acquisition unit 30 acquires genetic information. For example, the acquisition unit 30 may collect saliva, a part of the skin, hair, etc. from the user U, and extract the genetic information by a dedicated inspection device. Alternatively, the acquisition unit 30 may acquire the genetic information obtained by requesting the user U to another testing institution. The acquisition unit 30 stores the acquired genetic information in the user information DB 40 of the storage unit 4.

Further, the acquisition unit 30 acquires the user information input by the user U at the time of account creation and stores it in the user information DB 40. Further, the acquisition unit 30 acquires image information including the face of the user U when the user U makes a recovery request.

The estimation unit 31 estimates the kinship relationship between the users U based on the genetic information acquired by the acquisition unit 30. For example, the estimation unit 31 calculates the similarity of genetic information between users and estimates the kinship relationship based on the similarity. The degree of similarity can be calculated based on, for example, the base sequence, the amino acid sequence, the health risk, and the degree of agreement of the constitution.

For example, the estimation unit 31 presumes the kinship relationship before the recovery request is received by the reception unit 33, which will be described later, and sends a pre-certification request to the user U who is presumed to have a kinship relationship. Then, the estimation unit 31 stores the kinship information indicating the kinship relationship in the kinship information DB 42 of the storage unit 4 when the user U who has sent the pre-certification request responds indicating that the kinship relationship is recognized.

In this way, the estimation unit 31 can disperse the processing load by estimating the kinship relationship in advance. Further, by sending a pre-certification request to the user U who has a relative relationship and having the user U confirm the relative relationship in advance, it is possible to reduce the confusion of the second user U when requesting the approval of recovery.

Further, the estimation unit 31 is not limited to estimating the kinship relationship in advance, and may estimate the kinship relationship at the timing when the recovery request is made. Specifically, the estimation unit 31 estimates the kinship relationship based on the genetic information stored in the storage unit 4 when the recovery request is received by the reception unit 33 described later.

In this way, by estimating the kinship relationship only when there is a recovery request, unnecessary estimation processing can be omitted, so that the total processing amount can be reduced.

The management unit 32 manages the account of the user U. Specifically, the management unit 32 issues an account ID and a password when the user U creates an account. Further, the management unit 32 changes the account status of the account information stored in the storage unit 4 according to the login status of the user U.

For example, the management unit 32 changes the account status from "valid" to "expired" when the account ID or password is erroneously entered more than a specified number of times at the time of login. Then, when the recovery of the account is approved by the approval unit 34 described later, the management unit 32 changes the account status from "expired" to "valid", that is, executes the recovery.

If the account status is "expired" and recovery is not approved, the management unit 32 changes from "expired" to "suspended". Alternatively, the management unit 32 changes from "valid" to "suspended" when the account status is "valid", the login has not been performed for a certain period or more, or the account has been illegally used. That is, the account is disabled without granting recovery privileges.

The reception unit 33 receives a recovery request for an account owned by the first user in a predetermined service. For example, when the account status changes from "valid" to "expired", the reception unit 33 sends a confirmation request as to whether or not to execute recovery to the first user U, and executes recovery. Response is accepted as a recovery request.

When the recovery request is received by the reception unit 33, the approval unit 34 makes a recovery approval request for the first user to the second user who has a relative relationship with the first user. For example, the approval unit 34 makes an approval request to a second user who is recognized as having a kinship relationship based on the kinship information stored in the storage unit 4.

Further, each time the approval unit 34 receives the recovery request, when the estimation unit 31 performs the kinship estimation process, the approval unit 34 transmits the approval request to the second user of the kinship relationship estimated from the estimation unit 31.

Further, the approval unit 34 changes the number of second users who send the approval request according to the number of relatives. The number of relatives is the generation difference from the second user based on the generation of the first user. For example, parents and children have a relative number of "1", siblings, grandparents and grandchildren have a relative number of "2", and uncles and aunts have a relative number of "3".

Then, the approval unit 34 issues an instruction to execute the recovery to the management unit 32 when there is a response to approve the recovery from the number of second users corresponding to the number of relatives.

When transmitting a recovery approval request, the approval unit 34 may control to give priority to a second user having a small number of relatives (close to a relative). Further, the approval unit 34 may control approval based on the approval policy, such as giving priority to an older second user when the number of relatives of the plurality of second users is the same.

Further, when making a recovery approval request, the approval unit 34 requests the second user to confirm the identity of the first user. This point will be described with reference to FIG. 7.

FIG. 7 is a diagram showing the processing contents of the approval unit 34. As shown in FIG. 7, the approval unit 34 first acquires image information including the face of the first user when the recovery request is received by the reception unit 33.

Then, the approval unit 34 transmits a confirmation request and an approval request including the image information of the first user to the second user. In the example shown in FIG. 7, the confirmation request includes the content of confirming the person such as "Is this person your brother, Mr. XX?", The content of confirming the kinship relationship, and the like. The approval unit 34 may be provided with means for the second user to confirm that the confirmation request is certainly transmitted from the first user in response to the confirmation request shown in FIG. 7. Specifically, the approval unit 34 may, for example, give the confirmation request a signature of the first user, or may be given secret information that only both the first user and the second user can know. ..

Then, the approval unit 34 responded when "Yes" was selected by the second user, that is, from the second user to the first user himself / herself or having a relative relationship with the first user. If so, send a recovery approval request.

On the other hand, the approval unit 34 responded that when "No" was selected by the second user, that is, the second user was not the first user himself / herself or had no kinship with the first user. If you do not send a recovery approval request.

In this way, the approval unit 34 sends an approval request to the second user after confirming the identity and relatives of the first user, so that the approval request is erroneously transmitted to the second user who is not related to the relatives. It is possible to prevent unauthorized recovery by being done or by a first user impersonating another person.

Further, when the recovery request is received, the approval unit 34 can acquire the current face of the first user as image information by acquiring the image information, so that the identity verification by the second user can be facilitated.

The information acquired at the time of the recovery request is not limited to the image information of the first user, but may be user information such as voice information recorded from the utterance of the first user. Alternatively, the approval unit 34 may send pre-registered registration information such as information previously agreed between the first user and the second user to the second user as a confirmation request.

Further, in FIG. 7, the approval unit 34 has transmitted the confirmation request including the identity confirmation and the kinship confirmation of the first user to the second user, but the confirmation request for the identity confirmation and the kinship confirmation may be transmitted separately. good.

Specifically, the approval unit 34 transmits an identity verification request including user information of the first user to the second user. Then, when the second user responds indicating that he / she is the first user, the approval unit 34 sends a kinship confirmation request to the second user, and the second user has a kinship relationship with the first user. If there is a response indicating that, a recovery approval request is sent. The approval unit 34 may send the kinship confirmation request before the identity verification request. Further, the approval unit 34 may send only one of the identity verification request and the kinship verification request.

Next, the procedure of the process executed by the management system S according to the embodiment will be described with reference to FIG. FIG. 8 is a flowchart showing a procedure of processing executed by the management system S according to the embodiment. The "first user" shown in FIG. 8 indicates the processing of the terminal device 10 possessed by the first user, and the "second user" indicates the processing of the terminal device 10 possessed by the second user.

As shown in FIG. 8, first, the first user (terminal device 10) transmits a recovery request to the account management device 1 (S101). At this time, the first user sends the image information obtained by capturing the face together with the recovery request according to the instruction of the account management device 1.

Subsequently, the account management device 1 estimates the kinship relationship based on the genetic information (S102).

Subsequently, the account management device 1 transmits, as a result of estimation, a kinship confirmation request for confirming the kinship relationship with the first user to the second user (terminal device 10) having a kinship relationship with the first user. (S103). At this time, the account management device 1 transmits user information such as image information of the first user together with a kinship confirmation request.

Then, when the second user has a relative relationship with the first user, the second user transmits a response (approval response) indicating that the second user has a relative relationship with the first user (S104).

Subsequently, the account management device 1 transmits an identity verification request for confirming the identity of the first user to the second user (terminal device 10) (S105).

Then, in the case of the first user himself / herself, the second user transmits a response (approval response) indicating that he / she is the first user himself / herself (S106). The processing order of the kinship confirmation request (S103) and the identity verification request (S105) may be changed.

Subsequently, the account management device 1 transmits a recovery approval request to the second user (S107).

Then, when approving the recovery of the account of the first user, the second user sends an approval response (S108).

Subsequently, the account management device 1 executes recovery of the account of the first user (S109), sends a recovery notification indicating that the recovery is completed to the first user (S110), and ends the process.

Further, the account management device 1 according to the above-described embodiment is realized by, for example, a computer 1000 having a configuration as shown in FIG. FIG. 9 is a hardware configuration diagram showing an example of a computer 1000 that realizes the function of the account management device 1 according to the embodiment. The computer 1000 has a CPU 1100, a RAM 1200, a ROM 1300, an HDD 1400, a communication interface (I / F) 1500, an input / output interface (I / F) 1600, and a media interface (I / F) 1700.

The CPU 1100 operates based on a program stored in the ROM 1300 or the HDD 1400, and controls each part. The ROM 1300 stores a boot program executed by the CPU 1100 when the computer 1000 is started, a program depending on the hardware of the computer 1000, and the like.

The HDD 1400 stores a program executed by the CPU 1100, data used by such a program, and the like. The communication interface 1500 receives data from another device via the network N and sends it to the CPU 1100, and transmits the data generated by the CPU 1100 to the other device via the network N.

The CPU 1100 controls an output device such as a display or a printer, and an input device such as a keyboard or a mouse via the input / output interface 1600. The CPU 1100 acquires data from the input device via the input / output interface 1600. Further, the CPU 1100 outputs the generated data to the output device via the input / output interface 1600.

The media interface 1700 reads a program or data stored in the recording medium 1800 and provides the program or data to the CPU 1100 via the RAM 1200. The CPU 1100 loads the program from the recording medium 1800 onto the RAM 1200 via the media interface 1700, and executes the loaded program. The recording medium 1800 is, for example, an optical recording medium such as a DVD (Digital Versatile Disc) or PD (Phase change rewritable Disk), a magneto-optical recording medium such as MO (Magneto-Optical disk), a tape medium, a magnetic recording medium, or a semiconductor memory. And so on.

For example, when the computer 1000 functions as the account management device 1 according to the embodiment, the CPU 1100 of the computer 1000 realizes the function of the control unit 3 by executing the program loaded on the RAM 1200. Further, the data in the storage unit 4 is stored in the HDD 1400. The CPU 1100 of the computer 1000 reads and executes these programs from the recording medium 1800, but as another example, these programs may be acquired from another device via the network N.

In the above-described embodiment, the case where the account management device 1 according to the embodiment executes account recovery has been described, but the account may be closed, for example.

Specifically, the reception unit 33 of the account management device 1 according to the embodiment receives the account close processing request as an execution request. For example, when the first user himself dies, the account close processing request is received from a third party user or a user other than the first user such as the second user. It should be noted that the closing processing request may be set to be automatically transmitted when the terminal device 10 of the first user is canceled due to death or the like.

Then, when the approval unit 34 receives the close processing request, the approval unit 34 makes an approval request for the closing process to the second user who has a relative relationship with the first user. Then, when the management unit 32 receives the notification from the second user that the closing process is approved, the management unit 32 executes the closing process.

In this way, by estimating the kinship relationship based on the genetic information, for example, if the first user himself suddenly dies in an unexpected accident, the relative (second) will act as a proxy for closing the account of the first user. When it is carried out by the user), it is possible to reduce the labor required for authenticity determination as to whether or not the person is a relative.

In addition to the recovery and closing processes, other procedures such as account registration information change processing, new account registration, and account deletion may be performed.

As described above, the account management device 1 according to the embodiment includes a reception unit 33 and an approval unit 34. The reception unit 33 receives a request for executing the procedure of the account owned by the first user in the predetermined service. When the execution request is received by the reception unit 33, the approval unit 34 makes a procedure approval request to the second user who has a kinship relationship with the first user estimated based on the genetic information.

This makes it possible to improve the convenience of the user U regarding the procedure of the account.

Further, in the account management device 1 according to the above-described embodiment, the reception unit 33 receives the account recovery request as an execution request. The approval unit 34 makes a recovery approval request to the second user.

As a result, it is possible to perform recovery that is highly convenient for the user U.

Further, in the account management device 1 according to the above-described embodiment, the reception unit 33 accepts the account close processing request as an execution request. The approval unit 34 requests the second user to approve the closing process.

As a result, for example, if the first user himself suddenly dies in an unexpected accident, or if a relative (second user) performs the closing process of the account of the first user on behalf of the relative, whether or not the user is a relative. The labor required for authenticity determination can be reduced.

Further, in the account management device 1 according to the above-described embodiment, the approval unit 34 transmits an identity verification request and an approval request including user information of the first user to the second user, and the second user to the first user. If there is a response indicating that you are the person, the procedure will be executed.

As a result, even if a third party impersonates the first user and requests execution, the second user can confirm the identity of the first user and prevent the account procedure from being executed by mistake.

Further, in the account management device 1 according to the above-described embodiment, the approval unit 34 transmits a kinship confirmation request and an approval request including the user information of the first user to the second user, and the second user to the first user. If there is a response indicating that the person is related to the family, the procedure will be executed.

As a result, it is possible to confirm that the second user is a relative, so that a request for approval of the procedure can be reliably transmitted to the second user who is a relative.

Further, in the account management device 1 according to the above-described embodiment, the approval unit 34 uses the user information including at least one of the image information, the audio information, and the pre-registered registration information of the first user as the second user. Send to.

This makes it easy for the second user to confirm the first user.

Further, in the account management device 1 according to the above-described embodiment, the approval unit 34 acquires user information when the execution request is received by the reception unit 33.

As a result, the latest user information can be acquired, so that the confirmation of the first user by the second user can be facilitated.

Further, in the account management device 1 according to the above-described embodiment, the approval unit 34 executes the procedure when there is a response from the second user corresponding to the number of relatives to approve the procedure.

As a result, for example, the larger the number of relatives, that is, the larger the generation difference from the first user and the lower the reliability, the larger the number of approvals can be set, so that the approval accuracy of the procedure can be improved.

Further, the account management device 1 according to the above-described embodiment includes an acquisition unit 30 and an estimation unit 31. The acquisition unit 30 acquires the genetic information for each user. The estimation unit 31 estimates the kinship relationship based on the genetic information acquired by the acquisition unit 30.

As a result, the relative relationship of the user can be estimated with high accuracy, so that the second user who is a relative can be identified with high accuracy.

Further, in the account management device 1 according to the above-described embodiment, the estimation unit 31 estimates the kinship in advance before accepting the execution request, and sends a pre-certification request to the user who is presumed to have the kinship. , When there is a response from the user indicating that the kinship relationship is recognized, the kinship information indicating the kinship relationship is stored in the storage unit 4. The approval unit 34 makes an approval request to the second user who is recognized as having a kinship relationship based on the kinship information stored in the storage unit 4.

As a result, the estimation process for estimating the kinship relationship can be performed in a distributed manner, so that the processing load of the account management device 1 can be reduced.

Further, in the account management device 1 according to the above-described embodiment, the acquisition unit 30 stores the genetic information in the storage unit 4. When the execution request is received by the reception unit 33, the estimation unit 31 estimates the kinship relationship based on the genetic information stored in the storage unit 4.

As a result, since the minimum necessary estimation processing may be performed, it is possible to prevent the total processing amount of the account management device 1 from increasing.

Although some of the embodiments of the present application have been described in detail with reference to the drawings, these are examples, and various modifications are made based on the knowledge of those skilled in the art, including the embodiments described in the disclosure column of the invention. It is possible to carry out the present invention in other modified forms.

Further, among the processes described in the above-described embodiment, all or a part of the processes described as being automatically performed can be manually performed, or the processes described as being manually performed can be performed. All or part of it can be done automatically by a known method. In addition, information including processing procedures, specific names, various data and parameters shown in the above documents and drawings can be arbitrarily changed unless otherwise specified. For example, the various information shown in each figure is not limited to the information shown in the figure.

Further, each component of each of the illustrated devices is a functional concept, and does not necessarily have to be physically configured as shown in the figure. That is, the specific form of distribution / integration of each device is not limited to the one shown in the figure, and all or part of them may be functionally or physically distributed / physically in arbitrary units according to various loads and usage conditions. Can be integrated and configured.

In addition, the processes described in the above-described embodiments can be appropriately combined as long as the processing contents do not contradict each other.

Further, the above-mentioned "section, module, unit" can be read as "means" or "circuit". For example, the approval unit 34 can be read as an approval means or an approval circuit.

1 Account management device 2 Communication section 3 Control section 4 Storage section 10 Terminal device 30 Acquisition section 31 Estimating section 32 Management section 33 Reception section 34 Approval section 100 Service server U User

Claims (13)

The reception unit that accepts the execution request of the procedure of the account owned by the first user in the predetermined service,
When the execution request is received by the reception unit, the reception unit is provided with an approval unit that requests approval of the procedure to a second user who has a relative relationship with the first user estimated based on genetic information. An account management device featuring. The reception department
Accepting the recovery request of the account as the execution request,
The approval department
The account management device according to claim 1, wherein a recovery approval request is made to the second user. The reception department
Accepting the account close processing request as the execution request,
The approval department
The account management device according to claim 1 or 2, wherein the second user is requested to approve the closing process. The approval department
When the identity verification request and the approval request including the user information of the first user are transmitted to the second user and the second user responds indicating that the user is the first user, the said second user. The account management device according to any one of claims 1 to 3, characterized in that the procedure is executed. The approval department
When the kinship confirmation request and the approval request including the user information of the first user are transmitted to the second user, and the second user responds indicating that the kinship is related to the first user. , The account management device according to any one of claims 1 to 4, wherein the procedure is executed. The approval department
According to claim 4 or 5, the user information including at least one of the image information, the audio information, and the pre-registered registration information of the first user is transmitted to the second user. The account management device described. The approval department
The account management device according to any one of claims 4 to 6, wherein when the execution request is received by the reception unit, the user information is acquired. The approval department
The account management device according to any one of claims 1 to 7, wherein the procedure is executed when there is a response from the second user corresponding to the number of relatives to approve the procedure. .. An acquisition unit that acquires the genetic information for each user,
The account management device according to any one of claims 1 to 8, further comprising an estimation unit that estimates the kinship relationship based on the genetic information acquired by the acquisition unit. The estimation unit
Before accepting the execution request, the kinship relationship is estimated in advance, and a pre-certification request is sent to the user who is presumed to have the kinship relationship, and the user responds indicating that the kinship relationship is certified. In that case, the kinship information indicating the kinship relationship is stored in the storage unit, and the kinship information is stored in the storage unit.
The approval department
The account management device according to claim 9, wherein the approval request is made to the second user who is recognized as having a kinship relationship based on the kinship information stored in the storage unit. The acquisition unit
The genetic information is stored in the storage unit,
The estimation unit
The account management device according to claim 9, wherein when the execution request is received by the reception unit, the kinship relationship is estimated based on the genetic information stored in the storage unit. An account management method performed by a computer
The reception process that accepts the execution request of the procedure of the account owned by the first user in the predetermined service,
Includes an approval step of requesting approval of the procedure to a second user who has a kinship relationship with the first user estimated based on genetic information when the execution request is received by the reception step. An account management method that features. The reception procedure for accepting the execution request of the account procedure of the first user in the predetermined service,
When the execution request is received by the reception procedure, the computer is provided with an approval procedure for requesting approval of the procedure to a second user who has a kinship relationship with the first user estimated based on genetic information. An account management program characterized by running.

Images