KR20200019909A - System for Authentication a Caller and a Recipient based Authentication Contents - Google Patents

Abstract

Disclosed is an authentication system capable of authenticating a caller and a recipient, comprising: a calling terminal for sending a call requesting a call; a receiving terminal for receiving the call from the calling terminal; and an authentication server capable of authenticating whether the calling terminal is a legitimate caller and authenticating whether the receiving terminal is a legitimate recipient.

Description

System for Authentication a Caller and a Recipient based Authentication Contents}

The present invention relates to an authentication system capable of authenticating sender and receiver based on authenticated content and a mobile terminal used therein.

Recently, with the rapid development of communication technology, the use of mobile terminals (for example, smartphones) has been rapidly spread to become an essential means in modern life.

Furthermore, as financial transactions are also possible using mobile terminals, cases of leaking personal information such as smishing and using it for crime have been reported.

On the other hand, techniques for preventing such crimes, such as Korean Patent Publication No. 2013-0026265 (March 13, 2013) or Korean Patent Registration No. 1321721 (October 18, 2013) are published and However, there are still increasing cases of damage caused by crimes such as smishing.

According to an embodiment of the present invention, there is provided an authentication system capable of authenticating a sender and a receiver based on authenticated content, and a mobile terminal used therein.

 According to one embodiment of the invention, authentication that can prevent crimes (eg, voice phishing), such as attempts to leak personal information or direct cash taking, impersonating an agency such as a government office (police, fire department, etc.) or a bank. Provided is an authentication system capable of content-based sender and receiver authentication and a mobile terminal used therein.

According to an embodiment of the present invention, by displaying the authentication result of the sender or the receiver with the authentication content such as a video or a still image authentication system capable of authenticating the sender and the receiver capable of intuitively confirming whether the caller or the receiver is a legitimate sender or legitimate receiver. And a mobile terminal used therefor.

According to an embodiment of the present invention, even if an unjust caller modulates his / her phone number, there is provided an authentication system and mobile terminal used therefor that can accurately authenticate callers.

In the authentication system capable of sender and receiver authentication,

An originating terminal that originates a call requesting a call;

A receiving terminal for receiving the call from the calling terminal;

If there is a caller authentication request from the receiving terminal, it authenticates whether the calling terminal is a legitimate sender (called 'caller authentication'), and if there is a receiver authentication request from the calling terminal, it verifies whether the receiving terminal is a legitimate receiver ('receiver). Authentication server); And

Further comprising a authentication content providing server,

The authentication server

If the receiver determines that the receiver is a legitimate user, requesting the authentication content providing server to transmit the authentication content corresponding to the user of the receiving terminal to the calling terminal, and performing the calling party authentication operation. As a result, if it is determined that the caller is a legitimate user, the authentication system for authenticating the sender and the receiver, characterized in that the request for sending the authentication content corresponding to the user of the calling terminal to the receiving terminal.

According to one or more embodiments of the present invention, when there is a call attempt from the caller, the caller may be authenticated before the call, and thus, attempts to leak personal information impersonating an institution such as a government office (police, fire department, etc.) or a bank. And crimes such as direct cash takeover (eg, voice phishing) can be prevented.

According to one or more embodiments of the present invention, when there is a call attempt from the caller, the receiver may intuitively confirm whether the caller is a legitimate caller by displaying the authentication result of the caller before the call as authentication content such as a video or a still image. Will be. Therefore, even those with weak security, such as the elderly, can easily identify whether the legitimate caller.

According to one or more embodiments of the present invention, even if an unjust caller modulates his / her phone number, the caller can be correctly authenticated.

According to one or more embodiments of the present invention, when attempting a call to a recipient suspected to be unjust, the recipient may be authenticated before the call, thus impersonating an institution such as a government office (police, fire department, etc.) or a bank. It is possible to prevent crimes (e.g. voice phishing) such as attempts to leak personal information or direct cash taking.

According to one or more embodiments of the present invention, when attempting a call to a recipient suspected to be unjust, the sender is intuitively legitimate by displaying the authentication result for the recipient before the call as authentication content such as a video or still image. You can check whether it is the receiver. Therefore, even those with weak security, such as the elderly, can be easily identified as a legitimate recipient.

1 is a view illustrating an authentication system capable of authenticating a sender and a receiver according to an embodiment of the present invention.
FIG. 2 is a diagram for describing a caller authentication operation performed by the system of FIG. 1.
3 is a view for explaining a receiver authentication operation performed by the system of FIG.
4 is a diagram illustrating an authentication system capable of authenticating a sender and a receiver according to another embodiment of the present invention.
FIG. 5 is a diagram for describing a caller authentication operation performed by the system of FIG. 4.
6 is a view for explaining a receiver authentication operation performed by the system of FIG.
7 is a view for explaining a mobile terminal according to an embodiment of the present invention.
FIG. 8 is a view for explaining an operation when a call comes to a receiving terminal from an illegal sender ('criminal') in the authentication system according to the embodiment described with reference to FIGS. 1 and 2.
FIG. 9 is a view for explaining an operation when a calling terminal calls an unjustified receiver ('criminal person') in the authentication system according to the embodiment described with reference to FIGS. 1 and 3.

The above objects, other objects, features and advantages of the present invention will be readily understood through the following preferred embodiments associated with the accompanying drawings. However, the present invention is not limited to the embodiments described herein and may be embodied in other forms. Rather, the embodiments introduced herein are provided so that the disclosure may be made thorough and complete, and to fully convey the spirit of the invention to those skilled in the art.

Where the terms first, second, etc. are used herein to describe the components, these components should not be limited by these terms. These terms are only used to distinguish one component from another. The embodiments described and illustrated herein also include complementary embodiments thereof.

In this specification, the singular also includes the plural unless specifically stated otherwise in the phrase. As used herein, the words "comprise" and / or "comprising" do not exclude the presence or addition of one or more other elements.

Hereinafter, the present invention will be described in detail with reference to the accompanying drawings. In describing the specific embodiments below, various specific details are set forth in order to explain the invention more specifically and to help understand. However, one of ordinary skill in the art can understand that the present invention can be used without these various specific details. In some cases, it is mentioned in advance that parts of the invention that are commonly known and do not relate to the invention are not described in order to avoid confusion in describing the invention.

1 is a diagram illustrating an authentication system capable of authenticating a sender and a receiver according to an embodiment of the present invention, FIG. 2 is a diagram illustrating a caller authentication operation performed by the system of FIG. 1, and FIG. 1 is a view for explaining a receiver authentication operation performed by the system of FIG.

Referring to FIG. 1, an authentication system capable of authenticating a sender and a receiver according to an embodiment of the present invention (hereinafter, the present authentication system) includes a mobile terminal 10, an authentication content providing server 20, and an authentication server 30. ), And the mobile terminal 40.

