KR20230134361A - Method for providing identity verification management service and system thereof - Google Patents

Abstract

The present invention relates to a method and system for providing an identity verification management service that allows users to directly manage settings for arbitrary identity verification procedures. Specifically, the present invention allows the user to directly manage settings related to his or her identity verification process by blocking the identity verification process or monitoring the identity verification process in real time when the user's preset condition(s) are met. It relates to a method and system for providing identity verification management services made possible by.

Description

Method of providing identity verification management service and system therefor {METHOD FOR PROVIDING IDENTITY VERIFICATION MANAGEMENT SERVICE AND SYSTEM THEREOF}

The present invention relates to a method and system for providing an identity verification management service that allows users to directly manage settings for arbitrary identity verification procedures. Specifically, the present invention allows the user to directly manage settings related to his or her identity verification process by blocking the identity verification process or monitoring the identity verification process in real time when the user's preset condition(s) are met. It relates to a method and system for providing identity verification management services made possible by.

The identity verification process is a process that users who wish to use financial services, government services, membership services, etc. must complete before using the service. Authentication can now be easily performed anytime, anywhere, without being limited by time, as long as the user has a terminal equipped with network functions such as a smartphone, desktop, or laptop.

However, the development of information and communication technology has made it possible for users to easily use financial services and government services through user terminals anytime, anywhere. However, illegal activities such as hacking and snooping have also emerged, leading to illegal activities as well. It also comes with problems that can occur anytime, anywhere.

Recently, due to these problems, there is a need for services to monitor in real time whether others are disguising or stealing as users to verify their identity, or to block other people's attempts to verify their identity in advance to prevent users from being harmed financially or mentally. This is coming to the fore.

The technical problem that the present invention aims to solve is to provide a method and system for providing an identity verification management service that links user terminals and identity verification services to allow users to set blocking conditions and prevent identity procedures from being performed if the blocking conditions are met. The purpose is to

Another technical problem that the present invention aims to solve is to provide a method and system for providing an identity verification management service that monitors in real time whether identity verification is attempted and notifies the user through a message when it is detected that an arbitrary identity verification procedure is in progress. The purpose is to

Another technical problem that the present invention aims to solve is to allow users to use the identity verification management service even in the names of others other than themselves, in other words, the user can directly control the settings for the identity verification procedure even in the names of others. The purpose is to make it happen.

Meanwhile, the technical problems of the present invention are not limited to the technical problems mentioned above, and other technical problems not mentioned will be clearly understood by those skilled in the art from the description below.

In order to solve the above problem, the method of providing identity verification management service according to the present invention includes the steps of verifying the user's name information on the identity verification server and then checking whether the user has subscribed to the protection service on the identity verification management server; When it is confirmed that the user has subscribed to the protection service, checking whether the user has set a protection status; After confirming that the user has set the protection status, checking a blocking condition preset by the user; and, if the preset blocking conditions are met, transmitting an identity verification blocking request to the identity verification server.

In addition, in the method of providing the identity verification management service, the preset blocking condition may be at least one of an authentication number condition, an authentication time zone condition, an authentication period condition, a category condition, an authentication method condition, or an overseas authentication condition. .

In addition, the method of providing the identity verification management service includes the steps of monitoring in real time whether identity verification has been attempted after confirming that the user has set the protection status; When an identity verification attempt is received, transmitting an identity verification attempt message - the identity verification attempt message is a message indicating an attempt to verify identity - to the user terminal; When the identity verification attempt message is sent, waiting for a response for a preset time; and when there is no response from the user terminal, sending a blocking request to the identity verification server; may include.

In addition, the method of providing the identity verification management service includes the steps of waiting for a response for a preset time and then sending a blocking message to the user terminal when there is a response from the user terminal; And when a blocking message is received from the user terminal, transmitting a blocking request to the identity verification server may further include.

In addition, the method of providing the identity verification management service may further include constructing at least one of a protection status database (Database) or an identity verification details database (Database).

In addition, in the method of providing the identity verification management service, the protection status database is a database in which the authentication time zone, authentication period, authentication category, authentication method, and overseas authentication information are stored, and the identity verification history database is the title information, authentication occurrence date, and identity information. Verification status - The identity verification status is a state related to identity verification attempt, failure, success, or blocking - It can be characterized as a database in which information is stored.

In addition, the method of providing the identity verification management service includes, after the step of checking whether the user has subscribed to the protection service, when it is confirmed that the user has subscribed to the protection service, a PUSH-type identity verification start request is sent to the identity verification server. transmitting; and, when the user terminal rejects identity verification, transmitting an identity verification blocking request to the identity verification server.

