Patent Grant
8001185
The present invention relates in general to enterprise information systems. More particularly, the present invention relates to methods and apparatus for optimizing the delivery of data to a device.
Timely intelligence is critical to proper business decision making. Collecting and quickly analyzing information, however, is often difficult. In a dynamic marketplace, delayed delivery of intelligence can reduce both its reliability and relevancy. Substantial delays can even make the information, often acquired at considerable cost, completely worthless.
Intelligence is often extracted from OLTP applications and from specialized databases, called operational data stores, OLTP (online transaction processing) applications are those enterprise systems that manage a company's basic transactions, such as order entry and billing systems. Since they are commonly optimized for reading and writing, and not for querying, extracting information from an OLTP application can be sufficiently complex to require additional user training. Furthermore, while operational data stores generally archive OLTP information in a format for querying, they also generally do not maintain important historical information. For instance, an operational data store may store a current checking account balance, but not the individual daily balances over the previous month.
In addition, the queries themselves often take substantial time to execute, producing only static snapshots of the information. Observing the dynamic aspect of changing information is therefore difficult. A possible solution may be to sequentially execute and aggregate a series of queries. However, this solution can be both inefficient and ineffective, since manual manipulation still often delays the information delivery. That is, these queries must be first manually aggregated and summarized, before intelligence reports can be generated and delivered.
ETL (extraction, transformation, and loading) systems help by extracting, transforming, and aggregating the information. But latency inherently found in most distributed networks, coupled with considerable manual intervention that ETL systems often require, mean that critical information can still be received late.
Automatic notification is a possible solution. Many analytical products such as business intelligence (BI) and online analytical processing (OLAP) systems are capable of monitoring, scheduling, and broadcasting alerts via email or pager. These systems, however, cannot generally assure that the intended recipient promptly receives and reads the message. This presents a significant problem for time-sensitive information, where minutes or even seconds can make a difference.
To facilitate discussion,
OLTP (online transaction processing) applications 152 are commonly coupled to each other, as well as to other enterprise applications, through a dedicated messaging and queuing application (MQ), such as IBM's MQSeries. MQ provides an efficient communication channel for these applications, by storing and forwarding data messages, in a manner that is similar to email.
Commonly coupled to each OLTP application 152 is operational data store 154, such as an Oracle database. Through an API (application programming interface), transactional data can be transferred between the OLTP application and the database. Operational data store 154 consolidates that data from multiple sources and provides a near real-time, integrated view of volatile, current data. Since its purpose is to provide integrated data for operational purposes, operational data store 154 primarily has add, change, and delete functionality.
In order to conduct meaningful analysis, this information is often further placed in a more stable environment, optimized for random querying. ETL system 155 extracts the information from the appropriate data store 154, transforms and combines the data based on pre-defined constraints, and subsequently loads the data into data warehouse 156. A popular ETL technique, developed by Sagent, is the use of data flows.
Data flows are a series of rule-enabled transformations that are connected in data pipelines. They handle the tasks of joining, merging, comparing and splitting data and permit the separation of data into different logic paths, each of which can be further combined and split off to create more complex transformation sequences.
ETL data extractions often occur by either a bulk or a trickle method. In the bulk method, periodic snap shots of data in operational data store 154 are extracted and uploaded into data warehouse 156. This commonly occurs as a large batch file scheduled during a low system utilization period. In the trickle method, changes in operational data store 154 are continuously uploaded, or “trickled” into data warehouse 156. These updates are therefore frequent, smaller, and more current than in the bulk method. As in the case of OLTP 152 systems, ETL 155 can also use the MQ for data extraction.
Once the data is in data warehouse 156, it is available for OLAP 158 (online analytical processing). OLAP enables trained users to perform ad hoc analysis of data in multiple dimensions, such as with an OLAP cube. OLAP cubes provide multi-dimensional views of data, querying, and analytical capabilities. Furthermore, many OLAP products can schedule, run, publish, and broadcast reports, alerts and responses over the network, email, or personal digital assistant. Users often access OLAP 158 by thin client 162. Thin clients are applications that generally are integrated into the underlying client device, and generally require minimal modification. For instance, a thin client can be browser with a Macromedia Flash module installed.
Although OLAP analysis can provide valuable insight about business operations, critical information is often received late, even with automated reporting. Automated OLAP reporting often only has access to the information within data warehouse 156, which can be several processing stages behind OLTP 152. This delay can be substantial, reducing the information's value. Furthermore, these reports are often only static snapshots of information in data warehouse 156.
For example, a NASDAQ broker places an order into an OLTP 152 application called an electronic communications network, or ECN. The ECN matches customer buy and sell orders directly through the computer. In this case, an order to buy 100 shares of ABC at $18.75 was entered. This open order is stored in the ECN operational data store 154, subsequently extracted by ETL 155, and analyzed by OLAP 158. If the buy order amount is the then highest in the ECN, OLAP 158 forwards the information to thin client 164, NASDAQ quote montage, where it is immediately displayed on the familiar stock market ticker tape. And although this system delivers stock information to individual brokers with reasonably small latency, it is also not easily modified. The NASDAQ application is custom designed for the specific purpose of enabling stock trading. As such, it would be difficult to display additional data on the stock ticker, such as non-financial information, without substantial additional programming.
In view of the foregoing, there is desired a method and apparatus for optimizing the delivery of data to a device, in which relevant information is received in a timely manner, and in which that data is rendered in a dynamic format.
The invention relates, in one embodiment, to method for optimally monitoring a set of data elements for an event. The method includes determining a set of data elements, each of which further comprises a state. An event is commonly a change in this state. The method further includes creating a rule for monitoring the event, wherein the rule comprises an event identification portion resident on a first computer and an action portion resident on a second computer. The method also includes monitoring the set of data elements for the event based, in part, on the event identification portion, and determining if the event has occurred. If so, the method further includes sending the set of data elements to the second computer. The method also includes executing a set of actions, based in part, on the action portion. Thereafter, the method further includes monitoring the set of data elements based, in part, on the rule.
In another embodiment, the invention relates to an apparatus for optimally monitoring a set of data elements for an event. The apparatus includes a means for determining a set of data elements, each of which further comprises a state. An event is commonly a change in this state. The apparatus further includes a means for creating a rule for monitoring the event, wherein the rule comprises an event identification portion resident on a first computer and an action portion resident on a second computer. The apparatus also includes a means for monitoring the set of data elements for the event based, in par, on the event identification portion, and a means for determining if the event has occurred. If so, the apparatus further includes a means for sending the set of data elements to the second computer. The apparatus also includes a means for executing a set of actions, based in part, on the action portion. Thereafter, the apparatus further includes a means for monitoring the set of data elements based, in part, on the rule.
These and other features of the present invention will be described in more detail below in the detailed description of the invention and in conjunction with the following figures.
The present invention is illustrated by way of example, and not by way of limitation, in the figures of the accompanying drawings and in which like reference numerals refer to similar elements and in which:
The present invention will now be described in detail with reference to a few preferred embodiments thereof as illustrated in the accompanying drawings. In the following description, numerous specific details are set forth in order to provide a thorough understanding of the present invention. It will be apparent, however, to one skilled in the art, that the present invention may be practiced without some or all of these specific details. In other instances, well known process steps and/or structures have not been described in detail in order to not unnecessarily obscure the present invention. The features and advantages of the present invention may be better understood with reference to the drawings and discussions that follow.
In accordance with one embodiment of the present invention, an active data architecture is advantageously employed to facilitate the presence-aware delivery of timely data. That is, determining the type of device available to the user, and delivering the information in a format within the device's capabilities. In accordance with another embodiment of the present invention, information can be continuously extracted from data sources without the need for manual queries, or additional user training. In accordance with another embodiment of the present invention, information may be dynamically delivered in order to render streaming real-time or near real-time data and/or analytical results, whether graphically, textually, audibly, or otherwise.
Referring now to
As in
Through the use of browser technology, such as DHTML, thin client 114 and a rich client 282 provide the user with enhanced visualization functionality, such as the capability to graphically render streaming data. Thin client 114, in one embodiment, is called active viewer, and comprises a browser. Rich client 282, in another embodiment, is called active viewer pro, and comprises a browser with additionally installed software. DHTML is a combination of HTML, style sheets, and scripts, and allows web-pages to be animated. In addition, rich client 282 further allows for enhanced functionality, such as pen-based user input, secure instant messaging, robust printing capability, and the use of skins. Skins are configuration files that allow modification of the browser appearance. Messaging client 115, such as a SMS cell phone, or an instant messaging program, such as Yahoo Messenger or Windows Messenger, provides alert capability. These alerts, as well as static reports, can also be received through thin client 114, such as a browser. Other 280 represents those enterprise applications that have been programmatically coupled to active data platform 210, as a client.
In one embodiment, client applications in client layer 142 can reside on a Tablet PC. The Tablet PC represents the evolution of the business notebook personal computer. It marks a new direction for notebook PCs, adding pen-based technologies to existing notebook functionality and enabling Windows XP-compatible applications to take advantage of various input modes, such as pen and voice-based data. The Tablet PC will be among the most versatile PCs ever made, with high-powered and efficient processors, lightweight designs, and, for man, built-in wireless capability. All Tablet PCs will have keyboards, some permanently attached and others detachable. But the Tablet PC is more than just a great notebook. The real value of the Tablet PC is that it makes it possible for information workers to bring the power of their business PC into more places than ever before, and they can do it with the same software they use on their office PC or notebook today.
For example, betting transactions would be normally stored in a casino's game transaction system. Wanting to be extra-attentive to high-rollers, a casino would configure the active data platform to observe for any customer whose betting exceeds a specified threshold, upon which an alert would be sent to the closest pit boss. The pit boss would locate these customers and personally oversee that exceptional customer service was provided.
Active data cache 256 is the core repository for the active data platform. Unlike traditional databases, such as operational data store 104 and data warehouse 106, active data cache 256 stores data in a de-normalized format. Normalization is the practice of optimizing the database structure into multiple tables, eliminating data redundancy and improving sealability and maintainability.
Since active data cache 256 is primarily focused on automatic reporting, and not on querying, it generates substantially de-normalized tables representing each report or data stream. By logically placing these de-normalized tables near client layer 142, in a non-obvious fashion, fewer processing stages are required and latency is substantially reduced.
Database tables are not commonly de-normalized, since data is duplicated. In general, duplicated data tends to increase the likelihood of data corruption during updates. That is, multiple separate entries no longer match each other. Furthermore, de-normalized tables tend to be more difficult to query than normalized tables, since each individual data record may be substantially larger, and hence take longer to search. This is even more so if the table is not properly indexed. However, since ad-hoc querying is not a substantial requirement, and table joins are not necessary, normalization enables database tables within active data cache 256 to be optimized for the efficient creation of pre-defined reports and alerts. In one embodiment, a single de-normalized table is the source for each report.
Active design process 290 is powerful, intuitive suite of applications that allow a user to create rules, map onto message queues, manage security, define data objects, and configure enterprise link 254 processes and sources, based on simple drag-and-drop operations for the data streams, reports, and alerts. In addition to active design process 290 in active data layer 241, there is a corresponding active design process client in client layer 142, such as a web browser. In one embodiment, active design process 290 comprises an application entitled architect. Unlike traditional real-time business intelligence applications, active design process 290 allows a user to dynamically add new data sources, or create new transformations and reports, without changing the system as a whole. That is, unlike the NASDAQ stock trading example previously shown, which is not easily modified, active design process 290 can easily tailor the active data platform to new applications and changing corporate infrastructures.
Active report engine 274 converts the raw information in active data cache 256 into charts, tables, and graphs for display on a device in the client layer 142. Active studio 291 is a presentation editor that allows a user to easily create and format specific graphical and textual active views of data, based on pre-defined templates. Common views are tables, pie graphs, bar graphs, line graphs, scatter graphs, columnar reports, form reports, geographic (map) views, crosstabs, and Excel integration. For instance, a user can create an hourly report in which gambling customers are aggregated into different groups based on the value of their accumulated betting that day. The user selects a bar graph for the report, and changes the fill color and font type to the user's preference. These views can be substantially active, changing in near real time as the underlying data changes, or can be static, like a printed report.
Event engine 257 monitors the information in active data cache 256 for pre-determined changes, or events. Once an event occurs, such as a rising temperature in a chemical processing plant, message center 272 is notified, subsequently forwarding the appropriate message to messaging client 115, thin client 114, or rich client 282.
In one embodiment, message center 272 tracks the presence of client devices, as well as the status of users themselves, in order to substantially assure message delivery. This is in contrast to traditional messaging systems that cannot determine if messages are, in fact, delivered to intended recipients. Presence determines if the device is available on the network. Status determines if the intended recipient is available to read and respond to the instant message. Common status categories include descriptive information, such as “out to lunch”, “busy”, “away from desk”, “important meeting”, etc. For instance, the device may be turned on and available, but the intended recipient is in an important meeting and does not wish to be disturbed. The intended recipient sets the status to “important meeting” in order to notify message center 272, as well as any other subscribed user, that he will probably not respond to the alert until after the meeting. Message center 272 would then choose an alternative available recipient, based on an established notification rule.
For example, a casino's active data platform attempts to notify the nearest pit boss of a particularly prolific gaming customer. However, since the pit boss has a “busy” status, the casino manager is alerted instead, and subsequently walks over to greet the customer.
Enterprise security system 258 represents a company's existing security infrastructure, such as Steel-Belted Radius by Funk Software. Since operational information may be sensitive, active data cache 256 can be integrated into enterprise security system 258. In this way users are authenticated before information is transmitted to client layer 142 devices.
Event engine 257 is further comprised of four logical components: event generator manager 428, rules manager 408, accountability manager 410, and actions manager 412. Event generator manager 428 maintains the state information of monitored events 402 for rules manager 408. Rules manager 408 is the primary event handler for the active data platform. Accountability manager 410 monitors the delivery status of all reports and alerts. And, actions manager 412 initiates actions based on input from the actions module 434 of the rules manager 408.
Event generator manager 428 maintains state information of monitored events 402 for rules manager 408. Constraint module 426 specifies the parameters that must be satisfied before evaluating an event and/or a condition and/or before applying the rule. Conditions module 424 maintains information for the corresponding conditions module 432 in rules manager 408. It further specifics attributes relevant to the specific event, other than constraints, which must be satisfied before the action associated with the rule may be taken. Events module 425 maintains event information for the corresponding events module 430 in rules manager 408.
Rules manager 408 further includes three components in order to manage active data: an events module 430, a conditions module 432, and an actions module 434. Events module 430 monitors all generated events 402 within the active data platform. Conditions module 432 filters out non-relevant events, and forwards the information to actions module 434, which in turn, initiates new system events based on criteria within rule sets 256. For example, all betting transactions are sent as events to event generator manager 428, which in turn sends the information to the events module 430 of rules manager 408. The conditions module 432 is configured to subsequently filter out all but the blackjack events. The actions module, based on rules 256, then creates an internal system event to instruct the active reports engine 274, as shown in
Accountability manager 410 monitors the delivery status of all reports and alerts. It further includes an unaccounted notifies module 438, and a report engine tie module 436. The unaccounted notifies module 438 maintains the status of undelivered alerts and reports. That is, unaccounted notifies module 438 determines if a recipient cannot be reached, subsequently forwards a delivery-incomplete message to rules manager 408. Report engine tie 436 monitors for successfully received reports and alerts, and subsequently forwards a delivery-complete message to rules manager 408. For example, a receipt notification status message is received in accountability manager 410, which is subsequently processed. If the receipt notification status message comprises an acknowledgment, report engine tie module 436 further processes the message and forwards the information to rules manager 408. However, if an acknowledgment is not received, unaccounted notifies module 438 processes the message and forwards the information to rules manager 408, which in turn allows active data cache to escalate alerts and reports to alternate recipients, based on status and presence, should the original recipient be unavailable.
Actions manager 412 initiates events and actions based upon input from the actions module 434. It further includes a notification module 416, a generate event module 414, a run a plan module 418, a web service/MQ module 420, and an others module 422. Notification module 416 forwards any report and alert non-delivery messages to unaccounted notifies module 438. Generate event module 414 generates system events initiated by actions module 434 in rules manager 408. Run a plan module 418 executes script based on rules 256. Web service/MQ module 420 provides an interface to third-party web-services based on WSDL (web-service description language), as well as message queue applications. Others module 422 is an API that allows additional modules to be later added.
Rich client 282 is comprised of a main application 536, a rendered reports 540 component, and a re-notify applet 506 component. Main application 536 provides the core environment for client interface to the active data cache 256. It comprises several functional components that can dynamically render incoming data streams from active data cache 256, and locally create reports, such as report builder 538. Rendered reports 540 functions as a viewer to display reports from active data cache 256 which already have been assembled. Re-notify applet 506 displays notification messages to the user.
In a non-obvious fashion, rich client 282 substantially maintains an open TCP-IP connection to active data cache 256, through the execution of blocking HTTP request in a second open browser window. Internet browsers normally implement HTTP, an asynchronous protocol that uses multiple short-lived synchronous TCP-IP connections to render the objects on a web page. For instance, a connection is opened, a picture is rendered, and the connection is closed. However, in the current invention, a web server periodically sends keep-alive messages to the second open browser window, in order to prevent a TCP-IP connection timeout. Through the use of this code, a TCP-IP connection is kept open, allowing data to be sent in a substantially continuous way to rich client 282, without having first to refresh the browser window. Thus, the dynamic rendering process in the primary browser window is more readily controlled. For example, the following JavaScript code may be executed by the second browser window:
viewsetID indicates the viewset to which the active data applies, whereas strXML refers to an XML document describing new data. Line 1 indicates to the browser that the following section need not be rendered since it is a script section. The execution of line 2 causes the report in the main application (active studio or active viewer) browser to change. The execution of line 3 removes the script from the page. And line 4 indicates to the browser that the script section has ended.
Active data cache further comprises functional components that facilitate the generation of a report. These are: a report execution component 522, a view execution component 524, a report builder component 528, a rule builder component 530, a modifier builder component 532, data object builder component 534, a structured data supplier component 526, and a message center gateway 536.
Report execution 522 creates, caches, and then forwards specific reports based on configuration, to either rendered reports 540 for report builder 538. View execution 524 likewise creates and forwards views to report builder 538. Views are data objects that may be filtered. Report builder 528 pre-processes extracted information from multiple sources, and transforms the aggregated data into a format optimized for use in multiple reports. Rule builder 530 pre-processes stored rules from multiple rule caches for use in the generation of multiple reports. Modifier builder 532 pre-processes intermediate information transformations, such as additional metrics that the user wishes calculated and reported. Data object builder 534 pre-processes data objects into optimized formats for report execution component 522. Structured data supplier 526 forwards external pre-processed data to report builder 528.
API layer 605 provides a uniform application interface for system generated events, such as notification request 608, administration request 606, and presence request 604. Presence and notify component 612 provides the main messaging infrastructure for the active data platform. It insures that reports and alerts are properly routed to intended recipients. Local user information 626 maintains a local cache of user profile information, such as names, passwords, and delivery preferences.
Rich client interface 614 is further coupled to rich client 282, which provides the user with enhanced visualization functionality, such as the capability to graphically render streaming data. Thin client interface 616 is coupled to thin client 112, which further comprises agent application 660. Since thin client 114 is commonly a browser without presence functionality, agent 660 notifies presence and notify component 612 that a given report or alert is being viewed. Agent 660 is commonly an Active X component or a java applet. Email interface 618 is further coupled to email server 632, such as an SMTP server, which forwards messages to email client 115a. IM interface is further coupled to IM client manager 628 which sends a notification request 630 to IM client 115b. Instant messaging (IM) is a means for sending small, simple messages that are delivered immediately to online users. It differs from email primarily in that its primary focus is immediate end-user delivery. Through an IM client application, a user can discover and immediately begin a text conversation, or chat session. Common public instant message systems include AOL Instant Messenger, MSN Messenger, Yahoo! Messenger, Microsoft Exchange 2000 IM, and Lotus Sametime.
For example, a casino's active data cache identifies particularly prolific gaming customer. The active data cache forwards a notification request 608 to message center 272. The presence & notify module 626 then determines if the intended user's device is present, and the user is available. If so, message center 272 forwards an alert through IM interface 620 to IM server 630, and finally to IM client 657.
Unlike like the prior art, the active data platform is general purpose, and is substantially customizable by entering new parameters in active design process 290 and the active studio 291, as shown is
Referring now to
The display is divided into three sections, a tab pane 701, a function pane 714, and a display pane 715. Tab pane 701 further allows the user to select one of various functional displays within active studio 304, such as: home 705, my reports 706, shared reports 707, personalize 708, and alerts 709. Home 705 comprises a summarized view of the user's most recent activities. My reports 706 comprises a summarized list of the user's created reports. Shared reports 707 comprises a summarized list of third-part reports to which the user has subscribed. Personalize 708 comprises administrative components that can allow the user to modify report delivery and display parameters. And alerts 709 comprises a summarized list of a user's active alerts.
Function pane 714 displays several functional list boxes within home 705 tab, such as: recent list box 710, new list box 711, list toolbox 712, and actions list box 713. Recent list box 710 displays the user's most recently accessed reports. The new list box 711 displays the user's new reports. The alerts list box 712 displays the user's currently active alerts. And the actions list box 713 allows the user to create and edit reports. Display pane 715 displays the corresponding result of the chose function of function pane 714. In this case, a dynamic financial report comprising a cost bar graph and a percentage change line graph. For example, if a user where to select intraday sales by region in the new list box 711, the corresponding dynamic intraday sales report would be displayed in display pane 715. As sales are booked through out the day, the sales chart would dynamically change as well.
Referring now to
Referring now to
Referring now to
Referring now to
In another aspect of the invention, an Iteration instant messaging & collaboration server is advantageously employed to enable rich secure graphical collaboration in an instant messaging environment. Instant messaging systems commonly monitor the presence of devices, and availability state of users. Presence determines if the IM device is coupled to the given IM network, or at least reachable from the client. Status determines if the intended recipient is available to read and respond to the instant message. Common status categories also include descriptive information, such as “out to lunch”, “busy”, “away from desk”, “important meeting”, etc. For instance, the IM device may be turned on and available, but the user is in an important meeting and does not wish to be disturbed. The user would set the status to “important meeting,” in order to notify other subscribed IM users that he will probably not respond to a text message until after the meeting.
These IM systems, however, commonly lack the capability for graphical peer-to-peer or multi-party collaboration. That is, while short text messages can be sent back and forth in an online chat meeting, there is no comparable means for sharing a graph or report. This would normally have to be compressed and transmitted ahead of time to each recipient, who would each then download, de-compress, and locally store the file. In situations where the underlying data is continuously changing, as temperatures would be in a chemical plant, and impromptu collaboration is desired, pre-mailing a graph would be very impractical, inefficient, and of marginal use to the problem at hand.
Furthermore, public IM systems are not particularly secure. They were originally designed for rapid information text conversations, called chat. IM protocols emerged and were established primarily without supervision from any standard bodies, such as the Internet Engineering Task Force. Subsequently, security was never originally considered and common instant messaging traffic is essentially unencrypted. Just about anyone on the network can secretly monitor a chat conversation.
User manager 811 manages user profile information. Users create profiles based on rules, in which they describe events of which they want to notified. Should such an event occur, user manager 811 notifies message center 272, which in turn contacts the user. Furthermore, user manager 811 selects alternative recipients, if the primary recipient is unavailable, based on user preference and availability status. For instance, user #1 has configured user manager 811 for notification of a specific event, for example a temperature change beyond a certain range. Furthermore, user #1 also wants user #2 to be notified should user #1 be unavailable. Once the event occurs, if user #1 is unavailable, message center 272 attempts to notify user #2. Presence manager 813 monitors for the availability of user devices on the network. For instance, in the previous example, user #1 has a wireless PDA and a SMS phone. If the event occurs, and the PDA is turned-off, an alert is sent to the SMS phone instead.
IIM (Iteration instant messenger) interface 806 provides an interface to the HM client 819-823, an enhanced IM application that allows secure concurrent graphical collaboration and pen-based user input. In general, it is sometimes desirable to implement private instant messaging systems having enhanced capability (including different protocols, encryption capabilities, graphical processing/display capabilities, I/O capabilities, and/or the like) compared to public messaging systems (such as those available from Yahoo™, AOL™, and the like). IIM client is an example of a client in such a private instant messaging system.
IIM client 819-823 commonly connect through active collaboration server 817, which marshals collaboration request from multiple IIM clients, and combines connections whenever possible to improve overall system performance and scalability. Furthermore, active collaboration server 817 synchronizes the text and graphical portions of the IIM session to insure that all users view the same information at substantially the same time.
Active collaboration server 817 further enforces security protocols as implemented by the IIM client, in order to prevent unauthorized interception of the collaboration session. In one embodiment, IIM client 819-823 implements a Triple DES security protocol to protect the collaboration session and insure message integrity. Triple DES is an encryption algorithm whose security is based on a single secret key. Each key is generated (selected at random from all possible keys) for each particular collaboration session.
In another embodiment, only one user in an IIM collaboration session needs authorization to access a given alert or report. By virtue of being authenticated to the session, all other users will receive the alert or report with the security privileges of authorized user, for as long as these users participate in the session.
In addition to IIM interface 806, there is SMTP interface 807 and other IM interface 809. SMTP, or simple mail transfer protocol, is the most common protocol for sending email message on the internet. Through SMTP interface 807, message center 272 can forward email notifications with the event information to email server 815. Unlike IIM client 819-823, however, notification is not automatic. The user must first log onto mail server 815 with a SMTP client 827, such as MS Outlook and download the messages. Likewise, other IM interface 809 represents traditional IM interfaces to currently available IM systems 831, such as AOL Instant Messenger, MSN Messenger, Yahoo! Messenger, Microsoft Exchange 2000 IM, and Lotus Sametime. In contrast to SMTP, notification can be automatic, although communication is generally insecure. Furthermore, graphical collaboration is difficult.
For example, user #1 is a chemical engineer at a petroleum processing plant. He created a profile in user manager 811, in which he wants to be notified of specific events, such as a change in a process temperature beyond a certain range. The event occurs. Message center 272 forwards the notification to active collaboration server 817, through IIM interface 806. Seeing the temperature dynamically change on his device, user # 1 realizes that he wants additional advice from user #2, his manager. Through his IIM device, he instructs message center 272 to initiate a request for collaboration with user #2. Receiving a collaboration request from his subordinate, user #2 accepts the connection. User #1's display is immediately rendered on User 2's device, upon which they collaborate on the matter at hand.
Referring to
For example, user #1 is a network systems engineer monitoring traffic at a company's e-commerce web site. When network congestion reaches a certain point, active report engine 274 generates a report and forwards it to user #1. Realizing that customers are starting to have difficulty placing online orders, user # 1 initiates a connection with user #2, the web site manager, and user #3, the customer service manager. Once both accept, user #1's display is immediately rendered on the other devices, upon which all can collaborate on the matter at hand.
In another embodiment, an instant messaging manager is advantageously employed to rapidly alert intended recipients of data events. Referring to
Rules-based monitoring engine 916 monitors the applications in enterprise systems 902 for pre-defined events. A rule is a pre-defined procedure comprising the event(s) to be monitored, and the subsequent action or transformation that is required. For example, the event can be a specific transaction, a change in a file size, the publishing of a report, etc. Rules U/I 920 is typically graphical application that allows a user to create sophisticated and complex rules, as well as store the rules in the rules db 918 for use by rules based monitoring engine 916. In this case, the subsequent action is an alert.
When a specific event occurs, rules-based monitoring engine 916 forwards an alert to notification engine 924a, which properly formats the alert and transmits it via email system 915a, pager system 915b, or another system through proprietary API 915c. Alerts sent to email system 915a can further contain an embedded link to a report generated by active reports engine 274, as shown if
For example, betting transactions would be normally stored in a casino's game transaction system. Wanting to be extra-attentive to high-rollers, a casino would configure the rules based monitoring engine 916 to observe for any customer whose betting exceeds a specified threshold, upon which an alert would be sent to the closest pit boss with an embedded link to the customer record.
As in
Instant messaging manager 924b properly formats the alert as an instant message and transmits to the intended recipient through one of the various instant message systems 915d-f Unlike notification engine 924a, however, instant messaging manager 924b also monitors the various instant message systems 915d-f for changes in state for any subscribed users. State is comprised of presence and status. Presence determines if the IM device is coupled to the given IM network, or at least reachable from the client. The given instant message system 915d-f normally determines the presence of individual IM clients, and broadcast the information to interested parties, such as the instant messaging manager 924b. Status determines if the intended recipient is able to read and respond to the instant message. Normally whether a recipient is available or not is a true or false question. However, it is common for recipients to customize the unavailable status with further descriptive information, such as “out to lunch”, “busy”, “away from desk”, “important meeting”, etc.
For instance, the IM device can be turned on and available, but the user is in an important meeting and does not wish to be disturbed. The user can set the status to “important meeting” notifying any other subscribed users that he will probably not be able to respond to the instant message until after the meeting. The rules-based monitoring engine 916, realizing that the user will not immediately read the instant message, will choose an alternative present and available user based on a pre-determined notification rule. Rules-based monitoring engine 916 can forward an alert to instant messaging manager 924b for immediate delivery to the intended recipient.
Referring now to
In another embodiment, an event engine is advantageously employed to substantially assure the examination of a report by a user. Many analytical products such as business intelligence (BI) and online analytical processing (OLAP) systems are capable of monitoring, scheduling, and broadcasting alerts via email or pager. These systems, however, cannot generally assure that the intended recipient promptly receives and reads the message. This presents a significant problem for time-sensitive information, where minutes or even seconds can make a difference.
In the current invention, the event engine monitors the state of transmitted alerts in an escalation table. Upon receipt of an alert, the user reviews the received report. This is commonly done by manually browsing for the report, or by clicking an embedded URL contained within the alert. If the user does not review the report within a specified time, the escalation table can further escalate the alert to another user based upon predefined rules. For instance, the alert is transmitted to the user's manager.
Referring to
Enterprise data 140 comprises those enterprise systems that manage a company's basic transactions, such as order entry and billing systems. Active data cache 256 monitors transaction data packets 1104 generated by enterprise data 140. Active data cache 256 further comprises user data manager 1108, which describes user event interest, and monitoring rule manager 1111, that analyzes data packet 1104 for specific events.
Should an event of interest occur, monitoring rule manager 111 forwards a rule fired message 1116 to the rules list manager 1120 of event engine 257. Rules list manager 1120 further comprises the subsequent actions required for the fired rule, such as the transmission of a notification message to a user, the execution of a subsequent rule, or the generation of an accountability escalation event. In this case, notification message 1130 is forwarded to message center 272. Rules list manager 1120 also places an entry into escalation table 1120, describing notification message 1130, the intended recipient, and the time the message was sent. If a report viewed message 1176 is not received within a pre-determined amount of time, a timeout occurs, and escalation table 1122 notifies escalation manager 1138, which in turn executes pre-configured escalation rules, such as notification of a different person or entity, or the calling of a web service.
Upon receiving notification message 1130, user address manager 1142 attempts to find a device address at which the user is currently available. Message center 272 further embeds a link in notification message 1146, through which the user can review the corresponding report from active reports engine 274.
The user subsequently receives notification message 1146 on his device, in this case, through a browser. If not already viewing the report, the user can either locate the report by manually entering information such as a URL, or can also simply click on an embedded link to the report.
Upon receiving a request, report supplier 1168 of report engine 274, generates the report from information in the active reports table 1170, and forwards it to user device 1150. A report viewed message 1176 is also generated and forwarded to escalation table 1122, which in turn deactivates the previous notification message entry.
For example, a large multi-site manufacturing organization, such as Ford Motor Company, would configure the active data platform to monitor manufacturing processing information, such as increasing part reject rates, or outright machine failures. Should a machine failure actually occur, an alert is forwarded to the appropriate manufacturing process engineer. The alert would contain an embedded link to the specific machine's status report, as generated by active reports engine 274. If the process engineer did not review the report within a few minutes (or any time period specified), a new alert would be immediately forwarded to the local plant manager for immediate action.
Referring to
In accordance with one aspect of the present invention, rule evaluation is advantageously distributed in order to improve efficiency. To further elaborate, a rule often comprises multiple interdependent components (i.e., event, constraint, condition, and action) that must be evaluated and acted upon.
The first component of a rule is the event, which specifies the event of interest. An example of an event is when the sales volume exceeds 5,000 units. If the sales volume exceeds 5,000 units, the event component is satisfied.
The second component of a rule is the constraint, which specifies the parameters that must be satisfied before evaluating an event and/or a condition and/or before applying the rule. A constraint is usually provided for efficiency reasons and commonly comprises dates, times, and/or frequencies. For instance, if the specific event described in the event clause (e.g., sales volume in the previous example) does not need to be monitored over the weekend or between certain times or more often than a given frequency, then the constraint clause would instruct the event engine to that effect. Typically a constraint is evaluated to be either true or false. In one embodiment, if the constraint is evaluated to be false by the event engine, the satellite evaluation engine is informed accordingly and does not even need to spend its resources evaluating the event. Advantageously, efficiency is improved.
The third component of a rule is the condition, which further specifies other attributes relevant to the specific event, which attributes must be satisfied before the action associated with the rule may be taken. In the previous example, the condition may be to take action only if the sales volume that fires the event is achieved without any special promotion in place. Generally speaking, all conditions may be thought of as events but not all events are conditions.
The fourth component of a rule is the action, which determines the course of action taken should the event, constraint and/or condition components be satisfied. For instance, the sending of a notification to a specific person may be an action that needs to be taken if, as in the previous example, during a weekday (constraint satisfied), the sales volume exceeds 5,000 units (event satisfied) and the sales volume is achieved without any specific promotion in place (condition satisfied).
It should be noted that a rule typically includes an action but a rule does not require all three other components, i.e., event, condition, and constraint. A rule may have one, two, or three of these components as desired by the rule designer. Furthermore, each of the event, condition, constraint, and action components may be a complex Boolean operation comprising multiple sub-components. A preferred embodiment, however, is a single event component per rule.
For example, an event may be satisfied if sales volume is greater than 5,000 and the total revenue is greater than $10,000 (a Boolean operation of two sub-events).
In order to reduce design complexity, a common solution has been to evaluate and execute these rules in a centralized event engine. It is found, however, that the information that needs to be monitored and evaluated can be found anywhere on the enterprise network. It is often the case that the information that must be monitored and evaluated (e.g., the event or condition) may be distributed in one or more machines (such as servers) remote from the computer executing the centralized event engine. In some cases, only 5% of the information may be relevant to a particular rule. Yet when the rule evaluation is centralized, all the data that needs to be monitored and evaluated must be transmitted across the machine and/or process boundaries for the centralized event engine to perform its rule evaluation task. In a networked environment, the remaining 95% of the information that is needlessly sent represents an inefficient use of scarce network resources and bandwidth, as well as a detriment to performance.
In accordance with one embodiment of the invention, rule evaluation is distributed in one or more satellite evaluation engines local to or closer to the origin of the monitored information. The evaluation is distributed in satellite evaluation engines that are in communication with an event engine. Distributed rule evaluation allows the evaluation of a rule to take place with reduced bandwidth usage and delay. Since active data and the timely report/notification responsive to active data are important aspects of the active data platform, minimizing delay is an important consideration, and the distributed evaluation mechanism substantially furthers that goal.
To facilitate the implementation of distributed rule evaluation, it is highly preferable that a universal rule syntax be developed that allows the event engine to analyze any given rule and decides which portion of the rule should be distributed and which portion of the rule should be processed by the centralized event engine.
In accordance with one embodiment of the invention, a rule syntax is developed in which the four components of a rule (event, constraint, condition, action) are specified as clauses in a specific order to facilitate parsing.
For example, the following is a simplified example of a rule that may be executed:
Clause 1 describes the event to be executed by the satellite evaluation engine, in this case, the viewset application. The event is a change to QTD Sales information. Clause 2 comprises the constraint clause. It describes that the event will only be monitored from Monday to Friday. Clause 3 comprises the condition, further qualifying the situation that occasions the firing of the action. In this case, if the time was between 9:00 a.m. and 5:00 p.m. (i.e., 1700 hrs), and if the date corresponds to the end of the quarter. Clause 4 describes the action. In this case, the action is to send an email to user named Joe if the event, constraint, and condition are satisfied. Of course, these four components may be ordered in a different order if another syntax construct so dictates.
In accordance with one embodiment of the present invention, a rule is parsed to one or more core events, which are then distributed to one or more appropriate satellite evaluation engines to facilitate evaluation of the distributed event(s). In the previous example, the rule may be parsed and the event pertaining to the sales volume may be distributed to, for example, the satellite evaluation engine associated with the active data cache. The satellite valuation engine then evaluates the monitored data (sales volume in this example) and communicates the result (which may be simply true/false or may include pertinent sales volume data) back to the event engine. Meanwhile, the event engine is offloaded from the task of handling that rule until the event is satisfied.
To further improve efficiency, the centralized event engine may not even parse all components of a rule until the event is satisfied. Thus, if an event is never satisfied, no resource has been wasted parsing the entire rule and preparing the centralized event engine and/or the satellite evaluation engine(s) to handle the other components (which may never need to be handled if the event is never satisfied). Further, the satellite evaluation engine may only send information back to the event engine if the event evaluates to be true. Thus, if the sales volume is below 5,000 in the previous example, no message is sent from the satellite evaluation engine to advantageously avoid wasting bandwidth. Of course, as mentioned earlier, the evaluation of an event may be held off by the satellite evaluation engine to further avoid wasting resource unless the constraint is evaluated to be true by the centralized event monitor.
If the event is evaluated to be true at the satellite evaluation engine (and assuming any applicable constraint is also evaluated to be true), the satellite evaluation engine informs the centralized event engine, which may then evaluate the condition using either the same or another satellite evaluation engine or using the centralized resource. If the same or a different satellite evaluation engine is also used to evaluate a condition, the event monitor may send out the parsed condition and ask for the result of the evaluation of the condition. As the exemplary syntax above indicates, each of the event, constraint, condition, and action may be (but not required in all cases) implemented as a function. Distributing rule evaluation thus may comprise using the appropriate satellite evaluation engine to make the required function call.
Referring to
Satellite evaluation engines 1036a-1036h are some exemplary satellite evaluation engines employed by the active data platform of
In accordance with another embodiment of the present invention, there is provided a universal function call syntax to facilitate the task of distributing certain aspects of rule evaluation to one or more satellite evaluation engines. As discussed above, the rule syntax allows an event, a constraint, a condition, or an action to be specified as a function. Thus, the function call syntax may have the following construct:
where satname is the name of the satellite evaluation engine. Funcname, which is separated from satname by a symbol such as a dot, is the name of the function. The arguments represent optional arguments of the function.
By creating a universal function call syntax, the invention substantially simplifies the task of specifying that a particular satellite evaluation engine should handle a particular event or condition. Furthermore, the function syntax improves scalability in that a new satellite evaluation engine is added to the system, only the satellite evaluation engine name needs to be changed and the remainder of the syntax may be reused. Also, if a new event or condition is specified vis-à-vis an existing satellite evaluation engine, only the function name needs to be changed.
In one embodiment, a rule template library may be provided to allow users to leverage on work done by others. A rule template is simply a rule with certain argument(s) not completely specified. For example, a rule template may specify that if the sales volume exceeds 5,000 on a weekday and no special promotion is involved then notify person X. In this case, person X represents the argument that remains to be filled out to turn the rule template into a rule instance. In this example, the filling out of the person may be automatically accomplished by filling in the missing argument with the identity of the user accessing the rule template. In other cases, the missing arguments may be filled out by the user wishing to employ the rule template.
Of course the user can always edit existing rules (i.e., complete rule instances) to fit his needs. For example, the user can access an existing report and edit the rules therein to modify the arguments related to the event, condition, constraint, and/or action so that the newly created report would contain the information needed. The universal rule syntax renders it simple to implement rule templates and makes it easy for users to convert a rule template to a rule instance or to modify an existing rule to fit his needs.
While this invention has been described in terms of several preferred embodiments, there are alterations, permutations, and equivalents which fall within the scope of this invention. For example, although reference is given to Sagent Business Intelligence Solutions, it should be understood that the invention can also integrate with other business intelligence and ETL solutions. It should also be noted that there are many alternative ways of implementing the apparatuses of the present invention. It is therefore intended that the following appended claims be interpreted as including all such alterations, permutations, and equivalents as fall within the true spirit and scope of the present invention.
Advantages of the invention include optimizing the presence-aware delivery of relevant information to a device in a timely manner, and rendered in a dynamic format. Additional advantages include the continuous extraction of information from data sources without the need for manual queries, or the need of additional user training.
Having disclosed exemplary embodiments and the best mode, modifications and variations may be made to the disclosed embodiments while remaining within the subject and spirit of the invention as defined by the following claims.
The present application is a continuation of, and claims priority to, U.S. patent application Ser. No. 10/289,142, filed Nov. 5, 2002, entitled “Method and Apparatus For Distributed Rule Evaluation In A Near Real-Time Business Intelligence System,” which in turn is a continuation-in-part of and claims priority to, U.S. patent application Ser. No. 10/237,559, filed Sep. 6, 2002, entitled “Enterprise Link For a Software Database.” U.S. patent application Ser. No. 10/289,142 also claims benefit of U.S. Provisional Application No. 60/410,989, filed Sep. 16, 2002, entitled “Business Intelligent System.” U.S. patent application Ser. Nos. 10/289,142, 10/237,559 and 60/410,989 are incorporated by reference in their entirety for all purposes.
| Number | Name | Date | Kind |
|---|---|---|---|
| 5010478 | Deran | Apr 1991 | A |
| 5033009 | Dubnoff | Jul 1991 | A |
| 5283894 | Deran | Feb 1994 | A |
| 5510980 | Peters | Apr 1996 | A |
| 5553215 | Kaethler | Sep 1996 | A |
| 5592608 | Weber et al. | Jan 1997 | A |
| 5613131 | Moss et al. | Mar 1997 | A |
| 5615362 | Jensen et al. | Mar 1997 | A |
| 5654726 | Mima et al. | Aug 1997 | A |
| 5717895 | Leedom et al. | Feb 1998 | A |
| 5721847 | Johnson | Feb 1998 | A |
| 5754774 | Bittinger et al. | May 1998 | A |
| 5758337 | Hammond | May 1998 | A |
| 5765164 | Prasad et al. | Jun 1998 | A |
| 5778372 | Cordell et al. | Jul 1998 | A |
| 5781911 | Young et al. | Jul 1998 | A |
| 5784275 | Sojoodi et al. | Jul 1998 | A |
| 5787409 | Seiffert et al. | Jul 1998 | A |
| 5809267 | Moran et al. | Sep 1998 | A |
| 5812840 | Schwartz | Sep 1998 | A |
| 5831609 | London et al. | Nov 1998 | A |
| 5831615 | Drews et al. | Nov 1998 | A |
| 5857201 | Wright, Jr. et al. | Jan 1999 | A |
| 5862325 | Reed et al. | Jan 1999 | A |
| 5864669 | Osterman et al. | Jan 1999 | A |
| 5890174 | Khanna et al. | Mar 1999 | A |
| 5893126 | Drews et al. | Apr 1999 | A |
| 5893150 | Hagersten et al. | Apr 1999 | A |
| 5898434 | Small et al. | Apr 1999 | A |
| 5918009 | Gehani et al. | Jun 1999 | A |
| 5922044 | Banthia | Jul 1999 | A |
| 5926177 | Hatanaka et al. | Jul 1999 | A |
| 5928327 | Wang et al. | Jul 1999 | A |
| 5930794 | Linenbach et al. | Jul 1999 | A |
| 5943620 | Boltz et al. | Aug 1999 | A |
| 5974236 | Sherman | Oct 1999 | A |
| 6023694 | Kouchi et al. | Feb 2000 | A |
| 6025844 | Parsons | Feb 2000 | A |
| 6035324 | Chang | Mar 2000 | A |
| 6038558 | Powers et al. | Mar 2000 | A |
| 6055548 | Comer et al. | Apr 2000 | A |
| 6070197 | Cobb et al. | May 2000 | A |
| 6073242 | Hardy et al. | Jun 2000 | A |
| 6075530 | Lucas et al. | Jun 2000 | A |
| 6088481 | Okamoto et al. | Jul 2000 | A |
| 6092102 | Wagner | Jul 2000 | A |
| 6094681 | Shaffer et al. | Jul 2000 | A |
| 6112236 | Dollin et al. | Aug 2000 | A |
| 6125177 | Whittaker | Sep 2000 | A |
| 6141659 | Barker et al. | Oct 2000 | A |
| 6170019 | Dresel et al. | Jan 2001 | B1 |
| 6175859 | Mohler | Jan 2001 | B1 |
| 6182116 | Namma et al. | Jan 2001 | B1 |
| 6185582 | Zellweger et al. | Feb 2001 | B1 |
| 6189069 | Parkes et al. | Feb 2001 | B1 |
| 6201539 | Miller et al. | Mar 2001 | B1 |
| 6204846 | Little et al. | Mar 2001 | B1 |
| 6205474 | Hurley | Mar 2001 | B1 |
| 6208990 | Suresh et al. | Mar 2001 | B1 |
| 6219042 | Anderson et al. | Apr 2001 | B1 |
| 6233578 | Machihara et al. | May 2001 | B1 |
| 6239797 | Hills et al. | May 2001 | B1 |
| 6240444 | Fin et al. | May 2001 | B1 |
| 6243698 | Powers et al. | Jun 2001 | B1 |
| 6243713 | Nelson et al. | Jun 2001 | B1 |
| 6256649 | Mackinlay et al. | Jul 2001 | B1 |
| 6256676 | Taylor et al. | Jul 2001 | B1 |
| 6260114 | Schug | Jul 2001 | B1 |
| 6269393 | Yost et al. | Jul 2001 | B1 |
| 6292803 | Richardson et al. | Sep 2001 | B1 |
| 6301601 | Helland et al. | Oct 2001 | B1 |
| 6301609 | Aravamudan et al. | Oct 2001 | B1 |
| 6304546 | Natarajan et al. | Oct 2001 | B1 |
| 6314463 | Abbott et al. | Nov 2001 | B1 |
| 6317737 | Gorelik et al. | Nov 2001 | B1 |
| 6336135 | Niblett et al. | Jan 2002 | B1 |
| 6341312 | French et al. | Jan 2002 | B1 |
| 6348933 | Walls et al. | Feb 2002 | B1 |
| 6363363 | Haller et al. | Mar 2002 | B1 |
| 6393421 | Paglin | May 2002 | B1 |
| 6397217 | Melbin | May 2002 | B1 |
| 6430576 | Gates et al. | Aug 2002 | B1 |
| 6430604 | Ogle et al. | Aug 2002 | B1 |
| 6449344 | Goldfinger et al. | Sep 2002 | B1 |
| 6467052 | Kaler et al. | Oct 2002 | B1 |
| 6480847 | Linenbach et al. | Nov 2002 | B1 |
| 6501956 | Weeren et al. | Dec 2002 | B1 |
| 6510457 | Ayukawa et al. | Jan 2003 | B1 |
| 6513047 | Talley | Jan 2003 | B1 |
| 6519568 | Harvey et al. | Feb 2003 | B1 |
| 6519601 | Bosch | Feb 2003 | B1 |
| 6523046 | Liu et al. | Feb 2003 | B2 |
| 6532465 | Hartley et al. | Mar 2003 | B2 |
| 6535227 | Fox et al. | Mar 2003 | B1 |
| 6542165 | Ohkado | Apr 2003 | B1 |
| 6567796 | Yost et al. | May 2003 | B1 |
| 6567814 | Bankier et al. | May 2003 | B1 |
| 6574618 | Eylon et al. | Jun 2003 | B2 |
| 6574639 | Carey et al. | Jun 2003 | B2 |
| 6591277 | Spence et al. | Jul 2003 | B2 |
| 6591278 | Ernst | Jul 2003 | B1 |
| 6598167 | Devine et al. | Jul 2003 | B2 |
| 6606596 | Zirngibl et al. | Aug 2003 | B1 |
| 6640234 | Coffen et al. | Oct 2003 | B1 |
| 6647272 | Asikainen | Nov 2003 | B1 |
| 6651055 | Kilmer et al. | Nov 2003 | B1 |
| 6651142 | Gorelik et al. | Nov 2003 | B1 |
| 6654790 | Ogle et al. | Nov 2003 | B2 |
| 6664978 | Kekic et al. | Dec 2003 | B1 |
| 6668173 | Greene | Dec 2003 | B2 |
| 6678719 | Stimmel | Jan 2004 | B1 |
| 6687360 | Kung et al. | Feb 2004 | B2 |
| 6701485 | Igra et al. | Mar 2004 | B1 |
| 6714982 | McDonough et al. | Mar 2004 | B1 |
| 6731314 | Cheng et al. | May 2004 | B1 |
| 6745193 | Horvitz et al. | Jun 2004 | B1 |
| 6766418 | Alexander et al. | Jul 2004 | B1 |
| 6775267 | Kung et al. | Aug 2004 | B1 |
| 6775298 | Aggarwal | Aug 2004 | B1 |
| 6782424 | Yodaiken | Aug 2004 | B2 |
| 6789083 | Thelen | Sep 2004 | B2 |
| 6792456 | Hellerstein et al. | Sep 2004 | B1 |
| 6807562 | Pennock et al. | Oct 2004 | B1 |
| 6807583 | Hrischuk et al. | Oct 2004 | B2 |
| 6832341 | Vijayan | Dec 2004 | B1 |
| 6839737 | Friskel | Jan 2005 | B1 |
| 6870830 | Schuster et al. | Mar 2005 | B1 |
| 6898625 | Henry et al. | May 2005 | B2 |
| 6901592 | Mar et al. | May 2005 | B2 |
| 6907422 | Predovic | Jun 2005 | B1 |
| 6915457 | Miller | Jul 2005 | B1 |
| 6920607 | Ali et al. | Jul 2005 | B1 |
| 6937713 | Kung et al. | Aug 2005 | B1 |
| 6938221 | Nguyen | Aug 2005 | B2 |
| 6941345 | Kapil et al. | Sep 2005 | B1 |
| 6941351 | Vetrivelkumaran et al. | Sep 2005 | B2 |
| 6954757 | Zargham et al. | Oct 2005 | B2 |
| 6954902 | Noma et al. | Oct 2005 | B2 |
| 6996768 | Elo et al. | Feb 2006 | B1 |
| 7003568 | Chikada et al. | Feb 2006 | B1 |
| 7003731 | Rhoads et al. | Feb 2006 | B1 |
| 7024474 | Clubb et al. | Apr 2006 | B2 |
| 7028092 | MeLampy et al. | Apr 2006 | B2 |
| 7031314 | Craig et al. | Apr 2006 | B2 |
| 7032006 | Zhuk | Apr 2006 | B2 |
| 7035923 | Yoakum et al. | Apr 2006 | B1 |
| 7058953 | Willard et al. | Jun 2006 | B2 |
| 7096432 | Huapaya et al. | Aug 2006 | B2 |
| 7113964 | Bequet et al. | Sep 2006 | B1 |
| 7120139 | Kung et al. | Oct 2006 | B1 |
| 7139797 | Yoakum et al. | Nov 2006 | B1 |
| 7171473 | Eftis et al. | Jan 2007 | B1 |
| 7174339 | Wucherer et al. | Feb 2007 | B1 |
| 7177909 | Stark et al. | Feb 2007 | B2 |
| 7197565 | Abdelaziz et al. | Mar 2007 | B2 |
| 7221658 | Armstrong et al. | May 2007 | B1 |
| 7222294 | Coffen et al. | May 2007 | B2 |
| 7233979 | Dickerman et al. | Jun 2007 | B2 |
| 7243124 | Gardner et al. | Jul 2007 | B1 |
| 7243127 | Tabayoyon, Jr. et al. | Jul 2007 | B2 |
| 7243130 | Horvitz et al. | Jul 2007 | B2 |
| 7269627 | Knauerhase | Sep 2007 | B2 |
| 7272660 | Powers et al. | Sep 2007 | B1 |
| 7275215 | Werndorfer et al. | Sep 2007 | B2 |
| 7283805 | Agrawal | Oct 2007 | B2 |
| 7284034 | Matsa et al. | Oct 2007 | B2 |
| 7296217 | Earnshaw et al. | Nov 2007 | B1 |
| 7299257 | Boyer et al. | Nov 2007 | B2 |
| 7310532 | Knauerhase et al. | Dec 2007 | B2 |
| 7313593 | Pulito et al. | Dec 2007 | B1 |
| 7313617 | Malik et al. | Dec 2007 | B2 |
| 7353455 | Malik | Apr 2008 | B2 |
| 7359938 | Davies et al. | Apr 2008 | B1 |
| 7373428 | Armstrong et al. | May 2008 | B1 |
| 7379963 | Khare et al. | May 2008 | B1 |
| 7386588 | Mousseau et al. | Jun 2008 | B2 |
| 7389351 | Horvitz | Jun 2008 | B2 |
| 7392478 | Aureglia et al. | Jun 2008 | B2 |
| 7401158 | Beauchamp et al. | Jul 2008 | B2 |
| 7406569 | van de Waerdt | Jul 2008 | B2 |
| 7412481 | Nicholls et al. | Aug 2008 | B2 |
| 7412486 | Petrack et al. | Aug 2008 | B1 |
| 7412518 | Duigou et al. | Aug 2008 | B1 |
| 7412645 | Kotler et al. | Aug 2008 | B2 |
| 7415502 | Vishik et al. | Aug 2008 | B2 |
| 7426059 | Broda et al. | Sep 2008 | B2 |
| 7433922 | Engstrom | Oct 2008 | B2 |
| 7436939 | Packingham | Oct 2008 | B1 |
| 7436947 | Ordille et al. | Oct 2008 | B2 |
| 7454423 | Powers et al. | Nov 2008 | B2 |
| 7461378 | Beyda | Dec 2008 | B2 |
| 7464139 | Malik | Dec 2008 | B2 |
| 7487437 | Aureglia et al. | Feb 2009 | B2 |
| 7552204 | Bobde et al. | Jun 2009 | B2 |
| 7554938 | Smith et al. | Jun 2009 | B1 |
| 7627666 | DeGiulio et al. | Dec 2009 | B1 |
| 7631047 | Adamczyk | Dec 2009 | B1 |
| 7657616 | Poling et al. | Feb 2010 | B1 |
| 7664817 | Watanabe et al. | Feb 2010 | B2 |
| 7668915 | Couts et al. | Feb 2010 | B2 |
| 7668917 | Netsch et al. | Feb 2010 | B2 |
| 7725523 | Bolnick et al. | May 2010 | B2 |
| 20010034733 | Prompt et al. | Oct 2001 | A1 |
| 20010039616 | Kumagai et al. | Nov 2001 | A1 |
| 20010040945 | Fujino et al. | Nov 2001 | A1 |
| 20010049683 | Yoshikawa | Dec 2001 | A1 |
| 20010049721 | Blair et al. | Dec 2001 | A1 |
| 20020013853 | Baber et al. | Jan 2002 | A1 |
| 20020023143 | Stephenson et al. | Feb 2002 | A1 |
| 20020032602 | Lanzillo et al. | Mar 2002 | A1 |
| 20020038217 | Young | Mar 2002 | A1 |
| 20020038362 | Bhatia et al. | Mar 2002 | A1 |
| 20020056000 | Coussement | May 2002 | A1 |
| 20020057678 | Jiang et al. | May 2002 | A1 |
| 20020059425 | Belfiore et al. | May 2002 | A1 |
| 20020059472 | Wollrath et al. | May 2002 | A1 |
| 20020065894 | Dalal et al. | May 2002 | A1 |
| 20020075303 | Thompson et al. | Jun 2002 | A1 |
| 20020078208 | Crump et al. | Jun 2002 | A1 |
| 20020083067 | Tamayo et al. | Jun 2002 | A1 |
| 20020083072 | Steuart | Jun 2002 | A1 |
| 20020083118 | Sim | Jun 2002 | A1 |
| 20020095465 | Banks et al. | Jul 2002 | A1 |
| 20020103909 | Devine et al. | Aug 2002 | A1 |
| 20020107864 | Battas et al. | Aug 2002 | A1 |
| 20020107905 | Roe et al. | Aug 2002 | A1 |
| 20020107957 | Zargham et al. | Aug 2002 | A1 |
| 20020116362 | Li et al. | Aug 2002 | A1 |
| 20020116461 | Diacakis et al. | Aug 2002 | A1 |
| 20020120697 | Generous et al. | Aug 2002 | A1 |
| 20020120765 | Boehmke | Aug 2002 | A1 |
| 20020138640 | Raz et al. | Sep 2002 | A1 |
| 20020143710 | Liu | Oct 2002 | A1 |
| 20020147777 | Hackbarth et al. | Oct 2002 | A1 |
| 20020152402 | Tov et al. | Oct 2002 | A1 |
| 20020165849 | Singh et al. | Nov 2002 | A1 |
| 20020178035 | Lajouanie | Nov 2002 | A1 |
| 20020178353 | Graham | Nov 2002 | A1 |
| 20020184187 | Bakalash et al. | Dec 2002 | A1 |
| 20020194393 | Hrischuk et al. | Dec 2002 | A1 |
| 20020198985 | Fraenkel et al. | Dec 2002 | A1 |
| 20030004742 | Palmer et al. | Jan 2003 | A1 |
| 20030009603 | Ruths et al. | Jan 2003 | A1 |
| 20030014513 | Ruths et al. | Jan 2003 | A1 |
| 20030018719 | Ruths et al. | Jan 2003 | A1 |
| 20030023691 | Knauerhase | Jan 2003 | A1 |
| 20030028597 | Salmi et al. | Feb 2003 | A1 |
| 20030028682 | Sutherland | Feb 2003 | A1 |
| 20030028683 | Yorke et al. | Feb 2003 | A1 |
| 20030033329 | Bergman et al. | Feb 2003 | A1 |
| 20030037103 | Salmi et al. | Feb 2003 | A1 |
| 20030037113 | Petrovykh | Feb 2003 | A1 |
| 20030071850 | Geidi | Apr 2003 | A1 |
| 20030074393 | Peart | Apr 2003 | A1 |
| 20030088633 | Chiu et al. | May 2003 | A1 |
| 20030093585 | Allan | May 2003 | A1 |
| 20030101201 | Saylor et al. | May 2003 | A1 |
| 20030101223 | Pace et al. | May 2003 | A1 |
| 20030105837 | Kamen et al. | Jun 2003 | A1 |
| 20030110249 | Buus et al. | Jun 2003 | A1 |
| 20030112948 | Brown et al. | Jun 2003 | A1 |
| 20030115186 | Wilkinson et al. | Jun 2003 | A1 |
| 20030120805 | Couts et al. | Jun 2003 | A1 |
| 20030126136 | Omoigui | Jul 2003 | A1 |
| 20030154177 | Holland et al. | Aug 2003 | A1 |
| 20030158873 | Sawdon et al. | Aug 2003 | A1 |
| 20030182428 | Li et al. | Sep 2003 | A1 |
| 20030182461 | Stelting et al. | Sep 2003 | A1 |
| 20030187971 | Uliano et al. | Oct 2003 | A1 |
| 20030204741 | Schoen et al. | Oct 2003 | A1 |
| 20030208543 | Enete et al. | Nov 2003 | A1 |
| 20030217081 | White et al. | Nov 2003 | A1 |
| 20030217142 | Bobde et al. | Nov 2003 | A1 |
| 20030220860 | Heytens et al. | Nov 2003 | A1 |
| 20030229722 | Beyda | Dec 2003 | A1 |
| 20030235279 | Richomme | Dec 2003 | A1 |
| 20040002958 | Seshadri et al. | Jan 2004 | A1 |
| 20040003090 | Deeds | Jan 2004 | A1 |
| 20040010543 | Grobman | Jan 2004 | A1 |
| 20040019695 | Fellenstein et al. | Jan 2004 | A1 |
| 20040024822 | Werndorfer et al. | Feb 2004 | A1 |
| 20040030762 | Silverthorne et al. | Feb 2004 | A1 |
| 20040039776 | Ballard | Feb 2004 | A1 |
| 20040039800 | Black et al. | Feb 2004 | A1 |
| 20040049477 | Powers et al. | Mar 2004 | A1 |
| 20040054802 | Beauchamp et al. | Mar 2004 | A1 |
| 20040060001 | Coffen et al. | Mar 2004 | A1 |
| 20040073596 | Kloninger et al. | Apr 2004 | A1 |
| 20040087300 | Lewis | May 2004 | A1 |
| 20040146044 | Herkerdorf et al. | Jul 2004 | A1 |
| 20040152477 | Wu et al. | Aug 2004 | A1 |
| 20040254998 | Horvitz | Dec 2004 | A1 |
| 20050004984 | Simpson | Jan 2005 | A1 |
| 20050055329 | Bakalash et al. | Mar 2005 | A1 |
| 20050086211 | Mayer | Apr 2005 | A1 |
| 20050102294 | Coldewey | May 2005 | A1 |
| 20050102611 | Chen | May 2005 | A1 |
| 20050125377 | Kotler | Jun 2005 | A1 |
| 20050144114 | Ruggieri et al. | Jun 2005 | A1 |
| 20050187982 | Sato | Aug 2005 | A1 |
| 20060089939 | Broda et al. | Apr 2006 | A1 |
| 20060161540 | Schmitz et al. | Jul 2006 | A1 |
| 20060206589 | Lentini et al. | Sep 2006 | A1 |
| 20060259626 | Stone-Kaplan et al. | Nov 2006 | A1 |
| 20070192495 | Marais | Aug 2007 | A1 |
| 20080043256 | Broda et al. | Feb 2008 | A1 |
| 20080046505 | Netsch et al. | Feb 2008 | A1 |
| 20080046506 | Broda | Feb 2008 | A1 |
| 20080046510 | Beauchamp et al. | Feb 2008 | A1 |
| 20080046536 | Broda | Feb 2008 | A1 |
| 20080046556 | Nicholls et al. | Feb 2008 | A1 |
| 20080046568 | Broda et al. | Feb 2008 | A1 |
| 20080046803 | Beauchamp et al. | Feb 2008 | A1 |
| 20080046837 | Beauchamp et al. | Feb 2008 | A1 |
| 20080077656 | Broda | Mar 2008 | A1 |
| 20080155020 | Beauchamp et al. | Jun 2008 | A1 |
| 20090031205 | Aureglia et al. | Jan 2009 | A1 |
| 20090037803 | Bauchot | Feb 2009 | A1 |
| Number | Date | Country |
|---|---|---|
| WO 0163466 | Aug 2001 | WO |
| Number | Date | Country | |
|---|---|---|---|
| 20080148289 A1 | Jun 2008 | US |
| Number | Date | Country | |
|---|---|---|---|
| 60410989 | Sep 2002 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 10289142 | Nov 2002 | US |
| Child | 12035376 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 10237559 | Sep 2002 | US |
| Child | 10289142 | US |