The present authentication system can authenticate whether the recipient is a legitimate recipient ('recipient authentication') and can authenticate whether the sender is a legitimate sender ('caller authentication').

In the present authentication system, when it is determined that the receiver is a legitimate user, the authentication server requests the authentication content providing server to transmit the authentication content corresponding to the user of the receiving terminal to the calling terminal. As a result of performing the authentication operation, if it is determined that the caller is a legitimate user, the authentication server requests the authentication content providing server to transmit the authentication content corresponding to the user of the calling terminal to the receiving terminal.

The authentication server 30 may perform a sender authentication operation upon receiving a sender authentication request from a receiving terminal, and may perform a receiver authentication operation upon receiving a receiver authentication request from a calling terminal. Hereinafter, with reference to FIGS. 1 and 2, the caller authentication operation will be described first.

Caller authentication

According to the present embodiment, the mobile terminal 40 (hereinafter referred to as 'calling terminal') sends a call ('call connection request') requesting a call to the mobile terminal 10 (hereinafter referred to as 'receiving terminal'), Simultaneously with or after the call connection request, the sender (calling terminal 40) transmits a 'call attempt notification' to the authentication server 30 for notifying that the receiving terminal 10 is trying to connect.

 According to the present embodiment, when the receiving terminal 10 receives a call from the calling terminal 40, an authentication request to the authentication server 30 to confirm whether the calling terminal 40 is a legitimate caller ('caller authentication request'). ')can do.

The authentication server 30 performs an operation of checking whether the calling terminal 40 is a legitimate caller ('caller authentication'), and if the legitimate caller is authenticated, the authentication content providing server 20 authenticates the legitimate caller. Request to transmit the content to the receiving terminal (10).

The authentication content providing server 20 transmits the authentication content corresponding to the legitimate sender to the receiving terminal 10 in response to the request of the authentication server 30. On the other hand, when the authentication server 30 determines that the calling terminal 40 is not a legitimate caller or is a legitimate caller, the authentication server 30 is in doubt whether it is a legitimate caller or a legitimate caller. 'May transmit the authentication result to the receiving terminal 10.

According to the present embodiment, the originating terminal 40 sends a call attempt notification (to indicate that a call is being made with the receiving terminal) to the authentication server 30 at the same time as the originating call, or after transmitting the call. You can send a call notification.

According to the present embodiment, the receiving terminal 10 may include an app for requesting authentication and displaying authentication content. A more detailed description of the receiving terminal 10 will be described with reference to FIG. 5 to be described later.

The authentication request transmitted by the receiving terminal 10 to the authentication server 30 may include information necessary for authentication ('authentication information'). The authentication information may include, for example, sender identification information and receiver identification information.

The caller identification information may include a key generated from the telephone number of the calling terminal 40 or the telephone number of the calling terminal 40 ('caller identification key'). Here, the caller identification key uniquely corresponds to the telephone number of the caller terminal 40.

The receiver identification information may include a key generated from the telephone number of the receiver terminal 10 or the telephone number of the receiver terminal 10 ('key for identification of the receiver'). Here, the recipient identification key uniquely corresponds to the telephone number of the reception terminal 10.

On the other hand, in the above-described embodiment, when the caller identification key or the caller identification key is used, since the authentication server 30 does not need to store the caller's telephone number or the recipient's telephone number, there is no risk of personal information leaking. have.

According to the present embodiment, when the calling terminal 40 transmits a call to the receiving terminal 10, the authentication server 30 indicates that the self (calling terminal 40) is trying to call the receiving terminal 10. (This action is hereinafter referred to as call notification).

According to the present embodiment, the call attempt notification includes authentication information necessary for authenticating that the calling terminal 40 is a legitimate recipient, and the authentication information may include caller identification information and receiver identification information, for example. Since the sender identification information and the receiver identification information have been described above, they will be omitted here.

According to the present embodiment, the calling terminal 40 includes an app for performing a call attempt notification operation, and the app may be loaded and operated in a memory under the control of a computer processor.

The call attempt notification that the calling terminal 40 sends to the authentication server 30 may include, for example, caller identification information and receiver identification information.

According to one embodiment, the authentication server 30 is authenticated caller DB? It is possible to store and manage identification information (list of caller's phone numbers or keys corresponding to caller's phone number ('caller identification key')) for authenticated callers as legitimate callers.