Meanwhile, a method of providing an identity verification management service according to another embodiment of the present invention includes the steps of receiving a target setting request sent by a second terminal to set the first terminal as a target person; After receiving the target setting request, requesting transmission of target verification information to the second terminal; After receiving the subject verification information from the second terminal, verifying the subject verification information; After successfully verifying the subject verification information, generating and storing subject setting information; And after generating and storing the target setting information, sending a message to the second terminal indicating that the first terminal has been set as a target person. may include.

In addition, in the method of providing the identity verification management service, after the step of sending a message to the second terminal that the first terminal has been set as a subject, the first terminal sends a message to the second terminal through the identity verification server for identity verification. Receiving verification information indicating that the title information verification has been performed, and upon receiving the verification information, confirming that the first terminal is a target of the second terminal; may include.

In addition, the method of providing the identity verification management service includes transmitting an identity verification attempt of the first terminal after the step of confirming that the first terminal is a subject of the second terminal when the verification execution information is received. step; It may further include, after the second terminal receives the identity verification attempt from the first terminal, if the second terminal does not allow identity verification by the first terminal, a blocking procedure may be performed. .

According to the present invention as described above, the identity verification management service allows the user to set identity verification blocking conditions and prevents the identity process from taking place if the blocking conditions are met, so even if the user's name or personal information has been stolen, unless the user is the user It can have the effect of blocking identity verification.

In addition, the identity verification management service enables real-time monitoring of identity verification attempts and notifies the user through a message when identity verification is detected, fundamentally preventing the risk of identity theft for users using the identity verification management service. There is a possible effect.

In addition, the identity verification management service is linked with the user terminal and the identity verification service to store and build a database that stores identity verification-related information such as identity verification details, so that users can search for identity verification-related information when they want to. By allowing this, security can be maximized by storing and constructing information related to identity verification, and even if the user has been hacked, the stored information can be used as evidence.

In addition, the identity verification management service can achieve the effect of preventing and managing subjects from abusing or abusing identity verification in advance by providing a service for adding subjects and setting up identity verification.

Meanwhile, the effects of the present invention are not limited to those mentioned above, and other technical effects not mentioned will be clearly understood by those skilled in the art from the description below.

Figure 1 is a diagram briefly showing the conventional identity verification procedure as a flowchart.
Figure 2 is a flowchart showing a method of providing an identity verification management service according to the first embodiment.
Figure 3 is a diagram specifically showing the monitoring process of the identity verification management service according to the first embodiment.
Figure 4 is a diagram specifically showing the identity verification database construction process and utilization of the identity verification management service according to the first embodiment.
Figure 5 is a flowchart showing a method of providing an identity verification management service according to a second embodiment.
Figure 6 is a diagram showing a window or UX/UI displayed on the user terminal according to the process of providing identity verification management service in the second embodiment.
Figure 7 is a flowchart showing a method of providing identity verification management services according to the third embodiment.
Figure 8 is a flowchart showing a method for providing identity verification management services according to the fourth embodiment.
Figure 9 is a flowchart showing a method of providing a target setting service in the identity verification management service according to the fourth embodiment.

Hereinafter, preferred embodiments of the present invention will be described in detail with reference to the attached drawings. The advantages and features of the present invention and methods for achieving them will become clear by referring to the embodiments described in detail below along with the accompanying drawings. However, the present invention is not limited to the embodiments disclosed below and may be implemented in various different forms, and the present embodiments are merely intended to ensure that the disclosure of the present invention is complete and to provide common knowledge in the technical field to which the present invention pertains. It is provided to fully inform those who have the scope of the invention, and the present invention is only defined by the scope of the claims. Like reference numerals refer to like elements throughout the specification.

Unless otherwise defined, all terms (including technical and scientific terms) used in this specification may be used with meanings that can be commonly understood by those skilled in the art to which the present invention pertains. Additionally, terms defined in commonly used dictionaries are not interpreted ideally or excessively unless clearly specifically defined. The terms used in this specification are for describing embodiments and are not intended to limit the invention. As used herein, singular forms also include plural forms, unless specifically stated otherwise in the context.

Terms such as “first” and “second” are used to distinguish one component from another component, and the scope of rights should not be limited by these terms. For example, a first component may be named a second component, and similarly, the second component may also be named a first component.

As used herein, “comprises” and/or “comprising” refers to a referenced component, step, operation and/or element that includes one or more other components, steps, operations and/or elements. Does not exclude presence or addition.

Meanwhile, the present invention is not limited to the specific embodiments and application examples described above, and various modifications may be made by those skilled in the art without departing from the gist of the present invention as claimed in the claims. Of course, it is possible, but these modified implementations should not be understood separately from the technical idea or outlook of the present invention.

Before giving a full explanation of the present invention, we will first briefly explain the process of confirming the user's identity between the conventional user terminal 10 and the identity verification server 200.

