Event logging system and method for logging events in a network system

• US 5,857,190 A
• Filed: 06/27/1996
• Issued: 01/05/1999
• Est. Priority Date: 06/27/1996
• Status: Expired due to Term

• Current Assignee: Rovi Technologies Corporation (Adeia Inc.)
• Original Assignee: Microsoft Corporation
• Inventors: Brown, Matt
• Primary Examiner(s): Black, Thomas G.
• Assistant Examiner(s): MIZRAHI, DIANE D
• Application Number:
  US08/675,463
• Time in Patent Office: 922 Days
• Field of Search: 707/10, 707/104, 707/103, 348/1, 348/6, 348/39, 348/10, 348/7, 348/12, 348/13, 348/34, 348/153, 273/269, 380/10, 380/23, 343/13, 395/200.49, 455/5.1, 379/93.19
• US Class Current: 1/1
• CPC Class Codes: G06F 11/3476 Data logging G06F11/14, G06F11/2205 take precedence
• CPC Class Codes: H04N 7/17318 Direct or substantially direct transmission and handling of requests

Abstract

An event logging system is provided for an interactive entertainment network system having a headend or content provider interconnected via a distribution network to multiple user interface units. Each user interface unit has an event evaluator to determine whether an event is a loggable event. The user interface unit can be dynamically reconfigured to choose different groupings of events for logging. Loggable events are reported to an event log manager at the headend over the distribution network. The event logging system is designed so that the user interface unit does not need to know the exact location of the event log manager at the headend. The event log manager selects an appropriate database to store event information pertaining to the reported event. The database selection is based upon the kind of event being logged. The database might be local at the headend or remote therefrom. The event logging system is also designed to permit the operator to reconfigure where the events are actually logged to promote flexibility in resource allocation.

Claims

1. An event logging system for use in a network system having a content provider interconnected via a distribution network to at least one user interface unit, individual events being detected at the user interface unit, the event logging system comprising:

an event evaluator resident at the user interface unit to determine whether an event occurring at the user interface unit is a loggable event or a non-loggable event; and

an event log manager resident at the content provider to manage where events are to be logged, the event evaluator reporting the loggable event via the distribution network to the event log manager at the content provider.

2. An event logging system as recited in claim 1, wherein the event evaluator does not record the non-loggable events.

3. An event logging system as recited in claim 1, wherein the event evaluator is configured to be selectively enabled or disabled.

4. An event logging system as recited in claim 1, wherein the event evaluator reports a degree of importance of the loggable event.

5. An event logging system as recited in claim 1, wherein the event is categorized into one of three classes selected from a group comprising:

(1) system events for reporting on the interactive entertainment network system, (2) security events that relate to security aspects of the interactive entertainment network system, and (3) application events that pertain to operation of the user interface unit.

6. An event logging system as recited in claim 1, further comprising:

a buffer to temporarily batch multiple loggable events; and

the event evaluator being configured to periodically report the batched loggable events to the event log manager.

7. An event logging system as recited in claim 1, further comprising:

multiple servers at the content provider; and

the event log manager is configured to operate on a set of one or more of the servers and can be dynamically reconfigured to operate on a different set of one or more servers.

8. An event logging system as recited in claim 1, further comprising a database at the content provider to store information pertaining to the event reported by the event evaluator.

9. An event logging system as recited in claim 1, further comprising:

multiple databases for storing different kinds of event information;

a relational list at the content provider to relate the kinds of event information with the appropriate databases; and

the event log manager using the relational list to select the appropriate database for storing information pertaining to the event reported by the event evaluator at the user interface unit.

10. An event logging system as recited in claim 9, wherein at least one of the multiple databases is resident at the content provider and at least one of the multiple databases is situated remotely from the content provider.

11. An event logging system as recited in claim 1, further comprising:

a processor resident at the user interface unit; and

the event evaluator comprising a log application program interface (log API) which executes on the processor.

12. An event logging system as recited in claim 1 1, further comprising:

a server resident at the content provider; and

the event log manager comprising a callable logging service object that can be called by the log API using a remote procedure call (RPC) over the distribution network.

13. An event logging system for use in a network system having a content provider interconnected via a distribution network to at least one user interface unit, individual events being detected at the user interface unit, the event logging system comprising:

an event log manager resident at the content provider to manage where events are to be logged;

the user interface unit being configured to report events to the event log manager over the distribution network; and

a forwarding registry that is utilized by the user interface unit to locate the event log manager at the content provider, the forwarding register being configurable to change where events are reported at the content provider.

14. An event logging system as recited in claim 13, wherein the forwarding registry is configured so that the events are reported to a location other than the event log manager.

15. An event logging system as recited in claim 13, further comprising:

multiple servers at the content provider, the event log manager being supported by one or more of the servers; and

the forwarding register being utilized by the user interface unit to report the events to the event log manager regardless of where the event log manager is physically located on the one or more servers.

