System and method for authenticating received communication using dynamic verification

The system authenticates communications by comparing and optionally resending or redirecting them through separate channels, effectively addressing the inefficiencies of current verification methods and reducing the risk of scams.

WO2026235626A1PCT designated stage Publication Date: 2026-11-12PRIVATE NATION PTE LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
PCT/SG2026/050268
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2025-05-08
Filing Date
2026-04-24
Publication Date
2026-11-12

AI Technical Summary

Technical Problem

Current methods for verifying the authenticity of communications, such as scam messages and calls, are ineffective and inefficient, leading to significant threats and financial losses.

Method used

A system and method that utilizes a server to authenticate communications through alternative channels by comparing attributes of the received communication with those of the sent communication, and optionally resending or redirecting the communication through separate channels, allowing recipients to select from multiple authentication options.

Benefits of technology

Enhances the security and reliability of communication verification by ensuring that only genuine communications are received, reducing the risk of scams and phishing attacks.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure SG2026050268_12112026_PF_FP_ABST
    Figure SG2026050268_12112026_PF_FP_ABST
Patent Text Reader

Abstract

A system and method for authenticating received communication is provided. The system includes a server having at least one memory; and one or more processors to execute instructions stored in the memory that configures the server to: facilitate a plurality of options to authenticate a communication received by a recipient, based on a technique that references the received communication; execute the technique in accordance with a selected option, wherein one or more channels used by the server to facilitate the authentication of the communication is separate from the channel through which the communication is received by the recipient.
Need to check novelty before this filing date? Find Prior Art

Description

System and method for authenticating received communication using dynamic verificationTECHNICAL FIELD

[0001] The present disclosure relates generally to a system and method for dynamically authenticating received communication by providing for several options, with the authentication being facilitated by a server and alternative channels. The system serves to guard against phishing and scam communications.BACKGROUND

[0002] The prevalence of fraudulent communications, including scam messages, emails, and calls, poses significant threats to individuals and organizations worldwide. These deceptive schemes exploit the lack of effective mechanisms to verify the authenticity of communications, leading to financial losses.

[0003] Current protection measures in the market include: validate sender email address / phone number, spot spoofed logos, call sender / official sources, check with family / friends, check for grammar and spelling mistakes, examine attachments, etc. These measures are ineffective and inefficient in addressing fraudulent communications.

[0004] Therefore, it is desirable to provide a system that can authenticate received communications in an effective and efficient manner which addresses the technical disadvantages or limitations of existing approaches or, at the very least, provide the public with a useful alternative.SUMMARY

[0005] In accordance with an aspect of the present disclosure, a system for authenticating received communication is provided. The system includes a server having at least one memory; and one or more processors to execute instructions stored in the memory that configures the server to: facilitate a plurality of options to authenticate a communication received by a recipient, based on a technique that references the received communication; and execute the technique in accordance with the protocol of a selected option, wherein one or more channels used by the server to facilitate the authentication of the communication is separate from the channel through which the communication is received by the recipient.

[0006] In an embodiment, the technique comprises the server being configured to: facilitate comparison of attributes of a sent communication from a sender against corresponding attributes of the received communication in accordance with the protocol of the selected option, through a channel separate from the channel used by the received communication; and facilitate resending of the communication from the sender in accordance with the protocol ofthe selected option, through a channel separate from the channel used by the received communication.

[0007] In an embodiment, the protocol of a first of the options comprises further configuring the server to: receive a verification query and the attributes of the received communication from the recipient; forward the verification query to the sender; receive the attributes of the sent communication from the sender, in response to the verification query; perform the comparison, wherein the comparison result indicates whether the communication is authenticated; and transmit the comparison result to the recipient.

[0008] In an embodiment, the protocol of a second of the options comprises further configuring the server to: receive a verification query from the recipient; forward the verification query to the sender; receive the attributes of the sent communication from the sender, in response to the verification query; and forward the attributes of the sent communication to the recipient to perform the comparison.

[0009] In an embodiment, the protocol of a third of the options comprises further configuring the server to: receive a resend request from the recipient; and forward the resend request to the sender, to resend the communication to the recipient, whereby the resultant receipt of the resent communication by the recipient would inform the recipient that the earlier received communication is authentic.

[0010] In an embodiment, the protocol of the third of the options comprises further configuring the server to: receive the attributes of the resent communication from the sender, in response to the resend request; and forward the attributes of the resent communication to the recipient.

[0011] In an embodiment, the protocol of a fourth of the options comprises further configuring the server to: receive a redirect request from the recipient; and forward the redirect request to the sender, to redirect the communication to the recipient at an alternate address, whereby the resultant receipt of the redirected communication by the recipient would inform the recipient that the earlier received communication is authentic.

[0012] In an embodiment, the protocol of the fourth of the options comprises further configuring the server to: receive the attributes of the redirected communication from the sender, in response to the redirect request; and forward the attributes of the redirected communication to the recipient.

[0013] In an embodiment, the protocol of a fifth of the options comprises further configuring the server to: receive the attributes of the sent communication from the sender upon the sender sending the communication to the recipient; and forward the attributes of the sent communication to the recipient to perform the comparison.

[0014] In an embodiment, the server is further configured to support one or more of the options being selected, executed and repeated in any order.

[0015] In an embodiment, any initiation of the authentication of the received communication is by the recipient.

[0016] In an embodiment, the attributes comprise one or more of: sender address, recipient address, date, time, display name, agent name, call duration and single use code.

[0017] In an embodiment, the comparison provides for tolerance between the time of the sent communication and the time of the received communication; and the comparison result indicates compliance with the tolerance.

[0018] In an embodiment, the server is further configured to: receive a scam report from the recipient in response to failure of authentication of the received communication; and transmit the scam report to the sender.

[0019] In an embodiment, the received communication comprises electronic and nonelectronic communication.

[0020] In an embodiment, the electronic communication comprises one or more of emails, Short Messaging Service (SMS) messages, instant messages, phone calls, video calls, social media posts, forums, faxes, press releases, webpages and advertisements; and the nonelectronic communication comprises physical mails and physical meetings.

[0021] In an embodiment, the server is further configured to relay a verification query or a resend request received from the recipient to the sender; receive from the sender a denial of sending the received communication; fail the authentication of the received communication in response to the denial; and transmit a zero tuple or warning to the recipient.

