US6148306A
Expired / Lapsed
US
⏱️ 0.0 years remaining
Data structure for scheduled execution of commands in a facilities management control system
Assignee: Johnson Controls Technology Co
•
Filing: 1998-05-28
•
Granted: 2000-11-14
•
Expires: 2018-05-28
Abstract
Abstract An apparatus enables a controller to be programmed without being dependent upon a particular type of programming tool. This independence is accomplished by providing data structures in the controller which define a table of executable commands along with a set of rules associated with use of each command. Upon being connected to the controller, a programming tool downloads the valid commands and command usage rules for that particular controller. This enables a generic programming tool to be used with a variety of controllers that have different commands and usage rules. For a facilities management system, the controller stores a plurality of daily control strategies which specify events that call for execution of a particular sequence of commands.
Inventors
- 👤 Neal John Seidl
- 👤 August Antony Divjak
- 👤 Uday Ramchandra Kelkar
Bibliographic Details
Application Number
—
Jurisdiction
US
Data Source
google_patents
Last Synchronized
2026-11-07 10:44
CPC Classifications
G; G05; G05B; G05B19/00; G05B19/02; G05B19/04; G05B19/042; G05B19/0426; G05B2219/00; G05B2219/20; G05B2219/23; G05B2219/23077; G05B2219/23193; G05B2219/23195; G05B2219/25; G05B2219/25419; G05B2219/26; G05B2219/2614; Y; Y10; Y10S; Y10S707/00; Y10S707/99941; Y10S707/99944; Y10S707/99945; Y10S707/99948
Claims Analysis
Total Claims: 23
Claim 1
Independent Claim
130 words
A memory for storing a data structure defining command data and schedule data for operating a controller comprising: a variable length command table data structure for storing a set of executable commands, each of the commands having at least one context rule for defining the use of the command with respect to a sequence of selected commands; said command table data structure including a first variable specifying the quantity of daily strategies, and a second variable specifying the quantity of commands which may be used within a strategy, a command identification field associated with each command in the command table data structure; and a strategy table data structure containing a plurality of daily strategies each of which defines how to operate the controller on a different day that is specified.
Claim 2
Dependent Claim
130 words
A memory for storing a data structure defining command data and schedule data for operating a controller comprising: a variable length command table data structure for storing a set of executable commands, each of the commands having at least one context rule for defining the use of the command with respect to a sequence of selected commands; said command table data structure including a first variable specifying the quantity of daily strategies, and a second variable specifying the quantity of commands which may be used within a strategy, a command identification field associated with each command in the command table data structure; and a strategy table data structure containing a plurality of daily strategies each of which defines how to operate the controller on a different day that is specified.
Claim 3
Dependent Claim
36 words
The memory of claim 1 wherein each command includes a context rule defining which commands, when active, preclude the command from being selected into a sequence of commands defining a set of events within the strategy.
Claim 4
Dependent Claim
27 words
The memory of claim 2 wherein the context rule is an N element bit array where N is also the number of commands within the command table.
Claim 5
Dependent Claim
39 words
The memory of claim 1 wherein each command includes a context rule defining which commands are required to be active prior to the command being selected into a sequence of commands defining a set of events within the strategy.
Claim 6
Dependent Claim
27 words
The memory of claim 4 wherein the context rule is an N element bit array where N is also the number of commands within the command table.
Claim 7
Dependent Claim
41 words
The memory of claim 1 wherein each command includes a context rule defining which commands, if previously in effect, will be nullified by the current command being selected into a sequence of commands defining a set of events within the strategy.
Claim 8
Dependent Claim
27 words
The memory of claim 6 wherein the context rule is an N element bit array where N is also the number of commands within the command table.
Claim 9
Dependent Claim
57 words
The memory of claim 1 further including a schedule table data structure for storing the schedule data, the schedule table data structure including a weekly schedule table for storing a set of weekly strategies, a holiday schedule table for storing a set of holiday strategies, and an exception schedule table for storing a set of exception strategies.
Claim 10
Dependent Claim
35 words
The memory of claim 1 wherein a variable N has a value that equals the number of commands, and wherein N is defined by 8 times the second variable of the command table data structure.
Claim 11
Independent Claim
163 words
A system including a tool for programming a controller with a sequence of events which are selected by a system operator comprising: a data structure for storing a set of commands which can be executed by the controller, each of the commands having at least one context rule for defining the use of the command with respect to a sequence of selected commands; a validation engine associated with the tool, the validation engine maintaining a state table for tracking an outcome associated with the sequence of events, and the validation engine implementing a validation algorithm for validating the sequence of events; and an interface for providing data flow between the controller and the tool, whereby the validation engine gains access to the data structure for allowing the system operator to create the sequence of events, and for allowing the validation engine to apply the validation algorithm against the at least one context rule of each of the commands within the sequence of events.
Claim 12
Independent Claim
163 words
A system including a tool for programming a controller with a sequence of events which are selected by a system operator comprising: a data structure for storing a set of commands which can be executed by the controller, each of the commands having at least one context rule for defining the use of the command with respect to a sequence of selected commands; a validation engine associated with the tool, the validation engine maintaining a state table for tracking an outcome associated with the sequence of events, and the validation engine implementing a validation algorithm for validating the sequence of events; and an interface for providing data flow between the controller and the tool, whereby the validation engine gains access to the data structure for allowing the system operator to create the sequence of events, and for allowing the validation engine to apply the validation algorithm against the at least one context rule of each of the commands within the sequence of events.
Claim 13
Dependent Claim
16 words
The system of claim 10 wherein each command within the data structure includes three context rules.
Claim 14
Dependent Claim
34 words
The system of claim 10 wherein each of the commands includes a context rule defining which commands, when active, preclude the command from being selected into the sequence of selected commands defining a strategy.
Claim 15
Dependent Claim
27 words
The system of claim 12 wherein the context rule is an N element bit array where N is also the number of commands within the data structure.
Claim 16
Dependent Claim
37 words
The system of claim 10 wherein each of the commands includes a context rule defining which commands are required to be active prior to the command being selected into the sequence of selected commands defining a strategy.
Claim 17
Dependent Claim
27 words
The system of claim 14 wherein the context rule is an N element bit array where N is also the number of commands within the data structure.
Claim 18
Dependent Claim
39 words
The system of claim 10 wherein each of the commands includes a context rule defining which commands, if previously in effect, will be nullified by the current command being selected into the sequence of selected commands defining a strategy.
Claim 19
Dependent Claim
27 words
The system of claim 16 wherein the context rule is an N element bit array where N is also the number of commands within the data structure.
Claim 20
Independent Claim
180 words
A method for validating a sequence of events forming a strategy within a schedule for use with a controller comprising the steps of: providing a command table for storing a plurality of commands, said command table including a data structure having a command identification field and a plurality of command rule fields for defining context rules associated, with each command; accessing the command table with a controller independent scheduling tool for interpreting the commands and applying the context rules associated with each command for creating a strategy; selecting a command from the command table and associating the command with an execution time for defining an event within the strategy; validating each command within the strategy by applying a validation algorithm to the command rule fields of each command; repeating the steps of selecting and validating for creating said sequence of events until at least one validated strategy is defined; organizing the strategies into a schedule table; providing a processor within the controller for interpreting the schedule table; and executing the strategy stored in the schedule table for operating the controller.
Claim 21
Independent Claim
180 words
A method for validating a sequence of events forming a strategy within a schedule for use with a controller comprising the steps of: providing a command table for storing a plurality of commands, said command table including a data structure having a command identification field and a plurality of command rule fields for defining context rules associated, with each command; accessing the command table with a controller independent scheduling tool for interpreting the commands and applying the context rules associated with each command for creating a strategy; selecting a command from the command table and associating the command with an execution time for defining an event within the strategy; validating each command within the strategy by applying a validation algorithm to the command rule fields of each command; repeating the steps of selecting and validating for creating said sequence of events until at least one validated strategy is defined; organizing the strategies into a schedule table; providing a processor within the controller for interpreting the schedule table; and executing the strategy stored in the schedule table for operating the controller.
Claim 22
Dependent Claim
34 words
The method of claim 18 further including the step of maintaining a state table which is updated by the validation algorithm, the state table tracking the current state of the commands within the strategy.
Claim 23
Dependent Claim
20 words
The method of claim 18 wherein the plurality of command rule fields is defined by three command context rule fields.
References Cited (Backward Citations)
USPTO Annuity & Maintenance Windows
| Annuity Stage | Window Opens | Payment Deadline | Surcharge Period Until | Estimated Fee | Status |
|---|---|---|---|---|---|
| 3.5 Years (Year 4) | 2003-11-14 | 2004-05-15 | 2004-11-14 | $2000.00 | Window Closed / Lapsed |
| 7.5 Years (Year 8) | 2007-11-14 | 2008-05-15 | 2008-11-14 | $3760.00 | Window Closed / Lapsed |
| 11.5 Years (Year 12) | 2011-11-14 | 2012-05-15 | 2012-11-14 | $7700.00 | Window Closed / Lapsed |