Intelligent network charging edge

• US 7,526,547 B2
• Filed: 10/12/2001
• Issued: 04/28/2009
• Est. Priority Date: 10/12/2001
• Status: Expired due to Term

• Current Assignee: RPX Corporation
• Original Assignee: Nokia Corporation
• Inventors: Rodrigo, Anthony
• Primary Examiner(s): RUDY, ANDREW J
• Application Number:
  US09/976,876
• Publication Number:
  US 20030074286A1
• Time in Patent Office: 2,755 Days
• Field of Search: 709/223, 709/225, 709/227, 709/229, 705/32
• US Class Current: 709/225
• CPC Class Codes: G06Q 20/14 specially adapted for billing systems
• CPC Class Codes: G06Q 30/04 Billing or invoicing
• CPC Class Codes: G06Q 40/10 Tax strategies
• CPC Class Codes: G07F 17/0014 for vending, access and use of specific services not covered anywhere else in G07F17/00 meter-controlled dispensing of liquid, gas or electricity G07F15/00
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/04 specially adapted for terminals or networks with limited capabilities; specially adapted for terminal portability
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]
• CPC Class Codes: H04L 9/40 Network security protocols
• 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/43 Billing software details
• CPC Class Codes: H04M 15/53 using mediation
• CPC Class Codes: H04M 15/57 for integrated multimedia messaging subsystem [IMS]
• CPC Class Codes: H04M 15/68 Payment of value-added services
• CPC Class Codes: H04M 15/7655 shared by technologies
• CPC Class Codes: H04M 15/77 involving multiple accounts per user
• CPC Class Codes: H04M 15/772 per service, e.g. prepay or post-pay
• CPC Class Codes: H04M 15/80 Rating or billing plans; Tariff determination aspects
• CPC Class Codes: H04M 2215/0152 General billing plans, rate plans, e.g. charge rates, numbering plans, rate centers, customer accounts
• CPC Class Codes: H04M 2215/0172 Mediation, i.e. device or program to reformat CDRS from one or more switches in order to adapt to one or more billing programs formats
• CPC Class Codes: H04M 2215/0196 Payment of value-added services, mainly when their charges are added on the telephone bill, e.g. payment of non-telecom services, e-commerce, on-line banking
• CPC Class Codes: H04M 2215/208 : IMS, i.e. Integrated Multimedia messaging Subsystem
• CPC Class Codes: H04M 2215/725 : Shared by technologies, e.g. one account for different access technologies
• CPC Class Codes: H04M 2215/7254 : Multiple accounts per user
• CPC Class Codes: H04M 2215/7263 : per service, e.g. prepay and post-pay

Abstract

A system and method for managing charging and billing for services on a network, where the network includes network elements that provide billable services, and charging elements that perform various charging and billing functions. Charging event are received at a network charging edge that isolates the network elements and charging elements. The network charging edge includes one or more bridge modules that are logically coupled between the network elements and the charging elements. Charging transactions between the network elements and their respective charging elements are managed via the bridge modules, by applying rules to the charging transaction initiated by corresponding charging events.

Claims

1. A method comprising:

coupling a plurality of bridge modules to form a logical network layer between one or more network elements providing billable services and one or more charging elements;

receiving charging events at the bridge modules, wherein the charging events record details of the billable services; and

managing charging transactions at a network between the network elements and their respective charging elements via the bridge modules through the application of rules to the charging transaction initiated by corresponding charging events, wherein each of the bridge modules is configured with a subset of the rules assigned to the services managed by that bridge module, and one of the bridge modules is designated as a primary bridge module to receive the rules and distribute the subsets of rules to the remaining bridge modules.

2. The method as in claim 1 further comprising generating and transmitting the charging events by the network elements providing the billable services, wherein the charging events comprise service use parameters used by the charging elements.

3. The method as in claim 1, further comprising entering the rules at a console coupled to the primary bridge module.

4. The method as in claim 1, further comprising:

implementing an application programming interface (API) at each of the network elements providing billable services to interface each of the respective network elements to the one or more bridge modules; and

generating and transmitting the charging events by the network elements providing the billable services, wherein transmitting the charging events comprises transmitting XML-formatted charging events pursuant to the API.

5. The method as in claim 1, wherein receiving charging events comprises intercepting the charging events dispatched by the network elements to the charging elements.

6. The method as in claim 1, wherein managing charging transactions comprises applying the rules to transform the charging events to a format recognizable by targeted charging elements.

7. The method as in claim 6, wherein applying the rules to transform the charging events comprises converting the charging events from a first format to a second format.

8. The method as in claim 6, wherein applying the rules to transform the charging events comprises filtering the charging events to prevent transmission of particular ones of the charging events to the charging elements.