According to the present embodiment, when the authentication server 30 receives an authentication request from the receiving terminal 10, the authentication server 30 performs an authentication operation by using the method illustrated in FIG. 2 (hereinafter, 'first caller authentication method'). Can be done.

Referring to FIG. 2, the first sender authentication method will be described. The authentication server 30 determines whether the caller's identification information (for example, the caller's phone number or caller identification key) is included in the 'authorized caller DB'. If the identification information of the caller is included in the 'authenticated caller DB', it is determined whether there is a call attempt notification from the calling terminal 40. The authentication server 30 determines that the caller's identification information is included in the 'authenticated caller DB', and if there is a call attempt notification from the caller terminal 40, the caller is a legitimate person. In the first sender authentication method, the caller's identification information (for example, the caller's telephone number or caller identification key) is not included in the 'authenticated caller DB', or the caller's identification information (for example, If the caller's telephone number or caller identification key) is included in the 'authenticated caller DB', but there is no call attempt notification from the calling terminal 40, the caller is determined to be an invalid caller.

On the other hand, the authentication server 30 may perform an authentication operation using another method.

As an example of another method (hereinafter, 'second caller authentication method'), when the authentication server 30 receives an authentication request from the receiving terminal 10, identification information of the caller (for example, a caller's telephone number) B) It is determined whether the caller identification key) is included in the 'Authenticated Sender DB', and if the sender's identification information is included in the 'Authenticated Sender DB', it is determined that the sender is a legitimate person. On the other hand, if the identification information of the caller is not included in the 'authenticated caller DB', it is determined whether there is a call attempt notification from the calling terminal 40. The authentication server 30 determines that the caller is a legitimate caller, if there is a call attempt notification from the caller terminal 40. Here, the authentication server 30 updates the 'authenticated sender DB' by adding the sender determined to be a legitimate user to the 'authenticated sender DB'. If the call attempt notification is not received from the calling terminal 40 within a predetermined time, the authentication server 30 determines that the caller is not a legitimate user, and transmits the determination result to the receiving terminal 10. That is, the second caller authentication method is a method for determining that the caller is a legitimate person regardless of whether there is a call attempt notification if the caller identification information is included in the authenticated caller DB.

Another example of another method (hereinafter, 'third caller authentication method') is a method of not using an 'authenticated caller DB', and when there is an authentication request from the receiving terminal 10, a call from the calling terminal 40 is received. It determines whether the caller is a legitimate caller based on whether there is an attempt notification. That is, if there is no call attempt notification from the calling terminal 40 within a predetermined time, it is determined that the caller is not a valid caller.

On the other hand, among the above-described authentication methods, when the authentication server 30 is implemented to perform the authentication operation according to the first sender authentication method, the authentication server 30 is legitimate even if the caller has tampered with his / her telephone number. There is an effect that can determine whether the caller.

According to the present embodiment, the authentication server 30 compares the authentication information (caller identification information and recipient identification information) included in the call attempt notification with the authentication information (caller identification information and recipient identification information) included in the authentication request. In addition, it may determine whether or not a call attempt notification has been received.

According to the present embodiment, if it is determined that the originating terminal 40 is the legitimate sender, the authentication server 30 authenticates the authentication content corresponding to the legitimate sender to the authentication content providing server 20 (for example, if the legitimate originator is the National Police Agency, A mark indicating the National Police Agency may be the authentication content), and the authentication content providing server 20 transmits the authentication content corresponding to the legitimate caller to the reception terminal 10.

The authentication content providing server 20 stores and manages corresponding authentication content for each sender, and the sender here is authenticated as a legitimate sender.

According to the present embodiment, when the receiving terminal 10 initiates a call with the calling terminal 40, the receiving terminal 10 may stop displaying the authentication content and disconnect the connection with the authentication content providing server 20.

In the embodiment described with reference to FIGS. 1 and 2 as described above, the calling terminal 40 sends a call attempt notification to the authentication server 30, or the receiving terminal 10 sends an authentication request to the authentication server 30. In order to do this, programs for such operations must be installed in advance. For example, it may be installed in each terminal in a form called an app.

As described with reference to FIGS. 1 and 2, an authentication system capable of authenticating a caller and a receiver according to an embodiment of the present invention requires checking whether a caller is a legitimate caller when a call comes from a caller who is assumed to be a police officer or a bank. Useful if there is

Meanwhile, when the authentication server 30 receives a receiver authentication request from the calling terminal, the authentication server 30 may perform a receiver authentication operation. Hereinafter, a receiver authentication operation will be described with reference to FIGS. 1 and 3.

Recipient Authentication

The mobile terminal 40 (hereinafter referred to as 'calling terminal') sends a call ('call connection request') requesting a call to the mobile terminal 10 (hereinafter referred to as 'receiving terminal') and authenticates with the authentication server 30. Request ('Recipient Authentication Request').

According to one embodiment, the authentication server 30 stores the list of identification information (the recipient's telephone number or the key corresponding to the receiver's telephone number) for the authenticated recipients as the 'Authenticated Receiver DB' authorized recipients. Can manage

According to an embodiment, when there is a request for authenticating a receiver from the originating terminal 40, the authentication server 30 performs an authentication operation by using the method illustrated in FIG. 3 (hereinafter, 'first receiver authentication method'). Can be performed.

Referring to FIG. 3, when the first receiver authentication method is described, when the authentication server 30 receives an authentication request from the calling terminal 40, the identification information of the receiver (for example, the receiver's telephone number or a recipient identification key) ) Is included in the 'authenticated receiver DB', and if the receiver's identification information is included in the 'authenticated receiver DB', it is determined whether there is a call attempt notification from the receiving terminal 10. If the identification information of the receiver is included in the 'authenticated receiver DB' and there is a call attempt notification from the receiver terminal 10, the authentication server 30 determines that the receiver is a legitimate receiver. That is, in the first recipient authentication method, the identification information of the receiver (for example, the caller's telephone number or the caller identification key) is not included in the 'authenticated receiver DB', or the identification information of the receiver (for example, , The caller's telephone number or caller identification key) is included in the 'authenticated receiver DB', but if there is no call attempt notification from the receiving terminal 10, it is determined to be an invalid receiver.

On the other hand, the authentication server 30 may perform an authentication operation using another method.

As an example of another method (hereinafter, 'second receiver authentication method'), when there is a receiver authentication request from the calling terminal 40, the authentication server 30 sends the identification information of the receiver to the 'authenticated receiver DB'. If it is included in the 'authenticated receiver DB', it is determined that the receiver is a legitimate user. On the other hand, if the identification information of the receiver is not included in the 'authenticated receiver DB', it is determined whether there is a call attempt notification from the receiving terminal 10. The authentication server 30, if there was a call attempt notification from the receiving terminal 10-to inform that the calling terminal 40 is trying to connect to itself (the receiving terminal 10)-the recipient is a legitimate user I judge it. Here, the authentication server 30 updates the 'authenticated receiver DB' by adding the receiver determined to be a legitimate user to the 'authenticated receiver DB'. That is, in the second receiver authentication method, if the receiver's identification information is included in the 'authenticated receiver DB', it is determined that the receiver is legitimate regardless of whether there is a call attempt notification, and the receiver's identification information is 'authenticated receiver DB'. If it is not included, the authentication server 30 determines that it is not a legitimate receiver if the call attempt notification is not received from the receiving terminal 10 within a predetermined time.

As another example of another method (hereinafter referred to as 'third recipient authentication method'), the method does not use the 'authenticated recipient DB', and when there is an authentication request from the calling terminal 40, Based on whether there is a call attempt notification, it is determined whether it is a legitimate receiver. That is, if there is no call attempt notification within a predetermined time from the receiving terminal 10, it is determined as an unjust receiver.

When the receiving terminal 10 is a legitimate receiver, the authentication server 30 requests the authenticating content providing server 20 to transmit the authentication content corresponding to the legitimate receiver to the calling terminal 40.

The authentication content providing server 20 transmits the authentication content corresponding to the legitimate receiver to the calling terminal 40 in response to the request of the authentication server 30. On the other hand, the authentication server 30, if it is determined that the receiving terminal 10 is not a legitimate recipient or a legitimate receiver, the authentication result of the purpose of "I am not a legitimate receiver or suspect the legitimate receiver" May be transmitted to the calling terminal 40.

According to the present embodiment, the originating terminal 40 may make an authentication request to the authentication server 30 at the same time as calling the call or may make an authentication request to the authentication server 30 after sending the call.

According to the present embodiment, the calling terminal 40 may include an app for requesting authentication and displaying authentication content. A detailed description of the originating terminal 40 will be described later.

The authentication request transmitted from the originating terminal 40 to the authentication server 30 may include information ('authentication information') necessary for authentication. The authentication information may include, for example, sender identification information and receiver identification information. The caller identification information may include a key generated from the telephone number of the calling terminal 40 or the telephone number of the calling terminal 40 ('caller identification key'). Here, the caller identification key uniquely corresponds to the telephone number of the calling terminal 40.

The receiver identification information may include a key generated from the telephone number of the receiver terminal 10 or the telephone number of the receiver terminal 10 ('key for identification of the receiver'). Here, the recipient identification key uniquely corresponds to the telephone number of the reception terminal 10.

On the other hand, in the above-described embodiment, when the caller identification key or the callee identification key is used, there is no risk of personal information leakage because the authentication server 30 does not need to store the caller's telephone number or the recipient's telephone number. .

According to the present embodiment, when the receiving terminal 10 receives a call from the calling terminal 40, the called terminal 40 tells the authentication server 30 that the calling terminal 40 is trying to talk to itself (the receiving terminal 10). Notify ('call attempt').

According to the present embodiment, the call attempt notification includes authentication information necessary to authenticate that the receiving terminal 10 is a legitimate recipient, and the authentication information may include, for example, caller identification information and recipient identification information. . Since the sender identification information and the receiver identification information have been described above, they will be omitted here.

According to the present embodiment, the receiving terminal 10 includes an app for performing a call attempt notification operation, and the app may be loaded and operated in a memory under the control of a computer processor.

The call attempt notification that the receiving terminal 10 transmits to the authentication server 30 may include, for example, caller identification information and receiver identification information.

According to the present embodiment, the receiving terminal 10 may transmit a call attempt notification at the same time as receiving a call, or transmit a call attempt notification after receiving a call.

Alternatively, when receiving a call, the receiving terminal 10 does not indicate to the user of the receiving terminal 10 that the call has been received (for example, an operation indicating that there is a call such as a ringtone or vibration). Not first), first, a call attempt notification may be transmitted to the authentication server 30, and then the user may be indicated that the call has been received.

According to the present embodiment, the authentication server 30 compares the authentication information (caller identification information and recipient identification information) included in the call attempt notification with the authentication information (caller identification information and recipient identification information) included in the authentication request. In addition, it may determine whether or not a call attempt notification has been received.

According to the present embodiment, if it is determined that the receiving terminal 10 is a legitimate recipient, the authentication server 30, to the authentication content providing server 20 authenticated content corresponding to the legitimate receiver (for example, if the legitimate receiver is a police station, The mark indicating the National Police Agency may be authenticated content), and the authenticating content providing server 20 transmits the authenticating content corresponding to the legitimate receiver to the originating terminal 40.

The authentication content providing server 20 stores and manages the corresponding authentication content for each recipient, and the recipient is authenticated as a valid recipient.

According to the present embodiment, when the receiving terminal 10 starts a call with the calling terminal 40, the receiving terminal 10 transmits a 'call connection notification' to notify the call reception to the authentication server 30. The authentication server 30 receiving the 'call connection notification' may stop the transmission of the authentication content to the calling terminal 40.

Alternatively, the authentication server 30 receiving the 'call connection notification' may inform the calling terminal 40 to stop displaying the authentication content.

In the embodiment described with reference to FIGS. 1 and 3, in order for the calling terminal 40 to request authentication from the authentication server 30 or the receiving terminal 10 to notify the authentication server 30 of a call attempt, Each program for such operations must be pre-installed. For example, it may be installed in each terminal in a form called an app.

As described with reference to FIGS. 1 and 3, an authentication system capable of authenticating a receiver according to an embodiment of the present invention needs to confirm whether the receiver is a legitimate receiver when calling a receiver suspected to be a police agency or a bank. Useful if there is.

FIG. 4 is a diagram illustrating an authentication system capable of authenticating a sender and a receiver according to another embodiment of the present invention. FIG. 5 is a diagram illustrating an operation of authenticating a caller performed by the system of FIG. 4, and FIG. 6. 4 is a view for explaining a receiver authentication operation performed by the system of FIG.

FIG. 4 assumes that the caller terminal 40 in the embodiment of FIG. 1 is not a mobile terminal but is a terminal connected through an exchange such as an IP-PBX, for example, a telephone connected by wire or wirelessly with an IP-PBX. It is for explaining an authentication system capable of caller authentication according to an embodiment of the present invention.

Referring to FIG. 4, an authentication system capable of authenticating a sender and a receiver according to an embodiment of the present invention (hereinafter, 'the present authentication system') includes a mobile terminal 110, an authentication content providing server 120, and an authentication server 130. ), A mobile terminal 140 and an exchange (hereinafter, 'IP-PBX') 150.

The authentication system can authenticate whether the recipient is a legitimate recipient ('recipient authentication') and can authenticate whether the sender is a legitimate sender ('sender authentication').

In the present authentication system, when it is determined that the receiver is a legitimate user, the authentication server requests the authentication content providing server to transmit the authentication content corresponding to the user of the receiving terminal to the calling terminal. As a result of performing the authentication operation, if it is determined that the caller is a legitimate user, the authentication server requests the authentication content providing server to transmit the authentication content corresponding to the user of the calling terminal to the receiving terminal.

The authentication server 130 may perform a sender authentication operation upon receiving a sender authentication request from a receiving terminal, and may perform a receiver authentication operation upon receiving a receiver authentication request from a calling terminal. Hereinafter, the caller authentication operation will be described first with reference to FIGS. 4 and 5.

Caller authentication

The mobile terminal 140 (hereinafter referred to as 'calling terminal') transmits a call ('call connection request') requesting a call to the mobile terminal 110 (hereinafter referred to as 'receiving terminal'). The call connection request may include caller identification information and receiver identification information.

Since the call connection request sent from the calling terminal 140 is transmitted to the receiving terminal 110 via the IP-PBX 150, the IP-PBX 150 may know whether there is a call connection request.

The IP-PBX 150 receives a call originating from the originating terminal 140 and transmits it to a place (receiving terminal 110) where such a call is to be forwarded.

When the IP-PBX 150 receives a call connection request from the calling terminal 140, the IP-PBX 150 notifies the authentication server 130 of the 'call attempt notification' indicating that the calling terminal 140 tries to talk to the receiving terminal 110. send. The call attempt notification may include caller identification information and receiver identification information.

When the receiving terminal 110 receives the call originating from the calling terminal 140, in order to confirm whether the calling terminal 140 is the legitimate caller, the receiving terminal 110 may make an authentication request to the authentication server 130.

 When the receiving terminal 110 requests authentication from the authentication server 130, the authentication server 130 checks whether the calling terminal 140 is a legitimate sender, and if the legitimate sender is the legitimate caller, to the authentication content providing server 120. The legitimate sender is requested to transmit the corresponding authentication content to the receiving terminal 140.

The authentication content providing server 120 transmits the authentication content corresponding to the legitimate sender to the receiving terminal 110 in response to a request of the authentication server 130. On the other hand, the authentication server 130, if it is determined that the originating terminal 140 is not a legitimate caller or a legitimate caller, the authentication result of the effect that "I am not a legitimate caller or suspect that the legitimate caller" May be transmitted to the receiving terminal 110.

According to the present embodiment, the receiving terminal 110 may include an app for requesting authentication and displaying authentication content.

The authentication request transmitted by the receiving terminal 110 to the authentication server 130 may include authentication information-information necessary for authentication. The authentication information may include, for example, caller identification information and receiver identification information. Can be.

 According to this embodiment, the IP-PBX 150 authenticates that the originating terminal 140 is attempting to make a call to the receiving terminal 110 when there is a call transmitted from the originating terminal 140 to the receiving terminal 110. Inform 130 (this operation is hereinafter referred to as call notification).

According to the present embodiment, when the authentication server 130 receives an authentication request from the receiving terminal 110, the authentication server 130 performs an authentication operation by using the method illustrated in FIG. 5 (hereinafter, 'the fourth caller authentication method'). Can be done.

Referring to FIG. 5, the fourth caller authentication method will be described. When the authentication server 130 receives an authentication request from the receiving terminal 110, the caller's identification information (for example, a caller's phone number or caller identification is used). Key) is included in the 'Authenticated Caller DB', and if the caller's identification information is included in the 'Authenticated Caller DB', it is determined whether there is a call attempt notification from the IP-PBX 150. do. The authentication server 130 determines that the caller's identification information is included in the 'authenticated caller DB', and if the call attempt notification by the caller terminal 140 is received from the IP-PBX 150, the caller is a legitimate caller. . In the fourth caller authentication method, the caller's identification information (for example, the caller's telephone number or caller identification key) is not included in the 'authenticated caller DB', or the caller's identification information (for example, If the caller's telephone number or caller identification key) is included in the 'Authenticated Caller DB' but there is no call attempt notification from the IP-PBX 150, the caller is determined to be an invalid caller.