[0022] In accordance with another aspect of the present disclosure, a method for authenticating received communication is provided. The method includes facilitating, through the use of a server and alternative secure channels, a plurality of options to authenticate a received communication received by a recipient, based on a technique that references the received communication; facilitating the selection of an option at any time; dynamically executing the technique based on the protocol of the selected option upon the option’s selection, the technique comprising effecting transmission of verification data from a sender of the communication, to be used to determine if the received communication is authentic; facilitating, if required, the selection of an additional option at any time; and dynamically executing, if required, the technique based on the protocol of the additional selected option sequentially, conditionally or concurrently, upon the option’s selection.

[0023] In an embodiment, the technique comprises comparing attributes of a sent communication from a sender against corresponding attributes of the received communication in accordance with the protocol of the selected option, through a channel separate from the channel used by the received communication; or resending of the communication from the sender in accordance with the protocol of the selected option, through a channel separate from the channel used by the received communication.

[0024] In an embodiment, the protocol of a first of the options comprises receiving a verification query and the attributes of the received communication from the recipient; forwarding the verification query to the sender; receiving the attributes of the sent communication from the sender, in response to the verification query; performing the comparison at the server, wherein the comparison result indicates whether the communication is authenticated; and transmitting the comparison result to the recipient.

[0025] In an embodiment, the protocol of a second of the options comprises receiving a verification query from the recipient; forwarding the verification query to the sender; receiving the attributes of the sent communication from the sender, in response to the verification query; and forwarding the attributes of the sent communication to the recipient to perform the comparison.

[0026] In an embodiment, the protocol of a third of the options comprises receiving a resend request from the recipient; and forwarding the resend request to the sender, to resend the communication to the recipient, whereby the resultant receipt of the resent communication by the recipient would inform the recipient that the earlier received communication is authentic.

[0027] In an embodiment, the protocol of the third of the options further comprises receiving the attributes of the resent communication from the sender, in response to the resend request; and forwarding the attributes of the resent communication to the recipient.

[0028] In an embodiment, the protocol of a fourth of the options comprises receiving a redirect request from the recipient; and forwarding the redirect request to the sender, to redirect the communication to the recipient at an alternate address, whereby the resultant receipt of the redirected communication by the recipient would inform the recipient that the earlier received communication is authentic.

[0029] In an embodiment, the protocol of the fourth of the options further comprises receiving the attributes of the redirected communication from the sender, in response to the redirect request; and forwarding the attributes of the redirected communication to the recipient.

[0030] In an embodiment, the protocol of a fifth of the options further comprises receiving the attributes of the sent communication from the sender upon the sender sending the communication to the recipient; and forwarding the attributes of the sent communication to the recipient to perform the comparison.

[0031] Embodiments of the present disclosure may be provided as a network of communicating devices (i.e. a “computerized network”). Embodiments of the invention may be also provided as a software application downloadable into a computer device. The software application may be a computer program product, which may be stored on a non-transitory computer-readable medium on a tangible data-storage device (such as a storage device of a server, or one within a user device).

[0032] A system for authenticating received communication and the server and the alternative channels that facilitate the authentication are thus disclosed herein. Various features, aspects, and advantages of the present disclosure will become more apparent from the following detailed description of the embodiments of the present disclosure, by way of non-limiting examples only, along with the accompanying drawings.BRIEF DESCRIPTION OF THE DRAWINGS

[0033] Figure 1A is a diagram showing the entities of a system in accordance with an embodiment of the invention.

[0034] Figure 1 B shows a method for authenticating a received communication in accordance with an embodiment of the invention.

[0035] Figure 2 shows the system when the protocol of a first of the options is performed.

[0036] Figure 3 shows the system when the protocol of a second of the options is performed.

[0037] Figure 4 shows the system when the protocol of a third of the options is performed.

[0038] Figure 5 shows the system when the protocol of a fourth of the options is performed.

[0039] Figure 6 shows the system when the protocol of a fifth of the options is performed.

[0040] Figure 7 is a block diagram illustrating a technical architecture of a computing server for implementing the server and the protocols of the five options of Figures 2 to 6.DETAILED DESCRIPTION

[0041] In the following, embodiments of the present invention will be described as non-limiting examples with reference to the accompanying drawings.

[0042] For purposes of brevity and clarity, descriptions of embodiments of the present disclosure are directed to a system, server and alternative channels for authenticating received communication in accordance with the drawings. While aspects of the present disclosure will be described in conjunction with the embodiments provided herein, it will be understood that they are not intended to limit the present disclosure to these embodiments. On the contrary, the present disclosure is intended to cover alternatives, modifications and equivalents to the embodiments described herein, which are included within the scope of the present disclosure as defined by the appended claims. Furthermore, in the following detailed description, specific details are set forth in order to provide an understanding of the present disclosure. However, it will be recognized by an individual having ordinary skill in the art, i.e. a skilled person, that the present disclosure may be practiced without specific details, and / or with multiple details arising from combinations of aspects of particular embodiments. In a number of instances, well-known systems, methods, procedures, and components have not been described in detail so as to not unnecessarily obscure aspects of the embodiments of the present disclosure.

[0043] In embodiments of the present disclosure, depiction of a given element or consideration or use of a particular element number in a particular figure or a reference thereto in corresponding descriptive material can encompass the same, an equivalent, or an analogous element or element number identified in another figure or descriptive material associated therewith.

[0044] References to “an embodiment / example”, “another embodiment I example”, “some embodiments / examples”, “some other embodiments / examples”, and so on, indicate that the embodiment(s) / example(s) so described may include a particular feature, structure, characteristic, property, element, or limitation, but that not every embodiment I example necessarily includes that particular feature, structure, characteristic, property, element or limitation. Furthermore, repeated use of the phrase “in an embodiment / example” or “in another embodiment / example” does not necessarily refer to the same embodiment / example.

[0045] The terms “comprising”, “including”, “having”, and the like do not exclude the presence of other features / elements / steps than those listed in an embodiment. Recitation of certain features I elements I steps in mutually different embodiments does not indicate that a combination of these features / elements / steps cannot be used in an embodiment.

