Real-time equipment behavior selection

At creation, a state machine of an industrial control configuration can be hard-coded with a number of states in a hierarchical manner. Once implemented into the configuration, it can be desirable for the states, interpretations of the states, and the like to be modified in accordance with particular desires and processes. Therefore, a user can select a change to a hierarchical rule set of the state machine while the state machine is part of the configuration and the change can be implemented.

TECHNICAL FIELD

The subject specification relates generally to industrial control state machines and other modeled behaviors, and in particular to the application of multiple state machines to a hierarchy of objects and alteration of one or more of the state machines once implemented in an industrial control configuration.

BACKGROUND

Industrial control environments can typically involve complex mechanical, electronic, electromechanical, and/or robotic machinery that perform various automated mechanical and/or electrical functions. Such machinery can include industrial motors, pumps, conveyors, escalators, drills, refrigeration systems, and so on, that can provide a particular physical output. Typically, an industrial environment utilizes one or more control devices to determine when to activate or deactivate such machinery, as well as an appropriate level of activation (e.g., an amount of current to supply a variable input motor). Additionally, the control devices are associated with logical program code that can determine an appropriate time, degree, manner, etc., to operate such machinery based on various determinable circumstances (e.g., output of another device, reading of an optical sensor, electronic measurement such as current level in a device, movement or number of rotations of a device, and so on).

Different controls can be used to provide protective features in an industrial environment. If a user attempts to make a change upon the industrial environment, then various checks can take place to discover if a user is authorized to make the change, such as requesting the user to enter a username and password. In addition, the user can be provided various tools that can assist in making changes to the industrial environment, including providing a template to be used to make different modifications.

SUMMARY

The following discloses a simplified summary of the specification in order to provide a basic understanding of some aspects of the specification. This summary is not an extensive overview of the specification. It is intended to neither identify key or critical elements of the specification nor delineate the scope of the specification. Its sole purpose is to disclose some concepts of the specification in a simplified form as a prelude to the more detailed description that is disclosed later.

Conventionally, a state machine of an industrial control configuration can be hard-coded at development and thus be difficult to modify based on specific needs of an industry. A hierarchical layering can be created that enables details of a process to be evaluated and used. This hard-coding can become problematic as specific processes in their applicable industries can benefit from having state machines tailored to specific desired functionality. With specific tailoring, processes can run more efficiently, act appropriately regarding a particular industry, and the like.

With the disclosed innovation, a state machine can be modified, including one or more hierarchical rule sets of the state machine, as desired to allow for improved operation. A sequencing engine analyzes the hierarchical application of state machines and any proposed modifications and implements the modifications to the state machine. In addition, the modified state machines can be tested and modified in an attempt to ensure that the modification does not cause the state machines to fail. Moreover, security measures can be taken to protect the state machines, such that unauthorized modifications do not occur.

DETAILED DESCRIPTION

Now referring toFIG. 1, an example configuration100(e.g., portion of an industrial control configuration) is disclosed relating to executing a hierarchy of objects102through use of at least one state machine104. Typically, an industrial control configuration can have multiple state machines104as well as multiple objects102, where the objects102exist in a hierarchy. State machines104can be applied to the objects104in the hierarchy and the hierarchy can follow different state machines104. According to one embodiment, objects are grouped by physical or/and behavioral hierarchies. While portions of the subject specification discuss operational control hierarchies, it is to be appreciated that other hierarchies can be used (e.g., cleanliness) and could conceptually follow a similar configuration and execution pattern. State machines104can be applied to a behavior aspect of an object104in the hierarchy and the hierarchy can follow different state machines104. A sequencing engine106can execute the objects102down on the hierarchy to conform to a state machine104and what paths to take based upon the state machine104. According to one embodiment, the state machines104can be industry standard state machines (e.g., third party tools).

