IP Library Granted Patent US 8,359,400
Granted Patent B2
US 8,359,400 · App. 12/041,484 · Granted Jan 22, 2013

System and method for user-definable document exchange

Inventors: Shawn Zargham (Rockville, MD); Mark Hatam (Bethesda, MD)
Assignee: Telarix, Inc.
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 8,359,400
App. No.
12/041,484
Granted
Jan 22, 2013
Kind
B2
Abstract

A document exchange based on user-definable validation rules provided by the exchanging parties. In one embodiment, an uploader uploads a document from a first computer, the upload being associated with a first member account registered with a network site. A user interface receives a delivery destination for the document from the first computer, the delivery destination being associated with a second member account registered with the network site. A content validator validates content of the document based on rules registered at the network site in connection with the second member account. An output adaptor determines a document delivery format registered at the network site in connection with the second member account. A delivery component delivers the document in the determined format to a second computer associated with the second member account.

Claims (83)

1. A method, comprising:

establishing, by a transaction processing system, a link between a first party and a second party, the link being associated with one or more format rules, registered with the transaction processing system by the first party, specifying a document format and one or more business rules, registered with the transaction processing system by the second party, specifying how to process document content;

receiving, by the transaction processing system, a document from the first party in association with the link;

extracting, by the transaction processing system, multiple portions of content of the document;

determining, by the transaction processing system, whether each of the extracted multiple portions of content satisfies the one or more business rules registered with the transaction processing system by the second party in association with the link;

accepting, by the transaction processing system, one or more of the extracted multiple portions determined to satisfy the one or more business rules;

rejecting, by the transaction processing system, one or more of the extracted multiple portions determined not to satisfy the one or more business rules; and

delivering, by the transaction processing system, the accepted portions and not the rejected portions of the extracted content to the second party via the link.

2. The method of claim 1 , further comprising:

validating, by the transaction processing system, the content of the document based on business rules, registered with the transaction processing system by the first party in association with the link, specifying how to process document content.

3. The method of claim 1 , further comprising:

validating, by the transaction processing system, formatting associated with the document based on the one or more format rules registered with the transaction processing system by the first party.

4. The method of claim 3 , further comprising:

providing, by the transaction processing system, an error notification to the first party via the link if the formatting associated with the document violates the one or more format rules registered with the transaction processing system by the first party.

5. The method of claim 1 , further comprising:

providing, by the transaction processing system, an error notification to the first party regarding the rejected portions of the extracted content via the link.

6. The method of claim 1 , further comprising:

providing, by the transaction processing system, a delivery status of the document to the first party via the link.

7. The method of claim 6 , wherein the delivery status of the document comprises a partial rejection of the content of the document.

8. The transaction processing system of claim 7 , wherein the document format registered with the transaction processing system by the second party is Microsoft Excel.

9. The transaction processing system of claim 7 , wherein the document format registered with the transaction processing system by the second party is CSV.

10. The transaction processing system of claim 7 , wherein the document format registered with the transaction processing system by the second party is XML.

11. The method of claim 6 , wherein the delivery status of the document comprises a full rejection of the content of the document.

12. The method of claim 1 , wherein the first party and second party are communication service providers.

13. The method of claim 12 , wherein the document is a telecommunication wholesale business document.

14. The method of claim 13 , wherein the content of the document involves a price list.

15. The method of claim 13 , wherein the content of the document involves an invoice.

16. The method of claim 13 , wherein the content of the document involves a dispute.

17. The method of claim 1 , wherein the delivery of the accepted portions of the extracted content to the second party is made via e-mail.

18. The method of claim 1 , wherein the delivery of the accepted portions of the extracted content to the second party is made via File Transfer Protocol.

19. The method of claim 1 , wherein the delivery of the accepted portions of the extracted content to the second party is made via Web Services.

20. The method of claim 1 , wherein the receiving of the document by the transaction processing system is via e-mail.

21. The method of claim 1 , wherein the receiving of the document by the transaction processing system is via File Transfer Protocol.

22. The method of claim 1 , wherein the receiving of the document by the transaction processing system is via Web Services.

23. The method of claim 1 , wherein the receiving of the document by the transaction processing system is via portal upload.

24. The method of claim 1 , wherein the document received by the transaction processing system is in a Microsoft Excel format.

25. The method of claim 1 , wherein the document received by the transaction processing system is in a CSV format.

26. The method of claim 1 , wherein the document received by the transaction processing system is in an XML format.

27. The method of claim 1 , wherein the link is further associated with one or more format rules, registered with the transaction processing system by the second party, specifying a document format.

28. The method of claim 27 , wherein the document format registered with the transaction processing system by the second party is Microsoft Excel.

29. The method of claim 27 , wherein the document format registered with the transaction processing system by the second party is CSV.

30. The method of claim 27 , wherein the document format registered with the transaction processing system by the second party is XML.

31. The method of claim 27 , further comprising:

converting the accepted portions of the extracted content to the document format specified by the one or more format rules registered with the transaction processing system by the second party, and

delivering the converted accepted portions of the extracted content to the second party via the link.

32. A transaction processing system, comprising:

circuitry configured to establish a link between a first party and a second party, the link being associated with one or more format rules, registered with the transaction processing system by the first party, specifying a document format and one or more business rules, registered with the transaction processing system by the second party, specifying how to process document content;