[0046] As used herein, the terms “a” and “an” are defined as one or more than one. The use of 7” in a figure or associated text is understood to mean “and / or” unless otherwise indicated. The terms “first”, “second”, etc. are used merely as labels or identifiers and are not intended to impose numerical requirements on their associated terms.

[0047] As used in the present disclosure, the terms “component”, “module”, “system”, “interface” and the like are generally intended to refer to a computer-related entity, either hardware, a combination of hardware and software, software, or software in execution. For example, a module may be, but is not limited to being, a process running on a processor, a processor, an object, an executable, a thread of execution, a program, and / or a computer. By way of illustration, both an application running on a controller and the controller can be a component. One or more modules may reside within a process and / or thread of execution and a module may be localized on one computer and / or distributed between two or more computers. As another example, an interface can include I / O components as well as associated processor, application, and / or API components. In the context of the present disclosure, the authentication systems and methods, and their constituent parts, may be implemented as hardware, software, or a combination thereof.

[0048] Furthermore, various embodiments of the present disclosure may be implemented as a method, apparatus, or article of manufacture using standard programming and / or engineering techniques to produce software, firmware, hardware, or any combination thereof to control a computer to implement the disclosed subject matter. For instance, the claimed subject matter may be implemented as a computer-readable medium embedded with acomputer executable program, which encompasses a computer program accessible from any computer-readable storage device or storage media. For example, computer readable media can include but are not limited to magnetic storage devices (e.g., hard disk, floppy disk, magnetic strips, etc.), optical disks (e.g., compact disk (CD), digital versatile disk (DVD), etc.), smart cards, and flash memory devices (e.g., card, stick, key drive, etc.).

[0049] Herein disclosed is a system for authenticating received communication. The system includes a sender, a recipient, a server and communication channels. Within the system, communication received by the recipient is ideally authentic, such as being actually sent by the sender. However, fraud, phishing and scams now necessitate that any received communication be authenticated.

[0050] As used herein, the term "authenticate" refers to determining that a communication is genuine and has not been fabricated or impersonated by an unauthorized entity.

[0051] The present invention provides several options to authenticate a communication, with none relying on techniques such as validating a sender email address, spotting spoofed logos, calling the purported sender or an official source, checking grammar and spelling of the communication content. Rather, the options are based on a technique that references the received communication to be authenticated. Referencing means using the received communication in a manner determined by the selected authentication option.

[0052] The following is a non-exhaustive list of terms that are used when discussing operation of the system and elaborating on the options to authenticate the received communication. Entities and Applications

[0053] As used herein, the term “sender” refers to an individual or organisation that initiates and transmits a communication. Sender may use a phone, computer, system, or postal service, to send the communication.

[0054] As used herein, the term “recipient” refers to an individual or organisation receiving a communication. Recipient may use a phone, computer, system, or postal service, to receive the communication.

[0055] As used herein, the term “alternate address” refers to a recipient’s secondary email address, mobile number, residential address, fixed line telephone number, etc.

[0056] As used herein, the term “server” refers to a computer arrangement (such as a computer or a network of computers) designed to provide services and resources to the sender and the recipient.

[0057] As used herein, the term “sender application” refers to client-side software that runs on the sender’s devices.

[0058] As used herein, the term “recipient application” refers to client-side software that runs on the recipient’s devices.Communications, Queries and Requests

[0059] As used herein, the term ’’communication” refers to the transmission of data from one entity to another through a medium such as digital platform and postal service. Communication can be in electronic and non-electronic form. Electronic communication includes, but is not limited to, emails, Short Messaging Service (SMS) messages, instant messages, phone calls, video calls, social media posts, forums, faxes, press releases, webpages and advertisements. Non-electronic communication includes, but is not limited to, physical mails and physical meetings.

[0060] As used herein, the term, “first communication” refers to the first communication received by a recipient from a sender. In fraudulent scenarios, it could also have originated from a scammer posing as a sender.

[0061] As used herein, the term “attributes” refers to properties that provide information about the communication, the properties including, but not limited to: sender address, recipient address, date, time, display name, agent name, call duration and single use code.

[0062] As used herein, the term “first communication tuple” refers to a structured, immutable data container used to store essential attributes of a first communication.

[0063] As used herein, the term “verification query” refers to a query to verify whether a sender has sent any communication.

[0064] As used herein, the term “resend request” refers to a request for a sender to resend a first communication.

[0065] As used herein, the term “updated first communication tuple” refers to a structured, immutable data container used to store essential attributes of a resent communication.

[0066] As used herein, the term “redirected communication” refers to a communication that has the same content as the first communication but sent to the recipient’s alternate address.

[0067] As used herein, the term “redirect request” refers to a request for a sender to redirect a communication to a recipient’s alternate address.

[0068] As used herein, the term “redirected communication tuple” refers to a structured, immutable data container used to store essential attributes of a redirected communication.

[0069] As used herein, the term “zero tuple” refers to a tuple with zero elements.

[0070] As used herein, the term “scam report” refers to a notification of a suspected scam to a sender. Sender may use this as a trigger to initiate its investigation process and the securing of a recipient’s account.Communication Band and Channels

[0071] As used herein, the term “first band / channel” refers to a medium or pathway through which a first communication is transmitted from a sender to a recipient.

[0072] As used herein, the term “second band / channel” refers to a secure medium or pathway through which a recipient and a server communicate. The second band / channel is different and separate from first band / channel.

[0073] As used herein, the term “third band / channel” refers to a medium or pathway through which a redirected communication is transmitted from a sender to a recipient. The third band / channel is different and separate from first band / channel and second band / channel.

[0074] As used herein, the term “fourth band / channel” refers to a secure medium or pathway through which a sender and a server communicate. The fourth band / channel is different and separate from first band / channel, second band / channel and third band / channel.