Meanwhile, the authentication server 130 may perform an authentication operation using another method.

As an example of another method (hereinafter, referred to as a fifth sender authentication method), when the authentication server 130 receives an authentication request from the receiving terminal 110, the identification information of the sender is included in the 'authenticated sender DB'. If the identification information of the sender is included in the 'authenticated sender DB', it is determined that the sender is a legitimate person. On the other hand, if the identification information of the caller is not included in the 'authenticated caller DB', it is determined whether there is a call attempt notification from the IP-PBX 150. The authentication server 130 determines that the caller is a legitimate person, if there is a call attempt notification from the IP-PBX 150. Here, the authentication server 130 updates the 'authenticated sender DB' by adding the sender determined as a legitimate user to the 'authenticated sender DB'. If the call attempt notification is not received from the IP-PBX 150 within a predetermined time, the authentication server 130 determines that the caller is not a legitimate user, and transmits the determination result to the receiving terminal 110. That is, the fifth caller authentication method is a method for determining that the caller is a legitimate caller regardless of whether or not there is a call attempt notification if the caller identification information is included in the authenticated caller DB.

Another example of another method (hereinafter, 'sixth caller authentication method') is a method that does not use the 'authenticated sender DB', and when there is an authentication request from the receiving terminal 110, from the IP-PBX 150. It determines whether the caller is a legitimate caller based on whether there is a call attempt notification. In other words, if there is no call attempt notification from the IP-PBX 150 within a predetermined time, it is determined as an invalid caller.

