DETAILED ACTION
Notice of Pre-AIA or AIA Status
The present application, filed on or after March 16, 2013, is being examined under the first inventor to file provisions of the AIA .
Information Disclosure Statement
The information disclosure statements (IDSs) submitted on May 1, 2026, November 18, 2024 and September 6, 2026 are in compliance with the provisions of 37 CFR 1.97. Accordingly, the IDSs have been considered by the examiner.
Claim Status
In the August 30, 2024 submission, claims 1-20 were presented for consideration, and are pending.
Claim Rejections - 35 USC § 112
The following is a quotation of 35 U.S.C. 112(b):
(b) CONCLUSION.—The specification shall conclude with one or more claims particularly pointing out and distinctly claiming the subject matter which the inventor or a joint inventor regards as the invention.
The following is a quotation of 35 U.S.C. 112 (pre-AIA ), second paragraph:
The specification shall conclude with one or more claims particularly pointing out and distinctly claiming the subject matter which the applicant regards as his invention.
Claims 1-20 are rejected under 35 U.S.C. 112(b) or 35 U.S.C. 112 (pre-AIA ), second paragraph, as being indefinite for failing to particularly point out and distinctly claim the subject matter which the inventor or a joint inventor (or for applications subject to pre-AIA 35 U.S.C. 112, the applicant), regards as the invention.
Claims 1, 12 and 18 are rejected under 35 U.S.C. 112(b) or 35 U.S.C. 112 (pre-AIA ), second paragraph, as being incomplete for omitting essential elements, relationships and steps, such omission amounting to a gap between the elements, relationships and steps used in distinguishing a deterministic mode respective of a control algorithm, how it prioritizes communication and violation requirements effect equipment operations. See MPEP § 2172.01.
Regarding claim 1, the claim focuses on a building controller providing low latency control, wherein one or more memory devices having instructions executed on a processor enters a deterministic communication mode, and prioritize communications which affects equipment operations. In review of the art, the claim appears to lend to the general use of computers and/or system controllers in implementing building management systems (BMS) applications to control and manage various operational functions and prioritize communications to various components within the system, generally used in the art. However, the claim fails to provide support for the use of a control algorithm and how the algorithm is employed in affecting equipment operations using prioritized communication.
In terms of the control algorithm, [at least] par. 141 and 151 of the specification cites the following:
[0141] The controllers on network 570 may be responsible for providing control using several control algorithms. Each control algorithm may operate in one of many states (or modes), each requiring different sensor telemetry to perform the necessary function. COV s subscribed may be configured for the speed of communication and accuracy necessary during active control. With reference to FIG. 5B, controller 530 executes economizer damper control in some embodiments. The economizer cooling control algorithm 591 has three states in some embodiments. Economizer control algorithm may include mechanical cooling mode 592, economizer unavailable mode 593, and free cooling mode 594. Various conditions may cause the algorithm to transition from one state to another. For example, if the outside air temperature (Toa) becomes greater than an economizer availability threshold (Tecon), economizer cooling control algorithm 591 may transition to economizer unavailable mode 593. According to some embodiments, in mechanical cooling mode 592 the economizer damper remains at its maximum opening, and in economizer unavailable mode 593 the economizer damper remains at its minimum opening. Thus, in some embodiments, the outside air damper is only modulated to maintain a supply air temperature in one of the three modes of operation. For example, control algorithm 591 only requires measurements of the supply air temperature when in active control mode free cooling mode 594. Various control algorithms may have other sets of modes, some of which may include an active control loop. Active control modes may be entered based on a transition defined by a variable (e.g., the transitions shown in FIG. 5B), based on schedules (e.g., at the beginning of the occupied portion of the day), or based on the operational sequence of the device ( e.g., during the performance of calculations for a particular portion of a control algorithm).
[0151] In general, the processes of receiving data from sensors or other control devices,
sending data and/or commands to actuators, and performing the calculations required by the control logic may be done in parallel or in series. In parallel-type operation, the operations may be queued as required by controller coordinator 742 for execution and executed asynchronously. For example, a control algorithm may execute using the latest measurement currently stored in the controller for a measurement required to perform control. In series-type operation, controller coordinator 742 may execute sequences in a defined sequence. For example, controller coordinator 742 may determine the order that control algorithms must run, poll sensors for current information related to the information required for the currently executing control algorithm, perform the calculations of the control algorithm, and then send the results to the actuators before moving to the next control logic module. Building controller 720 may be configured to switch between series and parallel operation or run certain operations in series while running others in parallel. Series operations may be considered a prioritized form of communication as the building controller 720 purposely gets the latest sensor values when needed or may maintain the communication token until the operations of a control logic module are complete.
While the specification notes various embodiments and active functions which rely and employ the use of one or more control algorithms, application of the algorithm appears to depend on a relationship(s) with both the BMS and elements of the system (e.g., as input), as well as facilitate output and control parameters to elements of the system. As presented, the claim cites entry of a deterministic mode based on a control algorithm, and prioritize communication related to a control algorithm. However, the claim does not provide support detailing the relationship between the control algorithm and priority taken by the system.
Regarding prioritizing operational functions, the specification cites multiple applications and instances in which operational activity is prioritized (e.g., prioritize communications (par. 142 and 163), prioritize traffic (par. 153, 157), prioritize control (par. 142), etc.). Prioritization is initiated and performed using various techniques, wherein application relies on system data and/or set determinants (see at least par. 163-164). While dependent claims 2-11 provide further functional and component details allocated to the building controller, the claims fail to cure the deficits noted in claim 1.
Regarding claim 12, the claim is directed to a first and second building controller indicating that each has entered into a deterministic mode, wherein characteristics are adjusted relating to how the building controller communicates in response to the second indication. With regards to communication characteristics, paragraph 139 and 165 notes the following:
[0139] Several types of communications or messages may be sent over network 570. In some embodiments, controller 530 may periodically poll for information from any of the IO Ms related to sensors that are connected to the IOM. In some embodiments, the IOM may periodically send messages on network 570 to announce the current value of any sensor to which it is connected. In some embodiments, controller 530 may subscribe to a change-of-value (COY) with an IOM. The IOM may then send a new sensor value to the controller anytime the sensed value has changed by more than a specified amount (e.g., an amount provided in the characteristics of the COV configuration). In some embodiments, controller 530 may periodically send commands to any of the smart actuators on network 570. In some embodiments, router 566 may request values or subscribe to COV s for any of the devices connected to network 570. Router 566 may then communicate that information to devices (e.g., for display, storage, or processing) on network 571. In some embodiments, other forms of communication are performed on network 570.
[0165] In some embodiments, a building controller is configured to receive an indication from a second controller that the second controller has entered a deterministic communications mode. The building controller may, in response, change properties related to its communication. These operations may be performed to prioritize communications from the second controller that entered the deterministic mode (e.g., to perform operation 806 or a similar operation). FIG. 9 shows flow of operations 900, describing a similar flow for adjusting communication characteristics of the building controller according to some embodiments. In some embodiments, flow of operations 900 includes receiving an indication from a second controller indicating that the second building controller entered a deterministic mode. The deterministic mode may be entered for a variety of reasons related to the control of equipment (e.g., entering an active control state) in operation 902. According to some embodiments, the controller may respond by adjusting its communications characteristics in operation 904. For example, adjusting its communications characteristics may include adjusting a change-of-value (COY) subscription in operation 908. The COV threshold may be increased for certain devices to reduce the amount of network communication thus prioritizing other network communications. In some embodiments, it may be necessary to unsubscribe to a sensor COV and then subscribe to that COV with a larger threshold to perform the adjustment, if modifications to the COV subscription are not allowed.
As presented, the relationship and actionable control between the first and second controller is obscured, wherein the controllers are presented as separate entities without cross relations, making the relationship(s) governing the adjustment functions and characteristics unclear. The claim also does not provide further steps and support for implemented steps, relationships and elements employed in making adjustments to [undetermined] characteristics. As such, the claim is not clear in presenting what characteristics are adjusted, and which controller(s) are engaged in executing subsequent performance activities. While dependent claims 13-17 provide further functional and component details associated with communication control of the building controller, the claims fail to cure the deficits noted in claim 12.
Regarding claim 18, the claim focuses on a method for providing low latency control, wherein the system determines whether a control algorithm will violate timing requirements or provide control commands for a control algorithm. However, the claim fails to provide the steps and/or relationships necessary to determine whether conditions have been met or violated. In relation to violation conditions, paragraph 23 and 174 of the specification cites the following:
[0023] An embodiment of the present disclosure relates to a method for providing low latency control. The method includes generating a determination whether a control algorithm will violate requirements related to timing requirements of receiving sensor measurements or providing control commands required for the control algorithm. The method also includes entering a deterministic communications mode based on the determination. The method also includes adjusting a change-of-value subscription for a period of time of the deterministic communications mode. The method also includes operating equipment based on the control algorithm.
[0174] With reference to FIG. 13, flow 1300 of operations is used to provide low latency
communications for control, according to some embodiments. Flow 1300 may be performed by building controller 720 or another suitable device. In some embodiments, flow 1300 generates a determination related to whether a control algorithm will violate requirements related to latency in receiving sensor measurements required as inputs to the control algorithm in operation 1302. To generate the determination the network traffic may be predicted or otherwise estimated using historical data related to network traffic for similar times and/or conditions. For example, the historical data related to the amount or latency of network traffic for the same day of the week and time of day may be averaged to form the prediction. If the determination is true, a deterministic state may be entered in operation 1304 to provide priority communications. To provide priority communications, a COV subscription may be modified during the deterministic mode in operation 1304. The COV threshold for unprioritized communications may be increased to lower the level of network traffic and provide lower latency communications for those communications that are a priority (e.g., those used to perform control). In some embodiments, the control algorithm operates the equipment, providing an enhanced level of service because of the prioritized communications in the deterministic mode in operation 1308.
As presented, the claim presents a conditional state and steps taken thereafter. However, the claim does not provide further details delineating the conditional state. In reviewing the specification, it appears that violation of the conditional state is related to the system evaluating timing concerns, sensor input and determined control commands, and subsequently making relational decisions as to the terms and conditions determining violation. While the claim offers follow-up actions based on violating conditions, the steps, relationships and elements defining the measure for determining violation is obscured. While dependent claims 19-20 provide actionable steps for control output, the claims fail to cure the deficits noted in claim 18.
The presented claims provide elements used in controlling latency within a BMS, but does not provide the details in support of prioritizing communications based on a control algorithm, establishing controller relations and control steps necessary for adjusting operational parameters/characteristics of the system, and establishing violation parameters for the system to facilitate subsequent action. Examiner notes that during the examination process, claim language is considered in broad terms, whereby careful consideration is taken to view claim language in light of the specification, and not read details of the specification into the submitted claim language (see MPEP 2111).
Citation of Pertinent Prior Art
The prior art made of record and not relied upon is considered pertinent to applicant's disclosure. Gomes et al., “Agent-based architecture for demand side management using real-time resources’ priorities and a deterministic optimization algorithm” focuses on using distributed demand-side activity to optimize resources and control priorities within the system. The combination of Bigo et al., “Dynamic deterministic digital infrastructure for time-sensitive applications in factory floors” and Lu et al., “An intelligent deterministic scheduling method for ultralow latency communication in edge enabled industrial internet of things”, is directed at minimizing latency to optimize dynamic scheduling and increase fast response time within a system. The references cited in the attached PTO Form-892 focus on using BMS systems for controlling both communication processes and functional activities relating to various components within the business environment, inclusive of multiple building campuses.
Conclusion
The applicant is strongly encouraged to contact the examiner if further clarifications are needed with respect to interpretation of currently presented claims and/or cited prior art.
A reference to specific paragraphs, columns, pages, or figures in a cited prior art reference is not limited to preferred embodiments or any specific examples. It is well settled that a prior art reference, in its entirety, must be considered for all that it expressly teaches and fairly suggests to one having ordinary skill in the art. Stated differently, a prior art disclosure reading on a limitation of Applicant's claim cannot be ignored on the ground that other embodiments disclosed were instead cited. Therefore, the Examiner's citation to a specific portion of a single prior art reference is not intended to exclusively dictate, but rather, to demonstrate an exemplary disclosure commensurate with the specific limitations being addressed. In re Heck, 699 F.2d 1331, 1332-33,216 USPQ 1038, 1039 (Fed. Cir. 1983) (quoting In re Lemelson, 397 F.2d 1006,1009, 158 USPQ 275, 277 (CCPA 1968)). In re: Upsher-Smith Labs. v. Pamlab, LLC, 412 F.3d 1319, 1323, 75 USPQ2d 1213, 1215 (Fed. Cir. 2005); In re Fritch, 972 F.2d 1260, 1264, 23 USPQ2d 1780, 1782 (Fed. Cir. 1992); Merck& Co. v. BiocraftLabs., Inc., 874 F.2d 804, 807, 10 USPQ2d 1843, 1846 (Fed. Cir. 1989); In re Fracalossi, 681 F.2d 792,794 n.1,215 USPQ 569, 570 n.1 (CCPA 1982); In re Lamberti, 545 F.2d 747, 750, 192 USPQ 278, 280 (CCPA 1976); In re Bozek, 416 F.2d 1385, 1390, 163 USPQ 545, 549 (CCPA 1969).
Any inquiry concerning this communication or earlier communications from the examiner should be directed to KELVIN BOOKER whose telephone number is (571)272-7827. The examiner can normally be reached on M-F 9am-5pm.
If attempts to reach the examiner by telephone are unsuccessful, the examiner’s supervisor, Mohammad Ali can be reached on (571) 272-4105. The fax phone number for the organization where this application or proceeding is assigned is (571) 273-8300.
Information regarding the status of an application may be obtained from the Patent Application Information Retrieval (PAIR) system. Status information for published applications may be obtained from either Private PAIR or Public PAIR. Status information for unpublished applications is available through Private PAIR only. For more information about the PAIR system, see http://pair-direct.uspto.gov. Should you have questions on access to the Private PAIR system, contact the Electronic Business Center (EBC) at (866) 217-9197 (toll-free). If you would like assistance from a USPTO Customer Service Representative or access to the automated information system, call (800) 786-9199 (IN USA OR CANADA) or (571) 272-1000.
/Kelvin Booker/
Examiner, Art Unit 2119
/MOHAMMAD ALI/Supervisory Patent Examiner, Art Unit 2119