Login| Sign Up| Help| Contact|

Patent Searching and Data


Title:
A SYSTEM AND METHOD FOR BLOCKING OR ALLOWING A CALL BASED ON USER CREDENTIALS
Document Type and Number:
WIPO Patent Application WO/2018/225024
Kind Code:
A1
Abstract:
Embodiments of the present disclosure may relate to a system [100] and a method [400] for blocking or accepting a call received from a first device [102A]. In an embodiment, the first device [102A] transmits an attach request (comprising at least one of the user intent, the call type and the caller details) to the network entity [104]. Subsequently, the network entity [104] extracts at least one of the user intent, the call type and the caller details from the received message to compare the at least one of the user intent, the call type and the caller details with a rejection list. The network entity [104] blocks the call in case any one of the user intent, the call type and the caller details is identified in the rejection list; or else, the network entity [104] establishes the call between the first device [102A] and the second device [102B].

Inventors:
DAVLOS EFSTRATIOS (IN)
MALLEPALLI BHARATHKUMAR REDDY (IN)
AGRAWAL GAURAV (IN)
Application Number:
PCT/IB2018/054148
Publication Date:
December 13, 2018
Filing Date:
June 08, 2018
Export Citation:
Click for automatic bibliography generation   Help
Assignee:
RELIANCE JIO INFOCOMM LTD (IN)
International Classes:
H04M3/42; H04M7/00
Foreign References:
US20170163811A12017-06-08
US20140376705A12014-12-25
Attorney, Agent or Firm:
SAHNEY, Garima (IN)
Download PDF:
Claims:
We claim

1. A method [400] for performing at least one action on a call received from a first device [102A], wherein the method [400] is being performed by a network entity [104], the method comprising:

- receiving an attach request from the first device [102A] for establishing the call with a second device [102B], wherein the attach request comprises the at least one user intent;

- comparing the at least one user intent with at least one rejection list to generate one of a positive response and a negative response, wherein

the positive response is generated in an event the at least one user intent is identified in the at least one rejection list,

the negative response is generated in an event the at least one user intent is absent in the at least one rejection list, and

the at least one rejection list is pre-defined by the second device [102B]; and - performing the at least one action on the call received from the first device [102A] based on one of the positive response and the negative response, wherein the at least one action corresponds to:

blocking the call in an event the positive response is generated, and

establishing the call between the first device [102A] and the second device [102B] in an event the negative response is generated.

2. The method [400] as claimed in claim 1, further comprising pre-configuring the network entity

[104] with the at least one rejection list. 3. The method [400] as claimed in claim 1, further comprising blocking the call in an event at least one of caller details and a call type is identified in the at least one rejection list.

4. The method [400] as claimed in claim 1, further comprising establishing the call between the first device [102A] and the second device [102B] in an event at least one of the caller details and the call type is absent in the at least one rejection list. The method as claimed in claims 3 and 4, wherein the call type includes a spam call, an IVR call, an automated call, a video spam call, a data email, an IP voice call and an IP video call.

The method as claimed in claims 3 and 4, wherein the caller details comprises a contact number, a user display name, an IP number, a Mobile Station International Subscriber Directory Number (MSISDN), an alternative MSIDN, an Internet Protocol (IP) address and reachable IP address

The method [400] as claimed in claim 1, further comprising displaying a notification message to at least one of the first device [102A] and the second device [102B], wherein the notification message corresponds to the at least one action performed on the call.

The method [400] as claimed in claim 1, wherein the at least one user intent is identified from at least one of a text message and a voice message.

The method [400] as claimed in claim 1, wherein the at least one rejection list comprises at least one of the at least one user intent, the caller details and the call type.

The method [400] as claimed in claim 1, wherein the at least one user intent corresponds to at least one of an anger expression, a happy expression, a sad expression, a comedy expression, an emergency expression and an urgent expression.

A network entity [104] for performing at least one action on a call received from a first device [102A], the network entity [104] comprising:

- a communication module [104A] configured to receive an attach request from the first device [102A] for establishing a call with a second device [102B], wherein the attach request comprises the at least one user intent; and

- a processing module [104B] configured to:

- compare the at least one user intent with at least one rejection list to generate one of a positive response and a negative response, wherein the positive response is generated in an event the at least one user intent is identified in the at least one rejection list,

the negative response is generated in an event the at least one user intent is absent in the at least one rejection list, and

the at least one rejection list is pre-defined by the second device [102B]; and

- perform the at least one action based on one of the positive response and the negative response, wherein the at least one action corresponds to:

blocking the call in an event the positive response is generated, and

establishing the call between the first device [102A] and the second device [102B] in an event the negative response is generated.

12. The network entity [104] as claimed in claim 11, further comprising a display unit [104C] configured to display a notification message to at least one of the first device [102A] and the second device [102B], wherein the notification message corresponds to the at least one action performed on the call.

13. The network entity [104] as claimed in claim 11, wherein the communication module [104A] is further configured to:

- pre-configure the network entity [104] with the at least one rejection list; and

- establish the call between the first device [102A] and the second device [102B] in an event at least one of caller details and a call type is absent in the at least one rejection list.

14. The network entity [104] as claimed in claim 11, wherein the processing module [104A] is further configured to block the call in an event at least one of the caller details and the call type is identified in the at least one rejection list.

Description:
A SYSTEM AND METHOD FOR BLOCKING OR ALLOWING A CALL BASED ON USER CREDENTIALS

FIELD OF INVENTION The present disclosure generally relates to mobile communications and is more specifically, directed to systems and methods for blocking or allowing a call based on user credentials.

BACKGROUND With the increasing pace of advancement in wireless communications, particularly, licensed segments (GMS, EDGE, HSPA, LTE, etc.) and unlicensed segments (Wi-Fi, UMA, DECT, Bluetooth, Zigbee, RFID, etc.), the wireless networks are widely deployed to provide a plurality of communication and content services. In addition, said wireless networks typically have multiple access points/networks that are configured to support communications for multiple users by sharing the available network resources. Also said networks poses several additional features such as more reliable protocols, communications network and consumer hardware available.

Further, it is evident that a computing device or a smartphone ecosystem has also tremendously improved and has therefore, become widespread with additional value added services such as voice calling, messaging, video calling, etc. One of the important and valuable tools/features of communication in the smartphone device is voice call and message because of the voice identification, behavior, accent, emotion and additional information that a user may easily and efficiently communicate in the call and message. Other such commercially popular features displayed on the user device are the caller I D and rich communication message/s that enable the users to decide whether or not to accept an incoming call.

Moreover, said smartphone ecosystems are embedded with an integrated conversational interface having enhanced voice enabled features (speech command) and natural language recognition to enable the users to dial numbers or send messages using the speech commands. Also, the conversational interface displays the functions/commands on the recipient device with an intent text message in the incoming call, wherein said conversation interface and ability to obtain information to perform follow-on task, are implemented via command module, natural language module, dialog module, task management module, information management module and/or a plurality of external services. In addition, said voice enabled assistance features are implemented via various platforms, such as device APIs, web, email, etc., while the conversational interface is implemented via third party's applications such as Google Voice application, Nuance application, Diction application, etc.

Further, while the users can anytime reject or hang up the call, it is more preferable to the users that said unwanted call is not allowed to sustain in the first place followed by a notification. A huge escalation in advanced features such as intent communication voice call, video call and messaging with rich communication message has resulted in an arena of new technology development. However said features are unable to efficiently block spam calls/unwanted calls, thereby often irritating and disturbing the users. In this regard, there exists several known solutions to overcome the limitations of blocking the spam/unwanted calls. In one of said solutions, the block requests made by the user (recipient) are processed to decide the rejection and/or acceptance of said call. In another conventional system, the user (recipient) personally connects to a service center to inform about spam/unwanted contact numbers, thereby blocking the calls. However, said conventional systems are not efficient in blocking the spam/unwanted calls from an unspecified contact numbers and therefore, poses other limitations, inter alia, involvement of multiple people and lack of security against a person in attempting to block another person's phone number. Moreover, it is pertinent to note that said conventional systems not only failed to automatically block/accept and control a DND (Do Not Disturb) call based on intent communication voice call, but also lacked prioritization of the incoming intent communication calls with rich communication message with the DND features.