The sequencing engine106can include an examination component108that analyzes hierarchy of objects102that conform to at least one state machine104. The examination component108can operate as means for analyzing the hierarchy of objects through the access. In addition, an execution component110can be used that executes the objects in the hierarchy according to a hierarchical rule set based upon a result of the analysis. According to one embodiment, the objects102are distributed across a network (e.g., local network, remote network, etc.).

Now referring toFIG. 2, an example system200is disclosed for modifying a state machine104. A state machine104(e.g., S88 batch state machine) can be used in an industrial control configuration and can configure in a hierarchical manner such that different layers perform different details of a process. For example, a state machine can be used in a process for making ice cream. At a highest level, a general recipe can be used for ice cream creation. At lower levels, there can be smaller operations that are part of the ice cream making process, such as adding cream, mixing ingredients together, and the like. In addition, the state machine can include a number of hierarchical rule sets (e.g., rules) that dictate operation, such that different lower state combinations dictate how operation occurs at higher levels.

Conventionally, the state machine is hard coded at creation and shipped to a manufacturer such that changing hierarchical rule sets can be difficult if not impossible. For example, a conventional state machine can have a first level (e.g., general process) that is supported by a second level. At the second level there are two portions that can have different states—a ‘run’ state and an ‘abort’ state. When shipped, the state machine can have a hierarchical rule set that if either second level portion is at an ‘abort’, then the first level is automatically at ‘abort’. However, it is possible that this implementation is not desirable for all industries. For instance, in the ice cream example, it can be possible that there is a desire to only have the first level ‘abort’ if both lower portions are at ‘abort’, such as in a packaging scenario where one ‘abort’ would lower packaging capacity to 50%, which can be considered better than 0%.

With the disclosed innovation, a sequencing engine106can be used to modify operation of the state machine104. A change to a state machine hierarchical rule set can be collected and an evaluation component202can analyze the change (e.g., proposed change) to the hierarchical rule set of the state machine. Based upon the analysis (e.g., determining contents of the change), a performance component204can implement the change. Implementation of the change can be automatic (e.g., occur upon collecting the change) or upon determining if the change should take place (e.g., the change originates from an approved entity, the change is not likely to cause an error in the industrial control configuration, etc.). According to one embodiment, the state machine104is integrated in the industrial control configuration upon implementation of the change. However, it is to be appreciated that other execution can be practiced, such as a technician changing hierarchical rule sets upon the state machine at a manufacturing plant prior to implementation upon the configuration. The evaluation component202can function as means for evaluating a change to a hierarchical rule set of at least one state machine. The performance component204can operate as means for implementing the change.

Now referring toFIG. 3, an example system300is disclosed for modifying a state machine, commonly while integrated upon an industrial control configuration. A change to a state machine can be analyzed by an evaluation component202. To facilitate operation, the evaluation component202can use a communication component302that can engage with other devices to transfer information, such as to send a request for metadata, receiving metadata from an auxiliary source, etc. Operation can take place wirelessly, in a hard-wired manner, employment of security technology (e.g., encryption), etc. Additionally, metadata transfer can be active (e.g., query/response) or passive (e.g., monitoring of public communication signals). Moreover, the communication component302can use various protective features, such as performing a virus scan on collected metadata and blocking metadata that is positive for a virus.

A search component304can discover information sources that are part of the configuration as well as auxiliary sources (e.g. a separate database). For instance, the search component304can discover possible sources of change instructions relating to hierarchical rule sets of the state machine. A technician can integrate a portable electronic device to the configuration and the search component304can discover that the device is integrated, evaluate the device, and determine that the device has potential to provide a change. According to one embodiment, reliable source metadata can be retained in storage. For example, if the device is removed from the configuration, the search component304can retain a record that the source is likely to return in case the device re-integrates. In addition, if it is determined that an added device is unlikely to produce information, then the search component304can delete relevant metadata to minimize storage space consumed.

