Notice of Pre-AIA or AIA Status
The present application, filed on or after March 16, 2013, is being examined under the first inventor to file provisions of the AIA .
DETAILED ACTION
Claims 1-21 are presented for examination.
Claim Rejections - 35 USC § 101
35 U.S.C. 101 reads as follows:
Whoever invents or discovers any new and useful process, machine, manufacture, or composition of matter, or any new and useful improvement thereof, may obtain a patent therefor, subject to the conditions and requirements of this title.
Claims 1, 8, and 15 are rejected under 35 USC 101.
The claimed inventions are directed to non-statutory subject matter. The claim(s) are ineligible under 101 because each respective claim is directed to an Abstract idea, to include organizing human activity via geofenced alerting; mental process/evaluative selection; data receipt/transmission) and does not integrate them into a practical application. The additional elements do not provide “significantly more.”
For the same reasons, claims 2, 7, 9-14, and 16-21 are also rejected for depending on the above rejected claims. See the “Remarks” section for further clarification.
Claim Rejections - 35 USC § 102(a)(1)
A person shall be entitled to a patent unless –
(a) NOVELTY; PRIOR ART.—A person shall be entitled to a patent unless—
(1) the claimed invention was patented, described in a printed publication, or in public use, on sale, or otherwise available to the public before the effective filing date of the claimed invention
Claims 1-21 are rejected over 35 USC 102(a)(1) as being unpatentable over Poder, U.S. 2012/0169487.
On claim 1, Poder cites:
A method comprising:
receiving, by a computing device associated with a premises,
figure 4, and [0039] security system 400, one or more properties (which meets the claimed “premesis”), and any one of the cited processors 431, 421, 411, and 441.
information indicating that a security condition has occurred in proximity to the premises;
[0039] Security system 400 may include one or more security sensor nodes 410 (which may correspond to or be used with security sensors 306 and 307, cameras 310, and/or vehicle sensors 311 of FIG. 3)
and
sending, by the computing device
[0045] The various motion, position, location, movement, etc. detected by the security sensor node 410 may be reported via the LAN interface 414 to the alarm panel 420. The alarm panel 420 may operate within security system 400 to monitor one or more security sensor nodes 410 included in security system 400, and may provide additional functionalities, such as allowing a user to arm security system 400 and/or security sensor nodes 410. For instance, alarm panel 420 may be attached to a wall near an entrance to a secured area, and a user may interact with alarm panel 420 to arm security system 400 and/or security sensor nodes 410. In addition, alarm panel 420 may include a plurality of components, as further described below, that may enable alarm panel 420 to communicate with other devices included in security system 400 and thereby provide arming, monitoring, and other functionalities.
(the claimed “computing device” can be the cited processors 411 or 412 obtaining sensor information from sensors 415, 416, or sensor interface 445)
to a server, an indication of the security condition, wherein the indication is configured to cause the server to send an alert message to one or more wireless devices within a threshold distance of the premises based on location information associated with the premises.
[0037] Meanwhile, the web portal server 318 may be a computing device capable of providing a web portal through which users may view, on any connected display device, information regarding the security of the premises 300 and vehicle 301. Users may log-on to the web portal provided by the web portal server 318 and view an alarm event and/or information related to an alarm event, such as what sensor was triggered and when it was triggered.
[0045] For instance, alarm panel 420 may be attached to a wall near an entrance to a secured area, and a user may interact with alarm panel 420 to arm security system 400 and/or security sensor nodes 410. In addition, alarm panel 420 may include a plurality of components, as further described below, that may enable alarm panel 420 to communicate with other devices included in security system 400 and thereby provide arming, monitoring, and other functionalities.
On claim 2, Poder cites:
The method of claim 1, wherein the indication of the security condition comprises one or more of an image or video associated with the security condition, and wherein the alert message comprises the one or more of the image or video.
[0037] Meanwhile, the web portal server 318 may be a computing device capable of providing a web portal through which users may view, on any connected display device, information regarding the security of the premises 300 and vehicle 301. Users may log-on to the web portal provided by the web portal server 318 and view an alarm event and/or information related to an alarm event, such as what sensor was triggered and when it was triggered. Also through the web portal, a user may be able to view video of the premises 300 captured by the camera 310 or may be able to check the status of the security system to see if it is armed.
On claim 3, Poder cites:
The method of claim 1, wherein the indication of the security condition is further
configured to cause the server to send the alert message to:
the one or more wireless devices via a first protocol,
and at least one other wireless device via a second protocol different from the first protocol.
[0042] The security sensor node 410 may include one or more user interfaces 413. The user interfaces 413 may be, for example, any desired type of device to allow interaction with a user, such as buttons, lights, LED displays, audio speakers, etc. Additionally, the security sensor node 410 may include a local area network (LAN) interface 414. The LAN interface 414 may implement any desired type of communication medium for communicating signals between all components in the premises. For example, the LAN interface 414 may be a wireless IEEE 802.11 interface, allowing the security sensor node 410 to wirelessly communicate with the alarm panel 308, gateway 430, one or more vehicle security nodes 440, and/or other devices. Other wireless interfaces could be used as well, such as 802.15.4, ZigBee, Z-Wave, Bluetooth, etc. The LAN interface 414 can also use a wired medium, such as a MoCA (Multimedia Over Coax Alliance) interface connected to the in-home coaxial cable network, or to an Ethernet network.
On claim 4, Poder cites:
The method of claim 1, wherein the one or more wireless devices are within one or more of:
a services area associated with the premises, a police services boundary, an emergency medical services boundary, or a neighborhood group.
[0050] While the examples discussed above involve sending heartbeat messages with additional data reflecting a situation in which a burglar alarm has been tripped at premises 300, similar data may likewise be embedded into the heartbeat messages of a security system in other situations in which it may be desirable to notify other devices and users in a localized area of the occurrence of a particular event.
On claim 5, Poder cites:
The method of claim 1, wherein the indication of the security condition comprises a heartbeat message.
[0050] While the examples discussed above involve sending heartbeat messages with additional data reflecting a situation in which a burglar alarm has been tripped at premises 300, similar data may likewise be embedded into the heartbeat messages of a security system in other situations in which it may be desirable to notify other devices and users in a localized area of the occurrence of a particular event.
On claim 6, Poder cites:
The method of claim 1, wherein the indication of the security condition comprises an indication of one or more of:
output of a door sensor;
output of a smoke detector;
output of a glass-break sensor
[0029] FIG. 3 is a diagram showing an example operating environment in which various features described herein may be performed and implemented. The environment may include a premises 300 (which may correspond to the premises 102 of FIG. 1), such as a user residence, business, recreational facility, etc. (referred to herein as a user residence or premises in a non-limiting manner), a vehicle 301, and a local office 302 (which may correspond to the local office 103 of FIG. 1). One or more properties located on the premises 300, such as a television 303, may be secured according to one or more aspects described herein. The premises 300 may include one or more doors 304 and a plurality of windows 305. The doors 304 may be secured by an associated door security sensor 306 (e.g., a proximity sensor, contact switch, motion detector, etc.). In addition, each of the plurality of windows 305 may be secured by associated window security sensors 307, which may be similar to the door security sensor 306. The security sensors 306 and 307 may be communicatively coupled to an alarm panel 308, which may allow the security sensors 306 and 307 to be armed, disarmed, and monitored. For instance, a user may operate alarm panel 308 to arm security sensors 306, such that if a door 304 is opened while the associated security sensor 306 is armed, an alarm will be triggered. Herein, triggering an alarm may result in various actions, for example, playing an alarm sound, presenting an alarm message, turning on/off lights, turning on cameras, etc. In one arrangement, the alarm panel 308 may be implemented in and/or as part of gateway 309. Thus, in one example, gateway 309 may be communicatively coupled to security sensors 306 and 307, which may allow gateway 309 to arm, disarm, and/or monitor the security sensors 306 and 307. While the description above focuses on door security sensors 306 and window security sensors 307, many other security sensors and devices may be communicatively coupled to the alarm panel 308 and/or gateway 309. For example, the alarm panel 308 may be communicatively coupled to one or more cameras 310, which may record video to monitor the premises 300 and surrounding area.
On claim 7, Poder cites:
The method of claim 1, wherein the computing device comprises a mobile device, and wherein the indication of the security condition comprises a location of the mobile device and the location information associated with the premises.
[0031] The mobile security node or vehicle security node can be implemented as a computing device, and can be a dedicated security device akin to a traditional car alarm and computing systems. Alternatively, the mobile security node can be implemented as any other portable computing device, such as a smartphone, tablet, house key, etc. As mentioned above, the mobile security node may be referred to as a vehicle security node for clarity. However, use of the term "vehicle security node" should be interpreted in a non-limiting manner, and where reference is made to a vehicle, vehicle security node, and vehicle sensors, the functions and features of these elements may be similarly implemented with a mobile device (e.g., a smartphone, tablet, house key, etc.), a mobile security node, and sensors designed/adapted for a mobile device. Therefore, where a mobile security node is implemented on, for example, a smartphone, an alarm system of the smartphone may be integrated with the security system of the premises 300 when the mobile security node is in range of the security system.
On claim 8, Poder cites:
A computing device comprising:
one or more processors;
(the claimed “one or more processors” can be the cited processors 411 or 412 obtaining sensor information from sensors 415, 416, or sensor interface 445 disclosed in figure 4)
and
memory storing instructions
figure 4 includes memories 442, 412, 422, and 432.
[0025] FIG. 2 illustrates general hardware elements that can be used to implement any of the various computing devices discussed herein. The computing device 200 may include one or more processors 201, which may execute instructions of a computer program to perform any of the features described herein. The instructions may be stored in any type of computer-readable medium or memory, to configure the operation of the processor 201.
that, when executed by the one or more processors, cause the computing device to:
receive,
by the computing device associated with a premises,
information indicating that a security condition has occurred in proximity to the premises;
and send, to a server, an indication of the security condition, wherein the indication is configured to cause the server to send an alert message to one or more wireless devices within a threshold distance of the premises based on location information associated with the premises.
See the rejection of claim 1 which discloses the same subject matter as claim 8 and is rejected for the same reasons.
On claim 9, Poder cites:
The computing device of claim 8, wherein the indication of the security condition comprises one or more of an image or video associated with the security condition, and wherein the alert message comprises the one or more of the image or video.
See the rejection of claim 2 which discloses the same subject matter as claim 9 and is rejected for the same reasons.
On claim 10, Poder cites:
The computing device of claim 8, wherein the indication of the security condition is 10. further configured to cause the server to send the alert message to: the one or more wireless devices via a first protocol, and at least one other wireless device via a second protocol different from the first protocol.
See the rejection of claim 3 which discloses the same subject matter as claim 10 and is rejected for the same reasons.
On claim 11, Poder cites:
The computing device of claim 8, wherein the one or more wireless devices are within one or more of: a services area associated with the premises, a police services boundary, an emergency medical services boundary, or a neighborhood group.
See the rejection of claim 4 which discloses the same subject matter as claim 11 and is rejected for the same reasons.
On claim 12, Poder cites:
The computing device of claim 8, wherein the indication of the security condition
comprises a heartbeat message.
See the rejection of claim 5 which discloses the same subject matter as claim 12 and is rejected for the same reasons.
On claim 13, Poder cites:
The computing device of claim 8, wherein the indication of the security condition comprises an indication of one or more of: output of a door sensor; output of a window sensor; output of a smoke detector; output of a glass-break sensor; an image or video associated with output of one or more sensors at the premises; triggering of an alarm at the premises; user input to the computing device at the premises; or a request for assistance.
See the rejection of claim 6 which discloses the same subject matter as claim 13 and is rejected for the same reasons.
On claim 14, Poder cites:
The computing device of claim 8, wherein the computing device comprises a mobile device, and wherein the indication of the security condition comprises a location of the mobile device and the location information associated with the premises.
See the rejection of claim 7 which discloses the same subject matter as claim 14 and is rejected for the same reasons.
On claim 15, Poder cites:
One or more non-transitory computer-readable media storing instructions
that, when executed, cause:
by a computing device associated with a premises,
information indicating that a security condition has occurred in proximity to the premises;
and sending, by the computing device to a server, an indication of the security condition, wherein the indication is configured to cause the server to send an alert message to one or more wireless devices within a threshold distance of the premises based on location information associated with the premises.
On claim 16, Poder cites:
The one or more non-transitory computer-readable media of claim 15, wherein the indication of the security condition comprises one or more of an image or video associated with the security condition, and wherein the alert message comprises the one or more of the image or video.
See the rejection of claim 2 which discloses the same subject matter as claim 16 and is rejected for the same reasons.
On claim 17, Poder cites:
The one or more non-transitory computer-readable media of claim 15, wherein the indication of the security condition is further configured to cause the server to send the alert message to:
the one or more wireless devices via a first protocol, and at least one other wireless device via a second protocol different from the first protocol.
See the rejection of claim 6 which discloses the same subject matter as claim 17 and is rejected for the same reasons.
On claim 18, Poder cites:
The one or more non-transitory computer-readable media of claim 15, wherein the one or more wireless devices are within one or more of: a services area associated with the premises, a police services boundary, an emergency medical services boundary, or a neighborhood group.
See the rejection of claim 4 which discloses the same subject matter as claim 18 and is rejected for the same reasons.
On claim 19, Poder cites:
The one or more non-transitory computer-readable media of claim 15, wherein the indication of the security condition comprises a heartbeat message.
See the rejection of claim 5 which discloses the same subject matter as claim 19 and is rejected for the same reasons.
On claim 20, Poder cites;
indication of the security condition comprises an indication of one or more of: output of a door sensor; output of a window sensor; output of a smoke detector; output of a glass-break sensor; an image or video associated with output of one or more sensors at the premises; triggering of an alarm at the premises; user input to the computing device at the premises; or a request for assistance.
See the rejection of claim 6 which discloses the same subject matter as claim 20 and is rejected for the same reasons.
On claim 21, Poder cites:
The one or more non-transitory computer-readable media of claim 15, wherein the computing device comprises a mobile device, and wherein the indication of the security condition comprises a location of the mobile device and the location information associated with the premises.
See the rejection of claim 7 which discloses the same subject matter as claim 21 and is rejected for the same reasons.
Remarks
The applicant’s arguments regarding the rejection of claims 1, 4-8, 11, 13-13, 18, 20, and 21 under 35 USC 102(a)(1) over Meganathan et al., U.S. 2016/0217668 was reviewed and persuasive. Accordingly, the claims have been examined again as indicted above.
The applicant’s arguments regarding the rejection of claims 1, 8, and 15, to include their respective dependent claims, under 35 USC 101, have been carefully reviewed but are not persuasive. Rejection of that above claims was carried out under “Certain Methods of Organizing Human Activity.” Reviewing claim 1, for example, would be likened to a person, apprised of a security condition, such as a theft or home invasion of the person’s home, calling for help, to include as yelling or shouting for assistance from a neighbor. These is an example of a human behavior analogous to the claimed invention without the use of computers, servers, wireless messaging via wireless devices, and the like, wherein these devices do not amount to something significantly more than the judicial exception. See MPEP 2106.07.
Conclusion
Any inquiry concerning this communication or earlier communications from the examiner should be directed to CAL EUSTAQUIO whose telephone number is (571)270-7229. The examiner can normally be reached on 8am-5pm. If attempts to reach the examiner by telephone are unsuccessful, the examiner's supervisor, Brian Zimmerman, can be reached at (571) 272-3059. The fax phone number for the organization where this application or proceeding is assigned is 571-273-8300. Information regarding the status of an application may be obtained from the Patent Application lnformation Retrieval (PAIR) system. Status information for published applications may be obtained from either Private PAIR or Public PAIR. Status information for unpublished applications is available through Private PAlR only. For more information about the PAlR system, see http:/lpair-direct.uspto.gov. Should you have questions on access to the Private PAlR system, contact the Electronic Business Center (EBC) at 866-217-9197 (toll-free). If you would like assistance from a USPTO Customer Service Representative or access to the automated information system, call 800-786-91 99 (IN USA OR CANADA) or 571-272-1000.
/CAL J EUSTAQUIO/Examiner, Art Unit 2686
/BRIAN A ZIMMERMAN/Supervisory Patent Examiner, Art Unit 2686
Prosecution Insights