Communications pricing and charging maintenance sub-system and process

• US 5,943,657 A
• Filed: 09/30/1996
• Issued: 08/24/1999
• Est. Priority Date: 03/30/1994
• Status: Expired due to Fees

• Current Assignee: British Telecommunications PLC (BT Group PLC)
• Original Assignee: British Telecommunications PLC (BT Group PLC)
• Inventors: Regan, Timothy, Wilson, Jeremy, Heritage, Anthony, Thompson, Paul H, Wezeman, Clazien D, Kerr, Brian S., Freestone, David
• Primary Examiner(s): Cosimano, Edward R.
• Application Number:
  US08/723,410
• Time in Patent Office: 1,058 Days
• Field of Search: 364/400, 364/464.1, 379/111, 379/114, 379/115, 379/121, 395/201, 395/230, 395/231, 395/651, 395/701, 395/702, 395/705, 395/712, 705/1, 705/30, 705/31, 705/400
• US Class Current: 705/400
• CPC Class Codes: G06Q 30/0283 Price estimation or determination
• CPC Class Codes: G06Q 30/04 Billing or invoicing
• CPC Class Codes: H04M 15/00 Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
• CPC Class Codes: H04M 15/44 Augmented, consolidated or itemized billing statement or bill presentation
• CPC Class Codes: H04M 2215/0104 Augmented, consolidated or itemised billing statement, e.g. additional billing information, bill presentation, layout, format, e-mail, fax, printout, itemised bill per service or per account, cumulative billing, consolidated billing

Abstract

Pricing and charging arrangements available to communication network operators or service providers take account of factors such as taxes which affect the billable value and which may be put in place in many different ways and at variable times in relation to data processing exercises which need to be carried out. A system is provided which can be used in generating bills by applying modifying factors which can be changed or added to in a relatively easy manner. An object-oriented front end for a legacy system can be used in design and subsequently embedded. Programs developed in an object oriented environment are converted into instructions implementable by a procedurally based processing device. An activity hierarchy of functions is created for each object, a data subject area is created for each object and a main calling program specifies the relationship between the programs and data areas so as to retain encapsulation of the original object oriented definition. This is particularly useful for developing new systems in an object oriented environment which may then be embedded into existing procedurally based systems.

Claims

1. A process for generating billable amounts in respect of data records for the supply of goods or services over a period of time, said process comprising:

a period charge interface object, which provides control functionality for use by the process in relation to charges incurred over a period of time;

a tax table object, defining tax rates and callable by said period charge interface object;

a tax calculation object for calculating tax values in respect of said supply of goods or services, callable by the period charge interface object;

an accumulation object, for accumulating values returned to the period charge object from the tax calculation object,

wherein, in use, input data including a period start date and a period end date are supplied to the period charge interface object, tax rates are supplied to the period charge interface object from the tax table object, a tax calculation is made by the tax calculation object, and the resulting calculated tax values are supplied to the accumulation object; and

wherein a "table manager" object is arranged to supply values to the tax table object and to select operational policy options.

2. A process according to claim 1, wherein the calculation of tax at the bill date is a selectable option.

3. A process according to claim 1, wherein the calculation of tax at the end of the usage date is a selectable option.

4. A process according to claim 1, wherein the apportionment of tax over the usage period is a selectable option.

5. A process according to claim 1, including a "single date charge" object for calculating tax for a transaction occurring at a specific date, wherein said single date charge object is arranged to call the tax table object and the accumulation object.

6. A process according to claim 1, including a "tax refund" object arranged to call said tax calculation object, the period charge object and a re-tax object.

7. A process according to claim 1, wherein a "rounder" object callable by said tax calculation object is arranged to round values calculated by said tax calculation object.

8. A process according to claim 7, wherein a "configuration" object is arranged to facilitate programming of said rounder object.

9. Apparatus for processing data representing a supply of goods or services over a period of time to calculate tax associated with said supply, comprising processing means facilitating execution within an object orientated environment, characterised by the provision of:

a "period charge" interface object;

a "tax table" object defining tax rates and callable by the period charge interface object;

a tax calculation object for calculating tax for individual items, callable by the period charge interface object; and

an "accumulation" object for accumulating values returned to the period charge object from said tax calculation object, wherein

input data including a period start date and a period end date are supplied to the period charge interface object,