Accordingly, in order to overcome the aforementioned problems inherent in the existing solutions for blocking the spam/unwanted calls, there exists a need of an efficient mechanism to perform an action on a call i.e. automatically decide the blocking or accepting of the call based on user credentials such a user intent, a call type and/or caller details. SUMMARY

This section is provided to introduce certain objects and aspects of the present disclosure in a simplified form that are further described below in the detailed description. This summary is not intended to identify the key features or the scope of the claimed subject matter.

Embodiments of the present disclosure may relate to a method for performing at least one action on a call received from a first device, wherein the method is being performed by a network entity, the method comprising: receiving an attach request from the first device for establishing the call with a second device, wherein the attach request comprises the at least one user intent; comparing the at least one user intent with at least one rejection list to generate one of a positive response and a negative response, wherein the positive response is generated in an event the at least one user intent is identified in the at least one rejection list, the negative response is generated in an event the at least one user intent is absent in the at least one rejection list, and the at least one rejection list is pre-defined by the second device; and performing the at least one action on the call received from the first device based on one of the positive response and the negative response, wherein the at least one action corresponds to: blocking the call in an event the positive response is generated, and establishing the call between the first device and the second device in an event the negative response is generated.

Further, the embodiments of the present disclosure encompass a network entity for performing at least one action on a call received from a first device, the network entity comprising: a communication module configured to receive an attach request from the first device for establishing a call with a second device, wherein the attach request comprises the at least one user intent; and a processing module configured to: compare the at least one user intent with at least one rejection list to generate one of a positive response and a negative response, wherein the positive response is generated in an event the at least one user intent is identified in the at least one rejection list, the negative response is generated in an event the at least one user intent is absent in the at least one rejection list, and the at least one rejection list is pre-defined by the second device; and perform the at least one action based on one of the positive response and the negative response, wherein the at least one action corresponds to: blocking the call in an event the positive response is generated, and establishing the call between the first device and the second device in an event the negative response is generated. BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are incorporated herein, and constitute a part of this disclosure, illustrate exemplary embodiments of the disclosed methods and systems in which like reference numerals refer to the same parts throughout the different drawings. Components in the drawings are not necessarily to scale, emphasis instead being placed upon clearly illustrating the principles of the present disclosure. Some drawings may indicate the components using block diagrams and may not represent the internal circuitry of each component. It will be appreciated by those skilled in the art that disclosure of such drawings includes disclosure of electrical components or circuitry commonly used to implement such components.

FIG.l illustrates an exemplary system architecture [100] for performing at least one action on a call received from a first device, in accordance with an embodiment of the present invention.

FIG. 2 illustrates an exemplary high level logical flow system architecture for performing at least one action on a call received from a first device, in accordance with an embodiment of the present invention.

FIG. 3 illustrates an exemplary signaling diagram [300] relating to a pre-configuring of a network entity with at least one rejection list, in accordance with an embodiment of the present invention.

FIG. 4 illustrates an exemplary method flow diagram [400] for performing at least one action on a call received from a first device, in accordance with an embodiment of the present invention.

FIG.5 illustrates an exemplary signaling diagram [300] relating to a call flow in an internetwork operator scenario, in accordance with an embodiment of the present invention. DETAILED DESCRIPTION