On the other hand, among the above-described authentication methods, when the authentication server 130 is implemented to perform the authentication operation according to the fourth caller authentication method, the authentication server 130 is legitimate even if the caller has tampered with their phone number. There is an effect that can determine whether the caller.

 According to the present embodiment, if it is determined that the originating terminal 140 is a legitimate sender, the authentication server 130 authenticates the authentication content corresponding to the legitimate sender to the authentication content providing server 120 (for example, if the legitimate sender is the National Police Agency, A mark indicating the National Police Agency may be the authentication content), and the authentication content providing server 120 transmits the authentication content corresponding to the legitimate caller to the reception terminal 110.

The authentication content providing server 120 stores and manages corresponding authentication content for each sender, and the sender is authenticated as a legitimate sender.

According to the present embodiment, when the calling terminal 140 initiates a call with the receiving terminal 110, the receiving terminal 110 may stop displaying the authentication content.

The embodiment described with reference to FIGS. 4 and 5 is the same as the embodiment described with reference to FIGS. 1 and 2 except that the IP-PBX 150 transmits a call attempt notification to the authentication server.

As described above, in Fig. 1, the originating terminal 40 transmits a 'call attempt notification' to the authentication server 30, but in Fig. 4, the call attempt is performed by an exchange installed in a private switching network called IP-PBX 150. Notification 'is sent to the authentication server (130).

