IP Library Granted Patent US 7,302,433
Granted Patent B2
US 7,302,433 · App. 11/321,442 · Granted Nov 27, 2007

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,302,433
App. No.
11/321,442
Granted
Nov 27, 2007
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 (57)

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 a database storing rules associated with a plurality of different legal events;

receiving rule update information, wherein the rule update information identifies a rule set affected by the update, and further identifies the update as an event maintenance update or a non-event maintenance update, the event maintenance update potentially affecting at least one existing deadline calculated for at least one of the plurality of different legal events;

updating rules in the rules database based on the rule update information, wherein the updating the rules in the rules database includes:

determining whether a formula identified by the rule update information exists in the rules database:

responsive to a determination that the identified formula exists in the rules database, making changes to the formula in the rules database;

responsive to a determination that the identified formula does not exist in the rules database, adding the identified formula in the rules database;

determining whether the change or addition of the identified formula is an event maintenance or non-event maintenance update based on the identification of the associated rule set as an event maintenance update or a non-event update; and

responsive to a determination that the change or addition of the identified formula is an event maintenance update, storing information on the changed or added formula as event maintenance change information;

determining whether a particular rule update is an update potentially affecting at least one existing deadline calculated for at least one of the plurality of different legal events;

responsive to the determination, recalculating the existing deadline based on the particular rule update;

identifying a customer affected by the recalculated deadline; and

notifying the customer of the recalculated deadline.

2. The method of claim 1 , wherein the particular rule update is an update to date calculation instructions used to calculate the at least one existing deadline.

3. The method of claim 1 , wherein the rule update information identifies one or more changed or new formulas for the rule set.

4. The method of claim 1 , wherein the recalculating the existing deadline includes:

tracking calculated deadlines and formulas used for calculating the deadlines in customer-specific transaction records;

identifying the changed formula from the event maintenance change information;

identifying a customer-specific transaction record including the changed formula; and

recalculating a deadline in the customer-specific transaction record based on the changed formula.

5. The method of claim 1 , wherein the recalculating the existing deadline includes:

tracking calculated deadlines and formulas used for calculating the deadlines in customer-specific transaction records;

identifying the new formula from the event maintenance change information;

querying a formula relationship table for determining a related formula referenced by the new formula;

identifying a customer-specific transaction record including the related formula;

calculating a new event date based on the new formula; and

adding the new event date in the identified customer-specific transaction record.

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

7. The method of claim 6 , wherein the updating the rules in the rules database includes:

determining whether a holiday identified in the list of holidays exists in the rules database;

responsive to a determination that the identified holiday exists in the rules database, and that a date for the holiday in the list of holidays differs from a date for the holiday in the rule update information, changing the date of the holiday in the rules database and storing information for the holiday change as event maintenance change information; and

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

8. 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 a database storing rules associated with a plurality of different legal events;

receiving rule update information, wherein the rule update information identifies a rule set affected by the update, and further identifies the update as an event maintenance update or a non-event maintenance update, the event maintenance update potentially affecting at least one existing deadline calculated for at least one of the plurality of different legal events, and wherein the rule update information includes a list of holidays and associated dates for the rule set;

updating rules in the rules database based on the rule update information, wherein the updating the rules in the rules database includes:

determining whether a holiday identified in the list of holidays exists in the rules database;

responsive to a determination that the identified holiday exists in the rules database, and that a date for the holiday in the list of holidays differs from a date for the holiday in the rule update information, changing the date of the holiday in the rules database and storing information for the holiday change as event maintenance change information; and

responsive to a determination that the identified holiday does not exist in the rules database, adding the identified holiday in the rules database and storing information for the holiday addition as event maintenance change information;

determining whether a particular rule update is an update potentially affecting at least one existing deadline calculated for at least one of the plurality of different legal events;

responsive to the determination, recalculating the existing deadline based on the particular rule update, wherein the recalculating the existing deadline includes:

tracking calculated deadlines and formulas used for calculating the deadlines in customer-specific transaction records;

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

identifying a customer-specific transaction record including a deadline between the identified earliest holiday date and the identified latest holiday date; and

verifying the deadline based on holiday change or addition;

identifying a customer affected by the recalculated dead 1 ine; and

notifying the customer of the recalculated deadline.

9. The method of claim 1 , wherein the rule update information includes a list of deleted formulas in the rule set.

10. The method of claim 9 , wherein the updating the rules in the rules database includes:

determining whether a formula identified in the list of deleted formulas exists in the rules database;

responsive to a determination that the identified formula exists in the rules database, deleting the formula in the rules database; and

storing information on the deleted formula as event maintenance change information.

11. The method of claim 10 , wherein the recalculating the existing deadline includes:

tracking calculated deadlines and formulas used for calculating the deadlines in customer-specific transaction records;

identifying the deleted formula from the event maintenance change information;

identifying a customer-specific transaction record including the identified formula; and

deleting the identified formula and a deadline calculated by the identified formula from the customer-specific transaction record.

Assignments (8)
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 Oct 22, 2015
From: BANK OF MONTREAL, AS ADMINISTRATIVE AGENT
To: ADERANT COMPULAW, LLC
Reel/Frame 036858/0060 →
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 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Apr 11, 2006
From: KALMICK, DAVID J.; RAINS, RICKY J.; MANNERS, ALEXANDER J.
To: COMPULAW, LLC
Reel/Frame 017779/0045 →
Continuity (4)
Continuation In Part 1020156300 · Jul 22, 2002
Continuation In Part 1020159800 · Jul 22, 2002
Provisional Application 6030667700 · Jul 20, 2001
Related Publication 20060173917A1 · Aug 3, 2006