Method and apparatus for generating and collecting a billing event object within an on-line network

• US 5,893,077 A
• Filed: 08/23/1995
• Issued: 04/06/1999
• Est. Priority Date: 08/23/1995
• Status: Expired due to Term

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Griffin, William J.
• Primary Examiner(s): Tkacs, Stephen R.
• Application Number:
  US08/518,534
• Time in Patent Office: 1,322 Days
• Field of Search: 395/202, 395/207, 395/208, 395/210, 395/211, 395/226, 395/227, 395/230, 395/232, 395/234, 395/601, 395/609, 395/610, 395/614, 395/184.01, 395/186, 395/187.01 , 395/200.01, 395/200.02, 395/200.03, 395/200.06, 395/200.09, 395/683, 705/2, 705/7, 705/8, 705/10, 705/11, 705/26, 705/27, 705/30, 705/32, 705/34, 707/9, 707/10, 707/103, 707/104
• US Class Current: 705/34
• CPC Class Codes: G06Q 30/04 Billing or invoicing
• CPC Class Codes: G06Q 40/12 Accounting
• CPC Class Codes: H04L 12/14 Charging , metering or billing arrangements for data wireline or wireless communications
• CPC Class Codes: H04L 12/1403 Architecture for metering, charging or billing
• CPC Class Codes: Y10S 707/99945 Object-oriented database structure processing
• CPC Class Codes: Y10S 707/99948 Application of database or data structure, e.g. distributed, multimedia, or image

Abstract

An event generation and collection system for a distributed network includes an event source which generates event objects and an event collector for gathering objects. Conversion routines are run on the event objects so that the data they carry can be converted to a format that is useful by other processes in the network.

Claims

1. A method of handling a billing event in an on-line network, the method comprising the steps of:

providing a class hierarchy of billing events wherein each defined billing event is indicative of a customer computer access to the on-line network;

generating a billing event object from the billing event class in response to the customer computer accessing a server computer in the on-line network; and

serializing and collecting the billing event object generated on said server computer in the on-line network into a storage.

2. The method of claim 1, wherein the class hierarchy includes a connect event.

3. The method of claim 1, wherein the class hierarchy includes a download event.

4. The method of claim 1, wherein the customer computer accessing the server computer comprises connecting to an application server.

5. The method of claim 4, wherein the customer computer accessing the server computer is through a gateway.

6. The method of claim 1, wherein the billing event object is generated at a data center.

7. The method of claim 1, wherein the generated billing event object includes properties.

8. The method of claim 1, wherein the collecting step takes place at a billing event collector computer.

9. The method of claim 1, wherein the storage comprises a file.

10. The method of claim 1, wherein the collecting step includes the step of polling a plurality of billing event generation servers.

11. The method of claim 1, wherein the billing event object includes the customer ID and time of day.

12. The method of claim 1, further comprising the step of providing data within the billing event object to a billing system.

13. The method of claim 1, additionally comprising the step of providing data within the billing event object to a marketing analysis computer system.

14. The method of claim 1, wherein the billing event object is generated by an applications server.

15. The method of claim 1, wherein the billing event object is generated by a gateway.

16. The method of claim 1, further comprising the step of storing the billing event object into an event object queue.

17. The method of claim 16, wherein collecting the billing event object into a storage includes the steps of removing the billing event object from the event object queue and serializing the billing event object.

18. A billing event object generating system, comprising:

a plurality of computing devices connected together into a network;

a plurality of billing event object generators located in at least a portion of the computing devices, wherein billing event objects are generated which are indicative of actions within the network, and each billing event object generator serializes and stores a billing event object in a billing event generation file in a persistent storage;

a billing event collector connected to the network which periodically retrieves the billing event generation files from the billing event object generators.

19. The system of claim 18, wherein the computing devices include client and server computers.

20. The system of claim 18, wherein the network is an on-line network and the actions include a file download event.

21. The system of claim 18, wherein the persistent storage comprises a hard disk drive.