Locations deemed relevant by the search component304as well as other locations can have information accessed by an obtainment component306. The obtainment component306can gather information (e.g., access information) from various locations, including collecting an instruction for a change to a hierarchical rule set, determining a source of the instruction, collecting metadata related to the source (e.g., a person that sends an instruction), and the like. Filtering can be practiced, such that only information likely to be relevant is collected, information from more reliable sources is gathered first, a limited amount of data (e.g., based upon storage size) is collected, as well as other filtering types. The obtainment component306can operate as means for accessing a hierarchy of objects that conform to at least one state machine.

An analysis component308can be used to determine specific characteristics of the change. For example, the change can be that ‘run-abort’ in a lower level should change from signifying ‘run’ to signifying ‘abort’ in a higher level at a particular portion of a particular state machine. The analysis component308can determine a manner for implementing the change, appreciating what is intended by a change, employ the search component304to find the relevant state machine, evaluate the state machine to determine where the change should be made, and the like.

It is possible that changing operation of a state machine can cause an error in the state machine, an error in the configuration, an undesirable result (e.g., decreased efficiency), etc. Therefore, the evaluation component202can used a preservation component310that retains the hierarchical rule set of the state machine prior to implementing the change. Therefore, if after the change it is determined that the state machine should return to a pre-change status, a retained portion can be quickly access and used to bring the state machine back to a condition of desired operability. The preservation component310can retain the pre-state hierarchical rule set upon storage312. In addition, the preservation component310can perform management techniques, such as keeping a most recent previous capture (e.g., since the most recent change) to minimize an amount of consumed storage312.

Different pieces of information, such as collected metadata, component operating instructions (e.g., communication component302), source location, components themselves, etc. can be held on storage312. Storage312can arrange in a number of different configurations, including as random access memory, battery-backed memory, hard disk, magnetic tape, etc. Various features can be implemented upon storage312, such as compression and automatic back up (e.g., use of a RAID configuration). In addition, storage312can operate as memory that can be operatively coupled to a processor (not shown).

Moreover, there can be a computer program embodied upon the storage312(e.g., a computer-readable medium) including program code for identifying a modification to a hierarchical rule set of an operational control state machine integrated with an industrial control configuration and program code for altering operation of a controller based upon the hierarchical rule set change. The storage312can be a removable entity, not integrate with the sequencing engine, be part of a distinct controller or other configuration entity, and the like. The system300can include a performance component204that implements the change.

Now referring toFIG. 4, an example system400is disclosed for implanting a change to a state machine (e.g., change of a hierarchical rule set) for an industrial control configuration. The system400can use an evaluation component202that analyzes a change to a hierarchical rule set of a state machine. A performance component204can operate to implements the change.

The state machine can be configured such that it operates in an efficient manner (e.g., a most efficient manner). Therefore, an optimization component402can be used that improves operation of the industrial control configuration (e.g., improves operation of the state machine). For instance, a comparison can be made between the state machine before and after the change. If it is determined that the state machine is more efficient under an old configuration, then the optimization component402can automatically return the state machine (e.g., through used of the preservation component310ofFIG. 3).

An artificial intelligence component404can be used to facilitate determinations of the system400. It is to be appreciated that artificial intelligence techniques can be used to practice determinations and inferences disclosed in the subject specification. The artificial intelligence component404can employ one of numerous methodologies for learning from data and then drawing inferences and/or making determinations related to dynamically storing information across multiple storage units (e.g., Hidden Markov Models (HMMs) and related prototypical dependency models, more general probabilistic graphical models, such as Bayesian networks, e.g., created by structure search using a Bayesian model score or approximation, linear classifiers, such as support vector machines (SVMs), non-linear classifiers, such as methods referred to as “neural network” methodologies, fuzzy logic methodologies, and other approaches that perform data fusion, etc.) in accordance with implementing various automated aspects described herein. In addition, the artificial intelligence component404can also include methods for capture of logical relationships such as theorem provers or more heuristic rule-based expert systems. The artificial intelligence component404can be represented as an externally pluggable component, in some cases designed by a disparate (third) party.

