Prosecution Insights
Last updated: April 19, 2026
Application No. 18/024,063

CONTROL MODULE FOR CONTROLLING A RADIO FREQUENCY SENSING

Final Rejection §101§103§112
Filed
Mar 01, 2023
Examiner
CADORNA, CHRISTOPHER PALACA
Art Unit
2444
Tech Center
2400 — Computer Networks
Assignee
Signify Holding B V
OA Round
2 (Final)
68%
Grant Probability
Favorable
3-4
OA Rounds
3y 3m
To Grant
89%
With Interview

Examiner Intelligence

Grants 68% — above average
68%
Career Allow Rate
150 granted / 222 resolved
+9.6% vs TC avg
Strong +21% interview lift
Without
With
+21.3%
Interview Lift
resolved cases with interview
Typical timeline
3y 3m
Avg Prosecution
38 currently pending
Career history
260
Total Applications
across all art units

Statute-Specific Performance

§101
9.0%
-31.0% vs TC avg
§103
51.7%
+11.7% vs TC avg
§102
16.1%
-23.9% vs TC avg
§112
21.3%
-18.7% vs TC avg
Black line = Tech Center average estimate • Based on career data from 222 resolved cases

Office Action

§101 §103 §112
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 . Response to Arguments 1. Applicant's arguments have been fully considered as follows: Regarding previous 112(b) rejections relating to the means-plus function 112(f) issues, Examiner notes that while the amendments have addressed these issues by specifying the elements that perform the tasks, neither a sensing area definer nor a sensitivity controller are recited by within the Specification and thus lack written description, and furthermore these can be interpreted as software elements and rendering the claims to be software per se. 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. 2. Claims 1-11 are rejected under 35 U.S.C. 101 because the claimed invention is directed to non-statutory subject matter. The claims do not fall within at least one of the four categories of patent eligible subject matter because the claims are directed towards software per se. Specifically, a control module may comprise a software element. (Specification, ¶0039, moreover the control module 130… can be part of the software… of the network devices) Furthermore, the sensing area definer and the sensitivity controller can be interpreted as software per se as being part of the control module, and also having no definition in the specification limiting the interpretation of the elements to being hardware. Claim Rejections - 35 USC § 112 The following is a quotation of the first paragraph of 35 U.S.C. 112(a): (a) IN GENERAL.—The specification shall contain a written description of the invention, and of the manner and process of making and using it, in such full, clear, concise, and exact terms as to enable any person skilled in the art to which it pertains, or with which it is most nearly connected, to make and use the same, and shall set forth the best mode contemplated by the inventor or joint inventor of carrying out the invention. 3. Claims 1-11 are rejected under 35 U.S.C. 112(a) as failing to comply with the written description requirement. The claims contains subject matter which was not described in the specification in such a way as to reasonably convey to one skilled in the relevant art that the inventor or a joint inventor had possession of the claimed invention. Claims 1 recites a sensing area definer and a sensitivity controller. However, the terms “definer” nor “controller” is not recited in the specification, and as such is not part of the original disclosure and lacks written description. Claims 2-11 are rejected for the same reasons as Claim 1. Claim Rejections - 35 USC § 103 In the event the determination of the status of the application as subject to AIA 35 U.S.C. 102 and 103 (or as subject to pre-AIA 35 U.S.C. 102 and 103) is incorrect, any correction of the statutory basis (i.e., changing from AIA to pre-AIA ) for the rejection will not be considered a new ground of rejection if the prior art relied upon, and the rationale supporting the rejection, would be the same under either status. The following is a quotation of 35 U.S.C. 103 which forms the basis for all obviousness rejections set forth in this Office action: A patent for a claimed invention may not be obtained, notwithstanding that the claimed invention is not identically disclosed as set forth in section 102, if the differences between the claimed invention and the prior art are such that the claimed invention as a whole would have been obvious before the effective filing date of the claimed invention to a person having ordinary skill in the art to which the claimed invention pertains. Patentability shall not be negated by the manner in which the invention was made. 4. Claims 1-11 and 13-14 are rejected under 35 U.S.C. 103 as being unpatentable over Monaci et al. (US 20160198548 A1) in view of Rast (US 20050141997 A1). Claim 1 Monaci teaches a control module for controlling a radio frequency sensing performed by at least two network devices being part of a network of network devices, the control module comprising: a sensing area definer (Monaci, FIG. 1, Central Management System (CMS) 102, ¶0018) configured to define at least two sensing areas for the network by assigning at least one network device of the at least two network devices of the network to each area, (Monaci, FIG. 1, ¶0024, wherein CMS 102 defines sensing areas by for the network by implementing a lighting strategy for sensing areas wherein the lighting strategy assigns network devise to each of the areas according to the lighting strategy) and a sensitivity controller (Monaci, FIG. 1, Controller 105) configured to receive a signal indicative of a status of at least one network device of the network, (Monaci, FIG. 1, ¶0027, receiving status information regarding connected device 114) the status of the at least one network device having a lighting status of the lighting device (Monaci, ¶0027, wherein the status information comprises a lighting status, for example yellow light status) and a sensing result in at least one of the at least two sensing areas; (Monaci, ¶0027, wherein the lighting status comprises a sensing result, i.e. the lighting is a result of sensors) wherein the sensitivity controller is configured to control at least one assigned network device in at least one of the at least two sensing areas based on the lighting status of a lighting device (Monaci, FIGs. 1 and 2, ¶0018, wherein the controller 105 controls at least one device 106-n in a sensing area 207-n, ¶0027 based upon a lighting status, for example, a lighting status is used to forecast control for neighboring devices) and based on a sensing result in at least one of the at least two sensing areas such that a sensing sensitivity is configured, (Monaci, ¶0027, wherein the lighting status comprises a sensing result, i.e. the lighting is a result of sensors) and the sensing sensitivity being based on a classification threshold between a positive sensing result and a negative sensing result; (Monaci, ¶0027, wherein the light status takes the form of positive or negative, i.e. green or red) wherein the sensitivity controller configured to control at least one assigned network device in at least one of the at least two sensing areas based on the lighting status of the lighting device (Monaci, FIGs. 1 and 2, ¶0018, wherein the controller 105 controls at least one device 106-n in a sensing area 207-n, ¶0027 based upon a lighting status, for example, a lighting status is used to forecast control for neighboring devices) and based on a sensing result in at least one of the at least two sensing areas such that the sensing sensitivity in at least one sensing area is configured based on the lighting status; (Monaci, ¶0027, wherein the lighting status comprises a sensing result, i.e. the lighting) wherein at least one of the network devices is the lighting device, (Monaci, FIG. 1, Connected Device 114, ¶0027, wherein Connected Device 114 comprises a light device, such as a traffic light, ¶0020, wherein Connected Device 114 comprises a network device of a smart city connected infrastructure) and the control module is arranged for controlling the at least two network devices via a control communication between the control module and the at least two network devices or performed by the control module (Examiner notes that this is an intended use statement, i.e. “for controlling…” and therefore the limitation does not have patentable weight) when the control module is part of a network device of the at least two network devices. (Examiner notes that this is a conditional limitation, and as the condition is not necessary for the claims, therefor the limitation does not have patentable weight) However, Monaci does not explicitly teach that the control module is configured to control the assigned network devices to perform radio frequency sensing in a respective one of the at least two sensing areas. From a related technology, Rast teaches assigned network devices that contribute to the radio frequency sensing (Rast, ¶0037, sensing in the form of RF sensing) in the respective one of at least two sensing areas. (Rast, ¶0369-¶0371, detecting, i.e. sensing, an area of an intersection of two possible sensing areas, i.e. intersection and non-intersection) It would be obvious to one of ordinary skill in the art before the effective filing date of the claimed invention to modify the teachings of Monaci to incorporate particularly RF sensing technology implemented in Rast in order to more efficiently utilize network technology. Claim 1 Monaci teaches a control module for controlling a radio frequency sensing performed by at least two network devices being part of a network of network devices (Examiner notes that “for controlling” comprises an intended use statement, as well as is a limitation recited only in the preamble, and does not have patentable weight) wherein the at least one of the network devices of the network is a light device, (FIG. 1, Connected Device 114, ¶0027, wherein Connected Device 114 comprises a light device, such as a traffic light, ¶0020, wherein Connected Device 114 comprises a network device of a smart city connected infrastructure) wherein the control module (FIG. 1, Lighting Network 100, ¶0018) is arranged for controlling the at least two network devices via a control communication between the control module and the at least two network device or performed directly; (FIG. 1, ¶0018, Lighting Network arranged to control network devices via control communications) wherein the control module (FIG. 1, Lighting Network 100, ¶0018) comprises: a sensing area defining unit (FIG. 1, Central Management System (CMS) 102, ¶0018) is adapted for defining at least two sensing areas for the network by assigning at least one network device of the at least two network devices of the network to each area, (FIG. 1, ¶0024, wherein CMS 102 defines sensing areas by for the network by implementing a lighting strategy for sensing areas wherein the lighting strategy assigns network devise to each of the areas according to the lighting strategy) and a sensitivity controlling unit (FIG. 1, Controller 105) is adapted for receiving a signal indicative of a status of at least one network device of the network, (FIG. 1, ¶0027, receiving status information regarding connected device 114) wherein the status of the at least one network device comprises a lighting status of the lighting device, (¶0027, wherein the status information comprises a lighting status, for example yellow light status) and/or a sensing result in at least one of the at least two sensing areas; (See 112(b), Examiner notes that “and/or…” is interpreted as simply “or” for purposes of interpretation, and as a Markush Group, only one embodiment needs to be taught) wherein the sensitivity controlling unit is further adapted for controlling at least one assigned network device in at least one of the at least two sensing areas based on the lighting status of the lighting device (¶0027, wherein Controller 105 controls the detection level of at least one relevant light unit, i.e. assigned network device, in at least one of the two sensing areas, i.e. in a neighboring area, based on the status information) and/or based on a sensing result in at least one of the at least two sensing areas such that a sensing sensitivity is configured; wherein the sensing sensitivity refers to a classification threshold between a positive sensing result and a negative sensing result; (See 112(b), Examiner notes that “and/or…” is interpreted as simply “or” for purposes of interpretation, and as a Markush Group, only one embodiment needs to be taught) and/or wherein the sensitivity controlling unit is further adapted for controlling at least one assigned network device in at least one of the at least two sensing areas based on lighting status of the lighting device, (See 112(b), Examiner notes that “and/or…” is interpreted as simply “or” for purposes of interpretation, and as a Markush Group, only one embodiment needs to be taught) and/or based on a sensing result in at least one of the at least two sensing areas such that sensing mode in at least one sensing area is configured. (See 112(b), Examiner notes that “and/or…” is interpreted as simply “or” for purposes of interpretation, and as a Markush Group, only one embodiment needs to be taught) However, Monaci does not explicitly teach wherein the assigned network devices contribute to the radio frequency sensing in the respective one of the at least two sensing areas. From a related technology, Rast teaches assigned network devices that contribute to the radio frequency sensing (¶0037, sensing in the form of RF sensing) in the respective one of at least two sensing areas. (¶0369-¶0371, detecting, i.e. sensing, an area of an intersection of two possible sensing areas, i.e. intersection and non-intersection) It would be obvious to one of ordinary skill in the art before the effective filing date of the claimed invention to modify the teachings of Monaci to incorporate particularly RF sensing technology implemented in Rast in order to more efficiently utilize network technology. Claim 2 Monaci in view of Rast teaches Claim 1, and further teaches wherein the sensitivity controlling unit is adapted to control at least one assigned network device in each of the at least two sensing areas such that a sensing sensitivity and/or (See 112(b), Examiner notes that “and/or…” is interpreted as simply “or” for purposes of interpretation, and as a Markush Group, only one embodiment needs to be taught) sensing mode in each of the at least two sensing areas is configured. (Monaci, ¶0024, controlling the sensing mode in the sensing area) Claim 3 Monaci in view of Rast teaches Claim 2, and further teaches wherein the sensitivity controlling unit is adapted to control at least one assigned network device in each of the at least two sensing areas such that the sensing sensitivity in at least one area is increased and in at least one other area is decreased with respect to a current sensing sensitivity. (Monaci, ¶0024, controlling the sensing mode in the sensing area to increase or decrease the sensing sensitivity) Claim 4 Monaci in view of Rast teaches Claim 1, and further teaches wherein the lighting status of the at least one lighting device refers to at least one of an on/off state, a dim level, a light spectrum, a UV spectrum, a directionality of UV light, a UV radiance power, a battery status, a light intensity, an illumination of the environment. (Monaci, ¶0027, the lighting status referring to an illumination, e.g. green light, of the environment) Claim 5 Monaci in view of Rast teaches Claim 1, and further teaches wherein the sensing result comprises information on the presence or absence of at least one person or object in at least one of the at least two sensing areas. (Examiner notes that “the sensing result” refers to an element within a Markush group which is not being interpreted as being embodied, and therefore the limitation has no patentable weight) Claim 6 Monaci in view of Rast teaches Claim 1, and further teaches wherein the sensing result comprises information on a number of persons or classification of persons detected in at least one of the at least two sensing areas. (Examiner notes that “the sensing result” refers to an element within a Markush group which is not being interpreted as being embodied, and therefore the limitation has no patentable weight) Claim 7 Monaci in view of Rast teaches Claim 5, and further teaches wherein the sensitivity controlling unit is adapted to control at least one assigned network device in each of the at least two sensing areas such that the sensing sensitivity is increased in a sensing area for which the sensing result indicates the presence of a person or a specific activity of a person in the sensing area (Monaci, ¶0039, detecting the presence of a pedestrian) and such that the sensing sensitivity is decreased in at least one other sensing area with respect to a current sensing sensitivity. (Monaci, ¶0039, lowering detection threshold) Claim 8 Monaci in view of Rast teaches Claim 1, and further teaches wherein the sensitivity controlling unit comprises an activity expectation estimating unit for estimating an activity expectation for each of the at least two sensing areas, (Monaci, ¶0027, wherein controller 105 forecasts the level of traffic for neighboring light unit areas, i.e. activity expectation estimating) wherein the sensitivity controlling unit is adapted to control the at least one assigned network device based on the activity expectation. (Monaci, ¶0027, increases or decreases threshold detection based on forecast) Claim 9 Monaci in view of Rast teaches Claim 8, and further teaches wherein the sensitivity controlling unit is adapted to determine whether the activity expectation is estimated to lie above a threshold in at least one sensing area (Monaci, ¶0027, wherein controller 105 forecasts the level of traffic for neighboring light unit areas, i.e. activity expectation estimating) and wherein the sensitivity controlling unit is adapted to control at least one assigned network device in each sensing area such that the sensing sensitivity is decreased in each sensing areas for which the activity expectation lies above the threshold (Monaci, ¶0027, increases or decreases threshold detection based on forecast) and/or such that the sensing sensitivity is increased in at least one other sensing area with respect to a current sensing sensitivity. (See 112(b), Examiner notes that “and/or…” is interpreted as simply “or” for purposes of interpretation, and as a Markush Group, only one embodiment needs to be taught) Claim 10 Monaci in view of Rast teaches Claim 1, and further teaches wherein the sensitivity controlling unit is adapted to control the at least one assigned network device by controlling at least one radio frequency operating variable of the network device such that the sensing sensitivity and/or sensing mode is configured. (Monaci, ¶0027, increases or decreases threshold detection, where threshold detection comprises radio frequency operating variable) Claim 11 Monaci in view of Rast teaches Claim 10, and further teaches wherein the radio frequency operating variable refers to at least one of a threshold defining the detection of motion, (Monaci, ¶0027, increases or decreases threshold detection, where threshold detection comprises radio frequency operating variable; ¶0039, wherein the detection comprises a detection of a pedestrian, i.e. movement by a person) a number or frequency of sent or received radio frequency signals utilized for the radio frequency sensing, an amplitude of a radio frequency signal utilized for the radio frequency sensing, a sending direction of a radio frequency signal utilized for the radio frequency sensing, a focus of the radio frequency signal utilized for the radio frequency sensing, a radio frequency sensing frequency, a receiving antenna pattern and a utilized processing algorithm. Claim 13 is taught by Monaci in view of Rast as described for Claim 1. Claim 14 is taught by Monaci in view of Rast as described for Claim 1. Conclusion Applicant's amendment necessitated the new ground(s) of rejection presented in this Office action. Accordingly, THIS ACTION IS MADE FINAL. See MPEP § 706.07(a). Applicant is reminded of the extension of time policy as set forth in 37 CFR 1.136(a). A shortened statutory period for reply to this final action is set to expire THREE MONTHS from the mailing date of this action. In the event a first reply is filed within TWO MONTHS of the mailing date of this final action and the advisory action is not mailed until after the end of the THREE-MONTH shortened statutory period, then the shortened statutory period will expire on the date the advisory action is mailed, and any nonprovisional extension fee (37 CFR 1.17(a)) pursuant to 37 CFR 1.136(a) will be calculated from the mailing date of the advisory action. In no event, however, will the statutory period for reply expire later than SIX MONTHS from the mailing date of this final action. Any inquiry concerning this communication or earlier communications from the examiner should be directed to CHRISTOPHER PALACA CADORNA whose telephone number is (571)270-0584. The examiner can normally be reached M-F 10:00-7:00. Examiner interviews are available via telephone, in-person, and video conferencing using a USPTO supplied web-based collaboration tool. To schedule an interview, applicant is encouraged to use the USPTO Automated Interview Request (AIR) at http://www.uspto.gov/interviewpractice. If attempts to reach the examiner by telephone are unsuccessful, the examiner’s supervisor, Glenton Burgess can be reached at (571) 272-3949. The fax phone number for the organization where this application or proceeding is assigned is 571-273-8300. Information regarding the status of published or unpublished applications may be obtained from Patent Center. Unpublished application information in Patent Center is available to registered users. To file and manage patent submissions in Patent Center, visit: https://patentcenter.uspto.gov. Visit https://www.uspto.gov/patents/apply/patent-center for more information about Patent Center and https://www.uspto.gov/patents/docx for information about filing in DOCX format. For additional questions, contact the Electronic Business Center (EBC) at 866-217-9197 (toll-free). If you would like assistance from a USPTO Customer Service Representative, call 800-786-9199 (IN USA OR CANADA) or 571-272-1000. /CHRISTOPHER P CADORNA/Examiner, Art Unit 2444 /WILLIAM G TROST IV/Supervisory Patent Examiner, Art Unit 2442
Read full office action