In the following description, for the purposes of explanation, various specific details are set forth in order to provide a thorough understanding of embodiments of the present disclosure. It will be apparent, however, that embodiments of the present disclosure may be practiced without these specific details. Several features described hereafter can each be used independently of one another or with any combination of other features. An individual feature may not address any of the problems discussed above or might address only one of the problems discussed above. Some of the problems discussed above might not be fully addressed by any of the features described herein. Example embodiments of the present disclosure are described below, as illustrated in various drawings in which like reference numerals refer to the same parts throughout the different drawings.

Embodiments of the present disclosure may relate to a system and a method for either blocking or allowing/accepting a call based on user credentials such as a user intent, a call type and caller details. The system comprises a network entity and at least two devices i.e. a first device and a second device, wherein the at least two devices and the network entity communicate to each other through one of a wired medium and a wireless medium. I n an event a first user using the first device (also referred to as calling device) wishes to call a second user using the second device (also referred to as recipient device), the first user using the first device may send an attach request to the network entity, wherein the attach request comprises at least one of the at least one user intent, the call type and the caller details. The network entity subsequently may compare at least one of the at least one user intent user intent, the call type and the caller details with at least one rejection list to decide whether the call has to be blocked or allowed/accepted. The network entity may block the call if at least one of the at least one user intent, the call type and the caller details is identified in the at least one rejection list. Alternatively, the network entity may establish the call between the first device and a second device if at least one of the at least one user intent, the call type and the caller details is absent in the at least one rejection list. Additionally, the system may further display a notification message to at least one of the at least two devices indicating blocking/accepting of the call. The present invention also encompasses deciding on whether the communication service has to be blocked or allowed/accepted, wherein the communication service may include but not limited to video calls, messaging, RCS services, file transfer and video share.

The "network entity" as used herein may comprise of one or more components, wherein said components may include, but not limited to, a communication module, a processing module, a storage unit and a display unit. The network entity may refer to one of an eNodeB, a Base Transceiver Station (BTS), Base Station Controller (BSC), a Radio Network Controller (RNC), a Telephony Application Server (TAS) and any such device having capability to handle the communication.

The "at least two devices (the first device and the second device)" as used herein may include, but not limited to, a smart phone, a feature phone, a tablet, a phablet and any such device obvious to a person skilled in the art. Further, the first device and the second device may comprise an input means such as a keyboard, an operating system, a memory unit, a display interface, etc. More particularly, said devices may comprise a conversational interface (for example speech command and detection) along with a natural language recognition system, wherein the natural language recognition system may be implemented using at least one platform such as device APIs, web, email, for facilitating speech commands to dial contact numbers. Also, in an embodiment, ability to obtain information and perform a task of the conversational interface may be implemented using a command module, a natural language module, a dialog module, a task management module, an information management module and a plurality of external services.

The "at least one user intent" as used herein corresponds to what a user intends. More particularly, the at least one user intent corresponds to at least one of an anger expression depicting angry mood of the user, a happy expression depicting happiness of the user, a sad expression depicting sadness of the user, a comedy expression depicting comedy mood of the user,, an emergency expression depicting emergency of the user, and an urgent expression depicting urgency of the user. The at least one user intent may either be determined based on analysis of a text message, a voice message or a combination thereof. Moreover, in case of voice message, a further conversion to text may be performed to determine the at least one user intent. The "call type" as used herein comprises a spam call, an IVR call, an automated call, a video spam call, a data email, an I P voice call and an I P video call. The "caller details" as used herein comprises contact numbers, a user display name, IP numbers, Mobile Station International Subscriber Directory Number (MSISDN), an Internet Protocol (I P) address, a Mobile Station International Subscriber Directory Number (MSISDN), an alternative MSIDN, an Internet Protocol (IP) address and reachable IP address, wherein the caller details are stored in a personal contact list of at least one of the first device and the second device.

The "at least one rejection list" as used herein comprises at least one of the at least one user intent, the call type and the caller details. In an embodiment, the at least one rejection list is predefined by the second device. As illustrated in FIG. 1, the present disclosure encompasses a system [100] comprising a network entity [104] and at least two devices i.e. a first device [102A] and a second device [102B] in accordance with an embodiment of the present invention. Further, the network entity [104] may comprise a communication module [104A], a processing module [104B], a display unit [104C], a storage unit [104D] and a cellular radio [104E] connected with an antenna [108] .

