JP7311548B2 - 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.

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

Japanese Patent No. 6342035

However, the conventional technology has room for improvement in performing recovery that is highly convenient for the user. Specifically, in the conventional technology, since it is assumed that a user possesses a plurality of terminal devices, it cannot be said to be highly convenient for some users who have only one terminal device.

In addition, if the user himself/herself suddenly dies in an unforeseen accident, if a relative closes the user's account, 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, nor was it highly convenient.

SUMMARY OF THE INVENTION It is an object of the present application to provide an account management device, an account management method, and an account management program capable of improving convenience for users regarding account procedures.

An account management device according to the present application includes a reception unit and an approval unit. The reception unit receives a request to execute a procedure for an account owned by a first user in a predetermined service. The approval unit, when the execution request is received by the reception unit, for a second user who is in a blood relationship with the first user estimated based on the utterance information indicating the utterance feature of the first user , make a request for approval of said procedure.

According to one aspect of the embodiment, it is possible to improve convenience for the user regarding account procedures.

FIG. 1 is a diagram illustrating an example of account recovery processing according to an embodiment. FIG. 2 is a diagram showing the configuration of the management system according to the embodiment. FIG. 3 is a block diagram illustrating a configuration example of an 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 consanguinity information. FIG. 7 is a diagram showing the processing contents of the approval unit. FIG. 8 is a flowchart illustrating the 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 implements the functions of the account management device according to the embodiment.

Embodiments for implementing an account management device, an account management method, and an account management program (hereinafter referred to as "embodiments") according to the present application will be described in detail below with reference to the drawings. Note that the account management device, the account management method, and the account management program according to the present application are not limited to this embodiment. Also, in each of the following embodiments, the same parts are denoted by the same reference numerals, and overlapping descriptions are omitted.

First, an example of account recovery processing realized by an account management program according to an embodiment will be described with reference to FIG. FIG. 1 is a diagram illustrating an example of account recovery processing according to an embodiment. FIG. 1 illustrates a recovery process (an example of an account procedure) for requesting approval for recovery of an account from a second user who is related to the first user when the first user's account is invalidated.

It should be noted that the state in which the account is invalidated is, for example, a state in which the corresponding account becomes temporarily unusable if, for example, the password is entered incorrectly more than a specified number of times when logging in to the service.

As shown in FIG. 1, the account management device according to the embodiment first receives voice input from a first user and a second user (S1). Voice input is performed, for example, by the user speaking into a sound collecting device such as a microphone.

The account management device according to the embodiment generates utterance information indicating utterance characteristics for each user as an analysis result of voice input (S2). The utterance information includes, for example, information indicating characteristics of the voice of the user whose voice input is extracted. Specifically, the utterance information includes acoustic patterns, information on physical characteristics based on the acoustic patterns (such as the size of the throat and mouth), and information on characteristics caused by the living environment such as speech speed and intonation. included. Note that the account management device may acquire speech information generated by another analysis agency.

Subsequently, the account management device according to the embodiment estimates the kinship relationship between the first user and the second user based on the utterance information, and generates kinship information (S3). The account management device, for example, generates a model (speaker model) based on the utterance information, and estimates kinship based on the speaker model. Note that the kinship estimation process may be performed in advance, or may be performed at the timing of receiving a recovery request from the user.

Here, it is assumed that the account management device according to the embodiment receives a recovery request (an example of an execution request) for requesting account recovery from the first user whose account has been revoked (S4). When receiving the recovery request, the account management device according to the embodiment identifies the second user who is related to the first user based on, for example, the speaker model (S5).

Then, the account management device according to the embodiment requests the second user, who is related to the first user, to approve execution of the recovery of the account owned by the first user (S6).

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

After the recovery is completed, the account management device according to the embodiment notifies the first user of the recovery completion (S9).

As described above, the account management device according to the embodiment requests recovery approval from the relatives of the first user estimated based on the utterance information. , does not require multiple terminals.