The change can be enacted upon the state machine and a verification component406can test the implemented change to determine if the state machine is in error (e.g., complete failure/cannot operate, partial failure, functioning in an undesirable manner, etc.). According to one embodiment, the error can occur through incorrect implementation. However, errors can arise from other sources, such as malicious code (e.g., a change designed to cause an error), through a mistake made by a technician, and others.

To correct the error, the performance component204can employ an alteration component408that modifies the implemented change if it is determined that the state machine is in error. The alteration component408and/or verification component406can work in conjunction with the preservation component310ofFIG. 3. For example, if the verification component406determines that the state machine is in error then the retained hierarchical rule set can be used by the alteration component408to modify the hierarchical rule set from the implemented change back to the retained hierarchical rule set. Other actions can be taken by the alteration component408to correct an error—for instance, if an error originated from a typographical error of a technician (e.g., typing ‘abrt’ as opposed to ‘abort’), then the alteration component408can determine a likely spelling and perform an automatic correction. After a change by the alteration component408, the verification component406and alteration component408can run again to ensure the correction does not cause an error. However, there can be some instances where the state machine cannot or should not be corrected. Therefore, an error message can be generated and transferred to an appropriate entity (e.g., a display component, a message inbox, and the like).

Now referring toFIG. 5, an example system500is disclosed for protecting a state machine regarding modification. A user can engage an interface component502to access information about a state machine or control configuration, enter information, propose a change, and the like. The interface component502can configure as a touch screen, a monitor-keyboard-mouse configuration, integrate with a personal electronic device (such as a cellular telephone), and the like. The interface component502can implement as means for collecting the proposed modification of the hierarchical rule set.

For a variety of reasons, it can be desirable to offer protection in relation to state machine modification. For example, an unauthorized person (e.g., repair technician) can attempt to modify the state machine and a security component504can be used to prevent implementation or mitigate impact of a proposed modification. In an illustrative example, a repair technician can attempt to make a change to the state machine and the security component504can block the request. A message can be sent from the security component504to a central administrator to determine if the change can be authorized and processed (e.g., evaluated and implemented). However, the security component504can function to merely block unauthorized attempts, ask for a password before an attempt can be processed, and the like.

There can be an evaluation component202that analyzes a change to a hierarchical rule set of a state machine. Therefore, the evaluation component202can function as means for determining if a proposed modification to a state machine should take place as a function of a result of analysis of the proposed modification. The evaluation component202can use the security component504to be based upon based upon security of the state machine. In addition, the system500can use a performance component204that implements the change, thus functioning as means for executing the proposed modification. According to one embodiment, the state machine is part of the industrial control configuration upon collecting the proposed modification.

The evaluation component202can use a test component506to predict how the state machine and industrial control configuration can act with the implemented change. In addition, the change can be implemented by the performance component204and then the test component506can operate to determine if the state machine is in error (e.g., before bringing the state machine online). The test component506can be used by the evaluation component to base operation upon applicability of the proposed modification such that the proposed modification would cause the state machine to be in error. Additionally, the system500can use a management component508that takes the at least one state machine offline prior to implementing a change and brings the at least one state machine back online once it is determined that the at least one state machine is not in error (e.g., based on a result of the test component506, based upon an assumption, etc.).

Now referring toFIG. 6, an example of a simple state machine104is disclosed that can be used in accordance with aspects disclosed herein. A number of different layers can exist in the state machine and be used to control at least different portions of an industrial control process. Different functionality can implement the state machine with specific characteristics and hierarchical rule sets. For example, while operating the state machine104can be in ‘running’ condition. Two alternatives can take place, either a ‘hold’ (e.g., temporarily suspend, pause, etc.) or a ‘stop’. In an illustrative instance, when making ice cream the state machine104can control adding cream into a mixing bowl. Until a proper amount of cream is added, the state machine can function in a ‘running’ condition. If an error occurs, the state machine104can change to a ‘hold’ until the error is fixed and then move to ‘running’ so operation can occur again. However, when finished, the state machine104can transfer a done command such that the state machine is in a ‘hold’. The state machine104can be a portion of a larger configuration (e.g., large state machine) that uses the ‘idle’ designation to show that other operations should take place (e.g., when cream is done being added, the state machine shows ‘idle’ and mixing should occur). In a similar fashion, state machines with specific characteristics and hierarchical rule sets modeling other behavioral aspects besides the operational state of equipment can be defined and executed.

