Interactive diagnostics having graphical playback and solution implementation capabilities

A system(s) and method(s) that facilitates diagnosing a HMI system and automatically applying a solution to correct and/or update the HMI system. According to a feature is an interactive diagnosis system for an human machine interface (HMI) system. The interactive diagnosis system includes a data capture component that captures HMI system information and a diagnostic component that accepts a user input relating to an HMI system and receives the HMI system information from the data capture component. The user input can be communicated through an interactive voice response system. Also included in the interactive diagnosis system is an engine component that receives the user input and based in part on the captured HMI system information selectively requests diagnostic and solution information from a data source and automatically applies the solution to the HMI system.

TECHNICAL FIELD

The subject disclosure relates generally to industrial automation systems and more particularly to human machine interfaces (HMIs).

BACKGROUND

Complete or partial automation in factories, manufacturing facilities, and the like is possible through utilization of industrial control systems. A logic processor, such as a programmable logic controller (PLC) lies at the core of the industrial control system. PLCs can be programmed to operate manufacturing processes through logic programs and/or routines. These programs can be stored in memory and generally are executed by the PLC in a sequential manner, although instruction jumping, looping, and interrupt routines are also common. Industrial control systems typically include a plurality of input and output (I/O) modules communicatively coupled to the PLC through a backplane that interferes at a device level to switches, contactors, relays, solenoids and sensors, among other devices. Accordingly, such control systems are optimized to control and monitor industrial processes, machines, manufacturing equipment, industrial plants, and the like.

Human machine interfaces (HMIs) or simply user interfaces are important to the successful operation and maintenance of industrial automation devices including control systems and associated equipment and/or machinery. User interfaces provide the essential communication link between operators and automation devices. This link allows operators to, among other things, setup and control devices and receive feedback by monitoring device status and health during operation. Without such user interfaces, achieving high-level industrial automation would be difficult if not impossible.

When a user has a problem with their HMI system, the user generally contacts technical support staff associated with a software vendor, for example, through, for example, placing a telephone call. The technical support staff queries the user for information through a series of questions designed to assist the technical support staff in diagnosing the problem experience by the user. The user may need to create or generate a log file and send it to the technical support staff. If the problem cannot be diagnosed in such a manner, the technical support staff might attempt to simulate the problem at the support site by attempting to reproduce the HMI system operating conditions and potential faults. The user may assist in such a simulation process by running or executing various debugging utilities on the user HMI system. If the problem cannot be reproduced and/or solved, a software engineer or other service technician may be dispatched to the user site to diagnose and solve the problem in the field. In some situations, software that includes a patch or fix to a problem is installed on a removable medium and physically transported and installed on the machine. The various processes of diagnosing and repairing a problem can result in excessive downtime, loss of productivity, and considerable costs can be involved for the user and the technical support staff and/or software vendor.

To overcome the aforementioned deficiencies, there is a need to provide the software vendor a means to quickly and easily interact with the user HMI system environment for quick and accurate feedback of the operating conditions and machine faults. There is a also a need to provide the user a means to interact directly into the software vendor solution database for self-help or auto-help capability mitigating the necessity of seeking assistance from technical support staff.

SUMMARY

The following presents a simplified summary of one or more embodiments in order to provide a basic understanding of some aspects of such embodiments. This summary is not an extensive overview of the one or more embodiments, and is intended to neither identify key or critical elements of the embodiments nor delineate the scope of such embodiments. Its sole purpose is to present some concepts of the described embodiments in a simplified form as a prelude to the more detailed description that is presented later.

According to a feature is an interactive diagnosis system that includes a data capture component to capture HMI system information and a diagnostic component that accepts a user input relating to the HMI system. The system can receive the HMI system information from the data capture component. The user input can be communicated through an interactive voice response system. Also included in the interactive diagnosis system is an engine component that receives the user input and based in part on the captured HMI system information selectively requests diagnostic and solution information from a data source and automatically applies the solution to the HMI system.