Therefore, according to the account management method according to the embodiment, it is possible to perform recovery with high convenience for the user. In addition, the account management method according to the embodiment can also be applied when other procedures such as closing processing are performed in addition to account recovery. That is, according to the account management method according to the embodiment, it is possible to improve the convenience of the user regarding account procedures.

In addition, by setting the target of the recovery approval request to relatives, the approval request can be sent to the second user who is reliable for the first user whose account has been revoked, so the first user's satisfaction with the service can be improved. can.

In addition, since the kinship relationship is estimated based on the utterance information, it is possible to reduce the possibility that the recovery approval request is erroneously sent to users other than the relatives, thereby reducing the leakage of the user's account to a stranger. .

Next, the system configuration of the management system according to the embodiment will be described using FIG. FIG. 2 is a diagram showing the configuration of the management system according to the 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 via a network N by wire or wirelessly so as to be able to communicate with each other. The network N is, for example, a LAN (Local Area Network) or a WAN (Wide Area Network) such as the Internet. Terminal devices 10-1 to 10-n are operated by users U-1 to Un.

Hereinafter, the terminal devices 10-1 to 10-n are referred to as the terminal device 10 when they are indicated without distinction. Further, service servers 100-1 to 100-m are referred to as service server 100 when they are referred to without distinction, and users U-1 to Un are referred to as user U when they are referred to without distinction. do.

The terminal device 10 is a terminal device of the user U, and is a smart device (communication terminal) such as a smart phone, 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 via the network N from a browser or an application and use services provided by the service server 100 . In addition, 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 user U's operation.

The service server 100 is a server device that provides a predetermined service. Services provided by the service server 100 include, 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.

Note that 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 a single server device that centrally manages the accounts held by each of the plurality of service servers 100-1 to 100-m. It may be a server device.

Next, the configuration of the account management device 1 according to the embodiment will be described using 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 section 2 , a control section 3 and a storage section 4 .

The communication unit 2 is implemented 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 and receives information to and 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 device such as a RAM (Random Access Memory) or a 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 a user information DB 40, an account information DB 41, and a relative information DB 42.

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

As shown in FIG. 4, the user information includes items such as "user ID", "attribute" and "utterance information". “User ID” is identification information for identifying the user U. FIG. "Attribute" is information about attributes of the user U, and includes, for example, demographic attributes and psychographic attributes. The “utterance information” includes, for example, information indicating characteristics of the voice of the user from whom the voice input was extracted. Specifically, the utterance information includes acoustic patterns, information on physical characteristics based on the acoustic patterns (such as the size of the throat and mouth), and information on characteristics caused by the living environment such as speech speed and intonation. included.

It should be noted that the user information shown in FIG. 4 is an example, and may include, for example, user image information acquired when a recovery request is made, which will be described later.

The account information DB 41 contains account information relating to accounts of users who use services. 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".

“Account ID” is identification information issued by the service server 100 for each user U, and is a login ID for logging into the service. Note that the "account ID" may be the "user ID".

"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 a usable state, "Expired" indicates a state that is temporarily unavailable and can be restored to "Valid", and "Suspended" indicates that the Indicates an unrecoverable state. "Suspension" 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.

"Approval status" indicates the status of approval of recovery by the second user, and includes "whether there is a request" and "requester ID". The “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 made the recovery approval request.

The consanguinity information DB 42 includes consanguinity information indicating the consanguinity relationship between the users U. FIG. 6 is a diagram showing an example of consanguinity information. The consanguineous information is information on consanguinity estimated by the estimating unit 31, which will be described later. As shown in FIG. 6, the consanguineous information includes items such as "user ID", "consanguineous ID" and "relative relationship". “Belgium ID” is identification information (user ID) of a relative. "Bangal relationship" is a diagram showing the kinship relationship with relatives.

The control unit 3 is a controller, and various programs stored in a storage device inside the account management device 1 are stored in the RAM by means of, for example, a CPU (Central Processing Unit) or an MPU (Micro Processing Unit). It is realized by executing as Also, the control unit 3 is, for example, a controller, and is implemented 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 speech information. For example, the acquisition unit 30 may extract speech information as an analysis result based on user U's voice input. Alternatively, the acquisition unit 30 may acquire speech information obtained by the user U by requesting another analysis organization. The acquisition unit 30 stores the acquired speech information in the user information DB 40 of the storage unit 4 .