Now referring toFIG. 7, an example methodology700is disclosed for processing a proposed change to a state machine. A request to modify a state machine (e.g., hierarchical rule set of a state machine) can be collected at action702, thus operating as collecting the proposed modification of the hierarchical rule set. In one implementation, the state machine is part of an industrial control configuration upon collecting the proposed modification.

A requesting entity (e.g., a user, an automatic operating device, etc.) can be identified at event704as well as other information related to the request. For example, an automatic diagnostics tool can determine that the state machine is operating in an inefficient manner, evaluate the state machine, and suggest modifications. There can be identification of the device, analysis of when the device made the request, and the like. Event704can include identifying if an entity requesting to make a proposed modification is allowed to make the modification.

A check706can be performed to determine if the request is authorized. The check can compare a source of the request (e.g., Internet Protocol address of an origin device) against a list of authorized sources. In a more complex example, a determination can be made based upon the source, time the request is made, historical characteristics, contextual metadata (e.g., if the control configuration is considered to be in a vulnerable state, then higher scrutiny can be applied). Check706can include determining if the proposed modification should take place as a function of a result of analysis, where the determination is based upon security of the state machine. If it is determined that the request is not authorized, then the request can be denied at act708.

However, if it is determined that the request is authorized, then the request can be evaluated to determine how the request implements with the state machine at action710. Action710can function as analyzing a proposed modification to a hierarchical rule set of a state machine. When determining if a request is authorized, it is possible that merits of the request are not considered. However, even an authorized request can be problematic, such as causing a non-ending loop. A determination can be made at check712on if a proposed modification of the request is likely to cause an error. Check712can function for determining if the proposed modification should take place as a function of a result of the analysis, where the determination is based upon applicability of the proposed modification such that the proposed modification would cause the state machine to be in error.

According to one embodiment, a virtual control configuration can be used to test and predict how the modification influences other elements. If an error is deemed likely to occur, then the methodology700can attempt to correct the error at action714. Action714can include analyzing the proposed modification to the hierarchical rule set of the state machine includes testing the proposed modification to anticipate if implementation of the proposed modification causes the state machine to be in error. If an error is not likely or the correction is made, then the modification can be implemented at event716. However, it is to be appreciated the modification can be enacted and observations made if an error actually occurs—if an error occurs then a correction attempt can be made.

Now referring toFIG. 8, an example methodology800is disclosed for using protective measures in regard to changing a state machine, commonly of an industrial control configuration. A modification request can be collected at act802. At the time of the collection, a capture can be made of the state machine at action804. The capture can be a recording of at least part of how the state machine configures. The capture can retain a large amount of information relate to the state machine or just portions relevant to the modification portion (e.g., the portion that is impacted by the modification).

A determination can be made on if the capture is correctly taken—if there is a correctly taken capture, then the change can be implemented at event806. If it is determined that the capture is not correct (e.g., there is any error, there is a substantial error, etc.), then another capture can be taken, the request can be denied, and the like. A check808can take place to determine if the state machine causes an error. This can be an actual error (e.g., determined through observation) as well as an anticipated error (e.g., determined through testing).

If it is determined that there is an error, then the error can be identified and there can be an attempt to correct the error at act810. After the error is corrected, a check812can take place to determine if the correction is successful. If the correction is successful or an error is not determined at the check808, then the state machine can be brought online so that the industrial control configuration can use the state machine. However, if the correction is not successful, then the capture can be re-implemented at action816(e.g., modified hierarchical rule sets can be replaced with former hierarchical rule sets). It is to be appreciated that act810can be repeated multiple times before re-implementing the capture in order to attempt to correct the error.

