US 8,565,399 B2Grant
System and method for modifying communication information (MCI)
Issue Date:2013-10-22
•27 Claims
•6 Drawing Sheets
Abstract
A system for handling an outbound call from a call originator to a call target including a database storing a plurality of outgoing telephone numbers, each outgoing telephone number having one of two or more area codes; and an information processor controlled by the call originator. The information processor configured to process a trigger comprising at least an area code of a telephone number of the call target; select from the database a telephone number from the plurality of outgoing telephone numbers where the selected telephone number has at least an area code the same as the area code of the telephone number of the call target; set caller identification data of the outbound call to the selected telephone number; and transmit the caller identification data to the call target in connection with the outbound call.
Metadata
Assignee
- NobelBiz, Inc.
Inventor
- James Siminoff
Application Information
Application Number:US 13/676,546
Filing Date:2012-11-14
Priority Date:2005-10-20
Art Unit:2652
Classifications
IPC:
H04M3/42
Patent Drawings (6 sheets)
Description
Cross-Reference to Related Applications
[0001] This application claims priority to and is a continuation of pending U.S. application Ser. No. 13/013,233, filed Jan. 25, 2011, which claims priority to and is a continuation of U.S. application Ser. No. 11/584,176, filed Oct. 20, 2006, now U.S. Patent No. 7,899,169, which claims priority to U.S. provisional patent application Ser. No. 60/728,717, filed Oct. 20, 2005, entitled System and Method for Modifying Communication Information (MCI), the disclosures of which are incorporated herein by reference.
Background of the Invention
[0002] In certain forms of communication, the party being contacted (the “Target”) may have the opportunity to know information about the party attempting to originate a communication (the “Originator”) before the Target interacts with the Originator. Two notable forms of communication where this is true are telephone and e-mail. In each of those forms of communication, the Target may learn some information about the Originator, such as the Originator's telephone number or email address, before the Target agrees to accept data or create a two-way communication, i.e. a conversation. The information the Target receives may also be used to allow the Target to identify or contact the Originator.
[0003] When an Originator, such as a telemarketing firm, wishes to contact a Target, such as an individual, via telephone, the Originator may insert into the caller ID field a telephone number where the Originator may be contacted. When making a call, the Originator inserts a telephone number used at the location from which the call originated, e.g. a call center. However, the Originator may call a Target in an area distant from the Originator. As a result, if the Target wishes to call back the Originator at the telephone number listed, e.g. to be put on a Do Not Call List (DNC) or to receive other information, the Target may have to pay long distance charges to do so. However, the Originator may operate telephone numbers that are a local call from the Target, or are at least closer to the Target, and therefore less expensive to call, than the Originator's telephone number that appears on the Target's caller ID.
[0004] Therefore, it would be desirable to implement a system to modify a communication from an Originator to provide a callback number or other contact information to the Target that may be closer to or local to the Target, in order to reduce or eliminate the payment of long distance toll charges in the event the Target dials the callback number.
Summary of the Invention
[0005] The present disclosure relates to a method for processing a communication between a first party and a second party. A communication is received from the first party, the communication having first party information, and second party information. An entry in a database is identified that matches at least one of the first party information and the second party information and for which a predetermined rule is satisfied. A telephone number associated with the matching database entry is selected. The selected telephone number is transmitted to the second party.
Brief Description of the Drawings
[0006] FIG. 1 is a view of an end-to-end telecommunication connection according to an aspect of the system and method of the present disclosure.
[0007] FIG. 2 is a view of an end-to-end telecommunication connection found in related art.
[0008] FIG. 3 is a process flow of communication traveling from Originator to Target according to an aspect of the system and method of the present disclosure.
[0009] FIG. 4 is a process flow of communication traveling from Target to Originator according to an aspect of the system and method of the present disclosure.
[0010] FIG. 5 is a example of a routing table according to an aspect of the system and method of the present disclosure.
Detailed Description of the Drawings
[0011] FIG. 2 is a view of an end-to-end contact as would occur during standard communication between Originator 100 (e.g. call center, person or organization) and Target 140 (e.g. a person or organization) using Carrier Network 130 (e.g. telecommunication provider). Information, such as Target 140 telephone number, may be transmitted from Originator 100 to Carrier Network 130 via physical/virtual connection 110 (e.g. phone line, voice T1 , voice DS3) for an outbound call. Carrier Network 130 routes the call to Target 140 using, for example, a circuit switch, softswitch, or other routing intelligent system (not shown).
[0012] FIG. 1 illustrates aspects of the system of the present disclosure and includes Originator 100 which may transmit a call (including, e.g. sound and other data) through physical/virtual connection 110 to Target 140 through Carrier Network 130. Originator 100 may transmit data including signaling messages of telecommunication protocols (e.g., SS7, C7, ISDN, SIP, H.323, MGCP, MEGACO, IAX, IAX2) that may be used to identify or contact Originator 100. This may include caller ID information such as telephone number and subscriber name associated with Originator 100 telephone number.
[0013] Originator 100 may transmit Target Identifying Information, including Target 140 telephone number and other information via physical/virtual connection 110 to Carrier Network 130 for outbound calls. Target Identifying Information may include geographic location information about Target 140, which may be determined based on Caller ID of Target 140 in conjunction with telephone subscriber database information.
[0014] Carrier Network 130 may route the call to Distribution System 131 which may check each call for a trigger, such as information in the call or where the call originated from, such as which physical/virtual connection 110. Distribution System 131 may be a circuit switch, softswitch, or other routing intelligent system. Distribution System 131 may communicate with a table of data, such as, MCI Table 132, based on the trigger for the call. MCI Table 132 may be stored in a computer, server, database, flash memory or other computing storage device. Target 140 may receive information from the MCI Table 132 in the Caller ID field on received call via physical/virtual connection 120.
[0015] In one aspect, the system and method of the present disclosure may operate within or may be connected to Carrier Network 130. In other aspects, the system and method may operate in Originator's 100 PBX (e.g. corporate phone system, predictive dialer, call distribution system) or may be attached to or embedded within Originator's 100 communication device (e.g. telephone, VoIP phone, VoIP soft phone).
[0016] FIG. 3 shows the process flow where in Step S100 a communication is received by Carrier Network 130 from Originator 100. In one aspect, the system of the present invention may receive from Originator 100 Target Identifying Information and a trigger. As described above, Target Identifying Information may include the telephone number of Target 140. A trigger may be one or more predetermined numbers in the Caller ID field, one or more predetermined numbers appended to the telephone number of Target 140 when transmitted by Originator 100, or may be another predetermined communication between Originator 100 and the system.
[0017] In Step S200, the system checks the communication for the existence of trigger information and Target Identifying Information, and, based on this information, the system may modify the communication. Rules and data used to modify the communication may be stored in a table database, such as MCI Table 132 shown in FIG. 5 .
[0018] As shown in FIG. 5 , MCI Table 132 column A is a list of triggers, column B is a list of Target Identifying Information, and column C is a list of modified information that may be displayed to Target 140.
[0019] When the system of the present disclosure receives a call from Originator 100, the system may check for one of the triggers located in column A to determine whether this communication may be modified. In one aspect, the system may be initiated manually, e.g. using a website, and may be used to process communications originating from a specific physical or virtual area, e.g. one or more telephone lines, so that any communication originating from one of these areas will be processed by the system. If the system does not receive a trigger or is not initiated manually, then the system may pass the communication on to Target 140 without modifying data.
[0020] If the system has been manually initiated or finds the communication contains a trigger listed in column A, the system may then search column B for one or more entries associated with the trigger in column A based on the Target Identifying Information included in the communication. Column B entries may be telephone numbers, portions of telephone numbers, street addresses or geographic designations, such as country, state, city, or township. Column B entries may also include rules indicating how or when they may be applied, for example, days of the week and/or times of day.
[0021] In one aspect, the system may search a telephone number in column B that matches Target 140 telephone number. In another aspect, if multiple column B entries for a given trigger match the area code of the Target 140 telephone number, the system may select the column B entry based on prefix. If there are no acceptable column B entries for a trigger, the system may pass the communication without alterations thereto.
[0022] In other aspects, column B entries may be selected based on predetermined Originator 100 preference, by geographic proximity to Target 140.
[0023] Based on the results of the search in column B, information in the communication may be modified to appear as what is shown in the corresponding entry in column C, i.e. the telephone number in column C may be displayed in the Caller ID field in the call to Target 140.
[0024] Using information in MCI Table 132 in FIG. 5 , suppose for example, the system encounters a telephone call coming from Originator 100 telephone number 954-444-0001 that is made to Target 140 having telephone number 212-333-1234 on a weekday. The system may note the incoming caller ID field 954-444-0001 and attempt to match this to a trigger entry in column A. In this case, the number 954-444-0001 has five matches in column A, corresponding to table index entries A1 through A5. Once one or more acceptable entries are found in column A, the system may then compare Target ID information, in this case 212-333-1234, with one or more entries in column B corresponding to the one or more acceptable entries in column A.
[0025] In one aspect, the “x” character may be used as a wildcard to signify any character or number. Although not shown, such a wildcard character may also be used in elsewhere in the table.
[0026] In one aspect, the system may compare the Target ID information with the entries in column B by area code, prefix, and other rules, such as time of day. It will be clear to one of ordinary skill that the type, order and priority of such data comparison may be configurable.
[0027] Continuing the example, of the presently eligible entries 1-5 in column B, only entries 2, 3, and 4 match the area code “212” of the Target ID information, and of those, entries 3 and 4 match both the area code “212” and prefix “333” of the Target ID information. Column B entries 3 and 4 each contain a rule relating to the day of the week the call is made. In this example, because the call is placed on a weekday, column B entry 3 is the closest match to the Target ID information, and all rules of that entry are satisfied.
[0028] Based on this match in column B, the system may modify the communication to send an outbound Caller ID to Target 140 having the contents of entry 3 in column C, here 212-333-0001. Therefore, Target 140 may then make a return call to a local telephone number 212-333-0001 at a local area code (212), rather than potentially incurring long distance charges by making a return call to Originator 100 at a non-local number 954-444-0001 at a non-local area code (954).
[0029] In Step S300 the system then establishes the communication with Target 140 containing modified information.
[0030] Originator 100 may receive calls made to the telephone numbers listed in column C. Originator 100 may operate the telephone numbers listed in column C and/or calls to the telephone numbers in column C may be directed to telephone numbers used by Originator 100, in a manner described below with reference to FIG. 4 .
[0031] FIG. 4 shows the process flow, according to an aspect of the invention, when a communication is initiated by Target 140 to Originator 100. The system may receive the communication from Target 140 in Step S100. In Step S200, based on a set of rules, Target Identifying Information and the telephone number Target 140 is calling, the system may modify and/or route the communication to Originator 100. Originator 100 may receive the communication at an inbound customer service center or voice recording, at a predetermined telephone number. When routing and/or modifying Target 140 call, the system may use a table.
[0032] In Step S300, the system sends the communication to the appropriate party. When the system routes a call from Target 140 to Originator 100, the system may pass any one of the following information to Originator 100: the telephone number of Target 140, the “trigger” number in column A associated with that telephone number, or other identifier correlated to the Target 140, such as geographic location of the Target 140. In addition, the system can forward the call from Target 140 to a telephone number, trunk line, IP address as a VoIP call, or any other form of return communication as predetermined rules dictate.
[0033] Although illustrative embodiments have been described herein in detail, it should be noted and will be appreciated by those skilled in the art that numerous variations may be made within the scope of this invention without departing from the principle of this invention and without sacrificing its chief advantages.
[0034] Unless otherwise specifically stated, the terms and expressions have been used herein as terms of description and not terms of limitation. There is no intention to use the terms or expressions to exclude any equivalents of features shown and described or portions thereof and this invention should be defined in accordance with the claims that follow.
Claims
What is claimed is:
1. A system for handling an outbound call from a call originator to a call target, the system comprising:
a database storing a plurality of outgoing telephone numbers, each outgoing telephone number having one of two or more area codes; and
an information processor controlled by the call originator and configured to:
a) process a trigger comprising at least an area code of a telephone number of the call target;
b) select from the database a telephone number from the plurality of outgoing telephone numbers where the selected telephone number has at least an area code the same as the area code of the telephone number of the call target;
c) set caller identification data of the outbound call to the selected telephone number; and
d) transmit the caller identification data to the call target in connection with the outbound call.
2. The system of claim 1, wherein the system is embedded in one of a carrier network, a private branch exchange, and a communications device.
3. The system of claim 2, wherein the communications device is one of a telephone, a VoIP phone, and a VoIP soft phone.
4. The system of claim 1, wherein the system is embedded in one of a corporate phone system, a predictive dialer, and a call distribution system.
5. The system of claim 1, wherein the selected telephone number has an area code and a prefix the same as an area code and a prefix of the telephone number of the call target.
6. The system of claim 1, wherein the selected telephone number has an area code different from an area code of a telephone number of the call originator.
7. A computer for handling an outbound call from a call originator to a call target, the computer comprising:
memory having at least one region for storing computer executable program code; and
processor for executing the computer executable program code stored in the memory, where the computer executable program code comprises:
code for processing at least a portion of a telephone number of the call target;
code for accessing a database storing a plurality of outgoing telephone numbers, each outgoing telephone number having one of two or more area codes;
code for selecting from the database a telephone number from the plurality of outgoing telephone numbers based on at least a portion of the telephone number of the call target, the selected telephone number having an area code from a geographic region the same as a geographic region of an area code of the telephone number of the call target;
code for setting caller identification data of the call to the selected telephone number; and
code for transmitting the caller identification data to the call target in connection with the outbound call.
8. The computer of claim 7, wherein the selected telephone number has at least an area code the same as an area code of the telephone number of the call target.
9. The computer of claim 7, wherein the geographic region is one of a state and other municipality smaller than a state.
10. The computer of claim 7, wherein the area code of the selected telephone number is associated with a state different from a state associated with the area code of the telephone number of the call target.
11. The computer of claim 7, wherein the selected telephone number has an area code and a prefix the same as an area code and prefix of the telephone number of the call target.
12. The computer of claim 7, wherein the area code and prefix of the selected telephone number corresponds to a geographic region the same as the area code and prefix of the telephone number of the call target.
13. The computer of claim 12, wherein the geographic region is one of a state and other municipality smaller than a state.
14. The computer of claim 7, wherein the computer is embedded in one of a carrier network, a private branch exchange, and a communications device.
15. The computer of claim 14, wherein the communications device is one of a telephone, a VoIP phone, and a VoIP soft phone.
16. The computer of claim 7, wherein the computer is embedded in one of a corporate phone system, a predictive dialer, and a call distribution system.
17. The computer of claim 7, wherein the area code of the selected telephone number is of a geographic region different than a geographic region of the call originator.
18. A computer implemented method for handling an outbound call from a call originator to a call target comprising:
processing a trigger in the form of at least a portion of a telephone number of the call target;
accessing a database storing a plurality of outgoing telephone numbers, each outgoing telephone number having one of two or more area codes;
selecting from the database a telephone number from the plurality of outgoing telephone numbers based on at least a portion of the telephone number of the call target, the selected telephone number having an area code from a geographic region the same as a geographic region of an area code of the telephone number of the call target;
setting caller identification data of the call to the selected telephone number; and
transmitting the caller identification data to the call target in connection with the outbound call.
19. The computer implemented method of claim 18, wherein the selected telephone number has at least an area code the same as an area code of the telephone number of the call target.
20. The computer implemented method of claim 18, wherein the geographic region is one of a state and other municipality smaller than a state.
21. The computer implemented method of claim 18, wherein the selected telephone number has an area code and a prefix the same as an area code and prefix of the telephone number of the call target.
22. The computer implemented method of claim 18, wherein the area code and prefix of the selected telephone number corresponds to a geographic region the same as the area code and prefix of the telephone number of the call target.
23. The computer implemented method of claim 22, wherein the geographic region is one of a state and other municipality smaller than a state.
24. The computer implemented method of claim 18, wherein the method is performed in one of a carrier network, a private branch exchange, and a communications device.
25. The computer implemented method of claim 24, wherein the communications device is one of a telephone, a VoIP phone, and a VoIP soft phone.
26. The computer implemented method of claim 18, wherein the method is performed in one of a corporate phone system, a predictive dialer, and a call distribution system.
27. The computer implemented method of claim 18, wherein the area code of the selected telephone number is of a geographic region different than a geographic region of the call originator.
Patent Citations (29)
| Patent | Date | Inventor | Cited By |
|---|---|---|---|
| US6137870(A) | 2000-10-01 | Scherer | Applicant |
| US6324272(B1) | 2001-11-01 | Abu-Shukhaidem et al. | Applicant |
| US6330327(B1) | 2001-12-01 | Lee et al. | Applicant |
| US6546238(B1) | 2003-04-01 | Nightingale et al. | Applicant |
| US6556818(B1) | 2003-04-01 | Meehan | Applicant |
| US6608892(B2) | 2003-08-01 | Shaffer et al. | Applicant |
| US6700972(B1) | 2004-03-01 | McHugh et al. | Applicant |
| US6714535(B1) | 2004-03-01 | Herh | Applicant |
| US6813344(B1) | 2004-11-01 | Lemke | Applicant |
| US6901266(B2) | 2005-05-01 | Henderson | Applicant |
| US7027575(B1) | 2006-04-01 | Burgess | Applicant |
| US7340262(B1) | 2008-03-01 | Gillespie et al. | Applicant |
| US7346156(B1) | 2008-03-01 | Choupak et al. | Applicant |
| US7376228(B2) | 2008-05-01 | Haug, Jr. et al. | Applicant |
| US7602894(B1) | 2009-10-01 | Shaffer et al. | Applicant |
| US7640009(B2) | 2009-12-01 | Belkin et al. | Applicant |
| US7756253(B2) | 2010-07-01 | Breen et al. | Applicant |
| US7925003(B2) | 2011-04-01 | Haug, Jr. et al. | Applicant |
| US8027332(B1) | 2011-09-01 | Martin et al. | Applicant |
| US8040875(B2) | 2011-10-01 | Barclay et al. | Applicant |
| US2002/0061100(A1) | 2002-05-01 | DiCamillo et al. | Applicant |
| US2002/0181681(A1) | 2002-12-01 | Mani | Applicant |
| US2003/0007616(A1) | 2003-01-01 | Alves et al. | Applicant |
| US2004/0120477(A1) | 2004-06-01 | Nguyen et al. | Applicant |
| US2005/0053213(A1) | 2005-03-01 | Giannoit | Applicant |
| US2005/0105705(A1) | 2005-05-01 | Elcock et al. | Applicant |
| US2006/0140200(A1) | 2006-06-01 | Black et al. | Applicant |
| EP944229(A1) | 1999-09-01 | Applicant | |
| JP2004112253 | 2004-04-01 | Applicant |
Non-Patent Literature (33)
- Treese, G. Windfield and Stewart, Lawrence C., An Architecture for Security and Privacy in Mobile Communications, 29th TPRC Conference, 2001, arXiv:cs/0110042v! [cs.CY] Oct. 19, 2001, Cornell University Library, submitted Oct. 19, 2001.Applicant
- Chang, Cheng-Shin et al, Efficient End-to-End Authentication Protocols for Mobile Networks, Personal, Indoor and Mobile Radio Communications, 1996 Seventh IEEE International Symposium. Date of Conference: Oct. 15-18, 1996. vol. 3, pp. 1252-1256.Applicant
- Clarke, Ronald V. and Newman, Graeme R., Modifying Criminogenic Products: What Role for Government?, Crime Prevention Studies, vol. 18, pp. 7-83 (Jul. 2005).Applicant
- Lau, Tessa, Etzioni, Oren and Weld, Daniel S., Privacy Interfaces for Information Management, Communications of the ACM, vol. 42, issue 10, pp. 88-94, Oct. 1999.Applicant
- www.Star38.com/s38.php, (Aug. 31, 2004) via Wayback Machine (archive.org).Applicant
- In the Matter of Rules and Regulations Implementing the Telephone Consumer Protection Act of 1991, CG Docket No. 02-278, Section XII. Caller Identification, Federal Communications Commission (Jul. 3, 2003) available at: http://hraunfoss.fcc.gov/edocs—public/attachmatch/FCC-03-153A1.pdf.Applicant
- TCN Broadcasting User's Manual, Jan. 22, 2004, version 1.001.Applicant
- Lippincott, Melanie G., Global Connect “User's Guide”, Sep. 2004.Applicant
- Maney, Kevin, USA Today Article, Money, “Who's Calling? It might not be who you think it is”, website: http://www/usatoday.com/money/industries/telecom/2004-09-01-spoof—x.htm, Sep. 2004.Applicant
- Torrone, Phillip, Cellphones, Article, Questions about the Caller I.D. falsification (Caller ID Spoofing) service answered, Aug. 2004, website: www.engaadget.com/2004/08/31/questions-about-the-caller-i-d-falsification-caller-id/.Applicant
- Belson, Ken, The New York Times, Article, “A Commercial Software Service Aims to Outfox Caller ID”, Sep. 2, 2004.Applicant
- Ring Central (Your Phone System Everywhere), Press Release, RingCentral Launches RingOut Clink-to-call feature Helps Entrepreneurs to Generate Sales and Leads, Article, Aug. 19, 2005, website: www.ringcentral.com/whyringcentral/company/press releases/click-to-call.html.Applicant
- Ring Central (Your Phone System everywhere), Press Release, “RingCentral Announces Virtual Local Telephone Numbers in Major U.S. Cities”, Article, Jan. 22, 2004, website: www.ringcentral.com/whyringcentral/company/pressreleases/localnumbers.html.Applicant
- Civil docket for NobelBiz, Inc. v. Five 9, Inc., 6:12-cv-00243-MHS (E.D. Tex. 2012).Applicant
- Civil docket for NobelBiz, Inc. v. Five 9, Inc., 4:13-cv-01846-YGR (N. D. Cal. 2013).Applicant
- Civil docket for NobelBiz, Inc. v. LiveVox Inc., 6:12-cv-00246-MHS (E.D. Tex. 2012).Applicant
- Civil docket for NobelBiz, Inc. v. LiveVox Inc., 4:13-cv-01773-YGR (N. D. Cal. 2013).Applicant
- Civil docket for NobelBiz, Inc. v. AireSpring, Inc., 6:12-cv-00242-LED (E.D. Tex. 2012).Applicant
- Civil docket for NobelBiz, Inc. v. Global Connect, L.L.C., 6:12-cv-00244-MHS (E.D. Tex. 2012).Applicant
- Civil docket for NobelBiz, Inc. v. T C N, Inc., 6:12-cv-00247-MHS (E.D. Tex. 2012).Applicant
- Civil docket for NobelBiz, Inc. v. inContact, Inc., 6:12-cv-00272-LED (E.D Tex. 2012).Applicant
- Civil docket for NobelBiz, Inc. v. Stage 2 Networks, L.L.C., 6:12-cv-00308-LED (E.D. Tex 2012).Applicant
- Civil docket for NobelBiz, Inc. v. Omega Services, LLC, 6:12-cv-00432-LED (E.D. Tex. 2012).Applicant
- Civil docket for NobelBiz, Inc. v. Connect First, Inc., 6:12-cv-00549-LED (E.D. Tex 2012).Applicant
- Civil docket for NobelBiz, Inc. v. Intelligent Contacts, Inc., 6:12-cv-00831-MHS (E.D. Tex. 2012).Applicant
- Civil docket for NobelBiz, Inc. v. InsideSales.com, 6:13-cv-00360-MHS (E.D. Tex. 2013).Applicant
- Civil docket for NobelBiz, Inc. v. SafeSoft Solutions Inc., 4:13-cv-02423-YGR (N.D. Cal. 2013).Applicant
- Civil docket for NobelBiz, Inc. v. Veracity Networks, LLC, 4:13-cv-02518-YGR (N.D. Cal. 2013).Applicant
- TCN Inc.'s response to First Set of Interrogatories—Partially Redacted, Jun. 14, 2013, NobelBiz, Inc. v. TCN, Inc., 6:12-cv-247-JHS (E.D. Tex. 2012).Applicant
- LiveVox, Inc.'s Disclosure of Invalidity Contentions, May 13, 2013, NobelBiz, Inc. v. LiveVox, Inc., 4:13-CV-01773-YGR (N.D. Cal. 2013).Applicant
- Five 9, Inc.'s Disclosure of Invalidity Contentions, May 13, 2013, NobelBiz, Inc. v. Five 9, Inc., 4:13-cv-01846-YGR (N.D. Cal. 2013).Applicant
- TCN, Inc.'s Invalidity Contentions, Apr. 26, 2013, NobelBiz, Inc. v. Global Connect, L.L.C., 6:12-cv-00244-MHS (E.D. Tex. 2012), NobelBiz, Inc. v. TCN, Inc., 6:12-cv-00247-MHS (E.D. Tex. 2012).Applicant
- Global Connect, L.L.C.'s Disclosures of Invalidity Contentions and Accompanying Document Production, Apr. 26, 2013, 6:12-cv-00244-MHS (E.D. Tex. 2012).Applicant