[0075] The first communication tuple and redirected communication tuple have fields as shown in Table 1 below, each representing one communication attribute. Different communication modes use different fields, so different attributes apply for each different communication mode.Sender Address Recipient Address Date Time Display Name Agent Name Call Duration Single Use Code Definition Electronic or non-electronic Electronic or non-electronic Date when Time when Display Name of Name of Duration of Unique code address from which the address at which the communication was communication was Sender Agent Phone Call generated for eac communication was sent by communication was received sent sent communication Sender by RecipientNo. Communication Sender Address Recipient Address Date Time Display Name Agent Name Call Duration Single Use Code Mode1. Email Sender’s email address Recipient’s email address Date when email was Time when email was [Not used] [Not used] [Not used] Unique sent sent alphanumeric cod 2. SMS . Sender’s phone number Recipient’s phone number Date when SMS was Time when SMS was [Not used] [Not used] [Not used] Unique numeric • Senders SMS short code sent sent code . Senders alphanumeric ID3. Instant Message • Senders phone number Recipient’s phone number Date when Instant Time when Instant Display Name of Name of [Not used] Unique. Sender's alphanumeric ID Message was sent Message was sent Sender Agent alphanumeric cod 4. Phone Call (Call Sender’s phone number Recipient’s phone number Date when Phone Call Time when Phone Call [Not used] Name of Call Status, Unique numeric in Progress) started started Agent i e Call-in- code Progress5. Phone Call (Call Sender’s phone number Recipient’s phone number Date when Phone Call Time when Phone Call [Not used] Name of Duration of [Not used] Completed) started started Agent Phone Call6. Physical Mail Sender’s mailing address Recipient’s mailing address Date when mail was Time when mail was Name of Signatory [Not used] [Not used] Unique sent sent alphanumeric cod5

[0076] Accordingly, attributes in a received communication, or a sent communication comprise one or more of: sender address, recipient address, date, time, display name, agent name, call duration and single use code.

[0077] The system is described in greater detail below in conjunction with the Figures.

[0078] Figure 1A is a diagram showing the entities of a system 100 in accordance with an embodiment of the invention. As mentioned above, the system 100 includes a sender 110, a server 130 and a recipient 120.

[0079] The first channel 101 and third channel 103 are used by the sender 110 to send communications to the recipient 120. The first channel 101 is used when the sender 110 sends / transmits a first communication to the recipient 120. The goal of the present invention is to authenticate a communication that the recipient 120 receives, whereby the present disclosure may use the term “first communication” for the communication to be authenticated.

[0080] If the recipient 120 requests for a communication to be resent, being one of the authentication options (a third, described in greater detail below) facilitated by the server 130, the sender 110 will also use the first channel 101 to resend the first communication to the recipient (also called the “resent communication” by the present disclosure).

[0081] On the other hand, if the recipient 120 requests for a first communication to be resent to an alternate address, the sender 110 will use the third channel 103 to resend the first communication to the recipient (also called the “redirected communication” by the present disclosure). The alternate address is an address that is different from the address to which the earlier communication was sent.

[0082] The second channel 102 is used for server communication with the recipient 120. The fourth channel 104 is used for server communication with the sender 110.

[0083] The server 130 and the channels 101, 102, 103 and 104 enable the system 100 to have authentication ability, with the recipient 120 provided with a plurality of options, through an application, to authenticate a communication. The server 130 is configured to facilitate the plurality of options to authenticate a communication received by the recipient 120, based on a technique that references the received communication. The server 130 is further configured to execute the technique in accordance with the protocol of a selected one or more of the options of authentication. For one of the options (the first), the server 130 is configured to transmit a result of the authentication. Authentication results include whether the received communication is authenticated or unauthenticated, which is displayed in a recipient application, from the server 130 sending a suitable communication to the recipient application.

[0084] Accordingly, authentication of a received communication adopts a methodology as shown in Figure 1B.

[0085] At step 150, there is facilitation of a plurality of options to authenticate a received communication, based on a technique that references the received communication. As mentioned above, the server 130 facilitates the options through the use of alternative secure channels, while the communication is received by the recipient 120.

[0086] At step 160, there is facilitation of the selection of an option at any time.

[0087] At step 170, there is dynamic execution of the technique based on the protocol of the selected option upon the option’s selection. The technique comprises effecting transmission of verification data from the sender 110 of the communication, to be used to determine if the received communication is authentic.

[0088] The “verification data” that the sender 110 sends that is used to determine if the received communication is authentic is a first communication tuple (discussed in greater detail in the first, second and fifth options below) or the communication resent to the recipient 120 (discussed in greater detail in the third and fourth options below). The server 130 can effect the transmission of the verification data by sending / forwarding to the sender 110 a verification query (discussed in greater detail in the first and second options below); or a resend request or redirect request (discussed in greater detail respectively in the third and fourth options below).

[0089] At step 180, there is facilitation, if required, of the selection of an additional option at any time.

[0090] At step 190, there is dynamic execution, if required, of the technique based on the protocol of the additional selected option sequentially, conditionally or concurrently, upon the option’s selection.

[0091] Returning to Figure 1A, authentication of a communication in accordance with any one of the authentication options involves the server 130 communicating with the recipient 120 over the second channel 102 and the sender 110 over the fourth channel 104. As mentioned above, communication from the sender 110 to the recipient 120 is over the first channel 101 or the third channel 103, with all four channels 101, 102, 103 and 104 being independent to one another. Accordingly, the one or more channels 102, 104 used by the server 130 to facilitate the authentication of the communication is separate from the channels 101, 103 through which communication is received by the recipient 120. The use of separate channels enhances security as an attacker / scammer would need to compromise more than one channel.

[0092] Broadly, each of the plurality of options has the server 130 facilitate the authentication of a communication by referencing or making use of the communication in one of two ways.

[0093] In a first way, the server 130 is configured to facilitate comparison of attributes of the received communication by the recipient 120 against corresponding attributes of the sent communication from the sender 110, in accordance with the protocol of the selected one or more options. These attributes are transmitted through a channel separate from the channel 101 used by the received communication. The present disclosure discusses three options (namely a first, a second and a fifth) which follows the first way, with the three options being described in greater detail below.

[0094] In a second way, the server 130 is configured to facilitate resending of the communication from the sender 110 in accordance with the protocol of the selected one or more options. The recipient 120 receiving the resent communication is reflective of the first communication being genuine and authenticates the first communication because the resending occurs after a resend request was initiated by the recipient himself. If a scammer had sent the first communication (i.e. the communication that the recipient wants to authenticate), the scammer would not receive the resend request because the scammer does not have access to the server 130; and thus the resend request (or any messages) sent through the second channel 102 and the fourth channel 104. The present disclosure discusses two options (namely a third and a fourth) which follows the second way, with the two options being described in greater detail below.