According to another embodiment is a method for interactive diagnosis and solution implementation in an industrial environment. The method includes receiving a diagnostic request and retrieving HMI system data. The diagnostic request can be from a user through an interactive voice response system. The method further includes requesting diagnostic and solution information from an external source, such as a software vendor database. In an embodiment, the software vendor database does not include the diagnostic and solution information, the method automatically contacts technical support for the information. The method can further include automatically applying the solution to the HMI system to resolve the diagnostic request.

DETAILED DESCRIPTION

With reference now to the drawings,FIG. 1illustrates an HMI system100configured to capture and retain data regarding various system parameters. System100includes HMI component(s)102that interface with one or more data capture component104. The HMI component(s)102can be components of the HMI system100that are at various locations. For example, an HMI system100can be employed for use at different facilities and such facilities can be in different geographic locations (e.g., city, state, country). Regardless of the location of either the HMI component(s)102and/or the data capture component104, communication can be established through a plurality of wired and/or wireless communication links and all such communication means are intended to fall within the scope of the detailed description and appended claims.

As aspects and parameters of the HMI component(s)102are configured, modified, etc. the data capture component104receives or requests such information. The data capture component104(also referred to as an event database) can record and/or store information regarding what a user has done or changed over a period of time and further can include code execution, user interaction through instructions and/or graphical/video data. The data capture component104can also include detailed information about the environment in which the user and HMI system is operating. The environment can include the various servers and their locations, the devices and their location, the person that is logged in and where the software components are located as well as the state or portion of code currently being executed. The information can be periodically sent from an HMI component102to the data capture component104. In other embodiments, the data capture component104periodically polls for and requests information regarding changes to the HMI component(s)102. In still other embodiments, the HMI component(s)102automatically transmit such information to the data capture component104.

The data capture component104can be configured to retain such information in a readily accessible format. For example, the data capture component104can retain such information in a memory and/or some other medium that can store information. By way of illustration, and not limitation, the data capture component104can include nonvolatile and/or volatile memory. Suitable nonvolatile memory can include read only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), or flash memory. Volatile memory can include random access memory (RAM), which acts as external cache memory. By way of illustration and not limitation, RAM is available in many forms such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), Synchlink DRAM (SLDRAM), Rambus direct RAM (RDRAM), direct Rambus dynamic RAM (DRDRAM), and Rambus dynamic RAM (RDRAM).

According to some embodiments, the data capture component104can periodically remove or delete information based on predefined criteria. For example, the information relating to configuration, modification, etc. can be destroyed after a period of time (e.g., days, weeks, years) or the information can be retained indefinitely. A retention period can be based on a plurality of factors including system resources, amount and number of modifications to the system, etc.

The data capture component104can be configured to output information relating to the HMI component(s) upon a request from, for example, a diagnostic component or diagnostic engine configured to access the functionality of the HMI system100. For example, if a failure or other problem with an HMI system100is detected and communicated to a diagnostic component, the data capture component104can provide historic data relating to modifications, operating condition, etc. that may have contributed and/or caused such failure. Access to such data allows a diagnostic component to locate the fault condition or infer a fault based upon various system100parameters, reducing troubleshooting and/or repair time and resources. The access to the HMI system100information can be performed through a secure channel though the data capture component104. In such a manner, breach of system100integrity and security is minimized while allowing technical service technicians to obtain system100information.

FIG. 2illustrates an HMI system200configured to monitor and record system information. HMI system200includes HMI component(s)202that can be located at a plurality of geographic locations and a data capture component204configured to monitor modifications and other parameters to the system200. Data capture component204can both receive data from the HMI component(s)202and send information to the HMI component(s)202though a communication link (either wirelessly or through a wired link).

Data capture component204can include a plurality of modules to track and retain system200information. These modules can include a function module206, a mode module208, an identifier module210, and/or a time stamp module212. The data capture component204may include additional modules and/or may not include all of the modules discussed above. In addition or alternatively, the modules can be rearranged and/or combined.

The function module206is configured to capture the functionalities associated with the HMI system200. The functionalities can include the operational parameter(s) of the machine (e.g., what the machine is doing). Other functionalities include the operating conditions of the user and/or system200(e.g., external conditions in the plant in which the machine is located).