16. An event logging system as recited in claim 13, further comprising an event evaluator resident at the user interface unit to determine whether an event occurring at the user interface unit is a loggable event to be sent to the event log manager.

17. An event logging system as recited in claim 13, further comprising:

multiple databases for storing different kinds of event information;

a relational list at the content provider to relate the kinds of event information with the appropriate databases; and

the event log manager using the relational list to select the appropriate database for storing information pertaining to the event reported by the event evaluator at the user interface unit.

18. An event logging system as recited in claim 17, wherein at least one of the multiple databases is resident at the content provider and at least one of the multiple databases is situated remotely from the content provider.

19. An event logging system for use in a network system having a content provider interconnected via a distribution network to at least one user interface unit, individual events being detected at the user interface unit, the event logging system comprising:

an event log manager resident at the content provider to manage where events are to be logged;

the user interface unit being configured to report events to the event log manager over the distribution network;

multiple storage locations to record event information pertaining to the events reported to the content provider from the user interface unit; and

the event log manager being configurable to select a storage location from among the multiple storage locations.

20. An event logging system as recited in claim 19, further comprising:

a relational list that relates different kinds of event information with corresponding storage locations; and

the event log manager using the relational list to select the appropriate database for storing the event information.

21. An event logging system as recited in claim 19, wherein at least one of the multiple databases is resident at the content provider and at least one of the multiple databases is situated remotely from the content provider.

22. An event logging system as recited in claim 19, further comprising an event evaluator resident at the user interface unit to determine whether an event occurring at the user interface unit is a loggable event to be sent to the event log manager.

23. An event logging system for use in a network system, the event logging system comprising:

a memory resident at a computing unit;

an event configuration manager capable of writing an event filter criteria to the memory resident at the computing unit, the event filter criteria being used to determine whether an event is a loggable event or a non-loggable event; and

an event evaluator resident at the computing unit and operably coupled to access the memory, the event evaluator being configured to determine whether an event should be logged in accordance with the event filter criteria stored in the memory.

24. An event logging system as recited in claim 23, wherein the event configuration manager is located remotely from the computing unit and writes the event filter criteria to the memory over the distribution network.

25. An event logging system as recited in claim 23, wherein:

the event configuration manager writes a new event filter criteria to the memory independently of the event evaluator; and

the event evaluator evaluates subsequent events using the new event filter criteria stored the memory.

26. An event logging system for use in a network system having a content provider interconnected via a distribution network to at least one user interface unit, individual events being detected at the user interface unit, the event logging system comprising:

a processor resident at the user interface unit;

a log application program interface (log API) executing on the processor to determine whether an event is a loggable event;

a server resident at the content provider;

a logging service executing on the server, the logging service being configured as an callable object with a defined interface, the logging service object being callable by the log API using a remote procedure call (RPC) over the distribution network;

the log API being configured to call and bind to the logging service object and to report loggable events to the logging service object;

multiple databases to store event information pertaining to different kinds of loggable events;

the logging service object being further configured to select an appropriate database from among the multiple databases to store event information for a loggable event reported by the user interface unit; and

a database management application program interface executing on the server to route the event information from the logging service object to the appropriate database selected by the logging service object.

27. An event logging system as recited in claim 26, further comprising:

a memory resident at the user interface unit to store an event filter criteria, the log API using the event filter criteria to determine whether an event is a loggable event.

28. An event logging system as recited in claim 27, further comprising:

an event configuration manager separate from the user interface unit which accesses the memory at the user interface unit to write the event filter criteria into the memory.

29. An event logging system as recited in claim 26, further comprising:

multiple servers resident at the content provider, the logging service object being executable on one or more of the servers.

30. An event logging system as recited in claim 26, further comprising:

a source string store that identifies an appropriate database from among the multiple databases for a given kind of loggable event reported by the log API; and

the logging service object utilizing the source string store to select the appropriate database for storing event information pertaining to that loggable event.

31. An event logging system as recited in claim 26, wherein at least one of the multiple databases is resident at the content provider and at least one of the multiple databases is situated remotely from the content provider.

32. An event logging system as recited in claim 26, wherein log API is configured to perform a report function to report a loggable event to the logging service object, the report function including parameters selected from a group comprising:

(1) identity of user interface unit;

(2) class of event;

(3) importance level of event; and

(4) data.

33. A method for logging an event in a system having a content provider interconnected via a distribution network to at least one user interface unit, individual events being detected at the user interface unit, the method comprising the following steps:

determining, at the user interface unit, whether the event is a loggable event;

reporting loggable events to the content provider;

selecting a storage location to store event information pertaining to the loggable events; and

storing the event information at the storage location.

34. A method as recited in claim 33, further comprising the following additional steps:

reporting the loggable events to an event log manager provided at one location within the content provider;

moving the event log manager from the one location to a new location within the content provider; and

subsequently reporting the loggable events to the event log manager at the new location.

35. A method as recited in claim 33, further comprising the following additional steps:

storing an event filter criteria at the user interface unit; and