circuitry configured to receive a document from the first party in association with the link;

circuitry configured to extract multiple portions of content of the document;

circuitry configured to determine whether each of the extracted multiple portions of content satisfies the one or more business rules registered with the transaction processing system by the second party in association with the link;

circuitry configured to accepting, by the transaction processing system, one or more of the extracted multiple portions determined to satisfy the one or more business rules;

circuitry configured to rejecting, by the transaction processing system, one or more of the extracted multiple portions determined not to satisfy the one or more business rules; and

circuitry configured to deliver the accepted portions and not the rejected portions of the extracted content to the second party via the link.

33. The transaction processing system of claim 32 , wherein the circuitry is configured to validate the content of the document based on business rules, registered with the transaction processing system by the first party in association with the link, specifying how to process document content.

34. The transaction processing system of claim 32 ,

wherein the circuitry is configured to validate formatting associated with the document based on the one or more format rules registered with the transaction processing system by the first party.

35. The transaction processing system of claim 34 ,

wherein the circuitry is configured to provide an error notification to the first party via the link if the formatting associated with the document violates the rules registered with the transaction processing system by the first party.

36. The transaction processing system of claim 32 ,

wherein the circuitry is configured to provide an error notification to the first party regarding the rejected portions of the extracted content via the link.

37. The transaction processing system of claim 32 ,

wherein the circuitry is configured to provide a delivery status of the document to the first party via the link.

38. The transaction processing system of claim 37 , wherein the delivery status of the document comprises a partial rejection of the content of the document.

39. The transaction processing system of claim 37 , wherein the delivery status of the document comprises a full rejection of the content of the document.

40. The transaction processing system of claim 32 , wherein the first party and second party are communication service providers.

41. The transaction processing system of claim 40 , wherein the document is a telecommunication wholesale business document.

42. The transaction processing system of claim 41 , wherein the content of the document involves a price list.

43. The transaction processing system of claim 41 , wherein the content of the document involves an invoice.

44. The transaction processing system of claim 41 , wherein the content of the document involves a dispute.

45. The transaction processing system of claim 32 , wherein the circuitry is configured to deliver the accepted portions of the extracted content to the second party via e-mail.

46. The transaction processing system of claim 32 , wherein the circuitry is configured to deliver the accepted portions of the extracted content to the second party via File Transfer Protocol.

47. The transaction processing system of claim 32 , wherein the circuitry is configured to deliver the accepted portions of the extracted content to the second party via Web Services.

48. The transaction processing system of claim 32 , wherein the circuitry is configured to receive the document via e-mail.

49. The transaction processing system of claim 32 , wherein the circuitry is configured to receive the document via File Transfer Protocol.

50. The transaction processing system of claim 32 , wherein the circuitry is configured to receive the document via Web Services.

51. The transaction processing system of claim 32 , wherein the circuitry is configured to receive the document via portal upload.

52. The transaction processing system of claim 32 , wherein the circuitry is configured to receive the document in a Microsoft Excel format.

53. The transaction processing system of claim 32 , wherein the circuitry is configured to receive the document in a CSV format.

54. The transaction processing system of claim 32 , wherein the circuitry is configured to receive the document in an XML format.

55. The transaction processing system of claim 32 , wherein the link is further associated with one or more format rules, registered with the transaction processing system by the second party, specifying a document format.

56. The transaction processing system of claim 55 , wherein the circuitry is configure to

convert the accepted portions of the extracted content to the document format specified by the one or more format rules registered with the transaction processing system by the second party, and

deliver the converted accepted portions of the extracted content to the second party via the link.

Assignments (8)
SECURITY INTEREST Recorded Nov 2, 2022
From: TELARIX, INC.
To: BANK OF MONTREAL
Reel/Frame 061631/0082 →
RELEASE OF SECURITY INTEREST Recorded Jun 14, 2022
From: CORTLAND CAPITAL MARKET SERVICES LLC
To: TELARIX, INC.
Reel/Frame 060194/0899 →
RELEASE OF SECURITY INTEREST Recorded Nov 20, 2018
From: TELARIX, INC.
To: WELLS FARGO BANK, NATIONAL ASSOCIATION
Reel/Frame 047558/0095 →
SECURITY INTEREST Recorded Nov 19, 2018
From: TELARIX, INC.
To: CORTLAND CAPITAL MARKET SERVICES LLC
Reel/Frame 047541/0673 →
RELEASE OF SECURITY INTEREST Recorded Jan 14, 2016
From: COMERICA BANK
To: TELARIX, INC.
Reel/Frame 037494/0993 →
SECURITY AGREEMENT Recorded Jan 14, 2016
From: TELARIX, INC.
To: WELLS FARGO BANK, NATIONAL ASSOCIATION, AS AGENT
Reel/Frame 037519/0934 →
SECURITY AGREEMENT Recorded Jun 28, 2011
From: TELARIX, INC.
To: COMERICA BANK
Reel/Frame 026513/0707 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jun 12, 2008
From: ZARGHAM, SHAWN; HATAM, MARK
To: TELARIX, INC.
Reel/Frame 021087/0823 →
Continuity (2)
Provisional Application 60904352 · Mar 2, 2007
Related Publication 20080235319A1 · Sep 25, 2008