The mode module208is configured to monitor the particular state or stage of programs being executed by the system200. For example, if the machine is experiencing a particular problem, the mode module208can monitor a software code to determine the line of codes which may be contributing to the experienced problem. According to another aspect, the mode module208can detect a revision or modification level of software or hardware components of the system200.

An identifier module210associated with the data capture component204can be configured to identify a particular user of the HMI system200as well as the particular machine or component experiencing the problem. For example, a user, in order to operate the HMI system200and/or to alter configurations associated with the system200may need to log on with a unique user identification (id) and/or user password. With a user id the particular user can be identified, thus if there are problems with the system200that can be traced to a particular user, such user can be contacted for more information regarding any changes or experiences that user had with the system200. An unique user id can also mitigate the occurrence of unintentional and/or malicious changes to system200. It should be understood that other identification techniques could be utilized, such as biometric authentication that utilizes physical characteristic unique to individuals. According to other embodiments, user identification is not utilized and/or tracked.

To ascertain and understand a current condition of the system200in the case of a fault, it might be desirable to track changes and/or operation of the system and the date and time such changes or operation occurred. This information can be obtained and maintained utilizing a time stamp module212. In some embodiments, the time stamp module212can record the date and/or time when a modification occurred along with the particular modification, thus providing detailed information. In other embodiments, the time stamp module212can record a date and/or time when such information is communication to the data capture component204. For example, if the data capture component204queries for (or receives) information daily, the time stamp module212can associate the date received with the system200information. In such a manner, the modification or other parameter can be traced to a particular day and a determination can be made whether the modification and/or parameter caused and/or contributed to a particular fault condition (e.g., how soon after the modification did the fault occur).

With reference now toFIG. 3, illustrated is an interactive diagnostic system300having graphical playback and solution implementation capabilities. System300includes HMI component(s)302and one or more data capture component304, that operate in a manner similar to that shown and described in the above figures. The HMI component(s)302and data capture component304are included in an HMI system306.

System300also includes a diagnostic component308that is in communication with an engine component310that is in communication with the data capture component304. The diagnostic component308and/or engine component310can be located remote from the HMI system306. For example, diagnostic component308and/or engine component310can be isolated from the HMI system306operating in a plant environment. The interface component308receives an input from a user and/or entity (e.g., the Internet, another system, a computer, . . . ), hereinafter referred to as user. For example, a user experiencing a problem with HMI system302, may desire to have such problems diagnosed and, therefore, interacts with the diagnostic component308to facilitate HMI system306repair.

Diagnostic component308can provide various types of user interfaces. For example, the diagnostic component308can provide a graphical user interface (GUI), a command line interface, and the like. For example, a GUI can be rendered that provides a user with a region or means to load, import, read, etc. an HMI system fault condition, and can include a region to present the results of such. These regions can comprise known text and/or graphic regions comprising dialogue boxes, static controls, drop-down-menus, list boxes, pop-up menus, as edit controls, combo boxes, radio buttons, check boxes, push buttons, and graphic boxes. In addition, utilities to facilitate the presentation such as vertical and/or horizontal scroll bars for navigation and toolbar buttons to determine whether a region will be viewable can be employed. For example, the user can interact with the engine component310by entering the information into an edit control.

The user can also interact with the engine component310through the diagnostic component308to select and provide information through various devices such as a mouse, a roller ball, a keypad, a keyboard, a pen and/or voice activation, for example. Typically, a mechanism such as a push button or the enter key on the keyboard can be employed subsequent entering the information in order to initiate information conveyance. However, it is to be appreciated that the system300is not so limited. For example, merely highlighting a check box can initiate information conveyance. In another example, a command line interface can be employed. For example, the command line interface can prompt (e.g., through a text message on a display and an audio tone) the user for information by providing a text message. The user can than provide suitable information, such as alpha-numeric input corresponding to an option provided in the interface prompt or an answer to a question posed in the prompt. It is to be appreciated that the command line interface can be employed in connection with a GUI and/or API. In addition, the command line interface can be employed in connection with hardware (e.g., video cards) and/or displays (e.g., black and white, and EGA) with limited graphic support, and/or low bandwidth communication channels.

