Prosecution Insights
Last updated: November 20, 2026
Application No. 19/096,023

METHOD FOR TEMPORAL SYNCHRONIZATION OF DATA DETECTION WITH A TEST VEHICLE AND A DRONE

Non-Final OA §101§102
Filed
Mar 31, 2025
Priority
Apr 11, 2024 — DE 10 2024 203 336.7
Examiner
ANSARI, TAHMINA N
Art Unit
2674
Tech Center
2600 — Communications
Assignee
Robert Bosch GmbH
OA Round
1 (Non-Final)
85%
Grant Probability
Favorable
1-2
OA Rounds
10m
Est. Remaining
99%
With Interview

Examiner Intelligence

Grants 85% — above average
85%
Career Allowance Rate
777 granted / 910 resolved
+23.4% vs TC avg
Strong +19% interview lift
Without
With
+18.6%
Interview Lift
resolved cases with interview
Typical timeline
2y 6m
Avg Prosecution
26 currently pending
Career history
947
Total Applications
across all art units

Statute-Specific Performance

§101
13.0%
-27.0% vs TC avg
§103
42.1%
+2.1% vs TC avg
§102
22.1%
-17.9% vs TC avg
§112
10.4%
-29.6% vs TC avg
Black line = Tech Center average estimate • Based on career data from 910 resolved cases

Office Action