The acquisition unit 30 also acquires user information input by the user U when creating an account, and stores the information 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 estimating unit 31 estimates the kinship relationship between the users U based on the utterance information acquired by the acquiring unit 30 . For example, the estimating unit 31 generates a speaker model for each user based on utterance information for each user, and estimates kinship based on this speaker model.

Specifically, the estimation unit 31 performs machine learning using user information including utterance information, and generates a speaker model, which is a learning model indicating whether or not there is a consanguineous relationship. More specifically, the estimating unit 31 determines, as a learning model, a regression model in which the correctness of the kinship relationship between users is set as the objective variable, and the information of the utterance feature extracted from the user information including the utterance information is used as the explanatory variable. can be done.

In addition, for example, the estimation unit 31 presumes a blood relationship before a recovery request is received by the reception unit 33, which will be described later, and transmits a pre-certification request to the users U who are estimated to be in the blood relationship. Then, the estimating unit 31 stores the consanguineous information indicating the consanguineous relation in the consanguineous information DB 42 of the storage unit 4 when there is a response indicating that the consanguineous relation is approved from the user U who transmitted the pre-certification request.

In this way, the estimating unit 31 can distribute the processing load by estimating the consanguinity relationship in advance. In addition, by transmitting a pre-approval request to the user U who has a blood relationship and confirming the blood relationship in advance, it is possible to reduce the confusion of the second user U when requesting approval for recovery.

In addition, the estimation unit 31 may estimate the blood relationship at the timing when the recovery request is made, instead of presuming the blood relationship in advance. Specifically, the estimation unit 31 estimates the kinship relationship based on the utterance information and the speaker model stored in the storage unit 4 when the reception unit 33 (to be described later) receives a recovery request.

In this way, by estimating consanguinity only when there is a recovery request, unnecessary estimation processing can be omitted, and the overall processing amount can be reduced.

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

For example, the management unit 32 changes the account status from "valid" to "invalid" when the account ID or password is entered incorrectly more than a specified number of times during login. When the approval unit 34, which will be described later, approves the recovery of the account, the management unit 32 changes the account status from "expired" to "valid", that is, executes recovery.

If the account status is "expired" and the recovery is not approved, the management unit 32 changes the account status from "expired" to "suspended". Alternatively, the management unit 32 changes the account status from "valid" to "suspended" when login is not performed for a certain period of time or longer, or when the account is used illegally. In other words, the account is disabled without granting recovery privileges.

The accepting unit 33 accepts a recovery request for an account held by the first user in a predetermined service. For example, when the account status changes from “valid” to “expired”, the reception unit 33 transmits a confirmation request as to whether or not recovery is to be performed to the first user U, and sends a confirmation request to the first user U to indicate that the recovery is to be performed. response is accepted as a recovery request.

When the receiving unit 33 receives the recovery request, the approval unit 34 requests the second user who is related to the first user to approve the recovery of the first user. For example, the approval unit 34 makes an approval request to the second user who has been certified as having a consanguineous relation based on the consanguinity information stored in the storage unit 4 .

In addition, the approval unit 34 transmits an approval request to the second user with the blood relationship estimated by the estimation unit 31 each time the estimation unit 31 performs the blood relationship estimation process each time the estimation unit 31 receives the recovery request.

In addition, the approval unit 34 changes the number of second users to whom the approval request is sent according to the number of relatives. The degree of kinship is the generation difference between the generation of the first user and the second user. For example, parents and children have a kinship number of "1", siblings, grandparents and grandchildren have a kinship number of "2", and uncles and aunts have a kinship number of "3".

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

Note that, when transmitting the recovery approval request, the approval unit 34 may perform control to give priority to the second user having a small degree of kinship (close blood relationship). Furthermore, the approval unit 34 may control approval based on an approval policy, such as prioritizing a second user with a higher age when the number of degrees of kinship among a plurality of second users is the same.