[0095] The authentication options are now described below with reference to Figures 2 to 6, along with each of their respective protocols (i.e. the steps that are executed to perform authentication in each option). In addition, communication of the recipient 120 with the server 130 to execute one or more of the options is through a recipient application.

[0096] Figure 2 shows the protocol of a first of the options being performed. In the first option, authentication of the communication received by the recipient 120 is performed by the server 130. The protocol of the first option is as follows.

[0097] At step 210, the recipient 120 receives a first communication from the sender 110 through the first band / channel 101. In one implementation, at step 220, the recipient 120 can use the recipient application to scan the first communication to extract the key attributes of the first communication. For example, Optical Character Recognition (OCR) converts an image of the first communication into a machine-readable text format. Alternatively, the recipient 120 manually inputs key attributes of the first communication into the recipient application. These key attributes are described in Table 1.

[0098] Using the recipient application, the recipient 120 sends, at step 230, a verification query to the server 130; and attributes of the received communication (from the step 210) to the server 130. Both the verification query and the attributes of the received communication are transmitted on the second band / channel 102. The server 130 is configured to receive the verification query and the attributes of the received communication from the recipient 120.

[0099] At step 240, the server 130 sends or forwards the recipient verification query to the sender 110 over the fourth band / channel 104. The sender 110 receives the verification query via the sender application.

[0100] If the sender 110 had sent the first communication to the recipient 120 (confer step 210), then the sender 110 will respond to the server 130, over the fourth band / channel 104, with a first communication tuple at step 250. At step 260, the server 130 performs comparison of the attributes in the first communication tuple (received at step 250) against correspondingattributes received with the verification query at step 230, with the comparison result indicating whether the communication is authenticated.

[0101] If the sender 110 had not sent the first communication nor any other communication to the recipient 120, then the sender 110 will respond, over the fourth band / channel 104, with a zero tuple to the server 130, at step 250. Receipt of a zero tuple does not automatically mean that the first communication received at step 210 is a scam. One possible scenario is that the recipient 120 may be mistaken that a communication was even received at step 210. The recipient 120 may thus perform additional checks at his end, such as on the sender address and date of the first communication received at step 210; or whether a communication was indeed even received. If the result of the additional checks is that the first communication is unauthentic, the recipient 120 may send a scam report via the recipient application, discussed in greater detail at step 280 below.

[0102] At step 270, the server 130 transmits the comparison result to the recipient 120 by sending a server communication, over the second band / channel 102, which displays the result in the recipient application: authentic (i.e. the first communication is verified to be authentic) or unauthentic (i.e. the first communication is not from the sender 110).

[0103] If the result is unauthentic, then the recipient 120 has the option to send, at step 280, a scam report via the recipient application to the server 130. At step 285, the server 130 sends the scam report to the sender 110. At step 290, the sender 110 sends acknowledgement of the scam report to the server 130. At step 295, the server 130 displays the sender acknowledgement of the scam report in the recipient application.

[0104] Figure 3 shows the protocol of a second of the options being performed. In the second option, authentication of the communication received by the recipient 120 is performed by the recipient 120 himself. The protocol of the second option is as follows.

[0105] At step 210, the recipient 120 receives a first communication from the sender 110 through the first band / channel 101.

[0106] Using the recipient application, the recipient 120 sends, at step 330, a verification query to the server 130 on the second band / channel 102. In contrast to step 230 of Figure 2, the recipient 120 does not send attributes of the received communication to the server 130 at step 330. The server 130 is configured to receive the verification query from the recipient 120. The server 130 sends or forwards the recipient verification query to the sender 110 over the fourth band / channel 104 at step 340. The sender receives the verification query via the sender application.

[0107] If the sender 110 had sent the first communication to the recipient 120 (confer step 210), then the sender 110 will respond to the server 130, over the fourth band / channel 104, with a first communication tuple at step 350, in response to receipt of the verification query at step 340. At step 375, the server 130 forwards, over the second band / channel 102, the firstcommunication tuple to the recipient 120. The first communication tuple is displayed in user-friendly format in the recipient application for the recipient 120 to perform the comparison.

[0108] If the sender 110 had not sent the first communication nor any other communication to the recipient 120, then the sender 110 will respond, over the fourth band / channel 104, with a zero tuple to the server 130, at step 350. Receipt of a zero tuple does not automatically mean that the first communication received at step 210 is a scam. One possible scenario is that the recipient 120 may be mistaken that a communication was even received at step 210. The recipient 120 may thus perform additional checks at his end, such as on the sender address and date of the first communication received at step 210; or whether a communication was indeed even received. If the result of the additional checks is that the first communication is unauthentic, the recipient 120 may send a scam report via the recipient application, discussed in greater detail at step 380 below.

[0109] At step 376, the recipient 120 verifies if the first communication tuple matches the key attributes observed in the first communication received at step 210. The comparison result indicates whether the first communication is authentic.

[0110] If the recipient 120 determines that the first communication is unauthentic, the recipient 120 can send a scam report via the recipient application, at step 380. At step 385, the server 130 sends a scam report to the sender 110. At step 390, the sender 110 sends acknowledgement of the scam report to the server 130. At step 395, the server 130 displays the sender acknowledgement of the scam report in the recipient application.

[0111] Figure 4 shows the protocol of a third of the options being performed. In the third option, the recipient 120, via the server 130, requests for the sender 110 to resend the communication, whereby the resultant receipt of the resent communication by the recipient 120 would inform the recipient 120 that the first communication (i.e. the earlier communication) is authentic. The protocol of the third option is as follows.

[0112] At step 210, the recipient 120 receives a first communication from the sender 110 through the first band / channel 101. Using the recipient application, the recipient 120 sends, at step 420, a resend request to the server 130 on the second band / channel 102. The server 130 is configured to receive the resend request from the recipient 120. The server 130 sends or forwards the resend request to the sender 110 over the fourth band / channel 104 at step 430. The sender receives the resend request via the sender application.

[0113] If the sender 110 had sent the first communication to the recipient 120 (confer step 210), then the sender 110 will resend the first communication to the recipient 120 over the first band / channel 101 at step 412. The resultant receipt of the resent communication by the recipient 120 would inform the recipient 120 that the first communication is authentic. The sender 110 will respond to the server 130, over the fourth band / channel 104, with an updated first communication tuple at step 440. Accordingly, the server 130 will receive, at step 440, theattributes of the resent communication (i.e. the updated first communication tuple) from the sender 110. At step 450, the server 130 displays the updated first communication tuple in user-friendly format in the recipient application.