Now referring toFIG. 9, an example methodology900is disclosed for operating an entity (e.g., controller) that operates in conjunction with a state machine. A state machine can be analyzed at event902(e.g., hierarchical rule sets of the state machine can be determined). This can occur upon the state machine entering an industrial control configuration, upon the entity entering the configuration, and the like.

The state machine can be subjected to a change and this change can be observed by the entity at action904. Commonly the change is to a hierarchical rule set of the state machine, but it is to be appreciated that other changes are possible. A determination can be made at act906if the change to the state machine is considered final. For example, the state machine can be modified, but testing is not complete and thus the change is not considered final. However, brining the state machine online can be considered a sign of finality of a change.

The entity can be taken offline at event908to modify operation based upon the change to the state machine. Taking the state machine offline can assist in protect other entities from relying on incorrect data while change occurs. In addition, metadata relevant to the state machine can be collected, such as what hierarchical rule set is changed, why the change is made, how frequently information is changed, and the like. The entity can be evaluated through action910to assist in determining changes that are appropriate.

A check912can determine if a change to the entity is appropriate based upon modification of the state machine. For example, in an initial configuration if the state machine is at ‘abort’, then the entity can stop operating. However, if the state machine changes such that when a portion is at ‘abort’ other operations occur, then it can be detrimental for the entity to stop operation.

If it is determined that change is appropriate at check912, then a manner for modifying operation of the entity can be determined and a change can take place accordingly. The change can be tested (and corrected if appropriate) and the entity can be brought back online at act916. Additionally, if change is not appropriate, then the entity can be automatically brought back online. According to an alternative embodiment, then entity is taken offline only if it is determined that a change is appropriate.

For purposes of simplicity of explanation, methodologies that can be implemented in accordance with the disclosed subject matter were shown and described as a series of blocks. However, it is to be understood and appreciated that the claimed subject matter is not limited by the order of the blocks, as some blocks can occur in different orders and/or concurrently with other blocks from what is depicted and described herein. Moreover, not all illustrated blocks can be required to implement the methodologies described hereinafter. Additionally, it should be further appreciated that the methodologies disclosed throughout this specification are capable of being stored on an article of manufacture to facilitate transporting and transferring such methodologies to computers. The term article of manufacture, as used, is intended to encompass a computer program accessible from any computer-readable device, carrier, or media.

In order to provide a context for the various aspects of the disclosed subject matter,FIGS. 10 and 11as well as the following discussion are intended to provide a brief, general description of a suitable environment in which the various aspects of the disclosed subject matter can be implemented. While the subject matter has been described above in the general context of computer-executable instructions of a program that runs on one or more computers, those skilled in the art will recognize that the subject matter described herein also can be implemented in combination with other program modules. Generally, program modules include routines, programs, components, data structures, etc. that perform particular tasks and/or implement particular abstract data types. Moreover, those skilled in the art will appreciate that the inventive methods can be practiced with other computer system configurations, including single-processor, multiprocessor or multi-core processor computer systems, mini-computing devices, mainframe computers, as well as personal computers, hand-held computing devices (e.g., personal digital assistant (PDA), phone, watch . . . ), microprocessor-based or programmable consumer or industrial electronics, and the like. The illustrated aspects can also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. However, some, if not all aspects of the claimed subject matter can be practiced on stand-alone computers. In a distributed computing environment, program modules can be located in both local and remote memory storage devices.

Referring now toFIG. 10, there is illustrated a schematic block diagram of a computing environment1000in accordance with the subject specification. 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 house cookie(s) and/or associated contextual information by employing the specification, 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 specification, 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 can 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 via 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.

The illustrated aspects of the specification can also be practiced in distributed computing environments where certain tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules can be located in both local and remote memory storage devices.