Further, when requesting approval for recovery, the approval unit 34 requests the second user to verify the identity of the first user. This point will be described with reference to FIG.

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

The approval unit 34 then 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 contents such as "Is this person your brother XX?" Note that the approval unit 34 may include means for allowing the second user to confirm that the confirmation request shown in FIG. 7 has indeed been sent from the first user. Specifically, the approval unit 34 may, for example, attach the first user's signature to the confirmation request, or attach secret information that only both the first user and the second user can know. .

Then, when the second user selects "yes", the approval unit 34 receives a response from the second user indicating that the user is the first user or has a blood relationship with the first user. Submit a recovery approval request, if any.

On the other hand, when the second user selects "No", the approval unit 34 receives a response from the second user indicating that the user is not the first user or that the user is not related to the first user. Do not send a recovery approval request if

In this way, the approval unit 34 sends an approval request to the second user after confirming the identity of the first user and the blood relatives of the second user. unauthorized recovery by the first user pretending to be someone else.

In addition, when receiving the recovery request, the approval unit 34 can acquire the current face of the first user as image information by acquiring the image information, thereby facilitating identity verification by the second user.

Information to be acquired at the time of the recovery request is not limited to the first user's image information, and may be user information such as audio information obtained by recording the first user's speech. Alternatively, the approval unit 34 may transmit pre-registered registration information, such as information agreed upon in advance between the first user and the second user, to the second user as a confirmation request.

In addition, in FIG. 7, the approval unit 34 transmits the confirmation request including the first user's identity confirmation and consanguinity confirmation to the second user. good.

Specifically, the approval unit 34 transmits an identity verification request including the user information of the first user to the second user. Then, when there is a response from the second user indicating that the person is the first user, the approval unit 34 transmits a consanguinity confirmation request to the second user, and confirms that the second user has a consanguinity relationship with the first user. If there is a response indicating that it is, send a recovery authorization request. Note that the approval unit 34 may transmit the relative confirmation request before the personal identification request. Also, the approval unit 34 may transmit only one of the identity verification request and the relatives verification request.

Next, a procedure of processing executed by the management system S according to the embodiment will be described with reference to FIG. FIG. 8 is a flow chart showing the procedure of processing executed by the management system S according to the embodiment. Note that "first user" shown in FIG. 8 indicates processing of the terminal device 10 possessed by the first user, and "second user" indicates 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 transmits the face image information together with the recovery request according to the instruction of the account management device 1 .

Subsequently, the account management device 1 presumes kinship based on the speech information (S102).

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

Then, when the second user is related to the first user, the second user transmits a response (approval response) indicating that the second user is related to the first user (S104).

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

Then, when the second user is the first user, the second user transmits a response (approval response) indicating that the user is the first user (S106). It should be noted that the relative confirmation request (S103) and the personal identification request (S105) may be switched in order of processing.

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

Then, if the second user approves the recovery of the first user's account, the second user sends an approval response (S108).

Subsequently, the account management computer 1 recovers the first user's account (S109), transmits a recovery notification indicating that the recovery has been completed to the first user (S110), and ends the process.

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

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

The HDD 1400 stores programs executed by the CPU 1100, data used by the programs, and the like. Communication interface 1500 receives data from other devices via network N, sends the data to CPU 1100, and transmits data generated by CPU 1100 to other devices via network N. FIG.

The CPU 1100 controls output devices such as displays and printers, and input devices such as keyboards and mice, through an input/output interface 1600 . CPU 1100 acquires data from an input device via input/output interface 1600 . CPU 1100 also outputs the generated data to an output device via input/output interface 1600 .