[0114] If the sender 110 had not sent the first communication nor any other communication to the recipient 120, then the sender 110 will respond, over the fourth band / channel 104, with a zero tuple to the server 130 at step 412N. At step 470, the server 130 displays a warning message (such as, “Sender did not send any communication to you”) in the recipient application.

[0115] The receipt of the warning message does not automatically lead to the sending of a scam report. A first of several possible scenarios is that the recipient 120 may have mistaken the sender of the first communication and directed the resend request to a wrong sender 110 at step 420. A second possible scenario is that the recipient 120 may be mistaken that a communication was even received at step 210. The warning message of step 470 may thus cause the recipient 120 to perform additional checks at his end, such as on the sender address and date of the first communication received at step 210; or whether a communication was indeed even received.

[0116] If the result of the additional checks is that the first communication is unauthentic, the recipient 120 may send a scam report via the recipient application, at step 480. At step 485, the server 130 sends a scam report to the sender 110. At step 490, the sender 110 sends acknowledgement of the scam report to the server 130. At step 495, the server 130 displays the sender acknowledgement of the scam report in the recipient application.

[0117] Figure 5 shows the protocol of a fourth of the options being performed. In the fourth option, the recipient 120, via the server 130, requests for the sender 110 to redirect the communication to an alternate address, whereby the resultant receipt of the redirected communication by the recipient 120 would inform the recipient 120 that the first communication (i.e. the earlier communication) is authentic. The protocol of the fourth option is as follows.

[0118] At step 210, the recipient 120 receives a first communication from the sender 110 through the first band / channel 101. Using the recipient application, the recipient 120 sends, at step 520, a redirect request to the server 130 on the second band / channel 102. The server 130 is configured to receive the redirect request from the recipient 120. The server 130 sends or forwards the redirect request to the sender 110 over the fourth band / channel at step 530. The redirect request is for the sender 110 to redirect the communication to the recipient 120 at an alternate address. The sender receives the redirect request via the sender application.

[0119] If the sender 110 had sent the first communication to the recipient 120 (confer step 210), then the sender 110 will redirect the first communication to the recipient 120 over the third band / channel 103 at step 512. The resultant receipt of the redirected communication by the recipient 120 would inform the recipient 120 that the first communication is authentic. Thesender 110 will respond to the server 130, over the fourth band / channel 104, with a redirected communication tuple at step 540. Accordingly, the server 130 will receive, at step 540, the attributes of the redirected communication (i.e. the redirected communication tuple) from the sender 110. At step 550, the server 130 displays the redirected communication tuple in user-friendly format in the recipient application.

[0120] If the sender 110 had not sent the first communication nor any other communication to the recipient 120, then the sender 110 will respond, over the fourth band / channel 104, with a zero tuple to the server 130 at step 512N. At step 570, the server 130 displays a warning message (such as, “Sender did not send any communication to you”) in the recipient application.

[0121] The receipt of the warning message does not automatically lead to the sending of a scam report. A first of several possible scenarios is that the recipient 120 may have mistaken the sender of the first communication and directed the redirect request to a wrong sender 110 at step 520. A second possible scenario is that the recipient 120 may be mistaken that a communication was even received at step 210. The warning message of step 570 may thus cause the recipient 120 to perform additional checks at his end, such as on the sender address and date of the first communication received at step 210; or whether a communication was indeed even received.

[0122] If the result of the additional checks is that the first communication is unauthentic, the recipient 120 may send a scam report via the recipient application, at step 580. At step 585, the server 130 sends a scam report to the sender 110. At step 590, the sender 110 sends acknowledgement of the scam report to the server 130. At step 595, the server 130 displays the sender acknowledgement of the scam report in the recipient application.

[0123] Figure 6 shows the protocol of a fifth of the options being performed. Under the fifth option, the sender 110 sends the first communication tuple after sending the first communication to the recipient 120. The protocol of the fifth option is as follows.

[0124] At step 210, the recipient 120 receives a first communication from the sender 110 through the first band / channel 101.

[0125] At step 650, the sender 110 also sends, through the fourth band / channel 104, the first communication tuple to the server 130 via the sender application. That is, the recipient 120 does not need to send a request for the sender 110 to send the first communication tuple. Accordingly, at step 650, the server 130 is configured to receive the first communication tuple from the sender 110 upon the sender 110 sending the first communication to the recipient 120.

[0126] At step 675, the server 130 forwards, over the second band / channel 102, the first communication tuple to the recipient 120. The first communication tuple (i.e. attributes of the sent communication) is displayed in user-friendly format in the recipient application.

[0127] At step 676, the recipient 120 verifies if the first communication tuple matches the key attributes observed in the first communication received at step 210. The comparison result indicates whether the first communication is authentic.

[0128] It is possible that scammers and spammers can perform step 210 of the fifth option, e.g. by fabricating and sending an email. However, they would not be able to communicate with the server 130 to send the first communication tuple, i.e. they would not be able to perform the step 650.

[0129] From the above discussion of the five options, the following is observed.

[0130] Initiation of the authentication of the received communication is by the recipient 120, where the recipient 120 can select any of the five options to authenticate received communication through the recipient application. The recipient selection is made known to the server 130 and the sender 110. For example, selection of the fifth option is made known in advance to the sender 110, so that when the sender 110 sends a communication to the recipient 120, the sender also sends the communication attributes, in accordance with the protocol of the fifth option.

[0131] When comparing attributes of a communication sent by the sender 110 with corresponding attributes of the communication received by the recipient 120, the comparison may also provide for tolerance between the time of the sent communication and the time of the received communication. The comparison result may indicate compliance with the tolerance, such as how the degree of discrepancy between the time of the sent communication and the time of the received communication measures against the acceptable range. A large discrepancy may be an indicator that the received communication is unauthentic. In such a scenario, any one or more of the options may be performed again to re-authenticate the received communication.

[0132] The protocol for the options caters for the scenario where the sender 110 has not sent any communication to the recipient 120. As mentioned above, this happens by the server 130 relaying a verification query, resend request or redirect request from the recipient 120 to the sender 110. If the server 130 receives from the sender 110 a denial of sending the communication in the form of a zero tuple, the server 130 will fail the authentication of the communication in response to the denial. The server 130 then transmits a zero tuple or warning to the recipient 120.