The conventional identity verification procedure according to FIG. 1 begins with inputting the user's name information on a website or an application pre-installed on the user terminal 10.

At this time, the title information may include any type of letter, number, or combination thereof that can identify the user of the user terminal 10, such as the user's name or mobile phone number.

If the user enters name information for identity verification, the identity verification server 200 receives the name information directly from the user terminal 10, or acts as a member company that called the identity verification service, or an agency that provides the identity verification service. Afterwards, the identity verification server 200 refers to the name information and compares it with the name information already stored or the name information in the database accessible through inquiry. Perform verification.

If the name information is verified to match, the identity verification server 200 can generate a one-time code (OTP) and transmit it to the user terminal 10. At this time, the one-time code is dynamically generated through a designated code generation rule. It is a code in the form of a random number, and this one-time use code is intended to prevent exposure to danger by repeatedly using the same password.

Meanwhile, the user terminal 10 can transmit the one-time use code received from the identity verification server 200 back to the identity verification server 200 to enable identity verification on the identity verification server 200. At this time, the user terminal 10 can deliver the one-time code (OTP) by entering it on the web or an application, or by using a pass (PASS) method provided by a mobile communication company. On the other hand, if the one-time use code transmitted from the user terminal 10 is different from the one generated by the identity verification server 200, the identity verification will naturally fail. In this way, the identity verification server 200 performs an identity verification procedure by verifying the one-time code received from the user terminal 10.

If the identity verification server 200 verifies the one-time use code from the user terminal 10 and determines that it matches the one previously generated, the identity verification server 200 sends the user's name information to the personal identifier generation server 300. It is requested to generate personal identifiers such as CI (Connecting Information) and I-PIN, which are personal identification information that encrypts the name information, and DI (Duplicate Information), which is information to prevent duplicate registration, and send the result. The identity verification process is completed by receiving and providing the reply. For reference, the personal identifier generation server 300 may in some cases be operated by the same entity as the identity verification server 200, or the personal identifier creation server 300 and the identity verification server 200 may be operated by the same entity. It may be implemented as an integrated system. Meanwhile, if the identity verification server 200 determines that the one-time code does not match as a result of verification, the identity verification server 200 may determine that the identity verification has failed and not proceed with any further procedures.

With reference to FIG. 1, we looked at the authentication procedure between the user terminal 10 and the identity verification server 200 for verifying the identity of a conventional user. Such conventional user identity verification services have been limited to services that are faithful only to the basic function of verifying the user's identity. However, as previously mentioned in the background technology, identity verification is now frequently required in a wide variety of areas and services, so user identity verification is required accordingly. The fatigue of users is considerable, and attempts to steal users' personal information during the identity verification process and to gain unfair advantage through this frequently occur. Now, by breaking away from the traditional simple identity verification service, There is a need to provide a secure and more user-driven identity verification service.

Hereinafter, we will look at embodiments that enable the user to receive services while taking the initiative in the identity verification process by having an identity verification management server 100 in addition to the conventional identity verification server 200.

<First embodiment>

The identity verification management server 100 according to the first embodiment is a server that is linked with the user terminal 10 and the identity verification server 200. The identity verification management server 100 is the user terminal 10 and the identity described above. Intervention may be possible during the verification server 200 authentication process.

For reference, the user terminal 10 mentioned in this detailed description may be any terminal that has a network function, such as a user's desktop computer, smartphone, laptop computer, tablet computer, PDA, PDP, PMP, etc. You can.

Referring again to FIG. 2, the process of providing a service by the identity verification management server 100 is that when the identity verification server 200 first refers to the name information input from the user terminal 10, the name information matches. If verified, it may include a step (S101) of checking whether the user has subscribed to the protection service in the identity verification management server 100. Here, the protection service is a service that protects users from professional hackers or professional groups with similar purposes who try to harm users financially or mentally by having their personal information stolen or information required for identity verification hacked. It is mainly used for identity verification. It is a service that prevents the process from being abused by others and receives blocking conditions from the user to verify again whether the person in progress is the user.

Meanwhile, subscription to the protection service naturally refers to membership registration that the user must perform in advance in order to receive the protection service. If the identity verification management server (100) confirms whether or not the user has subscribed to the protection service, but determines that the user has not subscribed to the protection service, , as shown in Figure 2, the existing identity verification procedure is followed without implementing the protection service, and in more detail, the process moves on to the one-time code generation step of the identity verification server 200.

In addition, if the identity verification management server 100 checks whether the user has subscribed to the protection service (S101) and determines that the user has not subscribed to the protection service, consider the case where the user was not aware of the existence of the identity verification management server 100. Thus, promotional information for promoting the identity verification management server 100 and related services may be delivered to the user terminal 10.

