In many contexts, an enterprise or other stakeholder may be required and/or may desire to keep track of and/or exercise control over network or other communications, e.g., communications among employees of a corporation and/or between such employees and third parties, such as the corporation's customers and/or members of the general public. The requirements of the Securities and Exchange Commission, National Association of Securities Dealers, HIPAA, Sarbanes-Oxley Act of 2002, and various anti-harassment and anti-discrimination laws are among the many legal and regulatory requirements that may give rise to a need on the part of a corporation or other entity to be able to monitor, record, archive, index, retrieve, analyze, and/or control employee (or other user) communications.
The task of monitoring and controlling voice communications has been challenging. Not only has voice communication processing technology been traditionally limited, voice communication typically involves the use of communication devices and/or infrastructure beyond the control of the responsible entity. Therefore, there is a need for an effective way to monitor and/or control voice and other communications, including without limitation communications made using telephonic technology.
Various embodiments of the invention are disclosed in the following detailed description and the accompanying drawings.
The invention can be implemented in numerous ways, including as a process, an apparatus, a system, a composition of matter, a computer readable medium such as a computer readable storage medium or a computer network wherein program instructions are sent over optical or electronic communication links. In this specification, these implementations, or any other form that the invention may take, may be referred to as techniques. A component such as a processor or a memory described as being configured to perform a task includes both a general component that is temporarily configured to perform the task at a given time or a specific component that is manufactured to perform the task. In general, the order of the steps of disclosed processes may be altered within the scope of the invention.
A detailed description of one or more embodiments of the invention is provided below along with accompanying figures that illustrate the principles of the invention. The invention is described in connection with such embodiments, but the invention is not limited to any embodiment. The scope of the invention is limited only by the claims and the invention encompasses numerous alternatives, modifications and equivalents. Numerous specific details are set forth in the following description in order to provide a thorough understanding of the invention. These details are provided for the purpose of example and the invention may be practiced according to the claims without some or all of these specific details. For the purpose of clarity, technical material that is known in the technical fields related to the invention has not been described in detail so that the invention is not unnecessarily obscured.
Telephonic communication compliance processing is disclosed. In some embodiments, compliance processing includes redirecting and monitoring one or more telephonic communications of interest. Calls to and/or from one or more communication participants of interest are redirected through a compliance system accessible via a telephonic network, e.g., a telephone/cellular service provider network. A communication participant includes any users, systems, and/or devices involved in a communication. In some embodiments, a compliance system is configured to serve as a redirection point for calls associated with a communication participant of interest, thereby enabling various routing and compliance processing to be performed without necessarily involving a change in a third party telecommunications service provider's network or equipment.
In the example shown, monitored call participant 106 has a public call number and a non-public call number. The call numbers are used as identifiers of call participants. A call number may be a telephone number, extension number, IP address, and any numeric, alphabetic, alphanumeric or other identifier. In some embodiments, the public call number associated with monitored call participant 106 would be provided to one or more external calling parties or users, such as external call participant 108, to be used to place a call to the monitored call participant 106. In some embodiments, dialing the public call number associated with monitored call participant 106 results in a call being placed to compliance system 102, which is configured to recognize the call as being associated with monitored call participant 106 and establish a three way connection between the calling party (e.g., external call participant 108), the monitored call participant 106, and the compliance system 102, e.g., by using the non-public call number associated with monitored call participant 106 to conference monitored call participant 106 in to the call terminated between external call participant 108 and compliance system 102, thereby enabling the compliance system 102 to monitor and/or control the communications between external call participant 108 and monitored call participant 106.
In some embodiments, dialing the public call number associated with the monitored call participant 106 results in a call placed directly to call participant 106. Compliance processing is performed either in a compliance processing module of call participant 106 or an external compliance system associated with call participant 106. In some embodiments, call participant 106, upon receiving an incoming call, e.g., from an external call participant, first conferences in an associated compliance system prior to connecting a user associated with call participant 106 to the call, e.g., by providing a “ring” signal or indication to the user.
In some embodiments, the user of a device associated with monitored call participant 106 is not made aware of the non-public call number. In some embodiments, the user associated with monitored call participant 106 believes the public call number is the only call number associated with monitored call participant 106.
In some embodiments, when monitored call participant 106 dials an outgoing destination call number, a call is established with compliance system 102 and the outgoing destination call number is passed to the compliance system. The compliance system terminates a new call to the passed destination number and conferences the monitored call participant 106 with the terminated new call to the passed destination number. In some embodiments, telecommunication equipment associated with monitored call participant 106, e.g., a mobile or desktop telephone, is configured to only receive calls to the non-public number from compliance system 102 and make direct calls only to compliance system 102. In some embodiments, hardware, firmware, or software may be used to limit equipment associated with monitored call participant 106 to placing calls directly to and/or receiving calls at the non-public number from compliance system 102.
In some embodiments, call requester identifier data (i.e., Caller-ID data) is modified to allow the call participants to be unaware of the call redirections, e.g., by sending Caller ID data associated with external call participant 108 to equipment associated with monitored call participant 106 in connection with the call terminated by compliance system 102 to monitored call participant 106, e.g., using the non-public call number associated with monitored call participant 106, to conference monitored call participant 106 in to the call original terminated between external call participant 108 and compliance system 102, e.g., as a result of external call participant 108 dialing the public call number associated with monitored call participant 106.
Since compliance system 102 redirects all incoming and outgoing calls for monitored call participant 106, the compliance system is able to perform compliance processing on all calls associated with monitored call participant 106.
Any telephonic equipment may be associated with the call participants. For example, the call participants may be associated with mobile phones, telephones, computers, and/or any devices able to send and receive telephonic data. Any one or a combination of telecommunications networks may be used to transmit communication between the compliance system and the call participants, including without limitation, a direct or indirect physical connection, telephone service provider network, mobile communication network, public switched telephone network (PSTN), Blackberry network, PBX (Private Branch Exchange, i.e., a private telephone network within an enterprise) phone network, Voice-over-IP network, Internet, intranet, LAN, WAN, and/or any other forms of connecting two or more systems together. The telephone service provider network includes mobile communication network, public switched telephone network (PSTN), Blackberry network, Voice-over-IP network and/or any other forms of telecommunication network infrastructure. In some embodiments, monitored call participant 106 is configured to communicate with compliance system 102 by modifying or otherwise configuring firmware associated with monitored call participant 106 to perform such communication. In one embodiment, a communication policy, i.e. a policy regarding how to establish communication with other call participants, may be established and/or implemented by hardware design or modification of telecommunications equipment associated with monitored call participant 106. In one embodiment, the communication policy may be determined by software running on a processor associated with monitored call participant 106. Any suitable technique for enabling, determining, configuring, and/or enforcing may be used.
In some embodiments, compliance system 102 includes any component necessary to perform redirection and/or compliance processing. One or more telephonic identifiers, including telephone numbers, extension numbers, IP numbers, and numeric, alphabetic or alphanumeric identifier, may be associated with compliance system 102. Storage 104 may be a part of the compliance system or connected to the compliance system together through a connection or a network. The compliance system and a device associated with a monitored call participant may together comprise a single device, i.e., in one embodiment a telephone associated with the monitored call participant includes built-in compliance system processing inside the device.
Compliance processing may include processing based on at least a portion of the information transferred in the call. Information transferred in the call may include voice data (including conversation content and tone/character/accent/gender of voice), background call noise, any audible data, any binary data, data associated with devices of with call participants, data associated with communication service providers, data associated with routing devices, and/or data associated with other devices associated with the compliance system. Based at least in part on the information being processed, the calls may be monitored, recorded, indexed, retrieved, analyzed, controlled, blocked, redacted, modified, archived, and/or any other processing can be performed. In some embodiments, a call is blocked according to a call blocking policy, e.g., a call is blocked if one of the call participants is not on a list of allowed call participants, does not belong to a group of allowed call participants, is an external call participant, is on a list of non-allowed call participants, or belongs to a group of non-allowed call participants. A call may be blocked or modified during a call. For example, in one embodiment a call is terminated if information that violates a policy is discussed, as detected during the call by processing voice data communicated during the call, e.g., by detecting a key word or phrase. The blocked or modified call can be archived and reported to appropriate authorities. Audio data processing is described in greater detail in a U.S. patent application Ser. No. 10/884,453 entitled METHOD AND SYSTEM FOR PROCESSING AUDITORY COMMUNICATIONS filed Jul. 1, 2004.
In some embodiments, all or a portion of information transferred during a call may be archived. The determination of which transferred information portion to archive may be based at least in part on a preconfigured and/or dynamically configured archive policy. The policy may be based at least in part on any of the transferred information. Archiving includes saving transferred information to any storage medium, including hard drives, optical storage, data tape, audio tape, backup server, and networked storage (e.g., Storage Area Network, Network Attached Storage). Information may be converted (i.e. audio digitalization, voice to text translation, encoding format conversion, data filtering), compressed, and/or encrypted before being archived. Other compliance processing besides blocking, modifying, archiving may be performed by the compliance system.
For example, when a call either is made to or from monitored call participant 306, compliance system 302 is notified of the call. If a connection does not already exist between monitored call participant 306 and compliance system 302, a connection is established between them before a user associated with monitored call participant 306 is able to communicate with another call participant. In some embodiments, a call is made to the compliance system before any user communication is allowed, and the compliance system call is conferenced with both the incoming or outgoing call of a monitored call participant. This allows compliance system 302 to potentially process all information communicated between the call participants. In some embodiments, compliance system 302 has control over monitored call participant 306. For example, compliance system 302 may filter or block communication desired by monitored call participant 306.
Although the foregoing embodiments have been described in some detail for purposes of clarity of understanding, the invention is not limited to the details provided. There are many alternative ways of implementing the invention. The disclosed embodiments are illustrative and not restrictive.
Number | Name | Date | Kind |
---|---|---|---|
5416831 | Chewning et al. | May 1995 | A |
5432845 | Burd et al. | Jul 1995 | A |
5493692 | Theimer et al. | Feb 1996 | A |
5557655 | Lantto | Sep 1996 | A |
5590171 | Howe et al. | Dec 1996 | A |
5627764 | Schutzman et al. | May 1997 | A |
5784561 | Bruno et al. | Jul 1998 | A |
5796948 | Cohen | Aug 1998 | A |
5839067 | Jonsson | Nov 1998 | A |
5878351 | Alanara et al. | Mar 1999 | A |
5881132 | O'Brien et al. | Mar 1999 | A |
5890064 | Widergen et al. | Mar 1999 | A |
5890163 | Todd | Mar 1999 | A |
5983096 | Lietha et al. | Nov 1999 | A |
6028917 | Creamer et al. | Feb 2000 | A |
6064963 | Gainsboro | May 2000 | A |
6085099 | Ritter et al. | Jul 2000 | A |
6085231 | Agraharam et al. | Jul 2000 | A |
6112078 | Sormunen et al. | Aug 2000 | A |
6128739 | Fleming, III | Oct 2000 | A |
6141686 | Jackowski et al. | Oct 2000 | A |
6163546 | Sipila | Dec 2000 | A |
6167513 | Inoue et al. | Dec 2000 | A |
6249584 | Hamalainen et al. | Jun 2001 | B1 |
6301608 | Rochkind | Oct 2001 | B1 |
6311055 | Boltz | Oct 2001 | B1 |
6313734 | Weiss et al. | Nov 2001 | B1 |
6327343 | Epstein et al. | Dec 2001 | B1 |
6442595 | Kelly | Aug 2002 | B1 |
6442686 | McArdle et al. | Aug 2002 | B1 |
6487586 | Ogilvie et al. | Nov 2002 | B2 |
6522727 | Jones | Feb 2003 | B1 |
6609138 | Merriam | Aug 2003 | B1 |
6643684 | Malkin et al. | Nov 2003 | B1 |
6647255 | Nilsson | Nov 2003 | B1 |
6668044 | Schwartz et al. | Dec 2003 | B1 |
6675017 | Zellner et al. | Jan 2004 | B1 |
6678516 | Nordman et al. | Jan 2004 | B2 |
6694436 | Audebert | Feb 2004 | B1 |
6714791 | Friedman | Mar 2004 | B2 |
6721416 | Farrell | Apr 2004 | B1 |
6721785 | Raghunandan | Apr 2004 | B1 |
6760421 | Heilmann et al. | Jul 2004 | B2 |
6765996 | Baxter, Jr. | Jul 2004 | B2 |
6779022 | Horstmann et al. | Aug 2004 | B1 |
6785704 | McCanne | Aug 2004 | B1 |
6826609 | Smith et al. | Nov 2004 | B1 |
6829349 | Neale et al. | Dec 2004 | B1 |
6829635 | Townshend | Dec 2004 | B1 |
6868498 | Katsikas | Mar 2005 | B1 |
6870924 | Ukon | Mar 2005 | B1 |
6901445 | McCanne et al. | May 2005 | B2 |
6920209 | Gainsboro | Jul 2005 | B1 |
6963638 | Keller | Nov 2005 | B1 |
7020779 | Sutherland | Mar 2006 | B1 |
7031437 | Parsons et al. | Apr 2006 | B1 |
7089594 | Lal et al. | Aug 2006 | B2 |
7106850 | Campbell et al. | Sep 2006 | B2 |
7133898 | Malik | Nov 2006 | B1 |
7155243 | Baldwin et al. | Dec 2006 | B2 |
7230951 | Mizell et al. | Jun 2007 | B2 |
7260384 | Bales et al. | Aug 2007 | B2 |
7286834 | Walter | Oct 2007 | B2 |
7299263 | Claudatos et al. | Nov 2007 | B2 |
7330717 | Gidron et al. | Feb 2008 | B2 |
7392297 | Ozaki et al. | Jun 2008 | B2 |
7450937 | Claudatos et al. | Nov 2008 | B1 |
7457404 | Hession et al. | Nov 2008 | B1 |
7472163 | Ben-Yoseph et al. | Dec 2008 | B1 |
7489947 | Castrogiovanni et al. | Feb 2009 | B2 |
7650140 | Plumb et al. | Jan 2010 | B2 |
7680511 | Forte | Mar 2010 | B2 |
7715819 | Rockwell | May 2010 | B2 |
7725098 | Claudatos et al. | May 2010 | B1 |
8086255 | Claudatos et al. | Dec 2011 | B2 |
8126133 | Everingham et al. | Feb 2012 | B1 |
20010043697 | Cox et al. | Nov 2001 | A1 |
20020037075 | Flanagan | Mar 2002 | A1 |
20020054587 | Baker et al. | May 2002 | A1 |
20020090073 | Heilmann et al. | Jul 2002 | A1 |
20020107950 | Lu | Aug 2002 | A1 |
20020138652 | Taylor | Sep 2002 | A1 |
20020147734 | Shoup et al. | Oct 2002 | A1 |
20020165969 | Gallant | Nov 2002 | A1 |
20020198950 | Leeds | Dec 2002 | A1 |
20030008662 | Stern et al. | Jan 2003 | A1 |
20030032409 | Hutcheson et al. | Feb 2003 | A1 |
20030087638 | Taylor | May 2003 | A1 |
20030110212 | Lewis | Jun 2003 | A1 |
20030219103 | Rao et al. | Nov 2003 | A1 |
20030231207 | Huang | Dec 2003 | A1 |
20040066916 | Brown et al. | Apr 2004 | A1 |
20040153499 | Heddaya et al. | Aug 2004 | A1 |
20040170268 | Hakusui | Sep 2004 | A1 |
20040176080 | Chakravorty et al. | Sep 2004 | A1 |
20040198454 | Chavez et al. | Oct 2004 | A1 |
20040208304 | Miller | Oct 2004 | A1 |
20040244102 | Benzon et al. | Dec 2004 | A1 |
20040259534 | Chaudhari et al. | Dec 2004 | A1 |
20050018622 | Halbraich et al. | Jan 2005 | A1 |
20050031107 | Fotta | Feb 2005 | A1 |
20050053084 | Abrol et al. | Mar 2005 | A1 |
20050069096 | Claudatos et al. | Mar 2005 | A1 |
20050141674 | Brown et al. | Jun 2005 | A1 |
20050226221 | Fotta et al. | Oct 2005 | A1 |
20060043164 | Dowling et al. | Mar 2006 | A1 |
20060099965 | Aaron | May 2006 | A1 |
20060135140 | Rothman et al. | Jun 2006 | A1 |
20060148495 | Wilson | Jul 2006 | A1 |
20060168003 | Vau et al. | Jul 2006 | A1 |
20080292070 | Winter et al. | Nov 2008 | A1 |
20080311905 | Noldus et al. | Dec 2008 | A1 |
20100115038 | McEachern et al. | May 2010 | A1 |
20100159883 | Pascal et al. | Jun 2010 | A1 |
Number | Date | Country |
---|---|---|
1303184 | Jul 2001 | CN |
1072420 | Oct 2001 | CN |
1342278 | Mar 2002 | CN |
1083765 | Mar 2001 | EP |
0056015 | Sep 2000 | WO |
WO 0176181 | Oct 2001 | WO |
Entry |
---|
U.S. Appl. No. 60/500,453, filed Sep. 5, 2003, Claudatos. |
U.S. Appl. No. 10/884,453, filed Jul. 1, 2004, Claudatos et al. |
U.S. Appl. No. 10/884,477, filed Jul. 1, 2004, Claudatos et al. |
U.S. Appl. No. 10/884,345, filed Jul. 1, 2004, Claudatos et al. |
U.S. Appl. No. 10/884,473, filed Jul. 1, 2004, Claudatos et al. |
U.S. Appl. No. 10/936,439, filed Sep. 7, 2004, Claudatos et al. |
U.S. Appl. No. 10/936,443, filed Sep. 7, 2004, Claudatos et al. |
U.S. Appl. No. 10/936,442, filed Sep. 7, 2004, Claudatos et al. |
U.S. Appl. No. 11/173,174, filed Jun. 30, 2005, Claudatos et al. |
U.S. Appl. No. 11/173,949, filed Jun. 30, 2005, Claudatos et al. |
“Method for Preclude Unauthorized Sending or Forwarding of Mail Items” IBM Technical Disclosure Bulletin, IBM Corp. New York, US, vol. 37, No. 3, Mar. 1, 1994, p. 199, XP000441437, ISSN: 0018-8689. |
Legato, Email Management Solutions, The EmailXtender Family, 2004, http://www.legato.com/products/emailxtender/. |
Legato, EmailXtender Archive Edition, Email Archiving Software,2004, http://www.legato.com/products/emailxtender/emailarchive.cfm. |
Legato, EmailXaminer, Email Monitoring Software, EmailXaminer the Email Compliance Manager, 2004, http://www.legato.com/products/emailxtender/emailxaminer.cfm. |
EMMA™ E-Mail Monitoring Archive, 2004, http://elstore.com/emmamain.html. |
U.S. Appl. No. 11/174,288, filed Jun. 30, 2005, Schwartz et al. |
Number | Date | Country | |
---|---|---|---|
20070025537 A1 | Feb 2007 | US |