The user enters at least one of the text message or the voice message using the first device [104A], i.e. the first user using the first device [102A] may invoke the call by voice command or by a normal call procedure such as dialing the number from the dial pad or selecting the number from the contact book or dialing the number from the call log or by a Do Not Disturb (DND) system by transmitting a text message/voice message to the intent service. Thereafter, the first device [102A] may be configured to extract/identify at least one of the at least one user intent, the call type and the caller details from said message i.e. text message or voice command. Further, the first device [102A] may be configured to transmit the attach request to the communication module [104A] of the network entity [104], wherein the attach request comprises at least one of the at least one user intent, the call type and the caller details. The communication module [104A] of the network entity [104] on receiving the attach request from the first device [102A], may be integrally coupled to the processing module [104B] to transmit at least one of the at least one user intent, the call type and the caller details to the processing module [104B] of the network entity [104] .

The processing module [104B], on receiving at least one of the at least one user intent, the call type and the caller details, may be configured to extract/identify at least one of the at least one user intent, the call type and the caller details i.e. decode at least one of the at least one user intent, the call type and the caller details, wherein at least one of the at least one user intent, the call type and the caller details is identified from the text message and the voice message or a combination thereof based on the inputs received from the first device [102A] . In an event, the voice message is received, the processing module [104B] may be configured to first convert the voice message to a text using a network or a local system and subsequently convert the text to the at least one user intent. I n an embodiment where the voice message is easily understandable/decodable, the processing module [104B] may be configured to directly convert the voice message to the at least one user intent. Further, in an event, the text message is received, the processing module [104B] may be configured to convert the text message to the at least one user intent. Subsequently, the processing module [104B] may be configured to compare at least one of the at least one user intent, the call type and the caller details with the at least one rejection list, wherein the at least one rejection list is pre-defined by the second device [102B] and further comprises at least one of the at least one user intent, the call type and the caller details. Pursuant to the comparison, the processing module [104B] may be configured to generate one of a positive response and a negative response, wherein the positive response is generated in an event at least one of the at least one user intent, the call type and the caller details is identified in the at least one rejection list and the negative response is generated in an event at least one of the at least one user intent, the call type and the caller details is absent in the at least one rejection list.

Thereafter, the processing module [104B] may be configured to perform the at least one action i.e. blocking the call or allowing/accepting the call, wherein the at least one action is based on one of the positive response and the negative response. More specifically, in an event the positive response is generated, the at least one action corresponds to blocking the call i.e. the processing module [104B] may be configured to block the call received from the first device [102A], while in another event where the negative response is generated, the at least one action corresponds to establishing the call between the first device [102A] and the second device [102B] .

The display unit [104C] of the network entity [104] may be integrally coupled to the processing module [104B] and the communication module [104A] to display the notification message to at least one of the first device [102B] and the second device [102B], wherein the notification message corresponds to the at least one action performed on the call i.e. blocking the call or accepting/allowing the call.

Further, the storage unit [104D] of the network entity [104] may be integrally coupled to the processing module [104B], the communication module [104A] and the display unit [104C] to store and update the information relating to at least one of the attach request, the at least one rejection list and any such information as may be obvious to person skilled in the art. The storage unit [104D] may include, but not limited to, a volatile memory, non-volatile memory, a remote storage, a cloud storage, high-speed random access memory and/or non-volatile memory, such as one or more magnetic disk storage devices, one or more optical storage devices, and/or flash memory (e.g., NAND, NOR) or a combination thereof.

