The subject invention relates to industrial control systems, and more particularly to systems and methods for automatic visualization and display of data based upon attributes associated therewith.
Industrial controllers are special purpose processing devices used for controlling industrial processes, machines, manufacturing equipment, and other factory automation applications. In accordance with a control program or routine, an industrial controller can measure one or more process variables or inputs representative of the status of a controlled process, and change outputs effecting control of the process. The inputs and outputs can be binary, (e.g., on or off), and/or analog assuming a continuous range of values. The control routine can be executed in a series of execution cycles with batch processing capabilities, and can comprise one or more functional units. Such a control routine can be created in a controller configuration system having tools and interfaces whereby a user can implement a control strategy using programming languages or graphical representations of control functionality. The control routine can be downloaded from the configuration system into one or more controllers for implementation of the control strategy in controlling a process or machine.
The measured inputs received from a controlled process and the outputs transmitted to the process can pass through one or more input/output (I/O) modules in a control system, which serve as an electrical interface between the controller and the controlled process, and can be located proximate or remote from the controller. The inputs and outputs can be recorded in an I/O table in processor memory. Input values can be asynchronously read from the controlled process by one or more input modules and output values can be written directly to the I/O table by a processor for subsequent communication to the process by specialized communications circuitry. An output module can interface directly with a controlled process, by providing an output from an I/O table to an actuator such as a motor, drive, valve, solenoid, and the like.
During execution of the control routine, values of the inputs and outputs exchanged with the controlled process pass through the I/O table. The values of inputs in the I/O table can be asynchronously updated from the controlled process by dedicated scanning circuitry. This scanning circuitry can communicate with input and/or output modules over a bus on a backplane or network communications. The scanning circuitry can also asynchronously write values of the outputs in the I/O table to the controlled process. The output values from the I/O table can be communicated to one or more output modules for interfacing with the process. Thus, a controller processor can simply access the I/O table rather than needing to communicate directly with the controlled process.
In distributed control systems, controller hardware configuration can be facilitated by separating the industrial controller into a number of control modules, each of which performs a different function. Particular control modules needed for the control task can then be connected together on a common backplane within a rack and/or through a network or other communications medium. The control modules can include processors, power supplies, network communication modules, and I/O modules exchanging input and output signals directly with the controlled process. Data can be exchanged between modules using a backplane communications bus, which can be serial or parallel, or via a network. In addition to performing I/O operations based solely on network communications, smart modules exist which can execute autonomous logical or other control programs or routines.
Various control modules of a distributed control system can be spatially distributed along a common communication link in several racks. Certain I/O modules can thus be located proximate a portion of the control equipment, and away from the remainder of the controller. Data can be communicated with these remote modules over a common communication link, or network, wherein all modules on the network communicate via a standard communications protocol.
In a typical distributed control system, one or more I/O modules are provided for interfacing with a process. The outputs derive their control or output values in the form of a message from a master or peer device over a network or a backplane. For example, an output module can receive an output value from a processor, such as a programmable logic controller (PLC), via a communications network or a backplane communications bus. The desired output value is generally sent to the output module in a message, such as an I/O message. The output module receiving such a message will provide a corresponding output (analog or digital) to the controlled process. Input modules measure a value of a process variable and report the input values to a master or peer device over a network or backplane. The input values can be used by a processor (e.g., a PLC) for performing control computations.
In such distributed control systems, data can be collected, analyzed and disbursed throughout a control architecture. In some instances, data related to a particular system and/or process can be conveyed to a user wishing to inspect desired data values. Further, data can relate to multiple aspects of a particular process and can be routed to a particular destination utilizing a number of means. Conventionally, data transmitted throughout a control architecture is typically viewed before it is configured to modify its appearance. In addition, it can be difficult to determine which channels are employed to transmit data from a source to a particular destination. Thus, data is needed that can be easily modified and presented relative to various properties associated with such data.
The following presents a simplified summary of the invention in order to provide a basic understanding of some aspects of the invention. This summary is not an extensive overview of the invention. It is intended neither to identify key or critical elements of the invention nor to delineate the scope of the invention. Its sole purpose is to present some concepts of the invention in a simplified form as a prelude to the more detailed description that is presented later.
The invention provides systems and methods for automatic visualization and display of data based upon attributes associated therewith. Data received by a subscriber can have various attributes indicative of a source of the data and/or channels employed to deliver the data to the subscriber. For example, some data sources can only provide data with a time stamp, while others can support transactional capabilities, and still others can support more extensive attributes with varying degrees of sophistication. In addition, some devices (e.g., PLCs, controllers, etc.) can perform as servers adding attributes to data from other devices, while other devices can have as proxy servers for data in order to satisfy the data servicing requirements from automation devices for heavily utilized high overhead data. It is to be appreciated that in a data driven architecture, attributed data can be served in a hierarchical manner to designate the source and channels through which the data is routed. As known, data driven architecture can provide additional information to data subscribers in a particular control system to allow for more efficient and robust utilization of system resources. Partially attributed data can be published or made available to selected subscribers that can wish to view intermediate attributes of the data that relate to intermediate channels of data routing.
A common data object shell definition can provide a common framework for interoperable access to data on a plant floor in a manner that is amenable to manufacturing execution systems (MES) and/or enterprise resource planning (ERP) integrated information applications. Included in this data object shell definition can be tiered levels of human machine interface (HMI) visualization attributes for that data. A directory can be employed to provide a logical description to the user of devices in a factory, for example. The directory can provide a logical depiction of data tailored to the vernacular and/or plant organization of a user's industry. Thus, the directory can translate the logical view of the factory into physical locations and/or addresses needed for the required data access and/or associations.
According to one aspect of the invention, a system that provides automatic visualization configuration in an industrial environment is employed, comprising an input component that receives data from a source, wherein the data accumulates attributes based on data channeling from the source to the input component; and an analyzer that determines visualization attributes from the accumulated attributes and configures display properties of the data based at least in part upon the visualization attributes that are utilized during display of the data.
According to another aspect of the invention, a computer implemented method for automatic configuration of data is utilized that comprises receiving data from a source; analyzing the attributes associated with the data; determining data appearance configuration based on the analysis; and utilizing the configuration to display the data to a user.
According to yet another aspect of the invention, a computer implemented method for formatting data is employed comprising obtaining data from a source; determining attributes associated with the data based at least upon servers employed to communicate the data; and formatting the data based at least in part upon the attributes.
According to still yet another aspect of the invention, a computer implemented method for displaying data is employed comprising means for receiving data rules associated with visual formatting of the data; means for determining visual formatting properties associated with the data; and means for presenting the data on the display device based at least in part upon the visual formatting properties of the data. To the accomplishment of the foregoing and related ends, the invention, then, comprises the features hereinafter fully described. The following description and the annexed drawings set forth in detail certain illustrative aspects of the invention. However, these aspects are indicative of but a few of the various ways in which the principles of the invention can be employed. Other aspects, advantages and novel features of the invention will become apparent from the following detailed description of the invention when considered in conjunction with the drawings.
The various aspects of the subject invention will now be described with reference to the drawings, wherein like reference numerals are used to refer to like elements throughout. The invention relates to systems and methods that provide automatic visualization configuration and/or display in a data driven architecture. In such architecture, data can be received from any number of components, devices, systems, etc. throughout a factory, plant and the like. In addition, such architecture can provide various channels for information to be routed throughout the system such as servers, proxy servers, hubs and the like. In one aspect of the subject invention, the handling and processing of this data can be selectively transactional in nature. In addition, attributes associated with this data can be as simple as a time stamp or include units and data quality parameters, or include more sophisticated attributes such as transactional processing parameters, and various levels of visualization attributes.
Referring now to
The information received by the input component 110 can be related to specific processes, machines and/or data associated with various aspects of machine control, for example. Such information can be transmitted to the visualization component 120 to modify various properties related to visual format and display of the information to a user. The visualization component 120 can change visual properties associated with received information based on various parameters. The visualization component 120 can be employed to change any number of display properties such as color, font, size, location, etc. of the information. Additionally or alternatively, data can be displayed in various levels of detail and illustrated utilizing graphics such as bar graphs, dials, pie charts, and the like. Various external visual aids can be associated with the data and displayed in place of or along side the data to provide context for the information, such as bitmaps, vector based graphics, etc.
In order to modify the information displayed to a user, the visualization component 120 can analyze received data to determine if various properties and/or attributes are associated with the data. For example, attributes relating to the source of the data can be determined as well as the manner (e.g., channels, servers, data routing, etc.) in which a subscriber received such data. The visualization component 120 can dynamically format and generate data based on the visualization attributes associated with the data objects to be displayed. Formatting of data can be based upon user definable and/or configurable “skins” for preferences of appearance, etc. and/or user definable configuration rules for visualization formatting. In addition, visualization information can be selected based upon the role and/or location of a user, capabilities of a display device, process to be viewed, location of a process to be viewed, time and/or business logic, for example. Further, additional attributes can be employed to force changes on applicable data.
The input component 110 can facilitate communication with external devices utilizing a number of protocols and/or standards. Further, the communication link that connects the external hardware with the input component 110 can obtain connectivity many different ways. Various protocols can be employed between the input component 110 and external sources and such protocols can be selected by the user and/or detected by the input component 110 to begin communication between devices. In another approach, the system 100 can receive and/or modify data. For example, the input component 110 can be associated with an industrial controller, a distributed I/O module, a data acquisition board or the like. Data can be transmitted from the input component 110 to the visualization component 120 utilizing one or a plurality of different mediums such as coaxial cable, ControlNet, Profibus, Ethernet, etc.
The visualization component 120 can output data to a plurality of disparate devices to display such data to a user(s). Such data can be formatted to accommodate various aspects of the device that receives such data and/or the user viewing the data. In one aspect of the invention, after the formatted data has been sent to a display device, a user can modify the display of such data. In addition, data can be sent to a desktop monitor with a particular size and resolution capability. Display of such data can be modified based on other data and/or display constraints related to disparate processes associated with the monitor. In another example, the same data can be transmitted to a handheld PC with a different (e.g., smaller) screen size, resolution, processes, etc.
Turning now to
As described, the attribute analyzer 210 can be a virtual component that resides in the visualization component 120. In this manner, the visualization component 120 can act as a host for the analyzing process to take place. Alternatively, the visualization component 120 can exchange data with the attribute analyzer 210 wherein the attribute analyzer 210 is a separate entity. A memory (not shown) and a processor (not shown) can be coupled with the attribute analyzer 210 to facilitate analysis of received data. Once analysis is complete, data and/or a listing of attributes can be transmitted to the visualization component 120 for further processing.
Turning now to
Additionally, a user can create rules specific to various data that can be received by the visualization component to be visually formatted and output to a device. In order to create rules, the rules store 310 can provide a listing of possible attributes to the user that is associated with data received. In this manner, the user can select a desired attribute and assign it various formatting rules. Similarly, a listing of available formatting options can be presented to a user in order to simplify the rules creation process. Once a user creates a specific rule relating to a formatting configuration, he can employ the rules store 310 to store and access the rule at a later time. Thus, a user can generate and accumulate a plurality of various formats to be employed at a later date if desired. For instance, all data relating to a quenching process can have a graphic that displays a tank filled with water and a numerical field to display the data associated with the graphic. Additionally, the water level in the tank can be scaled so that the water height varies as a function of the numerical value of the data.
As shown, the rules store 310 is within the attribute analyzer 210. It is to be appreciated, however, that the rules store 310 can reside remotely from the attribute analyzer 210 and/or act as a virtual store that can be accessed from any number of locations. For example, the rules store 310 can be an HMI located on a remote computer that provides a graphical interface in order to create, edit and store attribute related rules. The HMI can provide an environment in which various routines, protocols, etc. can be employed to facilitate the development and execution of a rule(s).
In one aspect of the invention, user definable configuration rules for visualization formatting could utilize a method similar to that currently employed in standard portal technology, for example. In this approach, a user can select preferences for the visual formatting of information such as “overall process status in the top right corner of the screen”, “machine uptime and maintenance log in lower right corner of screen”, “navigation selection through buttons along bottom of screen” and/or “display weekly quantity history in the center of the screen.”
Automatic visualization can be performed by a visualization software process using visualization rules to dynamically construct and format HMI visualization screens based upon the aforementioned configuration settings and data attributes. The visualization can be formatted for display utilizing standard web-browser display devices. Based upon the capabilities of the display device, the size and information content of the visualization screen can be adjusted accordingly. The visualization rules can provide a mechanism to provide plant, process, machine, location, and/or business rules based logic for the presentation and access control of machine or process related information.
An example of a business rule could be to “optimize process finished goods quality, then machine utilization, then material utilization.” If finished goods quality is within specific limits, this can be shown as a simple status indicator. Alternatively, if the finished goods quality is not within limits, detailed quality visualization can be presented. In this aspect, the business rule along with the data itself can determine what information is presented to the user, in what manner and/or in what sequence.
Referring briefly to
In addition, address and interface information related to the data can be employed to change the state or force changes to one or more parameters (e.g., data values) that are displayed. When viewing a particular data value (e.g., tank level), the address provided in one of the tank level attributes can be the means to force the control system to either manually fill or drain the tank. Such attributes can be restricted and only added where such operation is permitted.
In order to set appearance related parameters, the API 520 can be employed to provide a user interface to the ACB 510. The API 520 can be an HMI wherein a plurality of appearance configuration options can be presented to a user. For example, in an editing feature of the API 520, a user can click on a particular aspect of a screen such as the title bar of a particular software application. Once clicked, a properties window can appear before the user to allow changes to be made to the size, color, font etc. associated with the title bar. After such appearance configuration parameters have been modified, a memory (not shown) can be employed for storage and retrieval of the configuration (e.g., skin) at a later time.
The display device 630 can receive formatted data utilizing various protocols, standards and/or media to convey such data. The manner of providing data to the display device can be dependent on the type of processing component 620, the type of display device 630 or both. For example, the data can be transmitted via a plurality of protocols such as RS-232, RS-485, Ethernet, ControlNet, DeviceNet and the like. In one approach, data can be transmitted via parallel cable from a processor to a monitor in a desktop PC. In addition, media such as coaxial cable, fiber optic cable, video cable, etc. can be utilized to facilitate data delivery from the processing device 620 to the display device 630.
The display device 630 can be substantially any type of device that can accept and display data to a user. For example, the display device 630 can be a laptop computer, a desktop computer, a programmable digital assistant, a workstation, a palm top computer, a cell phone, an industrial monitor, a television or a notebook computer. It is to be appreciated that although a single display device is shown, a plurality of display devices can be employed in one approach of the subject invention. The limitations and/or features of a display device 630 can determine the manner in which the data will be formatted.
The display device 630 can have an artificial intelligence (AI) component (not shown) that can determine the best manner in which the data will appear on the display device 630. For example, the AI component can determine that a display device employs a particular video driver and thus modify color and/or resolution related to data conveyed to the display device 630.
In one aspect of the subject invention, visual formatting, as well as attributes, etc. of data can be generated by machine learning wherein one or more training sets of data with examples of desired results and/or undesired results for searches can be utilized to train the system. In another aspect of the subject invention, initial conditions, based on one or more features that indicate desired results, can be utilized. Such initial conditions can be adjusted over time and in response to user actions associated with returned results in order to improve discrimination. For example, results utilized by the user can be employed to train the system to learn desired results for the associated query and results that are ignored by the user can be employed to train the system to learn undesired results of the query. In addition, the frequency of utilization of a result can further enhance such learning. For example, a result that is accessed more times by the user can be deemed more useful to the user. In this manner, if a particular subscriber employs a specific data type more times than another, that data type can be utilized in the future.
In addition, as utilized herein, the term “inference” refers generally to the process of reasoning about or inferring states of the system, environment, and/or user from a set of observations as captured via events and/or data. Inference can be employed to identify a specific context or action, or can generate a probability distribution over states, for example. The inference can be probabilistic—that is, the computation of a probability distribution over states of interest based on a consideration of data and events. Inference can refer to techniques employed for composing higher-level events from a set of events and/or data. Such inference can result in the construction of new events or actions from a set of observed events and/or stored event data, whether or not the events are correlated in close temporal proximity, and whether the events and data come from one or several event and data sources. Various classification schemes and/or systems (e.g., support vector machines, neural networks (e.g., back-propagation, feed forward back propagation, radial bases and fuzzy logic), expert systems, Bayesian networks, and data fusion) can be employed in connection with performing automatic and/or inferred action in connection with the subject invention.
In yet another aspect of the invention, a technique can be employed to anticipate the visualization attributes and display of particular data. For example, information such as historical data representing data and attributes associated with such data utilized with various display devices can be employed to predict the visual formatting of the data with the display device 630. For example, intelligent based decisions based on statistics, probabilities, inferences and classifiers (e.g., explicitly and implicitly trained), including Bayesian learning, Bayesian classifiers and other statistical classifiers, such as decision tree learning methods, support vector machines, linear and non-linear regression and/or neural networks can be employed in accordance with an aspect of the subject invention. In this manner, the AI component (not shown) can be employed by the display device 630 to provide decision making based on learned actions of a particular attribute in relation to the display device 630.
Referring now to
Each network 710-730 can comprise a plurality of devices that are coupled together utilizing various network architectures and/or protocols to facilitate communication between such network devices. Each network 710-730 can accommodate any number of devices that can interface to other components to provide electronic control of one or more processes, for example. In addition, the networks 710-730 can employ one or more servers to channel data from a source (e.g., drive, servo, measurement sensor, temperature sensor, switch, etc.) to a subscriber (e.g., programmable logic controller, computer, digital control system, etc.). Further, such data can be sent from one or more servers to a proxy server employed to accept data from disparate servers within a data driven architecture, such as the system 700.
Data conveyed between the one or more networks 710-730 and the VCS 740 can be sent based on a number of factors. For example, the data can be “pulled” from the networks 710-730 by the VCS 740 on a periodic basis and/or when a particular condition (e.g., specific data exceeds a predetermined value, time, etc.) is met. In addition, the VCS 740 can accept data from one or more networks 710-730 when a particular network attempts to deliver such data. For instance, the network 710 can attempt to deliver data once a specific process related to it is complete. In addition, the VCS 740 can poll the one or more networks to determine when data can be delivered and in what fashion (e.g., size of data, protocol, conduit, etc.) In this manner, data can be exchanged between the networks 710-730 and the VCS 740 in substantially any desired configuration.
The display device 750 can be one or more devices that can accept and display data received to a user. Such a display can occur utilizing a monitor, providing audio sounds, employing telephony and any number of methods and/or systems employed to communicate information to a user. The display device 750 can be an LED scroll bar, marquee, PA system, telephone, stereo, flat screen monitor, etc. In this manner, the data can be conveyed to a user in any desired audio or visual format. Moreover, such formatting can be configured based on attributes related to the data (e.g., channels the data employed to convey such data from a source to subscriber). For instance, attributes can be related to data that employs server A in plant 1 and proxy server 77 in the main plant to be transmitted from a source to a subscriber. In this example, the data can be displayed as text that is italicized and underlined with a font size of 80. Other configurations can be employed based on data attributes that provide inherent and/or programmed visual configuration and/or formatting. One skilled in the art can appreciate the limitless possibilities associated with the formatting and display of data based at least in part upon attributes associated with such data.
Referring now to
At 820, attributes are analyzed which are related to the received data. The attributes can be related to various channels in which the data is conveyed from the source to the component and/or device that receives the data. For example, if data is transmitted from a source to a server X, transmitted from server X to proxy server 17 and then transmitted to a data subscriber, the data channels can be conveyed as attributes and sent along with the data. It is to be appreciated that such attributes can be cumulative based on the various paths/routes/channels employed to convey data from a source to a subscriber, such as the source and the server X, for example. The attributes may not describe the communication path but rather varying degrees of visualization information and/or sophistication. In addition, the data ‘title’ or descriptive name can also be an attribute. Such attributes can be transmitted with the data such that the attributes are received before, after or simultaneous to the reception of the data.
At 830, appearance configuration settings (ACS) are determined. The ACS or “skins” provide a means for a user(s) to set preferences related to appearance related parameters such as color themes, fonts, object sizes and data display preferences. For example, data display preferences could include numerical indication, gauges, bar charts, go/no-go color indicators or a combination of these. At 840, the formatting of the data is modified based on the data attributes and appearance configuration. Such formatting can refer to size, color, font, graphics, etc. employed to display data to a user, as noted above.
At 850, the formatted data is transmitted to a display device and presented to a user. The display device can be substantially any system that can receive data and present such data to a user. For example, the display device can be a monitor, a laptop computer, a PC, a personal digital assistant or a cell phone. The data can be presented to the display device in a specific area of the device (e.g., upper right corner, bottom center, etc.) and/or justified as desired. In addition, the data can be re-sized so that it is proportional in relation to the display (e.g., screen, monitor, etc.) of the device. For example, data displayed to a desktop CRT can be one size and the same data can be re-sized to smaller proportions to be presented in a cell phone display. Once data is presented to the user, he can manipulate the data utilizing any number of programs (e.g., HMI, API, etc.) to make changes to various aspects of the data as desired.
At 920, the data is transmitted from the process to a first server. The server can be employed with any number of server platforms (e.g., hardware and/or software) to provide an engine that drives the server. In addition, the server can be one or more types of servers such as an application server, an audio/video server, a chat server, a fax server, an FTP server, a groupware server, an IRC server, a list server, a mail server, a news server, a proxy server, a telnet server and/or a web server. In addition, the server can be a location where data is stored and/or processed such as a PLC, automation controller, digital control system (DCS) and the like. It is to be appreciated to one skilled in the art that each server can have specific protocols and/or standards related to transmitting and/or receiving data and for the sake of brevity will not be mentioned in detail.
Further, the first server can be located remotely or locally to the location(s) of the data which is gathered. For example, data can be gathered from a single process that encompasses a multitude of disparate locations. Thus, the server can be local with regard to some aspects of the process and remote with other aspects. In addition, the manner in which the data is transmitted can employ wireless and/or wired technologies to convey data from a source to the first server. At 930, the data is transmitted from the first server to a second server employing various protocols, formats, standards and media as mentioned supra. It is to be appreciated that the methods outlined herein are non-exhaustive and that one skilled in the art can appreciate that any number of methods can be employed to transmit and/or receive data from the source to the servers, between servers and from the second server to the device that determines attributes related to the data conveyed.
At 940, attributes associated with the data are determined. As noted, some data sources can provide direct data with a time stamp, for example, while other data can directly support transactional capabilities and still others can support more extensive attributes such as HMI visualization attributes with varying degrees of sophistication. In addition, some devices can perform as servers adding attributes to the data from other devices. Such attributes can be determined utilizing a device and/or process for such purpose. The attributes can be related to the source of the data, the channels employed to convey the data, visualization configuration, etc. After the attributes have been determined, they can be stored in a memory (not shown) or similar storage device to retrieve and utilize at a later time.
At 960, the data is formatted based upon attributes. As noted herein, such data formatting can be accomplished by considering any number of factors such as role and location of a user viewing the data, capabilities of a display device, process to be viewed, time and/or business logic. In addition, formatting can refer to the size, shape, color, associated graphics, etc. of the data as it relates to how the data is presented to a user(s). Further, the data can be formatted at disparate levels such as simple, moderate and complex. For example, data can be presented as a simple multi-color indicator, or complex with specific data points mapped in relation to an associated graphic. By way of further example, data can have various formatting based on user preferences. For instance, particular data can have seven formatting configurations each related to one of seven users.
Turning now to
At 1030, display parameters of the display device are determined. Such display parameters can include bandwidth, dot clock, horizontal scan rate, refresh rate, interlacing, dot pitch, etc. of the device. Further, size of the screen (e.g., 3″, 8″, 14″, 15″, 17″, 20″, etc.) and screen resolution (e.g., 640×480, 800×600, 1024×768 and 1280×1024, etc.) can affect the appearance of visually formatted data. Thus, identically visually formatted data can be presented differently to a user if such data is sent to disparate devices with disparate display parameters. It is to be appreciated that display parameters can be consonant with various display devices. For instance, a cell phone can have a smaller screen and lower resolution than a desktop computer monitor. At 1040, the data is displayed to the user. Data can be displayed based at least upon the visual formatting properties associated with the data and the parameters associated with the display device, as noted above.
With reference to
The system bus 1118 can be any of several types of bus structure(s) including the memory bus or memory controller, a peripheral bus or external bus, and/or a local bus using any variety of available bus architectures including, but not limited to, 8-bit bus, Industrial Standard Architecture (ISA), Micro-Channel Architecture (MSA), Extended ISA (EISA), Intelligent Drive Electronics (IDE), VESA Local Bus (VLB), Peripheral Component Interconnect (PCI), Universal Serial Bus (USB), Advanced Graphics Port (AGP), Personal Computer Memory Card International Association bus (PCMCIA), and Small Computer Systems Interface (SCSI).
The system memory 1116 includes volatile memory 1120 and nonvolatile memory 1122. The basic input/output system (BIOS), containing the basic routines to transfer information between elements within the computer 1112, such as during start-up, is stored in nonvolatile memory 1122. By way of illustration, and not limitation, nonvolatile memory 1122 can include read only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable ROM (EEPROM), or flash memory. Volatile memory 1120 includes 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 synchronous RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), Synchlink DRAM (SLDRAM), and direct Rambus RAM (DRRAM).
Computer 1112 also includes removable/non-removable, volatile/nonvolatile computer storage media.
It is to be appreciated that
A user enters commands or information into the computer 1112 through input device(s) 1136. Input devices 1136 include, but are not limited to, a pointing device such as a mouse, trackball, stylus, touch pad, keyboard, microphone, joystick, game pad, satellite dish, scanner, TV tuner card, digital camera, digital video camera, web camera, and the like. These and other input devices connect to the processing unit 1114 through the system bus 1118 via interface port(s) 1138. Interface port(s) 1138 include, for example, a serial port, a parallel port, a game port, and a universal serial bus (USB). Output device(s) 1140 use some of the same type of ports as input device(s) 1136. Thus, for example, a USB port can be used to provide input to computer 1112, and to output information from computer 1112 to an output device 1140. Output adapter 1142 is provided to illustrate that there are some output devices 1140 like monitors, speakers, and printers, among other output devices 1140, which require special adapters. The output adapters 1142 include, by way of illustration and not limitation, video and sound cards that provide a means of connection between the output device 1140 and the system bus 1118. It should be noted that other devices and/or systems of devices provide both input and output capabilities such as remote computer(s) 1144.
Computer 1112 can operate in a networked environment using logical connections to one or more remote computers, such as remote computer(s) 1144. The remote computer(s) 1144 can be a personal computer, a server, a router, a network PC, a workstation, a microprocessor based appliance, a peer device or other common network node and the like, and typically includes many or all of the elements described relative to computer 1112. For purposes of brevity, only a memory storage device 1146 is illustrated with remote computer(s) 1144. Remote computer(s) 1144 is logically connected to computer 1112 through a network interface 1148 and then physically connected via communication connection 1150. Network interface 1148 encompasses communication networks such as local-area networks (LAN) and wide-area networks (WAN). LAN technologies include Fiber Distributed Data Interface (FDDI), Copper Distributed Data Interface (CDDI), Ethernet/IEEE 802.3, Token Ring/IEEE 802.5 and the like. WAN technologies include, but are not limited to, point-to-point links, circuit switching networks like Integrated Services Digital Networks (ISDN) and variations thereon, packet switching networks, and Digital Subscriber Lines (DSL).
Communication connection(s) 1150 refers to the hardware/software employed to connect the network interface 1148 to the bus 1118. While communication connection 1150 is shown for illustrative clarity inside computer 1112, it can also be external to computer 1112. The hardware/software necessary for connection to the network interface 1148 includes, for exemplary purposes only, internal and external technologies such as, modems including regular telephone grade modems, cable modems and DSL modems, ISDN adapters, and Ethernet cards.
One possible communication between a client 1202 and a server 1204 can be in the form of a data packet transmitted between two or more computer processes. The system 1200 further includes a communication framework 1208 that can be employed to facilitate communications between the client(s) 1202 and the server(s) 1204. The client(s) 1202 can interface with one or more client data store(s) 1210, which can be employed to store information local to the client(s) 1202. Similarly, the server(s) 1204 can interface with one or more server data store(s) 1206, which can be employed to store information local to the servers 1204.
What has been described above includes examples of the subject invention. It is, of course, not possible to describe every conceivable combination of components or methodologies for purposes of describing the subject invention, but one of ordinary skill in the art can recognize that many further combinations and permutations of the subject invention are possible. Accordingly, the subject invention is intended to embrace all such alterations, modifications and variations that fall within the spirit and scope of the appended claims. In this regard, it will also be recognized that the invention includes a system as well as a computer-readable medium having computer-executable instructions for performing the steps of the various methods of the invention. In addition, while a particular feature of the invention may have been disclosed with respect to only one of several aspects or implementations of the invention, such a feature can be combined with one or more other features of the other implementations as may be desired and advantageous for any given or particular application. Furthermore, to the extent that the terms “includes”, “including”, “has”, “having”, and variants thereof are used in either the detailed description or the claims, these terms are intended to be inclusive in a manner similar to the term “comprising” and its variants.
The subject application is a continuation of U.S. patent application Ser. No. 10/955,460, entitled “SYSTEMS AND METHODS FOR AUTOMATIC VISUALIZATION CONFIGURATION,” and filed on Sep. 30, 2004. The entirety of the aforementioned application is incorporated herein by reference.
Number | Name | Date | Kind |
---|---|---|---|
4268901 | Subrizi et al. | May 1981 | A |
4347564 | Sugano et al. | Aug 1982 | A |
4623964 | Getz et al. | Nov 1986 | A |
5072374 | Sexton et al. | Dec 1991 | A |
5185708 | Hall et al. | Feb 1993 | A |
5253184 | Kleinschnitz | Oct 1993 | A |
5282244 | Fuller et al. | Jan 1994 | A |
5301320 | McAtee et al. | Apr 1994 | A |
5446868 | Gardea et al. | Aug 1995 | A |
5455775 | Huber et al. | Oct 1995 | A |
5485620 | Sadre et al. | Jan 1996 | A |
5504891 | Motoyama et al. | Apr 1996 | A |
5537585 | Blickenstaff et al. | Jul 1996 | A |
5572731 | Morel et al. | Nov 1996 | A |
5611059 | Benton et al. | Mar 1997 | A |
5619724 | Moore | Apr 1997 | A |
5634048 | Ryu et al. | May 1997 | A |
5644740 | Kiuchi | Jul 1997 | A |
5675748 | Ross | Oct 1997 | A |
5715413 | Ishai et al. | Feb 1998 | A |
5721905 | Elixmann et al. | Feb 1998 | A |
5761499 | Sonderegger | Jun 1998 | A |
5790935 | Payton | Aug 1998 | A |
5797137 | Golshani et al. | Aug 1998 | A |
5812773 | Norin | Sep 1998 | A |
5828851 | Nixon et al. | Oct 1998 | A |
5832486 | Itoh et al. | Nov 1998 | A |
5838563 | Dove et al. | Nov 1998 | A |
5848273 | Fontana et al. | Dec 1998 | A |
5859978 | Sonderegger et al. | Jan 1999 | A |
5862052 | Nixon et al. | Jan 1999 | A |
5884025 | Baehr et al. | Mar 1999 | A |
5884033 | Duvall et al. | Mar 1999 | A |
5913029 | Shostak | Jun 1999 | A |
5924094 | Sutter | Jul 1999 | A |
5936539 | Fuchs | Aug 1999 | A |
5940294 | Dove | Aug 1999 | A |
5940854 | Green, Jr. et al. | Aug 1999 | A |
5951440 | Reichlinger | Sep 1999 | A |
5960420 | Leymann et al. | Sep 1999 | A |
5966705 | Koneru | Oct 1999 | A |
5970494 | Velissaropoulos et al. | Oct 1999 | A |
5978577 | Rierden et al. | Nov 1999 | A |
5980078 | Krivoshein et al. | Nov 1999 | A |
5983016 | Brodsky et al. | Nov 1999 | A |
5997167 | Crater et al. | Dec 1999 | A |
6011899 | Ohishi et al. | Jan 2000 | A |
6032208 | Nixon et al. | Feb 2000 | A |
6044217 | Brealey et al. | Mar 2000 | A |
6061740 | Ferguson et al. | May 2000 | A |
6063129 | Dadd et al. | May 2000 | A |
6081899 | Byrd | Jun 2000 | A |
6098116 | Nixon et al. | Aug 2000 | A |
6101531 | Eggleston et al. | Aug 2000 | A |
6115713 | Pascucci et al. | Sep 2000 | A |
6157864 | Schwenke et al. | Dec 2000 | A |
6195591 | Nixon et al. | Feb 2001 | B1 |
6208987 | Nihei | Mar 2001 | B1 |
6222540 | Sacerdoti | Apr 2001 | B1 |
6234899 | Nulph | May 2001 | B1 |
6266726 | Nixon et al. | Jul 2001 | B1 |
6268853 | Hoskins et al. | Jul 2001 | B1 |
6275977 | Nagai et al. | Aug 2001 | B1 |
6308168 | Dovich et al. | Oct 2001 | B1 |
6308224 | Leymann et al. | Oct 2001 | B1 |
6311187 | Jeyaraman | Oct 2001 | B1 |
6327511 | Naismith et al. | Dec 2001 | B1 |
6336152 | Richman et al. | Jan 2002 | B1 |
6356920 | Vandersluis | Mar 2002 | B1 |
6377957 | Jeyaraman | Apr 2002 | B1 |
6393566 | Levine | May 2002 | B1 |
6398106 | Ulvr et al. | Jun 2002 | B1 |
6409082 | Davis et al. | Jun 2002 | B1 |
6411987 | Steger et al. | Jun 2002 | B1 |
6415983 | Ulvr et al. | Jul 2002 | B1 |
6425051 | Burton et al. | Jul 2002 | B1 |
6438744 | Toutonghi et al. | Aug 2002 | B2 |
6445963 | Blevins et al. | Sep 2002 | B1 |
6446202 | Krivoshein et al. | Sep 2002 | B1 |
6457053 | Satagopan et al. | Sep 2002 | B1 |
6469986 | Lecheler et al. | Oct 2002 | B1 |
6473656 | Langels et al. | Oct 2002 | B1 |
6477435 | Ryan et al. | Nov 2002 | B1 |
6484061 | Papadopoulos et al. | Nov 2002 | B2 |
6501996 | Bieber | Dec 2002 | B1 |
6505247 | Steger et al. | Jan 2003 | B1 |
6510352 | Badavas et al. | Jan 2003 | B1 |
6539271 | Lech et al. | Mar 2003 | B2 |
6539430 | Humes | Mar 2003 | B1 |
6539458 | Holmberg | Mar 2003 | B2 |
6571282 | Bowman-Amuah | May 2003 | B1 |
6615091 | Birchenough et al. | Sep 2003 | B1 |
6631519 | Nicholson et al. | Oct 2003 | B1 |
6643555 | Eller et al. | Nov 2003 | B1 |
6661426 | Jetha et al. | Dec 2003 | B1 |
6664981 | Ashe et al. | Dec 2003 | B2 |
6676309 | Shima | Jan 2004 | B2 |
6681227 | Fujiwara et al. | Jan 2004 | B1 |
6687817 | Paul | Feb 2004 | B1 |
6697797 | Hoggatt et al. | Feb 2004 | B1 |
6704746 | Sokolov et al. | Mar 2004 | B2 |
6714949 | Frey, Jr. | Mar 2004 | B1 |
6714981 | Skaggs | Mar 2004 | B1 |
6738821 | Wilson et al. | May 2004 | B1 |
6745089 | Rasmussen et al. | Jun 2004 | B2 |
6748486 | Burton et al. | Jun 2004 | B2 |
6751634 | Judd | Jun 2004 | B1 |
6758403 | Keys et al. | Jul 2004 | B1 |
6760721 | Chasen et al. | Jul 2004 | B1 |
6760732 | Busshart et al. | Jul 2004 | B2 |
6763395 | Austin | Jul 2004 | B1 |
6766312 | Landt | Jul 2004 | B2 |
6768987 | Couch et al. | Jul 2004 | B1 |
6769095 | Brassard et al. | Jul 2004 | B1 |
6772144 | Brid | Aug 2004 | B2 |
6778537 | Ishibashi | Aug 2004 | B1 |
6807632 | Carpentier et al. | Oct 2004 | B1 |
6809732 | Zatz et al. | Oct 2004 | B2 |
6832120 | Frank et al. | Dec 2004 | B1 |
6836892 | Ikoma et al. | Dec 2004 | B2 |
6839790 | Barros De Almeida et al. | Jan 2005 | B2 |
6842769 | Kim et al. | Jan 2005 | B1 |
6853920 | Hsiung et al. | Feb 2005 | B2 |
6865509 | Hsiung et al. | Mar 2005 | B1 |
6868413 | Grindrod et al. | Mar 2005 | B1 |
6874145 | Ye et al. | Mar 2005 | B1 |
6874146 | Iyengar | Mar 2005 | B1 |
6880060 | Talagala et al. | Apr 2005 | B2 |
6889282 | Schollenberger | May 2005 | B2 |
6901403 | Bata | May 2005 | B1 |
6901578 | Beaven et al. | May 2005 | B1 |
6904450 | King et al. | Jun 2005 | B1 |
6904473 | Bloxham et al. | Jun 2005 | B1 |
6920474 | Walsh et al. | Jul 2005 | B2 |
6928521 | Burton et al. | Aug 2005 | B1 |
6930985 | Rathi et al. | Aug 2005 | B1 |
6934749 | Black et al. | Aug 2005 | B1 |
6938079 | Anderson et al. | Aug 2005 | B1 |
6944626 | Cameron et al. | Sep 2005 | B2 |
6947947 | Block et al. | Sep 2005 | B2 |
6950900 | McKean et al. | Sep 2005 | B1 |
6954770 | Carlson et al. | Oct 2005 | B1 |
6961728 | Wynblatt et al. | Nov 2005 | B2 |
6966033 | Gasser et al. | Nov 2005 | B1 |
6973556 | Milligan et al. | Dec 2005 | B2 |
6975913 | Kreidler et al. | Dec 2005 | B2 |
6985902 | Wise et al. | Jan 2006 | B2 |
7000017 | McGill et al. | Feb 2006 | B1 |
7031782 | Kappelhoff et al. | Apr 2006 | B2 |
7065714 | Theel et al. | Jun 2006 | B1 |
7072934 | Helgeson | Jul 2006 | B2 |
7093207 | Liao et al. | Aug 2006 | B1 |
7146355 | Chu-Carroll | Dec 2006 | B2 |
7162312 | Gross et al. | Jan 2007 | B2 |
7171476 | Maeda et al. | Jan 2007 | B2 |
7197715 | Valeria | Mar 2007 | B1 |
7225193 | Mets et al. | May 2007 | B2 |
7242988 | Hoffberg et al. | Jul 2007 | B1 |
7251193 | Jung | Jul 2007 | B2 |
7251222 | Chen et al. | Jul 2007 | B2 |
7272660 | Powers | Sep 2007 | B1 |
7308454 | Abineri et al. | Dec 2007 | B2 |
7315985 | Gauvin et al. | Jan 2008 | B1 |
7461158 | Rider et al. | Dec 2008 | B2 |
7565610 | Li et al. | Jul 2009 | B2 |
7603458 | Sexton et al. | Oct 2009 | B1 |
7610559 | Humpleman et al. | Oct 2009 | B1 |
20020007286 | Okamoto | Jan 2002 | A1 |
20020012401 | Karolys et al. | Jan 2002 | A1 |
20020013748 | Edmison et al. | Jan 2002 | A1 |
20020069167 | Conlow | Jun 2002 | A1 |
20020070965 | Austin | Jun 2002 | A1 |
20020073236 | Helgeson et al. | Jun 2002 | A1 |
20020087786 | Burton et al. | Jul 2002 | A1 |
20020091838 | Rupp et al. | Jul 2002 | A1 |
20020103785 | Harvey | Aug 2002 | A1 |
20020131404 | Mehta et al. | Sep 2002 | A1 |
20020161827 | Brault | Oct 2002 | A1 |
20020188366 | Pepper et al. | Dec 2002 | A1 |
20020194577 | Connor et al. | Dec 2002 | A1 |
20030014387 | Kreidler et al. | Jan 2003 | A1 |
20030036876 | Fuller et al. | Feb 2003 | A1 |
20030058280 | Molinari | Mar 2003 | A1 |
20030065673 | Grobler et al. | Apr 2003 | A1 |
20030090514 | Cole et al. | May 2003 | A1 |
20030120710 | Pulsipher et al. | Jun 2003 | A1 |
20030123467 | Du et al. | Jul 2003 | A1 |
20030126195 | Reynolds et al. | Jul 2003 | A1 |
20030126308 | Kim | Jul 2003 | A1 |
20030135609 | Carlson et al. | Jul 2003 | A1 |
20030172145 | Nguyen | Sep 2003 | A1 |
20030177114 | Lin et al. | Sep 2003 | A1 |
20030184584 | Vachuska et al. | Oct 2003 | A1 |
20030212828 | Miyazaki et al. | Nov 2003 | A1 |
20030218641 | Longobardi | Nov 2003 | A1 |
20030233427 | Taguchi | Dec 2003 | A1 |
20040006401 | Yamada et al. | Jan 2004 | A1 |
20040024812 | Park | Feb 2004 | A1 |
20040024995 | Swaine | Feb 2004 | A1 |
20040044421 | Brune et al. | Mar 2004 | A1 |
20040073565 | Kaufman et al. | Apr 2004 | A1 |
20040098153 | Neudeck | May 2004 | A1 |
20040098269 | Wise et al. | May 2004 | A1 |
20040117624 | Brandt et al. | Jun 2004 | A1 |
20040153171 | Brandt et al. | Aug 2004 | A1 |
20040167790 | Grasse | Aug 2004 | A1 |
20040168115 | Bauernschmidt | Aug 2004 | A1 |
20040193449 | Wildman et al. | Sep 2004 | A1 |
20040196855 | Davies et al. | Oct 2004 | A1 |
20040199655 | Davies et al. | Oct 2004 | A1 |
20040203620 | Thome et al. | Oct 2004 | A1 |
20040210629 | Klindt et al. | Oct 2004 | A1 |
20040249771 | Berg et al. | Dec 2004 | A1 |
20040260591 | King | Dec 2004 | A1 |
20040268186 | Maturana et al. | Dec 2004 | A1 |
20050005289 | Adolph et al. | Jan 2005 | A1 |
20050007249 | Eryurek | Jan 2005 | A1 |
20050015397 | Abineri et al. | Jan 2005 | A1 |
20050043922 | Weidl et al. | Feb 2005 | A1 |
20050044112 | Yamamoto et al. | Feb 2005 | A1 |
20050065626 | Kappelhoff et al. | Mar 2005 | A1 |
20050065829 | Birkhoelzer | Mar 2005 | A1 |
20050065971 | Honda | Mar 2005 | A1 |
20050069853 | Tyson et al. | Mar 2005 | A1 |
20050091349 | Scheibli | Apr 2005 | A1 |
20050102672 | Brothers | May 2005 | A1 |
20050107897 | Callaghan | May 2005 | A1 |
20050108247 | Heinla et al. | May 2005 | A1 |
20050120021 | Tang et al. | Jun 2005 | A1 |
20050129247 | Gammel et al. | Jun 2005 | A1 |
20050135782 | Ando et al. | Jun 2005 | A1 |
20050154741 | Hebert et al. | Jul 2005 | A1 |
20050154995 | Miller | Jul 2005 | A1 |
20050166215 | Holloway et al. | Jul 2005 | A1 |
20050177687 | Rao | Aug 2005 | A1 |
20050187925 | Schechinger et al. | Aug 2005 | A1 |
20050193118 | Le et al. | Sep 2005 | A1 |
20050198247 | Perry et al. | Sep 2005 | A1 |
20050198248 | Morimoto et al. | Sep 2005 | A1 |
20050216460 | Yoon et al. | Sep 2005 | A1 |
20050223010 | Murray | Oct 2005 | A1 |
20050251527 | Phillips et al. | Nov 2005 | A1 |
20050256788 | Mukai | Nov 2005 | A1 |
20050268253 | Johnson et al. | Dec 2005 | A1 |
20050278373 | Corbett et al. | Dec 2005 | A1 |
20060004475 | Brackett et al. | Jan 2006 | A1 |
20060004847 | Claudatos et al. | Jan 2006 | A1 |
20060064428 | Colaco et al. | Mar 2006 | A1 |
20060173895 | Engquist et al. | Aug 2006 | A1 |
20060195817 | Moon | Aug 2006 | A1 |
20060212855 | Bournas et al. | Sep 2006 | A1 |
20060277498 | Mann et al. | Dec 2006 | A1 |
20070268922 | Dougan et al. | Nov 2007 | A1 |
Entry |
---|
Office Action dated Jun. 27, 2007 for U.S. Appl. No. 10/955,460, 19 pages. |
Office Action dated Mar. 10, 2008 for U.S. Appl. No. 10/955,460, 15 pages. |
Office Action dated Oct. 3, 2008 for U.S. Appl. No. 10/955,460, 27 pages. |
Office Action dated Oct. 28, 2009 for U.S. Appl. No. 10/955,460, 40 pages. |
Office Action dated Apr. 16, 2010 for U.S. Appl. No. 10/955,460, 51 pages. |
Office Action dated May 10, 2012 for U.S. Appl. No. 10/955,460, 48 pages. |
Notice of Allowance dated Feb. 5, 2014 for U.S. Appl. No. 10/955,460, 107 pages. |
Gasser et al.; method and Apparatus for Representing resource in a Computer System Environment. May 18, 2001; 60 pages. |
Morrie Gasser; Method and Apparatus for Presenting information to a user of a Computer system. Apr. 10, 2000. |
Office Action dated Nov. 16, 2009 for U.S. Appl. No. 11/238,607, 84 pages. |
Office Action dated Oct. 28, 2008 for U.S. Appl. No. 11/240,335, 15 pages. |
ISR dated Jun. 19, 2008 for PCT Application No. PCT/ US06/ 18350, 2 pages. |
Office Action dated Apr. 15, 2009 for U.S. Appl. No. 11/240,335, 10 pages. |
Office Action dated May 15, 2008 for U.S. Appl. No. 11/240,335, 31 pages. |
Office Action dated Oct. 8, 2008 for U.S. Appl. No. 11/238,607, 32 pages. |
ISR dated Jul. 7, 2008 for PCT Application No. PCT/ US06/ 18180, 2 pages. |
Office Action dated Mar. 6, 2009 for U.S. Appl. No. 11/238,607, 61 pages. |
Office Action dated Apr. 2, 2008 for U.S. Appl. No. 11/238,607, 37 pages. |
Office Action dated Jun. 3, 2009 for U.S. Appl. No. 11/238,606, 25 pages. |
Office Action dated Jul. 2, 2008 for U.S. Appl. No. 11/238,606, 17 pages. |
Office Action dated Jan. 18, 2008 U.S. Appl. No. 11/238,606, 8 pages. |
Office Action dated Nov. 20, 2008 for U.S. Appl. No. 11/238,606, 19 pages. |
Office Action dated Apr. 22, 2008 for U.S. Appl. No. 11/238,537, 48 pages. |
Office Action dated Apr. 15, 2009 for U.S. Appl. No. 11/238,537, 22 pages. |
Ozsoyoglu, et al. Database Systems for Programmable Logic Contollers. Last accessed Apr. 15, 2009, 17 pages. |
Office Action dated Oct. 20, 2008 for U.S. Appl. No. 11/238,537, 44 pages. |
ISR dated May 6, 2008 for PCT Application No. PCT/ US06/ 18122, 1 page. |
ISR dated Jan. 24, 2008 for PCT Application No. PCT/ US06/ 18238, 1 page. |
Office Action dated May 1, 2009 for U.S. Appl. No. 11/239,567, 35 pages. |
Office Action dated May 30, 2008 for U.S. Appl. No. 11/239,567, 29 pages. |
International Search Report and Written Opinion for PCT Application No. PCT/US06/18181 dated Mar. 4, 2008, 2 pages. |
Pitzek et al., Configuration and Management of a Real-Time Smart Transducer Network, 2003 IEEE, 2003, 4 pages. |
European Search Report dated Jun. 12, 2005 for European Patent Application Serial No. EP05016793, 3 pages. |
John Kubiatowicz, et al. “OceanStore: An Architecture for Global-Scale Persistent Storage” ASPLOS 2000, Cambridge, Massachusetts (2000). |
Roy Goldman, et al. “From Semistructured Data to XML: Migrating the Lore Data Model and Query Language” (1999). |
SOFA/DCUP: Architecture for Component Trading and Dynamic Updating, by Plasil et al., Proceedings of the International Conference on Configurable Distributed Systems, p. 43, 1998, ISBN:O-8186-8451-8, 16 pages. |
Office Action dated Oct. 9, 2009 for U.S. Appl. No. 11/239,567, 41 pages. |
Office Action dated Nov. 14, 2008 for U.S. Appl. No. 11/239,567, 34 pages. |
Office Action dated Nov. 2, 2007 for U.S. Appl. No. 11/239,567,23 pages. |
ISR dated Jul. 7, 2008 for PCT Application No. PCT/US06/18180, 8 pgs. |
Number | Date | Country | |
---|---|---|---|
20140225895 A1 | Aug 2014 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 10955460 | Sep 2004 | US |
Child | 14254383 | US |