In the present embodiment, when the IP-PBX 150 receives a call from the originating terminal 140, the IP-PBX 150 can know from which originating terminal 140 to which receiving terminal 110, so that the call is attempted. 'Notification' may be transmitted to the authentication server 130.

 In the embodiment described with reference to FIGS. 4 and 5, in order for the receiving terminal 110 to perform an operation for requesting authentication to the authentication server 130, a program for such operations must be installed in advance. For example, an app for authentication (hereinafter, an 'authentication service app') may be installed in the receiving terminal 110. For example, when the app installed in the receiving terminal 110 receives a call from the calling terminal 110, the app requests authentication to the authentication server 130, and receives an authentication result from the authentication server 130 to receive the user. You can also mark

Meanwhile, the authentication server 130 may perform a receiver authentication operation when receiving a receiver authentication request from the calling terminal. Hereinafter, a receiver authentication operation will be described with reference to FIGS. 4 and 6.

Recipient Authentication

According to an embodiment, the authentication server 130 stores and stores identification information (list of the recipient's telephone number or a key corresponding to the receiver's telephone number) for the authenticated recipients as an authorized 'receiver DB' legitimate recipient. Can manage

According to an embodiment, when there is a request for authenticating a receiver from the originating terminal 140, the authentication server 130 performs an operation of authenticating whether the receiver is a legitimate receiver.

If the receiving terminal 110 is a legitimate receiver, the authentication server 130 requests the authenticating content providing server 120 to transmit the authenticating content corresponding to the legitimate receiver to the calling terminal 140.