§101 §102
DETAILED ACTION Notice of Pre-AIA or AIA Status Claims 1-12 are pending in this application. The present application, filed on or after March 16, 2013, is being examined under the first inventor to file provisions of the AIA . 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 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. Specification The title of the invention is not descriptive. A new title is required that is clearly indicative of the invention to which the claims are directed. 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-12 are rejected under 35 U.S.C. 101 because the claimed invention is directed to non-statutory subject matter. The claim(s) does/do not fall within at least one of the four categories of patent eligible subject matter because the claimed invention is directed to a judicial exception (i.e., abstract idea – an idea to itself/mathematical concept) without significantly more. (1) Are the claims directed to a process, machine, manufacture or composition of matter; (2A) Prong One: Are the claims directed to a judicially recognized exception, i.e., a law of nature, a natural phenomenon, or an abstract idea; Prong Two: If the claims are directed to a judicial exception under Prong One, then is the judicial exception integrated into a practical application; (2B) If the claims are directed to a judicial exception and do not integrate the judicial exception, do the claims provide an inventive concept. (Step 1) In the context of the flowchart in MPEP § 2106, subsection III, Step (1): Are the claims directed to a process, machine, manufacture or composition of matter? YES: the instant claims recite a method, a system and a non-transitory computer readable medium. (Step 2A) In the context of the flowchart in MPEP § 2106, subsection III, Step 2A Prong Two determines whether: Is the claim directed to a law of nature, a natural phenomenon, or an abstract idea? YES. When viewed under the broadest most reasonable interpretation, the instant claims are directed to a Judicial Exception – an abstract idea belonging to the group of mathematical concept.As a whole, the claimed features can be interpreted as an overall mathematical process, as they are a natural language representation of an overall mathematical algorithm, which qualifies as a judicial exception. Claim 1 is exemplary of the independent claims 1, 11 and 12, and is presented below. Specifically, the claim recites: -; 1. A method for temporal synchronization of data detection using a test vehicle and data detection using a drone which accompanies the test vehicle, comprising the following steps: -; a) recognizing signals and/or features of operation of the test vehicle in video data recorded using a camera of the accompanying drone; -; and b) performing the temporal synchronization using the signals and/or features recognized in step a). When viewed under the broadest most reasonable interpretation, the instant claims are directed to a Judicial Exception – an abstract idea belonging to the group of mathematical concept or mental action.As a whole, the claimed features can be interpreted as an overall mathematical process, as they are a natural language representation of an overall mathematical algorithm, which qualifies as a judicial exception. It can also be considered to constitute a mental activity, because there is no quantification or qualification for the manner of recognition or temporal synchronization. There is nothing in the claim that requires more than a human mentally looking at the dataset or an operation that a human, armed with the appropriate apparatus executing a mathematical algorithm (in this case “values”) can perform. Since the claim as a whole does not integrate the exception into a practical application, in which case the claim is directed to the judicial exception (Step 2A: YES), it requires further analysis under Step 2B (where it may still be eligible if it amounts to an inventive concept). (Step 2B) In the context of the flowchart in MPEP 2106, subsection III, Step 2B determines whether: Does the claim recited additional elements that amount to significantly more than the judicial exception?NO. The instant claims do not apply, rely on, or use the judicial exception in a manner that imposes a meaningful limit on the judicial exception of “provide/receive first/second fractional flow reserve value” and therefore does not integrate the judicial exception into a practical application.In accordance with the MPEP § 2106.04(d) Integration of a Judicial Exception Into A Practical Application [R-07.2022], Similarly, in a growing body of decisions, the Federal Circuit has distinguished between claims that are ‘‘directed to’’ a judicial exception (which require further analysis to determine their eligibility) and those that are not (which are therefore patent eligible), e.g., claims that improve the functioning of a computer or other technology or technological field. See Diamond v. Diehr, 450 U.S. 175, 209 USPQ 1 (1981); Gottschalk v. Benson, 409 U.S. 63, 175 USPQ 673 (1972). See, e.g., MPEP § 2106.06(b) (summarizing Enfish, LLC v. Microsoft Corp., 822 F.3d 1327, 118 USPQ2d 1684 (Fed. Cir. 2016), McRO, Inc. v. Bandai Namco Games Am. Inc., 837 F.3d 1299, 120 USPQ2d 1091 (Fed. Cir. 2016), and other cases that were eligible as improvements to technology or computer functionality instead of being directed to abstract ideas)” “Accordingly, after determining that a claim recites a judicial exception in Step 2A Prong One, examiners should evaluate whether the claim as a whole integrates the recited judicial exception into a practical application of the exception in Step 2A Prong Two. A claim that integrates a judicial exception into a practical application will apply, rely on, or use the judicial exception in a manner that imposes a meaningful limit on the judicial exception, such that the claim is more than a drafting effort designed to monopolize the judicial exception.” See MPEP § 2106.05 for discussion of Step 2B. With respect to the claimed limitations, the following features are directed to a mathematical process that do not integrate the judicial exception into a practical application, as there is no “meaningful limit”. In particular, the claim includes additional elements as follows and includes using a processing apparatus to perform the following: (i) 1. A method for temporal synchronization of data detection using a test vehicle and data detection using a drone which accompanies the test vehicle, comprising the following steps: (ii) a) recognizing signals and/or features of operation of the test vehicle in video data recorded using a camera of the accompanying drone; (iii) and b) performing the temporal synchronization using the signals and/or features recognized in step a). Step (i) is the preamble and constitutes intended use and possibly data gathering, which is an extra-solution activity. Step (ii) recognizes “signals”/”features” at a high level of generality such that said “signals”/”features” can be used in the operation of the recited judicial exception (the mental step of “recognizing”). Supplying “signals”/”features” does not provide for “integration” of the abstract idea into a practical application, as said “signals”/”features” do not change the way in which said apparatus operates. In fact, there are no limits on the apparatus, which is recited at a high level of generality and thus said apparatus does nothing more than perform generic computing functions of “recognizing” in the claim. Step (ii) can be done mentally as well, as there is qualification or quantification or manner claimed in the way the process of “recognizing” happens. Step (iii) can be done mentally; there are no specifics about what they are doing in ‘performing temporal synchronization’ thus one can merely ‘look’ at the data and make a ‘determination’. This is considered a mental activity or at best a mathematical calculation step. One can mentally verify if the data is occurring at the same time or use a mathematical formula for the determination. The steps claimed as a whole do not make the claim as a whole patent eligible because the claim does not integrate as a whole the judicial exception into a practical application. With regard to (2B), the pending claims do not show what is more than a routine in the art presented in the claims, i.e., the additional elements are nothing more than routine and well-known steps. There is no improvement to technology here. There is only a data gathering steps, followed by “recognizing”, “performing”, both of which constitute a mental process or mathematical operation. There is no metrics on quantifying, qualifying or describing the nature in which these feature are achieved and it has not been shown that the mental process allows the “technology” (whether it is computer technology or any other technology) to do something that it previously was not able to do. DIAMOND VS. DIEHR The claimed features, at best would invoke the analysis of the features under MPEP § 2106.05(a) as to whether the features qualify as improvements to the functioning of a computer or to any other technology or technical field. Even when considering the relevant consideration for evaluating whether the additional elements amount to an inventive concept, the limitations do not recite any elements that can be considered to qualify as “significantly more” when recited in a claim with judicial exception. At best, the claimed limitations only recite features that “apply” the judicial exception, and add “insignificant extra-solution activity to the judicial exception”, Dependent claims 2-10 are rejected for the same reasons; claims are directed to a judicial exception and do not integrate the judicial exception. Claim Rejections - 35 USC § 102 The following is a quotation of the appropriate paragraphs of 35 U.S.C. 102 that form the basis for the rejections under this section made in this Office action: A person shall be entitled to a patent unless – (a)(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. (a)(2) the claimed invention was described in a patent issued under section 151, or in an application for patent published or deemed published under section 122(b), in which the patent or application, as the case may be, names another inventor and was effectively filed before the effective filing date of the claimed invention. Claims 1-12 are rejected under 35 U.S.C. 102(a)(1) as being anticipated by Warner et al. (US PGPub 20220144429, hereby referred to as “Warner”). Consider Claims 1, 11 and 12. Warner teaches: 1. A method for / 11. A data processing device, comprising: / 12. A non-transitory computer-readable storage medium on which are stored commands for (Warner: abstract, Devices and methods for activating a flight-enable beacon configured to provide a light beacon or data signal comprising capability to establish and maintain a fixed set of coordinates. The flight-enabled beacon is configured with a processor, memory, motor, gimbal or swashplate and light emitting source and can be configured to attain and maintain a target altitude and emit a light over a fixed period of time. The flight-enabled beacon is configured to be light and with small form factor for easy portable transport in cases of emergency or to provide a signal easily locatable by parties located a distance from the activated light-enabled beacon.) 1. temporal synchronization of data detection using a test vehicle and data detection using a drone which accompanies the test vehicle, comprising the following steps: / 11. a processor adapted to temporally synchronize data detection using a test vehicle and data detection using a drone which accompanies the test vehicle, the processor adapted to: / 12. temporal synchronization of data detection using a test vehicle and data detection using a drone which accompanies the test vehicle, the commands, when executed by a computer, causing the computer to perform the following steps: (Warner: [0050] FIG. 1 is an exemplary diagram illustrating connected components for one embodiment of a flight-enabled beacon. As shown in FIG. 1, in conjunction with FIGS. 12-14, the flight-enabled beacon (100) comprises a processor (125, FIG. 14), memory (135, FIG. 14) coupled with the processor (125); one or more motors (110, FIG. 1, 112, FIGS. 12-14) in electronic communication with the processor (125) and configured to operate a rotational speed of one or more sets of rotatable blades, or propellers, (210, 220, FIGS. 12-14); one or more gimbals (240, 250, FIGS. 12-14) in electronic communication with the one or more motors (110, 112) and configured to operate one or more of an orientation or a direction of movement of the flight-enabled beacon (100) using the one or more rotatable blades (210, 220). Alternatively, the one or more gimbals (240, 250) is replaceable with a swashplate assembly. Further, a light emitting source (194, FIGS. 1, 12-14) in electronic communication with the processor (125) is configured to emit, at a target altitude, a light over a temporal period. It will be appreciated that the light emitting source (194) may comprise a number of programs for emitting light, such as, for example, emitting light immediately upon activation of the flight-enabled beacon (100), emitting light after a period of time while ascending to the target altitude, emitting light once the flight-enabled beacon (100) reaches the target altitude; emitting various colored lights, where the various colors may represent a specific situation, and/or emitting light in a patterned on/off cycle, such as SOS signal, among others.) 1. a) recognizing signals and/or features of operation of the test vehicle in video data recorded using a camera of the accompanying drone; and / 11. a) recognize signals and/or features of operation of the test vehicle in video data recorded using a camera of the accompanying drone; / 12. a) recognizing signals and/or features of operation of the test vehicle in video data recorded using a camera of the accompanying drone; (Warner: [0060] The flight controller (130, FIG. 1), which may be, for example, a microcontroller, is positioned within the housing, or body, of the flight-enabled beacon (100) and is coupled to a number of components, such as one or more of: the one or more motors (110, 112), the one or more rotor rotation control (120) of the motors (110, 112), the processor (125), the sensor (140) or set of sensors, the one or more gimbals (240, 250), an optional swashplate, the individual rotatable blades (210 a-b, 220 a-b) and/or the set of rotatable blades (210, 220), a power source (190), an optional safety unit, an optional audio unit, an inertial sensor and measurement unit (140), an optional GPS module (170), an optional transceiver (160), an optional camera (180), the light source (194), an optional flotation unit, or housing. FIGS. 12-14 show an example of the flight controller (130) positioned on the body of the flight-enabled beacon (100). [0061] The flight controller (130) can be configured to collect and/or receive data and other information from the one or more components of the flight-enabled beacon (100), such as the sensor (140) or set of sensors, gimbals (240, 250), each rotatable blade (210 a-b, 220 a-b) and/or the sets of rotatable blades (210, 220), power source (190), safety unit, audio unit, inertial measurement unit (140), GPS module (170), transceiver (160), camera (180), light emitting source (194), flotation unit, housing, etc., and perform an actionable outcome. Examples of data and other information include, for example, sensor data, altitude coordinates, orientation data, inertial data for navigation, automatic identification system (AIS) radio data (e.g., receive a land command), etc. More specifically, the flight-enabled beacon (100) may be configured with an antenna receiver, such as shown as 1802 in FIG. 18, or transceiver (160, FIG. 1) for receiving a radio frequency signal from an incoming rescue operation or vehicle, for example helicopter (1302), indicating the land command. Further, the flight controller (130) can be configured to receive and interpret data and information from a transceiver, or receiver, a GPS module, camera, a battery monitor, the inertial measurement unit (140), other onboard sensors, or user input (e.g., a “to follow me” command, a “maintain proximity to the user” command, and/or a “maintain the user in a line of sight” command in embodiments when the flight-enabled beacon (100) comprises a camera). In a further example, the flight controller (130) may communicate with the GPS module (170) and may be utilized by hikers, hunters, boaters, or other users desiring to use the flight-enabled beacon (100) as a positional tracking or locating system. The flight-enabled beacon (100) may optionally include a display and/or the flight-enabled beacon (100) may be in communication with a remote display showing its position and/or GPS coordinates in real-time. In some instances, the flight controller (130) can perform various operations with the components to perform an operation or method (e.g., controlling the gimbals (240, 250), or swashplate, controlling the rotor speed via the rotor rotation control (120) and motors (110, 112) of the individual or sets of rotatable blades (210, 220), activating the camera (180), activating the light emitting source (194), receiving or transmitting sounds or words via the audio unit, activating the safety unit, etc.); execute a preprogrammed or initiated command; and/or ascend and maintain the target altitude for a fixed time period. In a further embodiment, the flight controller (130) can maintain, or hover, the flight-enabled beacon (100) at the target altitude by using an internal command program loop, which calculates differences between its actual orientation and/or altitude and the target orientation and/or altitude and adjusts a parameter equivalent to the calculated difference. The flight controller (130) may use the feedback parameter, or command program loop output, to adjust the pitch, yaw, roll, and/or speed of individual and/or sets of rotatable blades (210, 220). In another embodiment, the flight controller (130) may receive input data, such as coordinates or commands, from a handheld controller or other user device to hold the orientation and/or target altitude.) 1. and b) performing the temporal synchronization using the signals and/or features recognized in step a). / 11. and b) perform the temporal synchronization using the signals and/or features recognized in step a). / 12. and b) performing the temporal synchronization using the signals and/or features recognized in step a). (Warner: [0050] Further, a light emitting source (194, FIGS. 1, 12-14) in electronic communication with the processor (125) is configured to emit, at a target altitude, a light over a temporal period. It will be appreciated that the light emitting source (194) may comprise a number of programs for emitting light, such as, for example, emitting light immediately upon activation of the flight-enabled beacon (100), emitting light after a period of time while ascending to the target altitude, emitting light once the flight-enabled beacon (100) reaches the target altitude; emitting various colored lights, where the various colors may represent a specific situation, and/or emitting light in a patterned on/off cycle, such as SOS signal, among others. The flight controller (130) can be configured to collect and/or receive data and other information from the one or more components of the flight-enabled beacon (100), such as the sensor (140) or set of sensors, gimbals (240, 250), each rotatable blade (210 a-b, 220 a-b) and/or the sets of rotatable blades (210, 220), power source (190), safety unit, audio unit, inertial measurement unit (140), GPS module (170), transceiver (160), camera (180), light emitting source (194), flotation unit, housing, etc., and perform an actionable outcome. Examples of data and other information include, for example, sensor data, altitude coordinates, orientation data, inertial data for navigation, automatic identification system (AIS) radio data (e.g., receive a land command), etc. More specifically, the flight-enabled beacon (100) may be configured with an antenna receiver, such as shown as 1802 in FIG. 18, or transceiver (160, FIG. 1) for receiving a radio frequency signal from an incoming rescue operation or vehicle, for example helicopter (1302), indicating the land command. Further, the flight controller (130) can be configured to receive and interpret data and information from a transceiver, or receiver, a GPS module, camera, a battery monitor, the inertial measurement unit (140), other onboard sensors, or user input (e.g., a “to follow me” command, a “maintain proximity to the user” command, and/or a “maintain the user in a line of sight” command in embodiments when the flight-enabled beacon (100) comprises a camera). In a further example, the flight controller (130) may communicate with the GPS module (170) and may be utilized by hikers, hunters, boaters, or other users desiring to use the flight-enabled beacon (100) as a positional tracking or locating system. The flight-enabled beacon (100) may optionally include a display and/or the flight-enabled beacon (100) may be in communication with a remote display showing its position and/or GPS coordinates in real-time. In some instances, the flight controller (130) can perform various operations with the components to perform an operation or method (e.g., controlling the gimbals (240, 250), or swashplate, controlling the rotor speed via the rotor rotation control (120) and motors (110, 112) of the individual or sets of rotatable blades (210, 220), activating the camera (180), activating the light emitting source (194), receiving or transmitting sounds or words via the audio unit, activating the safety unit, etc.); execute a preprogrammed or initiated command; and/or ascend and maintain the target altitude for a fixed time period. In a further embodiment, the flight controller (130) can maintain, or hover, the flight-enabled beacon (100) at the target altitude by using an internal command program loop, which calculates differences between its actual orientation and/or altitude and the target orientation and/or altitude and adjusts a parameter equivalent to the calculated difference. The flight controller (130) may use the feedback parameter, or command program loop output, to adjust the pitch, yaw, roll, and/or speed of individual and/or sets of rotatable blades (210, 220). In another embodiment, the flight controller (130) may receive input data, such as coordinates or commands, from a handheld controller or other user device to hold the orientation and/or target altitude.) 2. The method according to claim 1, wherein the following step is performed before step b): a') ascertaining operating parameters of the operation of the test vehicle that allow a comparison with the features of the operation of the test vehicle recognized in step a); wherein, in b), the operating parameters ascertained in step a') are additionally used to perform the temporal synchronization. (Warner: [0050] Further, a light emitting source (194, FIGS. 1, 12-14) in electronic communication with the processor (125) is configured to emit, at a target altitude, a light over a temporal period. It will be appreciated that the light emitting source (194) may comprise a number of programs for emitting light, such as, for example, emitting light immediately upon activation of the flight-enabled beacon (100), emitting light after a period of time while ascending to the target altitude, emitting light once the flight-enabled beacon (100) reaches the target altitude; emitting various colored lights, where the various colors may represent a specific situation, and/or emitting light in a patterned on/off cycle, such as SOS signal, among others. The flight controller (130) can be configured to collect and/or receive data and other information from the one or more components of the flight-enabled beacon (100), such as the sensor (140) or set of sensors, gimbals (240, 250), each rotatable blade (210 a-b, 220 a-b) and/or the sets of rotatable blades (210, 220), power source (190), safety unit, audio unit, inertial measurement unit (140), GPS module (170), transceiver (160), camera (180), light emitting source (194), flotation unit, housing, etc., and perform an actionable outcome. Examples of data and other information include, for example, sensor data, altitude coordinates, orientation data, inertial data for navigation, automatic identification system (AIS) radio data (e.g., receive a land command), etc. More specifically, the flight-enabled beacon (100) may be configured with an antenna receiver, such as shown as 1802 in FIG. 18, or transceiver (160, FIG. 1) for receiving a radio frequency signal from an incoming rescue operation or vehicle, for example helicopter (1302), indicating the land command. Further, the flight controller (130) can be configured to receive and interpret data and information from a transceiver, or receiver, a GPS module, camera, a battery monitor, the inertial measurement unit (140), other onboard sensors, or user input (e.g., a “to follow me” command, a “maintain proximity to the user” command, and/or a “maintain the user in a line of sight” command in embodiments when the flight-enabled beacon (100) comprises a camera). In a further example, the flight controller (130) may communicate with the GPS module (170) and may be utilized by hikers, hunters, boaters, or other users desiring to use the flight-enabled beacon (100) as a positional tracking or locating system. The flight-enabled beacon (100) may optionally include a display and/or the flight-enabled beacon (100) may be in communication with a remote display showing its position and/or GPS coordinates in real-time. In some instances, the flight controller (130) can perform various operations with the components to perform an operation or method (e.g., controlling the gimbals (240, 250), or swashplate, controlling the rotor speed via the rotor rotation control (120) and motors (110, 112) of the individual or sets of rotatable blades (210, 220), activating the camera (180), activating the light emitting source (194), receiving or transmitting sounds or words via the audio unit, activating the safety unit, etc.); execute a preprogrammed or initiated command; and/or ascend and maintain the target altitude for a fixed time period. In a further embodiment, the flight controller (130) can maintain, or hover, the flight-enabled beacon (100) at the target altitude by using an internal command program loop, which calculates differences between its actual orientation and/or altitude and the target orientation and/or altitude and adjusts a parameter equivalent to the calculated difference. The flight controller (130) may use the feedback parameter, or command program loop output, to adjust the pitch, yaw, roll, and/or speed of individual and/or sets of rotatable blades (210, 220). In another embodiment, the flight controller (130) may receive input data, such as coordinates or commands, from a handheld controller or other user device to hold the orientation and/or target altitude.) 3. The method according to claim 2, wherein, in step a), the operating parameters of the operation of the drone are recorded, which are used to perform the temporal synchronization in step b). (Warner: [0050] Further, a light emitting source (194, FIGS. 1, 12-14) in electronic communication with the processor (125) is configured to emit, at a target altitude, a light over a temporal period. It will be appreciated that the light emitting source (194) may comprise a number of programs for emitting light, such as, for example, emitting light immediately upon activation of the flight-enabled beacon (100), emitting light after a period of time while ascending to the target altitude, emitting light once the flight-enabled beacon (100) reaches the target altitude; emitting various colored lights, where the various colors may represent a specific situation, and/or emitting light in a patterned on/off cycle, such as SOS signal, among others. The flight controller (130) can be configured to collect and/or receive data and other information from the one or more components of the flight-enabled beacon (100), such as the sensor (140) or set of sensors, gimbals (240, 250), each rotatable blade (210 a-b, 220 a-b) and/or the sets of rotatable blades (210, 220), power source (190), safety unit, audio unit, inertial measurement unit (140), GPS module (170), transceiver (160), camera (180), light emitting source (194), flotation unit, housing, etc., and perform an actionable outcome. Examples of data and other information include, for example, sensor data, altitude coordinates, orientation data, inertial data for navigation, automatic identification system (AIS) radio data (e.g., receive a land command), etc. More specifically, the flight-enabled beacon (100) may be configured with an antenna receiver, such as shown as 1802 in FIG. 18, or transceiver (160, FIG. 1) for receiving a radio frequency signal from an incoming rescue operation or vehicle, for example helicopter (1302), indicating the land command. Further, the flight controller (130) can be configured to receive and interpret data and information from a transceiver, or receiver, a GPS module, camera, a battery monitor, the inertial measurement unit (140), other onboard sensors, or user input (e.g., a “to follow me” command, a “maintain proximity to the user” command, and/or a “maintain the user in a line of sight” command in embodiments when the flight-enabled beacon (100) comprises a camera). In a further example, the flight controller (130) may communicate with the GPS module (170) and may be utilized by hikers, hunters, boaters, or other users desiring to use the flight-enabled beacon (100) as a positional tracking or locating system. The flight-enabled beacon (100) may optionally include a display and/or the flight-enabled beacon (100) may be in communication with a remote display showing its position and/or GPS coordinates in real-time. In some instances, the flight controller (130) can perform various operations with the components to perform an operation or method (e.g., controlling the gimbals (240, 250), or swashplate, controlling the rotor speed via the rotor rotation control (120) and motors (110, 112) of the individual or sets of rotatable blades (210, 220), activating the camera (180), activating the light emitting source (194), receiving or transmitting sounds or words via the audio unit, activating the safety unit, etc.); execute a preprogrammed or initiated command; and/or ascend and maintain the target altitude for a fixed time period. In a further embodiment, the flight controller (130) can maintain, or hover, the flight-enabled beacon (100) at the target altitude by using an internal command program loop, which calculates differences between its actual orientation and/or altitude and the target orientation and/or altitude and adjusts a parameter equivalent to the calculated difference. The flight controller (130) may use the feedback parameter, or command program loop output, to adjust the pitch, yaw, roll, and/or speed of individual and/or sets of rotatable blades (210, 220). In another embodiment, the flight controller (130) may receive input data, such as coordinates or commands, from a handheld controller or other user device to hold the orientation and/or target altitude.) 4. The method according to claim 2, wherein, in step a), features of a movement of the test vehicle are recognized, and wherein, in step a'), data from an inertial sensor system of the test vehicle are ascertained as the operating parameters. (Warner: [0047] In general, the flight-enabled beacon described herein is designed to be a portable, low-cost, lightweight, and weathertight device with controls capability to ascend and hover for a period of time in adverse weather conditions, such as those present in a man-overboard situation at sea, a fireman fighting a forest fire, or a hiker or hunter trekking through a mountainous, deserted region. In order to facilitate search and rescue operations, for example, the flight-enabled beacon is configured to fly and ascend to a target altitude while activating a light emitting source, or beacon, to signal for help. In some embodiments, the target altitude is automatic and dynamic, and a position of the flight-enabled beacon at the target altitude may be based on one or more of: GPS coordinates at a launch point, sensor data at the launch point (e.g., inertial measurement unit data), electronic signals received from a user device, or caller, (e.g., a caller bracelet, a flotation device, a cellular device carried by user, etc.), and/or images received by an image sensor or camera associated with the flight-enabled beacon. [0061] The flight controller (130) can be configured to collect and/or receive data and other information from the one or more components of the flight-enabled beacon (100), such as the sensor (140) or set of sensors, gimbals (240, 250), each rotatable blade (210 a-b, 220 a-b) and/or the sets of rotatable blades (210, 220), power source (190), safety unit, audio unit, inertial measurement unit (140), GPS module (170), transceiver (160), camera (180), light emitting source (194), flotation unit, housing, etc., and perform an actionable outcome. Examples of data and other information include, for example, sensor data, altitude coordinates, orientation data, inertial data for navigation, automatic identification system (AIS) radio data (e.g., receive a land command), etc. More specifically, the flight-enabled beacon (100) may be configured with an antenna receiver, such as shown as 1802 in FIG. 18, or transceiver (160, FIG. 1) for receiving a radio frequency signal from an incoming rescue operation or vehicle, for example helicopter (1302), indicating the land command. Further, the flight controller (130) can be configured to receive and interpret data and information from a transceiver, or receiver, a GPS module, camera, a battery monitor, the inertial measurement unit (140), other onboard sensors, or user input (e.g., a “to follow me” command, a “maintain proximity to the user” command, and/or a “maintain the user in a line of sight” command in embodiments when the flight-enabled beacon (100) comprises a camera). In a further example, the flight controller (130) may communicate with the GPS module (170) and may be utilized by hikers, hunters, boaters, or other users desiring to use the flight-enabled beacon (100) as a positional tracking or locating system. The flight-enabled beacon (100) may optionally include a display and/or the flight-enabled beacon (100) may be in communication with a remote display showing its position and/or GPS coordinates in real-time. In some instances, the flight controller (130) can perform various operations with the components to perform an operation or method (e.g., controlling the gimbals (240, 250), or swashplate, controlling the rotor speed via the rotor rotation control (120) and motors (110, 112) of the individual or sets of rotatable blades (210, 220), activating the camera (180), activating the light emitting source (194), receiving or transmitting sounds or words via the audio unit, activating the safety unit, etc.); execute a preprogrammed or initiated command; and/or ascend and maintain the target altitude for a fixed time period. In a further embodiment, the flight controller (130) can maintain, or hover, the flight-enabled beacon (100) at the target altitude by using an internal command program loop, which calculates differences between its actual orientation and/or altitude and the target orientation and/or altitude and adjusts a parameter equivalent to the calculated difference. The flight controller (130) may use the feedback parameter, or command program loop output, to adjust the pitch, yaw, roll, and/or speed of individual and/or sets of rotatable blades (210, 220). In another embodiment, the flight controller (130) may receive input data, such as coordinates or commands, from a handheld controller or other user device to hold the orientation and/or target altitude.) 5. The method according to claim 4, wherein, in step a), speeds and/or yaw rates of the test vehicle relative to ground are recognized as the signals and/or features, and wherein, in step a'), corresponding speeds and/or yaw rates of the test vehicle are ascertained as the operating parameters. (Warner: [0061] The flight controller (130) can be configured to collect and/or receive data and other information from the one or more components of the flight-enabled beacon (100), such as the sensor (140) or set of sensors, gimbals (240, 250), each rotatable blade (210 a-b, 220 a-b) and/or the sets of rotatable blades (210, 220), power source (190), safety unit, audio unit, inertial measurement unit (140), GPS module (170), transceiver (160), camera (180), light emitting source (194), flotation unit, housing, etc., and perform an actionable outcome. Examples of data and other information include, for example, sensor data, altitude coordinates, orientation data, inertial data for navigation, automatic identification system (AIS) radio data (e.g., receive a land command), etc. More specifically, the flight-enabled beacon (100) may be configured with an antenna receiver, such as shown as 1802 in FIG. 18, or transceiver (160, FIG. 1) for receiving a radio frequency signal from an incoming rescue operation or vehicle, for example helicopter (1302), indicating the land command. Further, the flight controller (130) can be configured to receive and interpret data and information from a transceiver, or receiver, a GPS module, camera, a battery monitor, the inertial measurement unit (140), other onboard sensors, or user input (e.g., a “to follow me” command, a “maintain proximity to the user” command, and/or a “maintain the user in a line of sight” command in embodiments when the flight-enabled beacon (100) comprises a camera). In a further example, the flight controller (130) may communicate with the GPS module (170) and may be utilized by hikers, hunters, boaters, or other users desiring to use the flight-enabled beacon (100) as a positional tracking or locating system. The flight-enabled beacon (100) may optionally include a display and/or the flight-enabled beacon (100) may be in communication with a remote display showing its position and/or GPS coordinates in real-time. In some instances, the flight controller (130) can perform various operations with the components to perform an operation or method (e.g., controlling the gimbals (240, 250), or swashplate, controlling the rotor speed via the rotor rotation control (120) and motors (110, 112) of the individual or sets of rotatable blades (210, 220), activating the camera (180), activating the light emitting source (194), receiving or transmitting sounds or words via the audio unit, activating the safety unit, etc.); execute a preprogrammed or initiated command; and/or ascend and maintain the target altitude for a fixed time period. In a further embodiment, the flight controller (130) can maintain, or hover, the flight-enabled beacon (100) at the target altitude by using an internal command program loop, which calculates differences between its actual orientation and/or altitude and the target orientation and/or altitude and adjusts a parameter equivalent to the calculated difference. The flight controller (130) may use the feedback parameter, or command program loop output, to adjust the pitch, yaw, roll, and/or speed of individual and/or sets of rotatable blades (210, 220). In another embodiment, the flight controller (130) may receive input data, such as coordinates or commands, from a handheld controller or other user device to hold the orientation and/or target altitude.) 6. The method according to claim 2, wherein steps a) and a') are carried out in parallel with one another for a minimum time interval so that, after performing steps a) and a'), in each case a temporal profile of signals and/or features and the operating parameters of the operation of the test vehicle (1) is available, wherein performing the synchronization according to step b) includes the comparison of a temporal profile of the signals and/or features ascertained in step a) and a temporal profile of the operating parameters ascertained in step a'). (Warner: [0047] In general, the flight-enabled beacon described herein is designed to be a portable, low-cost, lightweight, and weathertight device with controls capability to ascend and hover for a period of time in adverse weather conditions, such as those present in a man-overboard situation at sea, a fireman fighting a forest fire, or a hiker or hunter trekking through a mountainous, deserted region. In order to facilitate search and rescue operations, for example, the flight-enabled beacon is configured to fly and ascend to a target altitude while activating a light emitting source, or beacon, to signal for help. In some embodiments, the target altitude is automatic and dynamic, and a position of the flight-enabled beacon at the target altitude may be based on one or more of: GPS coordinates at a launch point, sensor data at the launch point (e.g., inertial measurement unit data), electronic signals received from a user device, or caller, (e.g., a caller bracelet, a flotation device, a cellular device carried by user, etc.), and/or images received by an image sensor or camera associated with the flight-enabled beacon. [0061] The flight controller (130) can be configured to collect and/or receive data and other information from the one or more components of the flight-enabled beacon (100), such as the sensor (140) or set of sensors, gimbals (240, 250), each rotatable blade (210 a-b, 220 a-b) and/or the sets of rotatable blades (210, 220), power source (190), safety unit, audio unit, inertial measurement unit (140), GPS module (170), transceiver (160), camera (180), light emitting source (194), flotation unit, housing, etc., and perform an actionable outcome. Examples of data and other information include, for example, sensor data, altitude coordinates, orientation data, inertial data for navigation, automatic identification system (AIS) radio data (e.g., receive a land command), etc. More specifically, the flight-enabled beacon (100) may be configured with an antenna receiver, such as shown as 1802 in FIG. 18, or transceiver (160, FIG. 1) for receiving a radio frequency signal from an incoming rescue operation or vehicle, for example helicopter (1302), indicating the land command. Further, the flight controller (130) can be configured to receive and interpret data and information from a transceiver, or receiver, a GPS module, camera, a battery monitor, the inertial measurement unit (140), other onboard sensors, or user input (e.g., a “to follow me” command, a “maintain proximity to the user” command, and/or a “maintain the user in a line of sight” command in embodiments when the flight-enabled beacon (100) comprises a camera). In a further example, the flight controller (130) may communicate with the GPS module (170) and may be utilized by hikers, hunters, boaters, or other users desiring to use the flight-enabled beacon (100) as a positional tracking or locating system. The flight-enabled beacon (100) may optionally include a display and/or the flight-enabled beacon (100) may be in communication with a remote display showing its position and/or GPS coordinates in real-time. In some instances, the flight controller (130) can perform various operations with the components to perform an operation or method (e.g., controlling the gimbals (240, 250), or swashplate, controlling the rotor speed via the rotor rotation control (120) and motors (110, 112) of the individual or sets of rotatable blades (210, 220), activating the camera (180), activating the light emitting source (194), receiving or transmitting sounds or words via the audio unit, activating the safety unit, etc.); execute a preprogrammed or initiated command; and/or ascend and maintain the target altitude for a fixed time period. In a further embodiment, the flight controller (130) can maintain, or hover, the flight-enabled beacon (100) at the target altitude by using an internal command program loop, which calculates differences between its actual orientation and/or altitude and the target orientation and/or altitude and adjusts a parameter equivalent to the calculated difference. The flight controller (130) may use the feedback parameter, or command program loop output, to adjust the pitch, yaw, roll, and/or speed of individual and/or sets of rotatable blades (210, 220). In another embodiment, the flight controller (130) may receive input data, such as coordinates or commands, from a handheld controller or other user device to hold the orientation and/or target altitude.) 7. The method according to claim 1, wherein step b) includes solving an optimization function in which a time shift parameter is minimized. (Warner: [0051] The processor (125) of the flight-enabled beacon (100) is configured to receive inputs from one or more of the components (e.g., flight controller (130), gimbals (240, 250), motors (110, 112), sensors (140), light emitting source (194), etc.) and interfaces the inputs with command loops, executable files, programmed functions, or software programs stored in the memory (135) of the flight-enabled beacon. Instructions executable by the processor (125) can include commands to determine one or more of a horizontal or a vertical orientation of the flight-enabled beacon (100). [0122] In some embodiments, the SAR drone (100, 1200, 1600, 1800) will include a performance profile defined by the maximum wind speed within which operations can be conducted, the average wind speed for normal operation, a minimum station time limit, a minimum beacon time limit, a minimum required float time, a worst case sea state for conducting operations, a worst case weather state for conducting operations, a minimum altitude requirement, a minimum time and/or distance from launch to victim requirement, and a minimum impact force/deceleration tolerance. An example of such a performance profile can require that the SAR drone can reliably fly and hover in 50 knot winds and tolerate up to 80 knot winds; tolerate 15 foot seas with spray and a period of 10 seconds; tolerate rain and lightning; provide 1 hour station time in air; provide 2 hour station time in water; provide multi-mile strobe reception; provide multi-mile wristband alarm; hover 100 feet above sea surface or victim; maintain an average flight speed in non-wind conditions of 50 knots or more; maintain a top flight speed in non-wind conditions of 80 knots or more; and have a recharging time of 5 hours or less. Other values for the performance profile can be used and it is expected that these examples will improve with improved drone/battery/communications/etc. technologies.) 8. The method according to claim 1, wherein the test vehicle is configured to emit a temporal signal pattern which is recognized in the video data in step a). (Warner: [0051] The processor (125) of the flight-enabled beacon (100) is configured to receive inputs from one or more of the components (e.g., flight controller (130), gimbals (240, 250), motors (110, 112), sensors (140), light emitting source (194), etc.) and interfaces the inputs with command loops, executable files, programmed functions, or software programs stored in the memory (135) of the flight-enabled beacon. Instructions executable by the processor (125) can include commands to determine one or more of a horizontal or a vertical orientation of the flight-enabled beacon (100). [0122] In some embodiments, the SAR drone (100, 1200, 1600, 1800) will include a performance profile defined by the maximum wind speed within which operations can be conducted, the average wind speed for normal operation, a minimum station time limit, a minimum beacon time limit, a minimum required float time, a worst case sea state for conducting operations, a worst case weather state for conducting operations, a minimum altitude requirement, a minimum time and/or distance from launch to victim requirement, and a minimum impact force/deceleration tolerance. An example of such a performance profile can require that the SAR drone can reliably fly and hover in 50 knot winds and tolerate up to 80 knot winds; tolerate 15 foot seas with spray and a period of 10 seconds; tolerate rain and lightning; provide 1 hour station time in air; provide 2 hour station time in water; provide multi-mile strobe reception; provide multi-mile wristband alarm; hover 100 feet above sea surface or victim; maintain an average flight speed in non-wind conditions of 50 knots or more; maintain a top flight speed in non-wind conditions of 80 knots or more; and have a recharging time of 5 hours or less. Other values for the performance profile can be used and it is expected that these examples will improve with improved drone/battery/communications/etc. technologies. [0063] Further, in some embodiments, the flight controller (130) of the flight-enabled beacon (100) may be configured to fly to the target or predetermined altitude, capture one or more images with an image sensor or camera (180, FIG. 1), and return to the launch point without user feedback (i.e., no input from a user device or handheld controller). Such embodiments may be ideal, for example, for accident recreation or gathering information in advance of first responder arrival on a scene.) 9. The method according to claim 8, wherein the temporal signal pattern includes at least one light signal. (Warner: [0056] The sets of rotatable blades (210, 220) may be individually positioned anywhere along the length of the housing, or body, of the flight-enabled beacon (100). For example, the first set of rotatable blades (220) may be positioned proximally, near the light emitting source (194) of the flight-enabled beacon (100), and the second set of rotatable blades (210) may be positioned distally near an end opposite the light emitting source (194). Alternatively, both sets of rotatable blades (210, 220) may be positioned proximally or distally or within a center region of the housing, or body. Alternatively, the first set of rotatable blades (210) may be positioned proximally or distally and the second set of rotatable blades (220) may be positioned centrally along the housing, or body. In some embodiments, the first set of blades (210) can be positioned above the second set of blades (220) along the housing, or body, axis (290), such that each blade is oriented away from the origin of the axis (290) with the blades spinning in parallel relative to each other and perpendicular to said axis (290).) 10. The method according to claim 9, wherein the temporal signal pattern is generated using a regular light source present on the test vehicle. (Warner: [0056] The sets of rotatable blades (210, 220) may be individually positioned anywhere along the length of the housing, or body, of the flight-enabled beacon (100). For example, the first set of rotatable blades (220) may be positioned proximally, near the light emitting source (194) of the flight-enabled beacon (100), and the second set of rotatable blades (210) may be positioned distally near an end opposite the light emitting source (194). Alternatively, both sets of rotatable blades (210, 220) may be positioned proximally or distally or within a center region of the housing, or body. Alternatively, the first set of rotatable blades (210) may be positioned proximally or distally and the second set of rotatable blades (220) may be positioned centrally along the housing, or body. In some embodiments, the first set of blades (210) can be positioned above the second set of blades (220) along the housing, or body, axis (290), such that each blade is oriented away from the origin of the axis (290) with the blades spinning in parallel relative to each other and perpendicular to said axis (290).) Conclusion The prior art made of record in form PTO-892 and not relied upon is considered pertinent to applicant's disclosure. PNG media_image1.png 254 896 media_image1.png Greyscale Any inquiry concerning this communication or earlier communications from the examiner should be directed to TAHMINA ANSARI whose telephone number is 571-270-3379. The examiner can normally be reached on IFP Flex - Monday through Friday 9 to 5. If attempts to reach the examiner by telephone are unsuccessful, the examiner’s supervisor, O’NEAL MISTRY can be reached on 313-446-4912. The fax phone numbers for the organization where this application or proceeding is assigned are 571-273-8300 for regular communications and 571-273-8300 for After Final communications. TC 2600’s customer service number is 571-272-2600. Any inquiry of a general nature or relating to the status of this application or proceeding should be directed to the receptionist whose telephone number is 571-272-2600. 2674 /Tahmina Ansari/ October 17, 2026 /TAHMINA N ANSARI/Primary Examiner, Art Unit 2674
Read full office action

