SYSTEM AND METHOD FOR PROCESSING AN AUTOMATED CALL BASED ON PREFERENCES AND CONDITIONS

• US 20190158663A1
• Filed: 01/02/2019
• Published: 05/23/2019
• Est. Priority Date: 02/28/2017
• Status: Active Grant

• Current Assignee: AT&T Intellectual Property I LP (AT&T, Inc.)
• Original Assignee: AT&T Intellectual Property I LP (AT&T, Inc.)
• Inventors: Dowlatkhah, Sangar, Shaw, Venson
• Granted Patent: US 10,819,851 B2
• Time in Patent Office: Days
• CPC Class Codes: H04B 17/00 Monitoring; Testing of line transmission systems H04B3/46; arrangements for monitoring or testing transmission systems employing electromagnetic waves other than radio waves H04B10/07
• CPC Class Codes: H04B 17/27 for locating or positioning the transmitter
• CPC Class Codes: H04B 17/309 Measuring or estimating channel quality parameters
• CPC Class Codes: H04B 17/318 Received signal strength
• CPC Class Codes: H04B 7/0417 Feedback systems
• CPC Class Codes: H04B 7/0617 for beam forming
• CPC Class Codes: H04B 7/0619 using feedback from receiving side feedback signaling for adaptive modulation/coding H04L1/0001
• CPC Class Codes: H04B 7/0697 using spatial multiplexing
• CPC Class Codes: H04L 5/0007 the frequencies being orthogonal, e.g. OFDM(A), DMT
• CPC Class Codes: H04M 2203/2027 Live party detection
• CPC Class Codes: H04M 2203/2072 Schedules, e.g. personal calendars
• CPC Class Codes: H04M 2250/12 including a sensor for measuring a physical value, e.g. temperature or motion
• CPC Class Codes: H04M 3/42153 by subscriber
• CPC Class Codes: H04M 3/436 Arrangements for screening incoming calls , i.e. evaluating the characteristics of a call before deciding whether to answer it based on the calling party profile H04M3/42059; based on location H04M3/42348; based on presence H04M3/42365; diversion H04M3/54
• CPC Class Codes: H04M 3/5158 in combination with automated outdialling systems devices for signalling identity of wanted subscriber H04M1/26
• CPC Class Codes: H04W 16/18 Network planning tools
• CPC Class Codes: H04W 16/28 using beam steering
• CPC Class Codes: H04W 64/00 Locating users or terminals or network equipment for network management purposes, e.g. mobility management
• CPC Class Codes: H04W 64/003 locating network equipment
• CPC Class Codes: H04W 8/18 Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
• CPC Class Codes: H04W 8/183 : Processing at user equipment or user record carrier

Abstract

A system can be operable to receive an automated call from a communications device, determine whether preferences associated with a called party identity), is applicable to the automated call, and determine whether a condition that precludes acceptance of the automated call is present. The determination of whether the condition is present can be based on information received from a sensory device coupled to the user device. In response to the condition being determined to be present, the automated call can be denied.

Claims

1. A method, comprising:

approving, by a network device comprising a processor, a call for connection to a user equipment, wherein the call has been identified as a robotic call directed to the user equipment;

determining, by the network device, whether user preference data accessible via a network data store is applicable to the robotic call, wherein the user preference data is representative of a preference associated with a user identity,

based on the user preference data and information received from a sensory device coupled to the user equipment, determining, by the network device, whether a condition exists that precludes acceptance of the robotic call, and

in response to the condition being determined to exist, denying, by the network device, the robotic call.

2. The method of claim 1, wherein the information received from the sensory device comprises a heart rate associated with the user identity.

3. The method of claim 1, wherein the information received from the sensory device indicates that a user associated with the user identity is engaged in a physical activity comprising a sport activity.

4. The method of claim 1, wherein the information from the sensory device indicates that a user associated with the user identity is engaged in a physical activity comprising an exercise activity.

5. The method of claim 1, wherein the information from the sensory device comprises location data, and wherein the location data correlates to a location of the user equipment.

6. The method of claim 1, wherein the user preference data comprises an indication to deny the robotic call based on the location data.

7. The method of claim 1, wherein the denying the robotic call comprises blocking the robotic call.

8. The method of claim 1, wherein the denying the robotic call comprises directing that a message related to the robotic call be stored for future access.

9. A system, comprising:

a processor; and

a memory that stores executable instructions that, when executed by the processor, facilitate performance of operations, comprising;

approving a call, wherein the call was identified as a robotic call, for connection to a user equipment;

determining whether a condition is present that precludes acceptance of the robotic call by the user equipment, wherein the determining comprises;

determining whether user preference data stored on a network data store, the user preference data being representative of a preference associated with a user identity, is applicable to the robotic call, and

in response to the user preference data being determined to be applicable to the robotic call, determining, based on the user preference data, whether the condition is present; and

in response to the condition being determined to be present, denying the robotic call.

10. The system of claim 9, wherein the user preference data comprises an indication to deny the robotic call based on information received from a sensory device coupled to the user device.

11. The system of claim 10, wherein the sensory device is operable to determine sleep statistics based on biometric measurements associated with the user identity made by the sensory device.

12. The system of claim 10, wherein the sensory device is operable to determine a heart rate of a user associated with the user identity based on heart beat measurements associated with the user identity made by the sensory device.

13. The system of claim 9, wherein the user preference data comprises an indication to deny the robotic call based on location data being determined to correlate to a location of the user device.

14. The system of claim 9, wherein the user preference data comprises an indication to deny the robotic call based on a calendar entry associated with the user identity.

15. The system of claim 14, wherein the determining whether the condition is present further comprises determining whether the calendar entry comprises a keyword that indicates the condition.

16. A machine-readable storage medium, comprising executable instructions that, when executed by a processor, facilitate performance of operations, comprising:

identifying, by a network device, a call from a communication device to a user equipment as a robotic call;

approving, by the network device, the robotic call for connection to the user equipment;

determining, by the network device, whether user preference data representative of a preference associated with a user identity and stored on a network data store, is applicable to the robotic call; and

in response to the user preference data being determined to be applicable to the robotic call, determining, by the network device, whether a condition is present that precludes acceptance of the robotic call.

17. The machine-readable storage medium of claim 16, wherein the operations further comprise, in response to the condition being determined not to be present, enabling, by the network device, the acceptance of the robotic call.

18. The machine-readable storage medium of claim 16, wherein the operations further comprise, in response to the condition being determined to be present, denying the robotic call.

19. The machine-readable storage medium of claim 18, wherein denying the robotic call comprises blocking the robotic call.

20. The machine-readable storage medium of claim 18, wherein denying the robotic call comprises directing that a message related to the robotic call be stored for future access.