Method and apparatus pertaining to message-based functionality
Summary by NHIP
Wireless Barrier Operator Messaging
The method manages message-based functionality for a movable barrier operator by transmitting acknowledgements based on communication type and system identifiers. It prevents function execution when remote capability is uncertain and reduces retransmission attempts after detecting lack of acknowledgement for two wireless messages.
Claim Score by NHIP
Abstract
A movable barrier operator transmits a message to a remote peripheral platform and, upon determining that the remote peripheral platform is presently able to carry out a given functionality, responsively permits a particular function to be carried out by the movable barrier operator. Conversely, upon determining that it cannot be ascertained whether the remote peripheral platform is presently able to carry out the given functionality, the movable barrier operator responsively prevents the movable barrier operator from carrying out the particular function. Also, upon detecting that a targeted remote platform does not acknowledge a previously re-transmitted message and further upon detecting that this same remote platform has also not acknowledged a subsequent wirelessly-transmitted second message, the system can switch to automatically retransmitting that second message a lesser number of times than would otherwise be required.

Term
8.9 yearsleft in the term
Expires 7 August 2035, including 1,757 days of term adjustment.
- Priority and filed
- Granted
- Today
- Expires
4 claims: 1 independent, 3 dependent
- 1Broadest claimClaim Score 58, broad(NHIP)A method for use in a system that employs a wireless time-slotted frequency-hopping communications protocol, the method comprising:at a control circuit having a unique system identifier: upon receiving an individually-targeted communication, transmitting a corresponding acknowledgement message in a time slot regardless of whether that time slot corresponds to the unique system identifier;upon receiving a multi-target broadcast communication, transmitting a corresponding acknowledgement message in a time slot that uniquely corresponds to the unique system identifier;and upon determining a need to unilaterally transmit a message, transmitting the message asynchronously, wherein the asynchronous transmission is at any time including outside of a time slot of the communications protocol.
108 paragraphs in 4 sections, as filed
TECHNICAL FIELD
0001This invention relates generally to wireless data communications.
BACKGROUND
0002Wireless data communications comprises a well-developed area of prior art endeavor. This includes, for example, the transmission of remote-control signals/messages from a one-way wireless transmitter to a compatible wireless receiver as comprises a part of a movable barrier operator (such as, but not limited to, a garage door opener). For the most part such transmissions often make use of unlicensed spectrum in the ultra-high frequency (UHF) range.
0003Such approaches have served well for many years. There are application settings, however, where further capabilities in these regards would be useful. Two-way data communications in such an application setting, for example, has been proposed. The specifics, however, of suitably configuring a useful system to accommodate such a direction present numerous challenges. These challenges, in turn, have no doubt contributed to a delayed introduction of useful practices in these regards.
BRIEF DESCRIPTION OF THE DRAWINGS
The above needs are at least partially met through provision of the method and apparatus pertaining to message-based functionality described in the following detailed description, particularly when studied in conjunction with the drawings, wherein:
<figref idref="DRAWINGS">FIG. 1</figref> comprises a perspective view as configured in accordance with various embodiments of the invention;
<figref idref="DRAWINGS">FIG. 2</figref> comprises a block diagram as configured in accordance with various embodiments of the invention;
<figref idref="DRAWINGS">FIG. 3</figref> comprises a flow diagram as configured in accordance with various embodiments of the invention;
<figref idref="DRAWINGS">FIGS. 4A and 4B</figref> comprise a flow diagram as configured in accordance with various embodiments of the invention;
<figref idref="DRAWINGS">FIG. 5</figref> comprises a flow diagram as configured in accordance with various embodiments of the invention;
<figref idref="DRAWINGS">FIG. 6</figref> comprises a flow diagram as configured in accordance with various embodiments of the invention;
<figref idref="DRAWINGS">FIG. 7</figref> comprises a flow diagram as configured in accordance with various embodiments of the invention;
<figref idref="DRAWINGS">FIG. 8</figref> comprises a flow diagram as configured in accordance with various embodiments of the invention; and
<figref idref="DRAWINGS">FIG. 9</figref> comprises a flow diagram as configured in accordance with various embodiments of the invention.
0014Elements in the figures are illustrated for simplicity and clarity and have not necessarily been drawn to scale. For example, the dimensions and/or relative positioning of some of the elements in the figures may be exaggerated relative to other elements to help to improve understanding of various embodiments of the present invention. Also, common but well-understood elements that are useful or necessary in a commercially feasible embodiment are often not depicted in order to facilitate a less obstructed view of these various embodiments of the present invention. Certain actions and/or steps may be described or depicted in a particular order of occurrence while those skilled in the art will understand that such specificity with respect to sequence is not actually required. The terms and expressions used herein have the ordinary technical meaning as is accorded to such terms and expressions by persons skilled in the technical field as set forth above except where different specific meanings have otherwise been set forth herein.
DETAILED DESCRIPTION
0015Generally speaking, pursuant to these various embodiments, a movable barrier operator transmits a message to a remote peripheral platform and, upon determining that the remote peripheral platform is presently able to carry out a given functionality, responsively permits a particular function to be carried out by the movable barrier operator. Conversely, upon determining that it cannot be ascertained whether the remote peripheral platform is presently able to carry out the given functionality, the movable barrier operator responsively prevents the movable barrier operator from carrying out the particular function.
0016By one approach, this particular function comprise, for example, a timer-to-close function and/or a remote-close function. In such a case, the remote peripheral platform can comprise, for example, an announcing device such as a sound producing device or a light fixture and the given functionality can comprise, at least in part, having the announcing device announce a warning that the movable barrier operator will imminently carry out the particular function (such as close a movable barrier in an unattended manner).
0017By one approach, the movable barrier operator can make the aforementioned determination as a function of whether the remote peripheral platform acknowledges in an expected manner a message transmitted to the remote peripheral platform by the movable barrier operator.
0018If desired, these teachings will accommodate, in lieu of the foregoing or in combination therewith, automatically re-transmitting a message to a targeted remote platform upon detecting that this remote platform has not acknowledged a previous wirelessly transmitted message. This can comprise automatically retransmitting the message up to “X” times until an acknowledgement message is received. By one approach, upon detecting that the targeted remote platform does not acknowledge the re-transmitted messages and further upon detecting that this same remote platform has also not acknowledged another wirelessly-transmitted second message, the system can switch to automatically retransmitting that second message a lesser number of times.
0019These and other benefits may become clearer upon making a thorough review and study of the following detailed description. Referring now to the drawings, and in particular to <figref idref="DRAWINGS">FIG. 1</figref>, it may be helpful to first describe an illustrative application setting. It will be understood that the specific of this example are intended to serve only in an illustrative regard and are not intended to express or suggest any corresponding limitations with respect to the scope of these teachings.
0020In this illustrative example, a barrier movement controller <b>100</b> comprises, in part, a movable barrier operator <b>101</b> positioned within a garage <b>102</b>. This movable barrier operator <b>101</b> mounts to the garage ceiling <b>103</b> and serves to control and effect selective movement of a selectively movable barrier comprising, in this illustrative example, a multi-panel garage door <b>104</b>. The multi-panel garage door <b>104</b> includes a plurality of rollers (not shown) rotatably confined within a pair of tracks <b>105</b> positioned adjacent to and on opposite sides of the garage opening <b>106</b>.
0021The movable barrier operator <b>101</b> includes a head unit having a motive component such as an electric motor (not shown) to provide motion to the garage door <b>104</b> via a rail assembly <b>107</b>. The rail assembly <b>107</b> in this example includes a trolley <b>108</b> for releasable connection of the head unit to the garage door <b>104</b> via an arm <b>109</b>. The arm <b>109</b> connects to an upper portion <b>110</b> of the garage door <b>104</b>. The trolley <b>108</b> effects the desired movement of the door <b>104</b> via the arm <b>109</b> via a transmission that can be an endless chain, belt, or screw drive, all of which are well know in the industry. As an alternative another head unit that is well known in the industry is a jackshaft operator that moves the barrier by affecting a counter balance system.
0022The head unit includes a radio frequency receiver (not shown) having an antenna <b>111</b> to facilitate receiving coded radio frequency transmissions from one or more radio transmitters <b>112</b>. These transmitters <b>112</b> may include portable transmitters (such as keyfob-style transmitters) or keypad transmitters (such as those often installed in automobile sun visors). The radio receiver typically connects to a processor (not shown) in the head unit that interprets received signals and responsively controls other portions of the movable barrier operator <b>101</b>.
0023The head unit also includes a radio frequency transmitter (not shown) having an antenna <b>114</b> to facilitate transmitting coded radio frequency transmissions to one or more two-way remote platforms as described herein. In many application settings the radio frequency receiver and the radio frequency transmitter will operate using non-overlapping and considerably different bands. Together, this receiver and transmitter comprise a transceiver.
0024An end-user interface <b>113</b> such as a push button-based wall control unit can comprise one of the aforementioned two-way remote platforms and can wirelessly communicate with the head unit to effect control of a movable barrier operator motor and other components. So configured, for example, an end user can assert the end-user interface <b>113</b> to signal to the movable barrier operator <b>101</b> that the barrier <b>104</b> should now be moved from an opened position to a closed position.
0025An obstacle detector <b>115</b> can also comprise one of the aforementioned two-way remote platforms and can also wirelessly communicate with the head unit. The obstacle detector can employ, for example, optical (such as infrared-pulsed beams) approaches to detect when the garage door opening <b>106</b> is blocked. The obstacle detector <b>115</b> can then wirelessly signal the movable barrier operator <b>101</b> regarding the blockage. The latter can then, for example, cause a reversal or opening of the door <b>104</b> to avoid contacting the obstacle.
0026A light fixture <b>116</b> can also comprise one of the aforementioned two-way remote platforms and hence can also wirelessly communicate with (or via) the head unit. So configured, the movable barrier operator <b>101</b> can selectively cause the light fixture <b>116</b> to provide a source of light if and as appropriate.
0027<figref idref="DRAWINGS">FIG. 2</figref> provides further specific examples with respect to the movable barrier operator <b>101</b>. Again, these points of specificity are not to be taken as suggesting any particular limitations in these regards and are offered instead for the sake of illustration.
0028In this illustrative example the movable barrier operator <b>101</b> comprises a control circuit <b>201</b> of choice. Such a control circuit <b>201</b> can comprise a fixed-purpose hard-wired platform or can comprise a partially or wholly programmable platform. All of these architectural options are well known and understood in the art and require no further description here. This control circuit <b>201</b> can be configured to carry out one or more of the steps, actions, or functions described herein as desired.
0029By one approach, when the control circuit <b>201</b> comprises a partially or wholly-programmable platform this can comprise programming the control circuit <b>201</b> in this manner. In such a case the computer instructions comprising this programming can be stored within the control circuit <b>201</b> itself and/or can be partially or wholly stored in one or more memory components <b>202</b>. Such an approach is well understood in the art and hence will not be further elaborated upon here.
0030This control circuit <b>201</b> operably couples to a transceiver <b>203</b>. This transceiver <b>203</b> can comprise, for example, a wireless transceiver. This transceiver <b>203</b> can comprise both a wireless radio-frequency transmitter that is configured to transmit in a first discrete band <b>204</b> as well as a wireless radio-frequency receiver. (As used herein, the expression “band” will be understood to refer to a range of allocated or otherwise defined radio-frequency communications spectrum that is bounded by a lower frequency and a higher frequency and that includes all of the intervening frequencies.) By one approach this first discrete band <b>204</b> can comprise an industrial, scientific, and medical (ISM) band as allocated by the United States Federal Communications Commission at around 900 MHz for unlicensed use in support of such activities. (Those skilled in the art will know that other regulatory entities around the world have allocated spectrum for like usage at various frequencies and these allocations, too, can be considered ISM bands.)
0031By one approach the aforementioned wireless radio-frequency receiver can be configured to receive in both of at least two discrete bands. This can comprise, for example, the aforementioned ISM band in the 900 MHz-range ISM band as well as another discrete band <b>207</b> that comprises a lower-frequency band such as an ultra-high frequency (UHF) band. Such an approach will serve well in a variety of application settings. That said, these teachings are not limited in these regards. Accordingly, either or both of these bands can comprise, for example, a very-high frequency (VHF) band, a global system for mobile communications-railway (GSMR) band, or the aforementioned UHF or ISM bands to note but a few examples in these regards.
0032In this illustrative example this transceiver <b>203</b> has two antennas <b>205</b> and <b>206</b> (which may comprise, for example, whip antennas as are known in the art). The first antenna <b>205</b> is used by the aforementioned transmitter and is tuned to that first discrete band <b>204</b>. (As used herein, the expression “tuned to” will be understood to refer to a configuration and choice of materials and components that are particularly selected and suitable to optimize transmission at the frequencies comprising that first discrete band <b>204</b>.) The second antenna <b>206</b> operably couples to the aforementioned receiver. Accordingly, the transceiver <b>203</b> uses this reception antenna <b>206</b> to receive both transmissions within that first discrete band <b>204</b> as well as within the second discrete band <b>207</b>. By one approach, and notwithstanding this dual-usage approach, this second antenna <b>206</b> is tuned to the second discrete band <b>207</b>.
0033As noted above, these antennas can be tuned to optimize performance with respect to certain transmission/reception bands. If desired, one or both of these antennas can also be optimized in other ways as well. For example, the transmission antenna <b>205</b> can be further optimized, if desired, for transmissions intended for a presumably stationary receiver. As another example, the reception antenna <b>206</b> can be further optimized, if desired, to receive transmissions from a presumably mobile transmitter (such as, for example, a movable barrier operator remote control transmitter located in a moving automobile).
0034Accordingly, for example, this transceiver <b>203</b> would use an antenna tuned to a UHF band both when receiving transmissions within the UHF band and also within an ISM band in the 900 MHz-range ISM band. This approach serves to reduce the cost and complexity of the resultant platform. Of course, this also means that the transceiver <b>203</b> is not quite as able to receive transmissions within the first discrete range <b>204</b> as compared to transmissions within the second discrete range <b>207</b>. These teachings can compensate for this reduced capability by configuring the devices that transmit to this movable barrier operator <b>101</b> to employ relatively greater power when transmitting using the first discrete band <b>204</b>.
0035As noted above, the specifics of such an example are intended to serve in an illustrative capacity and are not intended to comprise either an exhaustive presentation in these regards or a definitive limiting characterization. To underscore this point, and referring momentarily to <figref idref="DRAWINGS">FIG. 3</figref>, a corresponding process <b>300</b> will be presented.
0036Step <b>301</b> of this process <b>300</b> provides a wireless radio-frequency receiver configured to selectively receive in at least two discrete bands while step <b>302</b> provides a wireless radio-frequency transmitter configured to selectively transmit in at least one of the two discrete bands. This can mean, of course, that the wireless radio-frequency transmitter is configured to transmit in only of the two discrete bands. As a specific example already noted above, this could mean providing a receiver that can receive in both a UHF band and a 900 MHz band and providing a transmitter that can only transmit in the 900 MHz band.
0037Step <b>303</b> of this process <b>300</b> then provides for operably coupling a first antenna comprising a reception antenna to the wireless radio-frequency receiver, where the reception antenna is tune to a first one of the at least two discrete bands (such as the UHF band). Step <b>304</b>, in turn, provides for operably coupling a second antenna (that is different from the first antenna) to the wireless radio-frequency transmitter, where the transmission antenna is tuned to a second one of the at least two discrete bands that is different than the first one of the at least two discrete bands.
0038So configured, of course, this process <b>300</b> will then support an optional step <b>305</b> that provides for receiving movable barrier remote control transmissions via the reception antenna and the wireless radio-frequency receiver. These transmissions can comprise, for example, encrypted movable barrier remote control transmissions (including but not limited to encryption by converting binary information into trinary information as characterizes many movable barrier remote control transmissions).
0039Returning again to <figref idref="DRAWINGS">FIG. 2</figref>, if desired, this movable barrier operator <b>101</b> can further optionally comprise one or more end-user interfaces <b>208</b> that operably couple to the control circuit <b>201</b>. Examples in these regards might comprise, for example, sliding switches, push buttons, dual-in-line package (DIP) switches, a touch-screen display, and so forth). In this illustrative example, these end-user interfaces <b>208</b> comprise a part of the movable barrier operator <b>101</b> itself and therefore share, for example, the movable barrier operator's housing, chassis, and so forth.
0040Such a movable barrier operator <b>101</b> can also optionally comprise, as alluded to above, a motive component <b>209</b> of choice to selectively move the corresponding movable barrier <b>104</b>. This motive component <b>209</b> can include, for example, an alternating current or a direct current motor.
0041So configured, in addition to responding appropriately to one or more transmitters <b>112</b> that traditionally employ the UHF band this movable barrier operator <b>101</b> can also wirelessly interact with any of a plurality of two-way remote platforms such as one or more light fixtures <b>116</b>, obstacle detectors <b>115</b>, end-user interfaces <b>113</b> (such as wall-mounted buttons, open-door indicators, or the like), and any number of other mechanisms (represented here by an Nth remote platform <b>210</b>). Examples in these regards include, but are not limited to, movement sensors, infrared sensors, smoke detectors, fire detectors, light detectors, access-control mechanisms, alarm systems, and so forth.
0042By one approach, the transceiver <b>203</b> can operate as a frequency-hopping transceiver when using the first discrete band <b>204</b>. This can comprise, for example, hopping in a predetermined sequence through a given number of predetermined carrier frequencies (such as, for example, fifty different predetermined carrier frequencies). By one approach this can comprise using a given carrier frequency for only a predetermined amount of time (such as, for example, 10 milliseconds) before hopping to the next carrier frequency in the sequence. Using a frequency-hopping methodology can assist with overcoming interference when operating in relatively unstructured spectra such as the aforementioned ISM band (as, at least in many cases, a given interferer will not identically impact every available carrier frequency within a given band).
0043For many application settings it can be useful for the movable barrier operator <b>101</b> to only accept instructions from, or to otherwise communicate with, remote platforms that are authorized to engage the movable barrier operator <b>101</b> in that manner. These teachings accommodate at least two approaches to such authorization. First, these teachings will facilitate a movable barrier operator learning a given remote platform. And second, these teachings will also facilitate a movable barrier operator pairing with a given remote platform. Generally speaking, learning is based upon a one-way approach to communications whereas pairing relies upon a two-way communications ability between the movable barrier operator and the remote platform.
0044By one approach, this can comprise initiating, via the control circuit <b>201</b>, a relationship-establishment mode of operation. During this relationship-establishment mode of operation the control circuit <b>201</b> then operates in both a learn mode of operation and a pairing mode of operation. Generally speaking, this can comprise at least a presentation of credentials. By one approach this relationship-establishment mode of operation can be initiated upon detecting an end-user's assertion of the corresponding input interface (such as a particular end-user interface <b>208</b> as shown in <figref idref="DRAWINGS">FIG. 2</figref>). This might comprise, for example, simply detecting that the end user has asserted a specific push button. By one approach, a single push of such a button will suffice to instigate the control circuit <b>201</b> to carry out a sophisticated series of actions in these regards as described below.
0045In a learn mode of operation, for example, the control circuit <b>201</b> can receive (via the transceiver <b>203</b>) the credentials as pertain to a given one-way remote platform. These credential might comprise, for example, a fixed identifier for this one-way remote platform along with a rolling code value. (The use of fixed identifiers that are relatively unique to a given remote platform (or, in some cases, to the control circuit <b>201</b>) and rolling code values is well understood in the art. The interested reader is referred to U.S. Pat. No. 6,154,544, U.S. Pat. No. 7,492,905, U.S. Published Patent Application No. 2007/0058811, and U.S. Published Patent Application No. 2007/0005806, the full contents of each of which are hereby incorporated herein by this reference.)
0046In a pairing mode of operation, as another example, the control circuit <b>201</b> can again receive such credentials and/or can present its own corresponding credentials to the opposite entity. A pairing mode of operation will typically include some two-way exchange of information (at the very least, for example, some identifier for one entity that is, in turn, acknowledged by the receiving entity).
0047Referring now to <figref idref="DRAWINGS">FIGS. 4A and 4B</figref>, this can comprise utilizing a process <b>400</b> by which the aforementioned control circuit <b>201</b> implements both a learn mode of operation and a pairing mode of operation. In this particular example, the control circuit <b>201</b> conducts itself in a first manner for a first predetermined period of time. The control circuit <b>201</b> then conducts itself in a second, different manner for a subsequent predetermined period of time, followed by yet a third, different manner for a subsequent and concluding predetermined period of time. The durations of these periods of time can vary as desired. By one approach, the first period of time can be quite brief while the second and third periods of time are relatively considerably longer. If desired, the second and third periods of time can have a same or nearly the same duration. By way of illustration and without intending any limitations in these regards, the first period of time can be about three seconds and the second and third periods of time can each be about thirty seconds.
0048At step <b>401</b>, during the first predetermined period of time the control circuit <b>201</b> monitors for both learn-mode transmissions and pairing-mode transmissions. This can comprise not transmitting during this first period of time unless and until a pairing-mode transmission is received. By one approach, learn-mode transmissions may tend to occur (or may exclusively occur) in the second discrete band <b>207</b> (such as a UHF band) while pairing-mode transmissions may tend to occur (or may exclusively occur) in the first discrete band <b>204</b> (such as a 900 MHz ISM band). In such a case, the transceiver <b>203</b> can be controlled to alternate, for example, receiving in the second discrete band <b>207</b> with transceiving in the first discrete band <b>204</b>.
0049As a more specific example, and presuming that the first predetermined period of time is three seconds, this can comprise scanning the second discrete band <b>207</b> for a learn-mode transmission from a remote platform for some fraction of the three seconds and then switching to scanning a particular selected carrier frequency (or frequencies) of the first discrete band <b>204</b> for a pairing-mode transmission. The reception mode can toggle back and forth between a first reception band and a second reception band (that is at least partially different from the first reception band) in a temporally-interleaved manner between these two receive states until the three seconds concludes or until the transceiver <b>203</b> receives such a transmission.
0050At step <b>402</b>, upon receiving (during this first predetermined period of time) a learn-mode transmission that contains relationship-establishment content from a first transmitting platform (such as a one-way remote platform <b>112</b>), the control circuit <b>201</b> uses the content to learn the first transmitting platform to thereby facilitate recognizing and acting upon subsequent transmissions from that first transmitting platform. This would permit, for example, a traditional garage door wireless remote opener to transmit its fixed identifier and a current rolling code value to a movable barrier operator. (Those skilled in the art will recognize that this learn-mode transmission may have an identical message-field syntax as at least some subsequent transmissions although the specific contents of those fields may change from one transmission to the next; for example, a rolling code value will typically change with each episode as may a recovery identifier-specified area or areas.)
0051The latter could then store this information and use this information to authenticate a next transmission from this remote device. Upon authenticating that transmission the movable barrier operator could then validly respond, for example, to an “open” command by causing its movable barrier to move from a closed position to an open position.
0052Upon learning a remote device in this manner, step <b>403</b> provides for automatically concluding the relationship-establishment mode of operation notwithstanding that the first predetermined period of time may not have yet expired. These teachings would accommodate other approaches here if desired. For example, this step of monitoring for both learn-mode and pairing-mode transmissions could continue for any remaining portion of the first predetermined period of time.
0053As noted, step <b>401</b> provides for monitoring for both learn-mode and pairing-mode transmissions. Accordingly, it is possible that a pairing-mode transmission rather than a learn-mode transmission may be received. In this case, at step <b>404</b>, upon receiving (during the first predetermined period of time) a pairing-mode transmission from a second transmitting platform (which likely, but not necessarily, is different from the aforementioned first transmitting platform), the control circuit <b>201</b> can transceive relationship-establishment content with the second transmitting platform to thereby pair with that second transmitting platform. By one approach, and as shown here, the control circuit <b>201</b> can then automatically conclude this relationship-establishment mode of operation notwithstanding that the first predetermined period of time may not have yet expired.
0054To summarize, during a first predetermined period of time (such as about three seconds), the control circuit <b>201</b> can utilize the transceiver <b>203</b> to switch back and forth between receiving the first discrete band <b>207</b> to monitor for learn-mode transmissions and the second discrete band <b>204</b> to monitor for pairing-mode transmissions. The control circuit <b>201</b> prompts no transmissions during this time unless and until a transmission becomes appropriate upon receiving a pairing-mode transmission.
0055Upon concluding this first predetermined period of time without receiving either a learn-mode transmission or a pairing-mode transmission, at step <b>405</b> the control circuit <b>201</b>, for a second predetermined period of time (such as about thirty seconds), continues to monitor for learn-mode transmissions while now transmitting pairing-mode content.
0056By one approach, this can comprise again alternating monitoring for learn-mode transmissions via the second discrete band <b>207</b> with transmitting the pairing-mode content via the first discrete band <b>204</b>. More particularly, when employing a frequency-hopping methodology in the first discrete band <b>204</b> as suggested above, this can comprise briefly transmitting the pairing-mode content using a first frequency carrier within the first discrete band <b>204</b> and then briefly monitoring for a pairing response from a two-way remote platform. In the absence of such a response the pairing-mode content can again be briefly transmitted using a second frequency carrier as per the frequency-hopping sequence followed again by briefly monitoring that second frequency carrier for a response. This iterative use of a sequence of frequency carriers can be repeated many times, if desired, before switching to the second discrete band <b>207</b> to scan for a learn-mode transmission.
0057At step <b>406</b>, if and when the control circuit <b>201</b> receives, during the second predetermined period of time, a pairing-mode response, the control circuit <b>201</b> can facilitate completing the pairing based upon the pairing-mode response. By one approach, if desired, this step <b>406</b> can then provide for automatically concluding the relationship-establishment mode of operation notwithstanding that the second predetermined period of time may not have yet expired.
0058Somewhat similarly, at step <b>407</b>, if and when the control circuit <b>201</b> instead receives, during the second predetermined period of time, a learn-mode transmission containing relationship-establishment content from a transmitting platform, the control circuit <b>201</b> can responsively use that relationship-establishment content to learn the transmitting platform and thereby facilitate recognizing and acting upon subsequent transmissions from that transmitting platform. By one approach, if desired, this step <b>407</b> can then provide for automatically concluding the relationship-establishment mode of operation notwithstanding that the second predetermined period of time may not have yet expired.
0059If, instead, the second predetermined period of time shall expire without the transceiver <b>203</b> having receiving either learn-mode content or a pairing-mode response to its own pairing-mode transmissions, at step <b>408</b> the control circuit <b>201</b> can now only monitor for pairing-mode transmissions (unless and until a pairing-mode transmission is received) for a third predetermined period of time (such as, for example, about thirty seconds). As before, if and when a transmitting platform shall respond to such a pairing-mode transmission with its own pairing-mode response, the control circuit <b>201</b> can then pair with that transmitting platform and, if desired, automatically conclude this process <b>400</b> notwithstanding that the third period of time may not have yet expired.
0060If the third period of time shall conclude while the process <b>400</b> is still active, at step <b>409</b> the control circuit <b>201</b> then automatically concludes this relationship-establishment mode of operation and returns, for example, to its ordinary stand-by mode of operation.
0061These teachings are highly flexible in practice and will accommodate a wide variety of variations with respect to that presented above. As but one example in these regards, upon completing a learn-mode of operation during the aforementioned process <b>400</b> and in lieu of automatically concluding the relationship-establishment mode of operation this process <b>400</b> can provide instead for switching to only operating using the pairing-mode of operation during a remainder of the relationship-establishment mode of operation. By one approach this can continue as stated unless and until the transceiver <b>203</b> receives a pairing-mode transmission. This exclusive use of only the pairing-mode of operation can comprise, as desired, transmitting pairing-content and waiting for a corresponding pairing response (regardless of whether a pairing-mode transmission is actually received) or only monitoring for a pairing-mode transmission (in which case a pairing-mode transmission can be offered in response).
0062Such an approach (i.e., switching to a pairing-mode of operation following completion of a learn-mode of operation) can facilitate establishing a full relationship with a given platform that utilizes both traditional one-way remote-control transmissions and two-way data communications. In such a case, this approach will permit the control circuit <b>201</b> to both learn this given platform and to pair with this given platform during a single relationship-establishment mode of operation as instigated, for example, by a single push of a button by an end user.
0063This process <b>400</b> can also be modified, in lieu of the foregoing or in combination therewith, to switch to only operating using the learn mode of operation during a remaining portion of the relationship-establishment mode of operation upon completing the pairing mode of operation for a given platform. This can comprise, for example, only monitoring for learn-mode transmissions during a remaining portion of the relationship-establishment mode of operation under such circumstances.
0064If desired, these approaches (i.e., switching from a first mode of operation (either the learn-mode of operation or the pairing-mode of operation) following completion of second mode of operation) can be conditioned upon the particulars of the given platform. For example, when transmitting learn content and/or pairing content, this given platform can include information regarding itself in these regards. This information could be as simple as a single bit that serves to flag whether the given platform uses only a single relationship-establishment mechanism (i.e., learning or pairing) or both. The control circuit <b>201</b> could then utilize that information to determine whether to switch to an alternative relationship-establishment mechanism upon establishing a relationship with the given platform using a first mechanism in these regards.
0065The foregoing permits remote platforms to establish a relationship with, for example, a movable barrier operator. This, in turn, allows the movable barrier operator to trust transmissions from the remote platforms. This trust can be leveraged by having the movable barrier operator act in accordance with instructions and/or data as received from these remote platforms.
0066That a given remote platform may be trusted at one point in time, however, does not mean that such trust shall persist indefinitely. Accordingly, it can be useful to provide a mechanism to support disabling a previously-established authorized relationship with one or more remote platforms. <figref idref="DRAWINGS">FIG. 5</figref> depicts some approaches in these regards.
0067Pursuant to this process <b>500</b>, at step <b>501</b> the control circuit <b>201</b> detects an end-user assertion of an end-user interface <b>208</b>. This can comprise, for example, the end user asserting a push button. By one approach, this can require that the end user assert the end-user interface <b>208</b> for at least some particular duration of time (such as, for example, two seconds, six seconds, or some other duration of choice). A relatively lengthy duration requirement (such as at least six seconds) can help, in some application settings, to avoid inadvertently disabling previously-established authorized relationships.
0068At step <b>502</b>, and in response to detecting the end-user's assertion of the end-user interface <b>208</b>, the control circuit <b>201</b> can disable all previously-established authorized relationships for each of a first category of remote platforms. By one approach, for example, this first category of remote platforms can comprise previously learned relationships (as versus, for example, previously paired relationships). Or, if desired, this first category of remote platforms could comprise all previously paired relationships (as versus, for example, previously learned relationships).
0069By one approach, this disablement can comprise erasing the relationship information from the memory <b>202</b> of the apparatus. By another approach, if desired, this disablement can comprise tagging or flagging the relationship information in some manner of choice to permit the control circuit <b>201</b> to identify that information as no longer being honored.
0070So configured, a complete group of previously-learned relationships can be categorically disabled with a single end-user assertion of an end-user interface <b>208</b>. This can yield considerable savings in time when the end user seeks to disable a relatively large number of previously-established authorized relationships (such as, for example, five, twenty-five, or one hundred previously-established authorized relationships).
0071At step <b>503</b> this process <b>500</b> can next detect a second end-user assertion of that same end-user interface <b>208</b>. By one approach this can comprise that the end user has asserted this end-user interface <b>208</b> within some predetermined amount of time (such as one second, three seconds, six seconds, or some other duration of choice) of having previously asserted the end-user interface <b>208</b>. This approach can also comprise, in lieu of the foregoing or in combination therewith, determining that the end user has asserted the end-user interface <b>208</b> a second time for at least a second particular duration of time (such as one second, three seconds, six seconds, or the like). If desired, this required duration of time can match the duration of time required at step <b>501</b> when such is the case.
0072If desired, this “second” end-user assertion can comprise detecting that the end user continues to assert the end-user interface <b>208</b> beyond a time duration associated with detecting the aforementioned first end-user assertion and for at least some further required period of time. For example, to detect a first end-user assertion it may be required that the end user assert the end-user interface <b>208</b> for at least six seconds and to detect the second end-user assertion it may be required that the end user continues to assert the end-user interface <b>208</b> for at least an additional six seconds.
0073In response to detecting this second end-user assertion, at step <b>504</b> the control circuit <b>201</b> can disable previously-established relationships with each of a second category of remote platforms (where the second category is different from the first category). By one approach, for example, the first category can consist of learned relationships while the second category consists of paired relationships.
0074So configured, by use of a single end-user interface <b>208</b> and potentially by a single end-user assertion of that interface <b>208</b>, this process <b>500</b> will permit an end user to disable all previously-established authorized relationships with remote platforms as belong to a first category of such relationships as well as all previously-established authorized relationships with remote platforms as belong to a second category of such relationships. This process <b>500</b> will also permit this end user to be more selective in these regards and to disable only the relationships that comprise one of these categories but not both.
0075This process <b>500</b> will accommodate a wide variety of variations that may be useful in a particular application setting. For example, by one approach, the end user can manipulate the end-user interface <b>208</b> to select the particular category of previously-established relationships is to be first disabled. As one simple example in these regards, the end user could assert this same end-user interface <b>208</b> twice in quick succession to signal that a subsequent assertion of the end-user interface <b>208</b> is to result at step <b>502</b> in disablement of the previously-established authorized relationships as comprise the second category rather than the first category.
0076As another example in these regards, a first assertion of the end-user interface <b>208</b> can be detecting as a “second” assertion of the end-user interface <b>208</b> at step <b>503</b> when the end user asserts the end-user interface <b>208</b> at a time where there is no extant previously-established authorized relationship with the first category of remote platform.
0077There can be other circumstances when it may be useful to accommodate purposefully disabling a previously-established authorized relationship. For example, an installer or service technician may employ a service tool that requires a temporary established relationship with a given movable barrier operator in order to facilitate its operational functionality. In such a case the movable barrier operator can learn and/or pair with the service tool to establish the necessary relationship.
0078In this case, however, and referring now to <figref idref="DRAWINGS">FIG. 6</figref>, step <b>601</b> of the illustrated process <b>600</b> provides for maintaining, on a non-temporary basis, previously-established authorized wireless relationships for each of a first category of remote platforms (these comprising remote platforms, for example, other than service tools that only require a temporary relationship) while step <b>602</b> provides for maintaining, only on a temporary basis, at least a portion of the previously-established authorized wireless relationships for each of a second category of remote platforms (where the second category is of course different from the first category and can include, for example, service tools that only requires temporary access to and cooperation with the movable barrier operator).
0079As used herein, the word “temporary” will be understood to refer to a period of time of set duration (such as one minute, five minutes, fifteen minutes, one hour, or such other duration of choice). Accordingly, “non-temporary” will be understood to refer to a period of time of unlimited duration in that the duration is unspecified. For example, the first category of remote platforms can be maintained on a non-temporary basis by maintaining these relationships until specifically instructed otherwise by an external source (such as the end user as per, for example, the procedures described above).
0080As another example in these regards, the relationships for the second category of remote platforms can be maintained only as a function of at least one external input to the control circuit <b>201</b> (such as, for example, a command input to operate the control circuit <b>201</b> to cause a movable barrier to move). Using this approach, and by way of an illustrative example, a movable barrier operator will maintain a relationship with a service tool unless and until the movable barrier operator receives a command from other than the service tool (hence an “external” input) to open or close the movable barrier that the movable barrier operator controls. Upon receiving such a command, it may be presumed that normal operation has commenced and that the relationship with the service tool can be terminated.
0081By one approach, step <b>602</b> can comprise automatically disabling the second category of remote platforms after a predetermined period of time by, for example, partially or completely erasing the corresponding information from memory. This step will also accommodate other approaches in these regards, however, such as using flags or tags to denote the disabled or now-unauthorized status of the relationship.
0082As noted above, these teachings readily facilitate the employment of two-way data communications between, for example, a movable barrier operator and any number of remote platforms. These data communications can facilitate both giving and receiving instructions (for example, to open the movable barrier or to switch on a light) as well as providing status information (for example, that the movable barrier is open, that a light is on, or that smoke is sensed). By one approach, these components can utilize an acknowledgement (ACK)-based communications protocol to confirm receipt of a given transmission. If desired, an acknowledgement message can comprise a required element for essentially all received transmissions to ensure a reliable transference of content. This acknowledgement message can comprise a simple mere acknowledgement of having received a prior transmission (perhaps coupled with an identifier (or even an updated rolling code value) for the acknowledging platform). Or, if desired, this acknowledgement message can comprise more elaborate content (such as, for example, a verbatim presentation of the received content to permit a comparison of the information as received by the acknowledging platform with the information as originally transmitted to the acknowledging platform).
0083Such an acknowledgement scheme can be further leveraged, if desired, to support other system functionality. For example, a movable barrier operator may have timer-to-close functionality (where the movable barrier operator automatically closes a movable barrier at some particular time (such as five minutes) after the movable barrier opens) and/or remote-close functionality (where the movable barrier operator responds to a remote control instruction from a source that is not physically present at the movable barrier) that relies upon an ability to provide a signal (such as a flashing light) to alert persons who might be in the area of the movable barrier before actually closing the movable barrier in an unattended manner. In such a case, a message (such as an acknowledgement message) from the light fixture can provide the movable barrier operator with the required assurance that the necessary visual signal is available before acting upon such functionality.
0084<figref idref="DRAWINGS">FIG. 7</figref> presents one illustrative example in these regards. At step <b>701</b> of this process <b>700</b>, the control circuit <b>201</b> transmits a message to a remote peripheral platform (such as, but not limited to, a light fixture <b>116</b> as shown in <figref idref="DRAWINGS">FIG. 2</figref>). This can, of course, comprise a wireless transmission. The message itself can be particularly targeted to this particular remote peripheral platform or can be more generally directed to a group of remote platforms that includes this particular remote peripheral platform.
0085(Optional step <b>702</b> illustrates that the control circuit <b>201</b> can also transmit another message (or messages) to a second remote peripheral platform (or platforms) as desired. This second remote peripheral platform might comprise, for example, a second light fixture, an audible-announcing fixture, or essentially any other remote platform of choice.
0086The message itself can comprise a specific instruction and/or status content as desired.
0087In any event, at step <b>703</b> the control circuit <b>201</b> determines that the remote peripheral platform is presently able to carry out a given functionality. For example, when the remote peripheral platform comprises a light fixture, this can comprise determining that the light fixture is presently available and able to respond to the control circuit's command to flash a warning/alert light. By one approach, this determination can be based, at least in part, upon receiving an acknowledgement transmission (as described above) from the remote peripheral platform in response to the aforementioned message.
0088Upon making this determination, this step <b>703</b> then provides for responsively permitting a particular function to be carried out by the movable barrier operator. This can comprise, for example, permitting the movable barrier operator to carry out a timer-to-close function or a remote-close function. This can also comprise, if desired, having the remote peripheral platform carry out the given functionality (for example, by having the light fixture flash its light as a visual warning that the movable barrier is about to imminently carry out an automatic closure of the movable barrier).
0089As noted above, this process <b>700</b> can optionally include transmissions to other remote peripheral platforms. When these other remote peripheral platforms are not required or otherwise critical to the particular function to be carried out by the movable barrier operator, step <b>703</b> can optionally be carried out as described regardless of whether it can be ascertained that the second remote peripheral platform is presently able to carry out another given functionality. This can be useful, for example, when the second remote peripheral platform comprises a secondary light fixture and where an automated unattended barrier closure can be carried out safely regardless of whether the secondary light fixture is available or not.
0090Conversely, at step <b>704</b> and when the control circuit <b>201</b> determines that it cannot ascertain whether the remote peripheral platform is presently able to carry out the given functionality, the control circuit <b>201</b> can responsively prevent the movable barrier operator from carrying out the particular function. Accordingly, and by way of example, a failure to receive an acknowledgement transmission (for example, with a predetermined period of time, such as 500 milliseconds, one second, five seconds, or some other duration of choice) from the remote peripheral platform in response to the aforementioned transmitted message can provide a basis for prohibiting the given functionality.
0091As noted above, by one approach each wireless communication (or at least those that presume a two-way operational paradigm) can require a corresponding acknowledgement from the intended recipient. In the absence of such an acknowledgement, the source platform can repeat the original transmission (presuming that the original transmission failed to reach the intended recipient). While effective in many application settings to ensure that a given intended recipient in fact receives a particular transmission, such an approach can also occasion other problems. For example, the intended recipient may be unavailable for some extended period of time (due, for example, to a local power outage, a long-lived powerful interferer, damage, and so forth). In such a case, repeating the original transmission over and over again because of a lack of an acknowledgement can unduly burden the available bandwidth and potentially interfere with the overall operation of the system.
0092<figref idref="DRAWINGS">FIG. 8</figref> presents one process <b>800</b> to effectively deal with such a situation. At step <b>801</b> of this process <b>800</b> and upon detecting that a targeted remote platform has not acknowledged a wirelessly-transmitted first message, the control circuit <b>201</b> automatically re-transmits that first message up to X times (where X is an integer at least equaling “1”) until an acknowledgement message is received from the targeted remote platform. This might comprise, for example, re-transmitting this message a total of, say, four times. The timing interval between these repeated transmissions can be statically or dynamically determined as desired.
0093At step <b>802</b>, upon then detecting that the targeted remote platform did not acknowledge any of these re-transmitted messages, and further upon detecting that the targeted remote platform has also not acknowledged another wirelessly-transmitted second message, the control circuit <b>201</b> then automatically re-transmits this second message only up to X-Y times (where Y is an integer no greater than X). As an illustrative but non-limiting example in these regards, when X is set to “4” and Y is set to “2,” this step <b>802</b> will adjust the number of re-transmissions under these circumstances to only two repetitions rather than the usual four repetitions.
0094Accordingly, so configured, the control circuit <b>201</b> becomes more sparing of its use of available system resources when a given intended recipient repeatedly fails to acknowledge a series of independent messages. By one approach, Y can be set to equal X. In this case, under the circumstances described, step <b>802</b> will prevent the control circuit <b>201</b> from providing even a single re-transmission of an unacknowledged transmission.
0095Eventually, of course, this intended recipient will again begin receiving and acknowledging its messages. Accordingly, at optional step <b>803</b>, upon detecting that the targeted remote platform (subsequent to having not acknowledged re-transmitted messages) did acknowledge having received a wirelessly-transmitted message, and further upon detecting that the targeted remote platform has now again not acknowledged a wireless-transmitted subsequent message, the control circuit <b>201</b> can again automatically re-transmit the subsequent message up to X times until an acknowledgement message is received from the targeted remote platform. In other words, operationally, this process <b>800</b> can begin anew under such circumstances.
0096By one approach, if desired and as a part of step <b>802</b>, this process <b>800</b> can revert to step <b>801</b> as a function of time even though the targeted recipient still fails to acknowledge received messages. For example, if the targeted recipient continuously fails to acknowledge messages for a period of twelve hours, it may be useful to more aggressively re-transmit unacknowledged messages to this targeted recipient on a temporary basis in an attempt to better the situation.
0097By one approach, if desired, this process <b>800</b> can be modified to incrementally decrement the number of attempted re-transmissions at step <b>802</b>. For example, initially, when X equals 4, Y may be set to 1 so that up to three re-transmissions are attempted. With a next message that the target fails to acknowledge, Y can then be set to 2 so that only up to two re-transmissions are attempted. This can continue until Y equals some particular stable value which the control circuit <b>201</b> employs thereafter as described.
0098Another problem that can occasionally arise when mandating acknowledgment messages is that a number of platforms can all attempt to transmit their required acknowledgement at the same time with one another. This can lead to signal collisions that prevent successful reception of some or all of the colliding messages. This, in turn, can lead to unwarranted re-transmissions of the original message in order to elicit a corresponding acknowledgement which again leads to another round of acknowledgement message collisions.
0099To assist in these regards these teachings will accommodate temporally parsing a given carrier frequency into a plurality of time slots. Certain of these time slots can be assigned to two-way remote platforms that have an established relationship with the movable barrier operator <b>101</b>. As a simple example in these regards, each carrier frequency opportunity can be parsed into twenty-two equally-sized transmit/receive pairs of time slots. A first such pair of time slots can be assigned to a remote platform that has also been assigned the network identifier “1.” A second such pair of time slots can be similarly assigned to a remote platform that has been assigned the network identifier “2.” Such a one-for-one assignment protocol can serve to pre-assign up to twenty-two remote platforms to a corresponding pair of time slots.
0100This time slotting, however, need not always dictate the transmission behavior of the remote platforms. Instead, if desired, the remote platforms may be permitted to unilaterally transmit at essentially any time during this parsed period of time when self-sourcing a specific communication (such as when providing an end-user instruction to a movable barrier operator or when reporting a monitored condition (such as the detected presence of an obstacle in the pathway of a moving movable barrier)). Such asynchronous transmissions can be readily accommodated in most application settings due to a likelihood of relatively low levels of traffic on the one hand and the aforementioned acknowledgement protocol that will tend to assure that the transmitting platform will re-transmit its message until an appropriate acknowledgement is received.
0101That said, there are other scenarios where observation of the aforementioned time slots can be required on the part of the remote platforms. <figref idref="DRAWINGS">FIG. 9</figref> presents an illustrative process <b>900</b> in these regards. This particular process <b>900</b> is particularly useful when implemented by a control circuit (including control circuits at remote platforms) having a unique system identifier (as assigned, for example, by a movable barrier operator and where that unique system identifier can be correlated (one-on-one) with a given time slot (which can include a pair of time slots to accommodate both transmissions and receptions, respectively).
0102Presuming such a configuration, at step <b>901</b> the control circuit receives an individually-targeted communication directed to itself. In response, this step <b>901</b> provides for transmitting a corresponding acknowledgement message in a time slot as defined by the above-described time slot-based protocol but without concern for whether the particular utilized time slot is one that has been previously correlated with and assigned to this particular control circuit/remote platform. Accordingly this acknowledgement message is transmitted in a time slot of convenience (such as a next-occurring time slot) regardless of whether that time slot corresponds to the unique system identifier as corresponds to this control circuit.
0103So configured, the control circuit can quickly respond with its acknowledgement upon receiving a communication that is individually targeted to that control circuit (i.e., that remote platform). Under the circumstances this approach is not especially likely to lead to a transmission collision as there is no particular anticipated reason why another remote platform would also be trying to transmit its own acknowledgement message at this time and, as noted above, traffic conditions will likely be otherwise relatively light in many application settings.
0104These teachings will also accommodate, however, a multi-target broadcast communication in addition to individually-targeted communications. Such a multi-target broadcast might be received, for example, by twenty or so remote platforms (and/or movable barrier operators). Per the dictates of the described protocol, each of these platforms is expected to respond with a corresponding acknowledgement.
0105Now, of course, having each of the remote platforms utilize a next-occurring time slot is considerably more likely to lead to transmission collisions. A similar result can be expected if these platforms are permitted to respond ad hoc without concern for the time slotting protocol.
0106Accordingly, to aid with avoiding such collisions, at step <b>902</b> this process <b>900</b> provides under such circumstances for transmitting the corresponding acknowledgement message in a time slot that uniquely corresponds to the unique system identifier (in other words, in the transmission time slot that has been previously assigned to this particular control circuit/remote platform. Such an approach will tend to assure that each acknowledging platform will transmit in a non-overlapping manner with the other acknowledging platform, hence avoiding collisions.
0107So configured, these teachings provide for an efficient and cost-effective approach to supporting two-way wireless data communications. What is more, these approaches are flexible in practice and can readily accommodate a variety of regulatory requirements or guidelines as may pertain to a given application setting.
0108Those skilled in the art will recognize that a wide variety of modifications, alterations, and combinations can be made with respect to the above described embodiments without departing from the spirit and scope of the invention, and that such modifications, alterations, and combinations are to be viewed as being within the ambit of the inventive concept.
Contents4
10 sheets
Sheet 1 Sheet 2 Sheet 3 Sheet 4 Sheet 5 Sheet 6 Sheet 7 Sheet 8 Sheet 9 Sheet 10
Every citation, both ways
| Document | Relation | Office | Cited during |
|---|---|---|---|
| US11795753B1 | Cited by | United States of America | Search report |
| US2023340831A1 | Cited by | United States of America | Search report |
| US11746584B2 | Cited by | United States of America | Search report |
| US12367752B2 | Cited by | United States of America | Search report |
| US2025215736A1 | Cited by | United States of America | Search report |
| US2023143698A1 | Cited by | United States of America | Search report |
| US2025179856A1 | Cited by | United States of America | Search report |
| US2001026539A1 | Cites | United States of America | Search report |
| US2002041578A1 | Cites | United States of America | Search report |
| US2002163905A1 | Cites | United States of America | Search report |
| US2003214385A1 | Cites | United States of America | Applicant |
| US2004085185A1 | Cites | United States of America | Search report |
| US2005272372A1 | Cites | United States of America | Applicant |
| US2006158344A1 | Cites | United States of America | Search report |
| US2008233964A1 | Cites | United States of America | Search report |
| US2008309535A1 | Cites | United States of America | Applicant |
| US2009175184A1 | Cites | United States of America | Search report |
| US2010034141A1 | Cites | United States of America | Search report |
| US2010056055A1 | Cites | United States of America | Applicant |
| US2010135225A1 | Cites | United States of America | Search report |
| US2010141381A1 | Cites | United States of America | Applicant |
| US2010202327A1 | Cites | United States of America | Search report |
| US2010312881A1 | Cites | United States of America | Search report |
| US2012092124A1 | Cites | United States of America | Applicant |
| US2012094604A1 | Cites | United States of America | Applicant |
| US3815104A | Cites | United States of America | Search report |
| US3988676A | Cites | United States of America | Applicant |
| US4691202A | Cites | United States of America | Search report |
| US5266925A | Cites | United States of America | Search report |
| US5404355A | Cites | United States of America | Search report |
| US5539394A | Cites | United States of America | Search report |
| US5761197A | Cites | United States of America | Search report |
| US5872513A | Cites | United States of America | Applicant |
| US5880721A | Cites | United States of America | Applicant |
| US6031832A | Cites | United States of America | Search report |
| US6091343A | Cites | United States of America | Applicant |
| US6275476B1 | Cites | United States of America | Search report |
| US6310548B1 | Cites | United States of America | Search report |
| US6346889B1 | Cites | United States of America | Search report |
| US6388559B1 | Cites | United States of America | Search report |
| US6424056B1 | Cites | United States of America | Search report |
| US6738602B1 | Cites | United States of America | Applicant |
| US6903650B2 | Cites | United States of America | Search report |
| US6907029B2 | Cites | United States of America | Search report |
| US6965580B1 | Cites | United States of America | Search report |
| US6990588B1 | Cites | United States of America | Applicant |
| US7005985B1 | Cites | United States of America | Search report |
| US7161952B1 | Cites | United States of America | Search report |
| US7221256B2 | Cites | United States of America | Applicant |
| US7266344B2 | Cites | United States of America | Applicant |
| US7271727B2 | Cites | United States of America | Search report |
| US7346374B2 | Cites | United States of America | Applicant |
| US7375484B2 | Cites | United States of America | Search report |
| US7506057B2 | Cites | United States of America | Applicant |
| US7602835B1 | Cites | United States of America | Applicant |
| US7708048B2 | Cites | United States of America | Search report |
| US7733213B2 | Cites | United States of America | Applicant |
| US7865813B2 | Cites | United States of America | Search report |
| US7979769B2 | Cites | United States of America | Search report |
| US8085131B2 | Cites | United States of America | Search report |
| US8243581B2 | Cites | United States of America | Search report |
| US8259636B2 | Cites | United States of America | Search report |
| US8380359B2 | Cites | United States of America | Applicant |
| US8392808B2 | Cites | United States of America | Search report |
| US8773242B2 | Cites | United States of America | Search report |
| USRE42254E | Cites | United States of America | Search report |
| US20010026539A1 | Cites | United States of America | Search report |
| US20020041578A1 | Cites | United States of America | Search report |
| US20020163905A1 | Cites | United States of America | Search report |
| US20030214385A1 | Cites | United States of America | Applicant |
| US20040085185A1 | Cites | United States of America | Search report |
| US20050272372A1 | Cites | United States of America | Applicant |
| US20060158344A1 | Cites | United States of America | Search report |
| US20080233964A1 | Cites | United States of America | Search report |
| US20080309535A1 | Cites | United States of America | Applicant |
| US20090175184A1 | Cites | United States of America | Search report |
| US20100034141A1 | Cites | United States of America | Search report |
| US20100056055A1 | Cites | United States of America | Applicant |
| US20100135225A1 | Cites | United States of America | Search report |
| US20100141381A1 | Cites | United States of America | Applicant |
| US20100202327A1 | Cites | United States of America | Search report |
| US20100312881A1 | Cites | United States of America | Search report |
| US20120092124A1 | Cites | United States of America | Applicant |
| US20120094604A1 | Cites | United States of America | Applicant |
| “Home Control Solution” Owner's Manual; Wayne Dalton Part No. 333394, Jul. 20, 2007 (cover through p. 18). | Non-patent | – | Applicant |
| “Prodrive Garage Door Opener Installation Instructions and Owner's Manual,” Wayne Dalton Part No. 325809, Jul. 16, 2008 (cover to cover) (pertaining to a Z-wave capable garage door opener of the type referred to in the “Home Control Solution” Owners Manual Submitted herewith). | Non-patent | – | Applicant |
| Bluetooth Standard, Jul. 26, 2007, pp. 534-536. | Non-patent | – | Applicant |
| “Home Control Solution” Owner's Manual; Wayne Dalton Part No. 333394, Jul. 20, 2007 (cover through p. 18). | Non-patent | – | Applicant |
| “Prodrive Garage Door Opener Installation Instructions and Owner's Manual,” Wayne Dalton Part No. 325809, Jul. 16, 2008 (cover to cover) (pertaining to a Z-wave capable garage door opener of the type referred to in the “Home Control Solution” Owners Manual Submitted herewith). | Non-patent | – | Applicant |
| Bluetooth Standard, Jul. 26, 2007, pp. 534-536. | Non-patent | – | Applicant |
5 members in 2 offices; this record represents the family
Priority claims2
| Document | Office | Kind | Date |
|---|---|---|---|
| 90557310 | United States of America | A | |
| US20100905573 | – | – | – |
Members5
| Document | Office | Kind | |
|---|---|---|---|
| CA2753675A1 | Canada | A1 | |
| US2012092125A1 | United States of America | A1 | |
| US9734645B2This record | United States of America | B2 | |
| US2017316628A1 | United States of America | A1 | |
| US11200769B2 | United States of America | B2 |
101 transactions on the USPTO file
Allowed after 3 non-final rejections, 2 final rejections, 1 RCE and 1 appeal.
- Non-final rejections
- 3
- Final rejections
- 2
- RCEs
- 1
- Appeals
- 1
Over time
Point at a mark for the transactionTransactions
| Event | Code | |
|---|---|---|
| Email NotificationEML_NTR | EML_NTR | |
| Change in Power of Attorney (May Include Associate POA)PA.. | PA.. | |
| Change in Power of Attorney (May Include Associate POA)PA.. | PA.. | |
| Payment of Maintenance Fee, 8th Year, Large EntityM1552 | M1552 | |
| Application ready for PDX access by participating foreign officesCCRDY | CCRDY | |
| Application ready for PDX access by participating foreign officesCCRDY | CCRDY | |
| Payment of Maintenance Fee, 4th Year, Large EntityM1551 | M1551 | |
| Correspondence Address ChangeC.ADB | C.ADB | |
| Recordation of Patent Grant MailedPGM/ | PGM/ | |
| Patent Issue Date Used in PTA CalculationAllowedPTAC | PTAC | |
| Issue Notification MailedAllowedWPIR | WPIR | |
| Dispatch to FDCD1935 | D1935 | |
| Application Is Considered Ready for IssuePILS | PILS | |
| Mail Response to 312 Amendment (PTO-271)MN271 | MN271 | |
| Response to Amendment under Rule 312N271 | N271 | |
| Response to Reasons for AllowanceREAS | REAS | |
| Amendment after Notice of Allowance (Rule 312)AllowedA.NA | A.NA | |
| Issue Fee Payment VerifiedN084 | N084 | |
| Issue Fee Payment ReceivedIFEE | IFEE | |
| Response to Reasons for AllowanceREAS | REAS | |
| Workflow - Drawings FinishedDRWF | DRWF | |
| Mail PUB other miscellaneous communication to applicantMM327-D | MM327-D | |
| PUB Other miscellaneous communication to applicantM327-D | M327-D | |
| Mail Notice of AllowanceAllowedMN/=. | MN/=. | |
| Notice of Allowance Data Verification CompletedAllowedN/=. | N/=. | |
| Reasons for Allowance | – | |
| Examiner's Amendment Communication | – | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Disposal for a RCE / CPA / R129AbandonedABN9 | ABN9 | |
| Request for Continued Examination (RCE)RCEX | RCEX | |
| Request for Extension of Time - GrantedXT/G | XT/G | |
| Workflow - Request for RCE - BeginBRCE | BRCE | |
| Mail Advisory Action (PTOL - 303)MCTAV | MCTAV | |
| After Final Consideration Program Amendment too ExtensiveAFNE | AFNE | |
| Advisory Action (PTOL-303)CTAV | CTAV | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| PILOT- Request for After Final Consideration ProgramRAFC | RAFC | |
| Response after Final ActionA.NE | A.NE | |
| Mail Final Rejection (PTOL - 326)Final rejectionMCTFR | MCTFR | |
| Final RejectionFinal rejectionCTFR | CTFR | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Response after Non-Final ActionA... | A... | |
| Request for Extension of Time - GrantedXT/G | XT/G | |
| Mail Non-Final RejectionNon-final rejectionMCTNF | MCTNF | |
| Non-Final RejectionNon-final rejectionCTNF | CTNF | |
| Interview Summary - Examiner Initiated - TelephonicEXET | EXET | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Appeal Brief Review CompleteAPBR | APBR | |
| track 1 OFFT1OFF | T1OFF | |
| Appeal Brief FiledAP.B | AP.B | |
| Notice of Appeal FiledN/AP | N/AP | |
| Mail Final Rejection (PTOL - 326)Final rejectionMCTFR | MCTFR | |
| Final RejectionFinal rejectionCTFR | CTFR | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Response after Non-Final ActionA... | A... | |
| Request for Extension of Time - GrantedXT/G | XT/G | |
| Mail Non-Final RejectionNon-final rejectionMCTNF | MCTNF | |
| Non-Final RejectionNon-final rejectionCTNF | CTNF | |
| Information Disclosure Statement considered | – | |
| Information Disclosure Statement considered | – | |
| Electronic Information Disclosure StatementEIDS. | EIDS. | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Response after Non-Final ActionA... | A... | |
| Request for Extension of Time - GrantedXT/G | XT/G | |
| Reference capture on IDSRCAP | RCAP | |
| Information Disclosure Statement (IDS) Filed | – | |
| Information Disclosure Statement (IDS) Filed | – | |
| Mail Non-Final RejectionNon-final rejectionMCTNF | MCTNF | |
| Non-Final RejectionNon-final rejectionCTNF | CTNF | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Information Disclosure Statement (IDS) Filed | – | |
| Reference capture on IDSRCAP | RCAP | |
| Information Disclosure Statement (IDS) Filed | – | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Electronic Information Disclosure StatementEIDS. | EIDS. | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Electronic Information Disclosure StatementEIDS. | EIDS. | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Electronic Information Disclosure StatementEIDS. | EIDS. | |
| PG-Pub Issue NotificationPG-ISSUE | PG-ISSUE | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Electronic Information Disclosure StatementEIDS. | EIDS. | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Application Dispatched from OIPEOIPE | OIPE | |
| Application Is Now CompleteCOMP | COMP | |
| Sent to Classification ContractorPGPC | PGPC | |
| Filing Receipt - UpdatedFLRCPT.U | FLRCPT.U | |
| Additional Application Filing FeesADDFLFEE | ADDFLFEE | |
| A statement by one or more inventors satisfying the requirement under 35 USC 115, Oath of the ApplicOATHDECL | OATHDECL | |
| Applicants have given acceptable permission for participating foreignAPPERMS | APPERMS | |
| Notice Mailed--Application Incomplete--Filing Date AssignedINCD | INCD | |
| Filing ReceiptFLRCPT.O | FLRCPT.O | |
| Cleared by OIPE CSR | – | |
| IFW Scan & PACR Auto Security Review | – |
9 legal events, as the office reported them to INPADOC
Over the term
Point at a mark for the eventEvents
| Event | Code | |
|---|---|---|
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| Maintenance fee paymentMAFP | MAFP | |
| Information on status: patent grantGrantedPATENTED CASESTCF | STCF | |
| AssignmentAS | AS |
Numbers
- Publication
- 09734645
- Publication, DOCDB
- 9734645
- Publication, EPODOC
- US9734645
- Application
- 12905573
- Application, DOCDB
- 90557310
- Application, EPODOC
- US20100905573
Titles
- English
- Method and apparatus pertaining to message-based functionality
Patent term adjustment
- A delay
- +834 daysthe office missed an examination deadline
- B delay
- +1,307 dayspendency past three years
- Overlap
- −164 daysdelays counted once
- Applicant delay
- −220 days
- Net adjustment
- 1,757 days
Classification
- CPC, 13
- G07C9/00111
- E05F15/668
- G07C9/28
- E05F15/00
- E05Y2400/50
- E05Y2400/822
- E05F15/77
- E05Y2800/424
- E05F15/79
- E05Y2800/00
- E05Y2400/59
- E05Y2900/106
- E05Y2400/83
- IPC, 6
- H04H20 71
- G07C9 00
- E05F15 668
- E05F15 00
- E05F15 77
- E05F15 79
- USPC, 1
- 001001000