On the other hand, if the identity verification management server 100 checks whether the user has subscribed to the protection service (S101) and it is confirmed that the user has subscribed to the protection service, the process proceeds to the step of checking whether the protection status is set (S102). The protection status settings may be set by the person or user who signed up for the above-mentioned protection service to manage the identity verification service. This includes, for example, the person who is the subject of the identity verification service (self, spouse, immediate descendant, etc.), the person This may include bulk settings of verification services or detailed settings of identity verification services.

Among these, the batch settings of the identity verification service may include protection settings, monitoring settings, or release settings. The protection settings are a setting that blocks attempts to verify identity in the name of the registered target and notifies the blocked details in real time. The monitoring setting may allow the identity verification process to proceed when an identity verification attempt is made in the name of the registered subject, but may be set to notify the result of identity verification in real time, and the off setting may allow the identity verification process to proceed when an identity verification attempt is made in the name of the registered subject. If present, the setting may be to allow this and not share notifications.

In addition, detailed settings for the identity verification service include setting a time zone to activate the identity verification service from a certain start time to an end time, setting a period to control the start date and end date, and specifying a designated category (e.g. identity verification on a financial site, identity verification on a gaming site). Settings by category to activate/deactivate the identity verification service only for (confirmation, etc.), settings by authentication method to enable identity verification only for pre-designated authentication methods (OTP input method, PASS method, etc.), authentication on a daily or monthly basis This may include authentication count settings that set the number of possible times, and overseas authentication protection settings that determine whether to protect against authentication attempts that occur overseas.

Meanwhile, the identity verification management server 100 checks whether the protection status is set (S102), and if it is determined that the user has not set the protection status, the existing identity verification procedure is performed without implementing the protection service as shown in FIG. 2. , and in more detail, it moves on to the one-time code generation step of the identity verification server (200).

In addition, if the protection status is not set, the identity verification management server 100 determines that there may be a situation in which the user accidentally canceled the protection status or did not recognize that the user set the protection status, and periodically sets the protection status. You can make it appear on the screen that it is not working.

On the other hand, if the identity verification management server 100 checks whether the protection status is set and confirms that the user has set the protection status, the identity verification management server 100 proceeds to the step of checking whether the blocking conditions have been previously set by the user. Go (S103).

Here, the preset blocking condition is a condition set by the user who has subscribed to the protection service to perform identity verification only under the conditions desired by the user, and this may be the various types of settings mentioned above. For example, assuming that a user who has experience with personal information theft sets conditions so that two identity verifications can be performed per day, even if the user is the user, once two identity verifications are completed, the identity verification management server starts from the third attempt at identity verification. (100) can block identity verification on its own. For reference, if the user has set the blocking conditions by mistake or changes the blocking conditions due to a change of mind, the user can change the condition settings after going through another identity verification process.

Next, the identity verification management server 100 checks whether the ongoing identity verification process corresponds to the blocking conditions preset by the user (S103), and if it is determined that it does not correspond to the blocking conditions preset by the user, the identity verification server ( 200) proceed with the identity verification process as is.

On the other hand, the identity verification management server 100 checks whether the blocking conditions have been set by the user, and if it determines that the blocking conditions set by the user are met, sending a request to block the identity verification to the identity verification server 200. It moves on to (S104).

The identity verification server 200, which receives the identity verification blocking request from the identity verification management server 100, blocks the identity verification and transmits the blocking result to the user terminal 10.

In addition, if the identity verification management server 100 transmits a request to block identity verification to the identity verification server 200 and the identity verification server 200 that received the blocking request blocks identity verification, the identity verification management server ( 100) stores the blocking details (S105).

The above process is a process in which the identity verification management server 100 determines whether to block or continue identity verification according to the blocking conditions preset by the user, but the identity verification management server 100 itself creates CI (Connecting Information). , It may also play a role in overseeing the completion of identity verification by generating DI (Duplicate Information) and I-PIN. In other words, the identity verification management server 100 not only performs the role of managing the user's identity verification process, but also performs the role of the personal identifier creation server 300, thereby simplifying the identity verification process.

Meanwhile, Figure 3 is a diagram showing the monitoring step (S121), which is a function of one of the protection services of the identity verification management server 100.

The real-time monitoring step (S121) is a process carried out to prevent illegal actions to be performed anytime and anywhere and to protect the user's personal information and property. The monitoring step (S121) will be described in detail below with reference to Figure 3.

The monitoring step (S121) is performed after the protection status setting confirmation step (S102), and is a step that monitors whether an attempt was made to verify identity using the user's name information in real time.

As can be seen in Figure 3, the monitoring step (S121) is a service provided to users who have subscribed to the protection service and set the protection status, but since it is an important step in preventing illegal activities, it is provided to users who have not set the protection service and protection status. It is possible to continuously provide users with information about the importance of the monitoring step (S121) and about illegal activities that occur if the monitoring step (S121) is not set.