tax rates are supplied to the period charge object from the tax table object,

the tax calculation is made by the tax calculation object, and

calculated tax value is supplied to the accumulation object.

10. A method of converting programs developed under an object oriented environment into instructions implementable by a procedurally based processing device, said method comprising:

(a) creating an activity hierarchy of functions for each of said objects;

(b) creating a data subject area for each of said objects; and

(c) defining a matrix of processes against data entities resulting from steps (a) and (b) arranged to specify the relationship between object derived programs and object derived data subject areas to thereby retain encapsulation as defined by an object oriented program.

11. A method according to claim 10, wherein said step of creating a data area includes defining a process for each object.

12. A method according to claim 10, wherein said data area creation step includes copying object descriptions to respective process descriptions.

13. A method according to claim 10, wherein said step of creating a procedural program includes creating an elementary process derived from an object and from an operation.

14. A method according to claim 10, wherein said activity hierarchy creation step includes defining import and export values.

15. A method according to claim 10, including checks for encapsulation violation.

16. A method of calculating taxes defined in an object oriented environment and converted into a procedural program by a method according to claim 10.

17. A method according to claim 16, wherein said object oriented definition includes:

a "period charge" interface object;

a "tax table" object defining tax rates and callable by said period charge interface object;

a tax calculation object for calculating tax for individual items, callable by the period charge interface object; and

an "accumulation" object for accumulating values returned to the period charge object from said tax calculation object, wherein input data including a period start date and a period end date are supplied to the period charge interface object,

tax rates are supplied to the period charge object from the tax table object,

a tax calculation is made by the tax calculation object, and

the calculated tax value is supplied to the accumulation object.

18. A process according to claim 17, wherein a "rounder" object callable by said tax calculation object, is arranged to round values calculated by said tax calculation object.

19. A process according to claim 17, wherein a "configuration" object is arranged to facilitate programming of said rounder object.

20. A data processing system, for use in pricing and charging equipment, to process data relevant to a period of time by selecting and applying appropriately one or more date-related modifying factors, the system comprising:

i) a data input for the data, said data

a) relating to one or more chargeable event(s),

b) containing for each chargeable event at least one charge-related value, as duration, and at least one event date, and

c) wherein, for at least one chargeable event, an event date comprises a start date and an end date relating to a period of time;

ii) a process control module for controlling processing of said data;

iii) a first data store for holding at least one set of definitions, each definition comprising, directly or indirectly, at least one of said modifying factors and at least one definition including one or more dates of validity relating to a modifying factor;

iv) a second data store arranged in sections for allocation to respective modifying factors;

v) means for determining a relevant identifier for each charge-related value; and

vi) calculating means for calculating a set of charge values from said charge-related values together with price data

wherein the process control module is arranged, on receipt of the data at the input, to control the system such that it;

vii) determines a relevant identifier for each charge-related value from the data;

viii) accesses the first data store and locates the relevant definition or definitions for that identifier;

ix) calculates a set of charge values from said charge-related values together with price data;

x) sorts the charge values according to modifying factor, using the relevant definition; and

xi) outputs the charge values to the relevant sections of the second data store, the charge value for any chargeable event for which the event date comprises a start date and an end date being apportioned between sections in accordance with any date of validity included in a relevant definition.

21. A system as in claim 20 wherein the modifying factor for a section of the second data store is zero.

22. A system as in claim 20 wherein the first data store holds a plurality of sets of definitions, the identifiers for each of the definitions being unique.

23. A system as in claim 20 wherein the data contains, for each chargeable event, an identifier for a definition.

24. A system as in claim 20 wherein the means for determining a relevant identifier comprises means for identifying category codes contained by the data in relation to the chargeable events, and for identifying predetermined combinations of category codes in relation to a chargeable event, each such combination of category codes determining a different identifier in place of the identifiers otherwise determined by each of the category codes on its own.

25. A system as in claim 20 which further comprises means to input one or more new definitions to said first data store.

26. A system as in claim 20 which further comprises means for substituting, at step x), a different date for a date of validity from a definition, and for repeating steps vii) to xi) in respect of data previously processed by the system.

27. A system as in claim 20 which further comprises means for updating one or more definitions in the first data store and for reprocessing data, by use of the system, using the updated definitions.