Media interface 1700 reads programs or data stored in recording medium 1800 and provides them to CPU 1100 via RAM 1200 . CPU 1100 loads such a program from recording medium 1800 onto RAM 1200 via 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 a PD (Phase change rewritable disc), a magneto-optical recording medium such as an MO (Magneto-Optical disk), a tape medium, a magnetic recording medium, or a semiconductor memory. etc.

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

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 accepting unit 33 of the account management device 1 according to the embodiment accepts an account closing process request as an execution request. For example, when the first user dies, the account closing processing request is accepted from a third user or a user other than the first user such as a second user. It should be noted that the closing processing request may 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 requests approval of the close processing to the second user who is related to the first user by blood. Then, when the management unit 32 receives a notification from the second user to the effect that the close processing is approved, the management unit 32 executes the close processing.

In this way, by estimating kinship based on genetic information, for example, when the first user himself/herself suddenly dies in an unforeseen accident, the close processing of the first user's account is performed on behalf of relatives (second When performed by the user, it is possible to reduce the labor required for authenticity determination as to whether or not relatives are present.

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

As described above, the account management device 1 according to the embodiment includes the reception unit 33 and the approval unit 34. The accepting unit 33 accepts a request to execute a procedure for an account owned by the first user in a predetermined service. When the acceptance unit 33 accepts the execution request, the approval unit 34 requests approval of the procedure from the second user who is related to the first user and is presumed based on the utterance information.

Thereby, it is possible to improve the convenience of the user U regarding account procedures.

In the account management device 1 according to the above-described embodiment, the accepting unit 33 accepts an account recovery request as an execution request. The approval unit 34 requests the second user to approve the recovery.

As a result, recovery that is highly convenient for the user U can be performed.

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

As a result, for example, when the first user himself/herself suddenly dies due to an unforeseen accident, when a relative (second user) closes the account of the first user on behalf of the first user, it is possible to determine whether the first user is a relative or not. 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 the user information of the first user to the second user. If there is a response indicating that the person is the person, the procedure is executed.

As a result, even if a third person pretends to be the first user and makes a recovery request, the second user can prevent the account from being erroneously executed by verifying the identity of the first user.

Further, in the account management device 1 according to the above-described embodiment, the approval unit 34 transmits a relative confirmation request and an approval request including the user information of the first user to the second user. Execute the procedure if there is a response indicating a consanguineous relationship with

As a result, since the second user can confirm that the second user is a relative, it is possible to reliably transmit a procedure approval request to the second user who is a relative.

Further, in the account management device 1 according to the above-described embodiment, the authorization unit 34 sends user information including at least one of the first user's image information, voice information, and pre-registered registration information to the second user. Send to

This facilitates confirmation of the first user by the second user.

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

Accordingly, since the latest user information can be obtained, confirmation of the first user by the second user can be facilitated.

In addition, in the account management device 1 according to the above-described embodiment, the approval unit 34 executes the procedure when the number of second users corresponding to the number of relatives approves the procedure.

As a result, for example, the higher the degree of kinship, that is, the greater the generation difference with the first user and the lower the reliability, the greater the number of approvals can be set.

Also, the account management device 1 according to the above-described embodiment includes an estimation unit 31 . The estimation unit 31 estimates a kinship relationship based on a speaker model for each user generated based on utterance information for each user.

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

Further, in the account management device 1 according to the above-described embodiment, the estimation unit 31 presumes the blood relationship before accepting the execution request, and transmits the pre-authorization request to the user estimated to be in the blood relationship. , when the user responds to confirm the kinship relationship, 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 has been certified as having a consanguineous relationship based on the consanguinity information stored in the storage unit 4 .

As a result, the estimation processing for estimating consanguinity can be distributed, so that the processing load on the account management device 1 can be reduced.

Also, in the account management device 1 according to the above-described embodiment, the acquisition unit 30 stores the speech information in the storage unit 4 . The estimating unit 31 estimates the kinship relationship based on the utterance information stored in the storage unit 4 when the receiving unit 33 receives the execution request.

As a result, it is possible to prevent the overall processing amount of the account management computer 1 from increasing because it is sufficient to perform the minimum necessary estimation processing.

As described above, some of the embodiments of the present application have been described in detail based on the drawings. It is possible to carry out the invention in other forms with modifications.

Further, among the processes described in the above embodiments, all or part of the processes described as being automatically performed can be manually performed, or the processes described as being performed manually can be performed manually. All or part of this can also be done automatically by known methods. 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 drawing is not limited to the illustrated information.