Next, when the identity verification management server 100 performs monitoring and detects an attempt to perform identity verification, a step of transmitting an identity verification attempt message (a message indicating that someone is attempting identity verification) to the user terminal 10. (S122) is carried out to confirm that the person attempting to verify identity is the person.

When an identity verification attempt message is transmitted to the user terminal 10, a step (S123) is performed in which the user or the identity verification management server 100 waits for a response to the identity verification attempt message for a preset time.

If there is no response to the identity verification attempt message for a preset time, the identity verification management server 100 determines that a user other than the user attempted to verify identity and requests the identity verification server 200 to block (S104) )do.

On the other hand, if there is a response to the identity verification attempt message within the preset time, a blocking message is sent to the user to determine whether it is the user and whether to block if not the user (S124).

Here, if the user who received the blocking message is the person attempting to verify his or her identity, the user proceeds to the existing identity verification process.

On the other hand, if the user who received the blocking message sends a message to the identity verification management server (100) informing him that the person trying to verify his identity is not him and requesting to block it, the identity verification management server (100) sends the identity verification server (200) ), request to block the identity verification procedure (S104).

Meanwhile, Figure 4 is a diagram showing the identity verification database (Data Base) construction step (S131), one of the functions of the protection service of the identity verification management server 100.

To put it simply, the stage of building an identity verification database (Data Base) is a relationship that collects and stores information about the identity verification process, number of times it was performed, number of attempts, etc., and builds a database so that users can later search for the information. .

The identity verification database construction step (S131) may include the process of building a database by dividing it into two databases: a protection settings status database and an identity verification history database. The protection settings status database may be a database that stores the blocking conditions set by the user to block identity verification if the blocking conditions are met in the step of checking whether the blocking conditions previously set by the user (S105). The identity verification history database contains information about the website or app authenticated by the user (URL, name, etc.), date and time of authentication, date and time of authentication, period of authentication by the user, which category the authentication was made in, and what authentication method. It may be a database on whether certification was achieved using this method or whether overseas certification was implemented.

In these databases, when a user requests to search for identity verification information from the user terminal 10, the identity verification management server 100 transmits the identity verification information stored in the database (S132) to search the information desired by the user. It allows you to

<Second Embodiment>

The method of providing the identity verification management service according to the second embodiment is a method in which the user receives confirmation in advance from the user terminal whether identity verification is approved. An easy example is to provide a PUSH type identity verification service (200; e.g. PASS application) to the user terminal 10. This is a service that receives an identity verification request and PUSH (authentication is completed by simply entering the preset password) and displays a window asking whether to approve the identity verification.

According to Figure 5, the start of this service is after the step (S101) of checking whether the user has subscribed to the protection service of the identity verification management server 100, the identity verification management server 100 allows the user to subscribe to the protection service. If it is determined that the process has been completed, the process begins with the step (S141) of transmitting a PUSH-type identity verification start request to perform the PUSH-type identity verification procedure to the PUSH-type identity verification server 200.

When the PUSH-type identity verification server 200 receives a request to start PUSH-type identity verification from the identity verification management server 100, a procedure is performed to check whether the user has joined the PUSH-type identity verification server 200.

If the user has not signed up for the PUSH type identity verification server 200, identity verification fails or the user is encouraged to use another identity verification server 200.

On the other hand, if the user has signed up for the PUSH-type identity verification server 200, the identity verification server 200 sends the user's pre-set password to the PUSH-type identity verification server 200 using the PUSH method. An identity verification request is sent so that you can verify your identity by inputting it.

When the user terminal 10 receives an identity verification request from the identity verification service, a window asking whether to approve the identity verification is displayed at the same time, as shown in (a) of FIG. 6.

When the user touches or clicks the identity verification approval window to respond to whether to approve identity verification, the site where identity verification is required is presented, as shown in (b) of Figure 6, and a question about whether to approve or block identity verification is displayed. UX/UI is displayed and a response is received as to whether the user has verified his or her identity.

If the user approves the identity verification, the PUSH-type identity verification server 200 receives the user's approval and transmits the approval to the personal identifier generation server 300.

Subsequently, when the personal identifier generation server 300 receives approval from the PUSH-type identity verification server 200, the personal identifier creation server 300 generates a personal identifier and sends the personal identifier to the PUSH-type identity verification server 200. When transmitted to , the identity verification server 200 receives it and successfully processes the identity verification.

On the other hand, when the user blocks identity verification, the user terminal 10 notifies the identity verification management server 100 of the fact that the user's identity verification has been blocked, and the identity verification management server 100 sends the identity verification server 200 to the identity verification server 200. A request to block confirmation is sent (S104). The identity verification server 200, which receives the identity verification blocking request, blocks the identity verification.

