Workflow decision management with heuristics
Methods, systems, and computer program products are provided for workflow decision management. Embodiments typically include maintaining a device state history; identifying a device usage pattern in dependence upon the device state history; identifying a derived scenario in dependence upon the device usage pattern; and selecting a heuristic in dependence upon the derived scenario. In typical embodiments, the heuristic has a tolerance. Embodiments also include identifying a workflow in dependence upon the selected heuristic and executing the workflow in dependence upon the tolerance.
1. Field of the Invention
The field of the invention is data processing, or, more specifically, methods, systems, and products for workflow decision management.
2. Description of Related Art
Conventional networks contain various networked devices. User's often use the various devices, or adjust particular settings of the devices, in accordance with consistent patterns and scenarios of device usage. Despite routinely using devices according to these consistent patterns and scenarios of device usage, conventional networked devices still often require user intervention to change attribute values of a device. It would be advantageous if there were a method of workflow decision management that used workflows to change in values of device attributes in a network in dependence upon identified patterns of usage and identified scenarios that did not require user intervention.
SUMMARY OF THE INVENTIONMethods, systems, and computer program products are provided for workflow decision management. Embodiments typically include maintaining a device state history, identifying a device usage pattern in dependence upon the device state history, identifying a derived scenario in dependence upon the device usage pattern, and selecting a heuristic in dependence upon the derived scenario. In typical embodiments, the heuristic has a tolerance. Embodiments also include identifying a workflow in dependence upon the selected heuristic and executing the workflow in dependence upon the tolerance.
In typical embodiments of the present invention, maintaining a device state history includes recording a plurality of attribute values for a device. In many embodiments, identifying a device usage pattern in dependence upon the device state history includes comparing the device state history with a plurality of device usage patterns records. In some embodiments, identifying a derived scenario in dependence upon the device usage pattern includes retrieving a derived scenario ID from a derived scenario table.
In typical embodiments, selecting a heuristic in dependence upon the derived scenario is carried out by reading a heuristic ID from a derived scenario record. In some embodiments, selecting a heuristic in dependence upon the derived scenario includes retrieving a heuristic ID from a heuristic table. In many embodiments, identifying a workflow in dependence upon the selected heuristic includes retrieving a workflow ID from a heuristic record.
In many embodiments, executing the workflow in dependence upon the tolerance is carried out by sending a message to a device. In some embodiments, executing the workflow in dependence upon the tolerance is carried out by calling a member method in a device class.
The foregoing and other objects, features and advantages of the invention will be apparent from the following more particular descriptions of exemplary embodiments of the invention as illustrated in the accompanying drawings wherein like reference numbers generally represent like parts of exemplary embodiments of the invention.
BRIEF DESCRIPTION OF THE DRAWINGS
The present invention is described to a large extent in this specification in terms of methods for workflow decision management. Persons skilled in the art, however, will recognize that any computer system that includes suitable programming means for operating in accordance with the disclosed methods also falls well within the scope of the present invention. Suitable programming means include any means for directing a computer system to execute the steps of the method of the invention, including for example, systems comprised of processing units and arithmetic-logic circuits coupled to computer memory, which systems have the capability of storing in computer memory, which computer memory includes electronic circuits configured to store data and program instructions, programmed steps of the method of the invention for execution by a processing unit.
The invention also may be embodied in a computer program product, such as a diskette or other recording medium, for use with any suitable data processing system. Embodiments of a computer program product may be implemented by use of any recording medium for machine-readable information, including magnetic media, optical media, or other suitable media. Persons skilled in the art will immediately recognize that any computer system having suitable programming means will be capable of executing the steps of the method of the invention as embodied in a program product. Persons skilled in the art will recognize immediately that, although most of the exemplary embodiments described in this specification are oriented to software installed and executing on computer hardware, nevertheless, alternative embodiments implemented as firmware or as hardware are well within the scope of the present invention.
Definitions“802.11” refers to a family of specifications developed by the IEEE for wireless LAN technology. 802.11 specifies an over-the-air interface between a wireless client and a base station or between two wireless clients.
“API” is an abbreviation for “application programming interface.” An API is a set of routines, protocols, and tools for building software applications.
“Bluetooth” refers to an industrial specification for a short-range radio technology for RF couplings among client devices and between client devices and resources on a LAN or other network. An administrative body called the Bluetooth Special Interest Group tests and qualifies devices as Bluetooth compliant. The Bluetooth specification consists of a ‘Foundation Core,’ which provides design specifications, and a ‘Foundation Profile,’ which provides interoperability guidelines.
“CEBus” is an abbreviation for Consumer Electronics Bus. CEBus is an open international standard for controlling devices over different media such as power line, radio frequency (RF), infrared (IR), coaxial cable, twisted pair, fiber optics and audio/video. The CEBus standard is promulgated by the Consumer Electronic Manufacturers Association (CEMA), a sector of the Electronics Industries Association (EIA) and described in 12 standards: the ANSI/EIA-600 series. The CEBus standard describes a physical design and topology of network media, a protocol for message generation, and a common application language (“CAL”). The CEBus specification is available for download at http://www.cebus.org.
CEBus provides a Common Application Language (CAL) defined in EIA 600.81 that uses an object-oriented model to provide interoperability between diverse devices in a networked environment. The CAL specification defines a set of classes that provide an interface to the internal operations of these disparate networked devices. If a function or feature cannot be mapped well to one of the classes defined in the CAL specification, the CAL specification has set aside a specific range of class identifiers for defining special classes.
CAL objects have two important attributes Instance Variables and Methods. Instance Variables contain information about a particular CAL object such as Boolean indications, numeric information, character-string information, and other data. Boolean Instance Variables can only be set to TRUE or FALSE. As the name implies, numeric Instance Variables are intended for storage of numbers. The character-string type Instance Variables provide storage of text. And other data-type Instance Variables provide storage of other information as a single-dimensioned array of one or more elements; each element containing the same number of one or more bytes.
Access to the information contained in CAL Instance Variables is accomplished through a set of member methods specific to that object. Examples of common methods include: setOn, setOff, setValue, getValue, setArray and getArray. Not all methods are appropriate for each Instance Variable type. For example, a setOn method is intended for manipulating Boolean Instance Variables and is therefore undefined for an Instance Variable of the character-string type.
“Coupled for data communications” means any form of data communications, wireless, 802.11b, Bluetooth, infrared, radio, internet protocols, HTTP protocols, email protocols, networked, direct connections, dedicated phone lines, dial-ups, serial connections with RS-232 (EIA232) or Universal Serial Buses, hard-wired parallel port connections, network connections according to the Power Line Protocol, and other forms of connection for data communications as will occur to those of skill in the art. Couplings for data communications include networked couplings for data communications. Examples of networks useful with various embodiments of the invention include cable networks, intranets, extranets, internets, local area networks, wide area networks, and other network arrangements as will occur to those of skill in the art. The use of any networked coupling among television channels, cable channels, video providers, telecommunications sources, and the like, is well within the scope of the present invention.
“HAVi” stands for ‘Home Audio Video interoperability,’ the name of a vendor-neutral audio-video standard particularly for home entertainment environments. HAVi allows different home entertainment and communication devices (such as VCRs, televisions, stereos, security systems, and video monitors) to be networked together and controlled from one primary device, such as a services gateway, PC, or television. Using IEEE 1394, the ‘Firewire’ specification, as the interconnection medium, HAVi allows products from different vendors to comply with one another based on defined connection and communication protocols and APIs. Services provided by HAVi's distributed application system include an addressing scheme and message transfer, lookup for discovering resources, posting and receiving local or remote events, and streaming and controlling isochronous data streams.
“HomePlug” stands for The HomePlug Powerline Alliance. HomePlug is a not-for-profit corporation formed to provide a forum for the creation of open specifications for high speed home powerline networking products and services. The HomePlug specification is designed for delivery of Internet communications and multimedia to homes through the home power outlet using powerline networking standards.
The HomePlug protocol allows HomePlug-enabled devices to communicate across powerlines using Radio Frequency signals (RF). The HomePlug protocol uses Orthogonal Frequency Division Multiplexing (OFDM) to split the RF signal into multiple smaller sub-signals that are then transmitted from one HomPlug enabled-device to another HomePlug-enabled device at different frequencies across the powerline.
“HTTP” stands for ‘HyperText Transport Protocol,’ the standard data communications protocol of the World Wide Web.
“ID” abbreviates “identification” as used by convention in this specification with nouns represented in data elements, so that ‘user ID’ refers to a user identification and ‘userID’ is the name of a data element in which is stored a user identification.
“LAN” is an abbreviation for “local area network.” A LAN is a computer network that spans a relatively small area. Many LANs are confined to a single building or group of buildings. However, one LAN can be connected to other LANs over any distance via telephone lines and radio waves. A system of LANs connected in this way is called a wide-area network (WAN). The Internet is an example of a WAN.
“LonWorks” is a networking platform available from Echelons. Lon Works is currently used in various network applications such as appliance control and lighting control. The LonWorks networking platform uses a protocol called “LonTalk” that is embedded within a “Neuron Chip” installed within Lon Works-enabled devices.
The Neuron Chip is a system-on-a-chip with multiple processors, read-write and read-only memory (RAM and ROM), and communication and I/O subsystems. The read-only memory contains an operating system, the LonTalk protocol, and an I/O function library. The chip has non-volatile memory for configuration data and for application programs, which can be downloaded over a LonWorks network to the device. The Neuron Chip provides the first 6 layers of the standard OSI network model. That is, the Neuron Chip provides the physical layer, the data link layer, the network layer, the transport layer, the session layer, and the presentation layer.
The Neuron Chip does not provide the application layer programming. Applications for LonWorks networks are written in a programming language called “Neuron C.” Applications written in Neuron C are typically event-driven, and therefore, result in reduced traffic on the network.
“OSGI” refers to the Open Services Gateway Initiative, an industry organization developing specifications for services gateways, including specifications for delivery of service bundles, software middleware providing compliant data communications and services through services gateways. The Open Services Gateway specification is a java based application layer framework that gives service providers, network operator device makers, and appliance manufacturer's vendor neutral application and device layer APIs and functions.
“USB” is an abbreviation for “universal serial bus.” USB is an external bus standard that supports data transfer rates of 12 Mbps. A single USB port can be used to connect up to 127 peripheral devices, such as mice, modems, and keyboards. USB also supports Plug-and-Play installation and hot plugging.
“WAP” refers to the Wireless Application Protocol, a protocol for use with handheld wireless devices. Examples of wireless devices useful with WAP include mobile phones, pagers, two-way radios, and hand-held computers. WAP supports many wireless networks, and WAP is supported by many operating systems. Operating systems specifically engineered for handheld devices include PalmOS, EPOC, Windows CE, FLEXOS, OS/9, and JavaOS. WAP devices that use displays and access the Internet run “microbrowsers.” The microbrowsers use small file sizes that can accommodate the low memory constraints of handheld devices and the low-bandwidth constraints of wireless networks.
The “X-10” means the X-10 protocol. Typical X-10 enabled devices communicate across AC powerline wiring, such as existing AC wiring in a home, using an X-10 transmitter and an X-10 receiver. The X-10 transmitter and the X-10 receiver use Radio Frequency (RF) signals to exchange digital information. The X-10 transmitter and the X-10 receiver communicate with short RF bursts which represent digital information.
In the X-10 protocol, data is sent in data strings called frames. The frame begins with a 4 bit start code designated as “1110.” Following the start code, the frame identifies a particular domain, such as house, with a 4 bit “house code,” and identifies a device within that domain with a 4 bit “devices code.” The frame also includes a command string of 8 bits identifying a particular preset command such as “on,” “off,” “dim,” “bright,” “status on,” “status off,” and “status request.”
Workflow Decision Management with Derived Scenarios and Workflow Tolerances Exemplary methods, systems, and products for workflow decision management, are now explained with reference to the accompanying drawings, beginning with
In the example of
The exemplary devices of
A device state history is a data structure containing the history of the values of one or more attributes of one or more devices. In the example of
A device usage pattern is typically implemented as a data structure representing a predetermined pattern of device usage for one or more devices. That is, a data structure representing a pattern of device usage. A device usage pattern may represent a pattern of usage of a single device or a pattern of usage of more than one device. The system of
The system of
The system of
The system of
The arrangement of devices making up the exemplary system illustrated in
Workflow decision management in accordance with the present invention is generally implemented with automated computing machinery installed on one or more workflow decision management compliant devices. For further explanation,
Also stored in RAM is a workflow decision management application (162). The workflow decision management application is application computer programming generally capable of maintaining a device state history, identifying a device usage pattern in dependence upon the device state history, and identifying a derived scenario in dependence upon the device usage pattern. The workflow decision management application is also generally capable of selecting a heuristic in dependence upon the derived scenario. The heuristic typically has a tolerance governing the execution of workflows. The exemplary devices of
The device (150) of
The exemplary device (150) of
The example device of
The example of
The example of
The example of
The example of
The exemplary devices usage (328) includes a usage ID (376) uniquely identifying a particular predetermined pattern of device usage. The exemplary device usage of
The example of
The example of
The example of
The example of
The example of
The exemplary derived scenario (352) of
The example of
The example of
The example of
The example of
The example of
The example of
The example of
The example of
The example of
The exemplary heuristic record of
In the example of
In the example of
In the example of
In the example of
In the example of
In the method of
The method of
As will occur to those of skill in the art, in typical embodiments, the values of the entries in the device state history do not have to be exactly the same as the values of the device usage records to identify a matching device usage record. In fact, the values of the entries of the device state history will often not be the exactly the same as the values of the device usage records when a matching record is identified. The degree to which the values of the entries in the device state history must be similar to the values of the device usage records to be considered a match will vary according to factors such as tolerances and methods used to used to compare the device state history with the device usage records, predefined tolerances for identifying a match, as well as other numerous factors that will occur to those of skill in the art.
The method of
In the method of
In the method of
The method of
In the method of
In the example of
The method of
The method of
Consider the following example. A networked home has a number of devices that are used to cool the west wing of the home. These devices include a fan, an air conditioner, and automatic shades. However, the automatic shades are currently not working and they currently will not close properly. A workflow decision management application operating according to the present invention has identified a scenario within a home network demonstrating that the west wing of the home is too warm and identified an appropriate heuristic to cool the wing. The workflow decision management application identifies and executes a workflow associated with the heuristic to cool the wing that includes reducing the thermostat for the air conditioner, increasing fan speed and closing the automatic shades.
Because the automatic shades are not working properly, the workflow does not reduce the temperature in the west wing sufficiently and soon thereafter the scenario that the room is too hot is again identified and again the same heuristic is identified. The same workflow is again identified and executed. By providing a tolerance for the execution of the workflow that defines a minimum tolerance value allowed for the thermostat, the air conditioner is spared from being overworked to the point of damage. That is, tolerances provide some boundaries for the execution of workflow preventing devices from being damaged by unforeseen problems with the execution of a workflow, such as in this case, the automatic shades not working properly. These tolerance values are often designed as a subset of the actual values that devices support. Such design advantageously recognizes that devices often support attribute values that will ultimately lead to damaging the device.
In the method of
It will be understood from the foregoing description that modifications and changes may be made in various embodiments of the present invention without departing from its true spirit. The descriptions in this specification are for purposes of illustration only and are not to be construed in a limiting sense. The scope of the present invention is limited only by the language of the following claims.
Claims
1. A method for workflow decision management, the method comprising:
- maintaining a device state history;
- identifying a device usage pattern in dependence upon the device state history;
- identifying a derived scenario in dependence upon the device usage pattern;
- selecting a heuristic in dependence upon the derived scenario; wherein the heuristic has a tolerance;
- identifying a workflow in dependence upon the selected heuristic; and
- executing the workflow in dependence upon the tolerance.
2. The method of claim 1 wherein maintaining a device state history further comprises recording a plurality of attribute values for a device.
3. The method of claim 1 wherein identifying a device usage pattern in dependence upon the device state history further comprises comparing the device state history with a plurality of device usage patterns records.
4. The method of claim 1 wherein identifying a derived scenario in dependence upon the device usage pattern further comprises retrieving a derived scenario ID from a derived scenario table.
5. The method of claim 1 wherein selecting a heuristic in dependence upon the derived scenario further comprises reading a heuristic ID from a derived scenario record.
6. The method of claim 1 wherein selecting a heuristic in dependence upon the derived scenario further comprises retrieving a heuristic ID from a heuristic table.
7. The method of claim 1 wherein identifying a workflow in dependence upon the selected heuristic comprises retrieving a workflow ID from a heuristic record.
8. The method of claim 1 wherein executing the workflow in dependence upon the tolerance further comprises sending a message to a device.
9. The method of claim 1 wherein executing the workflow in dependence upon the tolerance further comprises calling a member method in a device class.
10. A system for workflow decision management, the system comprising:
- means for maintaining a device state history;
- means for identifying a device usage pattern in dependence upon the device state history;
- means for identifying a derived scenario in dependence upon the device usage pattern;
- means for selecting a heuristic in dependence upon the derived scenario; wherein the heuristic has a tolerance;
- means for identifying a workflow in dependence upon the selected heuristic; and
- means for executing the workflow in dependence upon the tolerance.
11. The system of claim 10 wherein means for maintaining a device state history further comprises means for recording a plurality of attribute values for a device.
12. The system of claim 10 wherein means for identifying a device usage pattern in dependence upon the device state history further comprises means for comparing the device state history with a plurality of device usage patterns records.
13. The system of claim 10 wherein means for identifying a derived scenario in dependence upon the device usage pattern further comprises means for retrieving a derived scenario ID from a derived scenario table.
14. The system of claim 10 wherein means for selecting a heuristic in dependence upon the derived scenario further comprises means for reading a heuristic ID from a derived scenario record.
15. The system of claim 10 wherein means for selecting a heuristic in dependence upon the derived scenario further comprises means for retrieving a heuristic ID from a heuristic table.
16. The system of claim 10 wherein means for identifying a workflow in dependence upon the selected heuristic further comprises means for retrieving a workflow ID from a heuristic record.
17. The system of claim 10 wherein means for executing the workflow in dependence upon the tolerance further comprises means for sending a message to a device.
18. The system of claim 10 wherein means for executing the workflow in dependence upon the tolerance further comprises means for calling a member system in a device class.
19. A computer program product for workflow decision management, the computer program product comprising:
- a recording medium;
- means, recorded on the recording medium, for maintaining a device state history;
- means, recorded on the recording medium, for identifying a device usage pattern in dependence upon the device state history;
- means, recorded on the recording medium, for identifying a derived scenario in dependence upon the device usage pattern;
- means, recorded on the recording medium, for selecting a heuristic in dependence upon the derived scenario; wherein the heuristic has a tolerance;
- means, recorded on the recording medium, for identifying a workflow in dependence upon the selected heuristic; and
- means, recorded on the recording medium, for executing the workflow in dependence upon the tolerance.
20. The computer program product of claim 19 wherein means, recorded on the recording medium, for maintaining a device state history further comprises means, recorded on the recording medium, for recording a plurality of attribute values for a device.
21. The computer program product of claim 19 wherein means, recorded on the recording medium, for identifying a device usage pattern in dependence upon the device state history further comprises means, recorded on the recording medium, for comparing the device state history with a plurality of device usage patterns records.
22. The computer program product of claim 19 wherein means, recorded on the recording medium, for identifying a derived scenario in dependence upon the device usage pattern further comprises means, recorded on the recording medium, for retrieving a derived scenario ID from a derived scenario table.
23. The computer program product of claim 19 wherein means, recorded on the recording medium, for selecting a heuristic in dependence upon the derived scenario further comprises means, recorded on the recording medium, for reading a heuristic ID from a derived scenario record.
24. The computer program product of claim 19 wherein means, recorded on the recording medium, for selecting a heuristic in dependence upon the derived scenario further comprises means, recorded on the recording medium, for retrieving a heuristic ID from a heuristic table.
25. The computer program product of claim 19 wherein means, recorded on the recording medium, for identifying a workflow in dependence upon the selected heuristic further comprises means, recorded on the recording medium, for retrieving a workflow ID from a heuristic record.
26. The computer program product of claim 19 wherein means, recorded on the recording medium, for executing the workflow in dependence upon the tolerance further comprises means, recorded on the recording medium, for sending a message to a device.
27. The computer program product of claim 19 wherein means, recorded on the recording medium, for executing the workflow in dependence upon the tolerance further comprises means, recorded on the recording medium, for calling a member computer program product in a device class.
Type: Application
Filed: Jan 10, 2005
Publication Date: Jul 13, 2006
Inventors: William Brown (Raleigh, NC), Richard Muirhead (Tyler, TX), Francis Reddington (Richmond, VA)
Application Number: 11/032,336
International Classification: G06F 9/44 (20060101);