[0133] The server 130 is configured to facilitate independent operation of each of the five options. The independent operation allows the recipient 120 to dynamically switch / repeat / add options to check / confirm / reconfirm the authenticity of a communication. A non-exhaustive list of possible option sequences is shown in Table 2 below.Table 2 Non-exhaustive list of possible user selected verification sequencesUser Verification Sequence selected by User1. User 1 Option 12. User 2 Option 23. User 3 Option 34. User 4 Option 45. User 5 Option 56. User 6 Option 1 Option 37. User 7 Option 1 —> Option 48. User 8 Option 5 Option 19. User 9 Option 2 -»■ Option 3 — > Option 410. User 10 Option 2 Option 4 Option 3n User n Option p Option q — > > Option r

[0134] As such, the server 130 is configured to support one or more of the five options being selected and repeated in any order. After receiving a communication, the recipient 120 can choose:• whether or not to verify its authenticity• when to initiate the verification• which option to use• which option to add or repeat

[0135] This is in addition to the advantages of: having multiple secure bands / channels, having the dedicated server 130, the use of communication tuples, the single-use code, and the use of an alternate address (in the fourth option).

[0136] This user-led dynamic execution, variation and addition of verification options results in higher entropy for communication security. This is because, notwithstanding a scammer having no access to the secure second band / channel 102 and fourth band / channel 104, the scammer would not know the verification sequence chosen by the user / recipient 120. As such, a scammer would not be able to fabricate all the right verification outcomes and in the correct order of the selected verification sequence in realtime. For example, the Table 3 above shows that User 10 chooses to perform authentication in the following order: the second option, the fourth option and the third option. The verification outcome for User 10 is correspondingly the receipt of: a first communication tuple; a redirected communication; and a resent communication. The probability of a scammer fabricating the right verification outcomes, in the correct order, in realtime as User 10 activates the verification sequence, is extremely low.

[0137] It is also possible that the recipient application automatically performs a verification sequence, which follows a random sequence. In one implementation, the next stage happens only if a present stage authenticates the communication. E.g. the application randomly chooses a verification sequence: second option > fourth option > first option. The second stage (fourth option) is performed only if the communication is successfully authenticated in the first stage (second option), while the third stage (first option) is performed only if the communication is successfully authenticated in the second stage (fourth option). In another implementation, the recipient 120 can manually or the recipient application can automatically execute all three options (second option > fourth option > first option) in immediate succession, without even checking if the communication is successfully authenticated in the first stage (second option). A scammer would not know the verification sequence, which may even be randomly selected, as mentioned above. Nor would a scammer know if the verification sequence is a sequential dependency chain or a sequential independent execution. The probability of a scammer fabricating the right authentication outcomes is extremely low.

[0138] In addition to the above-mentioned random selection of the verification sequence, rules-based addition of options is also supported. For example, when the sender 110 does not respond (in the first to fourth options) or the first communication tuple does not match (in the first option), then the server 130 can add another authentication option to the verification sequence.

[0139] While only one of each entity is shown in Figure 1A, the system 100 may comprise a plurality of each entity. For example, the system may comprise a plurality of servers. Each of the plurality of servers can be located in the same location as or be remote from the server 130. For example, the system may comprise a plurality of first bands / channels. Each of the plurality of first bands / channels can be located in the same location as or be remote from the first band / channel 101.

[0140] The system 100 may authenticate one or more communication.

[0141] The system 100 or its functions may be implemented as a subsystem of sender systems or recipient systems.

[0142] Figure 7 is a block diagram illustrating a technical architecture 700 of a computing server for implementing the server 130, the method shown in Figure 1B and the protocols of the five options of Figures 2 to 6.

[0143] The technical architecture 700 includes a processor 702 (which may be referred to as a central processor unit or CPU) that is in communication with memory devices including secondary storage 704 (such as disk drives), read only memory (ROM) 706, random access memory (RAM) 708. The processor 702 may be implemented as one or more CPU chips. The technical architecture may further comprise input / output (I / O) devices 710, and network connectivity devices 712.

[0144] The secondary storage 704 is typically comprised of one or more disk drives or tape drives and is used for non-volatile storage of data and as an over-flow data storage device if RAM 708 is not large enough to hold all working data. Secondary storage 704 may be used to store programs which are loaded into RAM 708 when such programs are selected for execution.

[0145] In this embodiment, the secondary storage 704 includes a component 704a comprising non-transitory instructions operative by the processor 702 to perform various operations that implement the protocols of the first to the fifth options shown in Figures 2 to 6.

[0146] The ROM 706 is used to store instructions and perhaps data which are read during program execution. The secondary storage 704, the RAM 708, and / or the ROM 706 may be referred to in some contexts as computer readable storage media and / or non-transitory computer readable media.

[0147] I / O devices 710 may include printers, video monitors, liquid crystal displays (LCDs), plasma displays, touch screen displays, keyboards, keypads, switches, dials, mice, track balls, voice recognizers, card readers, paper tape readers, or other well-known input devices.

[0148] The processor 702 executes instructions, codes, computer programs, scripts which it accesses from hard disk, floppy disk, optical disk (these various disk-based systems may all be considered secondary storage 704), flash drive, ROM 706, RAM 708, or the network connectivity devices 712. While only one processor 702 is shown, multiple processors may be present. Thus, while instructions may be discussed as executed by a processor, the instructions may be executed simultaneously, serially, or otherwise executed by one or multiple processors.

[0149] The network connectivity devices 712 enable the technical architecture 700 to communicate with external systems, which may include distributed computing resources or cloud-based services.

[0150] Although the technical architecture 700 is described with reference to a computer, it should be appreciated that the technical architecture 700 may be formed by two or more computers in communication with each other that collaborate to perform a task. For example, but not by way of limitation, an application may be partitioned in such a way as to permit concurrent and / or parallel processing of the instructions of the application. Alternatively, the data processed by the application may be partitioned in such a way as to permit concurrent and / or parallel processing of different portions of a data set by the two or more computers. In an embodiment, virtualization software may be employed by the technical architecture 700 to provide the functionality of a number of servers that is not directly bound to the number of computers in the technical architecture 700. In an embodiment, the functionality disclosed above may be provided by executing the application and / or applications in a cloud computing environment. Cloud computing may comprise providing computing services via a networkconnection using dynamically scalable computing resources. A cloud computing environment may be established by an enterprise and / or may be hired on an as-needed basis from a third-party provider.