The diagnostic component308interfaces with an engine component310that is configured to search for a means to diagnose and/or repair an HMI system302fault. The engine component310retrieves information from the data capture component306through a secure communication link. The information received from the data capture component306is utilized by engine component310to diagnose the problem and/or automatically apply a patch or fix to the HMI system302. If necessary, the engine component310can output information to query additional sources to diagnose and fix the HMI system302. Additional sources include a software vendor database and/or communication directly with technical support personnel.

FIG. 4illustrates an interactive diagnostic system400that facilitates solution implementation strategies. System400includes HMI component(s)402that interface with a data capture component404that obtains and maintains information concerning HMI component(s)402information. The HMI component(s)402and data capture component404are included in an HMI system406. When a problem is experienced with the HMI system406, a user inputs the information into a diagnostic component408that interfaces with an engine component410. The diagnostic component408includes an interactive voice response (IVR) module412, a transmit module414and/or an instruction module416. The diagnostic component408can include additional modules and/or may not include all of the modules discussed above. In addition or alternatively, the modules can be arranged in a different order and/or combined.

A user can enter an input to the diagnostic component408through the IVR module412that is configured to allow a user to interact with the system400. The user can input information using a touch-tone telephone or computer to interact with the engine component410through the diagnostic component408. The user can also acquire information from the engine component410. In such a manner, the user contacts the engine component410for diagnosis of a problem with the HMI system406.

The user can input information into a computer, through the IVR module412, and utilize voice communication to talk to the computer by saying, for example, “I have an alarm on X machine, what does it mean?” This information is relayed to the transmit module414where it is transformed into a machine understandable set of instructions, through for example instruction sets. This can be achieved though any known techniques, for example, key words, terms, or phrases, can be recognized, decoded, and/or transferred into machine understandable (readable) code.

The transmit module414communicates the machine instructions to the engine component410that obtains further information regarding the machine, environment, and other operating parameters. Provided that the engine component410can diagnose the problem(s), it sends information to the diagnostic component408and the instruction module416can automatically apply a patch or other means to fix the HMI system406, by, for example uploading a solution or potential work-around. For example, the software vendor can interact with the engine component410to obtain additional information regarding how the user got into the problem, the events that took place at substantially the same time as the problem. In another embodiment, the instruction module416can notify the user if there is not a problem or if some other action must be taken. For example, if the user is pressing the incorrect button to achieve a particular function from the machine, the instruction module416can instruct the user of the incorrect button and suggest how to perform the desired function. The engine component410can diagnose the problem through internal means, such as an internal database that contains various symptoms and solutions, or through external means, such as a database maintained by a software vendor and/or through direct communication with the technical support staff.