Furthermore, the cellular radio [104E] of the network entity [104] may be connected to the antenna [108] for receiving and transmitting communication signals and information as encompassed by the present invention. FIG. 2 illustrates an exemplary high level logical flow system architecture for performing the at least one action on the call received from the first device [102A], in accordance with an embodiment of the present invention. The at least two devices (the first device [102A] and the second device [102B]) may be integrated with the conversational dialog and the rich communication message to enable the user to input the call in the conversational interface. The system may comprise a Bot As a Service (BAaS) with a machine language tool along with an intent manager to provide input to the a service network operator zone to filter the DND call for the voice enabled intent recognition call. The Bot service, as used herein, may be performed using a bot which may include web bot, mobile bot, device specific bot (internet robots) for performing various functions such as indexing a given data. Further, the BAaS is a platform based environment that may be configured to allow the user to create a bot without explicitly programming any functionality. The BAaS may be further configured to enable the user to learn from domain specific knowledge, wherein the domain is customer specific. Further, the BAaS may be configured to provide user defined response in a form of text, graphics, voice, video, hyperlinks, etc. Also, the BAaS may be configured to encapsulate and disseminate user defined troubleshooting knowledge. Further, the intent manager, in an embodiment, may be a general purpose or a dedicated processor or a micro-controller configured to read the indexed data received from the BAaS. In another embodiment, the intent manager may be a micro service platform that provides the intent label behind a user query. In yet another embodiment, the intent manager may be a machine learning platform. Further, a Logical Box of the system may be configured to check in for the intent and context of the call to determine whether the call has to be blocked or allowed/accepted. In an exemplary embodiment, the logical box may be a decision box comprising a set of instructions stored in the network entity [104] for performing respective function of analyzing the intent and deciding on the blocking or accepting the call. Further, the intent manager and the logic module may be referred to as the communication module [104A], while a service network operator zone may correspond to the network entity [104] .

FIG. 3 illustrates exemplary signaling diagram [300] relating to the pre-configuring of the network entity [104] with the at least one rejection list, in accordance with an embodiment of the present invention. As illustrated in FIG. 3, the at least one action, such as blocking or accepting a call, may be performed upon setting-up or pre-configuring the network entity [104] with the at least one rejection list, wherein the pre-configuration may be assisted by the communication module [104A] . An intent manager, a service module and a Telephone Application Server (TAS) may be referred to as sub-components of the communication module [104A] of the network entity [104], wherein the telephony application server may be invoked by the first device [102A] . In an event, the at least one intent is recognized to be related to activation of a Do Not Disturb (DND) service against a contact number, the service module may use a U nstructured Supplementary Service Data (USSD) supplementary activation in a session initiation protocol or any such protocol as may be obvious to a person skilled in the art for said activation of the DND i.e. the service module may be configured to use a specific star code that may be realized at the TAS. Also, the TAS may update a Home Subscriber Server (HSS) with the activation pursuant to successful activation. Additionally, the present invention encompasses prioritizing and profiling a related configuration, wherein the prioritizing and profiling may be implemented at the network entity [104] . In an embodiment, the prioritizing and profiling may be handled via various extension applications for example, an administrator device (Admin login).

FIG. 4 illustrates an exemplary method flow diagram [400] for performing the at least one action on the call received from the first device [102A], in accordance with an embodiment of the present invention. The method flow [400] initiates at step 402 where the user using the first device [104A] enters at least one of the text message or the voice message, i.e. the first user using the first device [102A] may invoke the call by voice command or by a normal call procedure and subsequently transmit the attach request to the communication module [104A] of the network entity [104], wherein the attach request comprises at least one of the at least one user intent, the call type and the caller details. Additionally, the communication module [104A] may be configured to pre- configure the network entity [104] with the at least one rejection list before initiating the performing of the at least one action.

At step 404, the communication module [104A] may be configured to receive the attach request from the first device [102A], At step 406, the communication module [104A] may further be configured to transmit at least one of the at least one user intent, the call type and the caller details to the processing module [104B] .