Prosecution Timeline

Mar 01, 2023
Application Filed
Dec 18, 2024
Non-Final Rejection — §101, §103, §112
Jun 23, 2025
Response Filed
Oct 04, 2025
Final Rejection — §101, §103, §112 (current)

Precedent Cases

Applications granted by this same examiner with similar technology

Patent 12563123
METHOD, APPARATUS, AND COMPUTER PROGRAM PRODUCT FOR ENLARGING USAGE OF USER CATEGORY WITHIN A CORE NETWORK
2y 5m to grant Granted Feb 24, 2026
Patent 12541244
OBTAINING LOCATION METADATA FOR NETWORK DEVICES USING AUGMENTED REALITY
2y 5m to grant Granted Feb 03, 2026
Patent 12537878
NEEDS-MATCHING NAVIGATOR SYSTEM
2y 5m to grant Granted Jan 27, 2026
Patent 12531762
Smart Energy Hub
2y 5m to grant Granted Jan 20, 2026
Patent 12513109
IPV6 ADDRESS CONFIGURATION METHOD AND ROUTING DEVICE
2y 5m to grant Granted Dec 30, 2025
Study what changed to get past this examiner. Based on 5 most recent grants.

AI Strategy Recommendation

Get an AI-powered prosecution strategy using examiner precedents, rejection analysis, and claim mapping.
Powered by AI — typically takes 5-10 seconds

Prosecution Projections

3-4
Expected OA Rounds
68%
Grant Probability
89%
With Interview (+21.3%)
3y 3m
Median Time to Grant
Moderate
PTA Risk
Based on 222 resolved cases by this examiner. Grant probability derived from career allow rate.

Sign in with your work email

Enter your email to receive a magic link. No password needed.

Personal email addresses (Gmail, Yahoo, etc.) are not accepted.

Free tier: 3 strategy analyses per month