Classifications

• • G—PHYSICS
  • G07—CHECKING-DEVICES
  • G07C—TIME OR ATTENDANCE REGISTERS; REGISTERING OR INDICATING THE WORKING OF MACHINES; GENERATING RANDOM NUMBERS; VOTING OR LOTTERY APPARATUS; ARRANGEMENTS, SYSTEMS OR APPARATUS FOR CHECKING NOT PROVIDED FOR ELSEWHERE
  • G07C5/00—Registering or indicating the working of vehicles
  • G07C5/008—Registering or indicating the working of vehicles communicating information to a remotely located station
• • G—PHYSICS
  • G07—CHECKING-DEVICES
  • G07C—TIME OR ATTENDANCE REGISTERS; REGISTERING OR INDICATING THE WORKING OF MACHINES; GENERATING RANDOM NUMBERS; VOTING OR LOTTERY APPARATUS; ARRANGEMENTS, SYSTEMS OR APPARATUS FOR CHECKING NOT PROVIDED FOR ELSEWHERE
  • G07C5/00—Registering or indicating the working of vehicles
  • G07C5/08—Registering or indicating performance data other than driving, working, idle, or waiting time, with or without registering driving, working, idle or waiting time

Definitions

• Unmanned vehicles such as unmanned aerial vehicles
• unmanned aerial vehicles have been developed for a wide range of applications including surveillance, search and rescue operations, exploration, and other fields.
• unmanned vehicles may be equipped with sensors for collecting data during flight.
• unmanned aerial vehicles are commonly provided with sensors for detecting parameters such as speed, altitude, and location of a vehicle.
• the recorded operation history may comprise outgoing operation commands sent from a remote controller of a remotely controlled vehicle, as well as incoming operation commands received by the remotely controlled vehicle.
• the recorded operation history may further comprise vehicle status data, such as data related to an operation process of the remotely controlled vehicle.
• the recorded operation history of a vehicle may be used to analyze a behavior of the vehicle.
• a method for recording user operation data for a remotely controlled vehicle comprises receiving, using a user interface of a remote controller, outgoing operation commands, the remote controller comprising a user operation data recorder.
• the method further comprises recording the user operation data to a memory of the user operation data recorder, the user operation data recorder comprising the outgoing commands.
• the user operation data recorded to the user operation data recorder may be inaccessible for modification.
• a device for recording user operation data for a remotely controlled vehicle comprises a memory configured to record user operation data, wherein the memory is received within a housing that is removable from the remote controller and more resistant to destruction than the rest of the remote controller.
• the user operation data may comprise outgoing operation commands that affect operation of the remotely controlled vehicle.
• the outgoing operation commands may be transmitted to the remotely controlled vehicle, and received via a remote controller of the remotely controlled vehicle.
• a user operation data recorder may be integrated via software with a processing unit configured to control operation of the remote controller, such that the remote controller becomes inoperable if the user operation data recorder is tampered with.
• the processing unit may be implemented with a software version corresponding to a unique identity of the user operation data recorder, such that regular operation of the software of the processing unit requires obtaining the unique identity of the user operation data recorder.
• a memory of a user operation data recorder is received in a housing that comprises a shock-absorbing material and/or a waterproof material.
• a user operation data recorder is configured to associate the user operation data with a specific user.
• the user operation data recorder may be configured to recognize an identity of a specific user entering the outgoing operation commands, and using the identity of the specific user, associate the user operation data with the specific user. Recognizing the identity of the specific user can comprise providing user authentication for each user.
• the device can be configured to begin recording user operation data once a user has been authenticated, and end recording when the user authentication is terminated.
• the user operation data for each user may be configured to be distinguished from data for other users via physically separated storage regions.
• the user operation data for each user may be configured to be distinguished from data for other users via digital means.
• the memory of a user operation data recorder may be a non-volatile memory. In some embodiments, the memory is configured to record data continuously. In some embodiments, the memory is configured to record data periodically at pre-determined intervals.
• a user operation data recorder is further configured to enter an accident mode that prevents updates to the recorder when the recorder is alerted that one or more accident conditions are detected.
• the one or more accident conditions may be selected from a loss of a global positioning system signal of the vehicle, a loss of a radio connection of the vehicle, vehicle collision, vehicle entry into a restricted area, deviation of a flight path of a vehicle from a projected path, abnormal acceleration of the vehicle, abnormal speed of the vehicle, abnormal temperature of the vehicle, and data from a vision sensor of a vehicle indicating poor visibility.
• the user operation data recorder may be further configured to exit the accident mode when the recorder receives instructions that the accident condition has been resolved.
• the user interface may be configured to receive outgoing operation commands, and configured to control operation of the remotely controlled vehicle.
• the communication module may be configured to transmit the outgoing operation commands from the remote controller to the remotely controlled vehicle.
• the device to record user operation data may comprise any user operation data recorder described herein.
• a device for recording vehicle operation data for a remotely controlled vehicle comprises a memory configured to record vehicle operation data, the vehicle operation data comprising incoming operation commands that affect operation of the remotely controlled vehicle, said incoming operation commands received via a remote controller of the remotely controlled vehicle.
• the vehicle operation data recorded by the memory may be inaccessible for modification.
• a memory of a vehicle operation data recorder is received in a housing that comprises a shock-absorbing material and/or a waterproof material.
• a housing receiving a memory of a vehicle operation data recorder comprises a tamper-evident structure.
• the tamper-evident structure may comprise one or more labels adhered to one or more fasteners of the housing, such that an attempt to unfasten the one or more fasteners results in evident physical damage to the label.
• the tamper-evident structure may comprise one or more fasteners of the housing that are coupled to an electrical circuit, such that an attempt to unfasten the one or more fasteners results in a detected change to the electrical circuit that is recorded to the memory or to a processing unit of the remotely controlled vehicle.
• vehicle operation data recorded by a vehicle operation data recorder further comprises vehicle status data relating to one or more environmental parameters or operation processes of the vehicle.
• the vehicle status data relating to one or more environmental parameters may comprise one or more of a location of the vehicle, outside temperature, wind speed, and detection of precipitation.
• the vehicle status data relating to one or more operation processes may comprise one or more of an acceleration of the vehicle, angular acceleration of the vehicle, speed of the vehicle, position of the vehicle, location of the vehicle, altitude of the vehicle, a position of a vehicle actuator, a flap setting of an aircraft, performance of an engine, running speed of an engine, power output of an engine, a charge percentage of a battery, vehicle cabin pressure, and vehicle cabin temperature.
• a remotely controlled vehicle further comprises a camera, and the vehicle status data further comprises one or more pictures taken by the camera of a surrounding environment of the vehicle.
• the vehicle status data may be associated with a corresponding incoming operation command.
• vehicle operation data recorded by a vehicle operation data recorder further comprises an identification of the remote controller.
• the identification may comprise a unique serial number of the remote controller.
• the vehicle operation data may be associated with a corresponding time.
• the memory of a vehicle operation data recorder may be a non-volatile memory. In some embodiments, the memory is configured to record data continuously. In some embodiments, the memory is configured to record data periodically at pre-determined intervals.
• the remotely controlled vehicle is an unmanned aerial vehicle.
• the incoming operation commands may affect flight of the unmanned aerial vehicle, operation of one or more sensors on-board the unmanned aerial vehicle, and/or positioning of a payload on-board the unmanned aerial vehicle with respect to the rest of the unmanned aerial vehicle.
• an apparatus for analyzing a behavior of a remotely controlled vehicle comprises a communication unit configured to receive (1) user operation data comprising outgoing operation commands that affect operation of the remotely controlled vehicle, said outgoing operation commands received via a remote controller of the remotely controlled, and (2) vehicle operation data comprising (i) the incoming operation commands that affect operation of the remotely controlled vehicle or (ii) vehicle status data relating to one or more environmental parameters or operation processes of the vehicle.
• the apparatus further comprises one or more processors individually or collectively configured to compare the user operation data and the vehicle operation data, thereby identifying discrepancies which can comprise (1) differences between the outgoing operation commands and the incoming operation commands or (2) differences between the incoming operation commands and the vehicle status data.
• the one or more processors can be further configured to determine, based on the identified discrepancies, one or more causes of the behavior of the remotely controlled vehicle.
• a system for analyzing a behavior of a remotely controlled vehicle comprises a user operation data recorder having a memory configured to record user operation data, wherein the user operation data comprises outgoing operation commands that affect operation of the remotely controlled vehicle, said outgoing operation commands received via a remote controller of the remotely controlled vehicle.
• the system further comprises a vehicle operation data recorder having a memory configured to record vehicle operation data, wherein the vehicle operation data comprises (1) incoming operation commands that affect operation of the remotely controlled vehicle or (2) vehicle status data relating to one or more environmental parameters or operation processes of the vehicle.
• the user operation data and the vehicle operation data are accessible for comparison, to identify discrepancies which can comprise (1) differences between the outgoing operation commands and the incoming operation commands or (2) differences between the incoming operation commands and the vehicle status data, thereby determining one or more causes of the behavior of the remotely controlled vehicle.
• the behavior of a remotely controlled vehicle is analyzed to improve design or manufacture of the vehicle or its components.
• the comparison between the user operation data and the vehicle operation data identifies no discrepancies between the outgoing operation commands and the incoming operation commands, and no discrepancies between the incoming operation commands and the vehicle status data.
• the cause of the behavior of the remotely controlled vehicle may then be determined to be the user sending the operation commands affecting the behavior, wherein the user sent said operation commands unintentionally or intentionally.
• the comparison between the user operation data and the vehicle operation data identifies a discrepancy between the incoming operation commands and the vehicle status data.
• the cause of the behavior may then be determined to be an error in execution of the incoming operation commands by the remotely controlled vehicle.
• the error may comprise a malfunction of an operation process of the remotely controlled vehicle, wherein the vehicle status data may comprise one or more of a data value that falls outside of a normal range for the operation process, a change in a data value that falls outside of a normal range for the operation process, an abnormal combination of data values for the operation processes, and data from a location sensor of the remotely controlled vehicle indicating failure of the location sensor.
• the error may comprise a disruption of an operation process of the remotely controlled vehicle by an environmental parameter, wherein the vehicle status data may comprise one or more of data indicating poor visibility, data indicating high winds, and data indicating heavy precipitation.
• FIG. 1 illustrates a system for recording operation data for a remotely controlled vehicle, in accordance with embodiments
• FIG. 3 is a schematic diagram of user operation data recorded by a user operation data recorder, in accordance with embodiments
• FIG. 4 is a schematic diagram of vehicle operation data recorded by a vehicle operation data recorder, in accordance with embodiments
• FIG. 5 illustrates, by way of a block diagram, a method for analyzing a behavior of a remotely controlled vehicle, in accordance with embodiments
• FIG. 6 is a flowchart illustrating a method for analyzing a behavior of a remotely controlled vehicle, in accordance with embodiments
• FIG. 7 is a table showing a method for analyzing a behavior of a remotely controlled vehicle, in accordance with embodiments.
• FIG. 8 illustrates an unmanned aerial vehicle, in accordance with embodiments
• FIG. 9 illustrates a movable object, in accordance with embodiments.
• FIG. 10 is a schematic illustration by way of block diagram of a system for controlling a movable object, in accordance with embodiments.
• Exceptions may occur during the operation of a remotely controlled vehicle, leading to a particular behavior of the vehicle. For example, a malfunction of a vehicle propulsion unit may lead to the vehicle crashing, or a malfunction of a component of the vehicle’s navigation system may lead to the vehicle deviating from its projected travel path. In such circumstances, an analysis of the vehicle’s operation history may help determine a potential cause for the behavior of the vehicle. As such, a system for maintaining a complete recordation of the operation history of the vehicle may provide a useful tool for analyzing the behavior of the vehicle.
• the operation data of a remotely controlled vehicle may be recorded by a remote controller or a component thereof. Alternatively or in combination, the operation data may be recorded by the remotely controlled vehicle or a component thereof. In order to protect the integrity of the recorded data, devices for recording the operation data may be have various features or configurations to protect the recorded data.
• the outgoing operation commands 270 may be transmitted through a wireless connection 110, and be received as incoming operation commands 370 by the remotely controlled vehicle 300.
• the wireless connection may be a direct or an indirect connection, and may, for example, comprise a connection using WiFi, BluetoothTM, or mobile or cellular phone networks (e.g., 3G or 4G networks), as described elsewhere herein.
• the incoming operation commands received by the remotely controlled vehicle can affect operation of the vehicle.
• the remote controller 200 may comprises a user operation data recorder 250 configured to record user operation data 265.
• the user operation data may comprise the outgoing operation commands 270.
• the user operation data recorder may have features or configurations to prevent tampering of the recorded user operation data.
• the recorded user operation data may be stored in the user operation data recorder, for example on a memory of the user operation data recorder. Alternatively or in combination, the recorded user operation data may be transmitted from the user operation data recorder to one or more other devices, for example for analysis and/or for backup storage, as described in further detail herein.
• the system 100 may further comprise an analysis unit or apparatus 400, configured to receive the user operation data 265 and the vehicle operation data 365, and based on the two sets of data, analyze a behavior of a remotely controlled vehicle.
• the analysis unit may be supported with a remote controller, with the remotely controlled vehicle, or with a separate device not on-board the remote controller or the vehicle.
• the system 100 can further comprise a backup unit 500, configured to receive the user operation data 265 and the vehicle operation data 365 over a secure connection and store the data in a database.
• the backup unit may be supported with a remote controller, with the remotely controlled vehicle, or with a separate device not on-board the remote controller or the vehicle.
• the backup unit may be supported with a management center, wherein the management center can be configured to communicate with the remote controller and/or the remotely controlled vehicle via a secure channel of communication. Operation data backed up to the backup unit may be retained for pre-determined period of time.
• FIG. 2 is a schematic diagram of the system 100 for recording the operation data for a remotely controlled vehicle 300, in accordance with embodiments.
• a user 10 can interact with the remote controller 200 via a user interface 215 of the remote controller, providing user input 217.
• the user input may comprise instructions for controlling operation of the remotely controlled vehicle, which may be translated to outgoing operating commands 270.
• the user interface 215 may comprise a physical user input component, such as one or more buttons, switches, levers, or joysticks disposed on the remote controller.
• the user interface may comprise means to utilize one or more sensors configured to detect a user input.
• the remote controller may comprise one or more inertial sensors configured to sense the tilting of the remote controller, wherein the tilting may be translated to an outgoing operation command.
• the processing unit 210 of the remote controller may be further configured to send the outgoing operation commands to a communication module 220 of the remote controller 200.
• the communication module may be configured to package the outgoing operation commands for wireless transmission to the remotely controlled vehicle 300.
• the communication module may be configured to compress and/or encrypt the outgoing operation commands for wireless transmission.
• the communication module 220 of the remote controller 200 may be in communication with a communication module 320 of the remotely controlled vehicle 300, via a wireless connection 110.
• the communication modules 220 and 320 can include transmitters and/or receivers configured to transmit and/or receive data.
• the communication modules can include transceivers incorporating one or more transmitters and one or more receivers.
• the transceiver may have one or more transmitters and one or more receivers integrated into a single component, or distributed over multiple components of the transceiver.
• the communication modules may communicate using one or more of many methods.
• the method may comprise a wireless serial communication link such as BluetoothTM.
• the method may comprise transmitting data over telecommunication networks, cellular networks, or data networks, wherein the networks may comprise Internet or Internet-based networks such as cloud communication networks.
• the method may comprise direct communication, wherein data is transmitted directly between the remote controller and the remotely controlled vehicle, or the method may comprise indirect communication, wherein data is transmitted via one or more intermediate network nodes such as relay stations, towers, satellites, mobile stations, computers, servers, and the like.
• the wireless connection 110 may, for example, comprise a connection using WiFi, WiMAX, coded orthogonal frequency-division multiplexing (COFDM), or mobile or cellular phone networks (e.g., 3G or 4G networks).
• COFDM coded orthogonal frequency-division multiplexing
• the communication module 320 of the remotely controlled vehicle 300 can receive incoming operation commands 370.
• the communication module may be configured to receive and unpackage the incoming operation commands, for example by de-compressing and/or de-encrypting the incoming operation commands.
• the incoming operation commands may be sent to a processing unit 310 of the remotely controlled vehicle, the processing unit configured to control operation of the remotely controlled vehicle based on the incoming operation commands.
• the processing unit may transmit instructions to one or more propulsion units 330 for affecting the movement of the remotely controlled vehicle, such as instructions to initiate one or more predetermined flight sequences of an unmanned aerial vehicle.
• the processing unit may further transmit instructions to control the positioning of a payload on-board the vehicle, control operation of a payload, control operation of one or more communication units of the vehicle, and/or control operation of one or more sensors on-board the vehicle.
• the processing unit 310 may be configured receive the vehicle status data 375 from one or more sensors, and to package the vehicle status data and the incoming operation commands into vehicle operation data 365.
• the processing unit may be further configured to send the vehicle operation data to the vehicle operation data recorder 350, where the data may be recorded.
• the vehicle operation data recorder can comprise a memory 355 configured to record the vehicle operation data, as described in detail elsewhere herein.
• the memory may be a non-volatile memory.
• the memory may be configured to record data continuously, or to record data periodically at pre-determined intervals. Alternatively or in combination, the memory may be configured to record data in response to events.
• the vehicle operation data recorder may further comprise a processing unit in communication with the memory, wherein the processing unit of the vehicle operation data recorder may be configured to receive the vehicle operation data from the processing unit 310 of the remotely controlled vehicle, and send the data to the memory.
• the processing unit of the vehicle operation data recorder may be further configured to package the vehicle operation data for storage in the memory. For example, where the vehicle operation data comprises two or more subsets of data, the processing unit of the vehicle operation data recorder may be configured to associate one subset of data with one or more other subsets of data, prior to transmitting the thus-packaged vehicle operation data to the memory.
• the system 100 may further comprise an analysis unit 400, configured to analyze a behavior of the remotely controlled vehicle 300.
• the analysis unit can provide an analysis of the possible causes for a behavior of the remotely controlled vehicle.
• the analysis unit may comprise a communication module 420 configured to receive user operation data 265 and vehicle operation data 365 from the user operation data recorder 250 and vehicle operation data recorder 350, respectively.
• the communication module 420 can be configured to communicate wirelessly with the user operation data recorder and vehicle operation data recorder, as described in further detail herein.
• the communication module 420 may be configured to communicate using a wired communication method.
• the wired communication method may utilize wires, cables, fiber optics, waveguides, or other suitable physical connections to transmit data.
• the analysis unit may be supported with a remote controller, with the remotely controlled vehicle, or with a separate device not on-board the remote controller or the remotely controlled vehicle.
• the analysis unit 400 may further comprise a processing unit 410, configured to receive the user operation data and vehicle operation data from the communication module 420.
• the processing unit 410 may comprise one or more processors, individually or collectively configured to compare the user operation data and vehicle operation data, thereby identifying discrepancies between the two data sets.
• the discrepancies may include, for example, differences between the outgoing operation commands and incoming operation commands, differences between the incoming operation commands and the vehicle status data, and/or differences between the outgoing operation commands and the vehicle status data. Based on the identified discrepancies, the processing unit 410 may determine one or more causes of a behavior of the remotely controlled vehicle, as described in further detail herein.
• the analysis unit 400 may be configured to perform an analysis periodically at pre-set intervals, for example every 5 seconds, or in response to one or more events, for example after the completion of each trip of the remotely controlled vehicle. Alternatively or in combination, the analysis unit may be configured to perform an analysis when prompted by a user having special privileges or authorization to access the recorded operation history. Alternatively or in combination, the analysis may be performed when vehicle operation has encountered one or more exceptional conditions.
• An exceptional condition may comprise, for example, one or more of a loss of communication with the vehicle, a missing remotely controlled vehicle, a remotely controlled vehicle collision, remotely controlled vehicle entry into a restricted area, deviation of the traveled path of a remotely controlled vehicle from the projected path, abnormal acceleration of the remotely controlled vehicle, abnormal speed of the remotely controlled vehicle, abnormal temperature of the remotely controlled vehicle, or data from a vision sensor of a remotely controlled vehicle indicating poor visibility.
• the system 100 may optionally comprise a backup unit 500, configured to store the user operation data and the vehicle operation data in a database.
• the backup unit may be supported with the remote controller 200, with the remotely controlled vehicle 300, or with a separate device not on-board the remote controller or the remotely controlled vehicle.
• the backup unit may be combined with the analysis unit 400, or the analysis unit and the backup unit may be separate devices.
• a backup unit may be configured to receive data from a plurality of remote controllers and/or a plurality of remotely controlled vehicles.
• the backup unit may be supported with a management center, wherein the management center can be configured to communicate with one or more remote controllers and/or the remotely controlled vehicles via a secure channel of communication.
• the management center can thus function as a repository of operation data. Operation data backed up to the backup unit may be retained for pre-determined period of time.
• the backup unit may comprise a communication module 520 configured to receive data from the user operation data recorder and the vehicle operation data recorder.
• the communication module can be configured to communicate with the user operation data recorder and vehicle operation data recorder using a wireless communication method, a wired communication method, or a combination thereof, as described in further detail herein.
• the communication method may, for example, comprise a connection over a network having an unlimited range, or a network having a limited range.
• the connection is a secure connection, to ensure the integrity of the data being transmitted.
• the user operation data recorder and vehicle operation data recorder may be configured to upload data to the backup unit periodically at pre-set intervals. Alternatively or in combination, data may be uploaded to the backup unit when vehicle operation has encountered one or more exceptional conditions, as described in further detail herein.
• the communication module 520 may be configured to provide the received data to a memory 555, the memory 555 comprising a database for storing the operation data.
• the database may be configured to store the operation data of a plurality of remote controllers and/or a plurality of remotely controlled vehicles.
• the memory 555 may comprise a plurality of memory units, each configured to store the operation data of each of the plurality of remote controllers or remotely controlled vehicles.
• the database may comprise a plurality of component databases, each configured to store the operation data of each of the plurality of remote controllers or remotely controlled vehicles.
• the database can provide back-up storage for the operation data, to prevent loss of the data in case one or more of the user operation data recorder and vehicle operation data recorder are compromised.
• the recorded user operation data and/or the vehicle operation data are accessible for retrieval only by users having special privileges or authorization.
• Users having special privileges or authorization may include a governmental agency or an operator authorized by the government.
• the authorized users may be a government-appointed law enforcement entity, retrieving the recorded operation history data for the purpose of conducting an investigation related to an incident of the remotely controlled vehicle entering a restricted area without authorization.
• the user operation data recorder and/or vehicle operation data recorder may be configured to have one or more settings that can be modified by users having special privileges or authorization.
• the user operation data recorder or vehicle operation data recorder may be configured to enter one or more special operation modes based on the occurrence of one or more particular operation conditions of the remotely controlled vehicle, or based on a particular behavior of the remotely controlled vehicle.
• the users having special privileges or authorization may have the ability to issue instructions to the user operation data recorder and/or the vehicle operation data recorder to change the operation mode.
• the user operation data recorder and/or vehicle operation data recorder may be configured to enter an “accident mode” when the recorders are alerted of the occurrence of one or more exceptional conditions in the operation of the remotely controlled vehicle 300 as described herein (e.g., vehicle collision, deviation of the traveled path of a vehicle from the projected path, etc.).
• the one or more exceptional conditions may be detected by one or more of the remote controller, the remotely controlled vehicle, and the analysis unit. Accordingly, one or more of the remote controller, the remotely controlled vehicle, and the analysis unit may generate an alert that is sent to the user operation data recorder and/or the vehicle operation data recorder.
• a system in package (SIP) technology may be used to integrate the user operation data recorder or the vehicle operation data recorder with the respective processing unit in one package.
• SIP system in package
• multiple functional chips of a processing unit may be packaged together with the memory of the data recorder, such that the package performs a complete function. An attempt to separate the memory from its package can destroy the functioning of the other modules in the package, resulting in a disabled remote controller or remotely controlled vehicle.
• chip-on-board (COB) technology may be used to integrate the user operation data recorder or vehicle operation data recorder with its respective processing unit, wherein each of the memories is adhered to an interconnection substrate and wire-bonded to achieve electrical connection.
• COB chip-on-board
• An attempt to remove the memory from the interconnection substrate can compromise the physical integrity of the memory, thus preventing a user from accessing the data recorded in the memory.
• an attempt to remove the memory from the interconnection substrate may not harm the integrity of the data stored in the memory, but destroy the functioning of other modules adhered to the same interconnection substrate, rendering the remote controller or the remotely controlled vehicle inoperable.
• Such a configuration may allow a user to retrieve the recorded data for analysis, though preferably the data is not accessible for modification.
• the user operation data recorder or the vehicle operation data recorder may be integrated via software with the processing unit of the remote controller or the remotely controlled vehicle.
• a processing unit may be implemented with a software version that corresponds to a unique identity of the user operation data recorder or the vehicle data operation recorder, respectively, such that regular operation of the software of the processing unit requires obtaining the unique identity of the user operation data recorder or the vehicle operation data recorder.
• the unique identity of either data recorder may be configured to be destroyed with a detected attempt to tamper with the data recorder, such that the software of the processing unit for the remote controller or the remotely controlled vehicle becomes inoperable thereafter.
• the user operation data recorder or the vehicle operation data recorder may further comprise a housing, configured to receive the memory of each recorder.
• the housing may be removable from the remote controller or from the remotely controlled vehicle, for the retrieval of the user operation data or the vehicle operation data.
• the housing is configured to be more resistant to destruction than the rest of the remote controller or the remotely controlled vehicle.
• the housing may comprise one or more of a shock-absorbing material, waterproof material, heatproof material, electrically insulated material, and corrosion resistant material.
• the housing may, for example, be configured to withstand an acceleration of up to 3,400 g, or an impact velocity of about 310 mph.
• the housing may be further configured to withstand temperatures over 1,000 °C.
• the housing may further comprise a tamper-evident structure, in order to discourage tampering attempts and detect any such attempts.
• the tamper-evident structure may comprise one or more labels, such as a paper label, adhered to one or more fasteners of the housing, such that an attempt to unfasten one or more of the fasteners can result in evident physical damage to the label.
• the tamper-evident structure may also comprise one or more fasteners of the housing that are coupled to an electrical circuit, such that an attempt to unfasten the one or more fastener can result in a detected change to the electrical circuit that is recorded to the memory or the processing unit of the remote controller or the remotely controlled vehicle.
• FIG. 3 is a schematic diagram of user operation data 265 recorded by a user operation data recorder, in accordance with embodiments.
• the user operation data may comprise the outgoing operation commands 270 that affect operation of a remotely controlled vehicle, wherein the outgoing operation commands are received from a user of the vehicle via a remote controller.
• the user operation data may further comprise other data related to the user or remote controller.
• the user operation data may further comprise the remote controller status data 275, which may comprise the location of the remote controller, the location of the remote controller often indicating the location of the user operating the remote controller.
• the remote controller may comprise one or more sensors configured to detect the remote controller location, such as a global positioning system (GPS) unit.
• GPS global positioning system
• the user operation data may further comprise the time 20 of recordation of each subset of data within the user operation data.
• the time may include one or more of the date, day of the week, time of day, or any other indication of time.
• Each subset of data such as a set of outgoing operation commands or the location of the remote controller, may be associated with the corresponding time.
• the “time-stamped” user operation data can provide a more complete picture of the operation history of the remotely controlled vehicle, and thereby facilitate the analysis of the operation data.
• the user operation data may further comprise an identification 305 of the remotely controlled vehicle.
• the system for recording the operation history of the remotely controlled vehicle can be configured to associate the user operation data with a unique identification of a remotely controlled vehicle, wherein the unique identification may differentiate and/or distinguish the remotely controlled vehicle from other remotely controlled vehicles, such as all other remotely controlled vehicles.
• the remotely controlled vehicle identification may, for example, comprise a unique serial number of the remotely controlled vehicle.
• the user operation data recorder may be configured to begin recording user operation data once a user is authenticated and logged in, associating the recorded data, comprising the outgoing operation commands entered into the remote controller by a specific user, with the identity of the user.
• the user operation data recorder may be further configured to end recording user operation data when the user authentication is terminated.
• the user operation data recorder may be configured to distinguish data for each user from data for other users via physical separation of the storage regions for each user’s data.
• the memory of the user operation data recorder may comprise physically separate memory components, each of which stores the user operation data for one user.
• the user operation data recorder may be configured to distinguish data for each user from data for other users via digital means.
• the memory may comprise digitally separated databases, each database storing the user operation data for one user. The association of user operation data with a user identity can provide a way to capture the contribution of each user to the recorded user operation data.
• FIG. 4 is a schematic diagram of vehicle operation data 365 recorded by a vehicle operation data recorder, in accordance with embodiments.
• the vehicle operation data may comprise incoming operation commands 370 that affect operation of a remotely controlled vehicle, wherein the incoming operation commands are received from a remote controller operated by a user of the remotely controlled vehicle.
• the remotely controlled vehicle operation data may further comprise vehicle status data 375, relating to one or more environmental parameters 385 or operation processes 380 of the remotely controlled remotely controlled vehicle.
• the remotely controlled remotely controlled vehicle may comprise one or more sensors configured to collect the remotely controlled vehicle operation data.
• one or more sensors may be coupled to one or more propulsion units of the remotely controlled remotely controlled vehicle to collect data relating to an operation process of the remotely controlled vehicle.
• the vehicle status data relating to one or more operation processes may include an acceleration of the remotely controlled vehicle, angular acceleration of the remotely controlled vehicle, speed of the remotely controlled vehicle, position of the remotely controlled vehicle, orientation of the remotely controlled vehicle relative to one, two, or three axes of rotation, location or global coordinate of the remotely controlled vehicle, altitude of the remotely controlled vehicle, a position of a remotely controlled vehicle actuator, a flap setting of an aircraft, performance of an engine, running speed of an engine, power output of an engine, a charge percentage of a battery, availability of communication networks, remotely controlled vehicle cabin pressure, and remotely controlled vehicle cabin temperature.
• one or more sensors may be coupled to an exterior portion of the remotely controlled remotely controlled vehicle, so as to collect data relating to an environmental parameter of the surrounding environment.
• Vehicle status data relating to one or more environmental parameters may include a location of the remotely controlled vehicle, outside temperature, wind speed, or detection of precipitation.
• the vehicle status data relating to an environmental parameter may comprise one or more pictures taken by the camera of the surrounding environment of the remotely controlled vehicle.
• the vehicle status data may be associated with a corresponding incoming operation command, wherein the vehicle status data results from the execution of the corresponding incoming operation command by the remotely controlled remotely controlled vehicle.
• the vehicle operation data may further comprise the time 20 of recordation of each subset of data within the vehicle operation data.
• the time may include one or more of the date, day of the week, time of day, or any other indication of time.
• Each subset of data such as a set of incoming operation commands or the vehicle status data, may be associated with the corresponding time.
• the “time-stamped” vehicle operation data can provide a more complete picture of the operation history of the remotely controlled vehicle, and thereby facilitate the analysis of the operation data.
• the user interface of the remote controller may provide a means for each user to log in to an air control system using a unique user identity and an authentication key, such as a password.
• the vehicle operation data recorder may be configured to begin recording user operation data once a user is authenticated and logged in, associating the recorded data with the identity of the user.
• the vehicle operation data recorder may be further configured to end recording vehicle operation data when the user authentication is terminated.
• the vehicle operation data recorder may be configured to distinguish data for each user from data for other users via physical separation of the storage regions for each user’s data.
• the memory of the vehicle operation data recorder may comprise physically separate memory components, each of which stores the vehicle operation data for one user.
• the vehicle operation data recorder may be configured to distinguish data for each user from data for other users via digital means.
• the memory may comprise digitally separated databases, each database storing the vehicle operation data for one user.
• FIG. 5 illustrates, by way of a block diagram, a system 600 for analyzing a behavior of a remotely controlled vehicle, in accordance with embodiments.
• the system may comprise a user operation data recorder 250 and a vehicle operation data recorder 350, as described in further detail herein.
• the user operation data recorder may be configured to record user operation data 265, comprising outgoing operation commands 270 that affect operation of the remotely controlled vehicle, the outgoing operation commands received via a remote controller from a user of the remotely controlled vehicle.
• the user operation data may further comprise remote controller status data, such as the location of the remote controller.
• the vehicle operation data recorder is configured to record vehicle operation data 365 comprising incoming operation commands 370 that affect operation of the remotely controlled vehicle, the incoming operation commands received from the remote controller by the remotely controlled vehicle.
• the vehicle operation data may further comprise vehicle status data 375, which may comprise data relating to an environmental parameter or operation process of the vehicle, as described herein.
• the system may further comprise an analysis unit as described herein, for performing an
• the user operation data and vehicle operation data are accessible for comparison, in order to identify discrepancies which may comprise (1) differences 610 between the outgoing operation commands and incoming operation commands and/or (2) differences 620 between the incoming operation commands and the vehicle status data.
• a comparison may also be performed to identify discrepancies 630 between the outgoing operation commands and the vehicle status data.
• the identified discrepancies may help to determine one or more causes of the behavior of the remotely controlled vehicle. Differences between the outgoing and incoming operation commands can help identify errors in the transmission of operation commands from the remote controller to the remotely controlled vehicle. Differences between the incoming operation commands and the vehicle status data can help identify errors in the execution of received operation commands by the remotely controlled vehicle. Differences between the outgoing operation commands and the vehicle status data can help identify errors in the execution of the operation commands as transmitted by the remote controller.
• FIG. 6 is a flowchart illustrating a method 700 for analyzing a behavior of a remotely controlled vehicle, in accordance with embodiments.
• the method may be performed using an analysis unit as described herein.
• the analysis unit receives the user operation data from the user operation data recorder, and the vehicle operation data from the vehicle operation data recorder.
• the user operation data may comprise outgoing operation commands affecting operation of the remotely controlled vehicle, transmitted from a remote controller to the remotely controlled vehicle;
• the vehicle operation data may comprise incoming operation commands received by the remotely controlled vehicle from the remote controller, as well as vehicle status data relating to one or more environmental parameters or operation processes of the vehicle.
• the user operation data and vehicle operation data are compared to identify any discrepancies. Any subset of data within the two data sets may be compared with one or more of the other subsets of data within the two data sets. For example, the outgoing operation commands from the user operation data may be compared with the vehicle status data from the vehicle operation data. Such a comparison may indicate whether any errors were present in the vehicle’s execution of the operation commands as transmitted by the remote controller, though the comparison may not provide detailed information regarding the nature of the identified errors or their cause. To gain further insight, additional comparisons between different subsets of data may be performed.
• the outgoing operation commands from the user operation data may be compared with the incoming operation commands from the vehicle operation data.
• the comparison may comprise, as in step 732, an identification of discrepancies between the two sets of data. If no discrepancies are found, in step 734, it may be determined that the operation commands were properly transmitted from remote controller to remotely controlled vehicle. If a discrepancy is identified, in step 736, it may be determined that at least a part of the cause of the vehicle behavior is an error in the transmission of the operation commands to the remotely controlled vehicle. Additional analyses may be performed to identify the type of error. For example, the analysis may find that the discrepancies comprise one or more portions of the outgoing operation commands missing from the incoming operation commands.
• Such discrepancies may indicate that the vehicle behavior may be attributed to a failure in the transmission of the outgoing operation commands from the remote controller to the vehicle.
• the discrepancies may indicate that the vehicle behavior may be attributed to a hijacking incident, wherein a hijacker has intercepted a portion of the outgoing operation commands.
• Further analyses may also find that the discrepancies comprise one or more portions of the outgoing operation commands being different from the corresponding portions of the incoming operation commands.
• Such discrepancies may indicate that the vehicle behavior is caused by an error in the transmission of the outgoing operation commands from the remote controller to the remotely controlled vehicle.
• the discrepancies may indicate the vehicle behavior was caused by a hijacking incident, wherein a hijacker has intercepted and modified a portion of the outgoing operation commands. Further analyses may also find that the discrepancies comprise one or more portions of the incoming operation commands missing from the outgoing operation commands. Such a discrepancy may indicate that the cause of the vehicle behavior may be a hijacking incident, wherein a hijacker has sent the operation commands received by the vehicle as incoming operation commands.
• the comparison 720 may further comprise step 750, wherein the incoming operation commands and the vehicle status data, both data subsets from the vehicle operation data, are compared.
• the comparison may comprise, as in step 752, an identification of discrepancies between the two sets of data. If no discrepancies are found, in step 754, it may be determined that the incoming operation commands were executed properly by the remotely controlled vehicle. If a discrepancy is identified, in step 756, it may be determined that the at least a part of the cause of the vehicle behavior is an error in the execution of the incoming operation commands by the remotely controlled vehicle. Further analysis of the discrepancies may provide additional insight regarding the nature of the identified errors. For example, a subset of the vehicle status data, generated from one sensor of the remotely controlled vehicle, may be compared with one or more other subsets of the vehicle status data, generated from other sensors of the remotely controlled vehicle.
• FIG. 7 is a table showing a method 700 for analyzing a behavior of a remotely controlled vehicle, in accordance with embodiments.
• the table summarizes some of the possible causes of the behavior of the remotely controlled vehicle, as determined by method 700.
• the possible causes summarized in FIG. 7 are provided by way of example only, and many other causes may also be possible either alternatively or in combination with one or more of the causes summarized in FIG. 7.
• the analysis performed using method 700 may identify no discrepancies between the outgoing operation commands and the incoming operation commands, and no discrepancies between the incoming operation commands and the vehicle status data.
• it may be determined the operation commands sent by the user were properly executed by the remotely controlled vehicle, and hence that the remotely controlled vehicle’s behavior was caused by the user’s commands.
• a user may have entered an input translated into outgoing operation commands comprising instructions for a UAV to enter a restricted area, causing the UAV to enter the restricted area.
• the user may be held liable for the consequences of the remotely controlled vehicle’s behavior.
• the user may have sent the operation commands unintentionally (e.g., accidentally touched wrong component of the remote controller’s user interface).
• the user may have sent the commands intentionally.
• the analysis performed using method 700 may identify a discrepancy between the outgoing operation commands and the incoming operation commands. Further analysis of the discrepancies may be performed, in order to gain further insight regarding the nature of errors, as described elsewhere herein.
• a malfunction of a communication link may comprise, for example, the loss of connectivity provided by a wireless network. Such a malfunction may lead to the failure of an outgoing operation command to reach the communication module of the remotely controlled vehicle.
• a malfunction of a communication module may comprise, for example, a mechanical or electrical failure of a communication module of the remote controller and/or the remotely controlled vehicle. Such a malfunction may lead to a failure of a remote controller to transmit the outgoing operation commands, or a failure of remotely controlled vehicle to receive the incoming operation commands.
• a hijacking incident may comprise a hijacker intercepting an outgoing operation commands, modifying an outgoing operation command, and/or sending an unauthorized operation command.
• a hijacker may intercept and/or modify an outgoing operation command comprising instructions for a landing sequence for a UAV, causing the UAV to crash or modify its flight path.
• the method for analyzing a behavior of a remotely controlled vehicle may have many applications. For example, an accident may occur with the remotely controlled vehicle, wherein the accident may comprise one or more of a remotely controlled vehicle collision, missing remotely controlled vehicle, remotely controlled vehicle entry into a restricted area, and remotely controlled vehicle conducting an illegal activity. The analysis may then be used to determine one or more possible causes of the accident, as described in detail herein.
• the information pertaining to the analysis may be used to facilitate an allocation of liabilities for the accident. For example, if a remotely controlled vehicle has collided with another remotely controlled vehicle, determining the cause of the collision may facilitate fault allocation for the collision.
• the operation data for the remotely controlled vehicles may be analyzed to determine whether the behavior of each remotely controlled vehicle was caused, for example, by user error, a malfunction of the remote controller, the remotely controlled vehicle, or a component thereof, a malfunction of a communication link between the remote controller and the remotely controlled vehicle, or a hijacking incident. If the analysis finds, for example, that the accident was caused by a malfunction of an operation process of one of the remotely controlled vehicles, the users may not be held liable for the accident. Fault may be allocated, instead, to a manufacturer of the remotely controlled vehicle or of a component of the remotely controlled vehicle.
• the allocation of liabilities may be used to determine insurance pay-outs. If a user is determined to be at fault (e.g., vehicle behavior was a result of user-entered command), the user may be personally held accountable for paying for the costs, if any, of the damage resulting from the accident. If a manufacturer of the remotely controlled vehicle or of a component of the remotely controlled vehicle is determined to be at fault, the manufacturer’s insurance may be required to cover the costs of the damage. If a third-party or environment conditions are determined to be at fault, such as a failure of a communication link, adverse weather conditions, and/or a hijacking incident, the user’s insurance and/or the manufacturer’s insurance may partially or completely cover the costs of the damage.
• the allocation of liabilities may be used to determine legal prosecution when illegal activities are identified. For example, if a remotely controlled vehicle enters a restricted area without authorization, an analysis of operation data may be performed as described herein to determine the cause of the vehicle behavior. If it is determined that the user is responsible for having entered the operation commands instructing the vehicle to enter the restricted area, the user may be prosecuted, and the operation data may be used as evidence during prosecution.
• the analysis of operation data as described herein may also help identify features of the vehicle that may need troubleshooting or improvement. For example, analysis of the operation data may show that a certain operation process of the vehicle, such as an engine function, is prone to errors leading to accidents. Information pertaining to the analysis may then be used to improve the design or manufacturing process of the component responsible for the operation process.
• a movable object of the present invention can be configured to move within any suitable environment, such as in air (e.g., a fixed-wing aircraft, a rotary-wing aircraft, or an aircraft having neither fixed wings nor rotary wings), in water (e.g., a ship or a submarine), on ground (e.g., a motor vehicle, such as a car, truck, bus, van, motorcycle; a movable structure or frame such as a stick, fishing pole; or a train), under the ground (e.g., a subway), in space (e.g., a spaceplane, a satellite, or a probe), or any combination of these environments.
• air e.g., a fixed-wing aircraft, a rotary-wing aircraft, or an aircraft having neither fixed wings nor rotary wings
• water e.g., a ship or a submarine
• ground e.g., a motor vehicle, such as a car, truck, bus, van, motorcycle
• a movable structure or frame such as
• the movable object can be a vehicle, such as a remotely controlled vehicle described elsewhere herein.
• the movable object can be mounted on a living subject, such as a human or an animal.
• Suitable animals can include avines, canines, felines, equines, bovines, ovines, porcines, delphines, rodents, or insects.
• the movable object may be capable of moving freely within the environment with respect to six degrees of freedom (e.g., three degrees of freedom in translation and three degrees of freedom in rotation). Alternatively, the movement of the movable object can be constrained with respect to one or more degrees of freedom, such as by a predetermined path, track, or orientation.
• the movement can be actuated by any suitable actuation mechanism, such as an engine or a motor.
• the actuation mechanism of the movable object can be powered by any suitable energy source, such as electrical energy, magnetic energy, solar energy, wind energy, gravitational energy, chemical energy, nuclear energy, or any suitable combination thereof.
• the movable object may be self-propelled via a propulsion system, such as described further below.
• the propulsion system may optionally run on an energy source, such as electrical energy, magnetic energy, solar energy, wind energy, gravitational energy, chemical energy, nuclear energy, or any suitable combination thereof.
• the movable object may be carried by a living being.
• the movable object can be a vehicle.
• Suitable vehicles may include water vehicles, aerial vehicles, space vehicles, or ground vehicles.
• aerial vehicles may be fixed-wing aircraft (e.g., airplane, gliders), rotary-wing aircraft (e.g., helicopters, rotorcraft), aircraft having both fixed wings and rotary wings, or aircraft having neither (e.g., blimps, hot air balloons).
• a vehicle can be self-propelled, such as self-propelled through the air, on or in water, in space, or on or under the ground.
• a self-propelled vehicle can utilize a propulsion system, such as a propulsion system including one or more engines, motors, wheels, axles, magnets, rotors, propellers, blades, nozzles, or any suitable combination thereof.
• the propulsion system can be used to enable the movable object to take off from a surface, land on a surface, maintain its current position and/or orientation (e.g., hover), change orientation, and/or change position.
• the propulsion system can include one or more rotors.
• a rotor can include one or more blades (e.g., one, two, three, four, or more blades) affixed to a central shaft.
• the blades can be disposed symmetrically or asymmetrically about the central shaft.
• the blades can be turned by rotation of the central shaft, which can be driven by a suitable motor or engine.
• the blades can be configured to spin in a clockwise rotation and/or a counterclockwise rotation.
• the rotor can be a horizontal rotor (which may refer to a rotor having a horizontal plane of rotation), a vertically oriented rotor (which may refer to a rotor having a vertical plane of rotation), or a rotor tilted at an intermediate angle between the horizontal and vertical positions.
• horizontally oriented rotors may spin and provide lift to the movable object.
• Vertically oriented rotors may spin and provide thrust to the movable object.
• Rotors oriented an intermediate angle between the horizontal and vertical positions may spin and provide both lift and thrust to the movable object.
• One or more rotors may be used to provide a torque counteracting a torque produced by the spinning of another rotor.
• the movable object can be controlled remotely by a user or controlled locally by an occupant within or on the movable object.
• the movable object is an unmanned movable object, such as a UAV.
• An unmanned movable object, such as a UAV, may not have an occupant onboard the movable object.
• the movable object can be controlled by a human or an autonomous control system (e.g., a computer control system), or any suitable combination thereof.
• the movable object can be an autonomous or semi-autonomous robot, such as a robot configured with an artificial intelligence.
• the movable object can have any suitable size and/or dimensions.
• the movable object may be of a size and/or dimensions to have a human occupant within or on the vehicle.
• the movable object may be of size and/or dimensions smaller than that capable of having a human occupant within or on the vehicle.
• the movable object may be of a size and/or dimensions suitable for being lifted or carried by a human.
• the movable object may be larger than a size and/or dimensions suitable for being lifted or carried by a human.
• the movable object may have a maximum dimension (e.g., length, width, height, diameter, diagonal) of less than or equal to about: 2 cm, 5 cm, 10 cm, 50 cm, 1 m, 2 m, 5 m, or 10 m.
• the maximum dimension may be greater than or equal to about: 2 cm, 5 cm, 10 cm, 50 cm, 1 m, 2 m, 5 m, or 10 m.
• the distance between shafts of opposite rotors of the movable object may be less than or equal to about: 2 cm, 5 cm, 10 cm, 50 cm, 1 m, 2 m, 5 m, or 10 m.
• the distance between shafts of opposite rotors may be greater than or equal to about: 2 cm, 5 cm, 10 cm, 50 cm, 1 m, 2 m, 5 m, or 10 m.
• the movable object may have a volume of less than 100 cm x 100 cm x 100 cm, less than 50 cm x 50 cm x 30 cm, or less than 5 cm x 5 cm x 3 cm.
• the total volume of the movable object may be less than or equal to about: 1 cm 3 , 2 cm 3 , 5 cm 3 , 10 cm 3 , 20 cm 3 , 30 cm 3 , 40 cm 3 , 50 cm 3 , 60 cm 3 , 70 cm 3 , 80 cm 3 , 90 cm 3 , 100 cm 3 , 150 cm 3 , 200 cm 3 , 300 cm 3 , 500 cm 3 , 750 cm 3 , 1000 cm 3 , 5000 cm 3 , 10,000 cm 3 , 100,000 cm 3 , 1 m 3 , or 10 m 3 .
• the total volume of the movable object may be greater than or equal to about: 1 cm 3 , 2 cm 3 , 5 cm 3 , 10 cm 3 , 20 cm 3 , 30 cm 3 , 40 cm 3 , 50 cm 3 , 60 cm 3 , 70 cm 3 , 80 cm 3 , 90 cm 3 , 100 cm 3 , 150 cm 3 , 200 cm 3 , 300 cm 3 , 500 cm 3 , 750 cm 3 , 1000 cm 3 , 5000 cm 3 , 10,000 cm 3 , 100,000 cm 3 , 1 m 3 , or 10 m 3 .
• the movable object may have a footprint (which may refer to the lateral cross-sectional area encompassed by the movable object) less than or equal to about: 32,000 cm 2 , 20,000 cm 2 , 10,000 cm 2 , 1,000 cm 2 , 500 cm 2 , 100 cm 2 , 50 cm 2 , 10 cm 2 , or 5 cm 2 .
• the footprint may be greater than or equal to about: 32,000 cm 2 , 20,000 cm 2 , 10,000 cm 2 , 1,000 cm 2 , 500 cm 2 , 100 cm 2 , 50 cm 2 , 10 cm 2 , or 5 cm 2 .
• the movable object may weigh no more than 1000 kg.
• the weight of the movable object may be less than or equal to about: 1000 kg, 750 kg, 500 kg, 200 kg, 150 kg, 100 kg, 80 kg, 70 kg, 60 kg, 50 kg, 45 kg, 40 kg, 35 kg, 30 kg, 25 kg, 20 kg, 15 kg, 12 kg, 10 kg, 9 kg, 8 kg, 7 kg, 6 kg, 5 kg, 4 kg, 3 kg, 2 kg, 1 kg, 0.5 kg, 0.1 kg, 0.05 kg, or 0.01 kg.
• the weight may be greater than or equal to about: 1000 kg, 750 kg, 500 kg, 200 kg, 150 kg, 100 kg, 80 kg, 70 kg, 60 kg, 50 kg, 45 kg, 40 kg, 35 kg, 30 kg, 25 kg, 20 kg, 15 kg, 12 kg, 10 kg, 9 kg, 8 kg, 7 kg, 6 kg, 5 kg, 4 kg, 3 kg, 2 kg, 1 kg, 0.5 kg, 0.1 kg, 0.05 kg, or 0.01 kg.
• a movable object may be small relative to a load carried by the movable object.
• the load may include a payload and/or a carrier, as described in further detail below.
• a ratio of an movable object weight to a load weight may be greater than, less than, or equal to about 1:1.
• a ratio of an movable object weight to a load weight may be greater than, less than, or equal to about 1:1.
• a ratio of a carrier weight to a load weight may be greater than, less than, or equal to about 1:1.
• the ratio of an movable object weight to a load weight may be less than or equal to: 1:2, 1:3, 1:4, 1:5, 1:10, or even less.
• the ratio of an movable object weight to a load weight can also be greater than or equal to: 2:1, 3:1, 4:1, 5:1, 10:1, or even greater.
• the movable object may have low energy consumption.
• the movable object may use less than about: 5 W/h, 4 W/h, 3 W/h, 2 W/h, 1 W/h, or less.
• a carrier of the movable object may have low energy consumption.
• the carrier may use less than about: 5 W/h, 4 W/h, 3 W/h, 2 W/h, 1 W/h, or less.
• a payload of the movable object may have low energy consumption, such as less than about: 5 W/h, 4 W/h, 3 W/h, 2 W/h, 1 W/h, or less.
• the length 810 can be within a range from 40 cm to 7 m, from 70 cm to 2 m, or from 5 cm to 5 m. Any description herein of a UAV may apply to a movable object, such as a movable object of a different type, and vice versa.
• the movable object can be configured to carry a load.
• the load can include one or more of passengers, cargo, equipment, instruments, and the like.
• the load can be provided within a housing.
• the housing may be separate from a housing of the movable object, or be part of a housing for a movable object.
• the load can be provided with a housing while the movable object does not have a housing.
• portions of the load or the entire load can be provided without a housing.
• the load can be rigidly fixed relative to the movable object.
• the load can be movable relative to the movable object (e.g., translatable or rotatable relative to the movable object).
• the load includes a payload.
• the payload can be configured not to perform any operation or function.
• the payload can be a payload configured to perform an operation or function, also known as a functional payload.
• the payload can include one or more sensors for surveying one or more targets. Any suitable sensor can be incorporated into the payload, such as an image capture device (e.g., a camera), an audio capture device (e.g., a parabolic microphone), an infrared imaging device, or an ultraviolet imaging device.
• the sensor can provide static sensing data (e.g., a photograph) or dynamic sensing data (e.g., a video). In some embodiments, the sensor provides sensing data for the target of the payload.
• the payload can include one or more emitters for providing signals to one or more targets. Any suitable emitter can be used, such as an illumination source or a sound source.
• the payload includes one or more transceivers, such as for communication with a module remote from the movable object.
• the payload can be configured to interact with the environment or a target.
• the payload can include a tool, instrument, or mechanism capable of manipulating objects, such as a robotic arm.
• the load may include a carrier.
• the carrier can be provided for the payload and the payload can be coupled to the movable object via the carrier, either directly (e.g., directly contacting the movable object) or indirectly (e.g., not contacting the movable object).
• the payload can be mounted on the movable object without requiring a carrier.
• the payload can be integrally formed with the carrier.
• the payload can be releasably coupled to the carrier.
• the payload can include one or more payload elements, and one or more of the payload elements can be movable relative to the movable object and/or the carrier, as described above.
• the carrier can be integrally formed with the movable object. Alternatively, the carrier can be releasably coupled to the movable object. The carrier can be coupled to the movable object directly or indirectly. The carrier can provide support to the payload (e.g., carry at least part of the weight of the payload).
• the carrier can include a suitable mounting structure (e.g., a gimbal platform) capable of stabilizing and/or directing the movement of the payload. In some embodiments, the carrier can be adapted to control the state of the payload (e.g., position and/or orientation) relative to the movable object.
• the carrier can be configured to move relative to the movable object (e.g., with respect to one, two, or three degrees of translation and/or one, two, or three degrees of rotation) such that the payload maintains its position and/or orientation relative to a suitable reference frame regardless of the movement of the movable object.
• the reference frame can be a fixed reference frame (e.g., the surrounding environment).
• the reference frame can be a moving reference frame (e.g., the movable object, a payload target).
• the carrier can be configured to permit movement of the payload relative to the carrier and/or movable object.
• the movement can be a translation with respect to up to three degrees of freedom (e.g., along one, two, or three axes) or a rotation with respect to up to three degrees of freedom (e.g., about one, two, or three axes), or any suitable combination thereof.
• the carrier actuation assembly can actuate a rotation of one or more carrier frame components about one or more axes of rotation (e.g., roll axis, pitch axis, or yaw axis).
• the rotation of the one or more carrier frame components can cause a payload to rotate about one or more axes of rotation relative to the movable object.
• the carrier actuation assembly can actuate a translation of one or more carrier frame components along one or more axes of translation, and thereby produce a translation of the payload along one or more corresponding axes relative to the movable object.
• the movement of the movable object, carrier, and payload relative to a fixed reference frame (e.g., the surrounding environment) and/or to each other, can be controlled by a terminal.
• the terminal can be a remote control device at a location distant from the movable object, carrier, and/or payload.
• the terminal can be disposed on or affixed to a support platform.
• the terminal can be a handheld or wearable device.
• the terminal can include a smartphone, tablet, laptop, computer, glasses, gloves, helmet, microphone, or suitable combinations thereof.
• the terminal can include a user interface, such as a keyboard, mouse, joystick, touchscreen, or display. Any suitable user input can be used to interact with the terminal, such as manually entered commands, voice control, gesture control, or position control (e.g., via a movement, location or tilt of the terminal).
• the terminal can include a suitable display unit for viewing information of the movable object, carrier, and/or payload.
• the terminal can be configured to display information of the movable object, carrier, and/or payload with respect to position, translational velocity, translational acceleration, orientation, angular velocity, angular acceleration, or any suitable combinations thereof.
• the terminal can display information provided by the payload, such as data provided by a functional payload (e.g., images recorded by a camera or other image capturing device).
• a first terminal may be used to control the positioning of the payload relative to an environment while a second terminal displays image data captured by the payload.
• Various communication modes may be utilized between a movable object and an integrated terminal that both controls the movable object and receives data, or between the movable object and multiple terminals that both control the movable object and receives data.
• at least two different communication modes may be formed between the movable object and the terminal that both controls the movable object and receives data from the movable object.
• FIG. 9 illustrates a movable object 900 including a carrier 902 and a payload 904, in accordance with embodiments.
• the movable object 900 is depicted as an aircraft, this depiction is not intended to be limiting, and any suitable type of movable object can be used, as previously described herein.
• any of the embodiments described herein in the context of aircraft systems can be applied to any suitable movable object (e.g., an UAV).
• the payload 904 may be provided on the movable object 900 without requiring the carrier 902.
• the movable object 900 may include propulsion mechanisms 906, a sensing system 908, and a communication system 910.
• the propulsion mechanisms 906 can include one or more of rotors, propellers, blades, engines, motors, wheels, axles, magnets, or nozzles, as previously described herein.
• the movable object may have one or more, two or more, three or more, or four or more propulsion mechanisms.
• the propulsion mechanisms may all be of the same type. Alternatively, one or more propulsion mechanisms can be different types of propulsion mechanisms.
• the propulsion mechanisms 906 can enable the movable object 900 to take off vertically from a surface or land vertically on a surface without requiring any horizontal movement of the movable object 900 (e.g., without traveling down a runway).
• the propulsion mechanisms 906 can be operable to permit the movable object 900 to hover in the air at a specified position and/or orientation.
• the rotation rate of each of the horizontally oriented rotors can be varied independently in order to control the lift and/or thrust produced by each rotor, and thereby adjust the spatial disposition, velocity, and/or acceleration of the movable object 900 (e.g., with respect to up to three degrees of translation and up to three degrees of rotation).
• the terminal 912 can provide control data to one or more of the movable object 900, carrier 902, and payload 904 and receive information from one or more of the movable object 900, carrier 902, and payload 904 (e.g., position and/or motion information of the movable object, carrier or payload; data sensed by the payload such as image data captured by a payload camera).
• control data from the terminal may include instructions for relative positions, movements, actuations, or controls of the movable object, carrier and/or payload.
• the movable object 900 can be configured to communicate with another remote device in addition to the terminal 912, or instead of the terminal 912.
• the terminal 912 may also be configured to communicate with another remote device as well as the movable object 900.
• the movable object 900 and/or terminal 912 may communicate with another movable object, or a carrier or payload of another movable object.
• the remote device may be a second terminal or other computing device (e.g., computer, laptop, tablet, smartphone, or other mobile device).
• the remote device can be configured to transmit data to the movable object 900, receive data from the movable object 900, transmit data to the terminal 912, and/or receive data from the terminal 912.
• the remote device can be connected to the Internet or other telecommunications network, such that data received from the movable object 900 and/or terminal 912 can be uploaded to a website or server.

Landscapes

• Physics & Mathematics (AREA)
• General Physics & Mathematics (AREA)
• Selective Calling Equipment (AREA)
• Telephonic Communication Services (AREA)
• Testing And Monitoring For Control Systems (AREA)
• Traffic Control Systems (AREA)

Applications Claiming Priority (1)

Publications (2)

Family

ID=57006523

Family Applications (1)

Country Status (4)

Families Citing this family (8)

Family Cites Families (26)

• 2015
  • 2015-03-31 JP JP2017544761A patent/JP6590937B2/ja active Active
  • 2015-03-31 CN CN201580033926.3A patent/CN106462160B/zh not_active Expired - Fee Related
  • 2015-03-31 WO PCT/CN2015/075615 patent/WO2016154938A1/en active Application Filing
  • 2015-03-31 EP EP15874403.7A patent/EP3155492A4/de not_active Withdrawn

Also Published As

Similar Documents

Legal Events