Prosecution Timeline

Mar 31, 2025
Application Filed
Oct 21, 2026
Non-Final Rejection mailed — §101, §102 (current)

Precedent Cases

Applications granted by this same examiner with similar technology

Patent 12802392
METHOD AND APPARATUS FOR VISUAL-FEATURE NORMALIZATION AND SHARING OF IMAGE DATA
2y 11m to grant Granted Nov 17, 2026
Patent 12793382
METHOD OF IMAGE MATCHING AND IMAGE PROCESSING DEVICE
2y 11m to grant Granted Nov 10, 2026
Patent 12784421
SYSTEMS AND METHODS FOR IMPROVED TRAINING OF MACHINE LEARNING MODELS
3y 6m to grant Granted Nov 03, 2026
Patent 12778680
SYSTEMS FOR DYNAMIC 3D LUNG VISUALIZATION WHILE NAVIGATING A CATHETER WITHIN THE LUNG
2y 9m to grant Granted Nov 03, 2026
Patent 12784253
REGISTERING COORDINATE FRAMES FOR MIXED REALITY
2y 8m to grant Granted Nov 03, 2026
Study what changed to get past this examiner. Based on 5 most recent grants.

Strategy Recommendation AI-generated — please review before filing

Get a prosecution strategy drawn from examiner precedents, rejection analysis, and claim mapping.
Typically takes 5-10 seconds — AI-generated, attorney review required before filing

Prosecution Projections

1-2
Expected OA Rounds
85%
Grant Probability
99%
With Interview (+18.6%)
2y 6m (~10m remaining)
Median Time to Grant
Low
PTA Risk
Based on 910 resolved cases by this examiner. Grant probability derived from career allowance 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