The authentication content providing server 120 transmits the authentication content corresponding to the legitimate receiver to the calling terminal 140 in response to the request of the authentication server 130. On the other hand, the authentication server 130, if it is determined that the receiving terminal 110 is not a legitimate recipient or a legitimate recipient, the authentication result of the purpose of 'I am not a legitimate receiver or suspect the legitimate recipient' May be transmitted to the calling terminal 140.

According to the present embodiment, the originating terminal 140 may request authentication from the authentication server 130 at the same time as the call is sent, or may request authentication from the authentication server 130 after the call is sent.

According to the present embodiment, the calling terminal 140 may include an app for requesting authentication and displaying authentication content.

In the authentication request transmitted from the calling terminal 140 to the authentication server 30, information necessary for authentication information-authentication, for example, caller identification information, is a phone number of the calling terminal 140 or a phone number of the calling terminal 140. It may include a key generated from ('caller identification key'). Here, the caller identification key uniquely corresponds to the telephone number of the caller terminal 140.

The receiver identification information may include a key generated from the telephone number of the receiving terminal 110 or the telephone number of the receiving terminal 110 ('recipient identification key'). Here, the recipient identification key uniquely corresponds to the telephone number of the reception terminal 110.

On the other hand, in the above-described embodiment, when using the caller identification key or the recipient identification key, there is no fear that personal information leaks because the authentication server 130 does not need to store the caller's telephone number or the recipient's telephone number. have.

 According to the present embodiment, when the IP-PBX 150 receives a call transmitted from the calling terminal 140 to the receiving terminal 110, the IP-PBX 150 transmits the call to the receiving terminal 110. When the IP-PBX 150 receives a call transmitted from the originating terminal 140 to the receiving terminal 110, the authentication server 30 further indicates that the originating terminal 140 is trying to make a call with the receiving terminal 110. ) ('Call attempt').

For example, when there is a request for authenticating a receiver from the originating terminal 140, the authentication server 130 may perform an authentication operation by using the method illustrated in FIG. 6 (hereinafter, 'the fourth receiver authentication method'). Can be.

Referring to FIG. 6, when the fourth receiver authentication method is described, when the authentication server 130 receives the receiver authentication request from the calling terminal 140, identification information of the receiver (for example, a recipient's phone number or recipient identification) Key) is included in the 'Authenticated Receiver DB', and if the receiver's identification information is included in the 'Authenticated Receiver DB', it is determined whether there is a call attempt notification from the IP-PBX 150. do. The authentication server 130 determines that the identification information of the receiver is included in the 'authenticated receiver DB', and if there is a call attempt notification from the IP-PBX 150, the receiver is a legitimate receiver. That is, in the fourth receiver authentication method, the receiver's identification information (for example, the caller's telephone number or the caller identification key) is not included in the 'authenticated receiver DB', or the receiver's identification information (for example, If the caller's phone number or caller identification key) is included in the 'authenticated receiver DB' but there is no call attempt notification from the IP-PBX 150, the caller is determined to be an invalid receiver.

Meanwhile, the authentication server 130 may perform an authentication operation by using another method.

As an example of another method (hereinafter referred to as a '5th recipient authentication method'), when the authentication server 130 requests a receiver authentication from the calling terminal 140, the identification information of the receiver is transferred to the 'authenticated receiver DB'. If the receiver's identification information is included in the 'Authenticated Receiver DB', the receiver is determined to be a legitimate user, and if the receiver's identification information is not included in the 'Authenticated Receiver DB' , The IP-PBX 150 determines whether there is a call attempt notification, and if the authentication server 130 has a call attempt notification from the IP-PBX 150, the receiver determines that the receiver is a legitimate user, the legitimate user Update the 'authenticated receiver DB' by adding the recipient determined to the 'authenticated receiver DB'. That is, in the fifth receiver authentication method, if the receiver's identification information is included in the 'authenticated receiver DB', the receiver determines that the receiver is legitimate regardless of whether there is a call attempt notification, and the receiver's identification information is 'authenticated receiver DB'. When not included in the above, when the call attempt notification is received from the receiving terminal 10 within a predetermined time, the authentication server 30 determines that the receiver is a legitimate recipient.

As another example of another method (hereinafter, 'the sixth recipient authentication method'), when the authentication server 130 receives a request for recipient authentication from the originating terminal 140, there is a call attempt notification from the IP-PBX 150. If there is a call attempt notification from the IP-PBX 150, the authentication server 130 determines that the receiver is a legitimate user, and the call attempt notification from the IP-PBX 150 is received within a predetermined time. If not, the authentication server 130 determines that the receiver is not a legitimate user, and transmits the determination result to the calling terminal 140.

According to the present embodiment, when the authentication terminal 130 determines that the receiver terminal 110 is a legitimate receiver, the authentication content providing server 120 authenticates the authentication content corresponding to the legitimate receiver (for example, if the legitimate receiver is the police agency, The mark indicating the National Police Agency may be authenticated content), and the authenticating content providing server 120 transmits the authenticating content corresponding to the legitimate receiver to the originating terminal 140.

The authentication content providing server 120 stores and manages the corresponding authentication content for each recipient, and the recipient is authenticated as a valid recipient.

According to the present embodiment, when the receiving terminal 110 starts a call with the calling terminal 140, the IP-PBX 150 transmits a 'call connection notification' for notifying the call connection to the authentication server 130. The authentication server 130 receiving the 'call connection notification' may stop the transmission of the authentication content to the calling terminal 140.