<Third Embodiment>

The method of providing an identity verification management service according to the third embodiment is that a second user using the identity verification management server 100 sets the first user as a subject, and the second user intervenes in the process of identity verification by the first user as the subject. This is a target setting service designed to enable this. As an easy example, the second user is a user using the second terminal 12, the first user is a user using the first terminal 11, the second user is the first user's guardian, and the first user is the first user. 2 Assuming that it is the user's child, the guardian intervenes in the child's identity verification process to prevent abuse or abuse of the child's identity verification or hacking that the child may be subjected to, and blocks it in advance or allows identity verification. This is a service that can be used.

For reference, the first and second terminals referred to herein may be smartphones, desktop computers, laptop computers, tablet computers, etc. used by individual users, and in addition to these, terminals with network functions. If so, it can be the first or second terminal regardless of its type.

In addition, in the target setting service of the identity verification management service according to the third embodiment, the second terminal 12 sets the first terminal 11 as a target, and in the process of the first terminal 11 attempting to verify the identity, the second terminal (12) is involved and explains that the second user manages the identity verification process of the first user, but since the first user may not own the terminal or the terminal may not have been activated, the subject according to the third embodiment The setting service is not limited to being performed only through the terminal, and the person attempting to verify his or her identity may attempt to verify his or her identity because a third party user other than the first or second user may attempt to verify his or her identity using the first user's name information. Those who wish to do so are not limited to the first user (target). In summary, the identity verification management service according to the third embodiment allows the second user, who has set the first user as the target user, to use the first user's name information to prevent the name information of the first user set as the target user from being inappropriately used or stolen. We emphasize once again that this is a service to protect, manage, and control the use of the service.

Meanwhile, in order to help understand the target setting service, Figure 7 is explained on the assumption that the first user and the second user own the first and second terminals, respectively, and that the person attempting to verify their identity is the first user.

According to Figure 7, this service is started when the second terminal (12, for example, can be seen as a guardian terminal) wants to set the first terminal (11, for example, can be seen as a child's terminal) as the target. It begins with a step (S151) of transmitting a target setting request to the identity verification management server 100.

The identity verification management server 100, which has received the target setting request from the second terminal 12, sends the target verification information to the target to verify whether the second terminal 12 and the first terminal 11 can be set as the target. Request transmission of verification information (S152).

Here, as an easy example, the target person can be a minor in need of protection and management, and the person who wants to set up the target person can be a legal representative who can protect and manage the minor. In this way, the target verification information is information that can be used to verify whether the person who wants to set up the target is qualified to set the target as the target.

Subsequently, the second terminal 12, which has received the subject verification information from the identity verification management server 100, sends the subject verification information to the person in order to verify that the first terminal 11 is the subject of the second terminal 12. It is sent to the patient management service (100).

When the identity verification management server 100 receives subject verification information from the second terminal 12, it verifies based on the subject verification information whether the second terminal 12 can set the first terminal 11 as a subject. (S153), if verification fails, the fact that verification has failed is sent to the second terminal 12 through a message, and if verification succeeds, information that the second terminal 12 has set the first terminal 11 as the target is sent. Create target setting information and store it (S154).

In this way, when the second terminal 12 creates and stores target setting information, which is information that the first terminal 11 has been set as a target, the first terminal 11 creates the target setting information through the identity verification management server 100. This means that the target of the second terminal 12 has been set, and the first terminal 11 transmits the fact that the target of the second terminal 12 has been set to the second terminal 12 through a message (S155).

We have looked at the target setting process according to the third embodiment. Hereinafter, when the first terminal 11 attempts identity verification after target setting is completed, the second terminal 12 and the identity verification management server 100 We will explain in detail how the process is carried out.

When the first terminal 11, which is set as the target of the second terminal 12, enters name information into the first terminal 11 to verify identity and attempts to verify the name information on the identity verification server 200, the identity Since the verification server 200 is linked to the identity verification management server 100, it transmits verification execution information indicating that the first terminal attempted to verify title information to the identity verification management server 100, and the identity verification management server 100 ) receives the verification execution information (S156).

When the identity verification management server 100 receives verification execution information from the identity verification server 200 (S156), the identity verification management server 100 uses the previously stored target setting information to first terminal (11). ) is confirmed to be the target of the second terminal 12 (S157).

When the identity verification management server 100 confirms that the first terminal 11 is the target of the second terminal 12, the identity verification of the first terminal 11 is performed to notify the second terminal 12 of this fact. The attempt is sent through a message (S158).