28. Apparatus for use in a system as in claim 20 for processing data representing a supply of goods or services over a period of time to calculate tax associated with said supply, the apparatus comprising processing means facilitating execution within an object orientated environment, characterized by the provision of:

a "period charge" interface object;

a "tax table" object defining tax rates and callable by the period charge interface object;

a tax calculation object for calculating tax for individual items, callable by the period charge interface object; and

an "accumulation" object for accumulating values returned to the period charge object from said tax calculation object, wherein

input data including a period start date and a period end date are supplied to the period charge interface object,

tax rates are supplied to the period charge object form the tax table object,

the tax calculation is made by the tax calculation object, and

calculated tax value is supplied to the accumulation object.

29. A process for generating billable amounts in respect of data records for the supply of goods or services over a period of time, by use of a system according to claim 20, the process being characterized by:

a period charge interface object, which provides control functionality for use by the process in relation to charges incurred over a period of time;

a tax table object, defining tax rates and callable by said period charge interface object;

a tax calculation object for calculating tax values in respect of said supply of goods or services, callable by the period charge interface object; and

an accumulation object, for accumulating values returned to the period charge object from the tax calculation object,

wherein, in use, input data including a period start date and a period end date are supplied to the period charge interface object, tax rates are supplied to the period charge interface object from the tax table object, a tax calculation is made by the tax calculation object, and the resulting calculated tax values are supplied to the accumulation object.

30. A process as in claim 29 including a "tax refund" object arranged to call said tax calculation object, the period charge object and a re-tax object.

31. A process as in claim 29 wherein a "rounder" object callable by said tax calculation object is arranged to round values calculated by said tax calculation object.

32. A process as in claim 31 wherein a "configuration" object is arranged to facilitate programming of said rounder object.

33. A process as in claim 29 wherein a "table manager" object is arranged to supply values to the tax table object and to select operational policy options.

34. A process as in claim 33 wherein the calculation of tax at the bill date is a selectable option.

35. A process as in claim 33 wherein the calculation of tax at the end of the usage date is a selectable option.

36. A process as in claim 33 wherein the apportionment of tax over the usage period is a selectable option.

37. A process as in claim 29 including a "single date charge" object for calculating tax for a transaction occurring at a specific date, wherein said single date charge object is arranged to call the tax table object and the accumulation object.

38. A configuration management system, for use in configuring pricing and charging equipment for processing data which has an associated set of modifying factors, by selecting and applying appropriately one or more of said modifying factors, the configuration management system including a data processing system for use in pricing and charging equipment, to process data relevant to a period of time by selecting and applying appropriately one or more date-related modifying factors, the data processing system comprising:

i) a data input for the data, said data

a) relating to one or more chargeable event(s),

b) containing for each chargeable event at least one charge-related value, as duration, and at least one event date, and

c) wherein, for at least one chargeable event, an event date comprises a start date and an end date relating to a period of time;

ii) a process control module for controlling processing of said data;

iii) a first data store for holding at least one set of definitions, each definition comprising, directly or indirectly, at least one of said modifying factors and at least one definition including one or more dates of validity relating to a modifying factor;

iv) a second data store arranged in sections for allocation to respective modifying factors;

v) means for determining a relevant identifier for each charge-related value; and

vi) calculating means for calculating a set of charge values from said charge-related values together with price data wherein the process control module is arranged, on receipt of the data at the input, to control the system such that it;

vii) determines a relevant identifier for each charge-related value from the data;

viii) accesses the first data store and locates the relevant definition or definitions for identifier;

ix) calculates a set of charge values from said charge-related values together with price data;

x) sorts the charge values according to modifying factor, using the relevant definition; and

xi) outputs the charge values to the relevant sections of the second data store, the charge value for any chargeable event for which the event date comprises a start date and an end date being apportioned between sections in accordance with any date of validity included in a relevant definition.

39. A process for use in pricing and charging event-related data relevant to a period of time, the data having been output by a communications system, said process comprising:

i) determining a relevant identifier for each charge-related value from the data;

ii) accessing a first data store and locating a relevant definition or definitions for that identifier;

iii) calculating a set of charge values from said charge-related values together with price data;

iv) sorting the charge values according to modifying factor, using the relevant definition; and

outputting the charge values to relevant sections of a second date store;

wherein the charge value for any chargeable event for which the event date comprises a start date and an end date being apportioned between sections of the second data store in accordance with any date of validity included in a relevant definition.