[0151] By programming and / or loading executable instructions onto the technical architecture 700, at least one of the CPU 702, the RAM 708, and the ROM 706 are changed, transforming the technical architecture 700 in part into a specific purpose machine or apparatus having the novel functionality taught by the present disclosure. It is fundamental to the electrical engineering and software engineering arts that functionality that can be implemented by loading executable software into a computer can be converted to a hardware implementation by well-known design rules. Such hardware implementations may include field-programmable gate arrays (FPGAs) or application-specific integrated circuits (ASICs), which can further enhance the system's performance for specific information processing tasks.

[0152] In the foregoing detailed description, embodiments of the present disclosure in relation to an authentication system and method are described with reference to the provided figures. The description of the various embodiments herein is not intended to call out or be limited only to specific or particular representations of the present disclosure, but merely to illustrate nonlimiting examples of the present disclosure. The present disclosure serves to address at least one of the mentioned problems and issues associated with the prior art. Although only some embodiments of the present disclosure are disclosed herein, it will be apparent to a person having ordinary skill in the art in view of the present disclosure that a variety of changes and / or modifications can be made to the disclosed embodiments without departing from the scope of the present disclosure. It will be understood by those skilled in the art that many variations of the embodiments can be made within the scope of the following claims. Moreover, features of one or more embodiments may be mixed and matched with features of one or more other embodiments. Therefore, the scope of the disclosure as well as the scope of the following claims is not limited to embodiments described herein.

Claims

CLAIMS1. A system for authenticating received communication, the system comprising:a server comprisingat least one memory; andone or more processors to execute instructions stored in the memory that configures the server to:facilitate a plurality of options to authenticate a communication received by a recipient, based on a technique that references the received communication; and execute the technique in accordance with protocol of a selected option, wherein one or more channels used by the server to facilitate the authentication of the communication is separate from the channel through which the communication is received by the recipient.

2. The system of claim 1, wherein the technique comprises the server being configured to:facilitate comparison of attributes of a sent communication from a sender against corresponding attributes of the received communication in accordance with the protocol of the selected one or more options, through a channel separate from the channel used by the received communication; andfacilitate resending of the communication from the sender in accordance with the protocol of the selected one or more options, through a channel separate from the channel used by the received communication.

3. The system of claim 2, wherein the protocol of a first of the options comprises further configuring the server to:receive a verification query and the attributes of the received communication from the recipient;forward the verification query to the sender;receive the attributes of the sent communication from the sender, in response to the verification query;perform the comparison, wherein the comparison result indicates whether the communication is authenticated; andtransmit the comparison result to the recipient.

4. The system of claim 2 or 3, wherein the protocol of a second of the options comprises further configuring the server to:receive a verification query from the recipient;forward the verification query to the sender;receive the attributes of the sent communication from the sender, in response to the verification query; andforward the attributes of the sent communication to the recipient to perform the comparison.

5. The system of claims 2 to 4, wherein the protocol of a third of the options comprises further configuring the server to:receive a resend request from the recipient; andforward the resend request to the sender, to resend the communication to the recipient, whereby the resultant receipt of the resent communication by the recipient would inform the recipient that the earlier received communication is authentic.

6. The server of claim 5, wherein the protocol of the third of the options comprises further configuring the server to:receive the attributes of the resent communication from the sender, in response to the resend request;forward the attributes of the resent communication to the recipient.

7. The system of claims 2 to 6, wherein the protocol of a fourth of the options comprises further configuring the server to:receive a redirect request from the recipient; andforward the redirect request to the sender, to redirect the communication to the recipient at an alternate address, whereby the resultant receipt of the redirected communication by the recipient would inform the recipient that the earlier received communication is authentic.

8. The server of claim 7, wherein the protocol of the fourth of the options comprises further configuring the server to:receive the attributes of the redirected communication from the sender, in response to the redirect request;forward the attributes of the redirected communication to the recipient.

9. The system of claims 2 to 8, wherein the protocol of a fifth of the options comprises further configuring the server to:receive the attributes of the sent communication from the sender upon the sender sending the communication to the recipient;forward the attributes of the sent communication to the recipient to perform the comparison.

10. The system of any one of the preceding claims, wherein the server is further configured to support one or more of the options being selected, executed and repeated in any order.

11. The system of any one of the preceding claims, wherein any initiation of the authentication of the received communication is by the recipient.

12. The system of claims 2 to 11, wherein the attributes comprise one or more of: sender address, recipient address, date, time, display name, agent name, call duration and single use code.

13. The system of claims 2 to 12, wherein the comparison provides for tolerance between the time of the sent communication and the time of the received communication; and the comparison result indicates compliance with the tolerance.

14. The system of claims 3 to 8, wherein the server is further configured to:receive a scam report from the recipient in response to failure of authentication of the received communication; andtransmit the scam report to the sender.

15. The system of any one of the preceding claims, wherein the communication comprises electronic and non-electronic communication.

16. The system of claim 15, wherein the electronic communication comprises emails, Short Messaging Service (SMS) messages, instant messages, phone calls, video calls, social media posts, forums, faxes, press releases, webpages and advertisements; and non-electronic communication comprises physical mails and physical meetings.

17. The system of any one of the preceding claims, wherein the server is further configured torelay a verification query or a resend request received from the recipient to the sender;receive from the sender a denial of sending the received communication;fail the authentication of the received communication in response to the denial; andtransmit a zero tuple or warning to the recipient.

18. A method for authenticating received communication, the method comprising:facilitating, through the use of a server and alternative secure channels, a plurality of options to authenticate a received communication received by a recipient, based on a technique that references the received communication;facilitating the selection of an option at any time;dynamically executing the technique based on the protocol of the selected option upon the option’s selection, the technique comprising effecting transmission of verification data from the sender of the communication, to be used to determine if the received communication is authentic;facilitating, if required, the selection of an additional option at any time; and dynamically executing, if required, the technique based on the protocol of the additional selected option sequentially, conditionally or concurrently, upon the option’s selection.