Subsequently, when the second terminal 12 receives the first terminal's identity verification attempt message from the identity verification management server 100, the second terminal 12 allows the first terminal 11 to perform identity verification. Decide whether to allow it or not to allow identity verification.

If the second terminal 12 allows identity verification by the first terminal 11, information indicating that identity verification of the first terminal 11 has been permitted is transmitted to the identity verification management server 100 to confirm the identity of the first terminal 11. The verification management server 100 performs the existing authentication procedure for the first terminal 11.

On the other hand, if the second terminal 12 does not allow the first terminal 11 to verify the identity, information indicating that the first terminal 11 has not been permitted to verify the identity is transmitted to the identity verification management server 100 to verify the identity of the first terminal 11. The confirmation management server 100 performs the existing blocking procedure for the first terminal 11.

<Fourth Embodiment>

The method of providing the identity verification management service according to the fourth embodiment is to prevent other users from opening a portable terminal through the mobile carrier server 400 with the user's name information, and the identity verification management server 100 protects and blocks this. It is a service that provides

Looking at the specific process of the method for providing identity verification management services according to the fourth embodiment, first, the mobile carrier server 400 begins with receiving the user's name information.

When the mobile communication company server 400 receives the user's name information, the mobile communication company server 400 at this time has no way of knowing whether the received user's name information was sent from another user or the user himself. If the user name information is transmitted from another user, the mobile carrier server 400 must block the opening procedure, and even if the user name information is transmitted from another user, there may be cases where the user himself is unable to open the service due to certain reasons, resulting in the user Since another user may have requested that the service be opened on behalf of the user, in order for the mobile carrier server (400) to properly determine this situation, the protection of the identity verification management server (100), which allows the user to proactively manage and control identity verification, is required. Active intervention in services is necessary.

Therefore, when the mobile communication company server 400 receives the user's name information, it transmits a request to the identity verification management server 100 to confirm whether the user is subscribed to the protection service of the identity verification management server 100. .

When the identity verification management server 100 receives a request to confirm whether to subscribe to the protection service from the mobile carrier server 400, the identity verification management server 100 checks whether to subscribe to the protection service (S161).

If the identity verification management server 100 determines that the user has not subscribed to the protection service as a result of checking whether the user has subscribed to the protection service, it sends a response to the mobile carrier server 400 that it is okay to proceed with the opening procedure as is.

On the other hand, if it is determined that the user has subscribed to the protection service, the identity verification management server 100 checks whether the user has set the protection status (S162).

If it is confirmed that the user has not set the protection status, the identity verification management server 100 transmits a request to the mobile carrier server 400 to proceed with the opening procedure as is, and if the user has set the protection status, the user has already set the protection status. Check whether the blocking conditions are met (S163). At this time, the preset blocking condition will naturally be a blocking condition related to the mobile carrier server 400, that is, a blocking condition related to terminal activation.

Next, the identity verification management server 100 checks whether the blocking conditions have been preset by the user, and if the conditions are not preset, it transmits a request to the mobile carrier server 400 to perform the opening procedure as is, and the preset conditions are not met. If the blocking conditions are met, a request to block the connection is sent to the mobile carrier server 400 (S164).

When the identity verification management server 100 transmits a request to block the opening to the mobile communication company server 400 and the mobile communication company server 400 receives it and blocks the opening, the identity verification management server 100 blocks the opening. Save the details (S165).

To summarize the method of providing the identity verification management service according to the fourth embodiment, the identity verification management server 100 not only protects and manages the identity verification process of the identity verification server 200, but also protects and manages the identity verification process of the identity verification server 200. The opening process can be protected and managed. In addition, the identity verification management server 100 is widely known in the technical field to which the present invention belongs, as well as the identity verification server 200 and the mobile carrier server 100 discussed above, so that the user's name information is transmitted and received from other users and the user's name is confirmed. It can also be used on servers that can be hijacked.

Meanwhile, Figure 9 is a diagram showing how the target setting service is utilized in the method of providing identity verification management services according to the fourth embodiment. In other words, when the first user set as a target by the second user or a third-party user who wishes to open the service in the name of the first user attempts to open the service through the mobile carrier server 400, the identity verification management server 100 2 This is a diagram that specifically shows the process of notifying the user of this fact so that the first user can manage the use of the title information.

Looking in detail at the target setting service of the identity verification management service according to the fourth embodiment with reference to FIG. 9, first of all, assuming that the second user has set the first user as the target, the first user (subject) or another user It begins with the user transmitting the first user's name information to the mobile carrier's server 400 for the purpose of opening, and at this time, a third-party user steals the name of the first user, not the first or second user, to open the service. This person may be said to be a person who transmits the first user's name information to the mobile carrier server 400 for the purpose of doing so.

When the first user or a third-party user transmits the first user's name information to the mobile carrier server 400, the mobile carrier server 400 verifies the first user's name information and manages identity verification with the information that verification has been performed. Transmitted to server 100.

