IP Library Granted Patent US 7,042,992
Granted Patent B1
US 7,042,992 · App. 10/360,248 · Granted May 9, 2006

Systems and methods for account establishment and transaction management using interrupt messaging

View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 7,042,992
App. No.
10/360,248
Granted
May 9, 2006
Kind
B1
Abstract

Disclosed are systems and methods which provide techniques providing account setup, management and transaction authorization determinations in real-time using transaction interrupt messaging. Embodiments preferably take into consideration the quality of one or more parties to the transaction and the means by which charges may be rendered to them when making account setup, management, and/or transaction authorization determinations. Accordingly, transactions, such as collect calls, meeting at least some minimal risk threshold may be completed on a first call attempt, even where a pre-arranged billing agreement or other business relationship is not previously in place.

Claims (97)

1. A method, comprising:

receiving a request related to a transaction attempt, the transaction attempt associated with an originating party, an end party, and a requested service;

determining if at least one charge rendering alternative is suitable for charging at least one party for the requested service;

performing at least one transaction interrupt to attempt to implement a suitable charge rendering alternative if no suitable charge rendering alternative has been implemented;

implementing a suitable charge rendering alternative for both the purpose of providing the requested service during the transaction attempt and the purpose of providing future requested services associated with at least one of said originating party and said end party; and

providing the requested service associated with the transaction attempt after the suitable charge rendering alternative is implemented.

2. The method of claim 1 , wherein the transaction attempt is further associated with at least one additional party.

3. The method of claim 1 , wherein at least one of the charge rendering alternatives comprises a prepaid account associated with the originating party, a prepaid account associated with the end party, a prepaid account associated with a third party, a direct billing account associated with the originating party, a direct billing account associated with the end party, a direct billing account associated with a third party, or a billing account associated with a carrier serving the end party.

4. The method of claim 1 , wherein determining if at least one charge rendering alternative is suitable for charging at least one party for the requested service comprises performing at least one transaction authorization.

5. The method of claim 4 , wherein performing the at least one transaction authorization comprises:

performing a primary transaction authorization; and

performing a secondary transaction authorization when the primary transaction authorization fails to authorize the requested service.

6. The method of claim 5 , wherein:

performing the primary transaction authorization comprises determining if the requested service represents a collect call and the end party is served by a carrier having no billing agreement with a service provider receiving the request; and

performing the secondary transaction authorization comprises determining if the end party meets a minimal risk threshold.

7. The method of claim 5 , wherein performing the at least one transaction interrupt comprises delivering a message to the end party when at least one of the primary and secondary transaction authorizations fails to authorize the requested service.

8. The method of claim 5 , wherein performing the at least one transaction interrupt comprises at least one of: delivering a message to the end party and providing the requested service for a limited amount of time, when at least one of the primary and secondary transaction authorizations fails to authorize the requested service.

9. The method of claim 8 , wherein said at least one of delivering a message to the end party and providing the requested service for a limited amount of time comprises demonstrating a need for the requested service.

10. The method of claim 5 , wherein the requested service is provided if authorized by the secondary transaction authorization, the secondary transaction authorization performed using a limited set of data; and

further comprising performing an additional transaction authorization using additional data collected as the requested service is being provided.

11. The method of claim 8 , further comprising:

changing the charge rendering alternative implemented for the requested service based upon said additional data collected.

12. The method of claim 1 , further comprising providing the requested service associated with the transaction attempt without performing any transaction interrupts in response to determining that at least one of the charge rendering alternatives is suitable for charging at least one of the parties for the requested service.

13. The method of claim 1 , wherein:

receiving the request comprises receiving the request at a first service provider network; and

providing the requested service comprises providing the requested service through a second service provider network.

14. The method of claim 1 , wherein said transaction attempt comprises attempting to establish communication between said originating party and said end party.

15. The method of claim 1 , wherein said transaction attempt comprises attempting a commissary transaction.

16. A system, comprising:

a transaction processor receiving a request related to a communication attempt from an originating party, the communication attempt associated with an end party and a requested service; and

a transaction validation engine operable to determine if at least one of a plurality of charge rendering alternatives is suitable for charging at least one party for the requested service, and perform at least one transaction interrupt to implement a suitable one of the charge rendering alternatives if none of the charge rendering alternatives has been implemented;

wherein the transaction processor implements a suitable one of the charge rendering alternatives for the communication attempt and future communication attempts and provides the requested service associated with the communication attempt after the suitable charge rendering alternative is implemented.

17. The system of claim 16 , wherein implementing the suitable one of the charge rendering alternatives and providing the requested service are completed in real-time with respect to receiving the request.