The embodiment described with reference to FIGS. 4 and 6 is the same as the embodiment described with reference to FIGS. 1 and 3 except that the IP-PBX 150 transmits a call attempt notification to the authentication server.

As described above, in the exemplary embodiment of FIG. 1, the 'call attempt notification' is transmitted to the authentication server 30 by the receiving terminal 10, whereas in the exemplary embodiment of FIG. 4, the private switching network called IP-PBX 150 is illustrated. 'Call attempt notification' is transmitted to the authentication server 30 by the exchange installed in the.

In the present embodiment, when the IP-PBX 150 receives a call from the originating terminal 140, the IP-PBX 150 knows to which receiving terminal 110 such call is transmitted. It is configured to transmit to).

As described above, in the embodiment described with reference to FIGS. 4 and 6, in order to perform an operation for requesting authentication to the authentication server 130 when the originating terminal 140 transmits a call, a program for such operations is performed. This should be pre-installed. For example, an app for authentication (hereinafter, an app for authentication service) may be installed in the calling terminal 140. For example, an app installed in the calling terminal 140 sends an authentication request to the authentication server 130 when the calling terminal 140 sends a call, and receives an authentication result from the authentication server 130 to the user. Can also be displayed.

7 is a view for explaining a mobile terminal according to an embodiment of the present invention.

Referring to FIG. 7, a mobile terminal according to an embodiment of the present invention may include a computer processor 11, a memory 13, a storage 40, a communication module 17, and an app 19. .

In the embodiments described with reference to FIGS. 1 to 6, the terminals 10, 40, 110, and 140 may have the same configuration as the mobile terminal illustrated in FIG. 7.

The app 19 of the mobile terminal illustrated in FIG. 7 is an application that performs an operation related to authentication, such as displaying an authentication request or authentication content. The app 19 may be stored in the storage 40 and loaded into the memory 13 under the control of a computer processor to perform an operation.

FIG. 8 is a view for explaining an operation when a call comes to a receiving terminal from an illegal sender ('criminal') in the authentication system according to the embodiment described with reference to FIGS. 1 and 2.

Referring to FIG. 8, the criminal terminal generates a call for a call connection and transmits it through a communication network, and the receiving terminal receives the call.

The receiving terminal makes an authentication request to the authentication server 30 to confirm whether the sender is a legitimate sender.

When an authentication request is received from the receiving terminal, the authentication server determines whether the caller is a legitimate caller by using any one of the authentication methods described above with reference to FIGS. 1 and 2, and transmits the result of the determination to the receiving terminal. . On the other hand, the criminal terminal is not a legitimate caller can not send a 'call attempt notification' to the authentication server, and will not be in the 'authenticated sender DB'.

The receiving terminal may display the determination result received from the authentication server to the user. For example, you can't see the called party. If you are talking about financial transactions or crimes, please check the other party. You can display a message or voice such as'.

Meanwhile, in the authentication system according to the embodiment described with reference to FIGS. 4 to 5, even when the calling terminal 140 is an unjust caller, the caller may be authenticated in the same manner as described with reference to FIG. 8. Can be. That is, an invalid caller cannot transmit a 'call attempt notification' to the authentication server, and in case of a legitimate caller, the IP-PBX can transmit a 'call attempt notification' to the authentication server, thereby enabling authenticating the caller.

FIG. 9 is a view for explaining an operation when the calling terminal 40 calls an illegal receiver ('criminal person') in the authentication system according to the embodiment described with reference to FIGS. 1 and 3.

Referring to FIG. 9, the calling terminal generates a call to a criminal terminal and transmits the call through a communication network, and sends an authentication request to the authentication server.

On the other hand, the criminal terminal receives the call from the originating terminal, but can not transmit the 'call attempt notification' to the authentication server because it is not a legitimate receiver.

The authentication server may perform an authentication operation by using any one of the authentication methods described with reference to FIGS. 1 and 3 when there is a receiver authentication request from the calling terminal 40.

The authentication server transmits the determination result to the calling terminal. The calling terminal may display the determination result received from the authentication server to the user. For example, you can't see the called party. If you are talking about financial transactions or crimes, please check the other party. You can display a message or voice such as'.

Meanwhile, in the authentication system according to the embodiment described with reference to FIGS. 4 and 6, even when the calling terminal 140 calls an unjustified receiver, the receiver is the same as described with reference to FIG. 9. Can be authenticated. In other words, an invalid receiver cannot transmit a 'call attempt notification' to the authentication server, and a legitimate receiver can transmit a 'call attempt notification' to the authentication server, thereby authenticating the receiver.

As such, those skilled in the art may make various modifications and variations from the description of the above specification. Therefore, the scope of the present invention should not be limited to the described embodiments, but should be defined by the claims below and equivalents thereof.

10, 40, 110, 140: mobile terminal
20, 120: authentication content providing server
30, 130: authentication server
150: IP-PBX

Claims (1)

In the authentication system capable of sender and receiver authentication,
An originating terminal that originates a call requesting a call;
A receiving terminal for receiving the call from the calling terminal;
If there is a caller authentication request from the receiving terminal, it authenticates whether the calling terminal is a legitimate caller (called 'caller authentication'). Authentication server); And
Further comprising a authentication content providing server,
The authentication server
If it is determined that the receiver is a legitimate user, the receiver requests the authentication content providing server to transmit the authentication content corresponding to the user of the receiving terminal to the calling terminal, and performs the calling party authentication operation. As a result, if it is determined that the caller is a legitimate user, the authentication system for authenticating the sender and the receiver, characterized in that the request for sending the authentication content corresponding to the user of the calling terminal to the receiving terminal.

Images