the determining step comprises the step of examining the event in accordance with the event filter criteria to decide whether the event is a loggable event.

36. A method as recited in claim 33, further comprising the step of reporting identification information pertaining to the user interface unit.

37. A method as recited in claim 33, further comprising the following additional steps:

batching multiple loggable events at the user interface unit; and

periodically reporting the loggable events that are batched.

38. A method as recited in claim 33, wherein:

the loggable events are reported to an event log manager that is implemented as a callable object executing at the content provider; and

the reporting step comprises the step of calling the object using a remote procedure call over the distribution network.

39. A method as recited in claim 33, further comprising the following additional steps:

correlating different kinds of event information with associated storage locations; and

selecting a suitable storage location in accordance with a kind of event information to be stored.

40. A method as recited in claim 39, further comprising the additional step of reassociating the different kinds of event information with different storage locations to alter where the event information is stored.

41. A method as recited in claim 33, wherein the storing step comprises storing the event information pertaining to some loggable events at a storage location that is local to the content provider and the event information pertaining to other loggable events at a storage location that is remote from the content provider.

42. A method for logging an event in a network system having first and second computing units interconnected via a network, the method comprising the following steps:

capturing an event at a first computing unit;

establishing a forwarding registry to direct where the event should be reported at the second computing unit;

reporting the event captured at the first computing unit to a place at the second computing unit that is located by the forwarding registry; and

changing the forwarding registry to alter the place at the second computing unit to which the event is reported.

43. A method as recited in claim 42, further comprising the additional step of determining, at the first computing unit, whether the event is a loggable event.

44. A method for logging an event in a network system having first and second computing units interconnected via a network, the method comprising the following steps:

capturing an event at the first computing unit;

reporting the event to the second computing unit;

selecting a storage location from a group of storage locations to store event information pertaining to the event; and

changing the group of storage locations to change where the event information is stored.

45. A method as recited in claim 44, further comprising the additional step of determining, at the first computing unit, whether the event is a loggable event.

46. A method as recited in claim 44, further comprising the following additional steps:

correlating different kinds of event information with associated ones of the storage locations; and

selecting a suitable storage location in accordance with a kind of event information to be stored.

47. A method as recited in claim 44, wherein the group of storage locations contains storage locations local to the second computing unit and storage locations remote from the second computing unit.

48. A method for initializing an event logging system used in a system having a server unit interconnected via a network to at least one client unit, the method comprising the following steps:

(a) storing an event filter criteria in a memory resident at the client unit;

(b) determining, at the client unit, whether the event is a loggable event based upon the event filter criteria stored in the memory; and

(c) changing the event filter criteria in the memory to a new event filter criteria so that subsequent events are analyzed under step (b) using the new event filter criteria.

49. A method as recited in claim 48, wherein the changing step (c) comprises remotely changing the event filter criteria from a remote location by transmitting the new event filter criteria over the distribution network.

50. An event logging system for use in a network system having a server interconnected via a network to at least one client, individual events being detected at the client, the event logging system comprising:

an event evaluator resident at the client to determine whether an event occurring at the client is a loggable event or a non-loggable event based upon an event filter criteria; and

the event evaluator being reconfigurable to change the event filter criteria.

51. An event logging system as recited in claim 50, further comprising a forwarding registry that is utilized by the client to locate a place on the server to report the loggable events, the forwarding register being configurable to change where events are reported at the server.

52. An event logging system as recited in claim 51, further comprising:

multiple storage locations at the server to record the loggable events; and

an event log manager, resident at the server, which is configurable to select a storage location from among the multiple storage locations.

53. A method for logging an event in a system having a server interconnected via a network to at least one client, individual events being detected at the client, the method comprising the following steps:

determining, at the client, whether the event is a loggable event based upon an event filter criteria; and

reconfiguring the event filter criteria to change which events are consider loggable events.

54. A method as recited in claim 53, further comprising the following steps:

reporting loggable events to a location at the server that is identified by a forwarding registry; and

changing the forwarding registry to report the loggable events to another location at the server.

55. A method as recited in claim 54, further comprising the following steps:

selecting a storage location from among multiple storage locations at the server to record the loggable events; and

changing from one storage location to another to store the loggable events.

56. A computer-readable medium used in an event logging system having a server interconnected via a network to at least one client, the computer-readable medium storing computer-executable instructions for performing the following steps:

storing an event filter criteria at the client;

determining, at the client, whether an event is a loggable event based upon the event filter criteria; and

changing the event filter criteria to a new event filter criteria so that subsequent events are analyzed using the new event filter criteria.

57. A computer-readable medium as recited in claim 56, further comprising computer-executable instructions for performing the following steps:

reporting loggable events to a location at the server that is identified by a forwarding registry; and

changing the forwarding registry to report the loggable events to another location at the server.

58. A computer-readable medium as recited in claim 57, further comprising computer-executable instructions for performing the following steps:

selecting a storage location from among multiple storage locations at the server to record the loggable events; and

changing from one storage location to another to store the loggable events.