22. The system of claim 18, wherein the persistent storage includes a file system.

23. The system of claim 18, wherein the billing event object generators execute on server computers.

24. The system of claim 18, wherein the billing event collector exports the billing event object into a plurality of export formats.

25. The system of claim 24, further comprising a plurality of export subdirectories, wherein the billing event collector places at least one of the billing event generation files in at least two of the export subdirectories.

26. The system of claim 18, additionally comprising a first program responsive to one export format and a second program responsive to another export format.

27. The system of claim 26, wherein the second program comprises a marketing statistics program.

28. The system of claim 26, wherein the first program comprises a billing program.

29. The system of claim 28, wherein a first thread of the billing event object generator stores the billing event object in an event object queue, and a second thread of the billing event object generator retrieves the billing event object from the event object queue, serializes the billing event object, and stores the serialized billing event object in the billing event generation file.

30. The billing event object generating system of claim 18, wherein a plurality of the billing event object generators are located within a plurality of computers distributed within the network, and the billing event collector centrally retrieves the billing event generation files from the plurality of billing event object generators distributed within the network.

31. The billing event object generating system of claim 18, wherein the billing event collector deserializes the billing event object within the retrieved billing event generation files.

32. A method of handling a billing event in an on-line network generated from a plurality of computer servers within an on-line network, the method comprising the steps of:

providing a class hierarchy of billing events wherein each defined billing event is indicative of a customer computer access to the on-line network;

generating a first billing event object from the billing event class in response to the customer computer accessing a first server computer in the on-line network;

generating a second billing event object from the billing event class in response to the customer computer accessing a second server computer in the on-line network;

storing the second billing event object in a second event object queue,

removing the second billing event object from the second event object queue,

serializing the second billing event object, and

storing the serialized second billing event object in a local storage in the second server computer; and

collecting by an event collecting computer the first and second billing event objects generated on said first and second server computers in the on-line network into a storage, including collecting the serialized second billing event object from the local storage.

33. The method of claim 32, wherein the first and second servers are not co-located within the on-line network, and the event collecting computer centrally collects the billing event objects.

34. The method of claim 32, further comprising the step of storing the first billing event object in a first event object queue.

35. A computer-readable medium having computer-executable instructions for a method of handling a billing event in an on-line network, the steps comprising:

providing a class hierarchy of billing events wherein each defined billing event is indicative of a customer computer access to the on-line network;

generating a billing event object from the billing event class in response to the customer computer accessing a server computer in the on-line network; and

serializing and collecting the billing event object generated on said server computer in the on-line network into a storage.

36. The computer-readable medium of claim 35, wherein the class hierarchy includes a connect event.

37. The computer-readable medium of claim 35, wherein the class hierarchy includes a download event.

38. The computer-readable medium of claim 35, further comprising the step of storing the billing event object into an event object queue.

39. The computer-readable medium of claim 38, wherein collecting the billing event object into a storage includes the steps of removing the billing event object from the event object queue and serializing the billing event object.

40. A computer-readable medium having computer-executable instructions for a method of handling a billing event in an on-line network generated from a plurality of computer servers within an on-line network, the steps comprising:

providing a class hierarchy of billing events wherein each defined billing event is indicative of a customer computer access to the on-line network;

generating a first billing event object from the billing event class in response to the customer computer accessing a first server computer in the on-line network;

generating a second billing event object from the billing event class in response to the customer computer accessing a second server computer in the on-line network;

storing the second billing event object in a second event object queue,

removing the second billing event object from the second event object queue,

serializing the second billing event object, and

storing the serialized second billing event object in a local storage in the second server computer; and

collecting by an event collecting computer the first and second billing event objects generated on said first and second server computers in the on-line network into a storage, including collecting the serialized second billing event object from the local storage.

41. The computer-readable medium of claim 40, wherein the first and second servers are not co-located within the on-line network, and the event collecting computer centrally collects the billing event objects.

42. The computer-readable medium of claim 40, further comprising the step of storing the first billing event object in a first event object queue.