At step 408, the processing module [104B], on receiving at least one of the at least one user intent, the call type and the caller details, may be configured to extract/identify the at least one user intent, the call type and the caller details from the text message, the voice message or a combination thereof based on the inputs received from the first device [102A] . In an event, the voice message is received, the method [400] may lead to step 410. Alternatively, in an event the text message is received, the method [400] may lead to step 412. At step 410, on receiving the voice message, the processing module [104B] may be configured to convert the voice message to text using a network or a local system. In an embodiment where the voice message is easily understandable/decodable, the method [400] leads to step 412.

At step 412, the processing module [104B] may be configured to convert the text to the at least one user intent.

At step 414, the processing module [104B] may be configured to compare at least one user intent, the call type and the caller details with the at least one rejection list, wherein the at least one rejection list may be pre-defined by the second device [102B] and further comprises at least one of the at least one user intent, the call type and the caller details. In an event the at least one of the at least one user intent, the call type and the caller details is identified in the at least one rejection list, the positive response is generated and the method leads to step 416. Alternatively, in an event at least one of the at least one user intent, the call type and the caller details is absent in the at least one rejection list, the negative response is generated and the method leads to step 418.

Thereafter, at step 416, the processing module [104B], may be configured to block the call based on the positive response.

At step 418, the processing module [104B], may be configured to accept/allow the call based on the negative response.

At step 420, the display unit [104C] may be configured to display the notification message to at least one of the first device [102B] and the second device [102B], wherein the notification message corresponds to the at least one action performed on the call i.e. blocking the call or accepting/allowing the call. Further, FIG.5 illustrates an exemplary signaling diagram [300] relating to a call flow in an internetwork operator scenario, in accordance with an embodiment of the present invention. More particularly and as illustrated in FIG.5, the first device [102A] and the second device [102B] may be operable with a subscriber identity module (SIM) comprising an I MSI and a unique key shared with the network operator, wherein the network operator of the first device [102A] and the second device [102B] may or may not be different. In an event, the first device [102A] via a network A wishes to establish a call with the second device [102B] having network B, the network A may transmit a service request to the first device [102A] as well as network B pursuant to which the network B may ask a DND server for permission to establish the call. In case the DND server allows for the call, the network B may transmit the service request to the second device [102B]. Subsequently, the second device [102B] may transmit the service response to the first device [102A] and consequently, the call may be established between the first device [102A] and the second device [102B] . Alternatively, in case the DND server does not allow for the call, the network B may transmit the service terminate response to the first device [102A] and as a result, the call may not be established. In an embodiment, the DND server may be referred to as a subcomponent of the communication module [104A] .

Thus, the present disclosure encompasses a system [100] and method [400] for performing the at least one action on the call received from the first device [102A] based on the response i.e. the call may be blocked in an event the positive response is generated (i.e. at least one of the at least one user intent, the call type and the caller details is identified in the at least one rejection list) whereas the call may be established between the first device [102A] and the second device [102B] in an event the negative response is generated (i.e. at least one of the at least one user intent, the call type and the caller details). Further, the system [100] and the method [400] in turn facilitates efficient identification of an unknown call that a second device [102B] receives and provide the details of the reasons, user intent and user's details. Another object of the present invention may be to enable the users with automatic control of the spam/unwanted voice calls and messages. Yet another object of the present invention may be to profile and prioritize the incoming calls with rich communication message with the DND features to provide the user priority for handling such calls. Though a limited number of the network entity [104], the devices [102A, 102B] and the components/sub systems therein, have been shown in the figures; however, it will be appreciated by those skilled in the art that the system [100] of the present disclosure encompasses any number and varied types of said entities/elements i.e. the network entity [104] the devices [102A, 102B], and the components/sub systems therein.

While considerable emphasis has been placed herein on the disclosed embodiments, it will be appreciated that many embodiments can be made and that many changes can be made to the embodiments without departing from the principles of the present disclosure. These and other changes in the embodiments of the present disclosure will be apparent to those skilled in the art, whereby it is to be understood that the foregoing descriptive matter to be implemented is illustrative and non-limiting.