18. The system of claim 16 , wherein at least one of the plurality of charge rendering alternatives comprises a prepaid account associated with the originating party, a prepaid account associated with the end party, a prepaid account associated with a third party, a direct billing account associated with the originating party, a direct billing account associated with the end party, a direct billing account associated with a third party, or a billing account associated with a carrier serving the end party.

19. The system of claim 16 , wherein the transaction validation engine determines if at least one of the plurality of charge rendering alternatives is suitable for charging at least one party for the requested service by performing at least one transaction authorization.

20. The system of claim 19 , wherein the transaction validation engine performs the at least one transaction authorization by:

performing a primary transaction authorization; and

performing a secondary transaction authorization when the primary transaction authorization fails to authorize the requested service.

21. The system of claim 20 , wherein:

the transaction validation engine causes the transaction processor to provide the requested service if authorized by the secondary transaction authorization, the secondary transaction authorization performed using a limited set of data; and

the transaction validation engine performs an additional transaction authorization using additional data collected as the requested service is being provided.

22. The system of claim 21 , wherein the transaction processor implements a different one of the charge rendering alternatives for the communication attempt based upon the additional transaction authorization.

23. The system of claim 16 , wherein said transaction interrupt performed by said transaction validation engine comprises said transaction validation engine causing at least one of

a message to be delivered from the originating party to the end party, and

allowing communication between the originating party and the end party for a limited amount of time.

24. The system of claim 23 , wherein the at least one of message delivered from the originating party and the end party and the communication between the originating party and the end party demonstrates a need for the requested service for facilitating implementing the suitable one of the charge rendering alternatives.

25. A transaction validation engine, comprising:

one or more billing system for implementing a plurality of charge rendering alternatives;

a plurality of filters used in determining if at least one of the plurality of charge rendering alternatives is suitable for charging at least one of a plurality of parties for a requested service; and

at least one interrupt unit establishing at least one account in the one or more billing system if none of the charge rendering alternatives has been implemented with respect to the at least one of the plurality of parties, the at least one account associated with one or more of the plurality of parties.

26. The transaction validation engine of claim 25 , wherein:

the at least one billing system comprises at least one of: a direct billing system, a prepaid accounting system, and a billing system associated with a carrier serving at least one of the parties.

27. The transaction validation engine of claim 25 , wherein:

the at least one interrupt unit comprises an interactive voice response unit.

28. The transaction validation engine of claim 25 , wherein the plurality of filters comprises at least one primary authorization filter and at least one secondary authorization filter.

29. The transaction validation engine of claim 28 , wherein:

the at least one primary authorization filter determines if the requested service represents a collect call and the party receiving the call is served by a carrier having no billing agreement with a service provider receiving a request for the service; and

the at least one secondary authorization filter determines if the party receiving the call meets a minimal risk threshold.

30. The transaction validation engine of claim 28 , further comprising a requested service need demonstrator establishing the requested service for a limited amount of time when at least one of the primary and secondary transaction authorization filters fails to authorize the requested service.

31. The transaction validation engine of claim 28 , further comprising a requested service need demonstrator delivering a message when at least one of the primary and secondary transaction authorization filters fails to authorize the requested service.

32. The transaction validation engine of claim 28 , wherein:

the at least one secondary authorization filter is capable of initially authorizing the requested communication service based on a limited set of data; and

the at least one secondary authorization filter is capable of performing an additional transaction authorization using additional data collected as the requested communication service is being provided.

33. The transaction validation engine of claim 25 , further comprising a requested service need demonstrator.

34. The transaction validation engine of claim 33 , wherein the requested service need demonstrator performs at least one of delivering a message and allowing said requested service for a limited time if none of the charge rendering alternatives has been implemented with respect to the at least one of the plurality of parties.

35. The transaction validation engine of claim 25 , wherein said requested service comprises a communication service.

36. The transaction validation engine of claim 25 , wherein said requested service comprises a commissary service.

37. A method, comprising:

receiving a request related to a communication attempt, the communication attempt associated with an originating party, an end party, and a requested service;

determining if at least one of a plurality of charge rendering alternatives is suitable for charging at least one party for the requested service;

performing at least one transaction interrupt to implement a suitable one of the charge rendering alternatives if a default one of the charge rendering alternatives is not suitable for implementation;

implementing a suitable charge rendering alternative for both the purpose of providing the requested service during the communication attempt and the purpose of providing services in response to future communication attempts; and

providing the requested service associated with the communication attempt after the suitable charge rendering alternative is implemented.

38. The method of claim 37 , wherein the communication attempt is further associated with at least one additional party.

