I 1111111111111111 11111 1111111111 lllll 111111111111111 11111 111111111111111111
`US008224282B2
`
`c12) United States Patent
`Songkakul et al.
`
`(IO) Patent No.:
`(45) Date of Patent:
`
`US 8,224,282 B2
`Jul. 17, 2012
`
`(54) METHOD AND DEVICE TO MANAGE
`POWER OF WIRELESS MULTI-SENSOR
`DEVICES
`
`(75)
`
`Inventors: Pornsak Songkakul, Mequon, WI (US);
`William Thomas Pienta, Prospect
`Heights, IL (US); James J. Coogan, Des
`Plaines, IL (US); Randall J. Amerson,
`Spring Grove, IL (US)
`
`(73) Assignee: Siemens Industry, Inc., Alpharetta, GA
`(US)
`
`( *) Notice:
`
`Subject to any disclaimer, the term ofthis
`patent is extended or adjusted under 35
`U.S.C. 154(b) by 576 days.
`
`(21)
`
`Appl. No.: 12/406,799
`
`(22)
`
`Filed:
`
`Mar. 18, 2009
`
`(65)
`
`Prior Publication Data
`
`US 2009/0240353 Al
`
`Sep.24,2009
`
`Related U.S. Application Data
`
`(60)
`
`Provisional application No. 61/037,739, filed on Mar.
`19, 2008.
`
`(51)
`
`(52)
`
`Int. Cl.
`(2006.01)
`G06F 17100
`(2006.01)
`G0SB 1100
`(2006.01)
`G0SB 21100
`U.S. Cl. ................. 455/343.1; 340/286.01; 340/540
`
`(58) Field of Classification Search ............... 455/343.1;
`340/286.01, 540,521,539.17, 539.22, 683,
`340/870.01
`See application file for complete search history.
`
`(56)
`
`References Cited
`
`U.S. PATENT DOCUMENTS
`6,437,692 Bl*
`8/2002 Petite et al. ................... 340/540
`7,053,767 B2 *
`5/2006 Petite et al. ................... 340/531
`2002/0125998 Al*
`9/2002 Petite et al. .............. 340/286.01
`* cited by examiner
`
`Primary Examiner - Daniel D Chang
`
`ABSTRACT
`(57)
`An automation component configured for wireless commu(cid:173)
`nication within a building automation system is disclosed.
`The automation component includes a multi-sensor package,
`a wireless communications component, a processor in com(cid:173)
`munication with the wireless communications component
`and the sensor package, and a memory in communication
`with the processor. The memory configured to store sensor
`data provided by the sensor package and computer readable
`instructions which are executable by the processor, wherein
`the computer readable instructions are programmed to
`receive status information related to sensor data in control at
`a second automation component in communication with the
`building automation system, and communicate a portion of
`the stored sensor data corresponding to the received status
`information to the second automation component.
`
`25 Claims, 7 Drawing Sheets
`
`{
`
`200
`
`220
`
`208
`
`218
`
`212
`
`214
`
`210
`
`222
`
`206
`
`204
`
`202
`
`216
`
`Emerson Exhibit 1001
`Emerson Electric v. Ollnova
`IPR2023-00624
`Page 00001
`
`

`

`U.S. Patent
`
`Jul. 17, 2012
`
`Sheet 1 of 7
`
`US 8,224,282 B2
`
`(cid:127)
`
`C)
`LL
`
`Cll
`00
`.,....
`
`N
`N
`
`)
`
`N
`0 .,....
`
`(
`
`00
`0 .,....
`
`I C
`
`C ....
`
`IPR2023-00624 Page 00002
`
`

