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

Abstract

Disclosed is an authentication system for a caller and a recipient based on authentication contents, wherein the authentication system comprises: a transmitting terminal which transmits a call to require a phone call; a receiving terminal which receives the call from the transmitting terminal; and an authentication system which authenticates whether the transmitting terminal is a correct caller, and the receiving terminal is a correct recipient.

Description

[0001] The present invention relates to an authentication system capable of authenticating a sender and a receiver based on authentication contents,

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

[0002] With the recent rapid development of communication technology, the use of mobile terminals (for example, smart phones) has spread rapidly and become an essential means in modern life.

Furthermore, as financial transactions become possible by using mobile terminals, there have been reported cases in which personal information is leaked and used for crime such as smsing.

On the other hand, techniques for preventing such crimes such as smashing - for example, Korean Patent Publication No. 2013-0026265 (March 13, 2013) and Korean Patent Registration No. 1321721 (Oct. However, there are still cases of damage caused by crimes such as smashing.

There is provided an authentication system capable of authenticating a sender and a receiver based on an authenticated content according to an embodiment of the present invention and a mobile terminal used therefor.

 According to one embodiment of the present invention, an authentication that can prevent an outflow of personal information impersonating an institution such as a government office (police, fire department, etc.) or a bank or an offense such as direct cash take-over (for example, voice phishing) An authentication system capable of authenticating sender and receiver based on content and a mobile terminal used therefor are provided.

According to an embodiment of the present invention, an authentication system capable of authenticating a sender and a recipient who can intuitively identify a legitimate sender or a legitimate recipient by displaying an authenticated result of a sender or a receiver as an authenticated content such as a moving picture or a still image, And a mobile terminal used therefor are provided.

According to an embodiment of the present invention, there is provided an authentication system capable of accurately authenticating a caller even when an unauthorized caller modifies his / her phone number and transmits the same, and a mobile terminal used therefor.

An authentication system capable of authenticating a sender and a receiver,

An originating terminal for originating 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 is authenticated that the calling terminal is a legitimate caller (referred to as 'caller authentication'), and if there is a request for a receiver authentication from the calling terminal, Authentication "); And

And an authenticated content providing server,

The authentication server

If it is determined that the receiver is a valid user as a result of performing the receiver authentication operation, the authentication content server requests the authentication content providing server to transmit the authentication content corresponding to the user of the receiver terminal to the originator terminal, The authentication system according to claim 1, wherein the authenticated content providing server requests authentication content corresponding to a user of the calling terminal to the receiving terminal when the calling party is determined to be a legitimate user.

According to one or more embodiments of the present invention, when a call attempt is made from a sender, the caller can be authenticated in advance of the call, so that leakage attempts of personal information impersonating an agency such as a government office (police, fire department) (For example, voice phishing) such as direct cash take-over.

According to one or more embodiments of the present invention, when there is a call attempt from the caller, the result of authenticating the caller in advance of the call is displayed as an authenticated content such as a moving picture or a still image so that the receiver can intuitively check whether the caller is a legitimate caller . Therefore, it is easy to identify vulnerable layers such as elderly people as legitimate senders.

According to one or more embodiments of the present invention, even if an unauthorized sender modifies his / her telephone number to originate the call, it can accurately authenticate the caller.

According to one or more embodiments of the present invention, when an attempt is made to call a recipient suspected of being unfair, the recipient can be authenticated in advance of the call, thereby impersonating an institution such as a government office (police, fire station, etc.) (For example, voice phishing) such as an attempt to leak personal information or a direct cash takeover.

According to one or more embodiments of the present invention, when a call attempt is made to a receiver suspected of being unjustified, the result of authenticating the recipient before the call is displayed as an authenticated content, such as a moving picture or still image, It is possible to confirm whether or not it is a receiver. Therefore, it is easy to check whether security vulnerable layers such as the elderly are legitimate recipients.

FIG. 1 is a view for explaining 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 explaining a caller authentication operation performed by the system of Fig. 1; Fig.
FIG. 3 is a diagram for explaining a recipient authentication operation performed by the system of FIG. 1; FIG.
4 is a diagram for explaining an authentication system capable of authenticating a sender and a receiver according to another embodiment of the present invention.
5 is a diagram for explaining a sender authentication operation performed by the system of FIG.
FIG. 6 is a diagram for explaining a recipient authentication operation performed by the system of FIG. 4; FIG.
7 is a view for explaining a mobile terminal according to an embodiment of the present invention.
FIG. 8 is a diagram for explaining an operation when a call is received from an unauthorized sender ('criminal') to a receiving terminal in the authentication system according to the embodiment described with reference to FIG. 1 and FIG.
FIG. 9 is a diagram for explaining an operation when the calling terminal makes a call to an unauthorized recipient ('criminal') in the authentication system according to the embodiment described with reference to FIGS.

BRIEF DESCRIPTION OF THE DRAWINGS The above and other objects, features, and advantages of the present invention will become more readily apparent from the following description of preferred embodiments with reference to the accompanying drawings. However, the present invention is not limited to the embodiments described herein but may be embodied in other forms. Rather, the embodiments disclosed herein are provided so that the disclosure can be thorough and complete, and will fully convey the scope of the invention to those skilled in the art.

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

In the present specification, the singular form includes plural forms unless otherwise specified in the specification. The terms "comprise" and / or "comprising" used in the specification 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 drawings. In describing the specific embodiments below, various specific details have been set forth in order to explain the invention in greater detail and to assist in understanding it. However, it will be appreciated by those skilled in the art that the present invention may be understood by those skilled in the art without departing from such specific details. In some cases, it should be mentioned in advance that it is common knowledge in describing an invention that parts not significantly related to the invention are not described in order to avoid confusion in explaining the present invention.

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

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

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

In this authentication system, if it is determined that the receiver is a legitimate user as a result of performing the receiver authentication operation, 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, If it is determined that the sender is an authorized user as a result of performing the authentication operation, the authentication server requests the authenticated content providing server to transmit the authenticated content corresponding to the user of the originating terminal to the receiving terminal.

The authentication server 30 performs a sender authentication operation upon receiving a sender authentication request from a receiving terminal and can perform a receiver authentication operation upon receiving a receiver authentication request from an originating terminal. Hereinafter, the caller authentication operation will be described first with reference to FIG. 1 and FIG.

Caller authentication

According to the present embodiment, the mobile terminal 40 (hereinafter referred to as a 'calling terminal') transmits a call requesting a call (a 'call connection request') to the mobile terminal 10 To the authentication server 30, a 'call attempt notification' for notifying that the calling terminal 40 is attempting to establish a call connection with the receiving terminal 10 at the same time as or after the call connection request.

 According to the present embodiment, upon receiving a call from the originating terminal 40, the receiving terminal 10 transmits an authentication request ('caller authentication request') requesting the authentication server 30 to check whether the calling terminal 40 is a legitimate caller ')can do.

The authentication server 30 performs an operation of confirming whether or not the calling terminal 40 is a legitimate caller ('caller authentication'), and if the caller is a legitimate caller, the authentication server 30 notifies the authenticated content providing server 20 of an authentication corresponding to a legitimate caller And requests the content to be transmitted to the receiving terminal 10.

The authenticated content providing server 20 transmits the authenticated content corresponding to a legitimate sender to the receiving terminal 10 at the request of the authentication server 30. On the other hand, when it is determined that the originating terminal 40 is not a legitimate sender or a legitimate sender, the authentication server 30 judges that the authenticating server 30 is' not a legitimate sender or a legitimate sender Can transmit the authentication result to the receiving terminal 10.

According to the present embodiment, the originating terminal 40 sends a call and at the same time sends a call attempt notification (notifying that the call is being made to the receiving terminal) to the authentication server 30, You can send a call attempt notification.

According to the present embodiment, the receiving terminal 10 may include an application 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 from the receiving terminal 10 to the authentication server 30 may include information ('authentication information') necessary for authentication. The authentication information may include, for example, sender identification information and recipient identification information.

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

The receiver identification information may include a key (' receiver identification key ') generated from the telephone number of the receiving terminal 10 or the telephone number of the receiving terminal 10. Here, the receiver identification key is uniquely associated with the telephone number of the receiving terminal 10. [

On the other hand, in the above-described embodiment, when the caller identification key or the recipient identification key is used, there is no need for the authentication server 30 to store the caller's telephone number or the receiver's telephone number, have.

According to the present embodiment, when the originating terminal 40 transmits a call to the receiving terminal 10, the authentication server 30 determines that the calling terminal 40 is attempting to call the receiving terminal 10, (Hereinafter referred to as " call attempt 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, for example, caller identification information and recipient identification information. The sender identification information and the receiver identification information have been described above, and thus will not be described here.

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

The call attempt notification sent from the originating terminal 40 to the authentication server 30 may include, for example, caller identification information and recipient identification information.

According to one embodiment, the authentication server 30 sends an authenticated sender DB? A list of authenticated senders as a legitimate sender (a list of sender's phone numbers or keys corresponding to caller's phone numbers ('caller identification keys')).

According to the present embodiment, when the authentication server 30 receives an authentication request from the receiving terminal 10, the authentication server 30 uses the method illustrated in FIG. 2 (hereinafter referred to as a 'first calling party authentication method') to perform an authentication operation Can be performed.

2, the authentication server 30 judges whether or not the identification information of the caller (for example, the telephone number of the caller or the key for identifying the caller) is included in the 'authenticated caller DB' If the sender's identification information is included in the " authenticated sender DB ", the originating terminal 40 determines whether there is a call attempt notification. The authentication server 30 judges that the caller is a legitimate person if the caller identification information is included in the 'authenticated caller DB' and there is a call attempt notification from the caller terminal 40. [ In the first authentication method of the sender, the identification information of the sender (for example, the telephone number of the sender or the key for identifying the sender) is not included in the authenticated sender DB or the sender's identification information (for example, The calling party's telephone number or key for identifying the caller) is included in the " authenticated caller DB " but the calling terminal 40 does not notify the calling party of the call attempt.

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

For example, when the authentication server 30 receives an authentication request from the receiving terminal 10, the authentication server 30 transmits the identification information of the calling party (for example, the telephone number of the calling party, Or the sender 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 sender. On the other hand, if the sender's identification information is not included in the " authenticated sender DB ", the originating terminal 40 determines whether there is a call attempt notification. The authentication server 30 judges 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 within a predetermined time from the originating terminal 40, 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, if the sender's identification information is included in the authenticated sender DB, the second sender authentication method is a method in which the sender is judged to be a legitimate person irrespective of whether there is a call attempt notification.

Another example of another method (hereinafter referred to as a 'third calling party authentication method') is a method that does not use an authenticated caller DB. When there is an authentication request from the receiving terminal 10, It is judged whether or not the sender is a legitimate sender based on whether there is an attempt notification. That is, if there is no notification of call attempt within a predetermined time from the calling terminal 40, it is determined that the caller is an unauthorized caller.

On the other hand, when the authentication server 30 is implemented so as to perform the authentication operation according to the first authentication method, among the above-described authentication methods, even when the caller modifies his or her telephone number, It is possible to determine whether the caller is a caller or not.

According to the present embodiment, the authentication server 30 compares the authentication information (sender identification information and receiver identification information) included in the call attempt notification with the authentication information (the sender identification information and the receiver identification information) included in the authentication request , It is possible to determine whether or not a call attempt notification has been received.

According to the present embodiment, when it is determined that the originating terminal 40 is a legitimate sender, the authentication server 30 instructs the authenticated content providing server 20 to authenticate content corresponding to a legitimate sender (for example, if a legitimate sender is a police agency, The authentication content providing server 20 transmits the authentication content corresponding to the legitimate sender to the receiving terminal 10. The authenticated content providing server 20 transmits the authenticated content to the receiving terminal 10,

The authentication content providing server 20 stores and manages the authentication contents corresponding to 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 can stop displaying the authentication content and disconnect the authentication content providing server 20.

As described above, in the embodiment described with reference to FIGS. 1 and 2, when the calling terminal 40 sends a call attempt notification to the authentication server 30, or when the receiving terminal 10 requests the authentication server 30 for authentication In order to do so, 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 above with reference to FIGS. 1 and 2, an authentication system capable of authenticating a sender and a receiver according to an embodiment of the present invention, when a call comes from a police station or a caller suspected of being a bank, needs to check whether the caller is a legitimate caller Is useful.

On the other hand, the authentication server 30 can perform the receiver authentication operation upon receiving the receiver authentication request from the originating terminal. Hereinafter, the recipient authentication operation will be described with reference to FIG. 1 and FIG.

Recipient Authentication

The mobile terminal 40 transmits a call requesting a call to the mobile terminal 10 (hereinafter referred to as a " call terminal connection request ") to the authentication server 30 ('Recipient Authentication Request').

According to one embodiment, the authentication server 30 may store and store identification information (a list of recipient's phone numbers or keys corresponding to recipient's phone numbers) for authenticated recipients as " authorized recipient DB " Can be managed.

According to one embodiment, when there is a receiver authentication request from the originating terminal 40, the authentication server 30 uses the method illustrated in FIG. 3 (hereinafter referred to as 'first receiver authentication method') to perform an authentication operation Can be performed.

3, when the authentication server 30 receives the authentication request from the originating terminal 40, the authentication server 30 transmits the identification information of the recipient (for example, the telephone number of the recipient or the key for identifying the recipient 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 or not there is a communication attempt notification from the receiving terminal 10. The authentication server 30 judges that the recipient is a legitimate recipient if the identification information of the recipient is included in the " authenticated recipient DB " That is, in the first receiver authentication method, the identification information of the receiver (for example, the telephone number of the sender or the key for identifying the sender) is not included in the 'authenticated receiver DB', or the receiver's identification information , The telephone number of the caller or the key for identifying the caller) is included in the 'authenticated receiver DB', but there is no call attempt notification from the receiving terminal 10, it is judged to be an unauthorized receiver.

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

For example, when there is a recipient authentication request from the originating terminal 40, the authentication server 30 sends the authentication information to the authentication server 30, And if the identification information of the receiver 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 or not there is a call attempt notification from the receiver terminal 10. The authentication server 30 notifies the call attempt notification from the receiving terminal 10 that the calling terminal 40 is informing that it is attempting to make a call connection with itself (the receiving terminal 10) . Here, the authentication server 30 updates the 'authenticated recipient DB' by adding the recipient judged as a legitimate user to the 'authenticated recipient 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 a legitimate receiver irrespective of whether there is a call attempt notification, The authentication server 30 judges that the call attempt notification is not a legitimate recipient 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 a 'Third Recipient Authentication Method'), as a method for not using the 'authorized recipient DB', when there is an authentication request from the originating terminal 40, It is judged whether or not it is a legitimate recipient based on whether or not there is a call attempt notification. That is, if there is no notification of the call attempt within a predetermined time from the receiving terminal 10, it is judged to be an unauthorized receiver.

The authentication server 30 requests the authenticated content providing server 20 to transmit the authenticated content corresponding to the legitimate recipient to the originating terminal 40 when the receiving terminal 10 is a legitimate recipient.

The authenticated content providing server 20 transmits the authenticated content corresponding to a legitimate recipient to the originating terminal 40 at the request of the authentication server 30. [ On the other hand, when it is determined that the receiving terminal 10 is not a legitimate recipient or a legitimate recipient, the authentication server 30 transmits an authentication result indicating that it is "not a legitimate recipient or a legitimate recipient" To the originating terminal (40).

According to the present embodiment, the originating terminal 40 can issue an authentication request to the authentication server 30 at the same time as issuing a call, or can issue an authentication request to the authentication server 30 after issuing a call.

According to the present embodiment, the originating terminal 40 may include an application for requesting authentication and displaying authentication content. A more detailed description of the originating terminal 40 will be given 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 recipient identification information. The caller identification information may include a key generated from a telephone number of the calling terminal 40 or a telephone number of the calling terminal 40 ('caller identification key'). Here, the caller identification key is uniquely associated with the telephone number of the calling terminal 40. [

The receiver identification information may include a key (' receiver identification key ') generated from the telephone number of the receiving terminal 10 or the telephone number of the receiving terminal 10. Here, the receiver identification key is uniquely associated with the telephone number of the receiving terminal 10. [

On the other hand, in the above-described embodiment, when the caller identification key or the recipient identification key is used, there is no need for the authentication server 30 to store the caller's telephone number or the receiver's telephone number, .

According to the present embodiment, when the receiving terminal 10 receives a call from the calling terminal 40, the calling terminal 40 informs the authentication server 30 that the calling terminal 40 is attempting to call itself (the receiving terminal 10) Notify ("call attempt notification").

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

According to the present embodiment, the receiving terminal 10 includes an app which performs a call attempt notification operation, and the app can be loaded into memory and operated under the control of a computer processor.

The call attempt notification transmitted from the receiving terminal 10 to the authentication server 30 may include, for example, caller identification information and recipient identification information.

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

Alternatively, 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 ringing tone or vibration) , It is possible to indicate to the user that the call has been received after transmitting the call attempt notification to the authentication server 30 first.

According to the present embodiment, the authentication server 30 compares the authentication information (sender identification information and receiver identification information) included in the call attempt notification with the authentication information (the sender identification information and the receiver identification information) included in the authentication request , It is possible to determine whether or not a call attempt notification has been received.

According to this embodiment, when it is determined that the receiving terminal 10 is a legitimate recipient, the authentication server 30 notifies the authenticated content providing server 20 of the authenticated content corresponding to the legitimate recipient (for example, if the legitimate recipient is the police agency, The authentication content providing server 20 sends the authenticated content corresponding to the legitimate recipient to the originating terminal 40. The authenticated content providing server 20 transmits the authentication content to the originating terminal 40,

The authenticated content providing server 20 stores and manages the authenticated contents in correspondence with each recipient, and the recipient here is authenticated as a legitimate recipient.

According to the present embodiment, when the calling terminal 10 initiates a call with the calling terminal 40, the receiving terminal 10 transmits a 'call connection notification' to the authentication server 30. The authentication server 30 having received the 'call connection notification' can stop the transmission of the authentication content to the calling terminal 40.

Alternatively, the authentication server 30 having received the 'call connection notification' may notify 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 originating terminal 40 to make an authentication request to the authentication server 30 or the receiving terminal 10 to notify the authentication server 30 of a call attempt, 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 3, the authentication system capable of authenticating the recipient according to the embodiment of the present invention needs to check whether or not such a receiver is a legitimate recipient when making a call to a police station or a receiver assumed to be a bank It is useful if you have.

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

4 assumes that the caller's terminal 40 is not a mobile terminal but a terminal connected via an exchange such as an IP-PBX, for example a telephone connected to the IP-PBX wired or wirelessly The present invention is to describe an authentication system capable of authenticating a sender according to an embodiment of the present invention.

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

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

In this authentication system, if it is determined that the receiver is a legitimate user as a result of performing the receiver authentication operation, 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, If it is determined that the sender is an authorized user as a result of performing the authentication operation, the authentication server requests the authenticated content providing server to transmit the authenticated content corresponding to the user of the originating terminal to the receiving terminal.

The authentication server 130 performs a sender authentication operation upon receiving a sender authentication request from a receiving terminal, and can perform a receiver authentication operation upon receiving a receiver authentication request from a sending terminal. Hereinafter, the caller authentication operation will be described first with reference to FIG. 4 and FIG.

Caller authentication

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

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

The IP-PBX 150 receives the call originating from the originating terminal 140, and transmits the call to the destination (the receiving terminal 110).

The IP-PBX 150 notifies the authentication server 130 of a 'call attempt notification' informing that the calling terminal 140 tries to make a call with the receiving terminal 110 when there is a call connection request from the calling terminal 140 send. Such a call attempt notification may include caller identification information and recipient identification information.

Upon receiving the call from the originating terminal 140, the receiving terminal 110 may request the authentication server 130 to authenticate the originating terminal 140 to determine whether the calling terminal 140 is a legitimate originator.

 When the receiving terminal 110 requests the authentication server 130 to authenticate the authentication server 130, the authentication server 130 checks whether the calling terminal 140 is a legitimate sender, and if it is a legitimate sender, And requests the receiving terminal 140 to transmit the authenticated content corresponding to the legitimate sender.

The authentication content providing server 120 transmits the authentication content corresponding to the legitimate sender to the receiving terminal 110 according to the request of the authentication server 130. [ On the other hand, when it is determined that the calling terminal 140 is not a legitimate caller or a legitimate caller, the authentication server 130 determines that the authentication result of the authentication result indicates that the caller is 'not a legitimate caller or a legitimate caller' To the receiving terminal 110.

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

The authentication request transmitted from the receiving terminal 110 to the authentication server 130 may include authentication information - information necessary for authentication. The authentication information includes, for example, the sender identification information and the receiver identification information .

 The IP-PBX 150 notifies that the calling terminal 140 is attempting to call the receiving terminal 110 when there is a call from the calling terminal 140 to the receiving terminal 110, (Hereinafter referred to as " call attempt 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 using the method illustrated in FIG. 5 (hereinafter referred to as a 'fourth calling party authentication method') Can be performed.

5, when the authentication server 130 receives an authentication request from the receiving terminal 110, the authentication server 130 transmits the identification information of the calling party (for example, the telephone number of the calling party, PBX 150 determines whether or not there is a call attempt notification from the IP-PBX 150 if the sender's identification information is included in the " authenticated sender DB " do. The authentication server 130 judges that the calling party is a legitimate caller if the caller's identification information is included in the 'authenticated caller DB', and if there is a call attempt notification from the IP-PBX 150 by the calling terminal 140 . In the fourth authentication method of the sender, the identification information of the sender (for example, the telephone number of the sender or the key for identifying the sender) is not included in the authenticated sender DB, or the identification information of the sender If the caller's telephone number or caller identification key) is included in the " authenticated caller DB " but the call attempt is not made from the IP-PBX 150, the caller is determined to be an unauthorized caller.

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

For example, when the authentication server 130 receives an authentication request from the receiving terminal 110, the authentication server 130 includes the sender's identification information included in the 'authenticated sender DB' If the sender's identification information is included in the " authenticated sender DB ", it is determined that the sender is a legitimate sender. On the other hand, if the sender's identification information is not included in the " authenticated sender DB ", the IP-PBX 150 determines whether there is a call attempt notification. 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 to be a legitimate user to the 'authenticated sender DB'. If the call attempt notification from the IP-PBX 150 is not received within a predetermined time, the authentication server 130 determines that the caller is not a legitimate user and transmits the determination result to the reception terminal 110. [ That is, if the sender's identification information is included in the authenticated sender DB, the fifth sender authentication method is a method of determining that the sender is a legitimate sender irrespective of whether there is a call attempt notification.

Another example of another method (hereinafter referred to as a 'sixth sender authentication method') is a method that does not use the 'authenticated sender DB'. When there is an authentication request from the receiving terminal 110, It is judged whether or not it is a legitimate sender based on whether or not there is a call attempt notification. That is, if there is no notification of call attempt within a predetermined time from the IP-PBX 150, it is determined that the caller is an unauthorized caller.

In the meantime, when the authentication server 130 is implemented to perform the authentication operation according to the fourth authentication method, among the authentication methods described above, even when the caller modifies his / her telephone number, It is possible to determine whether the caller is a caller or not.

 According to the present embodiment, when it is determined that the calling terminal 140 is a legitimate caller, the authentication server 130 notifies the authenticated contents providing server 120 of the authenticated contents corresponding to the legitimate caller (for example, if the legitimate caller is the police agency, The authenticated content providing server 120 transmits the authenticated content corresponding to the legitimate sender to the receiving terminal 110. In this case,

The authentication content providing server 120 stores and manages the authentication contents in correspondence with each sender, and the sender here 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 can stop displaying the authenticated content.

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

1, the originating terminal 40 transmits a 'call attempt notification' to the authentication server 30, but in FIG. 4, the call set up by the exchange installed in the private exchange network called 'IP-PBX 150' Notification 'is transmitted to the authentication server 130.

In this embodiment, when the IP-PBX 150 receives a call from the originating terminal 140, it can know from which originating terminal 140 such a call is transmitted to which receiving terminal 110, Notification '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 application for authentication (hereinafter referred to as an 'application for authentication service') may be installed in the receiving terminal 110. For example, when an application installed in the receiving terminal 110 receives a call from the originating terminal 110, the app sends an authentication request to the authentication server 130, receives an authentication result from the authentication server 130, . ≪ / RTI >

On the other hand, the authentication server 130 can perform a receiver authentication operation upon receiving a receiver authentication request from an originating terminal. Hereinafter, the recipient authentication operation will be described with reference to FIG. 4 and FIG.

Recipient Authentication

According to one embodiment, the authentication server 130 may store and store identification information (a list of recipient's phone numbers or keys corresponding to the recipient's phone number) for authenticated recipients as authentic ' recipient DB ' Can be managed.

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

When the receiving terminal 110 is a legitimate recipient, the authentication server 130 requests the authenticated contents providing server 120 to transmit the authenticated contents corresponding to the legitimate recipient to the calling terminal 140. [

The authentication content providing server 120 transmits the authentication content corresponding to a legitimate recipient to the calling terminal 140 in response to a request from the authentication server 130. [ On the other hand, when it is determined that the receiving terminal 110 is not a legitimate recipient or a legitimate recipient, the authentication server 130 transmits an authentication result indicating that it is 'not a legitimate recipient or a legitimate recipient' To the originating terminal (140).

According to the present embodiment, the originating terminal 140 may request authentication to the authentication server 130 at the same time as issuing a call, or may request the authentication server 130 to authenticate after issuing a call.

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

The authentication request transmitted from the originating terminal 140 to the authentication server 30 includes information necessary for authentication information authentication such as the calling party identification information is a telephone number of the calling terminal 140 or a telephone number of the calling terminal 140 (&Quot; caller identification key "). Here, the calling party identification key is uniquely associated with the telephone number of the calling terminal 140.

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

On the other hand, in the above-described embodiment, in the case of using the key for identifying the sender or the key for identifying the receiver, since there is no need for the authentication server 130 to store the sender's telephone number or the receiver's telephone number, have.

 According to the present embodiment, when the IP-PBX 150 receives a call delivered from the originating terminal 140 to the receiving terminal 110, the IP-PBX 150 delivers 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 IP-PBX 150 further informs the authentication server 30 that the calling terminal 140 is attempting to communicate with the receiving terminal 110 ) ("Call attempt notification").

For example, when there is a receiver authentication request from the originating terminal 140, the authentication server 130 performs an authentication operation using a method illustrated in FIG. 6 (hereinafter, a 'fourth receiver authentication method') .

Referring to FIG. 6, a fourth receiver authentication method will be described. When the authentication server 130 receives a receiver authentication request from the originating terminal 140, the authentication server 130 transmits identification information of the receiver (for example, If the identification information of the receiver is included in the " authenticated receiver DB ", it is determined whether or not there is a call attempt notification from the IP-PBX 150 do. The authentication server 130 judges that the receiver is a legitimate recipient if the identification information of the receiver is included in the 'authenticated receiver DB' and there is a call attempt notification from the IP-PBX 150. That is, in the fourth receiver authentication method, the identification information of the receiver (e.g., the telephone number of the sender or the key for identifying the sender) is not included in the " authenticated receiver DB " , The caller's telephone number or key for identifying the caller) is included in the 'authorized recipient DB', but there is no call attempt notification from the IP-PBX 150, it is judged to be an unjust recipient.

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

For example, when the authentication server 130 receives a request for authentication of a recipient from the originator terminal 140, the authentication server 130 transmits the authentication information to the 'authorized recipient DB' If the receiver's identification information is included in the 'authenticated receiver DB', it is determined that the receiver is a legitimate user. If the receiver's identification information is not included in the 'authenticated receiver DB' The authentication server 130 determines whether the recipient is a legitimate user if there is a call attempt notification from the IP-PBX 150. If the legitimate user To the 'authenticated recipient DB', thereby updating the 'authenticated recipient DB'. That is, in the fifth receiver authentication method, if the identification information of the receiver is included in the " authenticated receiver DB ", it is determined that the receiver is a legitimate receiver irrespective of whether or not there is a call attempt notification, The authentication server 30 judges that it is a legitimate recipient when a call attempt notification is received from the receiving terminal 10 within a predetermined time.

In another example of another method (hereinafter referred to as a 'sixth receiver authentication method'), when the authentication server 130 receives a receiver authentication request from the calling terminal 140, there is a call attempt notification from the IP-PBX 150 The authentication server 130 determines that the recipient is a legitimate user and notifies the IP-PBX 150 of a call attempt notification within a predetermined period of time 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 it is determined that the receiving terminal 110 is a legitimate recipient, the authentication server 130 notifies the authenticated contents providing server 120 of the authenticated contents corresponding to the legitimate recipient (for example, if the legitimate recipient is the police agency, The authentication content providing server 120 transmits the authenticated content corresponding to the legitimate recipient to the originating terminal 140. The authenticated content providing server 120 transmits the authenticated content corresponding to the valid recipient to the originating terminal 140. [

The authentication content providing server 120 associates and stores the authentication contents for each recipient, and the recipient here is authenticated as a legitimate recipient.

According to the present embodiment, when the receiving terminal 110 initiates a call with the calling terminal 140, the IP-PBX 150 transmits a 'call connection notification' informing the call connection to the authentication server 130. The authentication server 130 receiving the 'call connection notification' can 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 FIG. 1 and FIG. 3, except that the IP-PBX 150 transmits a call attempt notification to the authentication server.

1, the 'call attempt notification' is transmitted to the authentication server 30 by the receiving terminal 10, whereas in the embodiment of FIG. 4, the private exchange network called 'IP-PBX 150' The " call attempt notification " is transmitted to the authentication server 30 by the exchange installed in the "

In this embodiment, when the IP-PBX 150 receives a call from the originating terminal 140, it can know to which receiving terminal 110 such a call is transmitted, .

As described above, in the embodiment described with reference to FIGS. 4 and 6, in order for the calling terminal 140 to perform an operation for requesting authentication to the authentication server 130 when transmitting a call, Must be installed in advance. For example, an application for authentication (hereinafter referred to as an 'application for authentication service') may be installed in the calling terminal 140. For example, when the calling terminal 140 sends a call, the app installed in the calling terminal 140 sends an authentication request to the authentication server 130, receives the authentication result from the authentication server 130, It can also be displayed.

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

7, a mobile terminal according to an embodiment of the present invention may include a computer processor 11, a memory 13, a storage unit 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 shown in Fig.

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

FIG. 8 is a diagram for explaining an operation when a call is received from an unauthorized sender ('criminal') to a receiving terminal in the authentication system according to the embodiment described with reference to FIG. 1 and FIG.

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

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

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

The receiving terminal can display the judgment result transmitted from the authentication server to the user. For example, "I can not verify the person on the phone. If you have a financial transaction or a crime-related call, please check with the person you are calling. Quot ;, and the like can be displayed.

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 unauthorized calling party, it is possible to authenticate the calling party similarly to the principle described with reference to FIG. 8 . That is, an unauthorized sender can not transmit a 'call attempt notification' to the authentication server. In case of a legitimate caller, the IP-PBX can transmit a 'call attempt notification' to the authentication server, thereby authenticating the caller.

FIG. 9 is a diagram for explaining an operation when the calling terminal 40 makes a call to an unauthorized receiver ('criminal') in the authentication system according to the embodiment described with reference to FIG. 1 and FIG.

Referring to FIG. 9, the originating terminal generates a call to the criminal terminal, transmits the call through the 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 since it is not a legitimate recipient.

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

The authentication server transmits the determination result to the originating terminal. The calling terminal can display the judgment result transmitted from the authentication server to the user. For example, "I can not verify the person on the phone. If you have a financial transaction or a crime-related call, please check with the person you are calling. Quot ;, and the like can be displayed.

Meanwhile, in the authentication system according to the embodiment described with reference to FIGS. 4 and 6, even when the calling terminal 140 makes a call to an unauthorized recipient, as in the principle described with reference to FIG. 9, Can be authenticated. That is, the unauthorized receiver can not transmit the 'call attempt notification' to the authentication server, and the legitimate receiver can transmit the 'call attempt notification' to the authentication server, so that the receiver can be authenticated.

Various modifications and variations of the present invention are possible in light of the above teachings. Therefore, the scope of the present invention should not be limited by the described embodiments, but should be determined by the scope of the appended claims, as well as the appended claims.

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

Claims (1)

An authentication system capable of authenticating a sender and a receiver,
An originating terminal for originating 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 is authenticated that the calling terminal is a legitimate caller (referred to as 'caller authentication'), and if there is a request for a receiver authentication from the calling terminal, Authentication "); And
And an authenticated content providing server,
The authentication server
If it is determined that the receiver is a valid user as a result of performing the receiver authentication operation, the authentication content server requests the authentication content providing server to transmit the authentication content corresponding to the user of the receiver terminal to the originator terminal, The authentication system according to claim 1, wherein the authenticated content providing server requests authentication content corresponding to a user of the calling terminal to the receiving terminal when the calling party is determined to be a legitimate user.

Images