39. The method of claim 37 , wherein:

the default charge rendering alternative comprises collect call billing; and

the suitable charge rendering alternative comprises at least one of: a prepaid account associated with the originating party, a prepaid account associated with the end party, a prepaid account associated with a third party, a direct billing account associated with the originating party, a direct billing account associated with the end party, and a direct billing account associated with a third party.

40. The method of claim 37 , wherein determining if at least one of the plurality of charge rendering alternatives is suitable for charging at least one party for the requested service comprises performing at least one transaction authorization.

41. The method of claim 40 , wherein performing the at least one transaction authorization comprises:

performing a primary transaction authorization; and

performing a secondary transaction authorization when the primary transaction authorization fails to authorize the requested service.

42. The method of claim 41 , wherein:

performing the primary transaction authorization comprises determining if the requested service represents a collect call and the end party is served by a carrier having no billing agreement with a service provider receiving the request; and

performing the secondary transaction authorization comprises determining if the end party meets a minimal risk threshold.

43. The method of claim 41 , wherein performing the at least one transaction interrupt comprises at least one of: delivering a message to the end party and providing the requested service for a limited amount of time.

44. The method of claim 43 , wherein said at least one of delivering a message to the end party and providing the requested service for a limited amount of time comprises demonstrating a need for the requested service.

45. The method of claim 41 , wherein the requested service is provided if authorized by the secondary transaction authorization, the secondary transaction authorization performed using a limited set of data; and

further comprising performing an additional transaction authorization using additional data collected as the requested service is being provided.

46. The method of claim 45 , further comprising:

changing the charge rendering alternative implemented for the requested service based upon said additional data collected.

47. The method of claim 1 , wherein said determining if at least one charge rendering alternative is suitable comprises:

analyzing said at least one party with respect to a quality metric.

48. The method of claim 47 , wherein said quality metric comprises a minimum quality threshold.

49. The system of claim 16 , wherein said transaction validation engine operates to determine if at least one of said plurality of charge rendering alternatives is suitable as a function of a quality metric associated with said at least one party.

50. The system of claim 25 , wherein at least one of said filters references a quality metric associated with said at least one of said plurality of parties.

51. The method of claim 37 , wherein said determining if at least one of said plurality of charge rendering alternatives is suitable comprises:

analyzing said at least one party with respect to a quality metric.