9. The method as in claim 6, wherein applying the rules to transform the charging events comprises recalculating fields of the charging events to present the fields in units utilized in the charging elements.

10. The method as in claim 6, wherein applying the rules to transform the charging events comprises routing the charging events to multiple destinations.

11. The method as in claim 6, further comprising transmitting the transformed charging events via interface objects corresponding to respective charging elements.

12. The method as in claim 11, further comprising directing the transformed charging events to the interface objects corresponding to targeted charging elements based on the rules and the transformed charging events.

13. The method as in claim 12, wherein directing the transformed charging events further comprises applying the rules to the transformed charging events to identify addresses of the interface objects corresponding to the targeted charging elements.

14. The method as in claim 1, wherein managing charging transactions comprises selecting an interface object for communicating with a corresponding charging element, wherein selecting an interface object comprises identifying one of a plurality of the interface objects as determined by object configuration rules.

15. The method as in claim 1, wherein managing charging transactions comprises performing a plurality of transaction operations with a plurality of the charging elements in a sequence dictated by the rules.

16. The method as in claim 15, wherein performing a plurality of transaction operations with a plurality of the charging elements comprises applying the rules to responsive messages from at least one of the charging elements to perform one or more of the transaction operations.

17. The method as in claim 1, wherein managing charging transactions comprises coordinating one or more communications with the charging elements to carry out the charging transaction.

18. The method as in claim 17, wherein coordinating the communications with the charging elements comprises transmitting a first call to a first charging element in response to applying the rules to the charging transaction initiated by the corresponding charging event.

19. The method as in claim 18, wherein coordinating the communications with the charging elements further comprises receiving a response to the first call from the first charging element, and transmitting a second call to a second charging element in response to applying the rules to the response to the first call.

20. An apparatus, comprising:

a processor configured with executable instructions that;

couple one or more bridge modules to form a logical network layer between one or more network elements providing billable services and one or more charging elements;

receive charging events at the one or more bridge modules, wherein the charging events record details of the billable services; and

manage charging transactions at the network between the network elements and their respective charging elements via the one or more bridge modules through the application of rules to the charging transaction initiated by corresponding charging events, wherein managing the charging transactions comprises applying the rules to transform the charging events to a format recognizable by targeted charging elements.

21. The apparatus as in claim 20, wherein the executable instructions further cause the apparatus to generate and transmit the charging events by the network elements providing the billable services, wherein the charging events comprise service use parameters used by the charging elements.

22. The apparatus as in claim 20, wherein the executable instructions further:

implement an application programming interface (API) at each of the network elements providing billable services to interface each of the respective network elements to the one or more bridge modules; and

generate and transmit the charging events by the network elements providing the billable services, wherein transmitting the charging events comprises transmitting XML-formatted charging events pursuant to the API.

23. The apparatus as in claim 20, wherein receiving charging events comprises intercepting the charging events dispatched by the network elements to the charging elements.

24. The apparatus as in claim 20, wherein managing charging transactions comprises applying the rules to transform the charging events to a format recognizable by targeted charging elements.

25. The apparatus as in claim 24, wherein applying the rules to transform the charging events comprises converting the charging events from a first format to a second format.

26. The apparatus as in claim 24, wherein applying the rules to transform the charging events comprises filtering the charging events to prevent transmission of particular ones of the charging events to the charging elements.

27. The apparatus as in claim 24, wherein applying the rules to transform the charging events comprises recalculating fields of the charging events to present the fields in units utilized in the charging elements.

28. The apparatus as in claim 24, wherein applying the rules to transform the charging events comprises routing the charging events to multiple destinations.

29. The apparatus as in claim 24, wherein the executable instructions further transmit the transformed charging events via interface objects corresponding to respective charging elements.

30. The apparatus as in claim 29, wherein the executable instructions further direct the transformed charging events to the interface objects corresponding to targeted charging elements based on the rules and the transformed charging events.

31. The apparatus as in claim 30, wherein directing the transformed charging events further comprises applying the rules to the transformed charging events to identify addresses of the interface objects corresponding to the targeted charging elements.

32. The apparatus as in claim 20, wherein managing charging transactions comprises selecting an interface object for communicating with a corresponding charging element, wherein selecting an interface object comprises identifying one of a plurality of the interface objects as determined by object configuration rules.

33. The apparatus as in claim 20, wherein managing charging transactions comprises performing a plurality of transaction operations with a plurality of the charging elements in a sequence dictated by the rules.

34. The apparatus as in claim 33, wherein performing a plurality of transaction operations with a plurality of the charging elements comprises applying the rules to responsive messages from at least one of the charging elements to perform one or more of the transaction operations.

35. The apparatus as in claim 20, wherein managing charging transactions comprises coordinating one or more communications with the charging elements to carry out the charging transaction.