With reference again toFIG. 11, the example environment1100for implementing various aspects of the specification includes a computer1102, the computer1102including a processing unit1104, a system memory1106and a system bus1108. The system bus1108couples system components including, but not limited to, the system memory1106to the processing unit1104. The processing unit1104can be any of various commercially available processors or proprietary specific configured processors. Dual microprocessors and other multi-processor architectures can also be employed as the processing unit1104.

The system bus1108can be any of several types of bus structure that can 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 memory1106includes read-only memory (ROM)1110and random access memory (RAM)1112. A basic input/output system (BIOS) is stored in a non-volatile memory1110such as ROM, EPROM, EEPROM, which BIOS contains the basic routines that help to transfer information between elements within the computer1102, such as during start-up. The RAM1112can also include a high-speed RAM such as static RAM for caching data.

The computer1102further includes an internal hard disk drive (HDD)1114(e.g., EIDE, SATA), which internal hard disk drive1114can also be configured for external use in a suitable chassis (not shown), a magnetic floppy disk drive (FDD)1116, (e.g., to read from or write to a removable diskette1118) and an optical disk drive1120, (e.g., reading a CD-ROM disk1122or, to read from or write to other high capacity optical media such as the DVD). The hard disk drive1114, magnetic disk drive1116and optical disk drive1120can be connected to the system bus1108by a hard disk drive interface1124, a magnetic disk drive interface1126and an optical drive interface1128, respectively. The interface1124for 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 subject specification.

A number of program modules can be stored in the drives and RAM1112, including an operating system1130, one or more application programs1132, other program modules1134and program data1136. All or portions of the operating system, applications, modules, and/or data can also be cached in the RAM1112. It is appreciated that the specification can be implemented with various proprietary or commercially available operating systems or combinations of operating systems.

A user can enter commands and information into the computer1102through one or more wired/wireless input devices, e.g., a keyboard1138and a pointing device, such as a mouse1140. Other input devices (not shown) can 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 unit1104through an input device interface1142that is coupled to the system bus1108, 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 monitor1144or other type of display device is also connected to the system bus1108via an interface, such as a video adapter1146. In addition to the monitor1144, a computer typically includes other peripheral output devices (not shown), such as speakers, printers, etc.

When used in a LAN networking environment, the computer1102is connected to the local network1152through a wired and/or wireless communication network interface or adapter1156. The adapter1156can facilitate wired or wireless communication to the LAN1152, which can also include a wireless access point disposed thereon for communicating with the wireless adapter1156.

When used in a WAN networking environment, the computer1102can include a modem1158, or is connected to a communications server on the WAN1154, or has other means for establishing communications over the WAN1154, such as by way of the Internet. The modem1158, which can be internal or external and a wired or wireless device, is connected to the system bus1108via the input device interface1142. In a networked environment, program modules depicted relative to the computer1102, or portions thereof, can be stored in the remote memory/storage device1150. It will be appreciated that the network connections shown are example and other means of establishing a communications link between the computers can be used.

The aforementioned systems have been described with respect to interaction among several components. It should be appreciated that such systems and components can include those components or sub-components specified therein, some of the specified components or sub-components, and/or additional components. Sub-components can also be implemented as components communicatively coupled to other components rather than included within parent components. Additionally, it should be noted that one or more components could be combined into a single component providing aggregate functionality. The components could also interact with one or more other components not specifically described herein but known by those of skill in the art.

What has been described above includes examples of the subject specification. It is, of course, not possible to describe every conceivable combination of components or methodologies for purposes of describing the subject specification, but one of ordinary skill in the art can recognize that many further combinations and permutations of the subject specification are possible. Accordingly, the subject specification is intended to embrace all such alterations, modifications and variations that fall within the spirit and scope of the appended claims. Furthermore, to the extent that the term “includes” is used in either the detailed description or the claims, such term is intended to be inclusive in a manner similar to the term “comprising” as “comprising” is interpreted when employed as a transitional word in a claim.