Assignments (35)
ASSIGNMENT OF SECURITY INTEREST IN PATENTS Recorded Apr 21, 2025
From: DEUTSCHE BANK AG NEW YORK BRANCH, AS EXISTING COLLATERAL AGENT
To: WILMINGTON SAVINGS FUND SOCIETY, FSB, AS SUCCESSOR COLLATERAL AGENT
Reel/Frame 070903/0303 →
SECURITY INTEREST Recorded Mar 29, 2024
From: AVENTIV TECHNOLOGIES, LLC; SECURUS TECHNOLOGIES, LLC; SATELLITE TRACKING OF PEOPLE LLC; ALLPAID, INC.
To: WILMINGTON SAVINGS FUND SOCIETY, FSB
Reel/Frame 066951/0054 →
RELEASE OF SECURITY INTEREST Recorded Mar 29, 2024
From: ALTER DOMUS (US) LLC
To: AVENTIV TECHNOLOGIES, LLC; SECURUS TECHNOLOGIES, LLC; ALLPAID, INC.
Reel/Frame 066951/0385 →
RELEASE OF SECURITY INTEREST Recorded Mar 29, 2024
From: ALTER DOMUS (US) LLC
To: AVENTIV TECHNOLOGIES, LLC; SECURUS TECHNOLOGIES, LLC; ALLPAID, INC.
Reel/Frame 066951/0514 →
RELEASE OF SECURITY INTEREST Recorded Mar 29, 2024
From: ALTER DOMUS (US) LLC
To: AVENTIV TECHNOLOGIES, LLC; SECURUS TECHNOLOGIES, LLC; ALLPAID, INC.
Reel/Frame 066951/0561 →
RELEASE OF SECURITY INTEREST Recorded Mar 29, 2024
From: ALTER DOMUS (US) LLC
To: AVENTIV TECHNOLOGIES, LLC; SECURUS TECHNOLOGIES, LLC; ALLPAID, INC.
Reel/Frame 066951/0630 →
RELEASE OF SECURITY INTEREST Recorded Mar 29, 2024
From: ALTER DOMUS (US) LLC
To: AVENTIV TECHNOLOGIES, LLC; SECURUS TECHNOLOGIES, LLC; ALLPAID, INC.
Reel/Frame 066952/0914 →
SUPER-PRIORITY FIRST LIEN PATENT SECURITY AGREEMENT Recorded Mar 28, 2024
From: SECURUS TECHNOLOGIES, LLC; SATELLITE TRACKING OF PEOPLE LLC; ALLPAID, INC.
To: DEUTSCHE BANK AG NEW YORK BRANCH AS COLLATERAL AGENT
Reel/Frame 066945/0310 →
PRIORITY SECOND LIEN PATENT SECURITY AGREEMENT Recorded Feb 1, 2024
From: SECURUS TECHNOLOGIES, LLC; SATELLITE TRACKING OF PEOPLE LLC; ALLPAID, INC.
To: WILMINGTON SAVINGS FUND SOCIETY, FSB AS COLLATERAL AGENT
Reel/Frame 066436/0420 →
PRIORITY FIRST LIEN PATENT SECURITY AGREEMENT Recorded Jan 2, 2024
From: SECURUS TECHNOLOGIES, LLC; ALLPAID, INC.; SATELLITE TRACKING OF PEOPLE LLC
To: DEUTSCHE BANK AG NEW YORK BRANCH, AS COLLATERAL AGENT
Reel/Frame 066567/0620 →
SECURITY INTEREST Recorded Aug 24, 2023
From: ALLPAID, INC.; SATELLITE TRACKING OF PEOPLE LLC; SECURUS TECHNOLOGIES, LLC
To: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A.
Reel/Frame 064699/0842 →
CHANGE OF NAME Recorded Aug 12, 2020
From: SECURUS TECHNOLOGIES, INC.
To: SECURUS TECHNOLOGIES, LLC
Reel/Frame 053476/0289 →
SECOND LIEN SECURITY AGREEMENT Recorded Nov 6, 2017
From: SECURUS TECHNOLOGIES HOLDINGS, INC.; SECURUS TECHNOLOGIES, INC.; SATELLITE TRACKING OF PEOPLE LLC
To: DEUTSCHE BANK AG NEW YORK BRANCH, AS COLLATERAL AGENT
Reel/Frame 044368/0969 →
FIRST LIEN SECURITY AGREEMENT Recorded Nov 3, 2017
From: SECURUS TECHNOLOGIES HOLDINGS, INC.; SECURUS TECHNOLOGIES, INC.; SATELLITE TRACKING OF PEOPLE LLC
To: DEUTSCHE BANK AG NEW YORK BRANCH, AS COLLATERAL AGENT
Reel/Frame 044779/0573 →
FIRST LIEN TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENTS RECORDED AT REEL 030369, FRAME 0648 Recorded Nov 2, 2017
From: DEUTSCHE BANK TRUST COMPANY AMERICAS
To: SECURUS TECHNOLOGIES, INC.; SECURUS TECHNOLOGIES HOLDINGS
Reel/Frame 044681/0227 →
SECOND LIEN TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENTS RECORDED AT REEL 030368, FRAME 0743 Recorded Nov 2, 2017
From: DEUTSCHE BANK TRUST COMPANY AMERICAS
To: SECURUS TECHNOLOGIES, INC.; SECURUS TECHNOLOGIES HOLDINGS
Reel/Frame 044361/0267 →
RELEASE OF 2ND LIEN SECURITY INTEREST Recorded Nov 1, 2017
From: DEUTSCHE BANK TRUST COMPANY AMERICAS
To: SECURUS TECHNOLOGIES, INC.; SECURUS TECHNOLOGIES HOLDINGS, INC.
Reel/Frame 044653/0030 →
RELEASE OF 1ST LIEN SECURITY INTEREST Recorded Nov 1, 2017
From: DEUTSCHE BANK TRUST COMPANY AMERICAS
To: SECURUS TECHNOLOGIES, INC.; SECURUS TECHNOLOGIES HOLDINGS, INC.
Reel/Frame 044640/0547 →
RELEASE OF SECURITY INTEREST FIRST LIEN Recorded May 8, 2013
From: BNP PARIBAS
To: SECURUS TECHNOLOGIES, INC.; T-NETIX, INC
Reel/Frame 030378/0419 →
RELEASE OF SECURITY INTEREST SECOND LIEN Recorded May 8, 2013
From: BNP PARIBAS
To: SECURUS TECHNOLOGIES, INC.; T-NETIX, INC
Reel/Frame 030378/0433 →
SECURITY AGREEMENT Recorded May 7, 2013
From: SECURUS TECHNOLOGIES, INC.; SECURUS TECHNOLOGIES HOLDINGS, INC.
To: DEUTSCHE BANK TRUST COMPANY AMERICAS, AS ADMINISTRATIVE AGENT
Reel/Frame 030369/0648 →
SECURITY AGREEMENT Recorded May 7, 2013
From: SECURUS TECHNOLOGIES, INC.; SECURUS TECHNOLOGIES HOLDINGS, INC.
To: DEUTSCHE BANK TRUST COMPANY AMERICAS, AS ADMINISTRATIVE AGENT
Reel/Frame 030369/0743 →
RELEASE OF SECURITY INTEREST Recorded May 31, 2011
From: JEFFERIES FINANCE LLC
To: SECURUS TECHNOLOGIES, INC. (N/K/A SECURUS TECHNOLOGIES HOLDINGS, INC.); TELEQUIP LABS, INC.; T-NETIX, INC.; EVERCOM SYSTEMS, INC. N/K/A SECURUS TECHNOLOGIES, INC.
Reel/Frame 026362/0632 →
RELEASE OF SECURITY INTEREST Recorded May 31, 2011
From: JEFFERIES FINANCE LL> (AS SUCCESSOR BY ASSIGNMENT TO H.I.G. SECURUS AGENT, LLC)
To: SECURUS TECHNOLOGIES, INC. (N/K/A SECURUS TECHNOLOGIES HOLDINGS, INC.); TELEQUIP LABS, INC.; T-NETIX, INC.; EVERCOM SYSTEMS, INC. N/K/A SECURUS TECHNOLOGIES, INC.
Reel/Frame 026362/0644 →
SECURITY AGREEMENT Recorded May 31, 2011
From: SECURUS TECHNOLOGIES, INC.; T-NETIX, INC.
To: BNP PARIBAS
Reel/Frame 026363/0253 →
SECURITY AGREEMENT Recorded May 31, 2011
From: SECURUS TECHNOLOGIES, INC.; T-NETIX, INC.
To: BNP
Reel/Frame 026363/0393 →
SUPPLEMENTAL NAME CHANGE SUBMISSION WITH UPDATED LIST OF PATENTS TO CONFIRM OWNERSHIP BY SECURUS TECHNOLOGIES, INC. Recorded May 18, 2011
From: EVERCOM SYSTEMS, INC.
To: SECURUS TECHNOLOGIES, INC.
Reel/Frame 026304/0596 →
CHANGE OF NAME Recorded Aug 9, 2010
From: EVERCOM SYSTEMS, INC.
To: SECURUS TECHNOLOGIES, INC.
Reel/Frame 024804/0421 →
CHANGE OF NAME Recorded Aug 9, 2010
From: SECURUS TECHNOLOGIES, INC.
To: SECURUS TECHNOLOGIES HOLDINGS, INC.
Reel/Frame 024804/0633 →
SECURITY AGREEMENT Recorded May 7, 2010
From: SECURUS TECHNOLOGIES, INC.; EVERCOM SYSTEMS, INC.; T-NETIX, INC.; TELEQUIP LABS, INC.
To: H.I.G. SECURUS AGENT, LLC
Reel/Frame 024351/0427 →
ASSIGNMENT AND RELEASE OF SECURITY INTEREST Recorded May 4, 2010
From: WELLS FARGO FOOTHILL, LLC
To: T-NETIX, INC.; EVERCOM SYSTEMS, INC.; SECURUS TECHNOLOGIES, INC.
Reel/Frame 024329/0310 →
ASSIGNMENT AND RELEASE OF SECURITY INTEREST Recorded May 4, 2010
From: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A.
To: T-NETIX, INC.; SECURUS TECHNOLOGIES, INC.; TELEQUIP LABS, INC.; T-NETIX TELECOMMUNICATIONS SERVICES, INC.; EVERCOM HOLDINGS, INC.; EVERCOM, INC.; EVERCOM SYSTEMS, INC.; SYSCON JUSTICE SYSTEMS, INC.; MODELING SOLUTIONS LLC; MODELING SOLUTIONS, LLC
Reel/Frame 024329/0282 →
SECURITY AGREEMENT Recorded May 4, 2010
From: TELEQUIP LABS, INC.; EVERCOM SYSTEMS, INC.; T-NETIX, INC.
To: JEFFERIES FINANCE LLC
Reel/Frame 024329/0295 →
SECURITY AGREEMENT Recorded Oct 9, 2008
From: EVERCOM SYSTEMS, INC.
To: WELLS FARGO FOOTHILL, LLC
Reel/Frame 021651/0094 →
RELEASE OF SECURITY INTEREST Recorded Oct 3, 2008
From: ING CAPITAL LLC
To: EVERCOM SYSTEMS, INC.
Reel/Frame 021617/0789 →