`

`U.S. Patent
`
`Jul. 17, 2012
`
`Sheet 2 of 7
`
`US 8,224,282 B2
`
`{200
`
`----220
`
`SENSOR PACKAGE
`
`222----....L
`
`BATTERY
`
`202---1
`
`PROCESSOR
`
`216
`
`212
`
`210
`
`FIG. 2
`
`IPR2023-00624 Page 00003
`
`

`

`U.S. Patent
`
`Jul. 17, 2012
`
`._____20(cid:143)-a ___,,-
`
`US 8,224,282 B2
`
`Sheet 3 of 7
`
`(300
`r302
`~ J...____20(cid:143)-b ___,
`
`FIG. 3
`
`POLL
`
`L.02
`
`404
`
`406
`
`408
`
`GOV
`ACKNOWLEDGMENT
`
`NEGATIVE GOV
`ACKNOWLEDGMENT
`
`410
`
`RESPOND
`
`412
`
`PROVIDE SECOND GOV
`ACKNOWLEDGMENT
`
`FIG. 4
`
`IPR2023-00624 Page 00004
`
`

`

`U.S. Patent
`
`Jul. 17, 2012
`
`Sheet 4 of 7
`
`US 8,224,282 B2
`
`CHECK
`VALUES
`
`502
`
`504
`
`506
`
`508
`
`cov
`ACKNOWLEDGMENT
`
`NEGATIVE COV
`ACKNOWLEDGMENT
`
`510
`
`CLEAR COV
`- - - STATUS - - -~
`
`512
`
`RETURN TO
`NORMAL
`OPERATION
`
`FIG. 5
`
`IPR2023-00624 Page 00005
`
`

`

`U.S. Patent
`
`Jul. 17, 2012
`
`Sheet 5 of 7
`
`US 8,224,282 B2
`
`(600
`
`602
`
`604
`
`SCAN
`SENSOR
`DATA
`
`COMPARE
`SENSOR
`DATA TO COV
`THRESHOLDS
`
`RECEIVE USAGE
`INFORMATION
`
`COMMUNICATE
`IDENTIFIED SENSOR
`DATA
`
`COMMUNICATE ALL
`SENSOR DATA AT
`INTERVAL
`
`606
`
`608
`
`610
`
`FIG. 6
`
`IPR2023-00624 Page 00006
`
`

`

`U.S. Patent
`
`Jul. 17, 2012
`
`Sheet 6 of 7
`
`US 8,224,282 B2
`
`702
`
`704
`
`SCAN
`SENSOR
`DATA
`
`COMPARE
`SENSOR
`DATA TO COV
`THRESHOLDS
`
`RECEIVE STATUS
`INFORMATION
`
`COMMUNICATE
`IDENTIFIED SENSOR
`DATA
`
`COMMUNICATE ALL
`SENSOR DATA AT
`INTERVAL
`
`706
`
`708
`
`710
`
`FIG. 7
`
`IPR2023-00624 Page 00007
`
`

`

`U.S. Patent
`
`Jul. 17, 2012
`
`Sheet 7 of 7
`
`US 8,224,282 B2
`
`(800
`
`RECEIVE "ON"
`COMMAND
`
`IMPLEMENT POWER(cid:173)
`SAVING ALGORTHIM
`
`RECEIVE "OFF"
`COMMAND
`
`SEND STATUS
`UPDATE
`
`802
`
`804
`
`806
`
`808
`
`FIG. 8
`
`IPR2023-00624 Page 00008
`
`

`

`US 8,224,282 B2
`
`1
`METHOD AND DEVICE TO MANAGE
`POWER OF WIRELESS MULTI-SENSOR
`DEVICES
`
`PRIORITY CLAIM
`
`This patent document claims the priority benefit provided
`under 35 U.S.C. § 119( e) to U.S. provisional patent applica(cid:173)
`tion Ser. No. 61/037,739, filed on Mar. 19, 2008. The content
`of this provisional patent application is incorporated herein
`by reference for all purposes.
`
`BACKGROUND
`
`The present disclosure generally relates to communica(cid:173)
`tions within a building automation system. In particular, the
`present disclosure relates to methods and devices for commu(cid:173)
`nicating change-of-value information within a building auto(cid:173)
`mation system.
`A building automations system (BAS) typically integrates 20
`and controls elements and services within a structure such as
`the heating, ventilation and air conditioning (HVAC) system,
`security services, fire systems and the like. The integrated and
`controlled systems are arranged and organized into one or
`more floor level networks (FLNs) containing application or 25
`process specific controllers, sensors, actuators, or other
`devices distributed or wired to form a network. The floor level
`networks provide general control for a particular floor or
`region of the structure. For example, a floor level network
`may be an RS-485 compatible network that includes one or
`more controllers or application specific controllers config(cid:173)
`ured to control the elements or services within floor or region.
`The controllers may, in tum, be configured to receive an input
`from a sensor or other device such as, for example, a room
`temperature sensor (RTS) deployed to monitor the floor or
`region. The input, reading or signal provided to the controller,
`in this example, may be a temperature indication representa(cid:173)
`tive of the physical temperature. The temperature indication
`can be utilized by a process control routine such as a propor(cid:173)
`tional-integral control routine executed by the controller to
`drive or adjust a damper, heating element, cooling element or
`other actuator towards a predefined set-point.
`Information such as the temperature indication, sensor
`readings and/or actuator positions provided to one or more
`controllers operating within a given floor level network may, 45
`in tum, be communicated to an automation level network
`(ALN) or building level network (BLN) configured to, for
`example, execute control applications, routines or loops,
`coordinate time-based activity schedules, monitor priority
`based overrides or alarms and provide field level information
`to technicians. Building level networks and the included floor
`level networks may, in tum, be integrated into an optional
`management level network (MLN) that provides a system for
`distributed access and processing to allow for remote super(cid:173)
`vision, remote control, statistical analysis and other higher
`level functionality. Examples and additional information
`related to BAS configuration and organization may be found
`in the co-pending U.S. patent application Ser. No. 11/590,157
`(2006P18573 US), filed on Oct. 31, 2006, and co-pending
`U.S. patent application Ser. No. 10/915,034 (2004P13093 60
`US), filed on Aug. 8, 2004, the contents of these applications
`are hereby incorporated by reference for all purposes.
`Wireless devices, such as devices that comply with IEEE
`802.15.4/ZigBee protocols, may be implemented within the
`control scheme of a building automation system without 65
`incurring additional wiring or installation costs. ZigBee(cid:173)
`compliant devices such as full function devices (FFD) and
`
`2
`reduced function devices (RFD) may be interconnected to
`provide a device net or mesh within the building automation
`system. For example, full function devices are designed with
`the processing power necessary to establish peer-to-peer con(cid:173)
`nections with other full function devices and/or execute con(cid:173)
`trol routines specific to a floor or region of a floor level
`network. Each of the full function devices may, in tum, com(cid:173)
`municate with one or more of the reduced function devices in
`a hub and spoke arrangement. Reduced function devices such
`10 as the temperature sensor described above are designed with
`limited processing power necessary to perform a specific
`task(s) and communicate information directly to the con(cid:173)
`nected full function device.
`Wireless devices for use within the building automation
`15 system must operate for an extended period on a limited
`battery charge. Systems, devices and methods to maximize
`power conservation may be desirable to extend and/or maxi(cid:173)
`mize the operating life of wireless devices and the network in
`which they operate.
`
`SUMMARY
`
`The present disclosure generally provides for communi(cid:173)
`cating information between wireless devices and/or automa(cid:173)
`tion components operating within a building automation sys(cid:173)
`tem (BAS). Wireless devices and/or automation components
`may be configured to optimize radio and/or data communi(cid:173)
`cations to extend battery life.
`In one embodiment, an automation component configured
`30 for wireless communication within a building automation
`system is disclosed. The automation component includes a
`multi-sensor package, a wireless communications compo(cid:173)
`nent, a processor in communication with the wireless com(cid:173)
`munications component and the sensor package, and a
`35 memory in communication with the processor. The memory
`configured to store sensor data provided by the sensor pack(cid:173)
`age and computer readable instructions which are executable
`by the processor, wherein the computer readable instructions
`are progranmied to receive status information related to sen-
`40 sor data in control at a second automation component in
`communication with the building automation system, and
`communicate a portion of the stored sensor data correspond(cid:173)
`ing to the received status information to the second automa-
`tion component.
`In another embodiment, an automation component config-
`ured for wireless communication within a building automa(cid:173)
`tion system is disclosed. The automation component includes
`a multi-sensor package, a wireless communications compo(cid:173)
`nent, a processor in communication with the wireless com-
`50 munications component and the sensor package, a memory in
`communication with the processor, the memory configured to
`store sensor data provided by the sensor package and com(cid:173)
`puter readable instructions which are executable by the pro(cid:173)
`cessor. The computer readable instructions are programmed
`55 to receive status data related to sensor data in control at a
`second automation component in communication with the
`building automation system, determine the sensor data in
`control at the second automation component based on the
`received status data, and communicate the stored sensor data
`corresponding the sensor data in control at the second auto(cid:173)
`mation component.
`In another embodiment, an automation component config(cid:173)
`ured for wireless communication within a building automa(cid:173)
`tion system is disclosed. The automation component
`includes, a multi-sensor package, a wireless communications
`component, a processor in communication with the wireless
`communications component and the sensor package, a
`
`IPR2023-00624 Page 00009
`
`

`

`US 8,224,282 B2
`
`3
`memory in communication with the processor, the memory
`configured to store sensor data provided by the sensor pack(cid:173)
`age and computer readable instructions which are executable
`by the processor. The computer readable instructions are pro(cid:173)
`grammed to receive a wake-up command from a second auto(cid:173)
`mation component, communicate stored sensor data related
`to the sensor data in control at a second automation compo(cid:173)
`nent, and receive a power-down command from the second
`automation component.
`A method for providing power saving wireless communi- 10
`cation within a building automation system is disclosed. The
`method includes scanning sensor data associated with a
`multi-sensor package of a first automation component, iden(cid:173)
`tifying changed sensor values within the sensor data, receiv(cid:173)
`ing a first communication from a second automation compo- 15
`nent in communication with the first automation component
`and the building automation system, and communicating a
`portion of the identified changed sensor values associated
`with the first communication received from the second auto(cid:173)
`mation component.
`Additional features and advantages of the present inven(cid:173)
`tion are described in, and will be apparent from, the following
`Detailed Description and the figures.
`
`BRIEF DESCRIPTION OF THE FIGURES
`
`The method, system and teaching provided relate to bind(cid:173)
`ing automation components within a building automation
`system (BAS).
`FIG. 1 illustrates an embodiment of a building automation
`system configured in accordance with the disclosure provided
`herein;
`FIG. 2 illustrates an embodiment of a wireless device or
`automation component that may be utilized in connection
`with the building automation system shown in FIG. 1;
`FIG. 3 illustrates an exemplary flowchart representative of
`a communications and updating configuration;
`FIG. 4 illustrates an exemplary flowchart representative of
`a communications algorithm;
`FIG. 5 illustrates an exemplary flowchart representative of
`another communications algorithm;
`FIG. 6 illustrates an exemplary flowchart representative of
`a communications and power saving configuration;
`FIG. 7 illustrates an exemplary flowchart representative of
`a communications and power saving algorithm; and
`FIG. 8 illustrates an exemplary flowchart representative of
`another communications and power saving algorithm.
`
`DETAILED DESCRIPTION
`
`The embodiments discussed herein include automation
`components, wireless devices and transceivers. The devices
`may be IEEE 802.15.4/ZigBee-compliant automation com(cid:173)
`ponents such as: a personal area network (PAN) coordinator
`which may be implemented as a field panel transceiver
`(FPX); a full function device (FFD) implemented as a floor
`level device transceiver (FLNX); and a reduced function
`device (RFD) implemented as a wireless room temperature
`sensor (WRTS) that may be utilized in a building automation
`system (BAS). The devices identified herein are provided as
`an example of automation components, wireless devices and
`transceivers that may be integrated and utilized within a
`building automation system embodying the teachings dis(cid:173)
`closed herein and are not intended to limit the type, function(cid:173)
`ality and interoperability of the devices and teaching dis(cid:173)
`cussed and claimed herein. Moreover, the disclosed building
`automation system describes automation components that
`
`4
`may include separate wireless devices and transceivers, how(cid:173)
`ever it will be understood that that the wireless device and
`transceiver may be integrated into a single automation com(cid:173)
`ponent operable within the building automation system.
`I. Building Automation System Overview
`One exemplary building automation system that may
`include the devices and be configured as described above is
`the APOGEE® system provided by Siemens Building Tech(cid:173)
`nologies, Inc. The APOGEE® system may implement
`RS-485 wired communications, Ethernet, proprietary and
`standard protocols, as well as known wireless communica-
`tions standards such as, for example, IEEE 802.15 .4 wireless
`communications which are compliant with the ZigBee stan(cid:173)
`dards and/or ZigBee certified wireless devices or automation
`components. ZigBee standards, proprietary protocols or other
`standards are typically implemented in embedded applica-
`tions that may utilize low data rates and/or require low power
`consumption. Moreover, ZigBee standards and protocols are
`suitable for establishing inexpensive, self-organizing, mesh
`20 networks which may be suitable for industrial control and
`sensing applications such as building automation. Thus, auto(cid:173)
`mation components configured in compliance with ZigBee
`standards or protocols may require limited amounts of power
`allowing individual wireless devices, to operate for extended
`25 periods of time on a finite battery charge.
`The wired or wireless devices such as the IEEE 802.15.4/
`ZigBee-compliant automation components may include, for
`example, anRS-232 connection withanRJl 1 or other type of
`connector, an RJ45 Ethernet compatible port, and/or a uni-
`30 versa! serial bus (USB) connection. These wired, wireless
`devices or automation components may, in turn, be config(cid:173)
`ured to include or interface with a separate wireless trans(cid:173)
`ceiver or other communications peripheral thereby allowing
`the wired device to communicate with the building automa-
`35 tion system via the above-described wireless protocols or
`standards. Alternatively, the separate wireless transceiver
`maybe coupled to a wireless device such as a IEEE 802.15.4/
`ZigBee-compliant automation component to allow for com(cid:173)
`munications via a second communications protocol such as,
`40 for example, 802.1 lx protocols (802.1 la, 802.11 b . . .
`802.1 ln, etc.) These exemplary wired, wireless devices may
`further include a man-machine interface (MMI) such as a
`web-based interface screen that provide access to config(cid:173)
`urable properties of the device and allow the user to establish
`45 or troubleshoot communications between other devices and
`elements of the BAS.
`FIG. 1 illustrates an exemplary building automation sys(cid:173)
`tem or control system 100 that may incorporate the methods,
`systems and teaching provided herein. The control system
`50 100 includes a first network 102 such as an automation level
`network (ALN) or management level network (MLN) in
`communication with one or more controllers such as a plu(cid:173)
`rality of terminals 104 and a modular equipment controller
`(MEC) 106. The modular equipment controller or controller
`55 106 is a progranimable device which may couple the first
`network 102 to a second network 108 such as a floor level
`network (FLN). The second network 108, in this exemplary
`embodiment, may include a first wired network portion 122
`and a second wired network portion 124 that connect to
`60 building automation components 110 (individually identified
`as automation components 110a to 110.1). The second wired
`network portion 124 may be coupled to wireless building
`automation components 112 via the automation component
`126. For example, the building automation components 112
`65 may include wireless devices individually identified as auto(cid:173)
`mation components 112a to 112/ In one embodiment, the
`automation component 112/ may be a wired device that may
`
`IPR2023-00624 Page 00010
`
`

`

`US 8,224,282 B2
`
`5
`or may not include wireless functionality and connects to the
`automation component 112e. In this configuration, the auto(cid:173)
`mation component 112/ may utilize or share the wireless
`functionality provided by the automation component 112e to
`define an interconnected wireless node 114. The automation
`components 112a to 112/may, in tum, communicate or con(cid:173)
`nect to the first network 102 via, for example, the controller
`106 and/or an automation component 126. The automation
`component 126 may be a field panel, FPX or another full
`function device in communication with the second wired
`network portion 124 which, in tum, may be in communication
`with the first network 102.
`The control system 100 may further include automation
`components generally identified by the reference numerals
`116a to 116g. The automation components 116a to 116gmay 15
`be configured or arranged to establish one or more networks
`or subnets 118a and 118b. The automation components 116a
`to 116g such as, for example, full or reduced function devices
`and/or a configurable terminal equipment controller (TEC),
`cooperate to wirelessly communicate information between 20
`the first network 102, the control system 100 and other
`devices within the mesh networks or subnets 118a and 118b.
`For example, the automation component 116a may commu(cid:173)
`nicate with other automation components 116b to 116d
`within the mesh network 118a by sending a message
`addressed to the network identifier, alias and/or media access
`control (MAC) address assigned to each of the interconnected
`automation components 116a to 116g and/or to a field panel
`120. In one configuration, the individual automation compo(cid:173)
`nents 116a to 116d within the subnet 118a may communicate
`directly with the field panel 120 or, alternatively, the indi(cid:173)
`vidual automation components 116a to 116d may be config(cid:173)
`ured in a hierarchal manner such that only one of the compo(cid:173)
`116c,
`nents
`for
`example,
`automation
`component
`communicates with the field panel 120. The automation com(cid:173)
`ponents 116e to 116g of the mesh network 118b may, in tum,
`communicate with the individual automation components
`116a to 116d of the mesh network 118a or the field panel 120.
`The automation components 112e and 112/ defining the
`wireless node 114 may wirelessly communicate with the 40
`second network 108, and the automation components 116e to
`116g of the mesh network 118b to facilitate communications
`between different elements, section and networks within the
`control system 100. Wireless communication between indi(cid:173)
`vidual the automation components 112, 116 and/or the sub(cid:173)
`nets 118a, 118b may be conducted in a direct or point-to(cid:173)
`point manner, or in an indirect or routed manner through the
`nodes or devices comprising the nodes or networks 102, 108,
`114 and 118. In an alternate embodiment, the first wired
`network portion 122 is not provided, and further wireless
`connections may be utilized.
`FIG. 2 illustrates an exemplary automation component 200
`that may be utilized within the control system 100. The auto(cid:173)
`mation component 200 maybe be a full function device or a
`reduced function device and may be utilized interchangeably
`with the automation components 110, 112 and 116 shown and
`discussed in connection with FIG. 1. The automation compo(cid:173)
`nent 200 in this exemplary embodiment may include a pro(cid:173)
`cessor 202 such as an INTEL® PENTIUM, an AMD® ATH(cid:173)
`LON™, an Atmel® ATMega, or other 8, 12, 16, 24, 32 or 64
`bit classes of processors in communication with a memory
`204 or storage medium. The memory 204 or storage medium
`may contain random access memory (RAM) 206, flashable or
`non-flashable read only memory (ROM) 208 and/or a hard
`disk drive (not shown), or any other known or contemplated
`storage device or mechanism. The automation component
`may further include a communications component 210. The
`
`6
`communications component 210 may include, for example,
`the ports, hardware and software necessary to implement
`wired communications with the control system 100. The
`communications component 210 may alternatively, or in
`addition to, contain a wireless transmitter 212 and a receiver
`214 communicatively coupled to an antenna 216 or other
`broadcast hardware.
`The sub-components 202, 204 and 210 of the exemplary
`automation component 200 may be coupled and able to share
`10 information with each other via a communication bus 218. In
`this way, computer readable instructions or code such as
`software or firmware may be stored on the memory 204. The
`processor 202 may read and execute the computer readable
`instructions or code via the communication bus 218. The
`resulting commands, requests and queries may be provided to
`the communications component 210 for transmission via the
`transmitter 212 and the antenna 216 to other automation
`components 200, 112 and 116 operating within the first and
`second networks 102 and 108. Sub-components 202-218 may
`be discrete components or may be integrated into one (1) or
`more integrated circuits, multi-chip modules, and/or hybrids.
`The automation component 200 may be a multi-sensor
`wireless device that includes a sensor package 220 in com(cid:173)
`munication with the sub-components 202, 204 and 210 via
`25 the communication bus 218. The sensor package 220 may be
`configured to sense or detect a variety of variables such as, for
`example, temperature, humidity, carbon dioxide, carbon
`monoxide, volatile organic compounds, etc. Sensed values,
`signals and other data may be stored within the memory 204
`30 and accessible to the processor 202. Moreover, the signal or
`indication may be flagged to indicate that a change-of-value
`has occurred within the automation component 200. In other
`words, the detection or reception of the signal or indication
`may operate as a change-of-value flag which denotes that the
`35 information, setting, signals and/or indications stored within
`the memory 204 have been altered, updated or otherwise
`changed. Alternatively, a separate change-of-value flag may
`be set and/or correspond to each detected or received signal or
`indication.
`A battery 222 may power the sub-components 202, 204,
`210 and 220 via the communication bus 218, direct or hard(cid:173)
`wired connections via a circuit board, one or more wires or
`conduits or any other suitable power communication
`medium. Communication of the stored sensor readings and/
`45 or data via the communication component 210 is a power
`intensive operation that may drain the battery 222. Moreover,
`some of the sensors within the sensor package 220 may
`require a great deal of power to operate. In order to increase
`the life of the battery 222, the high power requirement sensors
`50 within the sensor package 220 may be configured to operate
`periodically or on a set schedule.
`II. Automation Component Communication and Updating
`FIG. 3 illustrates an exemplary communications and
`updating configuration 300 that may be implemented
`55 between automation components 200. In this exemplary con(cid:173)
`figuration, the automation components 200a may be config(cid:173)
`ured to implement a request-response (polling) communica(cid:173)
`tion 302 in order to pull information from 200b device(s) to
`the polling device or for the 200b device to push values up to
`60 the 200a device. For example, the automation component
`200a may represent a field panel, FPX or another full function
`device. Similarly, the automation component 200b may rep(cid:173)
`resent a TEC, FLNX, a Full function or reduced function
`device, a wireless actuator or any other wired or wireless
`65 device operable within the BAS 100. Moreover, the automa(cid:173)
`tion components 200a, 200b may be operative within, for
`example, the mesh network or subnet 118a.
`
`IPR2023-00624 Page 00011
`
`

`

`US 8,224,282 B2
`
`20
`
`7
`A. Request-Response (Polled) Communications
`FIG. 4 illustrates a poll communication algorithm 400 or
`method that may be implemented, for example, between the
`automation components 200a, 200b. At block 402, the auto(cid:173)
`mation component 200a, which may be a field panel or other
`full function device, may generate and communicate a
`change-of-value (COY) request message to one or more auto(cid:173)
`mation components 200b operating within the BAS 100 and/
`or within the individual FLN s that make up the BAS 100. The
`COY request message may request or direct the automation
`component 200b to indicate whether any of the local detected
`values, received values, parameters, or measurements have
`changed or altered beyond a pre-defined reporting limit, e.g.
`COY limit.
`At block 404, the automation component 200b receives the
`COY request message. For example, if the automation com(cid:173)
`ponent 200b has, since receipt of the last COY request mes(cid:173)
`sage, detected or received a new value representing the
`change-of-value, then at block 406 the automation compo(cid:173)
`nent 200b may generate a COY acknowledgment message for
`communication to the automation component 200a. Alterna(cid:173)
`tively, if the automation component 200b hasn't detected or
`received the new value representing the change-of-value,
`then at block 408 the automation component 200b may gen(cid:173)
`erate a negative COY acknowledgment message for commu(cid:173)
`nication to the automation component 200a.
`At block 410, if the automation component 200a has suc(cid:173)
`cessfully received the COY acknowledgment message pro(cid:173)
`vided by the automation component 200b, then the automa(cid:173)
`tion component 200a may generate and send an acknowledge
`COY request message for reply to the automation component
`200b.
`At block 412, the automation component 200b, in response
`to the acknowledge COY request message provided by the
`automation component 200a, knows the COY was success(cid:173)
`fully transferred to the device 200a and clears those reported
`COV's, and provides a acknowledge COY request acknowl(cid:173)
`edgment message. After block 412, the communication algo(cid:173)
`rithm 400 may restart and another wireless device or automa(cid:173)
`tion component within the BAS 100 may be polled. It will be
`understood that the exemplary communications algorithm
`400 may be implemented in a wired or wireless BAS 100
`B. Push Communications
`FIG. 5 illustrates an alternate communication algorithm
`500 or method that may be implemented, for example,
`between the automation components 200a, 200b. The exem(cid:173)
`plary communication method 500 may be employed in a BAS
`100 configured for hybrid communications utilizing both
`wired and wireless communications.
`At block 502, the automation component 200b, which may
`be, for example, a full function device, an FLNX and or a
`TEC, will check its inputs and outputs for new or changed
`values. If the new value has changed more than a pre-defined
`amount from the last reported value, then the variable is to be
`reported on the next COY communication.
`At block 504, the automation component 200b will check,
`at regular intervals established by an internal COY Reporting
`time interval or as needed by the internal algorithm, to see if
`Change-Of-Value (COY) are waiting to be reported. If so, the
`automation component 200b will create a Push COY message
`containing all queued COY values and send them to automa(cid:173)
`tion component 200a. At block 506, the automation compo(cid:173)
`nent 200a may respond to automation component 200b with
`a Push COY acknowledge response if the message is received
`and understood, or, at block 508, will respond with a negative
`acknowledge (NAK) and an error code if the message was not
`understood. On receipt, at block 510, automation component
`200b clears the COY status. At block 512, the automation 65
`component 200b may return to its normal operations until the
`next check for new values.
`
`8
`Automation component 200a now processes those queued
`COV's into the internal database of the automation compo(cid:173)
`nent 200a and may optionally report those new values to other
`devices as defined in the drawings and description of FIG. 1.
`If automation component 200b was in fact a hardwired
`device with an external wireless network interface, such as a
`TEC with an FLNX configuration, then the FLNX would
`need to poll the TEC for COV's and hold them within the
`FLNX while the communication to automation component
`10 200a was occurring. In addition, the FLNX would need to
`acknowledge the COV's from the TEC as was defined in
`algorithm of FIG. 4.
`If automation component 200a was a hardwired device
`with an external wireless network interface, such as a field
`15 panel with an FPX, then the FPX would need to act has the
`buffer for pushed COV's and queue the COV's for the field
`panel. The field panel would poll the FPX, in accordance with
`the algorithms of FIG. 4, to accept the COV's into the data-
`base of the automation component 200a.
`In this configuration, the communication algorithm 500
`allows COY related messages to be gathered and pushed from
`one or more automation components 200b up to the 200a
`device and from the 200a device to other system components
`as defined in FIG. 1. By