When the mobile carrier server 400 transmits the verification execution information to the identity verification management server 100, the identity verification management server 100 receives the verification execution information (S171), and the first user is the subject of the second user. Confirm that it is (S172).

When the identity verification management server 100 confirms that the first user is the target of the second user, the identity verification management server 100 attempts to verify the first user's title information and attempts to open the service using the title information. The fact is transmitted to the second user (S173).

When the identity verification management server 100 notifies the second user that the first user attempted to open the service using the title information, the second user determines whether to allow the opening using the title information.

If the second user is notified by the identity verification management server (100) that the first user attempted to open the service using name information and allows the use of the first user's name information, the identity verification management server (100) The server 400 performs the existing opening procedure, and if the second user does not allow the use of the first user's name information, the identity verification management server 100 allows the mobile carrier server 400 to perform the existing opening blocking procedure. Let it be implemented.

We have looked at all examples of how to provide identity verification management services.

Meanwhile, the present invention is not limited to the specific embodiments and application examples described above, and various modifications may be made by those skilled in the art without departing from the gist of the present invention as claimed in the claims. Of course, it is possible, but these modified implementations should not be understood separately from the technical idea or outlook of the present invention.

User terminal (10)
1st terminal (11)
Second terminal (12)
Identity verification management server (100)
Identity verification server (200)
Personal identifier generation server (300)
Mobile carrier server (400)

Claims (10)

In the method of the identity verification management server providing identity verification management service,
Confirming whether the user subscribes to the protection service on the identity verification management server;
When it is confirmed that the user has subscribed to the protection service, checking whether the user has set a protection status;
After confirming that the user has set the protection status, checking a blocking condition preset by the user; and
If the preset blocking conditions are met, sending an identity verification blocking request to the identity verification server;
Including,
How to provide identity verification management service.
According to claim 1,
The preset blocking condition is characterized in that it is at least one of an authentication number condition, an authentication time zone condition, an authentication period condition, a category condition, an authentication means condition, or an overseas authentication condition.
How to provide identity verification management service.
According to paragraph 1,
After confirming that the user has set the protection status,
Monitoring in real time whether identity verification has been attempted;
When an identity verification attempt is received, transmitting an identity verification attempt message - the identity verification attempt message is a message indicating an attempt to verify identity - to the user terminal;
When the identity verification attempt message is sent, waiting for a response for a preset time; and
If there is no response from the user terminal, sending a blocking request to the identity verification server;
Including,
How to provide identity verification management service.
According to paragraph 3,
After waiting for a response for a preset time,
When there is a response from the user terminal, sending a blocking message to the user terminal; and
When receiving a blocking message from the user terminal, sending a blocking request to the identity verification server;
Containing more,
How to provide identity verification management service.
According to paragraph 1,
Protection status database (Database),
Or building at least one of the identity verification details database (Database);
Containing more,
How to provide identity verification management service.
According to clause 5,
The protection status database is a database in which authentication time zone, authentication period, authentication category, authentication method, and foreign authentication information are stored, and the identity verification history database includes title information, authentication occurrence date, and identity verification status - the identity verification status is identity verification. States related to attempt, failure, success, and blocking - characterized as a database in which information is stored,
How to provide identity verification management service.
According to claim 1,
After confirming whether the user has subscribed to the protection service,
When confirming that the user has subscribed to the protection service, transmitting a PUSH-type identity verification start request to the identity verification server; and
If the user terminal rejects identity verification, sending an identity verification blocking request to the identity verification server;
Including,
How to provide identity verification management service.
In the method of the identity verification management server providing identity verification management service,
Receiving a target setting request sent by the second terminal to set the first terminal as a target;
After receiving the target setting request, requesting transmission of target verification information to the second terminal;
After receiving the subject verification information from the second terminal, verifying the subject verification information;
After successfully verifying the subject verification information, generating and storing subject setting information; and
After generating and storing the target setting information, sending a message to the second terminal indicating that the first terminal has been set as a target person;
Including,
How to provide identity verification management service.
According to clause 8,
After sending a message to the second terminal that the first terminal has been set as a target,
Receiving verification information that the first terminal has performed the name information verification through the identity verification server to verify identity, and
Upon receiving the verification execution information, confirming that the first terminal is a target of the second terminal;
Including,
How to provide identity verification management service.
According to clause 9,
When receiving the verification execution information, after confirming that the first terminal is the target of the second terminal,
transmitting an identity verification attempt of the first terminal;
It further includes,
After the second terminal receives the identity verification attempt from the first terminal,
Characterized in executing a blocking procedure if the second terminal does not allow identity verification of the first terminal,
How to provide identity verification management service.