With reference now toFIG. 5, illustrated is an interactive diagnostic system500configured to automatically diagnose and correct system problems. System500includes HMI component(s) that are monitored for modifications, etc. by a data capture component504, both including within an HMI system506. The information retained by the data capture component504is utilized when a user reports a system failure through a diagnostic component508by means of an interactive voice response, for example. The diagnostic component508relays the reported failure to an engine component510configured to search for solutions to the failure and automatically correct the detected failures. The engine component510can be located at a plurality of physical locations (e.g., at a customer's site) but does not have to be physically located at the plant. The engine component510includes a secured channel to the HMI system506that mitigates the occurrence of unauthorized personnel gaining access to the system.

Engine component510includes a search module512, a contact module514, and/or an upgrade module516. The search module512is configured to access databases internal to the engine component510and databases external to the engine component510to obtain diagnostic information relating to a machine failure. The search module512can obtain information from the data capture component504to determine the machine conditions and/or operating parameters at substantially the same time as the reported failure. The machine conditions leading up to the failure can also be obtained to assist in diagnosing the system506failure.

The search module512can include a database or other means of retrieval internal to the engine component510that includes known fault conditions relating to the HMI system506. In addition or alternatively, the search module512can request and obtain diagnostic information automatically from a software vendor knowledge database if the diagnosis cannot be performed internal to the engine component510. If the information is available though interaction with the software vendor knowledge database, the engine component510automatically upgrades the system through the upgrade module516.

Sometimes the diagnostic and/or repair information is not available through the software vendor knowledge database and technical support needs to be contacted. The contact module514automatically notifies the software vendor technical support staff without needing the user to perform the function. The software vendor can be notified and a solution implemented without user interaction. In another embodiment, the technical support staff is notified and a communication is established with the user. Contacting the technical support staff can be performed in the background while the search module512is continuously accessing data.

The upgrade module516automatically upgrades or repairs the system without needing user interaction. In an embodiment, the upgrade module516can monitor the system506, through the data capture component504, and make a determination whether the solution applied to the system does correct the problem. If not, the engine component510and/or technical support can continue to search for a solution in a similar manner to that described above.

In some embodiments, the engine component510can interface with the HMI system506to perform a function, such as applying a patch to correct the problem. In another embodiment, the engine component510can request an authorization from appropriate personnel prior to the change being applied to the HMI system506. In a further embodiment, the engine component510can reconfigure the HMI system506to diagnose and correct the problem. In other embodiments, the engine component510can instruct the HMI system506to perform a debugging function to further assist in diagnosing a system506failure. It is to be understood that the functionality of the engine component510is dependent upon preauthorization to perform various functions. In some situations a user might not desire intrusive changes (e.g., reconfiguring system506), as such the engine component510can be restricted to recommend a change and prompting the user for confirmation before the change is applied. Other techniques to restrict the operation of the engine component510can be applied, based on user-defined criteria and parameters.

Referring now toFIG. 6, illustrated is a representation of an interactive diagnostic system utilizing the disclosed techniques. A user602interacts with an HMI system604whose components can be dispersed thought a plurality of geographic areas. The HMI system604interacts with a database608to provide logging of data relating to events occurring in the HMI system604, information relating to the HMI system604, and/or the operating environment of the HMI system604.

The user602can interact with an interface, such as an interactive voice response (IVR) diagnostic system610, through voice commands relayed trough a computer or telephone. The IVR diagnostics system610sends diagnostics information to a diagnostics engine612. The diagnostics engine612retrieves information from the database608and/or directly from the HMI system604. In order to diagnose the problem, the diagnostics engine612contacts a software vendor knowledge database614and communicates the potential problem. If the solution is available through the software vendor knowledge database614, the solution is communicated to the diagnostics engine612. The diagnostics engine612can communicate the solution to the user602, through the IVR diagnostics system610. In other embodiments, the diagnostics engine612communicates the information to the database608and/or can apply the patch, solution and/or work-around directly to the HMI system604.

If a solution is not available through the software vendor knowledge database614, the diagnostics engine612automatically contacts technical support staff616. The technical support staff616can respond to the request and suggest a patch and/or solution without the user602being involved with such diagnosis. If further information is necessary, the user602can be contacted through the IVR diagnostics system610, such as through a voice request for further information. The software database614can further apply system604upgrades through the database608and/or diagnostic engine612.

In view of the exemplary systems shown and described above, methodologies, which may be implemented in accordance with one or more aspects of the disclosed embodiments, will be better appreciated with reference to the diagram ofFIGS. 7 and 8. While, for purposes of simplicity of explanation, the methodologies are shown and described as a series of acts (or function blocks), it is to be understood and appreciated that the methodologies are not limited by the order of acts, as some acts may, in accordance with these methodologies, occur in different orders and/or concurrently with other acts from that shown and described herein. Moreover, not all illustrated acts may be required to implement a methodology in accordance with one or more aspects of the disclosed embodiments. It is to be appreciated that the various acts may be implemented by software, hardware, a combination thereof or any other suitable means (e.g. device, system, process, component) for carrying out the functionality associated with the acts. It is also to be appreciated that the acts are merely to illustrate certain aspects presented herein in a simplified form and that these aspects may be illustrated by a lesser and/or greater number of acts. Moreover, not all illustrated acts may be required to implement the following methodologies. Those skilled in the art will understand and appreciate that a methodology could alternatively be represented as a series of interrelated states or events, such as in a state diagram.

Initially referring toFIG. 7, illustrated is a methodology700for interactive diagnostic and solution implementation according to some embodiments presented herein. The method700begins at702where a request for diagnostic information is received. This request can be from a user and/or entity (e.g., the Internet, another system, a computer, . . . ). The request can be through any interactive means including, but not limited to, a keyboard input, a pushbutton phone, an interactive voice response system, etc. The diagnostic request relates to an HMI system for which the user is experiencing a problem, failure, or other reasons for which upgrade, diagnosis, and/or other information is desired.

System data is retrieved through a secured communication, at704, and includes parameters associated with the HMI system including modifications, operating conditions, and other system information. This information is utilized to diagnose the problem being experienced and/or evaluate system operating and/or parameters. The information relating to the particular problem and/or machine is sent to the software vendor (sw) along with a request for a solution to the problem that can be implemented. The vendor knowledge database is searched for information to upgrade, diagnose and/or repair system. When the solution is received, the method continues, at708, and the solution is automatically applied to the HMI system without necessitating further interaction from a user and/or vendor.

FIG. 8illustrates a methodology800for receiving a diagnostic request and automatically implement solutions utilizing a plurality of sources. The method800beings at,802, when an interactive voice response (IVR) request is received from a user experiencing problems with (or requesting upgrades and/or information) an HMI system. Information relating to the particular problem and/or HMI component or machine is retrieved at804. The information can include machine identification, user identification, code or instruction information, operating conditions, as well as other parameters associated with the machine. The information can be maintained in a database that is associated with the HMI system. At substantially the same time of the problem and/or machine is identified, a request for diagnosis and correction is requested from the software (sw) vendor, at806.

At808a determination is made whether a solution to the problem is available. If there is a solution available, “YES” the method continues at812where the problem is resolved automatically. If the solution is not available “NO” the method continues at810where technical support personnel are automatically contacted. The technical support personnel can further diagnose and research the problem. Additional information may also be needed from the user, at814, from whom the IVR request was received. In such a manner, the user does not have to interact with technical support personnel unless additional information is necessary in order to properly diagnose the problem. The problem is automatically resolved, at812. In another embodiment, the solution can be communication to the user, through the IVR, and the user manually applies the solution.

Referring now toFIG. 9, there is illustrated a block diagram of a computer operable to execute the disclosed architecture. In order to provide additional context for various aspects disclosed,FIG. 9and the following discussion are intended to provide a brief, general description of a suitable computing environment900in which the various aspects can be implemented. While the one or more embodiments have been described above in the general context of computer-executable instructions that may run on one or more computers, those skilled in the art will recognize that the embodiments also can be implemented in combination with other program modules and/or as a combination of hardware and software.

With reference again toFIG. 9, the exemplary environment900for implementing various aspects of the disclosed embodiments includes a computer902, the computer902including a processing unit904, a system memory906and a system bus908. The system bus908couples system components including, but not limited to, the system memory906to the processing unit904. The processing unit904can be any of various commercially available processors. Dual microprocessors and other multi-processor architectures may also be employed as the processing unit904.

The system bus908can be any of several types of bus structure that may further interconnect to a memory bus (with or without a memory controller), a peripheral bus, and a local bus using any of a variety of commercially available bus architectures. The system memory906includes read-only memory (ROM)910and random access memory (RAM)912. A basic input/output system (BIOS) is stored in a non-volatile memory910such as ROM, EPROM, EEPROM, which BIOS contains the basic routines that help to transfer information between elements within the computer902, such as during start-up. The RAM912can also include a high-speed RAM such as static RAM for caching data.

The computer902further includes an internal hard disk drive (HDD)914(e.g., EIDE, SATA), which internal hard disk drive914may also be configured for external use in a suitable chassis (not shown), a magnetic floppy disk drive (FDD)916, (e.g., to read from or write to a removable diskette918) and an optical disk drive920, (e.g., reading a CD-ROM disk922or, to read from or write to other high capacity optical media such as the DVD). The hard disk drive914, magnetic disk drive916and optical disk drive920can be connected to the system bus908by a hard disk drive interface924, a magnetic disk drive interface926and an optical drive interface928, respectively. The interface924for external drive implementations includes at least one or both of Universal Serial Bus (USB) and IEEE 1394 interface technologies. Other external drive connection technologies are within contemplation of the disclosed embodiments.

A number of program modules can be stored in the drives and RAM912, including an operating system930, one or more application programs932, other program modules934and program data936. All or portions of the operating system, applications, modules, and/or data can also be cached in the RAM912. It is appreciated that the embodiments can be implemented with various commercially available operating systems or combinations of operating systems.

A user can enter commands and information into the computer902through one or more wired/wireless input devices, e.g., a keyboard938and a pointing device, such as a mouse940. Other input devices (not shown) may include a microphone, an IR remote control, a joystick, a game pad, a stylus pen, touch screen, or the like. These and other input devices are often connected to the processing unit904through an input device interface942that is coupled to the system bus908, but can be connected by other interfaces, such as a parallel port, an IEEE 1394 serial port, a game port, a USB port, an IR interface, etc.

A monitor944or other type of display device is also connected to the system bus908by an interface, such as a video adapter946. In addition to the monitor944, a computer typically includes other peripheral output devices (not shown), such as speakers, printers, etc.

The computer902may operate in a networked environment using logical connections through wired and/or wireless communications to one or more remote computers, such as a remote computer(s)948. The remote computer(s)948can be a workstation, a server computer, a router, a personal computer, portable computer, microprocessor-based entertainment appliance, a peer device or other common network node, and typically includes many or all of the elements described relative to the computer902, although, for purposes of brevity, only a memory/storage device950is illustrated. The logical connections depicted include wired/wireless connectivity to a local area network (LAN)952and/or larger networks, e.g., a wide area network (WAN)954. Such LAN and WAN networking environments are commonplace in offices and companies, and facilitate enterprise-wide computer networks, such as intranets, all of which may connect to a global communications network, e.g., the Internet.

When used in a LAN networking environment, the computer902is connected to the local network952through a wired and/or wireless communication network interface or adapter956. The adaptor956may facilitate wired or wireless communication to the LAN952, which may also include a wireless access point disposed thereon for communicating with the wireless adaptor956.

When used in a WAN networking environment, the computer902can include a modem958, or is connected to a communications server on the WAN954, or has other means for establishing communications over the WAN954, such as by way of the Internet. The modem958, which can be internal or external and a wired or wireless device, is connected to the system bus908through the serial port interface942. In a networked environment, program modules depicted relative to the computer902, or portions thereof, can be stored in the remote memory/storage device950. It will be appreciated that the network connections shown are exemplary and other means of establishing a communications link between the computers can be used.

Referring now toFIG. 10, there is illustrated a schematic block diagram of an exemplary computing environment1000in accordance with the disclosed embodiments. The system1000includes one or more client(s)1002. The client(s)1002can be hardware and/or software (e.g., threads, processes, computing devices). The client(s)1002can maintain information by employing the embodiments, for example.

The system1000also includes one or more server(s)1004. The server(s)1004can also be hardware and/or software (e.g., threads, processes, computing devices). The servers1004can house threads to perform transformations by employing the disclosed embodiments, for example. One possible communication between a client1002and a server1004can be in the form of a data packet adapted to be transmitted between two or more computer processes. The data packet may include a cookie and/or associated contextual information, for example. The system1000includes a communication framework1006(e.g., a global communication network such as the Internet) that can be employed to facilitate communications between the client(s)1002and the server(s)1004.

Communications can be facilitated by a wired (including optical fiber) and/or wireless technology. The client(s)1002are operatively connected to one or more client data store(s)1008that can be employed to store information local to the client(s)1002(e.g., cookie(s) and/or associated contextual information). Similarly, the server(s)1004are operatively connected to one or more server data store(s)1010that can be employed to store information local to the servers1004.

What has been described above includes examples of the one or more embodiments. It is, of course, not possible to describe every conceivable combination of components or methodologies for purposes of describing the subject embodiments, but one of ordinary skill in the art may recognize that many further combinations and permutations of the disclosed embodiments are possible. Accordingly, the detailed description is intended to embrace all such alterations, modifications, and variations that fall within the spirit and scope of the appended claims.