Patent Grant
12280889
As compared to outdoor operations, operating an unmanned aerial vehicle, or drone, within indoor spaces presents a unique set of challenges for the unmanned aerial vehicle, and creates unique risks for contents of the indoor spaces. For example, an unmanned aerial vehicle that operates outdoors may typically climb above any encountered hazards by increasing altitude, in order to elevate above ground-based or airborne obstacles, which may include humans or other animals, or other stationary or moving objects. An unmanned aerial vehicle that operates indoors, however, is commonly constrained by ceilings at eight to ten foot elevations, or approximately one to five feet above the heights of most humans.
An unmanned aerial vehicle operating outdoors may capture data regarding its positions and orientations using one or more onboard sensors and interpret the data to generate commands or instructions for operating motors or control surfaces to avoid such obstacles. Because obstacles that are encountered in outdoor areas, such as structures, plant life, or others, are often separated by comparatively large distances, and because outdoor areas typically include sufficiently large spaces for operating unmanned aerial vehicles, an unmanned aerial vehicle is typically able to make wide, smooth changes in course or altitude without risking contact with any obstacles, even where the unmanned aerial vehicle is operating at or near its maximum speeds. Conversely, because indoor spaces are commonly constrained by narrow hallways or other passageways, and feature limited operating areas between floors and ceilings, an unmanned aerial vehicle that operates indoors must often make tight turns or changes in altitude, or travel well below its maximum speeds, in order to avoid contacting walls, ceilings, floors or other structural features.
For these reasons, and others, navigation systems and sensors provided aboard unmanned aerial vehicles operating in indoor spaces have small margins of error, and must capture and process data rapidly to ensure that changes in course, speed or altitude are timely and appropriately made.
As is set forth in greater detail below, the present disclosure is directed to systems and methods for indoor navigation and obstacle avoidance by unmanned aerial vehicles. The present disclosure describes, inter alia, unmanned aerial vehicles that are configured to calculate trajectories for traveling in a manner that minimizes snap, and for modifying such trajectories, as necessary, to maximize a speed of an unmanned aerial vehicle while traveling along a trajectory, or to minimize a risk that the unmanned aerial vehicle will contact one or more objects. An unmanned aerial vehicle may calculate a trajectory at any time prior to, during or following operations, such as when the unmanned aerial vehicle is at or over a waypoint, when the unmanned aerial vehicle has potentially detected an obstacle, or when the unmanned aerial vehicle has determined that a braking maneuver is necessary, among others. A trajectory may include sets of points in three-dimensional space.
In accordance with one or more preferred implementations, a trajectory may also include, for each defined point in three-dimensional space forming part of the trajectory, a time value indicating a time at which the trajectory passes through that point (e.g. a time at which a drone following that trajectory should pass through that point). Thus, a trajectory may be characterized as defining points in four-dimensional space-time.
In accordance with one or more preferred implementations, a trajectory may also include, for each defined point in three-dimensional space forming part of the trajectory, a yaw value indicating a yaw angle at that point of the trajectory.
In accordance with one or more preferred implementations, a trajectory is calculated using, or is defined by, one or more equations (e.g., a set of polynomial equations), and points along the trajectory can be calculated using the one or more equations. In accordance with one or more preferred implementations, one or more trajectory equations can be used to generate, at each time t along a trajectory, x, y, and z values indicating a position in three-dimensional space. In accordance with one or more preferred implementations, the one or more trajectory equations or x, y, and z values generated based thereon can be used to generate velocity information for any time t (e.g., indicating speed and direction).
In accordance with one or more preferred implementations, one or more trajectory equations can be used to generate, at each time t along a trajectory, a yaw value indicating a yaw angle. In accordance with one or more preferred implementations, the one or more trajectory equations or yaw values generated based thereon can be used to generate yaw velocity information for any time t (e.g., indicating speed and direction).
An unmanned aerial vehicle may generate and execute any number of commands or instructions (which may be executed by a control system or another component of the unmanned aerial vehicle), in order to cause the unmanned aerial vehicle to remain on a desired course, at a desired speed, or at a desired altitude in accordance with the trajectory.
The systems and methods of the present disclosure are further directed to unmanned aerial vehicles that continuously or repeatedly monitor for objects within predetermined ranges of their respective directions of travel using one or more range sensors. Upon determining that an object is detected within a predetermined range, an unmanned aerial vehicle may immediately slow, e.g., by one or more “braking” maneuvers, to decelerate or otherwise reduce a speed of the unmanned aerial vehicle, and continue to monitor for objects within a shorter, predetermined range using the one or more range sensors. Such a braking maneuver may include, for example, reducing a rotational speed or adjusting an operation of one or more rotors or engines. Ranges or distances to objects that are determined based on information or data captured by such sensors may be modified to account for travel of the unmanned aerial vehicle, in order to rapidly and efficiently assess whether such objects pose a risk of collision with the unmanned aerial vehicle. A speed at which to operate an unmanned aerial vehicle may be selected based on a state of the unmanned aerial vehicle, as determined based on such information or data, and the unmanned aerial vehicle may be configured to execute an emergency braking maneuver or take other action where the risk of collision is sufficiently high. Such an emergency braking maneuver may include, for example, operating one or more rotors or engines to cease thrust or to effect thrust in a direction opposite to a current direction of motion, such as to sharply reduce a speed of the unmanned aerial vehicle, or to bring the unmanned aerial vehicle to a stop.
The systems and methods of the present disclosure are also directed to unmanned aerial vehicles that are further configured to capture information or data from one or more range sensors, and to construct local maps of ranges from such information or data. The local maps may include a plurality of cells or other sectors, e.g., in a grid. One or more such cells may be determined to be obstructed where a calculated number of points, returns or detections received from such cells exceeds a predetermined threshold, and where a confidence level in the calculated number is sufficiently high. Additionally, upon determining that a cell may be obstructed, the number of points, returns or detections received from the cell may be compared to numbers of points, returns or detections received from neighboring cells (e.g., one or more adjacent cells). Where one or more of the numbers from neighboring cells is sufficiently high, a determination that the cell is obstructed may be confirmed.
Referring to
The drone 110 may be configured for travel within the facility 160, such as by way of the passageway 165. The drone 110 may include one or more motors, rotors, propellers, control surfaces or other features for causing the drone 110 to travel on any course, at any speed or at any altitude. The drone 110 may also include one or more onboard sensors, e.g., range sensors such as time-of-flight sensors or LIDAR (viz., light detection and ranging) sensors, imaging devices (e.g., digital cameras), microphones, or other sensors configured to capture information or data regarding temperatures, humidities, pressures, atmospheric conditions or other attributes of spaces of the facility 160, such as the passageway 165. The drone 110 may further include any number of computer processors, transceivers or other components that may be in communication with any number of computer systems (not shown) over a network that may include the Internet in whole or in part, or one or more of such networks. In some other embodiments, the facility 160 may include any number of other drones or other vehicles (not shown), e.g., two or more of such vehicles, which may be located in any number of spaces within the facility 160, or outside of the facility 160.
As is shown in
The coordinates of the waypoints A, B, C, D and E or coordinates of segments of a path between such waypoints may be programmed or represented in a map, e.g., an environment map of the facility 160 as a whole or an environment map of the passageway 165 in particular. For example, the environment map may also identify locations of boundaries such as walls, ceilings or floors within the facility 160, as well as locations of various utilities, portals, systems, appliances, fixtures or other aspects of the facility 160. For example, the drone 110 may also be programmed with coordinates of the potted plant 175 or any other obstacles (not shown) within the passageway 165. In some embodiments, map data may have been generated at least in part by the drone 110, or by one or more other autonomous vehicles, during one or more prior or concurrent missions throughout the facility 160, e.g., based on a simultaneous localization and mapping, or “SLAM,” algorithm. The drone 110 may further select any courses, speeds and/or altitudes for traveling within the facility 160 on any basis.
In some implementations of the present disclosure, a drone may be configured to calculate a trajectory that minimizes snap (or jounce), e.g., a fourth derivative of position, or a second derivative of acceleration, which may represent a rate of change of jerk with respect to time. Calculating a trajectory that minimizes snap enables the drone to travel through a plurality of waypoints in an efficient manner with limited yaw, pitch or roll. For example, as is shown in
where m is greater than or equal to two, and times Tj are times at which the drone 110 is located at a waypoint j between 0 and m.
The function ƒ(t) defines a trajectory in terms of positions in three-dimensional space and a yaw value, e.g., values of x, y, z, and ψ. Each of the values of the coefficients c0 . . . cm-1 may be solved by minimizing a fourth derivative of the function ƒ(t). In accordance with one or more preferred implementations, a function ƒ(t) may be utilized which defines a trajectory in terms of positions in three-dimensional space and a yaw value, e.g., values of x, y, z, and ψ.
A trajectory calculated according to the trajectory equation of
Once a trajectory is calculated according to the equation of
In some implementations, a trajectory may be calculated between two or more waypoints for the drone 110 by a navigation module (or a path planning module, a path learning module, or any other module). Inputs to the navigation module may include a path of a plurality of waypoints, or a map including one or more of the waypoints, as well as a current position or pose, velocity and acceleration of the drone 110, physical constraints of the drone 110, e.g., maximum velocities or accelerations of the drone 110, and continuity constraints of the drone 110, e.g., such that the trajectory is continuous at each waypoint. Outputs received from the navigation module may include a trajectory that passes through all of the waypoints, as well as one or more commands or instructions to be executed to cause the drone 110 to travel along the trajectory. The trajectory may be calculated with goals of smoothness (e.g., to avoid jittering motion during flight), safety (e.g., to minimize drift), feasibility (e.g., to ensure that the drone 110 may travel along the trajectory subject to its physical constraints) and timeliness (e.g., to ensure that the trajectory may be calculated promptly and with little to no latency).
In some implementations, a trajectory may be calculated for travel by the drone 110 through a next waypoint, or through a next two waypoints, rather than through all of the waypoints through which the drone 110 is required to travel. The trajectory may be calculated and recalculated or updated as the drone 110 passes through each of the waypoints, thereby conserving processing power and resources in real time, and enabling the drone 110 to make adjustments, as necessary. Alternatively, a trajectory may be calculated initially for traveling through all of the waypoints, and adjusted only as necessary. Additionally, and preferably, the trajectory may be calculated for travel by the drone 110 between a second waypoint, and a second-to-last waypoint, e.g., when the drone 110 is airborne, and not for travel by the drone 110 between a first waypoint and the second waypoint, e.g., when the drone 110 is taking off, or between the second-to-last waypoint and the last waypoint, e.g., when the drone is 110 is landing. In some implementations, a trajectory may also be calculated upon detecting an obstacle, upon executing a braking maneuver, or at any other time.
As is shown in
In accordance with one or more preferred implementations, a plurality of trajectory equations are calculated to define a trajectory from a first waypoint to a third waypoint through a second waypoint, and the trajectory equations are then utilized to generate a plurality of intermediate trajectory points (x, y, z) at various times t along the trajectory. In accordance with one or more preferred implementations, these calculated intermediate trajectory points are sent, at appropriate times, as setpoints to a navigation controller or module or another controller or module of a drone to attempt to effect travel of the drone along the trajectory. It will be appreciated that the result is that the drone will approximate the trajectory as it travels to the calculated points sent as setpoints for navigation.
As is shown in
Therefore, as is shown in
As is shown in
As is shown
For example, as is shown in
Additionally, in some implementations, an intervening waypoint may be inserted between a pair of waypoints in a path, as necessary, in order to ensure that the drone 110 may achieve or maintain a desired yaw angle while traveling along the path. For example, in some implementations, where a calculated trajectory calls for a change in yaw of the drone 110 between a pair of waypoints, e.g., a rotation from a first yaw angle to a second yaw angle, an estimated time for achieving the desired change in yaw may be calculated based on a maximum yaw velocity of the drone 110, and compared to an estimated time required to translate between the pair of waypoints according to a calculated trajectory. Where an estimated time for achieving the change in yaw is less than an estimated time required to translate between the pair of waypoints, then the calculated trajectory is sufficient to achieve both the desired translation from a first waypoint of the pair to a second waypoint of the pair, and also the desired change in yaw, and commands or instructions for traveling along the trajectory may be generated and executed by the drone 110. Where the estimated time for achieving the change in yaw is greater than the estimated time required to translate between the pair of waypoints according to the calculated trajectory, however, an intervening waypoint may be inserted between the pair of waypoints, and a new trajectory for traveling along a path between the three waypoints may be calculated, such as is shown in
Alternatively, in some implementations, a “safety corridor” may be established on segments of a path extending between any pair of waypoints, viz., the waypoints A, B, C, D and E. The safety corridor may be defined with respect to a straight-line segment of a path between any pair of the waypoints, and may have a width or another dimension on either side of the straight-line segment that is defined arbitrarily, defined with respect to one or more dimensions of the drone 110, or defined on any other basis. For example, the safety corridor may be defined with respect to the passageway 165, such as to be narrower than a width of the passageway 165, e.g., by a safety margin, with respect to any walls, floors or ceilings of the passageway 165. Where a trajectory calculated in accordance with implementations of the present disclosure would cause the drone 110 to breach or otherwise pass outside of a safety corridor so defined, an intervening waypoint may be inserted between the waypoints of the pair, and another trajectory that would cause the drone 110 to travel through the intervening waypoint may be calculated, such as is shown in
The systems and methods of the present disclosure are directed to the indoor navigation and obstacle avoidance by aerial vehicles (e.g., unmanned aerial vehicles, or drones). The aerial vehicles of the present disclosure may be of any type or form, and may include but need not be limited to low-power drones that may be configured for efficient path planning, adaptive speed modification, and obstacle avoidance techniques during operations within indoor spaces.
In some implementations, an unmanned aerial vehicle may be configured to calculate or plan trajectories that rely on maximum speed capacities of the unmanned aerial vehicle. For example, where an unmanned aerial vehicle is programmed or configured to travel through each of a plurality of waypoints (or spatial points), the unmanned aerial vehicle may calculate a trajectory as a set of piece-wise polynomial functions of orders from zero to six, through a plurality of m waypoints, viz., from a waypoint 0 to a waypoint m, that represent positions of the unmanned aerial vehicle in three-dimensional space and minimize snap for the unmanned aerial vehicle. The unmanned aerial vehicle may adjust its speed according to a calculated risk of collision with any obstacles, and make smooth transitions in speed, while traveling through the various waypoints, with minimized yaw, pitch or roll.
In some implementations, an unmanned aerial vehicle may determine whether a trajectory would cause the unmanned aerial vehicle to come into contact with one or more known obstacles while traveling between waypoints. If the unmanned aerial vehicle determines that the trajectory would cause the unmanned aerial vehicle to come into contact with or pass unacceptably close to an obstacle between a pair of waypoints, the unmanned aerial vehicle may insert an additional waypoint (e.g., an intervening waypoint at a midpoint between the pair of waypoints), and recalculate a trajectory that causes the unmanned aerial vehicle to pass through the additional waypoint. If the recalculated trajectory would cause the unmanned aerial vehicle to pass the obstacle at a safe distance, the unmanned aerial vehicle may proceed along the recalculated trajectory.
In some implementations, an unmanned aerial vehicle may determine whether a distance between any of a pair of waypoints is sufficiently long to enable the unmanned aerial vehicle to accelerate to a maximum speed upon departing from one of the waypoints and to decelerate from the maximum speed prior to arriving at another of the waypoints. If the unmanned aerial vehicle may both accelerate to and decelerate from a maximum speed between a pair of waypoints, the trajectory may be calculated to include a first intervening waypoint located at a minimum acceleration distance from one of the waypoints of the pair and a second intervening waypoint located at a minimum deceleration distance from another of the waypoints of the pair. The unmanned aerial vehicle may thus travel at the maximum speed between the first intervening waypoint and the second intervening waypoint.
In some implementations, an unmanned aerial vehicle may be outfitted or equipped with one or more modules, e.g., hardware components or software applications to be executed by one or more hardware components. Such modules may include an obstacle detection module that may assess relative positions of obstacles in a given environment, using temporal information to fuse data received from range sensors provided aboard the unmanned aerial vehicle, e.g., a rotating two-dimensional LIDAR sensor and time-of-flight sensors provided in fixed orientations with respect to a fuselage or other component of the unmanned aerial vehicle. Additionally, a range map, a point cloud or another representation may be subject to pixelization to determine whether any obstacles are present, and to minimize computation resources and processing power.
Additionally, in some implementations, an unmanned aerial vehicle may be configured to determine a state of risk that the unmanned aerial vehicle may collide with one or more objects, and to select a speed of the unmanned aerial vehicle based on the state of risk. For example, where the unmanned aerial vehicle does not detect any obstacles within a first predetermined range in a direction of travel of the unmanned aerial vehicle (or on a heading of the unmanned aerial vehicle), the unmanned aerial vehicle may travel at a maximum speed, or at any other safe speed, along the direction of travel, consistent with a state of low or insignificant risk. Alternatively, where the unmanned aerial vehicle detects one or more obstacles within the first predetermined range in the direction of travel, the unmanned aerial vehicle may execute an immediate braking maneuver, and may slow to a predetermined speed that may be a fraction of the maximum speed, consistent with a state of high or significant risk. For example, in some implementations, in order to immediately brake, an unmanned aerial vehicle may insert an intervening waypoint that is directly behind a position of the unmanned aerial vehicle, and calculate a trajectory that would cause the unmanned aerial vehicle to attempt to return to the intervening waypoint, e.g., by operating one or more motors or control surfaces, and to effectively brake as a result.
The unmanned aerial vehicle may recalculate a trajectory for the unmanned aerial vehicle at the reduced speed, and continue to determine whether any obstacles are present along the trajectory of the unmanned aerial vehicle within a second predetermined range that may be shorter than the first predetermined range, subject to any adjustments compensating for the motion of the unmanned aerial vehicle along the direction of travel. If an obstacle is present within the second predetermined range, the unmanned aerial vehicle may execute an emergency maneuver, e.g., to immediately brake or to otherwise avoid the obstacle, such as by inserting an intervening waypoint immediately behind the unmanned aerial vehicle. If no obstacles are detected within the second predetermined range, then the unmanned aerial vehicle may continue to proceed at the predetermined reduced speed before accelerating to the maximum speed again upon confirming that the unmanned aerial vehicle is at a state of acceptable risk.
In accordance with some embodiments of the present disclosure, an unmanned aerial vehicle (e.g., a drone) may be programmed or configured to generate one or more environment maps of spaces within a facility using images or other data captured by one or more onboard sensors. Such sensors may include digital cameras (e.g., visual or depth cameras) or other imaging devices, which may be aligned with fields of view or axes of orientation extending in any direction, e.g., forward, aft, port, starboard, up, down, or in any other direction. For example, the imaging devices may have fields of view or axes of orientation that are aligned along or parallel to yaw, pitch or roll axes of an unmanned aerial vehicle, e.g., principal axes of the unmanned aerial vehicle, or at any other angle. In some embodiments, an unmanned aerial vehicle may include one or more depth cameras or range sensors, such as LIDAR sensors or time-of-flight sensors, that are aligned at any angle with respect to an orientation or configuration of an unmanned aerial vehicle. For example, the unmanned aerial vehicle may include depth cameras or range sensors with fields of view or orientations pointing vertically upward or downward, as well as depth cameras or range sensors having fields of view or orientations that vary with respect to an orientation or configuration of the unmanned aerial vehicle. In some embodiments, an unmanned aerial vehicle may include one or more imaging devices such as depth cameras or range sensors (e.g., LIDAR sensors or other time-of-flight sensors) that are configured to determine ranges based on any number of pixels of data, e.g., grids of four pixels by four pixels, or eight pixels by eight pixels, or the like. In some embodiments, an unmanned aerial vehicle may include one or more imaging devices such as depth cameras or range sensors that are configured to determine ranges based on single pixels of data, e.g., a single-pixel LIDAR sensor or other sensor. Moreover, the unmanned aerial vehicle may include one or more depth cameras, range sensors or other systems that are aligned with fixed orientations, or with variable orientations (e.g., rotating or shifting orientations).
The unmanned aerial vehicles of the present disclosure may be outfitted with one or more processors, components, transceivers, sensors or other systems for engaging in communications with aspects of a facility (e.g., appliances, lighting, environmental or other systems), as well as any persons within the facility. For example, an unmanned aerial vehicle may include any number of transceivers for communicating with aspects of the Internet or one or more other networks, including but not limited to any wired or wireless routers within a facility, or any other computer devices therein, as well as any number of sensors or readers for communicating via any wired or wireless systems or protocols, including but not limited to wireless fidelity (“Wi-Fi”), Bluetooth, radio frequency identification (or “RFID”), near-field communication (or “NFC”) readers, or any other type of systems or protocols. For example, the unmanned aerial vehicles may further include any number of audio or video sensors, including but not limited to one or more imaging devices (e.g., digital cameras) and/or microphones, or any other type of sensors, embedded or incorporated therein.
Additionally, an unmanned aerial vehicle may further include any number of sensors, such as imaging devices (e.g., cameras configured to capture visual or depth data), temperature sensors, magnetometers, Wi-Fi receivers, Bluetooth receivers, or others, and may be programmed or configured to travel throughout one or more spaces of a facility and to capture data using such sensors. Based on the captured data, an environment map of such spaces or the facility may be generated. The environment map may identify or depict one or more boundaries (e.g., walls, ceilings, floors) or other aspects of such spaces, as well as the respective dimensions of such spaces, or the respective surfaces or textures of such boundaries. In some embodiments, an unmanned aerial vehicle may autonomously travel throughout one or more spaces of a facility in order to capture data using one or more sensors, and such data may be utilized in generating an environment map of the spaces of the facility. In some other embodiments, an unmanned aerial vehicle may be transported (e.g., carried) or escorted by a human actor throughout such spaces, and may capture data using one or more sensors as the unmanned aerial vehicle is transported or escorted throughout such spaces. Data captured as the unmanned aerial vehicle is escorted may be utilized in generating an environment map of the spaces of the facility. Additionally, in some embodiments, the unmanned aerial vehicle may selectively operate one or more propulsion motors as the unmanned aerial vehicle is transported or otherwise escorted throughout such spaces, in order to maintain altitude and/or tilt control. Furthermore, in some embodiments, data captured by the unmanned aerial vehicle as the unmanned aerial vehicle travels throughout the spaces of the facility may be adjusted to account for presence of one or more body parts of a human actor that is transporting or otherwise escorting the unmanned aerial vehicle through the facility.
In accordance with some embodiments of the present disclosure, an unmanned aerial vehicle may be configured to operate along with one or more stations, e.g., base components, charging docks (or charging stations or docking stations), or other intermediary devices. Such stations may have openings, cavities or spaces configured to accommodate one or more portions of an unmanned aerial vehicle, and may include one or more surfaces that are aligned to come into contact with corresponding surfaces of the unmanned aerial vehicle, thereby enabling electrical power, information or data to be conveyed between the unmanned aerial vehicle and such stations. In some embodiments, a base component, a charging dock, or another intermediary device may include an opening, a cavity or another space that is sized and shaped to receive or accommodate a specific portion of an unmanned aerial vehicle, e.g., a fuselage of the unmanned aerial vehicle, and to enable the unmanned aerial vehicle to be aligned in one of a plurality of alignments or orientations with respect to the base component, the charging dock or intermediary device.
Moreover, aerial vehicles of the present disclosure may be configured for use or operation within facilities of any kind. As used herein, the term “facility” shall refer to any building, region, structure or other space (e.g., covered or uncovered), such as a home of any type, kind, shape or form, including but not limited to a house, an apartment, a condominium, a dormitory, a barracks, or any other defined or undefined structure having one or more living spaces. A facility may also be a business-related structure such as a building, an office, a shopping center, a restaurant, a post office, a grocery store, a department store, a materials handling facility, or any other defined or undefined structure having one or more commercial areas. A facility may also be any other type of facility including but not limited to stadiums, ballfields, transportation centers or financial institutions (e.g., banks). In some embodiments, the facility may be or include an island or a space station.
Referring to
The unmanned aerial vehicle 210 may be an aerial vehicle (e.g., a drone), that may be programmed or configured to autonomously perform one or more operations within spaces of a facility. As is shown in
The processor 212 may be configured to perform any type or form of computing function associated with the operation of the unmanned aerial vehicle 210. For example, the processor 212 may be configured to execute any other algorithms or techniques (e.g., machine learning systems or techniques) associated with one or more applications, purposes or functions, such as navigation, monitoring or collision avoidance, or to select at least one of a course, a speed or an altitude for the safe operation of the unmanned aerial vehicle 210. The processor 212 may be configured to control any aspects of the operation of the unmanned aerial vehicle 210 and any computer-based components thereon, including but not limited to the motors 225 or the sensors 230. For example, the processor 212 may control the operation of one or more control systems or modules, such as the control system 220, for generating instructions for conducting operations of one or more of the motors 225 or the sensors 230. Such control systems or modules may be associated with one or more other computing devices or machines, and may communicate with the data processing system 280 or one or more other computer devices over the network 290, through the sending and receiving of digital data.
The processor 212 may be a uniprocessor system including one processor, or a multiprocessor system including several processors (e.g., two, four, eight, or another suitable number), and may be capable of executing instructions. For example, in some embodiments, the processor 212 may be a general-purpose or embedded processor unit such as a CPU or a GPU having any number of instruction set architectures (ISAs), such as the x86, PowerPC, SPARC, or MIPS ISAs, or any other suitable ISA. Where the processor 212 is a multiprocessor system, each of the processors within the multiprocessor system may operate the same ISA, or different ISAs.
Additionally, the unmanned aerial vehicle 210 further includes one or more memory or storage components 214 (such as databases or data stores) for storing any type of information or data, e.g., instructions for operating the unmanned aerial vehicle 210, or information or data captured during operations of the unmanned aerial vehicle 210. The memory 214 may be configured to store executable instructions, imaging data, paths or routes, control parameters and/or other data items accessible by or to the processor 212. The memory 214 may be implemented using any suitable memory technology, such as random-access memory (or “RAM”), static RAM (or “SRAM”), synchronous dynamic RAM (or “SDRAM”), nonvolatile/Flash-type memory, or any other type of memory. In some embodiments, program instructions, imaging data, flight paths, flight control parameters and/or other data items may be received or sent via the transceiver 216, e.g., by transmission media or signals, such as electrical, electromagnetic, or digital signals, which may be conveyed via a communication medium such as a wired and/or a wireless link.
The transceiver 216 may be configured to enable the unmanned aerial vehicle 210 to communicate through one or more wired or wireless means, e.g., wired technologies such as Universal Serial Bus (or “USB”) or fiber optic cable, or standard wireless protocols or standards such as Bluetooth or any Wi-Fi protocol, over the network 290 or directly. The transceiver 216 may further include or be in communication with one or more input/output (or “I/O”) interfaces, and may be configured to allow information or data to be exchanged between one or more of the components of the unmanned aerial vehicle 210, or to one or more other computer devices or systems (e.g., other aerial vehicles, not shown) via the network 290. For example, in some embodiments, the transceiver 216 may be configured to coordinate I/O traffic between the processor 212 and one or more onboard or external computer devices or components, e.g., the control system 220, or the motors 225 or sensors 230. The transceiver 216 may perform any necessary protocol, timing or other data transformations in order to convert data signals from a first format suitable for use by one component into a second format suitable for use by another component. In some embodiments, the transceiver 216 may include support for devices attached through various types of peripheral buses, e.g., variants of the Peripheral Component Interconnect (PCI) bus standard or the USB standard. In some other embodiments, functions of the transceiver 216 may be split into two or more separate components, or integrated with the processor 212.
The control system 220 may include one or more electronic speed controls, power supplies, navigation systems and/or payload engagement controllers for controlling the operation of the unmanned aerial vehicle 210 and for engaging with or releasing items, as desired. For example, the control system 220 may be configured to cause or control the operation of one or more of the motors 225, e.g., to cause one or more of the motors 225 to operate at desired speeds, in order to guide the unmanned aerial vehicle 210 along a desired course, at a desired speed, or at a desired altitude, as appropriate. The control system 220 may further control any other aspects of the unmanned aerial vehicle 210, including but not limited to the operation of one or more steering or braking systems, or one or more control surfaces such as wings, rudders, flaperons, elevons, elevators, ailerons, flaps, brakes or slats, within desired ranges. In some embodiments, the control system 220 may be integrated with one or more of the processor 212, the memory 214 and/or the transceiver 216.
The motors 225 may be any type or form of motor (e.g., electric, gasoline-powered or any other type of motor) capable of generating sufficient rotational speeds of one or more propellers or other components to provide thrust and/or lift forces to the unmanned aerial vehicle 210 and any payload engaged thereby. In some embodiments, one or more of the motors 225 may be a brushless direct current (“DC”) multi-phase motor such as an outrunner brushless motor or an inrunner brushless motor.
The unmanned aerial vehicle 210 may include any number of such motors 225 of any kind. For example, one or more of the motors 225 may be aligned or configured to operate with different capacities or ratings, or at different speeds, or coupled to any number of wheels or propellers having different sizes and shapes. Additionally, one or more of the motors 225 may be an electric motor, e.g., a brushless DC multi-phase motor, and one or more of the motors 225 may be a gasoline-powered motor.
The unmanned aerial vehicle 210 may also include any number of sensors 230 or other components or other features for capturing data within a vicinity of the unmanned aerial vehicle 210, including but not limited to one or more imaging devices (e.g., digital cameras), Global Positioning System (“GPS”) receivers or sensors, compasses, speedometers, altimeters, thermometers, barometers, hygrometers, gyroscopes, air monitoring sensors (e.g., oxygen, ozone, hydrogen, carbon monoxide or carbon dioxide sensors), ozone monitors, pH sensors, magnetic anomaly detectors, metal detectors, radiation sensors (e.g., Geiger counters, neutron detectors, alpha detectors), attitude sensors, depth gauges, accelerometers, or sound sensors (e.g., microphones, piezoelectric sensors, vibration sensors or other transducers for detecting and recording acoustic energy from one or more directions).
Although the block diagram of
The personnel 240 (or operators, or users, or other persons) may be any individual or entity associated with the facility 260. For example, the personnel 240 may be any individual or entity having a permanent or temporary right of occupation, possession or ownership of all or any portion of the facility 260, including but not limited to a resident, a tenant, an employee, or a contractor, or any other individual designated by an owner, a resident, a tenant, an employee or a contractor of the facility 260. The personnel 240 may utilize any number of computing devices 245 (e.g., a smartphone, a tablet computer, a laptop computer, a desktop computer, or computing devices provided in wristwatches, televisions, set-top boxes, automobiles or any other appliances or machines), or any other machines. As is shown in
The intermediary device 250 includes one or more processors 252, data stores 254, transceivers 256, sensors 257 and/or feedback devices 258. The transceivers 256 may be configured to receive or transmit electrical power to or from the unmanned aerial vehicle 210, or to receive or transmit information or data to or from the unmanned aerial vehicle 210, the personnel 240, the facility 260 and/or the data processing system 280, or any other computing device over the network 290.
Moreover, in some embodiments, the intermediary device 250 may be configured to receive and/or interpret signals received from any systems or sensors within or without the facility 260, and to determine, with one or more measures of a level of confidence (e.g., a confidence score), whether a predetermined event or condition has occurred or is present within the one or more spaces. In some embodiments, the intermediary device 250 may transmit one or more sets of instructions to such systems or sensors, or to establish one or more settings or conditions of such systems or sensors. Any of the applications or functions described herein as being executed or performed by the data processing system 280 herein may be executed or performed by the intermediary device in accordance with embodiments of the present disclosure.
Additionally, the intermediary device 250 may further include any type of power source for providing electrical power, e.g., alternating current (“AC”) or DC power, or other forms of power in support of one or more electrical loads. Such power sources may include, for example, one or more batteries or other power cells, e.g., dry cell or wet cell batteries such as lead-acid batteries, lithium ion batteries, nickel cadmium batteries or nickel metal hydride batteries, or any other type, size or form of batteries, and may each have any cell voltages, peak load currents, charge times, specific energies, internal resistances or cycle lives, or other power ratings. The intermediary device 250 may also include any type, size or form of other power source, e.g., other than a battery, including but not limited to one or more fuel cells or solar cells.
The intermediary device 250 may be or include any computer-related machine that is configured to control the operation of one or more aspects of the facility 260 on behalf of the personnel 240. For example, the intermediary device 250 may be configured to control the capture of information or data within the facility 260 by one or more sensors 270-1, 270-2 . . . 270-n, or to grant or restrict access to the facility 260 by operating (e.g., locking, unlocking, opening, closing) one or more of the portals 274. Alternatively, the intermediary device 250 may be configured to activate any other systems that may be associated with the facility 260 (e.g., lighting and/or environmental systems). In this regard, the intermediary device 250 may receive information, data and/or instructions from one or more of the personnel 240, e.g., by way of the computer device 245, in the form of a direct inter-device connection or over the network 290. In some embodiments, the intermediary device 250 may be a general purpose computer device or system, or a special purpose computer device or system, provided within or in association with the facility 260, and configured to execute one or more applications or functions associated with operations occurring within the facility 260.
In some embodiments, the intermediary device 250 may be a charging station, e.g., a system including a set of one or more contacts for transferring electrical power to the unmanned aerial vehicle 210 or any other component, or for receiving electrical power from the unmanned aerial vehicle 210 or any other component, via a corresponding set of one or more contacts provided on one or more portions of the unmanned aerial vehicle 210. In some embodiments, the intermediary device 250 may be a docking station, e.g., a system including one or more physical or structural features for engaging with or providing support to the unmanned aerial vehicle 210 or any other component, such as to maintain the unmanned aerial vehicle 210 in a specific location, position or orientation. In some embodiments, the intermediary device 250 may be a charging dock, e.g., a system having one or more features of a charging station and/or a docking station as described herein. In some embodiments, the intermediary device 250 may be a smart speaker, a personal assistant device, a home security system component, or any other like machine associated with the facility 260. Alternatively, or additionally, in some embodiments, the intermediary device 250 may include any number or set of features of a charging station, a docking station, a charging dock, a smart speaker, a personal assistant device, a home security system component, or any other machine or component.
The sensors 257 may be any type or form of sensors having any components or features for determining one or more attributes of the intermediary device 250 and/or the facility 260, including extrinsic information or data or intrinsic information or data. Such sensors 257 may be installed in the same common unit as the one or more processors 252, data stores 254, transceivers 256 and/or feedback devices 258, or in one or more units provided in association with (and in communication with) such components, subject to functional or spacing limitations or constraints.
In some embodiments, the sensors 257 may include one or more thermometers, barometers, hygrometers, anemometers, current sensors, voltage sensors, resistance sensors or any other type or form of sensor. In some other embodiments, the sensors 257 may include one or more air monitoring sensors (e.g., oxygen, ozone, hydrogen, carbon monoxide or carbon dioxide sensors), acoustic sensors (e.g., microphones, piezoelectric sensors, vibration sensors), infrared sensors, ozone monitors, pH sensors, magnetic anomaly detectors, metal detectors, radiation sensors (e.g., Geiger counters, neutron detectors, alpha detectors) or the like, as well as one or more imaging devices (e.g., digital cameras). In some embodiments, information or data captured by one or more of the sensors 257 may be used to authenticate one or more individuals or entities at the facility 260, including but not limited to the personnel 240, or any other individual or entity.
The intermediary device 250 may further include one or more feedback devices 258. The feedback devices 258 may be any component configured for returning feedback to the personnel 240, or to any other individuals or entities in or around the facility 260. Such feedback devices 258 may be installed in the same common unit as the one or more processors 252, data stores 254 and/or transceivers 256, or in one or more units provided in association with (and in communication with) such components, subject to functional or spacing limitations or constraints.
In some embodiments, the feedback devices 258 may include one or more individually addressable lighting elements (e.g., LED lights) that may be automatically controlled or configured to emit light in any frequency, intensity or hue. In some other embodiments, the feedback devices 258 may include one or more audio speakers or other physical components that may be automatically controlled or configured to transmit audible messages, signals or sounds. In some other embodiments, the feedback devices 258 may include one or more haptic vibrating elements, e.g., any physical component that may be automatically controlled or configured to generate tactile vibrations of any frequency or intensity.
The facility 260 may be any building, region, structure or other space (e.g., covered or uncovered) to which the automated control of access may be desired, or from within which secure communications may be desired. For example, as is discussed above, the facility 260 may be a home or a business-related structure of any type, kind, shape or form, or any other type of facility. The facility 260 may further include a networked computer infrastructure, including one or more processors 262, data stores (e.g., databases) 264, transceivers 266 (e.g., transmitters and/or receivers) and I/O devices 268 (e.g., keyboards, keypads, mice, styluses, touchscreens, RFID readers, or other devices).
The facility 260 further includes the sensors 270-1, 270-2 . . . 270-n, one or more sources 272 of wireless energy, and one or more portals 274. The sensors 270-1, 270-2 . . . 270-n may take the form of one or more of the sensors 257 described above, and, like such sensors 257, may be any operational and/or environmental sensors having any components or features for determining one or more attributes of the facility 260, including extrinsic information or data or intrinsic information or data. The sensors 270-1, 270-2 . . . 270-n may further include one or more sensors that are associated with security functions at the facility 260, including one or more door sensors, window sensors, motion sensors, security cameras, or others.
In some embodiments, the I/O devices 268 may be configured to receive and provide information to the personnel 240 or to any other individuals or entities at the facility 260, and may include, but are not limited to, a display, (e.g., a touch-screen display), a scanner, a keypad, a biometric scanner, an audio transducer, one or more speakers, one or more imaging devices such as a video camera, and any other types of input or output devices that may support interaction between the intermediary device 250, the facility 260 and/or the various personnel 240. For example, in one embodiment, the I/O devices 268 may include a touchscreen display and/or a keypad for receiving inputs. In various embodiments, the I/O devices 268 may have capabilities for directly receiving such signals from the personnel 240 or the intermediary device 250 that provides a signal or an instruction to operate one or more of the portals 274.
The sources 272 may be any components within or associated with the facility 260 that are configured to transmit wireless energy in any type or form. For example, one or more of the sources 272 may include a current-carrying conductor of any kind, which may generate and radiate a magnetic field according to Ampere's Law. The sources 272 may further include any device or system that is configured to communicate according to one or more wireless protocols or standards, such as any Wi-Fi or Bluetooth protocol or standard.
The portals 274 may include one or more doors, windows or other access points, as well as any electrometrical components for automatically operating such doors or other access points. Such portals 274 may be used to obtain access to the facility 260, e.g., an external door, or to obtain access to one or more specific spaces within the facility 260, e.g., an internal door, such as one or more rooms within the facility 260. The portals 274 may further include any other systems associated with other openings to the facility 260, such as windows.
The portals 274 may be operated under the control of the unmanned aerial vehicle 210, the processors 262 and/or the intermediary device 250 or, alternatively, the computer device 245 of the personnel 240. For example, each of the portals 274 may be in communication with the one or more processors 262 and/or the intermediary device 250, e.g., Bluetooth® or Wi-Fi, and may transmit or receive one or more signals or instructions associated with their respective operations. Alternatively, any of the portals 274 may be operated based at least in part on manual or automatic inputs provided by the personnel 240 or another authorized individual at the facility 260, e.g., by way of the I/O devices 268. In some embodiments, one or more of the portals 274 may include an electromechanical operating and/or locking mechanism which is designed to automatically open or close a portal, or to lock or unlock the portal, in response to signals or instructions from an authorized device using a wired or wireless protocol. Such instructions may include a password or another authenticator (e.g., a cryptographic key). Additionally, the portals 274 may be associated with the one or more sensors 270-1, 270-2 . . . 270-n, or may include one or more sensors, and may be configured to capture information or data regarding successful or unsuccessful attempts at operation thereof, or any other events occurring at the facility 260.
The data processing system 280 includes one or more physical computer servers 282 having one or more computer processors, one or more data stores (e.g., databases) 284, and any number of transceivers 286 associated therewith, as well as provided for any specific or general purpose. In some embodiments, the data processing system 280 of
The servers 282 may be connected to or otherwise communicate with the data stores 284 and the transceivers 286, and may receive, analyze or store any type of information or data, e.g., imaging data, acoustic signals, environmental conditions, operational characteristics, or positions, or any other information or data, for any purpose. The servers 282 and/or the data stores 284 may also connect to or otherwise communicate with the network 290, through the sending and receiving of digital data. In some embodiments, the data processing system 280 may be provided in a physical location, e.g., in association with the facility 260. In other such embodiments, the data processing system 280 may be provided in one or more alternate or virtual locations, e.g., in a “cloud”-based environment. In still other embodiments, the data processing system 280 may be provided onboard one or more vehicles, including but not limited to the unmanned aerial vehicle 210.
Each of the transceivers 216, 246, 256, 266, 286 or other communications devices, systems or components may be configured to communicate through one or more wired or wireless means, e.g., wired technologies such as Universal Serial Bus (or “USB”) or fiber optic cable, or wireless standards or protocols such as Bluetooth® or any Wi-Fi protocol, over the network 290 or directly. The transceivers 216, 246, 256, 266, 286 may further include or be in communication with one or more I/O interfaces, network interfaces or devices, and may be configured to allow information or data to be exchanged between one another, or to or from one or more other computer devices or systems via the network 290.
The transceivers 216, 246, 256, 266, 286 may perform any necessary protocol, timing or other data transformations in order to convert data signals from a first format suitable for use by one component into a second format suitable for use by another component. For example, in some embodiments, the transceivers 216, 246, 256, 266, 286 may be configured to communicate according to one or more protocols traditionally associated with discrete components, e.g., within specific frequency spectra, including but not limited to radio frequency signals typically within ranges of approximately three hundred to four hundred megahertz, or MHz, as well as radio frequency signals typically within ranges of approximately three hundred to five hundred megahertz, or MHz.
In some embodiments, the transceivers 216, 246, 256, 266, 286 may be configured to transmit or receive Bluetooth® signals sent within an industrial, scientific and medical (ISM) radio frequency range of approximately 2.400 to approximately 2.500 gigahertz (GHz), with a center frequency of approximately 2.450 GHz. Such signals are typically sent within a particular range of approximately 2.402 to approximately 2.480 GHz, and have a maximum transmission rate on Bluetooth® networks of 3 megabits per second (or 3 Mbps) or more, with a maximum transmission range of 10 to 100 meters or more, and at powers of approximately one milliwatt (mW), or 0.001 watts (W). The transceivers 216, 246, 256, 266, 286 may operate according to a frequency-hopping spread spectrum (FHSS) method, e.g., by switching carriers across multiple frequency channels and transmitting communications in small segments, and in respective time slots. In some embodiments, such communications may be transmitted at approximately 1,600 times per second across 79 different subfrequencies at bandwidths of 0.001 GHz, or one megahertz (MHz) across the 2.402 to 2.480 GHz range.
In some embodiments, the transceivers 216, 246, 256, 266, 286 may be configured to transmit or receive Ultra-Wide Band (or “UWB”) signals over one or more broad spectrums within any radio frequency range. In some embodiments, the UWB signals may be transmitted and/or received over a range of approximately three to eleven gigahertz (GHz), or over a range of approximately four to six gigahertz (GHz), with a center frequency of approximately five gigahertz (GHz). Alternatively, the UWB signals may be transmitted over any frequency range, and with any center frequency. Additionally, the UWB signals may consist of billions of pluses transmitted across such frequency spectrums, and at various power levels or power densities.
In some embodiments, the transceivers 216, 246, 256, 266, 286 may be configured to transmit or receive RFID signals at low frequency (LF), medium frequency (MF) or high frequency (HF) levels (e.g., approximately 3 kilohertz to 30 megahertz, or 3 kHz-30 MHz) and transfer relatively small-sized sets or packets of data over short ranges (e.g., between one and one hundred centimeters, or 1-100 cm). In some other embodiments, the transceivers 216, 246, 256, 266, 286 may be configured to transmit or receive RFID signals at higher frequency levels, such as ultrahigh frequency (UHF) or microwave levels (e.g., approximately 300 megahertz to 300 gigahertz, or 300 MHz-300 GHz) including larger sets or packets of data at ranges of one meter (1 m) or longer.
Alternatively, the transceivers 216, 246, 256, 266, 286 may be configured to communicate within customized frequency spectra, or at dynamic frequencies, in accordance with the present disclosure. For example, in some embodiments, one or more of the transceivers 216, 246, 256, 266, 286 may be configured to communicate according to a proprietary standard or protocol, or within a proprietary frequency spectrum.
In some embodiments, the transceivers 216, 246, 256, 266, 286 may include support for devices attached through various types of peripheral buses, e.g., variants of the PCI standard or the USB standard. In some other embodiments, functions of the transceivers 216, 246, 256, 266, 286 may be split into two or more separate components, or incorporated directly into one or more processors or other components.
The network 290 may be any wired network, wireless network, or combination thereof, and may comprise the Internet in whole or in part. In addition, the network 290 may be a personal area network, local area network, wide area network, cable network, satellite network, cellular telephone network, or combination thereof. The network 290 may also be a publicly accessible network of linked networks, possibly operated by various distinct parties, such as the Internet. In some embodiments, the network 290 may be a private or semi-private network, such as a corporate or university intranet. The network 290 may include one or more wireless networks, such as a Global System for Mobile Communications (GSM) network, a Code Division Multiple Access (CDMA) network, a Long-Term Evolution (LTE) network, or some other type of wireless network. Protocols and components for communicating via the Internet or any of the other aforementioned types of communication networks are well known to those skilled in the art of computer communications and thus, need not be described in more detail herein. Any combination of networks or communications protocols may be utilized in accordance with the systems and methods of the present disclosure. For example, the various components described herein may be configured to communicate via an open or standard protocol such as Wi-Fi. Alternatively, such components may be configured to communicate with one another directly outside of a centralized network, such as the network 290, e.g., by a wireless protocol such as Bluetooth, in which two or more of such components may be paired with one another.
The computers, servers, devices and the like described herein have the necessary electronics, software, memory, storage, databases, firmware, logic/state machines, microprocessors, communication links, displays or other visual or audio user interfaces, printing devices, and any other I/O devices to provide any of the functions or services described herein and/or achieve the results described herein. Also, those of ordinary skill in the pertinent arts will recognize that users of such computers, servers, devices and the like may operate a keyboard, keypad, mouse, stylus, touch screen, or other device (not shown) or method to interact with the computers, servers, devices and the like, or to “select” an item, link, node, hub or any other aspect of the present disclosure.
The unmanned aerial vehicle 210, the personnel 240, the intermediary device 250, the facility 260 and/or the data processing system 280 may use any web-enabled or Internet applications or features, or any other client-server applications or features including electronic mail (or E-mail), or other messaging techniques, to connect to the network 290 or to communicate with one another, such as through short or multimedia messaging service (SMS or MMS) text messages, social network messages, online marketplace messages, telephone calls or the like. For example, the unmanned aerial vehicle 210, the computer device 245, the intermediary device 250, the facility 260 and/or the data processing system 280 may be adapted to transmit information or data in the form of synchronous or asynchronous messages between or among themselves, or between or among any other computer device in real time or in near-real time, or in one or more offline processes, via the network 290. Those of ordinary skill in the pertinent arts would recognize that the unmanned aerial vehicle 210, the computer device 245, the intermediary device 250, the facility 260 and/or the data processing system 280 may operate any of a number of computing devices that are capable of communicating over the network, including but not limited to set-top boxes, personal digital assistants, digital media players, web pads, laptop computers, desktop computers, laptop computers, tablet computers, smartphones, smart speakers, wrist watches, electronic book readers, and the like. The protocols and components for providing communication between such devices are well known to those skilled in the art of computer communications and need not be described in more detail herein.
The data and/or computer-executable instructions, programs, firmware, software and the like (also referred to herein as “computer-executable” components) described herein may be stored on a computer-readable medium that is within or accessible by computers or computer components such as the processors 212, the computer device 245, the intermediary device 250, the facility 260 and/or the data processing system 280, or any other computers or control systems, and having sequences of instructions which, when executed by a processor (e.g., a central processing unit, or “CPU”), cause the processor to perform all or a portion of the functions, services and/or methods described herein. Such computer-executable instructions, programs, software and the like may be loaded into the memory of one or more computers using a drive mechanism associated with the computer readable medium, such as a floppy drive, CD-ROM drive, DVD-ROM drive, network interface, or the like, or via external connections.
Some embodiments of the systems and methods of the present disclosure may also be provided as a computer-executable program product including a non-transitory machine-readable storage medium having stored thereon instructions (in compressed or uncompressed form) that may be used to program a computer (or other electronic device) to perform processes or methods described herein. The machine-readable storage medium may include, but is not limited to, hard drives, floppy diskettes, optical disks, CD-ROMs, DVDs, ROMs, RAMs, erasable programmable ROMs (“EPROM”), electrically erasable programmable ROMs (“EEPROM”), flash memory, magnetic or optical cards, solid-state memory devices, or other types of media/machine-readable medium that may be suitable for storing electronic instructions. Further, embodiments may also be provided as a computer-executable program product that includes a transitory machine-readable signal (in compressed or uncompressed form). Examples of machine-readable signals, whether modulated using a carrier or not, may include, but are not limited to, signals that a computer system or machine hosting or running a computer program can be configured to access, or including signals that may be downloaded through the Internet or other networks.
Referring to
As is shown in
The fuselage 313 comprises a housing or chamber having a shape that is also defined by a plurality of sides (e.g., four sides) and a common height. For example, as is shown in
As is also shown in
The frame 311 and the fuselage 313 are mounted to one another in a manner that causes a geometric center or centroid of a cross-section of the frame 311 to be aligned along a common axis with a geometric center or centroid of a cross-section of the fuselage 313. As is shown in
The time-of-flight sensor module 330-1 may comprise an illuminator or other light source (e.g., a modulated light source) that is configured to transmit light along axes or directions that are normal to, and extend radially outward from, the axis along which the geometric center or centroid of the frame 311 and the geometric center or centroid of the fuselage 313 are coaligned. The time-of-flight sensor module 330-1 is further configured to capture reflections of the light off one or more surfaces. Reflected light captured by the time-of-flight sensor module 330-1 may be interpreted to generate a depth image or range profile of distances between the time-of-flight sensor module 330-1, and the one or more surfaces, several times per second.
In some embodiments, the time-of-flight sensor module 330-1 may be configured to rotate an illuminator, or the axis or the direction along which the time-of-flight sensor module 330-1 transmits light, about the axis along with the geometric center or centroid of the frame 311 and the geometric center or centroid of the fuselage 313 are coaligned. By rotating the illuminator or the transmissions of light about the axis along with the geometric center or centroid of the frame 311, and the geometric center or centroid of the fuselage 313 are coaligned, the time-of-flight sensor module 330-1 may be used to generate depth images, range profiles or other sets of distances covering three hundred sixty degrees around the aerial vehicle 310.
The time-of-flight sensors 330-2, 330-3 also include illuminators or other light sources (e.g., modulated light sources) that are configured to transmit light along axes that are parallel to the axis along which the geometric center or centroid of the frame 311 and the geometric center or centroid of the fuselage 313 are coaligned, and in opposite directions, e.g., up and down, with respect to the orientation of the aerial vehicle 310 as shown in
The aerial vehicle 310 includes a visual camera 330-4 or other imaging device embedded or installed within the housing or chamber defined by the fuselage 313. The visual camera 330-4 has a lens and an image sensor defining a field of view extending normal to one of the sides of the fuselage 313. Alternatively, the aerial vehicle may include any number of the visual cameras 330-4, which may be provided on the same side of the fuselage 313, or on different sides of the fuselage 313. In some embodiments, the aerial vehicle 310 may include at least one visual camera 330-4 provided on each of the sides of the fuselage 313, thereby covering three hundred sixty degrees around the aerial vehicle 310. Alternatively, in some other embodiments, one or more visual cameras 330-4 may be mounted in association with the frame 311 or in any other location on the aerial vehicle 310. The housing or chamber defined by the fuselage 313 may further include any number of other components therein, including but not limited to processors, control systems, memory components, batteries or other power sources, transceivers, circuitry, or other sensors.
As is shown in
As is also shown in
As is also shown in
As is further shown in
In accordance with embodiments of the present disclosure, the top cover 315-1 and the bottom cover 315-2 may be mounted to the upper and lower edges of the frame 311 in any manner, such as by clips, screws, bolts, snap-fit connections, or any other features. Alternatively, or additionally, the covers 315-1, 315-2 may be mounted to the fuselage 313, the struts 317, the propulsion motors 325, the time-of-flight sensor modules 330-1, 330-2, 330-3 or any other portion of the aerial vehicle 310 in any manner. Moreover, as is further shown in
As is further shown in
Furthermore, the frame 311, the fuselage 313, the covers 315-1, 315-2 and the struts 317, or external portions of housings of the propulsion motors 325, or any other components of the aerial vehicle 310, may be formed as single pieces, or as two or more pieces, that may be joined together or combined to form such components. For example, as is shown in
In some embodiments, the top cover 315-1, the bottom cover 315-2 and one or more portions of the fuselage 313 may be mated together in a manner that defines a cavity or volume that includes the propulsion motors 325 and any rotating propellers therein. For example, as is shown in
The unmanned aerial vehicles of the present disclosure may be formed from materials of any type or form. For example, in some embodiments, one or more of the frame 311, the fuselage 313, the covers 315-1, 315-2 and the struts 317, or external portions of housings of the propulsion motors 325, may be formed from one or more polycarbonates, or from one or more styrenes, e.g., polystyrenes or acrylonitrile butadiene styrenes (or “ABS”), or blends thereof, including but not limited to blends of polycarbonates and ABS. Alternatively, or additionally, one or more of the frame 311, the fuselage 313, the covers 315-1, 315-2 and the struts 317, or external portions of housings of the propulsion motors 325, may be formed from any other lightweight, durable materials such as plastics (e.g., thermosetting plastics such as epoxy or phenolic resins, polyurethanes or polyesters, as well as polyethylenes, polypropylenes or polyvinyl chlorides, and also recycled plastics), wood (e.g., woods with sufficient strength properties such as ash), metals (e.g., lightweight metals such as aluminum, or metals of heavier weights including alloys of steel), composites (e.g., carbon fiber), rubbers, or any other combinations of materials.
Aerial vehicles of the present disclosure may be operated in any manner to capture information or data, e.g., distances or ranges to surfaces of objects above, below or around the aerial vehicles, as well as images of their surroundings, or any other information or data. Referring to
As is shown in
The range sensor 430-1 extends above the aerial vehicle 410 and is configured to transmit light on axes or directions that may rotate at any angular velocity ω, such as ten revolutions per second, relative to the fuselage 413. The range sensors 430-2, 430-3 are configured to transmit light in fixed axes or directions above and below the aerial vehicle 410, respectively. The range sensor 430-4 extends radially outward from the fuselage 413, and is configured to transmit light on a fixed axis or direction relative to the fuselage 413. In some implementations, one or more of the range sensors 430-1, 430-2, 430-3, 430-4 may be or include additional sensors or components. Alternatively, one or more of the range sensors 430-1, 430-2, 430-3, 430-4 may be replaced by other sensors or components.
In some implementations, fields of view of the range sensors 430-2, 430-3, 430-4 may define any angles with respect to their axes of orientation. For example, in some implementations, the fields of view may extend from the respective range sensors 430-2, 430-3, 430-4 at angles of twenty to thirty degrees on either side of their respective axes of orientation. The range sensors 430-2, 430-3, 430-4 may thus define image planes in the shapes of squares having sides of approximately sixteen centimeters (16 cm) each at a distance of twenty centimeters (20 cm) from the respective sensors, or sides of approximately twenty-eight centimeters (28 cm) each at a distance of thirty-five centimeters (35 cm) from the respective sensors. Alternatively, the sensors 430-2, 430-3, 430-4 may define fields of view having any other angles, and with any other dimensions, in accordance with implementations of the present disclosure.
Reflections of light captured by the range sensors 430-1, 430-2, 430-3, 430-4 may be interpreted to construct depth images, range profiles or other sets of distances between the range sensors 430-1, 430-2, 430-3, 430-4 and one or more surfaces above, below or around the aerial vehicle 410, or forward of the aerial vehicle 410, several times per second.
Thus, as is shown in
As is discussed above, an unmanned aerial vehicle may be programmed or configured to calculate a trajectory for traveling between various waypoints (or spatial points) within indoor spaces, and to minimize snap of the aerial vehicle along the trajectory. Referring to
At box 510, an unmanned aerial vehicle (or “UAV”) is programmed with n waypoints for travel within one or more indoor spaces, where a value of n is greater than two. The n waypoints may be represented in any manner, e.g., by waypoint data or spatial point data including one or more sets of coordinates in three-dimensional space, and may be associated with any mission to be executed by unmanned aerial vehicles within the indoor spaces in general, or by the unmanned aerial vehicle in particular.
At box 515, a value of a step variable i is set equal to one, or i=1. At box 520, the unmanned aerial vehicle departs from waypoint i toward waypoint i+1. For example, the unmanned aerial vehicle may execute any number of commands for operating one or more motors, control surfaces or other systems to cause the unmanned aerial vehicle to depart from a position in three-dimensional space corresponding to the waypoint i, on a desired course, at a desired speed or at desired altitude, toward the waypoint i+1.
At box 525, whether a distance between the waypoint i and the waypoint i+1 is greater than a sum of a minimum acceleration distance for the unmanned aerial vehicle and a minimum deceleration distance for the unmanned aerial vehicle is determined.
If the distance between the waypoint i and the waypoint i+1 is not greater than the sum of a minimum acceleration distance for the unmanned aerial vehicle and a maximum deceleration distance, then the process advances to box 530, where the unmanned aerial vehicle calculates a trajectory from the waypoint i to the waypoint i+2 through the waypoint i+1 to minimize snap at a safe speed. Because there is insufficient distance for the unmanned aerial vehicle to safely accelerate from a velocity of zero at the waypoint i to a maximum velocity of the unmanned aerial vehicle and to decelerate from the maximum velocity to a velocity of zero at the waypoint i+1, the unmanned aerial vehicle may calculate a trajectory that calls for travel at a safe speed, or one or more safe speeds, between the waypoint i and the waypoint i+1, beginning from a velocity of zero at the waypoint i and ending at a velocity of zero at the waypoint i+1.
If the distance between the waypoint i and the waypoint i+1 is greater than the sum of a minimum acceleration distance for the unmanned aerial vehicle and a maximum deceleration distance, then the process advances to box 535, where the unmanned aerial vehicle selects a first intervening waypoint and a second intervening waypoint between the waypoint i and the waypoint i+1. In some implementations, the first intervening waypoint may be located at the minimum acceleration distance from the waypoint i, and the second intervening waypoint may be located at the minimum deceleration distance from the waypoint i+1. Therefore, the unmanned aerial vehicle may safely accelerate from a velocity of zero at the waypoint i to a maximum velocity at the first intervening waypoint, and may safely decelerate from the maximum velocity at the second intervening waypoint to a velocity of zero at the waypoint i+1, subject to any physical constraints.
At box 540, the unmanned aerial vehicle calculates a trajectory from the waypoint i to the waypoint i+2 via the first intervening waypoint, the second intervening waypoint and the waypoint i+1 to minimize snap of the unmanned aerial vehicle, at a maximum speed from the first intervening waypoint to the second intervening waypoint.
At box 545, the unmanned aerial vehicle transmits one or more commands for causing the unmanned aerial vehicle to travel on the calculated trajectory, e.g., the trajectory calculated at box 535 or the trajectory calculated at box 540, and at one or more selected speeds. In some implementations, the unmanned aerial vehicle may generate commands or instructions at any rate or frequency, e.g., ten times per second, or at ten Hertz (10 Hz), and execute such commands or instructions to operate one or more motors or control surfaces accordingly.
At box 550, whether the unmanned aerial vehicle has reached the waypoint i+1 is determined. If the unmanned aerial vehicle has yet to reach the waypoint i+1, then the process returns to box 545, where the unmanned aerial vehicle continues to transmit one or more commands for traveling on the calculated trajectory.
If the unmanned aerial vehicle has reached the waypoint i+1, then the process advances to box 555, where whether a sum of the step variable i and 2 equals the number n, or whether i+2=n. For example, if i+2=n, then only two waypoints remain for the unmanned aerial vehicle to travel within the indoor spaces. If the sum of the step variable i and 2 does not equal the number n, meaning that the unmanned aerial vehicle must travel through more than two waypoints to complete its travel within the indoor spaces, then the process advances to box 560, where the value of the step variable i is set equal to i+1, or i=i+1, before returning to box 520, where the unmanned aerial vehicle departs from waypoint i toward waypoint i+1.
If the sum of the step variable i and 2 equals the number n, then the process advances to box 565, where the unmanned aerial vehicle departs from waypoint i+1 toward waypoint n, and the process ends.
As is discussed above, an unmanned aerial vehicle traveling on a trajectory may modify its speed, and recalculate a trajectory as necessary, based on a level of risk that the unmanned aerial vehicle will contact one or more obstacles. Referring to
At box 610, a value of a step variable i is set equal to one, or i=1. At box 620, a module provided aboard an unmanned aerial vehicle (or “UAV”) calculates a trajectory for the unmanned aerial vehicle to travel in a low-risk state from a waypoint i to a waypoint i+1 of n waypoints (or spatial points). The trajectory may be calculated according to one or more formulas for minimizing snap of the unmanned aerial vehicle, e.g., the drone trajectory equation of
The low-risk state may be one of a plurality of states of the unmanned aerial vehicle that are defined as functional limits on a safe speed of the unmanned aerial vehicle. For example, in some implementations, where sensors provided aboard the unmanned aerial vehicle (e.g., time-of-flight sensors, LIDAR sensors, cameras or other imaging devices) have not detected any obstacles within a predetermined distance or range, the unmanned aerial vehicle may be deemed to be at a low risk of coming into contact with any obstacles. In the low-risk state, the unmanned aerial vehicle may be permitted to travel at or near a maximum speed, which may be defined subject to any constraints on the unmanned aerial vehicle. In some other implementations, where the sensors detect one or more obstacles within the predetermined distance or range, the unmanned aerial vehicle may be deemed to be at a high risk of coming into contact with any of the obstacles. In the high-risk state, the unmanned aerial vehicle may then be permitted to travel at a substantially lower speed, which may be a fraction of the maximum speed, in order to provide the unmanned aerial vehicle with sufficient time to take adequate actions in response to detections of such obstacles. In the high-risk state, the unmanned aerial vehicle may also begin searching for obstacles within another predetermined distance or range, which may be shorter than the predetermined distance or range by which the one or more obstacles were originally detected. Furthermore, where the sensors determine that a collision with one or more of the obstacles is likely or imminent, the unmanned aerial vehicle may automatically execute one or more braking evolutions, in the imminent-collision state.
At box 630, the unmanned aerial vehicle travels on the trajectory calculated at box 620 in the low-risk state while scanning for objects using one or more onboard sensors. For example, the unmanned aerial vehicle may generate commands or instructions at any rate or frequency, e.g., ten times per second, or at ten Hertz (10 Hz), and execute such commands or instructions for operating motors, control surfaces or other components to cause the unmanned aerial vehicle to remain on the trajectory accordingly. Referring again to
At box 640, whether the unmanned aerial vehicle has detected any objects within a first threshold distance is determined. The unmanned aerial vehicle may detect an object based on points, returns or detections received from one or more time-of-flight sensors or LIDAR sensors while traveling on the trajectory calculated at box 620, and may process the points, returns or detections to determine whether such points, returns or detections are of sufficiently high confidence, or are otherwise reliable indications of an object within the first threshold distance, which may be approximately one meter (1 m), or one hundred centimeters (100 cm), or any other distance.
In some implementations, the unmanned aerial vehicle may construct a local map having a grid of a plurality of cells, and may count numbers of points, returns or detections received from one or more sensors in each of such cells during a scan by one or more of the sensors. If the points, returns or detections in a cell exceed a threshold and are both of sufficiently high confidence, and also consistent with points, returns or detections in neighboring cells, the cell may be deemed to be obstructed, or non-empty. If such points, returns or detections do not exceed the threshold, are not of sufficiently high confidence, or are inconsistent with points, returns or detections in any neighboring cells, the cell may be deemed to be unobstructed, or empty. The points, returns or detections may be processed to determine whether the unmanned aerial vehicle has detected any objects at any rate or frequency, e.g., ten hertz (10 Hz), or ten times per second, or at any other rate or frequency. Moreover, where multiple sensors capture information or data representing distances to any surrounding objects, the information or data may be time-stamped, and synchronized based on such time stamps, such that information or data captured using multiple sensors may be collectively processed to determine whether such sensors have detected any objects. Furthermore, multiple scans at different times (e.g., consecutive scans) may also be collectively processed to determine whether such sensors have detected any objects.
In some implementations, a range sensor (e.g., a LIDAR sensor, or a time-of-flight sensor) may continuously or repeatedly estimate a position of the unmanned aerial vehicle, and establish a map (e.g., an environment map) of an indoor space in which the unmanned aerial vehicle travels. For example, where a pitch or a roll of the unmanned aerial vehicle is non-zero, polar coordinates representing returns received by a range sensor may be converted, as necessary, to Cartesian coordinates in a horizontal plane using an estimated pitch or roll angle, which may be determined by one or more onboard sensors (e.g., inertial measurement unit sensors). Distances from positions of the unmanned aerial vehicle to objects may be calculated based on such returns, as necessary, and a two-dimensional local map of an environment that includes the distances from various positions of the unmanned aerial vehicle may be constructed accordingly.
If the unmanned aerial vehicle does not detect any objects within the first threshold distance, then the process advances to box 642, where whether the unmanned aerial vehicle has arrived at the final waypoint, viz., waypoint n, is determined. If the unmanned aerial vehicle has arrived at the final waypoint, then the process ends. If the unmanned aerial vehicle has not arrived at the final waypoint, then the process advances to box 644, where whether the unmanned aerial vehicle has arrived at the waypoint i+1, viz., a next waypoint, is determined. If the unmanned aerial vehicle has not arrived at the waypoint i+1, then the process returns to box 630, where the unmanned aerial vehicle executes one or more commands for causing the unmanned aerial vehicle to travel on the trajectory calculated at box 620 in the low-risk state, and to scan for objects using one or more onboard sensors. If the unmanned aerial vehicle has arrived at the waypoint i+1, then the process advances to box 646, where the value of the step variable i is incremented by one, or is set to equal i+1, before returning to box 620, where the module calculates a trajectory for the unmanned aerial vehicle to travel in a low-risk state from the waypoint i to a next waypoint of the n waypoints, viz., waypoint i+1.
If the unmanned aerial vehicle detects one or more objects within the first threshold distance, then the process advances to box 650, where the module updates the trajectory for the unmanned aerial vehicle to travel in a high-risk state to the waypoint i+1. For example, the high-risk state may have a maximum velocity that is significantly less than the maximum velocity of the unmanned aerial vehicle subject to the physical constraints, e.g., a fraction of the maximum speed. In some implementations, where the unmanned aerial vehicle has a maximum speed of one meter per second (1 m/s) in the low-risk state, the unmanned aerial vehicle may have a maximum speed of approximately 0.3 to 0.5 meters per second (0.3-0.5 m/s) in the high-risk state. Alternatively, the unmanned aerial vehicle may be programmed or configured with any other maximum speeds in the low-risk state, the high-risk state, or any other state.
Moreover, where the maximum speed available to the unmanned aerial vehicle is reduced upon transitioning to the high-risk state, a new trajectory for traveling through the waypoint i+1 may be calculated accordingly.
At box 655, the unmanned aerial vehicle travels on the updated trajectory calculated at box 650 and in the high-risk state while scanning for one or more objects using the onboard sensors.
At box 660, whether the unmanned aerial vehicle has detected any objects within a second threshold distance, which may be shorter than the first threshold distance, is determined. For example, where the first threshold distance is approximately one meter (1 m), or one hundred centimeters (100 cm), the second threshold distance may be approximately 0.3 meters (0.3 m), or thirty centimeters (30 cm). Alternatively, the first threshold distance and the second threshold distance may have any lengths in accordance with implementations of the present disclosure.
In some implementations, the unmanned aerial vehicle may compensate for any motion of the unmanned aerial vehicle between a detection of an object within the first threshold distance at box 640, and any subsequent scans to determine whether any objects are present within the second threshold distance at box 655. For example, a latency distance may be calculated based on a speed of the unmanned aerial vehicle, a position of the unmanned aerial vehicle at a time when the object was detected within the first threshold distance at box 640, and a time at which a scan to determine whether any objects are present within the second threshold distance at box 655 is conducted. A position of the unmanned aerial vehicle in the future may be calculated or estimated based on the latency distance.
If the unmanned aerial vehicle does not detect any objects within the second threshold distance, then the process advances to box 662, where whether the unmanned aerial vehicle has arrived at the final waypoint, viz., waypoint n, is determined. If the unmanned aerial vehicle has arrived at the final waypoint, then the process ends. If the unmanned aerial vehicle has not arrived at the final waypoint, then the process advances to box 664, where whether the unmanned aerial vehicle has arrived at the waypoint i+1, viz., a next waypoint, is determined. If the unmanned aerial vehicle has not arrived at the waypoint i+1, then the process returns to box 640, where whether the unmanned aerial vehicle has detected any objects within the first threshold distance is determined. If the unmanned aerial vehicle has arrived at the waypoint i+1, then the process advances to box 666, where the value of the step variable i is incremented by one, or is set to equal i+1, before returning to box 620, where the module calculates a trajectory for the unmanned aerial vehicle to travel in a low-risk state from the waypoint i to a next waypoint of the n waypoints, viz., waypoint i+1.
If the unmanned aerial vehicle detects one or more objects within the second threshold distance, thereby indicating that a collision with one or more obstacles is likely or imminent, then the process advances to box 670, where the unmanned aerial vehicle executes commands for performing an emergency braking maneuver, and the process ends. For example, in some implementations, the unmanned aerial vehicle may insert an intervening waypoint immediately behind the unmanned aerial vehicle and calculate a new trajectory that calls for traveling through the intervening waypoint. Alternatively, the unmanned aerial vehicle may be programmed or configured with any other commands or instructions for responding to a detection of an object within the second threshold distance, e.g., returning to the waypoint i−1, changing course to turn away from the object, or taking any other actions.
Referring to
As is shown in
The unmanned aerial vehicle 710 includes one or more range sensors, e.g., time-of-flight sensors, LIDAR sensors, imaging devices, or others. The unmanned aerial vehicle 710 may capture information or data using such sensors, and continuously or repeatedly determine whether any objects are within a predetermined range (or distance) D1 forward of the unmanned aerial vehicle 710, e.g., within a sector having an arc subtended by an angle θ on either side of the direction β, e.g., a detection area or a detection zone. The angle θ may have any value and may be selected on any basis, e.g., a field of view of any of such sensors. In some implementations, the angle θ may have a value of approximately twenty to thirty degrees (25° to 30°). In some implementations, a value of the angle θ may be defined based on the predetermined range D1, as well as a maximum width of the unmanned aerial vehicle 710 subject to the direction β, in order to ensure that any objects forward of the unmanned aerial vehicle 710 that may come into contact with the unmanned aerial vehicle 710 while traveling in the direction β and at the speed V1 are detected by such sensors. As is shown in
As is shown in
As is shown in
As is shown in
Referring to
As is shown in
The unmanned aerial vehicle 810 is outfitted or equipped with one or more range sensors for continuously or repeatedly determining whether any obstacles are present forward of the unmanned aerial vehicle 810, or otherwise in a direction of travel of the unmanned aerial vehicle 810, e.g., within a predetermined range or distance, and within a sector having an arc defined by an angle on either side of the direction of travel, such as a detection area or a detection zone, as well as whether any of such objects poses a risk of collision to the unmanned aerial vehicle 810. The predetermined range or distance or the angle may have any dimension, and may be selected on any basis, such as an operating range of one or more sensors, a minimum distance required for the unmanned aerial vehicle to decelerate or change course upon detecting an obstacle, or any other factors.
In some implementations, a speed of the unmanned aerial vehicle 810 may be selected based on a state of the unmanned aerial vehicle 810, or a level of risk to the unmanned aerial vehicle 810. For example, where the unmanned aerial vehicle 810 does not detect any obstacles within the predetermined range or distance and within the sector, the unmanned aerial vehicle 810 may be deemed to be in a low-risk state, and may travel at a maximum speed V1 between two or more waypoints.
As is shown in
While traveling at the speed V2, the unmanned aerial vehicle 810 may continuously or repeatedly monitor for any obstacles that may be present forward of the unmanned aerial vehicle 810, or in a direction of travel of the unmanned aerial vehicle 810, at a predetermined range or distance that may be smaller than the predetermined range or distance at which the edge or the side of either of the structural features 875-1, 875-2 defining the opening 874 was originally detected. The predetermined range or distance or an angle defining an arc of a sector on either side of a direction of travel of the unmanned aerial vehicle may be selected on any basis, e.g., a minimum distance required for the unmanned aerial vehicle to decelerate to a velocity of zero or execute an emergency braking maneuver, or any other factors. The unmanned aerial vehicle 810 may continue to travel at the speed V2 until no obstacles are detected forward of the unmanned aerial vehicle 810, or otherwise within a direction of travel of the unmanned aerial vehicle 810, or until any such obstacles are determined to not pose a risk of collision to the unmanned aerial vehicle 810.
Subsequently, upon determining that the unmanned aerial vehicle 810 is no longer at risk of colliding with edges or sides of the opening 874 or any other obstacles, the unmanned aerial vehicle 810 may calculate a new trajectory, limited only by the maximum speed V1, and may travel along the new trajectory through the waypoint C to the waypoint D.
Referring to
As is shown in
In some implementations, the range sensor 930-1 may be a LIDAR sensor that is configured to calculate distances to objects at an angular range of three hundred sixty degrees about the range sensor 930-1, and at any maximum measuring radius, e.g., twelve meters (12 m) or more. For example, in some implementations, the range sensor 930-1 may be configured to transmit light at any measurement frequency, e.g., up to 4,500 Hertz (or 4,500 measurements per second). The transmitted light may be infrared light, or light at any other wavelength or frequency. In some implementations, the range sensor 930-1 may transmit light in a single direction, and capture or receive reflections of the light from one or more objects. A difference between a time at which light is transmitted, and a time at which reflections of the light are received, is commonly called a “time-of-flight,” and may be used with the speed of light to calculate distances to objects from which the light was reflected. In some implementations, the range sensor 930-1 may be configured to emit light at a wavelength of approximately 905 nanometers, e.g., within an infrared band, and at a power of approximately twenty-five milliwatts (25 mW).
The range sensor 930-1 may further combine distances calculated based on times-of-flight with information regarding angles at which the light was emitted and received to generate a point cloud or another representation of positions of objects, which may be stored by the unmanned aerial vehicle 910 and processed or transmitted to one or more external devices or systems for processing. The range sensor 930-1 may also include one or more motor drivers or other components for controlling a start, a stop or a speed of a motor, and may generate and transmit packets of data including any information regarding transmissions or returns, e.g., rotational speeds, start or end angles, time stamps, or other related data.
As is also shown in
As is shown in
The unmanned aerial vehicle 910 may be configured to capture information or data using the range sensors 930-1, 930-2 while traveling within the facility 960. As is further shown in
As is further shown in
As is shown in
In some other implementations, a position or an orientation of the unmanned aerial vehicle 910 may be determined based on information or data captured by one or more other sensors, e.g., the range sensors 930-1, 930-2, which may detect one or more objects having known positions within the facility 960, e.g., according to a local or global coordinate system, and may determine a position or an orientation of the unmanned aerial vehicle 910 with respect to such objects.
The unmanned aerial vehicle 910 may capture information or data using such sensors, e.g., the range sensors 930-1, 930-2, and determine whether any objects are within a detection area or a detection zone defined by a predetermined range or distance forward of the unmanned aerial vehicle 910, and within an arc or sector that has a radius of the predetermined range or distance and subtends an angle on either side of the flight direction of approximately twenty to thirty degrees, or any other angle. For example, as is shown in
The range sensor 930-1 may be configured to transmit and receive light at regular intervals about the one or more principal axes. For example, as is shown in
In some implementations, the predetermined range D may be approximately one meter (1 m), or one hundred centimeters (100 cm), where no objects have been detected forward of the unmanned aerial vehicle 910, or approximately 0.3 to 0.5 meters (0.3-0.5 m), or thirty to fifty centimeters (30-50 cm), where one or more objects have been detected forward of the unmanned aerial vehicle 910. Alternatively, the predetermined range D may be defined by one or more limitations of the range sensor 930-1.
As is shown in
As is shown in
Thus, where the number of the points Cij calculated for the cell 935-ij exceeds a threshold K, where the confidence score γij in the number of the points Cy exceeds a threshold T, and where the number of the points Cij is consistent with numbers of points of one or more neighboring cells, the cell 935-ij may be determined to be non-empty (or obstructed), and an object may be determined to be within the field of view FOV2. Conversely, if the cell 935-ij does not exceed the threshold K, if the confidence score γij in the number of the points Cy does not exceed the threshold T, or if the number of the points Cij is inconsistent with each of the numbers of points of neighboring cells, the cell 935-ij may be determined to be empty (or unobstructed), and the field of view FOV2. may be determined to be free of objects within a predetermined distance D. The unmanned aerial vehicle 910 may be determined to be at risk of collision where any number of the cells 935-n, viz., one or more, is determined to be non-empty (or obstructed).
As is shown in
Upon detecting the temporary obstacle 975, a position of the temporary obstacle 975 in three-dimensional space may be determined, e.g., based on the navigation map 965, or in any other manner, and stored in one or more data stores. In some implementations, the position of the temporary obstacle 975 may be determined based on times associated with detections of the temporary obstacle 975 by the range sensor 930-1 and the range sensor 930-2, respectively. For example, a two-dimensional point cloud or other representation determined by the range sensor 930-1 may be fused or combined with a three-dimensional depth image or other representation determined by the range sensor 930-2, to determine a position in three-dimensional space of the temporary obstacle 975, where a pose (e.g., a position or an orientation) of the unmanned aerial vehicle 910 are known.
Accordingly, the unmanned aerial vehicle 910 may execute one or more braking maneuvers, calculate a new trajectory for the unmanned aerial vehicle 910, or take any other actions.
In accordance with one or more preferred implementations, an unmanned aerial vehicle determines a yaw adjustment plan for a flight from a first waypoint to a second waypoint separate from determination of a translation plan (e.g., a translation plan determined based on a calculated trajectory). Such a yaw adjustment plan may be determined based on (i) a calculated trajectory or (ii) pose/yaw information for waypoints stored as part of path or waypoint data. For example, waypoint data for a first waypoint may include an indication that, at the first waypoint, the unmanned aerial vehicle should have a particular yaw angle with respect to a particular point of reference or coordinate system. As another example, trajectory data for a first waypoint may include an indication that, at the first waypoint, the unmanned aerial vehicle should have a particular yaw angle with respect to a particular point of reference or coordinate system. In accordance with one or more preferred implementations, a desired yaw value for a waypoint is determined based on spatial data for a next waypoint.
In some implementations, where a calculated trajectory or yaw adjustment plan calls for a change in yaw of an unmanned aerial vehicle between a pair of waypoints, an estimated time for achieving the change in yaw may be calculated based on a maximum yaw velocity of the unmanned aerial vehicle, and compared to an estimated time required to translate between the pair of waypoints according to a calculated trajectory.
For example, in accordance with one or more preferred implementations, where an estimated time for achieving a change in yaw is greater than an estimated time required to translate between a pair of waypoints according to a calculated trajectory, then two-point path planning for an unmanned aerial vehicle to travel from a first waypoint of the pair to a second waypoint of the pair is utilized. Once the unmanned aerial vehicle reaches the second waypoint, the unmanned aerial vehicle may pause its translation to complete a required yaw rotation, or, alternatively, continue onward in accordance with a calculated trajectory. Commands or instructions for causing the unmanned aerial vehicle to translate along the trajectory and effect a yaw rotation may be generated and sent to a flight controller separately or together.
In accordance with one or more preferred implementations, where the estimated time for achieving the change in yaw is less than the estimated time required to translate between the pair of waypoints according to the calculated trajectory, however, an intervening waypoint is inserted between the pair of waypoints, at a distance from the second waypoint that is sufficient to allow the unmanned aerial vehicle to complete the yaw rotation during its flight from the intervening waypoint to the second waypoint. During flight, yaw rotation may begin when the unmanned aerial vehicle reaches the intervening waypoint. Alternatively, in accordance with one or more preferred implementations, where the estimated time for achieving the change in yaw is less than the estimated time required to translate between the pair of waypoints according to the calculated trajectory, an intervening waypoint is inserted between the pair of waypoints, based on a determined point that is a distance from the first waypoint sufficient to allow the unmanned aerial vehicle to complete its yaw rotation during its flight from the first waypoint to the intervening waypoint. During flight, yaw rotation may begin at the first waypoint and ends when the unmanned aerial vehicle reaches the intervening waypoint. Commands or instructions for causing the unmanned aerial vehicle to translate along the trajectory and effect yaw rotation may be generated and sent to a flight controller separately or together.
The contents of U.S. patent application Ser. Nos. 16/584,721 and 17/029,688, and International Patent Application No. PCT/US2020/052268, are incorporated by reference herein in their entireties.
Although some embodiments of the present disclosure show the use of unmanned aerial vehicles in support of one or more applications or functions at a facility such as a home or a like structure, those of ordinary skill in the pertinent arts will realize that the systems and methods of the present disclosure are not so limited. Rather, the systems and methods of the present disclosure may be utilized in connection with any facility, including but not limited to homes, in support of any type of application or function.
It should be understood that, unless otherwise explicitly or implicitly indicated herein, any of the features, characteristics, alternatives or modifications described regarding a particular embodiment herein may also be applied, used, or incorporated with any other embodiment described herein, and that the drawings and detailed description of the present disclosure are intended to cover all modifications, equivalents and alternatives to the various embodiments as defined by the appended claims. Moreover, with respect to the one or more methods or processes of the present disclosure described herein, including but not limited to the flow charts shown in
Conditional language, such as, among others, “can,” “could,” “might,” or “may,” unless specifically stated otherwise, or otherwise understood within the context as used, is generally intended to convey in a permissive manner that certain embodiments could include, or have the potential to include, but do not mandate or require, certain features, elements and/or steps. In a similar manner, terms such as “include,” “including” and “includes” are generally intended to mean “including, but not limited to.” Thus, such conditional language is not generally intended to imply that features, elements and/or steps are in any way required for one or more embodiments or that one or more embodiments necessarily include logic for deciding, with or without user input or prompting, whether these features, elements and/or steps are included or are to be performed in any particular embodiment.
The elements of a method, process, or algorithm described in connection with the embodiments disclosed herein can be embodied directly in hardware, in a software module stored in one or more memory devices and executed by one or more processors, or in a combination of the two. A software module can reside in RAM, flash memory, ROM, EPROM, EEPROM, registers, a hard disk, a removable disk, a CD-ROM, a DVD-ROM or any other form of non-transitory computer-readable storage medium, media, or physical computer storage known in the art. An example storage medium can be coupled to the processor such that the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium can be integral to the processor. The storage medium can be volatile or nonvolatile. The processor and the storage medium can reside in an ASIC. The ASIC can reside in a user terminal. In the alternative, the processor and the storage medium can reside as discrete components in a user terminal.
Disjunctive language such as the phrase “at least one of X, Y, or Z,” or “at least one of X, Y and Z,” unless specifically stated otherwise, is otherwise understood with the context as used in general to present that an item, term, etc., may be either X, Y, or Z, or any combination thereof (e.g., X, Y, and/or Z). Thus, such disjunctive language is not generally intended to, and should not, imply that certain embodiments require at least one of X, at least one of Y, or at least one of Z to each be present.
Unless otherwise explicitly stated, articles such as “a” or “an” should generally be interpreted to include one or more described items. Accordingly, phrases such as “a device configured to” are intended to include one or more recited devices. Such one or more recited devices can also be collectively configured to carry out the stated recitations. For example, “a processor configured to carry out recitations A, B and C” can include a first processor configured to carry out recitation A working in conjunction with a second processor configured to carry out recitations B and C.
Language of degree used herein, such as the terms “about,” “approximately,” “generally,” “nearly” or “substantially” as used herein, represent a value, amount, or characteristic close to the stated value, amount, or characteristic that still performs a desired function or achieves a desired result. For example, the terms “about,” “approximately,” “generally,” “nearly” or “substantially” may refer to an amount that is within less than 10% of, within less than 5% of, within less than 1% of, within less than 0.1% of, and within less than 0.01% of the stated amount.
Although the invention has been described and illustrated with respect to illustrative embodiments thereof, the foregoing and various other additions and omissions may be made therein and thereto without departing from the spirit and scope of the present disclosure.
| Number | Name | Date | Kind |
|---|---|---|---|
| 3417729 | Gilday et al. | Dec 1968 | A |
| 3575527 | Sumitani et al. | Apr 1971 | A |
| 3805723 | Bernaerts | Apr 1974 | A |
| 4865248 | Barth | Sep 1989 | A |
| 4954962 | Evans, Jr. et al. | Sep 1990 | A |
| 5040116 | Evans, Jr. et al. | Aug 1991 | A |
| 5283739 | Summerville et al. | Feb 1994 | A |
| 5371581 | Wangler et al. | Dec 1994 | A |
| 5386462 | Schlamp | Jan 1995 | A |
| 5452374 | Cullen et al. | Sep 1995 | A |
| 5497236 | Wolff et al. | Mar 1996 | A |
| 5731884 | Inoue | Mar 1998 | A |
| 5847522 | Barba | Dec 1998 | A |
| 5901253 | Tretter | May 1999 | A |
| 5995898 | Tuttle | Nov 1999 | A |
| 6031612 | Shirley | Feb 2000 | A |
| 6266577 | Popp et al. | Jul 2001 | B1 |
| 6344796 | Ogilvie et al. | Feb 2002 | B1 |
| 6374155 | Wallach et al. | Apr 2002 | B1 |
| 6426699 | Porter | Jul 2002 | B1 |
| 6507670 | Moed | Jan 2003 | B1 |
| 6543983 | Felder et al. | Apr 2003 | B1 |
| 6636781 | Shen et al. | Oct 2003 | B1 |
| 6676460 | Motsenbocker | Jan 2004 | B1 |
| 6690997 | Rivalto | Feb 2004 | B2 |
| 6694217 | Bloom | Feb 2004 | B2 |
| 6705523 | Stamm et al. | Mar 2004 | B1 |
| 6804607 | Wood | Oct 2004 | B1 |
| 6919803 | Breed | Jul 2005 | B2 |
| 6954290 | Braudaway et al. | Oct 2005 | B1 |
| 6961711 | Chee | Nov 2005 | B1 |
| 6965440 | Nakagiri et al. | Nov 2005 | B1 |
| 6970838 | Kamath et al. | Nov 2005 | B1 |
| 7006952 | Matsumoto et al. | Feb 2006 | B1 |
| 7016536 | Ling et al. | Mar 2006 | B1 |
| 7031519 | Elmenhurst | Apr 2006 | B2 |
| 7129817 | Yamagishi | Oct 2006 | B2 |
| 7133743 | Tilles et al. | Nov 2006 | B2 |
| 7145699 | Dolan | Dec 2006 | B2 |
| 7149611 | Beck et al. | Dec 2006 | B2 |
| 7171879 | Gass et al. | Feb 2007 | B2 |
| 7188513 | Wilson | Mar 2007 | B2 |
| 7335071 | Motsenbocker | Feb 2008 | B1 |
| 7337686 | Sagi-Dolev | Mar 2008 | B2 |
| 7337944 | Devar | Mar 2008 | B2 |
| 7339993 | Brooks et al. | Mar 2008 | B1 |
| 7459880 | Rosen | Dec 2008 | B1 |
| 7639386 | Siegel et al. | Dec 2009 | B1 |
| 7668404 | Adams et al. | Feb 2010 | B2 |
| 7673831 | Steele et al. | Mar 2010 | B2 |
| 7685953 | Giles | Mar 2010 | B2 |
| 7693745 | Pomerantz et al. | Apr 2010 | B1 |
| 7894939 | Zini et al. | Feb 2011 | B2 |
| 7925375 | Schininger et al. | Apr 2011 | B2 |
| 7946526 | Zimet | May 2011 | B2 |
| 7946530 | Talmage, Jr. | May 2011 | B1 |
| 7966093 | Zhuk | Jun 2011 | B2 |
| 8015023 | Lee et al. | Sep 2011 | B1 |
| 8078317 | Allinson et al. | Dec 2011 | B2 |
| 8126642 | Trepagnier et al. | Feb 2012 | B2 |
| 8131607 | Park et al. | Mar 2012 | B2 |
| 8145351 | Schininger et al. | Mar 2012 | B2 |
| 8195328 | Mallett et al. | Jun 2012 | B2 |
| 8286236 | Jung et al. | Oct 2012 | B2 |
| 8412588 | Bodell et al. | Apr 2013 | B1 |
| 8418959 | Kang et al. | Apr 2013 | B2 |
| 8429754 | Jung et al. | Apr 2013 | B2 |
| 8473189 | Christoph | Jun 2013 | B2 |
| 8511606 | Utke et al. | Aug 2013 | B1 |
| 8577538 | Lenser et al. | Nov 2013 | B2 |
| 8599027 | Sanchez | Dec 2013 | B2 |
| 8602349 | Petrov | Dec 2013 | B2 |
| 8639400 | Wong | Jan 2014 | B1 |
| 8736820 | Choe et al. | May 2014 | B2 |
| 8752166 | Jung et al. | Jun 2014 | B2 |
| 8791790 | Robertson et al. | Jul 2014 | B2 |
| 8874301 | Rao et al. | Oct 2014 | B1 |
| 8899903 | Saad et al. | Dec 2014 | B1 |
| 8948914 | Zini et al. | Feb 2015 | B2 |
| 8956100 | Davi et al. | Feb 2015 | B2 |
| 8989053 | Skaaksrud et al. | Mar 2015 | B1 |
| 9033285 | Iden et al. | May 2015 | B2 |
| 9051043 | Peeters et al. | Jun 2015 | B1 |
| 9079587 | Rupp et al. | Jul 2015 | B1 |
| 9139310 | Wang | Sep 2015 | B1 |
| 9163909 | Chengalva | Oct 2015 | B2 |
| 9193452 | Carreker | Nov 2015 | B2 |
| 9195959 | Lopez et al. | Nov 2015 | B1 |
| 9216587 | Ando et al. | Dec 2015 | B2 |
| 9216857 | Kalyan et al. | Dec 2015 | B1 |
| 9230236 | Villamar | Jan 2016 | B2 |
| 9235213 | Villamar | Jan 2016 | B2 |
| 9244147 | Soundararajan et al. | Jan 2016 | B1 |
| 9256852 | Myllymaki | Feb 2016 | B1 |
| 9261578 | Im et al. | Feb 2016 | B2 |
| 9321531 | Takayama et al. | Apr 2016 | B1 |
| 9336506 | Shucker et al. | May 2016 | B2 |
| 9336635 | Robertson et al. | May 2016 | B2 |
| 9358975 | Watts | Jun 2016 | B1 |
| 9373149 | Abhyanker | Jun 2016 | B2 |
| 9381916 | Zhu et al. | Jul 2016 | B1 |
| 9397518 | Theobald | Jul 2016 | B1 |
| 9404761 | Meuleau | Aug 2016 | B2 |
| 9409644 | Stanek et al. | Aug 2016 | B2 |
| 9411337 | Theobald et al. | Aug 2016 | B1 |
| 9412280 | Zwillinger et al. | Aug 2016 | B1 |
| 9436183 | Thakur et al. | Sep 2016 | B2 |
| 9436926 | Cousins et al. | Sep 2016 | B2 |
| 9448559 | Kojo et al. | Sep 2016 | B2 |
| 9489490 | Theobald | Nov 2016 | B1 |
| 9510316 | Skaaksrud | Nov 2016 | B2 |
| 9535421 | Canoso et al. | Jan 2017 | B1 |
| 9545852 | Streett | Jan 2017 | B2 |
| 9561941 | Watts | Feb 2017 | B1 |
| 9563201 | Tofte et al. | Feb 2017 | B1 |
| 9568335 | Thakur et al. | Feb 2017 | B2 |
| 9582950 | Shimizu et al. | Feb 2017 | B2 |
| 9600645 | Fadell et al. | Mar 2017 | B2 |
| 9619776 | Ford et al. | Apr 2017 | B1 |
| 9623553 | Theobald et al. | Apr 2017 | B1 |
| 9623562 | Watts | Apr 2017 | B1 |
| 9650136 | Haskin et al. | May 2017 | B1 |
| 9652912 | Fadell et al. | May 2017 | B2 |
| 9656805 | Evans et al. | May 2017 | B1 |
| 9671791 | Paczan | Jun 2017 | B1 |
| 9677564 | Woodworth et al. | Jun 2017 | B1 |
| 9682481 | Lutz et al. | Jun 2017 | B2 |
| 9697730 | Thakur et al. | Jul 2017 | B2 |
| 9718564 | Beckman et al. | Aug 2017 | B1 |
| 9720414 | Theobald | Aug 2017 | B1 |
| 9731821 | Hoareau et al. | Aug 2017 | B2 |
| 9733646 | Nusser et al. | Aug 2017 | B1 |
| 9746852 | Watts et al. | Aug 2017 | B1 |
| 9746853 | Scheepjens et al. | Aug 2017 | B2 |
| 9778653 | McClintock et al. | Oct 2017 | B1 |
| 9786187 | Bar-Zeev et al. | Oct 2017 | B1 |
| 9796529 | Hoareau et al. | Oct 2017 | B1 |
| 9828092 | Navot et al. | Nov 2017 | B1 |
| 9858604 | Apsley et al. | Jan 2018 | B2 |
| 9886035 | Watts et al. | Feb 2018 | B1 |
| 9896204 | Willison | Feb 2018 | B1 |
| 9959771 | Carlson | May 2018 | B1 |
| 9959773 | Raptopoulos et al. | May 2018 | B2 |
| 9974612 | Pinter et al. | May 2018 | B2 |
| 10022753 | Chelian et al. | Jul 2018 | B2 |
| 10022867 | Saboo et al. | Jul 2018 | B2 |
| 10048697 | Theobald | Aug 2018 | B1 |
| 10108185 | Theobald | Oct 2018 | B1 |
| 10137984 | Flick | Nov 2018 | B1 |
| 10558226 | Bigdeli | Feb 2020 | B1 |
| 10649469 | Salas-Moreno et al. | May 2020 | B2 |
| 10745132 | Kimchi | Aug 2020 | B1 |
| 10780988 | Buchmueller et al. | Sep 2020 | B2 |
| 10860115 | Tran | Dec 2020 | B1 |
| 11164149 | Williams | Nov 2021 | B1 |
| 11619952 | Kwon et al. | Apr 2023 | B2 |
| 11628932 | Seung et al. | Apr 2023 | B2 |
| 11649050 | Miller | May 2023 | B1 |
| 11726184 | Ferreira et al. | Aug 2023 | B2 |
| 11808580 | Ebrahimi Afrouzi et al. | Nov 2023 | B1 |
| D1008873 | Lin | Dec 2023 | S |
| 11851162 | Daube et al. | Dec 2023 | B1 |
| 11868146 | Yasunaga et al. | Jan 2024 | B2 |
| 11933613 | Michini et al. | Mar 2024 | B2 |
| 20010045449 | Shannon | Nov 2001 | A1 |
| 20020016726 | Ross | Feb 2002 | A1 |
| 20020035450 | Thackston | Mar 2002 | A1 |
| 20020072979 | Sinha et al. | Jun 2002 | A1 |
| 20020087375 | Griffin et al. | Jul 2002 | A1 |
| 20020107751 | Rajagopalan et al. | Aug 2002 | A1 |
| 20020111914 | Terada et al. | Aug 2002 | A1 |
| 20020116289 | Yang | Aug 2002 | A1 |
| 20020123930 | Boyd et al. | Sep 2002 | A1 |
| 20020156645 | Hansen | Oct 2002 | A1 |
| 20030040980 | Nakajima et al. | Feb 2003 | A1 |
| 20030072031 | Kuwata et al. | Apr 2003 | A1 |
| 20030121968 | Miller et al. | Jul 2003 | A1 |
| 20030141411 | Pandya et al. | Jul 2003 | A1 |
| 20040002898 | Kuhlmann et al. | Jan 2004 | A1 |
| 20040068416 | Solomon | Apr 2004 | A1 |
| 20040112660 | Johansson et al. | Jun 2004 | A1 |
| 20040160335 | Reitmeier et al. | Aug 2004 | A1 |
| 20040162638 | Solomon | Aug 2004 | A1 |
| 20040257199 | Fitzgibbon et al. | Dec 2004 | A1 |
| 20050068178 | Lee et al. | Mar 2005 | A1 |
| 20050093865 | Jia | May 2005 | A1 |
| 20050102240 | Misra et al. | May 2005 | A1 |
| 20050244060 | Nagarajan et al. | Nov 2005 | A1 |
| 20050285934 | Carter | Dec 2005 | A1 |
| 20060053534 | Mullen | Mar 2006 | A1 |
| 20060118162 | Saelzer et al. | Jun 2006 | A1 |
| 20060136237 | Spiegel et al. | Jun 2006 | A1 |
| 20060287829 | Pashko-Paschenko | Dec 2006 | A1 |
| 20070016496 | Bar et al. | Jan 2007 | A1 |
| 20070073552 | Hileman | Mar 2007 | A1 |
| 20070102565 | Speer et al. | May 2007 | A1 |
| 20070150375 | Yang | Jun 2007 | A1 |
| 20070170237 | Neff | Jul 2007 | A1 |
| 20070210953 | Abraham et al. | Sep 2007 | A1 |
| 20070233337 | Plishner | Oct 2007 | A1 |
| 20070244763 | Williams et al. | Oct 2007 | A1 |
| 20070246601 | Layton | Oct 2007 | A1 |
| 20070262195 | Bulaga et al. | Nov 2007 | A1 |
| 20070293978 | Wurman et al. | Dec 2007 | A1 |
| 20080012697 | Smith et al. | Jan 2008 | A1 |
| 20080027591 | Lenser et al. | Jan 2008 | A1 |
| 20080100258 | Ward | May 2008 | A1 |
| 20080109246 | Russell | May 2008 | A1 |
| 20080111816 | Abraham et al. | May 2008 | A1 |
| 20080141921 | Hinderks | Jun 2008 | A1 |
| 20080150679 | Bloomfield | Jun 2008 | A1 |
| 20080154659 | Bettes et al. | Jun 2008 | A1 |
| 20080167817 | Hessler et al. | Jul 2008 | A1 |
| 20080184906 | Kejha | Aug 2008 | A1 |
| 20080189012 | Kaufmann | Aug 2008 | A1 |
| 20080301009 | Plaster et al. | Dec 2008 | A1 |
| 20090027253 | Tooren et al. | Jan 2009 | A1 |
| 20090062974 | Tamamoto et al. | Mar 2009 | A1 |
| 20090063166 | Palmer | Mar 2009 | A1 |
| 20090079388 | Reddy | Mar 2009 | A1 |
| 20090086275 | Liang et al. | Apr 2009 | A1 |
| 20090091435 | Bolourchi | Apr 2009 | A1 |
| 20090106124 | Yang | Apr 2009 | A1 |
| 20090149985 | Chirnomas | Jun 2009 | A1 |
| 20090164379 | Jung et al. | Jun 2009 | A1 |
| 20090165127 | Jung et al. | Jun 2009 | A1 |
| 20090236470 | Goossen et al. | Sep 2009 | A1 |
| 20090254457 | Folsom | Oct 2009 | A1 |
| 20090254482 | Vadlamani et al. | Oct 2009 | A1 |
| 20090299903 | Hung et al. | Dec 2009 | A1 |
| 20090303507 | Abeloe | Dec 2009 | A1 |
| 20090314883 | Arlton et al. | Dec 2009 | A1 |
| 20100007479 | Smith | Jan 2010 | A1 |
| 20100030608 | Kaminsky et al. | Feb 2010 | A1 |
| 20100031351 | Jung et al. | Feb 2010 | A1 |
| 20100088163 | Davidson et al. | Apr 2010 | A1 |
| 20100088175 | Lundquist | Apr 2010 | A1 |
| 20100100269 | Ekhaguere et al. | Apr 2010 | A1 |
| 20100169185 | Cottingham | Jul 2010 | A1 |
| 20100206145 | Tetelbaum et al. | Aug 2010 | A1 |
| 20100287065 | Alivandi | Nov 2010 | A1 |
| 20100299067 | McCollough et al. | Nov 2010 | A1 |
| 20100299222 | Hamilton et al. | Nov 2010 | A1 |
| 20110035149 | McAndrew et al. | Feb 2011 | A1 |
| 20110074570 | Feldstein et al. | Mar 2011 | A1 |
| 20110087350 | Fogel et al. | Apr 2011 | A1 |
| 20110112761 | Hurley et al. | May 2011 | A1 |
| 20110153052 | Pettibone et al. | Jun 2011 | A1 |
| 20110166707 | Romanov et al. | Jul 2011 | A1 |
| 20110178711 | Christoph | Jul 2011 | A1 |
| 20110210866 | David et al. | Sep 2011 | A1 |
| 20110227435 | Maeda | Sep 2011 | A1 |
| 20110246331 | Luther et al. | Oct 2011 | A1 |
| 20110253831 | Cheng | Oct 2011 | A1 |
| 20110264311 | Lee et al. | Oct 2011 | A1 |
| 20110282476 | Hegemier et al. | Nov 2011 | A1 |
| 20110301787 | Chaperon et al. | Dec 2011 | A1 |
| 20110313878 | Norman | Dec 2011 | A1 |
| 20120039694 | Suzanne | Feb 2012 | A1 |
| 20120078592 | Sims | Mar 2012 | A1 |
| 20120091260 | Callou | Apr 2012 | A1 |
| 20120109419 | Mercado | May 2012 | A1 |
| 20120219397 | Baker | Aug 2012 | A1 |
| 20120221438 | Cook et al. | Aug 2012 | A1 |
| 20120227389 | Hinderks | Sep 2012 | A1 |
| 20120229325 | Dutruc | Sep 2012 | A1 |
| 20120234969 | Savoye et al. | Sep 2012 | A1 |
| 20120235606 | Takeuchi | Sep 2012 | A1 |
| 20120323365 | Taylor et al. | Dec 2012 | A1 |
| 20130006739 | Horvitz et al. | Jan 2013 | A1 |
| 20130073477 | Grinberg | Mar 2013 | A1 |
| 20130081245 | Vavrina et al. | Apr 2013 | A1 |
| 20130093582 | Walsh et al. | Apr 2013 | A1 |
| 20130126611 | Kangas et al. | May 2013 | A1 |
| 20130148123 | Hayashi | Jun 2013 | A1 |
| 20130206915 | Desaulniers | Aug 2013 | A1 |
| 20130218446 | Bradley et al. | Aug 2013 | A1 |
| 20130218799 | Lehmann et al. | Aug 2013 | A1 |
| 20130261792 | Gupta et al. | Oct 2013 | A1 |
| 20130262251 | Wan et al. | Oct 2013 | A1 |
| 20130262252 | Lakshman et al. | Oct 2013 | A1 |
| 20130262276 | Wan et al. | Oct 2013 | A1 |
| 20130262336 | Wan et al. | Oct 2013 | A1 |
| 20130264381 | Kim et al. | Oct 2013 | A1 |
| 20130320133 | Ratti et al. | Dec 2013 | A1 |
| 20130324164 | Vulcano | Dec 2013 | A1 |
| 20130332062 | Kreitmair-Steck et al. | Dec 2013 | A1 |
| 20140010656 | Nies | Jan 2014 | A1 |
| 20140022055 | Levien et al. | Jan 2014 | A1 |
| 20140025230 | Levien et al. | Jan 2014 | A1 |
| 20140030444 | Swaminathan et al. | Jan 2014 | A1 |
| 20140031964 | Sidhu et al. | Jan 2014 | A1 |
| 20140032034 | Raptopoulos et al. | Jan 2014 | A1 |
| 20140040065 | DuBois | Feb 2014 | A1 |
| 20140052661 | Shakes et al. | Feb 2014 | A1 |
| 20140058959 | Isbjornssund et al. | Feb 2014 | A1 |
| 20140081445 | Villamar | Mar 2014 | A1 |
| 20140089073 | Jacobs et al. | Mar 2014 | A1 |
| 20140136282 | Fedele | May 2014 | A1 |
| 20140136414 | Abhyanker | May 2014 | A1 |
| 20140149244 | Abhyanker | May 2014 | A1 |
| 20140156053 | Mahdavi et al. | Jun 2014 | A1 |
| 20140180914 | Abhyanker | Jun 2014 | A1 |
| 20140200697 | Cheng | Jul 2014 | A1 |
| 20140214684 | Pell | Jul 2014 | A1 |
| 20140244433 | Cruz | Aug 2014 | A1 |
| 20140254896 | Zhou et al. | Sep 2014 | A1 |
| 20140271200 | Sutton et al. | Sep 2014 | A1 |
| 20140283104 | Nilsson | Sep 2014 | A1 |
| 20140309813 | Ricci | Oct 2014 | A1 |
| 20140325218 | Shimizu et al. | Oct 2014 | A1 |
| 20140330456 | Morales et al. | Nov 2014 | A1 |
| 20150006005 | Yu et al. | Jan 2015 | A1 |
| 20150066178 | Stava | Mar 2015 | A1 |
| 20150069968 | Pounds | Mar 2015 | A1 |
| 20150098819 | Tourin et al. | Apr 2015 | A1 |
| 20150102154 | Duncan et al. | Apr 2015 | A1 |
| 20150112837 | O'Dea | Apr 2015 | A1 |
| 20150112885 | Fadell et al. | Apr 2015 | A1 |
| 20150120094 | Kimchi et al. | Apr 2015 | A1 |
| 20150120602 | Huffman et al. | Apr 2015 | A1 |
| 20150127712 | Fadell et al. | May 2015 | A1 |
| 20150129716 | Yoffe | May 2015 | A1 |
| 20150153175 | Skaaksrud | Jun 2015 | A1 |
| 20150154545 | Skaaksrud et al. | Jun 2015 | A1 |
| 20150158599 | Sisko | Jun 2015 | A1 |
| 20150175276 | Koster | Jun 2015 | A1 |
| 20150183528 | Walsh et al. | Jul 2015 | A1 |
| 20150185034 | Abhyanker | Jul 2015 | A1 |
| 20150191255 | Zolich et al. | Jul 2015 | A1 |
| 20150193971 | Dryanovski et al. | Jul 2015 | A1 |
| 20150202770 | Patron et al. | Jul 2015 | A1 |
| 20150227882 | Bhatt | Aug 2015 | A1 |
| 20150246727 | Masticola et al. | Sep 2015 | A1 |
| 20150253777 | Binney et al. | Sep 2015 | A1 |
| 20150254611 | Perez | Sep 2015 | A1 |
| 20150259078 | Filipovic et al. | Sep 2015 | A1 |
| 20150286216 | Miwa | Oct 2015 | A1 |
| 20150314881 | Tsaliah et al. | Nov 2015 | A1 |
| 20150317597 | Shucker et al. | Nov 2015 | A1 |
| 20150332206 | Trew et al. | Nov 2015 | A1 |
| 20150367850 | Clarke et al. | Dec 2015 | A1 |
| 20150370251 | Siegel et al. | Dec 2015 | A1 |
| 20160001877 | Paulos | Jan 2016 | A1 |
| 20160009413 | Lee et al. | Jan 2016 | A1 |
| 20160019495 | Kolchin | Jan 2016 | A1 |
| 20160033966 | Farris et al. | Feb 2016 | A1 |
| 20160051110 | Cao et al. | Feb 2016 | A1 |
| 20160058181 | Han et al. | Mar 2016 | A1 |
| 20160068267 | Liu et al. | Mar 2016 | A1 |
| 20160070265 | Liu et al. | Mar 2016 | A1 |
| 20160085238 | Hayes | Mar 2016 | A1 |
| 20160104099 | Villamar | Apr 2016 | A1 |
| 20160104113 | Gorlin | Apr 2016 | A1 |
| 20160107750 | Yates | Apr 2016 | A1 |
| 20160114488 | Medina et al. | Apr 2016 | A1 |
| 20160117931 | Chan et al. | Apr 2016 | A1 |
| 20160125746 | Kunzi et al. | May 2016 | A1 |
| 20160129592 | Saboo et al. | May 2016 | A1 |
| 20160130015 | Caubel et al. | May 2016 | A1 |
| 20160132059 | Mason et al. | May 2016 | A1 |
| 20160144734 | Wang et al. | May 2016 | A1 |
| 20160144982 | Sugumaran | May 2016 | A1 |
| 20160180618 | Ho et al. | Jun 2016 | A1 |
| 20160196755 | Navot et al. | Jul 2016 | A1 |
| 20160196756 | Prakash et al. | Jul 2016 | A1 |
| 20160200438 | Bokeno et al. | Jul 2016 | A1 |
| 20160207627 | Hoareau et al. | Jul 2016 | A1 |
| 20160214717 | Silva | Jul 2016 | A1 |
| 20160214728 | Rossi et al. | Jul 2016 | A1 |
| 20160221671 | Fisher et al. | Aug 2016 | A1 |
| 20160235236 | Byers et al. | Aug 2016 | A1 |
| 20160236778 | Takayama et al. | Aug 2016 | A1 |
| 20160239789 | Hanks | Aug 2016 | A1 |
| 20160239803 | Borley et al. | Aug 2016 | A1 |
| 20160257401 | Buchmueller et al. | Sep 2016 | A1 |
| 20160258775 | Santilli et al. | Sep 2016 | A1 |
| 20160266578 | Douglas et al. | Sep 2016 | A1 |
| 20160282126 | Watts et al. | Sep 2016 | A1 |
| 20160299233 | Levien et al. | Oct 2016 | A1 |
| 20160321503 | Zhou | Nov 2016 | A1 |
| 20160334229 | Ross et al. | Nov 2016 | A1 |
| 20160340021 | Zhang et al. | Nov 2016 | A1 |
| 20160364660 | Brown | Dec 2016 | A1 |
| 20160364679 | Cao | Dec 2016 | A1 |
| 20160364823 | Cao | Dec 2016 | A1 |
| 20160364989 | Speasl et al. | Dec 2016 | A1 |
| 20160371984 | Macfarlane | Dec 2016 | A1 |
| 20170011333 | Greiner et al. | Jan 2017 | A1 |
| 20170011340 | Gabbai | Jan 2017 | A1 |
| 20170032315 | Gupta et al. | Feb 2017 | A1 |
| 20170087999 | Miller et al. | Mar 2017 | A1 |
| 20170096222 | Spinelli et al. | Apr 2017 | A1 |
| 20170098378 | Soundararajan et al. | Apr 2017 | A1 |
| 20170100837 | Zevenbergen et al. | Apr 2017 | A1 |
| 20170101017 | Streett | Apr 2017 | A1 |
| 20170113352 | Lutz et al. | Apr 2017 | A1 |
| 20170147975 | Natarajan et al. | May 2017 | A1 |
| 20170152060 | Morisawa | Jun 2017 | A1 |
| 20170154347 | Bateman | Jun 2017 | A1 |
| 20170164319 | Skaaksrud et al. | Jun 2017 | A1 |
| 20170167881 | Rander et al. | Jun 2017 | A1 |
| 20170193442 | Ekkel et al. | Jul 2017 | A1 |
| 20170199522 | Li et al. | Jul 2017 | A1 |
| 20170255896 | Dyke | Sep 2017 | A1 |
| 20170286905 | Richardson et al. | Oct 2017 | A1 |
| 20170300855 | Lund et al. | Oct 2017 | A1 |
| 20170305526 | Thomassey | Oct 2017 | A1 |
| 20170308098 | Yu et al. | Oct 2017 | A1 |
| 20170316379 | Lepek et al. | Nov 2017 | A1 |
| 20170330145 | Studnicka et al. | Nov 2017 | A1 |
| 20170345245 | Torresani et al. | Nov 2017 | A1 |
| 20170372256 | Kantor et al. | Dec 2017 | A1 |
| 20180024554 | Brady et al. | Jan 2018 | A1 |
| 20180088586 | Hance et al. | Mar 2018 | A1 |
| 20180127211 | Jarvis et al. | May 2018 | A1 |
| 20180137454 | Kulkarni et al. | May 2018 | A1 |
| 20180203464 | Yu et al. | Jul 2018 | A1 |
| 20180257775 | Baek et al. | Sep 2018 | A1 |
| 20190051192 | Schick et al. | Feb 2019 | A1 |
| 20190135403 | Perry et al. | May 2019 | A1 |
| 20190161190 | Gil et al. | May 2019 | A1 |
| 20190172358 | Zhou et al. | Jun 2019 | A1 |
| 20200272144 | Yang et al. | Aug 2020 | A1 |
| 20200284883 | Ferreira et al. | Sep 2020 | A1 |
| 20200324898 | Youmans et al. | Oct 2020 | A1 |
| 20200369384 | Kelly | Nov 2020 | A1 |
| 20210089055 | Tran | Mar 2021 | A1 |
| 20210094686 | Metzner et al. | Apr 2021 | A1 |
| 20220009647 | Johannesson et al. | Jan 2022 | A1 |
| 20220144424 | Metzner et al. | May 2022 | A1 |
| 20220162001 | Gherardi | May 2022 | A1 |
| 20220163980 | Beer et al. | May 2022 | A1 |
| 20230244249 | Smith et al. | Aug 2023 | A1 |
| 20230298268 | Oleynikova et al. | Sep 2023 | A1 |
| Number | Date | Country |
|---|---|---|
| 101385059 | Mar 2009 | CN |
| 103224026 | Jul 2013 | CN |
| 203039518 | Jul 2013 | CN |
| 103365297 | Oct 2013 | CN |
| 104760704 | Jul 2015 | CN |
| 109118826 | Jan 2019 | CN |
| 102011086497 | May 2013 | DE |
| 3415436 | Dec 2018 | EP |
| 2692064 | Dec 1993 | FR |
| 2455374 | Jun 2009 | GB |
| S48088255 | Oct 1973 | JP |
| S56048952 | Nov 1981 | JP |
| H0712088 | Jan 1995 | JP |
| 2004126800 | Apr 2004 | JP |
| 2009297449 | Dec 2009 | JP |
| 2010095246 | Apr 2010 | JP |
| 2011211025 | Oct 2011 | JP |
| 2012037204 | Feb 2012 | JP |
| 2007052246 | May 2007 | WO |
| 2008147484 | Dec 2008 | WO |
| 2008147484 | Feb 2009 | WO |
| 2009153588 | Dec 2009 | WO |
| 2010070717 | Jun 2010 | WO |
| 2012012752 | Jan 2012 | WO |
| 2012012752 | Jun 2012 | WO |
| 2013140085 | Sep 2013 | WO |
| 2013148123 | Oct 2013 | WO |
| 2014064431 | May 2014 | WO |
| 2014068982 | May 2014 | WO |
| 2014080409 | May 2014 | WO |
| 2014064431 | Jul 2014 | WO |
| 2017064202 | Apr 2017 | WO |
| 2017186137 | Nov 2017 | WO |
| 2018136753 | Jul 2018 | WO |
| 2018156991 | Aug 2018 | WO |
| Entry |
|---|
| Wikipedia, “Ramer-Douglas-Peucker Algorithm,” www.wikipedia.com, Wikipedia: The Free Encyclopedia, 5 pages, Aug. 18, 2022, URL: https://en.wikipedia.org/wiki/Ramer%E2%80%93Douglas%E2%80%93Peucker_algorithm, obtained via web.archive.org on Jan. 6, 2023. |
| Bullock et al., “Analysis of the Use of Digital Road Maps in Vehicle Navigation,” 1994, IEEE, p. 494-501 (Year: 1994). |
| DHL Trend Research, “Self-Driving Vehicles in Logistics,” Dec. 2014, Markus Kuckelhaus et al. (downloaded from http://www.dhl.com/content/dam/downloads/g0/about_us/logistics_insights/dhl_self_driving_vehicles.pdf with an archived Web version available on https://web.archive.org/web/20151018154844/http://www.dhl.com/content/dam/downloads/g0/about_us/logistics_insights/dhl_self_driving_vehicles.pdf), 39 pages. |
| DHL Trend Research, “Unmanned Aerial Vehicles in Logistics: A DHL perspective on implications and use cases for the logistics industry,” 2014, Markus Kuckelhaus et al., URL: http://www.dhl.com/content/dam/downloads/g0/about_us/logistics_insights/dhl_trend_report_uav.pdf with a Web Archive version available at: https://web.archive.org/web/20150923080141/http://www.dhl.com/en/about_us/logistics_insights/dhl_trend_research/uav.html, 24 pages. |
| Hawas et al., “Infrastructureless Inter-Vehicular Real-Time Route Guidance,” 2008, IEEE, p. 1213-1219 (Year: 2008). |
| Kais, Mikael et al., “An Intelligent architecture for automated transportation in our cities”, 2001 European Control Conference (ECC), Porto, Portugal, Sep. 4-7, 2001, pp. 277-282 (Year: 2001). |
| Kladis et al., “Event-Based Energy Optimum Route Planning in the Context of Unmanned Aerial Vehicles for Multi-Objective Exploration Missions,” 2009, IEEE, p. 1281-1286 (Year: 2009). |
| Marcus Wohlsen, “The Next Big Thing You Missed: Amazon's Delivery Drones Could Work—They Just Need Trucks,” Wired: Business, Jun. 10, 2014, URL: https://www.wired.com/2014/06/the-next-big-thing-you-missed-delivery-drones-launched-from-trucks-are-the-future-of-shipping/, 4 pages. |
| Mike Murphy, “Google wants to deliver packages from self-driving trucks,” published Feb. 9, 2016, URL: https://qz.com/613277/google-wants-to-deliver-packages-from-self-driving-trucks/, 4 pages. |
| Nanohawk Aeraccess: “Unmanned Aerial Vehicle—Aeraccess—Nanohawk—Webarchive Jun. 16, 2019”, Jun. 16, 2019 (Jun. 16, 2019), pp. 1-3, XP055759013, URL: https://web.archive.org/web/20190616235755/http://www.aeraccess-group.com/product/indoor/nanohawk [Retrieved from the Internet: Dec. 10, 2020]; the whole document. |
| Navaravong et al., “Formation Reconfiguration for Mobile Robots with Network Connectivity Constraints,” 2012, IEEE, p. 18-24 (Year: 2012). |
| Parent, Michel et al., “Intelligent Transportation in Cities with CTS”, The IEEE 5th International Conference on Intelligent Transportation Systems, Sep. 3-6, 2002, Singapore, pp. 826-830 (Year: 2002). |
| Sandoval, “Google patents secure rolling box to receive packages from drones,” Geekwire.com, Jan. 27, 2016, URL: http://www.geekwire.com/2016/google-pondering-drone-delivery-even-about-boxes-it-flies-to-front-doors/, 11 pages. |
| Smith, Randall C., and Peter Cheeseman, “On the Representation and Estimation of Spatial Uncertainty,” The Int'l Journal of Robotics Research, vol. 5, No. 4 (Winter 1986), Copyright 1986 Massachusetts Institute of Technology, 14 pages. |
| URL: https://web.archive.org/web/20160804001046/https://www.starship.xyz/, download date: Aug. 4, 2016, 21 pages. |
| Andrew Amato, “Parrot Announces New Bobop Drone”, Dronelife.com, May 12, 2014; http://dronelife.com/2014/05/12/parrot-announces-new-bebop-drone/, accessed Dec. 21, 2016. |
| Ivan Barajas, “Parrot Unveils New Drone and Controller,” May 14, 2014; https://blog.newegg.com/parrot-unveils-drone-controller-oculus-compatible/, accessed Dec. 21, 2016. |
| Microchip Technology Inc. AT42QT1010 Data Sheet. Copyright © 2017 Microchip Technology Inc. 30 pages. |
| MicroPilot home page, https://www.micropilot.com/; archived on Jan. 3, 2013 by Internet Archive, http://web.archive.org/web/2013103180733/http://www.micropilot.com/?, accessed May 2, 2016. |
| Norman Chan, “Hands-On with Parrot's Bebop Drone Quadcopter”, tested.com, May 12, 2014; http://www.tested.com/tech/robots/461148-parrots-bebop-drone-what-you-should-know/, accessed Dec. 22, 2016. |
| rhelicopterfun.com, “Parrot AF Drone Quadcopter Review”, http://www.rchelicopterfun.com/parrot-ar-drone.html; archived on Mar. 27, 2012 by Internet Archive, http://web.archive.org/web/20120327140509/http://www.rchelicopterfun.com/parrot-ar-drone.html, accessed Apr. 27, 2016. |
| Wang, David. Application Report: FDC1004: Basics of Capacitive Sensing and Applications. SNOA927A—Dec. 2014—Revised Jun. 2021. Copyright © 2021 Texas Instruments Incorporated. 12 pages. |
| Wikipedia, “Apollo Abort Modes”, https://en.wikipedia.org/wiki/Apollo_abort_modes; archived by Internet Archive on Aug. 16, 2012, https://web.archive.org/web/20120816115115/https://en.wikipedia.org/wiki/Apollo_abort_modes; accessed Jul. 9, 2019 (Year: 2012). |
| Wikipedia, “Space Shuttle Abort Modes,” https://en.wikipedia.org/wiki/Space_Shuttle_abort_modes; archived by Internet Archive on Aug. 15, 2012, https://web.archive.org/web/20120815031221/https://en.wikipedia.org/wiki/Space_Shuttle_abort_modes; accessed Jul. 9, 2019 (Year: 2012). |
| Elizondo-Leal, J. C., et al., “The Exact Euclidean Distance Transform: A New Algorithm for Universal Path Planning.” www.intechopen.com, International Journal of Advanced Robotic Systems 10, No. 6 (2013): 266, www.researchgate. net, URL: https://www.researchgate.net/publication/274622763_The_Exact_Euclidean_Distance_Transform_A_New_Algorithm_for_Universal_Path_Planning. |
| Faro, “GeoSLAM ZEB Horizon RT Mobile Scanner,” www.faro.com, FARO Technologies, Inc., Copyright 2024 Faro URL: https://www.faro.com/en/Products/Hardware/GeoSLAM-ZEB-Horizon-RT (Year 2024). |
| Faro, “GeoSLAM ZEB Horizon RT Mobile Scanner: Features—Sensor Features, ” www.faro.com, FARO Technologies, Inc., Copyright 2024 Faro URL: https://www.faro.com/en/Products/Hardware/GeoSLAM-ZEB-Horizon-RT (Year 2024). |
| Faro, “GeoSLAM ZEB Horizon RT Mobile Scanner: Value—Capture Data Faster—Aerial Vehicle / Scanner Carried by Human While Walking, ” www.faro.com, FARO Technologies, Inc., Copyright 2024 Faro URL: https://www.faro.com/en/Products/Hardware/GeoSLAM-ZEB-Horizon-RT (Year 2024). |
| Faro, “GeoSLAM ZEB Horizon RT Mobile Scanner: Value—Complement Other Forms of Data Capture—Justification for Combining Scanner Method Data With Other Art, ” www.faro.com, FARO Technologies, Inc., Copyright 2024 Faro URL: https://www.faro.com/en/Products/Hardware/GeoSLAM-ZEB-Horizon-RT (Year 2024). |
| Faro, “GeoSLAM ZEB Horizon RT Mobile Scanner: Versatility—UAV Mount—Initial Walking UAV with Scanner, ” www.faro.com, FARO Technologies, Inc., Copyright 2024 Faro URL: https://www.faro.com/en/Products/Hardware/GeoSLAM-ZEB-Horizon-RT (Year 2024). |
| Jung, J.W., et al., “Expanded Douglas-Peucker Polygonal Approximation and Opposite Angle-Based Exact Cell Decomposition for Path Planning With Curvilinear Obstacles.” Applied Sciences 9, No. 4 (2019): 638, www.mdpi.com, Copyright 1996-2024 MDPI (Basel, Switzerland), URL: https://www.mdpi.com/2076-3417/9/4/638 (Year: 2019). |
| Sanchez-Ibáñez, J. R., et al., “Path Planning for Autonomous Mobile Robots: A Review,” www.mdpi.com, Copyright 1996-2024 MDPI (Basel, Switzerland), URL: https://www.mdpi.com/1424-8220/21/23/7898 (Year: 2022). |
