IP Library Granted Patent US 7,580,937
Granted Patent B2
US 7,580,937 · App. 11/941,025 · Granted Aug 25, 2009

Method and apparatus for updating rules and transmitting change notifications

Assignee: Compulaw, LLC
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,580,937
App. No.
11/941,025
Granted
Aug 25, 2009
Kind
B2
Abstract

A method and apparatus for generating court dates. A Date Calculation Engine (DCE) is coupled to a court date server and a court rule database for generation of court dates. The court rule database includes formulas written in a Date Calculation Scripting Language (DCSL) for calculating the court dates. The court rules further include instructions for generating a Jurisdiction Selection Expert (JSE) and an Event Selection Expert (ESE) that enable a user to quickly select a jurisdiction and an event using hierarchal data structures. The DCE is combined with other software components to build a complete court date server system. The court rule database is maintained up-to-date with the latest changes to the rules. Deadlines affected by any rule changes are automatically identified and recalculated, and customers for whom the deadlines were calculated automatically notified to inform them of the changed deadlines.

Claims (96)

1. A method for generating and transmitting a calendar of different legal events capable of occurring in the course of a legal proceeding, the method comprising:

maintaining in a database at least one rule set including a plurality of date calculation instructions for calculating a plurality of different legal events;

receiving, under control of a server, an initial trigger date for an initial trigger legal event;

selecting, under control of the server, one or more date calculation instructions from the database based on the initial trigger legal event;

calculating, under control of the server, one or more event dates based on the initial trigger date and the retrieved date calculation instructions;

transmitting, under control of the server, the one or more calculated event dates to a user client;

maintaining, under control of the server, a transaction record of the one or more date calculation instructions used for generating the one or more event dates for the user client;

monitoring, under control of the server, a changes table for changes in the plurality of date calculation instructions, the changes table identifying the changed date calculation instructions;

automatically determining, under control of the server, whether the one or more date calculation instructions identified in the record are identified in the changes table;

for each one of the one or more date calculation instructions identified in the changes table, recalculating, under control of the server, the associated event date based on the change to the corresponding date calculation instruction; and

transmitting, under control of the server, the recalculated one or more event dates to the user client.

2. The method of claim 1 further comprising:

maintaining a relationship table storing relationship information for a plurality of the date calculation instructions, the relationship table indicating whether a particular date calculation instruction is related to another date calculation instruction; and

updating, under control of the server, relationship information in the relationship table based on the changed date calculation instructions.

3. The method of claim 1 further comprising:

identifying, under control of the server, a customer affected by the recalculated one or more event dates; and

transmitting, under control of the server, a notification to the customer of the recalculated one or more event dates.

4. The method of claim 1 further comprising:

calculating, under control of the server, a fee for recalculating the one or more event dates; and

charging, under control of the server, a user account based on the calculated fee.

5. The method of claim 1 further comprising:

receiving, under control of the server, update information for updating the date calculation instructions identified in the changes table, the update information identifying a rule set affected by the update, and further identifying the update as an event maintenance update or a non-event maintenance update, the event maintenance update triggering the recalculation of the one or more event dates identified in the changes table.

6. The method of claim 5 , wherein the updating includes:

determining, under control of the server, whether a date calculation instruction identified in the changes table exists in the database;

responsive to a determination that the identified date calculation instruction does not exist in the database, adding, under control of the server, the identified date calculation instruction to the database.

7. The method of claim 6 further comprising:

determining, under control of the server, whether the addition of the identified data calculation instruction is an event maintenance or non-event maintenance update; and

responsive to a determination that the addition of the identified date calculation instruction is an event maintenance update, storing, under control of the server, information on the added date calculation instructions as event maintenance change information.

8. The method of claim 5 , wherein the update information includes a list of holidays and associated dates for the identified rule set.

9. The method of claim 8 , wherein the updating includes:

determining, under control of the server, whether a holiday identified in the list of holidays exists in the database;

responsive to a determination that the identified holiday does not exist in the database, adding, under control of the server, the identified holiday to the database and storing information for the holiday addition as event maintenance change information.

10. The method of claim 9 , wherein the recalculating includes:

identifying, under control of the server, an earliest holiday date and a latest holiday date from the event maintenance change information;

determining, under control of the server, whether the one or more calculated event dates fall between the identified earliest holiday date and the identified latest holiday date; and

verifying, under control of the server, the one or more calculated event dates based on the holiday addition.

11. The method of claim 5 , wherein the update information includes a list of deleted date calculation instructions in the identified rule set.

12. The method of claim 11 , wherein the updating includes:

determining, under control of the server, whether a date calculation instruction identified in the list of deleted date calculation instructions exists in the database;

responsive to a determination that the identified date calculation instruction exists in the database, deleting, under control of the server, the date calculation instruction from the database; and

storing information on the deleted date calculation instruction as event maintenance change information.

13. A system for generating and transmitting a calendar of different legal events capable of occurring in the course of a legal proceeding, the system comprising:

a database storing at least one rule set including a plurality of date calculation instructions for calculating a plurality of different legal events;

a server coupled to the database, the server being configured to:

receive an initial trigger date for an initial trigger legal event;

select one or more date calculation instructions from the database based on the initial trigger legal event;

calculate one or more event dates based on the initial trigger date and the retrieved date calculation instructions;

transmit the one or more calculated event dates to a user client; and

maintain a transaction record of the one or more date calculation instructions used for generating the one or more event dates for the user client;

a database update module coupled to the server, the database update module being configured to monitor a changes table for changes in the plurality of date calculation instructions, the changes table identifying the changed date calculation instructions; and

a date maintenance module configured to automatically determine whether the one or more date calculation instructions identified in the record are identified in the changes table, and, for each one of the one or more date calculation instructions identified in the changes table, the date maintenance module being further configured to recalculate the associated event date based on the change to the corresponding date calculation instruction, and transmit the recalculated one or more event dates to the user client.

14. The system of claim 13 , wherein the server is further configured to:

maintain a relationship table storing relationship information for a plurality of the date calculation instructions, the relationship table indicating whether a particular date calculation instruction is related to another date calculation instruction; and

update relationship information in the relationship table based on the changed date calculation instructions.

15. The system of claim 13 further comprising:

a change notification module configured to identify a customer affected by the recalculated one or more event dates, and transmit a notification to the customer of the recalculated one or more event dates.

16. The system of claim 13 , wherein the server is further configured to:

calculate a fee for recalculating the one or more event dates; and

charge a user account based on the calculated fee.

17. The system of claim 13 , wherein the database update module is further configured to receive update information for updating the date calculation instructions identified in the changes table, the update information identifying a rule set affected by the update, the database update module being further configured to identify the update as an event maintenance update or a non-event maintenance update, the event maintenance update triggering the recalculation of the one or more event dates identified in the changes table.

18. The system of claim 17 , wherein the database update module, in updating the date calculation instructions, is further configured to:

determine whether a date calculation instruction identified in the changes table exists in the database; and

responsive to a determination that the identified date calculation instruction does not exist in the database, add the identified date calculation instruction to the database.

19. The system of claim 18 , wherein the database update module is further configured to:

determine whether the addition of the identified data calculation instruction is an event maintenance or non-event maintenance update; and

responsive to a determination that the addition of the identified date calculation instruction is an event maintenance update, store information on the added date calculation instructions as event maintenance change information.

20. The system of claim 17 , wherein the update information includes a list of holidays and associated dates for the identified rule set.

21. The system of claim 20 , wherein the database update module, in updating the date calculation instructions, is further configured to:

determine whether a holiday identified in the list of holidays exists in the database; and

responsive to a determination that the identified holiday does not exist in the database, add the identified holiday to the database and store information for the holiday addition as event maintenance change information.

22. The system of claim 21 , wherein the date maintenance module, in recalculating the one or more event dates, is further configured to:

identify an earliest holiday date and a latest holiday date from the event maintenance change information;

determine whether the one or more calculated event dates fall between the identified earliest holiday date and the identified latest holiday date; and

verify the one or more calculated event dates based on the holiday addition.

23. The system of claim 17 , wherein the update information includes a list of deleted date calculation instructions in the identified rule set.

24. The system of claim 23 , wherein the database update module, in updating the date calculation instructions, is further configured to:

determine whether a date calculation instruction identified in the list of deleted date calculation instructions exists in the database;

responsive to a determination that the identified date calculation instruction exists in the database, delete the date calculation instruction from the database; and

store information on the deleted date calculation instruction as event maintenance change information.

25. A system for generating and transmitting a calendar of different legal events capable of occurring in the course of a legal proceeding, the system comprising:

a database maintaining at least one rule set including a plurality of date calculation instructions for calculating a plurality of different legal events;

means for receiving an initial trigger date for an initial trigger legal event; means for selecting one or more date calculation instructions from the database based on the initial trigger legal event;

means for calculating one or more event dates based on the initial trigger date and the retrieved date calculation instructions;

means for transmitting the one or more calculated event dates to a user client;