36. The apparatus as in claim 35, wherein coordinating the communications with the charging elements comprises transmitting a first call to a first charging element in response to applying the rules to the charging transaction initiated by the corresponding charging event.

37. The apparatus as in claim 36, wherein coordinating the communications with the charging elements further comprises receiving a response to the first call from the first charging element, and transmitting a second call to a second charging element in response to applying the rules to the response to the first call.

38. The apparatus as in claim 20, wherein the executable instructions further receive the rules at a console coupled to the primary bridge module.

39. A computer-readable storage medium encoded with instructions that, when executed by an apparatus, perform:

coupling a plurality of bridge modules to form a logical network layer between one or more network elements providing billable services and one or more charging elements;

receiving charging events at the bridge modules, wherein the charging events record details of the billable services; and

managing charging transactions at a network between the network elements and their respective charging elements via the bridge modules through the application of rules to the charging transaction initiated by corresponding charging events, wherein each of the bridge modules is configured with a subset of the rules assigned to the services managed by that bridge module, and one of the bridge modules is designated as a primary bridge module to receive the rules and distribute the subsets of rules to the remaining bridge modules.

40. The computer-readable storage medium as in claim 39, wherein the executable instructions further cause the apparatus to generate and transmit the charging events by the network elements providing the billable services, wherein the charging events comprise service use parameters used by the charging elements.

41. The computer-readable storage medium as in claim 39, wherein the executable instructions further cause the apparatus to:

implement an application programming interface (API) at each of the network elements providing billable services to interface each of the respective network elements to the one or more bridge modules; and

generate and transmit the charging events by the network elements providing the billable services, wherein transmitting the charging events comprises transmitting XML-formatted charging events pursuant to the API.

42. The computer-readable storage medium as in claim 39, wherein receiving charging events comprises intercepting the charging events dispatched by the network elements to the charging elements.

43. The computer-readable storage medium as in claim 39, wherein managing charging transactions comprises applying the rules to transform the charging events to a format recognizable by targeted charging elements.

44. The computer-readable storage medium as in claim 43, wherein applying the rules to transform the charging events comprises converting the charging events from a first format to a second format.

45. The computer-readable storage medium as in claim 43, wherein applying the rules to transform the charging events comprises filtering the charging events to prevent transmission of particular ones of the charging events to the charging elements.

46. The computer-readable storage medium as in claim 43, wherein applying the rules to transform the charging events comprises recalculating fields of the charging events to present the fields in units utilized in the charging elements.

47. The computer-readable storage medium as in claim 43, wherein applying the rules to transform the charging events comprises routing the charging events to multiple destinations.

48. The computer-readable storage medium as in claim 43, wherein the executable instructions further cause the apparatus to transmit the transformed charging events via interface objects corresponding to respective charging elements.

49. The computer-readable storage medium as in claim 48 wherein the executable instructions further cause the apparatus to direct the transformed charging events to the interface objects corresponding to targeted charging elements based on the rules and the transformed charging events.

50. The computer-readable storage medium as in claim 49, wherein directing the transformed charging events further comprises applying the rules to the transformed charging events to identify addresses of the interface objects corresponding to the targeted charging elements.

51. The computer-readable storage medium as in claim 39, wherein managing charging transactions comprises selecting an interface object for communicating with a corresponding charging element, wherein selecting an interface object comprises identifying one of a plurality of the interface objects as determined by object configuration rules.

52. The computer-readable storage medium as in claim 39, wherein managing charging transactions comprises performing a plurality of transaction operations with a plurality of the charging elements in a sequence dictated by the rules.

53. The computer-readable storage medium as in claim 52, wherein performing a plurality of transaction operations with a plurality of the charging elements comprises applying the rules to responsive messages from at least one of the charging elements to perform one or more of the transaction operations.

54. The computer-readable storage medium as in claim 39, wherein managing charging transactions comprises coordinating one or more communications with the charging elements to carry out the charging transaction.

55. The computer-readable storage medium as in claim 43, wherein managing charging transactions comprises selecting an interface object for communicating with a corresponding charging element, wherein selecting an interface object comprises identifying one of a plurality of the interface objects as determined by object configuration rules.

56. The computer-readable storage medium as in claim 43, wherein managing charging transactions comprises performing a plurality of transaction operations with a plurality of the charging elements in a sequence dictated by the rules.

57. The computer-readable storage medium as in claim 56, wherein performing a plurality of transaction operations with a plurality of the charging elements comprises applying the rules to responsive messages from at least one of the charging elements to perform one or more of the transaction operations.

58. The computer-readable storage medium as in claim 43, wherein managing charging transactions comprises coordinating one or more communications with the charging elements to carry out the charging transaction.