Also, each component of each device illustrated is functionally conceptual, and does not necessarily need to be physically configured as illustrated. In other words, the specific forms of distribution and integration of each device are not limited to those shown in the figure, and all or part of them can be functionally or physically distributed and integrated in arbitrary units according to various loads and usage conditions. Can be integrated and configured.

Further, each processing described in the above-described embodiments can be appropriately combined within a range that does not contradict the content of the processing.

Also, the "section, module, unit" described above can be read as "means" or "circuit". For example, the approval unit 34 can be read as approval means or approval circuit.

1 account management device 2 communication unit 3 control unit 4 storage unit 10 terminal device 30 acquisition unit 31 estimation unit 32 management unit 33 reception unit 34 approval unit 100 service server U user

Claims (12)

a reception unit that receives a request to execute a procedure for an account owned by a first user in a predetermined service;
requesting approval of the procedure to a second user having a predetermined relationship with the first user estimated based on the information input by the first user when the execution request is received by the receiving unit; an approval department that performs
with
The reception unit
Accepting the account close processing request as the execution request,
The approval unit
An account management device that requests the second user to approve closing processing. The reception unit
accepting a recovery request for the account as the execution request;
The approval unit
2. The account management device according to claim 1 , wherein the second user is requested to approve recovery. The approval unit
Sending the identity verification request and the approval request including the user information of the first user to the second user, and when the second user responds indicating that the identity of the first user is the identity of the first user, the 3. The account management device according to claim 1 or 2 , for executing a procedure. The approval unit
transmitting a relationship confirmation request including user information of the first user and the approval request to the second user, and receiving a response from the second user indicating that the first user has the predetermined relationship with the first user; 4. The account management device according to any one of claims 1 to 3 , wherein said procedure is executed when there is an error. The approval unit
5. The method according to claim 3 or 4 , wherein said user information including at least one of image information, voice information and pre-registered registration information of said first user is transmitted to said second user. Account management device as described. The approval unit
The account management device according to any one of claims 3 to 5 , wherein the user information is obtained when the execution request is received by the receiving unit. The approval unit
The procedure according to any one of claims 1 to 6 , wherein the procedure is executed when a response approving the procedure is received from a number of the second users corresponding to the predetermined degree of relationship. Account management device as described. The account management device according to any one of claims 1 to 7 , further comprising an estimation unit that estimates the predetermined relationship based on a model for each user generated based on the information for each user. . The estimation unit
presuming the predetermined relationship before accepting the execution request, transmitting a pre-approval request to the user presumed to be in the predetermined relationship, and indicating that the predetermined relationship is to be authenticated; storing relationship information indicating the predetermined relationship in a storage unit when a response is received from the user;
The approval unit
9. The account management device according to claim 8 , wherein said approval request is made to said second user who has been identified as having said predetermined relationship based on said relationship information stored in said storage unit. An acquisition unit that acquires the information and stores it in a storage unit,
The estimation unit
9. The account management device according to claim 8 , wherein, when said execution request is accepted by said accepting unit, said predetermined relationship is estimated based on said information stored in said storage unit. A computer-implemented account management method comprising:
a receiving step of receiving a request to execute a procedure for an account held by a first user in a predetermined service;
requesting approval of the procedure to a second user who has a predetermined relationship with the first user estimated based on the information input by the first user when the execution request is received by the receiving step; an approval process for
including
The receiving step includes
Accepting the account close processing request as the execution request,
The approval step includes:
An account management method, comprising: requesting the second user to approve closing processing. a reception procedure for receiving a request to execute a procedure for an account held by a first user in a predetermined service;
requesting approval of the procedure to a second user who has a predetermined relationship with the first user estimated based on the information input by the first user when the execution request is accepted by the accepting procedure; an approval procedure that performs
on the computer, and
The reception procedure includes:
Accepting the account close processing request as the execution request,
The approval procedure includes:
An account management program for requesting the second user to approve closing processing.

Images