means for maintaining a transaction record of the one or more date calculation instructions used for generating the one or more event dates for the user client;

means for monitoring a changes table for changes in the plurality of date calculation instructions, the changes table identifying the changed date calculation instructions;

means for automatically determining whether the one or more date calculation instructions identified in the record are identified in the changes table;

for each one of the one or more date calculation instructions identified in the changes table, means for recalculating the associated event date based on the change to the corresponding date calculation instruction; and

means for transmitting the recalculated one or more event dates to the user client.

26. The system of claim 25 further comprising:

means for maintaining a relationship table storing relationship information for a plurality of the date calculation instructions, the relationship table indicating whether a particular date calculation instruction is related to another date calculation instruction; and

means for updating relationship information in the relationship table based on the changed date calculation instructions.

27. The system of claim 25 further comprising: means for identifying a customer affected by the recalculated one or more event dates; and

means for transmitting a notification to the customer of the recalculated one or more event dates.

28. The system of claim 25 further comprising:

means for receiving update information for updating the date calculation instructions identified in the changes table, the update information identifying a rule set affected by the update, and further identifying the update as an event maintenance update or a non-event maintenance update, the event maintenance update triggering the means for recalculating with respect to the one or more event dates identified in the changes table.

Assignments (7)
RELEASE OF SECURITY INTEREST Recorded Oct 22, 2015
From: BANK OF MONTREAL, AS ADMINISTRATIVE AGENT
To: ADERANT COMPULAW, LLC
Reel/Frame 036858/0060 →
RELEASE OF SECURITY INTEREST Recorded Oct 22, 2015
From: NEW MOUNTAIN FINANCE HOLDINGS, L.L.C., AS ADMINISTRATIVE AGENT
To: ADERANT COMPULAW, LLC
Reel/Frame 036856/0524 →
RELEASE OF SECURITY INTEREST Recorded Jan 8, 2013
From: WELLS FARGO CAPITAL FINANCE, LLC (FORMERLY KNOWN AS WELLS FARGO FOOTHILL, LLC), AS ADMINISTRATIVE AGENT
To: TAUPO HOLDING, INC.; ADERANT HOLDINGS, INC.; NOVIENT, INC.; ADERANT NORTH AMERICA, INC.; ADERANT ENTERPRISE HOLDINGS, INC.; ADERANT LEGAL HOLDINGS, INC.; ADERANT LEGAL HOLDINGS (NZ) ULC; ADERANT CASE MANAGEMENT, LLC; ADERANT FM, LLC; ADERANT CM, LLC; ADERANT CRM, LLC; ADERANT COMPULAW, LLC; ADERANT INTERNATIONAL HOLDINGS, INC.
Reel/Frame 029583/0136 →
SECURITY AGREEMENT Recorded Dec 21, 2012
From: ADERANT COMPULAW, LLC
To: NEW MOUNTAIN FINANCE HOLDINGS, L.L.C., AS ADMINISTRATIVE AGENT
Reel/Frame 029531/0618 →
SECURITY AGREEMENT Recorded Dec 20, 2012
From: ADERANT COMPULAW, LLC
To: BANK OF MONTREAL, AS ADMINISTRATIVE AGENT
Reel/Frame 029530/0594 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Nov 12, 2012
From: COMPULAW LLC
To: ADERANT COMPULAW, LLC
Reel/Frame 029279/0244 →
AMENDED AND RESTATED PATENT SECURITY AGREEMENT Recorded Aug 19, 2011
From: TAUPO HOLDING, INC.; ADERANT NORTH AMERICA, INC.; ADERANT HOLDINGS, INC.; ADERANT LEGAL HOLDINGS, INC.; ADERANT ENTERPRISE HOLDINGS, INC.; ADERANT INTERNATIONAL HOLDINGS, INC.; NOVIENT, INC.; ADERANT LEGAL HOLDINGS (NZ) ULC; ADERANT CASE MANAGEMENT, LLC; ADERANT FM, LLC; ADERANT CM, LLC; ADERANT CRM, LLC; ADERANT COMPULAW, LLC
To: WELLS FARGO CAPITAL FINANCE, LLC (FORMERLY KNOWN AS WELLS FARGO FOOTHILL, LLC), AS AGENT
Reel/Frame 026781/0173 →
Continuity (5)
Continuation 1132144200 · Dec 28, 2005
Continuation In Part 1020156300 · Jul 22, 2002
Continuation In Part 1020159800 · Jul 22, 2002
Provisional Application 6030667700 · Jul 20, 2001
Related Publication 20080140721A1 · Jun 12, 2008