US20200149845A1 - Seamless smart munitions system and method - Google Patents
Seamless smart munitions system and method Download PDFInfo
- Publication number
- US20200149845A1 US20200149845A1 US16/410,705 US201916410705A US2020149845A1 US 20200149845 A1 US20200149845 A1 US 20200149845A1 US 201916410705 A US201916410705 A US 201916410705A US 2020149845 A1 US2020149845 A1 US 2020149845A1
- Authority
- US
- United States
- Prior art keywords
- munition
- link
- coordinates
- network
- smart
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
- 238000000034 method Methods 0.000 title claims abstract description 39
- 230000008685 targeting Effects 0.000 claims abstract description 31
- 238000004891 communication Methods 0.000 description 10
- 230000008569 process Effects 0.000 description 9
- 238000010200 validation analysis Methods 0.000 description 6
- 238000005516 engineering process Methods 0.000 description 5
- 238000012545 processing Methods 0.000 description 5
- 230000005540 biological transmission Effects 0.000 description 3
- 238000006243 chemical reaction Methods 0.000 description 3
- 239000004570 mortar (masonry) Substances 0.000 description 3
- 230000003287 optical effect Effects 0.000 description 3
- 230000008901 benefit Effects 0.000 description 2
- 238000010586 diagram Methods 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 230000004044 response Effects 0.000 description 2
- 230000003068 static effect Effects 0.000 description 2
- 230000002459 sustained effect Effects 0.000 description 2
- 238000007792 addition Methods 0.000 description 1
- 230000004931 aggregating effect Effects 0.000 description 1
- 230000027455 binding Effects 0.000 description 1
- 238000009739 binding Methods 0.000 description 1
- 230000001413 cellular effect Effects 0.000 description 1
- 238000004590 computer program Methods 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 230000009365 direct transmission Effects 0.000 description 1
- 230000006870 function Effects 0.000 description 1
- 230000003116 impacting effect Effects 0.000 description 1
- 230000000977 initiatory effect Effects 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 231100000225 lethality Toxicity 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 230000006855 networking Effects 0.000 description 1
- 238000007781 pre-processing Methods 0.000 description 1
- 244000062645 predators Species 0.000 description 1
- 238000012549 training Methods 0.000 description 1
Images
Classifications
-
- F—MECHANICAL ENGINEERING; LIGHTING; HEATING; WEAPONS; BLASTING
- F41—WEAPONS
- F41G—WEAPON SIGHTS; AIMING
- F41G3/00—Aiming or laying means
- F41G3/02—Aiming or laying means using an independent line of sight
-
- F—MECHANICAL ENGINEERING; LIGHTING; HEATING; WEAPONS; BLASTING
- F41—WEAPONS
- F41G—WEAPON SIGHTS; AIMING
- F41G7/00—Direction control systems for self-propelled missiles
- F41G7/20—Direction control systems for self-propelled missiles based on continuous observation of target position
- F41G7/30—Command link guidance systems
- F41G7/301—Details
-
- F—MECHANICAL ENGINEERING; LIGHTING; HEATING; WEAPONS; BLASTING
- F41—WEAPONS
- F41G—WEAPON SIGHTS; AIMING
- F41G3/00—Aiming or laying means
- F41G3/04—Aiming or laying means for dispersing fire from a battery ; for controlling spread of shots; for coordinating fire from spaced weapons
-
- F—MECHANICAL ENGINEERING; LIGHTING; HEATING; WEAPONS; BLASTING
- F41—WEAPONS
- F41G—WEAPON SIGHTS; AIMING
- F41G7/00—Direction control systems for self-propelled missiles
- F41G7/20—Direction control systems for self-propelled missiles based on continuous observation of target position
- F41G7/22—Homing guidance systems
- F41G7/2206—Homing guidance systems using a remote control station
-
- F—MECHANICAL ENGINEERING; LIGHTING; HEATING; WEAPONS; BLASTING
- F41—WEAPONS
- F41G—WEAPON SIGHTS; AIMING
- F41G7/00—Direction control systems for self-propelled missiles
- F41G7/20—Direction control systems for self-propelled missiles based on continuous observation of target position
- F41G7/22—Homing guidance systems
- F41G7/2233—Multimissile systems
-
- F—MECHANICAL ENGINEERING; LIGHTING; HEATING; WEAPONS; BLASTING
- F41—WEAPONS
- F41G—WEAPON SIGHTS; AIMING
- F41G7/00—Direction control systems for self-propelled missiles
- F41G7/20—Direction control systems for self-propelled missiles based on continuous observation of target position
- F41G7/22—Homing guidance systems
- F41G7/2273—Homing guidance systems characterised by the type of waves
- F41G7/2293—Homing guidance systems characterised by the type of waves using electromagnetic waves other than radio waves
-
- F—MECHANICAL ENGINEERING; LIGHTING; HEATING; WEAPONS; BLASTING
- F41—WEAPONS
- F41G—WEAPON SIGHTS; AIMING
- F41G7/00—Direction control systems for self-propelled missiles
- F41G7/20—Direction control systems for self-propelled missiles based on continuous observation of target position
- F41G7/30—Command link guidance systems
-
- F—MECHANICAL ENGINEERING; LIGHTING; HEATING; WEAPONS; BLASTING
- F41—WEAPONS
- F41G—WEAPON SIGHTS; AIMING
- F41G7/00—Direction control systems for self-propelled missiles
- F41G7/20—Direction control systems for self-propelled missiles based on continuous observation of target position
- F41G7/30—Command link guidance systems
- F41G7/301—Details
- F41G7/308—Details for guiding a plurality of missiles
-
- F—MECHANICAL ENGINEERING; LIGHTING; HEATING; WEAPONS; BLASTING
- F41—WEAPONS
- F41G—WEAPON SIGHTS; AIMING
- F41G7/00—Direction control systems for self-propelled missiles
- F41G7/34—Direction control systems for self-propelled missiles based on predetermined target position data
Definitions
- Embodiments of the present invention generally relate to systems and methods for providing targeting support for munitions, and more specifically for providing a seamless logistics network supporting munitions deployment.
- surveillance networks such as unmanned air vehicle (“UAV”) fleets provide targeting information for guiding munitions to a target. It is often the case that targeting information is analyzed and relayed manually from the surveillance network to a munitions deployment team, which may guide deployed munitions through a munitions network, which is separate from the surveillance network.
- UAV unmanned air vehicle
- Embodiments of the present invention generally relate to systems and methods for providing targeting support for munitions, and more specifically for providing an automated logistics network supporting munitions deployment.
- a method includes establishing a link between one or more unmanned aerial vehicles and a smart munition, transmitting, over the link, coordinates to the smart munition, programming the smart munition with targeting information including at least in part the coordinates, and deploying the smart munition based on the programming.
- the link further includes a connection over a common wireless network and the smart munition comprising a munition with a radio receiver.
- the link is established through a control box including a radio, processor, and virtual core network.
- the grid coordinates are for a Military Grid Reference System (MGRS).
- MGRS Military Grid Reference System
- the method further includes transmitting, from the one or more unmanned aerial vehicles to the smart munition and over the link, metadata.
- the coordinates are grid coordinates.
- the network is a combination of one or more dynamic mesh networks and one or more hub and spoke networks.
- the method further includes validating the smart munition by checking for a device entry in a database.
- FIG. 1A is an illustration of an example operating environment for providing targeting support for munitions, in accordance with various embodiments of the subject technology
- FIG. 1B is an illustration of an example system for providing targeting support for munitions, in accordance with various embodiments of the subject technology
- FIG. 2A is flowchart for an example method of providing targeting support for munitions, in accordance with various embodiments of the subject technology
- FIG. 2B is a method flowchart for generating targeting information for a munitions guidance system, in accordance with various embodiments of the subject technology.
- FIG. 3 is an example system which may implement the systems and methods discussed herein, in accordance with various embodiments of the subject technology.
- COT data may be provided to the munitions over a wireless network and, in some examples, may provide continuous updates to munitions prior to and during deployment (e.g., on route to a target, etc.).
- munitions may be “smart” and include onboard processing and/or a sustained and responsive linkage over the wireless network to COT providers and/or controllers. Furthermore, smart munitions may adjust their flight paths based on the sustained linkage.
- munitions receive preprogrammed instructions, such as targeting directives, prior to deployment.
- preprogrammed targeting directives may be manually entered and are susceptible to human error. Manual entry also takes substantial time during which an intended target may move or respond and/or preemptively attack the munitions launch point, thus causing an increased likelihood of friendly casualties and/or increasing collateral damage or miss rates by the deployed munitions.
- Systems and methods disclosed herein can shorten a “kill chain,” or time between acquiring telemetry on a target and impacting a munition on the target, and thus increase the likelihood of first round hits, increase the lethality of munitions hits, and reduce a target's freedom of movement and/or ability to exit a “kill zone,” or an area to which the munitions are deployed.
- a typical targeting solution for mortar rounds can take approximately four minutes to deploy effectively to a target (e.g., a four-minute kill chain).
- the systems and methods disclosed herein can provide an approximately 15-second kill chain for deploying effective mortar rounds to a target.
- the amount of time necessary for training indirect fires (e.g., mortar, artillery, and the like) personnel may be reduced due to the system offloading logistics processing from human personnel to the systems and methods disclosed herein and so provide efficiency advantages over, for example, near-peer adversaries.
- UAV can communicate with each other and with the munitions via a common network architecture.
- the common network architecture may include one or more secured channels, VPNs, encryption layers, and the like.
- Software defined radios may provide for any band to be used for the common network architecture.
- Bands can be selected based on operation parameters, such as, without imputing limitation, target distance, terrain, complexity of resolving a targeting solution, and the like.
- bands may include 4G, LTE, 5G, Mobile Ad-Hoc Network (“MANET”) L, S, and/or C bands, and/or any other radio waveform applied to military requirements.
- MANET Mobile Ad-Hoc Network
- Metadata may be delivered over the common network architecture to the munitions.
- a group communication system (“GCS”) may receive metadata from UAV and other targeting sensors over the common network architecture and transmit the metadata and/or derived information based on the metadata to a smart munition.
- Metadata can include, for example and without imputing limitation, 8-10 digit grid coordinate values for each of target position, UAV airspeed, altitude, position, flight pattern, and/or other flight characteristic information that may have bearing on indirect fires (e.g., munitions deployment), digital terrain information such as terrain elevation, geography, and/or other terrain information that may have bearing on direct or indirect fires, time of day, temperature, and/or other weather information.
- the smart munitions and/or the GCS cause the metadata to resolve targets at the point of munition launch and thus widen a span of usability of a window of opportunity to strike.
- the GCS can aggregate data from multiple sources and formats to provide up-to-date targeting information and/or resolution to a linked smart munition. Metadata from UAV and other sources can be broadcast to the entire network in a continuous update stream and processed by the GCS and/or munition control interfaces.
- a UAV can track a moving vehicle, providing to the network a continuously updating stream of 10-digit Military Grid Reference System (“MGRS”) coordinates related to the vehicle position.
- MGRS Military Grid Reference System
- the GCS may use the continuously updating stream to resolve a target for a munition pre-deployment and/or link the munitions to the updating stream.
- the munition may make flight adjustments post-deployment (e.g., in-flight) in response to the linked continuously updating stream from the UAV in order to successfully deploy to the tracked moving vehicle.
- FIG. 1A and FIG. 2A depict smart munitions operating environment 100 and munitions targeting method 200 , respectively.
- Smart munitions operating environment 100 can include a network across which sensor systems and munitions may communicate, demarcated here as a sensors side network portion 101 A and a munitions side network portion 101 B.
- a link between a UAV 102 , or other COT capable sensor system, and a munition 108 can be established across the network (operation 202 ).
- a validation and/or authentication process may occur to ensure that only authorized munitions and COT capable sensor systems interact.
- the validation may include checking a database or other data storage for credential information (e.g., device identification and the like).
- While the network is depicted here as demarcated into two sides, it will be understood by a person having ordinary skill in the art that various network architectures may provide a communications plane within smart munitions operating environment 100 .
- UAV may communicate directly with munitions
- multiple subnetworks may be included along with aggregating receivers, and other configurations as will be apparent to a person having ordinary skill in the art may be utilized over smart munitions operating environment 100 as a communications plane.
- UAV 102 acquires COT metadata for a target, such as 10-digit MGRS information, through sensors onboard UAV 102 (operation 204 ).
- the COT metadata may be associated with particular targets 104 which may, in some examples, be identified by onboard UAV 102 systems such as computer vision, targeting systems, and the like.
- a remote processor or service may provide target identification and tracking for UAV 102 .
- UAV 102 transmits COT metadata referencing targets 104 to a GCS 106 via network portion 101 A for downstream provision of the COT metadata to munition 108 (operation 206 ).
- GCS 106 may further process the received COT metadata.
- multiple UAVs may transmit COT metadata which can be aggregated into a higher resolution target.
- other sensors including, without imputing limitation, ground-based sensors can transmit COT metadata to GCS 106 .
- the transmission may be a network-wide transmission or may be a direct transmission. In both cases, the transmission can be encrypted and include other credentialing data (e.g., such as a transmitter identifier and the like).
- GCS 106 having received COT metadata from UAV 102 , may transmit all or a portion of the received COT metadata to munition 108 (linked to UAV 102 ) via network portion 101 B.
- multiple munitions may be linked to UAV 102 through either a direct peer-to-peer linkage or via GCS 106 .
- GCS 106 can initially link UAV 102 and munition 108 , which may thereafter communicate directly with each other over a shared network.
- Munition 108 can then be deployed to targets 104 using the received COT metadata (operation 208 ).
- Munition 108 can further include an onboard computer and/or radio receiver (not depicted).
- the radio receiver may be a programmable software radio included as part of, or in addition to, the onboard computer.
- Munition 108 may receive additional updates from UAV 102 or GCS 106 while in-flight to targets 104 .
- Munition 108 can then use the additional updates to adjust a flight trajectory and the like in order to increase the chance of successfully striking targets 104 .
- the in-flight updates may comprise COT metadata similarly to above.
- GCS 106 may preprocess the COT metadata in order to provide streamlined data to munition 108 so as to hasten in-flight computing.
- UAV 102 may provide COT metadata directly to munition 108 over a shared network so as to reduce latency and increase accuracy of the provided COT metadata as the munition travels to targets 104 .
- FIG. 1B is a block diagram depicting a smart munitions targeting system 150 which seamless connects a surveillance network 152 and a munitions network 154 to provide rapid target resolution and support.
- smart munitions targeting system 150 may be deployed in smart munitions operating environment 100 discussed above in reference to FIG. 1A .
- surveillance network 152 and munitions network 154 are depicted here as distinct networks, it is understood that this is for explanatory purposes only and, in some examples, surveillance network 152 and munitions network 154 may be sub-networks or abstracted segregated network traffic flows of a larger shared network or the like.
- surveillance network 152 and munitions network 154 may operate over any medium as will be understood by a person having ordinary skill in the art. For example, networking may be performed over LTE mobile network protocols and bands, radio frequency, cellular, 4G, 5G, WiFi, sonic, optical, etc. and can transmit logistics and other data between network endpoints.
- surveillance network 152 includes a fleet of one or more UAVs 151 in communication with a UAV ground controller and/or each other.
- UAVs 151 may all be the same type UAV (e.g., predator drone, etc.) communicating over a dedicated network.
- the fleet of UAVs 151 may include multiple types of drones within a shared control group and may communicate with each other via the ground controller or the like.
- UAV 151 A may generate targeting (e.g., COT, etc.) metadata by identifying and/or tracking a munitions target based on onboard (e.g., autopilot, vision and tracking modules, etc.) processes and/or ground-based (e.g., remote pilot, etc.) processes. Nevertheless, UAV 151 A transmits targeting metadata to a logistics conduit system 156 for deploying munitions to the munitions target.
- Logistics conduit system 156 includes a radio 160 A for interfacing with surveillance network 152 and a radio 160 B for interfacing with munitions network 154 .
- radios 160 A-B can be software radios or may include one or more additional radios.
- Munitions networks 154 includes a communications network or mesh between one or more munitions 155 and a ground munitions controller.
- each munition 155 communicates with logistics conduit system 156 for deploying and guiding respective munitions 155 .
- a munition 155 A has established a link with logistics conduit system 156 via radio 160 B to receive appropriate targeting metadata for deploying munition 155 A to a tracked target, etc.
- Logistics conduit system 156 receives targeting metadata from surveillance network 152 and provides appropriate targeting and guidance data to munition 155 A based on the received target metadata. Received metadata is provided to a control box 158 for further processing. In some examples, logistics conduit system 156 may include preprocessing and or analytic processes (not depicted) for processing the received metadata prior to being provided to control box 158 .
- Control box 158 includes a metadata exchange process 162 for converting metadata received from surveillance network 152 to a format actionable by one or more munitions 155 (e.g., munition 155 A).
- conversion processes and/or functions may be retrieved from an external data store (not depicted) or from a dedicated store within logistics conduit system 156 .
- Control box 158 further includes an internal core network 161 which may include, for example and without imputing limitation, one or more virtual networks and/or virtual network endpoints.
- internal core network 161 may bind together surveillance network 152 and munitions network 154 .
- Internal core network 161 may include endpoint bindings, via radios 160 A-B, to surveillance network 152 and/or munitions network 154 .
- logistics conduit system 156 may communicate with a validation data store 165 to validate an identity of munition 155 A and/or UAV 151 A.
- validation data store 165 may further store conversion schema or the like for metadata exchange process 162 .
- metadata exchange process 162 may retrieve the conversion schema based on a retrieved identity of UAV 151 A and munitions 155 A.
- Validation data store 165 may include one or more databases 166 for storing, managing, and retrieving data.
- FIG. 2B is a method 250 for guiding a munition based on targeting data provided by a targeting (e.g., COT) system. While method 250 is depicted as initiating from step 252 , in some examples method 250 may initiate from step 256 following step 206 of method 200 discussed above in reference to FIG. 2A .
- a targeting e.g., COT
- a format is identified for metadata received from a COT system.
- the format may be identified implicitly (e.g., based on a parsing of its structure) or may be identified via an identifier or the like retrieved from a providing UAV or associated with the metadata in a data store.
- a munition is validated by identifying a device entry in a data store.
- the munition may be identified by the metadata, such as by a destination field or the like.
- the munition may be identified and validated prior to UAV or COT system deployment.
- the munition may be required to be validated before respectively provided metadata is used for deploying and/or guiding a munition.
- a munitions communication protocol and data formats for the validated munition are identified.
- munitions communication protocol may be preselected from a selection prior to UAV and/or COT system deployment.
- munitions communication may be select dynamically or quasi-dynamically based on munitions identification information.
- COT metadata is received for a target.
- the COT metadata may be received directly from a UAV, such as UAV 151 discussed above in reference to FIG. 1B .
- the COT metadata may be preprocessed to identify appropriate formats and/or perform validation procedures.
- a munition control data package conforming to the munition communication protocol and data formats based on the received metadata is generated.
- the munition communication protocol may be identified based on a munition identifier such as that used to validate the munition at step 254 .
- the munition control data package is transmitted to the validated munition for guiding the munition to the target.
- the munition control data package may be transmitted directly the validated munition for receipt by onboard controllers.
- the munition control data package can be transmitted to an interim deployment control terminal for automatically providing downstream to the validated munitions.
- FIG. 3 is a block diagram illustrating an example of a computing device or computer system 300 which may be used in implementing the embodiments of the components of the systems and methods disclosed above.
- the computing system 300 of FIG. 3 may be logistics conduit system 156 discussed above.
- the computer system (system) includes one or more processors 302 - 306 .
- Processors 302 - 306 may include one or more internal levels of cache (not shown) and a bus controller or bus interface unit to direct interaction with the processor bus 312 .
- Processor bus 312 also known as the host bus or the front side bus, may be used to couple the processors 302 - 306 with the system interface 314 .
- System interface 314 may be connected to the processor bus 312 to interface other components of the system 300 with the processor bus 312 .
- system interface 314 may include a memory controller 314 for interfacing a main memory 316 with the processor bus 312 .
- the main memory 316 typically includes one or more memory cards and a control circuit (not shown).
- System interface 314 may also include an input/output (I/O) interface 320 to interface one or more I/O bridges or I/O devices with the processor bus 312 .
- I/O controllers and/or I/O devices may be connected with the I/O bus 326 , such as I/O controller 328 and I/O device 340 , as illustrated.
- I/O device 340 may also include an input device (not shown), such as an alphanumeric input device, including alphanumeric and other keys for communicating information and/or command selections to the processors 302 - 306 .
- an input device such as an alphanumeric input device, including alphanumeric and other keys for communicating information and/or command selections to the processors 302 - 306 .
- cursor control such as a mouse, a trackball, or cursor direction keys for communicating direction information and command selections to the processors 302 - 306 and for controlling cursor movement on the display device.
- System 300 may include a dynamic storage device, referred to as main memory 316 , or a random access memory (RAM) or other computer-readable devices coupled to the processor bus 312 for storing information and instructions to be executed by the processors 302 - 306 .
- Main memory 316 also may be used for storing temporary variables or other intermediate information during execution of instructions by the processors 302 - 306 .
- System 300 may include a read only memory (ROM) and/or other static storage device coupled to the processor bus 312 for storing static information and instructions for the processors 302 - 306 .
- ROM read only memory
- FIG. 3 is but one possible example of a computer system that may employ or be configured in accordance with aspects of the present disclosure.
- the above techniques may be performed by computer system 300 in response to processor 304 executing one or more sequences of one or more instructions contained in main memory 316 . These instructions may be read into main memory 316 from another machine-readable medium, such as a storage device. Execution of the sequences of instructions contained in main memory 316 may cause processors 302 - 306 to perform the process steps described herein. In alternative embodiments, circuitry may be used in place of or in combination with the software instructions. Thus, embodiments of the present disclosure may include both hardware and software components.
- a machine readable medium includes any mechanism for storing or transmitting information in a form (e.g., software, processing application) readable by a machine (e.g., a computer). Such media may take the form of, but is not limited to, non-volatile media and volatile media. Non-volatile media includes optical or magnetic disks. Volatile media includes dynamic memory, such as main memory 316 .
- Machine-readable medium may include, but is not limited to, magnetic storage medium (e.g., floppy diskette); optical storage medium (e.g., CD-ROM); magneto-optical storage medium; read only memory (ROM); random access memory (RAM); erasable programmable memory (e.g., EPROM and EEPROM); flash memory; or other types of medium suitable for storing electronic instructions.
- magnetic storage medium e.g., floppy diskette
- optical storage medium e.g., CD-ROM
- magneto-optical storage medium e.g., magneto-optical storage medium
- ROM read only memory
- RAM random access memory
- EPROM and EEPROM erasable programmable memory
- flash memory or other types of medium suitable for storing electronic instructions.
- Embodiments of the present disclosure include various steps, which are described in this specification. The steps may be performed by hardware components or may be embodied in machine-executable instructions, which may be used to cause a general-purpose or special-purpose processor programmed with the instructions to perform the steps. Alternatively, the steps may be performed by a combination of hardware, software and/or firmware.
Abstract
Description
- This application is related to and claims priority under 35 U.S.C. § 119(e) from U.S. Patent Application No. 62/670,415, filed May 11, 2018, the entire contents of which is incorporated herein by reference for all purposes.
- Embodiments of the present invention generally relate to systems and methods for providing targeting support for munitions, and more specifically for providing a seamless logistics network supporting munitions deployment.
- In battlefield situations, it is typically the case that surveillance networks, such as unmanned air vehicle (“UAV”) fleets provide targeting information for guiding munitions to a target. It is often the case that targeting information is analyzed and relayed manually from the surveillance network to a munitions deployment team, which may guide deployed munitions through a munitions network, which is separate from the surveillance network.
- Embodiments of the present invention generally relate to systems and methods for providing targeting support for munitions, and more specifically for providing an automated logistics network supporting munitions deployment.
- In one embodiment, a method includes establishing a link between one or more unmanned aerial vehicles and a smart munition, transmitting, over the link, coordinates to the smart munition, programming the smart munition with targeting information including at least in part the coordinates, and deploying the smart munition based on the programming.
- In one embodiment, the link further includes a connection over a common wireless network and the smart munition comprising a munition with a radio receiver.
- In one embodiment, the link is established through a control box including a radio, processor, and virtual core network.
- In one embodiment, the grid coordinates are for a Military Grid Reference System (MGRS).
- In one embodiment, the method further includes transmitting, from the one or more unmanned aerial vehicles to the smart munition and over the link, metadata.
- In one embodiment, the coordinates are grid coordinates.
- In one embodiment, the network is a combination of one or more dynamic mesh networks and one or more hub and spoke networks.
- In one embodiment, the method further includes validating the smart munition by checking for a device entry in a database.
-
FIG. 1A is an illustration of an example operating environment for providing targeting support for munitions, in accordance with various embodiments of the subject technology; -
FIG. 1B is an illustration of an example system for providing targeting support for munitions, in accordance with various embodiments of the subject technology; -
FIG. 2A is flowchart for an example method of providing targeting support for munitions, in accordance with various embodiments of the subject technology; -
FIG. 2B is a method flowchart for generating targeting information for a munitions guidance system, in accordance with various embodiments of the subject technology; and -
FIG. 3 is an example system which may implement the systems and methods discussed herein, in accordance with various embodiments of the subject technology. - Aspects of the present disclosure involve systems, methods, computer program products, and the like, for linking organic munitions to aerial and ground-based sensor Cursor-on-Target (“COT”) data providers. COT data may be provided to the munitions over a wireless network and, in some examples, may provide continuous updates to munitions prior to and during deployment (e.g., on route to a target, etc.). In some examples, munitions may be “smart” and include onboard processing and/or a sustained and responsive linkage over the wireless network to COT providers and/or controllers. Furthermore, smart munitions may adjust their flight paths based on the sustained linkage.
- Typically, munitions receive preprogrammed instructions, such as targeting directives, prior to deployment. Furthermore, preprogrammed targeting directives may be manually entered and are susceptible to human error. Manual entry also takes substantial time during which an intended target may move or respond and/or preemptively attack the munitions launch point, thus causing an increased likelihood of friendly casualties and/or increasing collateral damage or miss rates by the deployed munitions. Systems and methods disclosed herein can shorten a “kill chain,” or time between acquiring telemetry on a target and impacting a munition on the target, and thus increase the likelihood of first round hits, increase the lethality of munitions hits, and reduce a target's freedom of movement and/or ability to exit a “kill zone,” or an area to which the munitions are deployed.
- For example, a typical targeting solution for mortar rounds can take approximately four minutes to deploy effectively to a target (e.g., a four-minute kill chain). In some examples, the systems and methods disclosed herein can provide an approximately 15-second kill chain for deploying effective mortar rounds to a target. Further, the amount of time necessary for training indirect fires (e.g., mortar, artillery, and the like) personnel may be reduced due to the system offloading logistics processing from human personnel to the systems and methods disclosed herein and so provide efficiency advantages over, for example, near-peer adversaries.
- Delivery of data from COT capable UAV to munitions can increase accuracy and speed at which munitions can be deployed to targets. While UAV are referred to in examples provided herein, it is understood that other COT capable sensor systems, such as land based radar systems and the like, may provide data to munitions as discussed below. UAV are used for explanatory purposes and are understood to be but one of many examples of COT capable sensor systems which can be used as disclosed herein. The UAV can communicate with each other and with the munitions via a common network architecture. In some examples, multiple and/or various frequency bands can be used for the common network architecture. The common network architecture may include one or more secured channels, VPNs, encryption layers, and the like.
- Software defined radios may provide for any band to be used for the common network architecture. Bands can be selected based on operation parameters, such as, without imputing limitation, target distance, terrain, complexity of resolving a targeting solution, and the like. For example, and without imputing limitation, bands may include 4G, LTE, 5G, Mobile Ad-Hoc Network (“MANET”) L, S, and/or C bands, and/or any other radio waveform applied to military requirements. While particular bands and waveforms are enumerated herein, it will be understood by a person having ordinary skill in the art with the benefit of this disclosure that the systems and methods disclosed herein are not limited to any particular band or waveform, but can include various bands or waveforms as well as legacy Radio over IP (“RoIP”) networks and the like. In some examples, multiple bands and/or switching bands may be employed for increased security and/or network stability.
- Metadata may be delivered over the common network architecture to the munitions. In one example, a group communication system (“GCS”) may receive metadata from UAV and other targeting sensors over the common network architecture and transmit the metadata and/or derived information based on the metadata to a smart munition. Metadata can include, for example and without imputing limitation, 8-10 digit grid coordinate values for each of target position, UAV airspeed, altitude, position, flight pattern, and/or other flight characteristic information that may have bearing on indirect fires (e.g., munitions deployment), digital terrain information such as terrain elevation, geography, and/or other terrain information that may have bearing on direct or indirect fires, time of day, temperature, and/or other weather information. The smart munitions and/or the GCS cause the metadata to resolve targets at the point of munition launch and thus widen a span of usability of a window of opportunity to strike.
- In some examples, the GCS can aggregate data from multiple sources and formats to provide up-to-date targeting information and/or resolution to a linked smart munition. Metadata from UAV and other sources can be broadcast to the entire network in a continuous update stream and processed by the GCS and/or munition control interfaces. For example, a UAV can track a moving vehicle, providing to the network a continuously updating stream of 10-digit Military Grid Reference System (“MGRS”) coordinates related to the vehicle position. The GCS may use the continuously updating stream to resolve a target for a munition pre-deployment and/or link the munitions to the updating stream. Further, the munition may make flight adjustments post-deployment (e.g., in-flight) in response to the linked continuously updating stream from the UAV in order to successfully deploy to the tracked moving vehicle.
-
FIG. 1A andFIG. 2A depict smartmunitions operating environment 100 andmunitions targeting method 200, respectively. Smartmunitions operating environment 100 can include a network across which sensor systems and munitions may communicate, demarcated here as a sensorsside network portion 101A and a munitionsside network portion 101B. A link between aUAV 102, or other COT capable sensor system, and amunition 108 can be established across the network (operation 202). In some examples, a validation and/or authentication process may occur to ensure that only authorized munitions and COT capable sensor systems interact. The validation may include checking a database or other data storage for credential information (e.g., device identification and the like). - While the network is depicted here as demarcated into two sides, it will be understood by a person having ordinary skill in the art that various network architectures may provide a communications plane within smart
munitions operating environment 100. For example, and without imputing limitation, UAV may communicate directly with munitions, multiple subnetworks may be included along with aggregating receivers, and other configurations as will be apparent to a person having ordinary skill in the art may be utilized over smartmunitions operating environment 100 as a communications plane. -
UAV 102 acquires COT metadata for a target, such as 10-digit MGRS information, through sensors onboard UAV 102 (operation 204). The COT metadata may be associated withparticular targets 104 which may, in some examples, be identified byonboard UAV 102 systems such as computer vision, targeting systems, and the like. In some examples, a remote processor or service may provide target identification and tracking forUAV 102. - Nevertheless,
UAV 102 transmits COTmetadata referencing targets 104 to aGCS 106 vianetwork portion 101A for downstream provision of the COT metadata to munition 108 (operation 206).GCS 106 may further process the received COT metadata. In some examples, multiple UAVs may transmit COT metadata which can be aggregated into a higher resolution target. In some examples, other sensors, including, without imputing limitation, ground-based sensors can transmit COT metadata toGCS 106. The transmission may be a network-wide transmission or may be a direct transmission. In both cases, the transmission can be encrypted and include other credentialing data (e.g., such as a transmitter identifier and the like). -
GCS 106, having received COT metadata fromUAV 102, may transmit all or a portion of the received COT metadata to munition 108 (linked to UAV 102) vianetwork portion 101B. In some examples, multiple munitions may be linked toUAV 102 through either a direct peer-to-peer linkage or viaGCS 106. In some examples,GCS 106 can initially linkUAV 102 andmunition 108, which may thereafter communicate directly with each other over a shared network. -
Munition 108 can then be deployed totargets 104 using the received COT metadata (operation 208).Munition 108 can further include an onboard computer and/or radio receiver (not depicted). The radio receiver may be a programmable software radio included as part of, or in addition to, the onboard computer.Munition 108 may receive additional updates fromUAV 102 orGCS 106 while in-flight totargets 104.Munition 108 can then use the additional updates to adjust a flight trajectory and the like in order to increase the chance of successfully strikingtargets 104. - The in-flight updates may comprise COT metadata similarly to above. In some examples,
GCS 106 may preprocess the COT metadata in order to provide streamlined data to munition 108 so as to hasten in-flight computing. In other examples,UAV 102 may provide COT metadata directly tomunition 108 over a shared network so as to reduce latency and increase accuracy of the provided COT metadata as the munition travels totargets 104. -
FIG. 1B is a block diagram depicting a smartmunitions targeting system 150 which seamless connects asurveillance network 152 and amunitions network 154 to provide rapid target resolution and support. In some examples, smartmunitions targeting system 150 may be deployed in smartmunitions operating environment 100 discussed above in reference toFIG. 1A . Whilesurveillance network 152 andmunitions network 154 are depicted here as distinct networks, it is understood that this is for explanatory purposes only and, in some examples,surveillance network 152 andmunitions network 154 may be sub-networks or abstracted segregated network traffic flows of a larger shared network or the like. Either or bothsurveillance network 152 andmunitions network 154 may operate over any medium as will be understood by a person having ordinary skill in the art. For example, networking may be performed over LTE mobile network protocols and bands, radio frequency, cellular, 4G, 5G, WiFi, sonic, optical, etc. and can transmit logistics and other data between network endpoints. - In particular,
surveillance network 152 includes a fleet of one ormore UAVs 151 in communication with a UAV ground controller and/or each other. In some examples,UAVs 151 may all be the same type UAV (e.g., predator drone, etc.) communicating over a dedicated network. In some examples, the fleet ofUAVs 151 may include multiple types of drones within a shared control group and may communicate with each other via the ground controller or the like.UAV 151A may generate targeting (e.g., COT, etc.) metadata by identifying and/or tracking a munitions target based on onboard (e.g., autopilot, vision and tracking modules, etc.) processes and/or ground-based (e.g., remote pilot, etc.) processes. Nevertheless,UAV 151A transmits targeting metadata to alogistics conduit system 156 for deploying munitions to the munitions target. -
Logistics conduit system 156 includes aradio 160A for interfacing withsurveillance network 152 and aradio 160B for interfacing withmunitions network 154. In some examples,radios 160A-B can be software radios or may include one or more additional radios. -
Munitions networks 154 includes a communications network or mesh between one ormore munitions 155 and a ground munitions controller. In some examples, eachmunition 155 communicates withlogistics conduit system 156 for deploying and guidingrespective munitions 155. Here, amunition 155A has established a link withlogistics conduit system 156 viaradio 160B to receive appropriate targeting metadata for deployingmunition 155A to a tracked target, etc. -
Logistics conduit system 156 receives targeting metadata fromsurveillance network 152 and provides appropriate targeting and guidance data tomunition 155A based on the received target metadata. Received metadata is provided to acontrol box 158 for further processing. In some examples,logistics conduit system 156 may include preprocessing and or analytic processes (not depicted) for processing the received metadata prior to being provided to controlbox 158. -
Control box 158 includes ametadata exchange process 162 for converting metadata received fromsurveillance network 152 to a format actionable by one or more munitions 155 (e.g.,munition 155A). In some examples, conversion processes and/or functions may be retrieved from an external data store (not depicted) or from a dedicated store withinlogistics conduit system 156. -
Control box 158 further includes aninternal core network 161 which may include, for example and without imputing limitation, one or more virtual networks and/or virtual network endpoints. In some examples,internal core network 161 may bind togethersurveillance network 152 andmunitions network 154.Internal core network 161 may include endpoint bindings, viaradios 160A-B, tosurveillance network 152 and/ormunitions network 154. - In some examples,
logistics conduit system 156 may communicate with avalidation data store 165 to validate an identity ofmunition 155A and/orUAV 151A. In some examples,validation data store 165 may further store conversion schema or the like formetadata exchange process 162. For example,metadata exchange process 162 may retrieve the conversion schema based on a retrieved identity ofUAV 151A andmunitions 155A.Validation data store 165 may include one ormore databases 166 for storing, managing, and retrieving data. -
FIG. 2B is amethod 250 for guiding a munition based on targeting data provided by a targeting (e.g., COT) system. Whilemethod 250 is depicted as initiating fromstep 252, in someexamples method 250 may initiate fromstep 256 followingstep 206 ofmethod 200 discussed above in reference toFIG. 2A . - At
step 252, a format is identified for metadata received from a COT system. The format may be identified implicitly (e.g., based on a parsing of its structure) or may be identified via an identifier or the like retrieved from a providing UAV or associated with the metadata in a data store. - At
step 254, a munition is validated by identifying a device entry in a data store. The munition may be identified by the metadata, such as by a destination field or the like. In some examples, the munition may be identified and validated prior to UAV or COT system deployment. In some examples, the munition may be required to be validated before respectively provided metadata is used for deploying and/or guiding a munition. - At
step 256, a munitions communication protocol and data formats for the validated munition are identified. In some examples, munitions communication protocol may be preselected from a selection prior to UAV and/or COT system deployment. In some examples, munitions communication may be select dynamically or quasi-dynamically based on munitions identification information. - At
step 258, COT metadata is received for a target. For example, the COT metadata may be received directly from a UAV, such asUAV 151 discussed above in reference toFIG. 1B . In some examples, the COT metadata may be preprocessed to identify appropriate formats and/or perform validation procedures. - At
step 260, a munition control data package conforming to the munition communication protocol and data formats based on the received metadata is generated. The munition communication protocol may be identified based on a munition identifier such as that used to validate the munition atstep 254. - At
step 262, the munition control data package is transmitted to the validated munition for guiding the munition to the target. In some examples, the munition control data package may be transmitted directly the validated munition for receipt by onboard controllers. In some examples, the munition control data package can be transmitted to an interim deployment control terminal for automatically providing downstream to the validated munitions. -
FIG. 3 is a block diagram illustrating an example of a computing device orcomputer system 300 which may be used in implementing the embodiments of the components of the systems and methods disclosed above. For example, thecomputing system 300 ofFIG. 3 may belogistics conduit system 156 discussed above. The computer system (system) includes one or more processors 302-306. Processors 302-306 may include one or more internal levels of cache (not shown) and a bus controller or bus interface unit to direct interaction with theprocessor bus 312.Processor bus 312, also known as the host bus or the front side bus, may be used to couple the processors 302-306 with the system interface 314. System interface 314 may be connected to theprocessor bus 312 to interface other components of thesystem 300 with theprocessor bus 312. For example, system interface 314 may include a memory controller 314 for interfacing amain memory 316 with theprocessor bus 312. Themain memory 316 typically includes one or more memory cards and a control circuit (not shown). System interface 314 may also include an input/output (I/O)interface 320 to interface one or more I/O bridges or I/O devices with theprocessor bus 312. One or more I/O controllers and/or I/O devices may be connected with the I/O bus 326, such as I/O controller 328 and I/O device 340, as illustrated. - I/O device 340 may also include an input device (not shown), such as an alphanumeric input device, including alphanumeric and other keys for communicating information and/or command selections to the processors 302-306. Another type of user input device includes cursor control, such as a mouse, a trackball, or cursor direction keys for communicating direction information and command selections to the processors 302-306 and for controlling cursor movement on the display device.
-
System 300 may include a dynamic storage device, referred to asmain memory 316, or a random access memory (RAM) or other computer-readable devices coupled to theprocessor bus 312 for storing information and instructions to be executed by the processors 302-306.Main memory 316 also may be used for storing temporary variables or other intermediate information during execution of instructions by the processors 302-306.System 300 may include a read only memory (ROM) and/or other static storage device coupled to theprocessor bus 312 for storing static information and instructions for the processors 302-306. The system set forth inFIG. 3 is but one possible example of a computer system that may employ or be configured in accordance with aspects of the present disclosure. - According to one embodiment, the above techniques may be performed by
computer system 300 in response toprocessor 304 executing one or more sequences of one or more instructions contained inmain memory 316. These instructions may be read intomain memory 316 from another machine-readable medium, such as a storage device. Execution of the sequences of instructions contained inmain memory 316 may cause processors 302-306 to perform the process steps described herein. In alternative embodiments, circuitry may be used in place of or in combination with the software instructions. Thus, embodiments of the present disclosure may include both hardware and software components. - A machine readable medium includes any mechanism for storing or transmitting information in a form (e.g., software, processing application) readable by a machine (e.g., a computer). Such media may take the form of, but is not limited to, non-volatile media and volatile media. Non-volatile media includes optical or magnetic disks. Volatile media includes dynamic memory, such as
main memory 316. Common forms of machine-readable medium may include, but is not limited to, magnetic storage medium (e.g., floppy diskette); optical storage medium (e.g., CD-ROM); magneto-optical storage medium; read only memory (ROM); random access memory (RAM); erasable programmable memory (e.g., EPROM and EEPROM); flash memory; or other types of medium suitable for storing electronic instructions. - Embodiments of the present disclosure include various steps, which are described in this specification. The steps may be performed by hardware components or may be embodied in machine-executable instructions, which may be used to cause a general-purpose or special-purpose processor programmed with the instructions to perform the steps. Alternatively, the steps may be performed by a combination of hardware, software and/or firmware.
- Various modifications and additions can be made to the exemplary embodiments discussed without departing from the scope of the present invention. For example, while the embodiments described above refer to particular features, the scope of this invention also includes embodiments having different combinations of features and embodiments that do not include all of the described features. Accordingly, the scope of the present invention is intended to embrace all such alternatives, modifications, and variations together with all equivalents thereof.
Claims (24)
Priority Applications (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US16/410,705 US10641582B1 (en) | 2018-05-11 | 2019-05-13 | Seamless smart munitions system and method |
US16/863,236 US11035649B2 (en) | 2018-05-11 | 2020-04-30 | Seamless smart munitions system and method |
US17/338,557 US11614307B2 (en) | 2018-05-11 | 2021-06-03 | Seamless smart munitions system and method |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US201862670415P | 2018-05-11 | 2018-05-11 | |
US16/410,705 US10641582B1 (en) | 2018-05-11 | 2019-05-13 | Seamless smart munitions system and method |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US16/863,236 Continuation US11035649B2 (en) | 2018-05-11 | 2020-04-30 | Seamless smart munitions system and method |
Publications (2)
Publication Number | Publication Date |
---|---|
US10641582B1 US10641582B1 (en) | 2020-05-05 |
US20200149845A1 true US20200149845A1 (en) | 2020-05-14 |
Family
ID=68468428
Family Applications (3)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US16/410,705 Active US10641582B1 (en) | 2018-05-11 | 2019-05-13 | Seamless smart munitions system and method |
US16/863,236 Active US11035649B2 (en) | 2018-05-11 | 2020-04-30 | Seamless smart munitions system and method |
US17/338,557 Active 2039-11-17 US11614307B2 (en) | 2018-05-11 | 2021-06-03 | Seamless smart munitions system and method |
Family Applications After (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US16/863,236 Active US11035649B2 (en) | 2018-05-11 | 2020-04-30 | Seamless smart munitions system and method |
US17/338,557 Active 2039-11-17 US11614307B2 (en) | 2018-05-11 | 2021-06-03 | Seamless smart munitions system and method |
Country Status (2)
Country | Link |
---|---|
US (3) | US10641582B1 (en) |
WO (1) | WO2019217971A1 (en) |
Families Citing this family (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2019217971A1 (en) * | 2018-05-11 | 2019-11-14 | Fenix Group, Inc. | Seamless smart munitions system and method |
US11913757B2 (en) * | 2022-01-18 | 2024-02-27 | Rosemount Aerospace Inc. | Constraining navigational drift in a munition |
Citations (13)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US3778007A (en) * | 1972-05-08 | 1973-12-11 | Us Navy | Rod television-guided drone to perform reconnaissance and ordnance delivery |
US6037899A (en) * | 1997-05-05 | 2000-03-14 | Rheinmetall W&M Gmbh | Method for vectoring active or combat projectiles over a defined operative range using a GPS-supported pilot projectile |
US20040068415A1 (en) * | 2002-04-22 | 2004-04-08 | Neal Solomon | System, methods and apparatus for coordination of and targeting for mobile robotic vehicles |
US20040134336A1 (en) * | 2002-04-22 | 2004-07-15 | Neal Solomon | System, methods and apparatus for aggregating groups of mobile robotic vehicles |
US7338009B1 (en) * | 2004-10-01 | 2008-03-04 | The United States Of America As Represented By The Secretary Of The Navy | Apparatus and method for cooperative multi target tracking and interception |
US7494089B2 (en) * | 2005-11-23 | 2009-02-24 | Raytheon Company | Multiple kill vehicle (MKV) interceptor and method for intercepting exo and endo-atmospheric targets |
US7494090B2 (en) * | 2006-03-01 | 2009-02-24 | Raytheon Company | Multiple kill vehicle (MKV) interceptor with autonomous kill vehicles |
US7947936B1 (en) * | 2004-10-01 | 2011-05-24 | The United States Of America As Represented By The Secretary Of The Navy | Apparatus and method for cooperative multi target tracking and interception |
US8084724B1 (en) * | 2006-02-01 | 2011-12-27 | Raytheon Company | Enhanced multiple kill vehicle (MKV) interceptor for intercepting exo and endo-atmospheric targets |
US8748787B2 (en) * | 2010-05-27 | 2014-06-10 | Nederlandse Organisatie Voor Toegepast-Natuurwetenschappelijk Onderzoek Tno | Method of guiding a salvo of guided projectiles to a target, a system and a computer program product |
US20170254622A1 (en) * | 2016-03-01 | 2017-09-07 | Northrop Grumman Systems Corporation | Aircraft force multiplication |
US20170328679A1 (en) * | 2016-05-11 | 2017-11-16 | Rivada Research, Llc | Method and System for Using Enhanced Location-Based Information to Guide Munitions |
US10073454B2 (en) * | 2016-03-17 | 2018-09-11 | Northrop Grumman Systems Corporation | Machine vision enabled swarm guidance technology |
Family Cites Families (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5855339A (en) * | 1997-07-07 | 1999-01-05 | Raytheon Company | System and method for simultaneously guiding multiple missiles |
US10048039B1 (en) * | 2002-05-18 | 2018-08-14 | John Curtis Bell | Sighting and launching system configured with smart munitions |
EP1974305A4 (en) * | 2006-01-11 | 2011-11-09 | Carmel Haifa University Economic Corp Ltd | Uav decision and control system |
US20080010273A1 (en) * | 2006-06-12 | 2008-01-10 | Metacarta, Inc. | Systems and methods for hierarchical organization and presentation of geographic search results |
US7999212B1 (en) * | 2008-05-01 | 2011-08-16 | Emag Technologies, Inc. | Precision guided munitions |
US9491801B2 (en) * | 2012-09-25 | 2016-11-08 | Parallel Wireless, Inc. | Dynamic multi-access wireless network virtualization |
US9541350B1 (en) * | 2015-11-19 | 2017-01-10 | Raytheon Company | Coordinating waves of long-range strike weapons (LRSWs) to attack a target set by passing observational sensor data from lead LRSWs to follower LRSWs |
WO2019217971A1 (en) * | 2018-05-11 | 2019-11-14 | Fenix Group, Inc. | Seamless smart munitions system and method |
-
2019
- 2019-05-13 WO PCT/US2019/032040 patent/WO2019217971A1/en active Application Filing
- 2019-05-13 US US16/410,705 patent/US10641582B1/en active Active
-
2020
- 2020-04-30 US US16/863,236 patent/US11035649B2/en active Active
-
2021
- 2021-06-03 US US17/338,557 patent/US11614307B2/en active Active
Patent Citations (17)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US3778007A (en) * | 1972-05-08 | 1973-12-11 | Us Navy | Rod television-guided drone to perform reconnaissance and ordnance delivery |
US6037899A (en) * | 1997-05-05 | 2000-03-14 | Rheinmetall W&M Gmbh | Method for vectoring active or combat projectiles over a defined operative range using a GPS-supported pilot projectile |
US20040068415A1 (en) * | 2002-04-22 | 2004-04-08 | Neal Solomon | System, methods and apparatus for coordination of and targeting for mobile robotic vehicles |
US20040134336A1 (en) * | 2002-04-22 | 2004-07-15 | Neal Solomon | System, methods and apparatus for aggregating groups of mobile robotic vehicles |
US7947936B1 (en) * | 2004-10-01 | 2011-05-24 | The United States Of America As Represented By The Secretary Of The Navy | Apparatus and method for cooperative multi target tracking and interception |
US7338009B1 (en) * | 2004-10-01 | 2008-03-04 | The United States Of America As Represented By The Secretary Of The Navy | Apparatus and method for cooperative multi target tracking and interception |
US7494089B2 (en) * | 2005-11-23 | 2009-02-24 | Raytheon Company | Multiple kill vehicle (MKV) interceptor and method for intercepting exo and endo-atmospheric targets |
US8084724B1 (en) * | 2006-02-01 | 2011-12-27 | Raytheon Company | Enhanced multiple kill vehicle (MKV) interceptor for intercepting exo and endo-atmospheric targets |
US7494090B2 (en) * | 2006-03-01 | 2009-02-24 | Raytheon Company | Multiple kill vehicle (MKV) interceptor with autonomous kill vehicles |
US8748787B2 (en) * | 2010-05-27 | 2014-06-10 | Nederlandse Organisatie Voor Toegepast-Natuurwetenschappelijk Onderzoek Tno | Method of guiding a salvo of guided projectiles to a target, a system and a computer program product |
US20170254622A1 (en) * | 2016-03-01 | 2017-09-07 | Northrop Grumman Systems Corporation | Aircraft force multiplication |
US10073454B2 (en) * | 2016-03-17 | 2018-09-11 | Northrop Grumman Systems Corporation | Machine vision enabled swarm guidance technology |
US20170328679A1 (en) * | 2016-05-11 | 2017-11-16 | Rivada Research, Llc | Method and System for Using Enhanced Location-Based Information to Guide Munitions |
US20170328682A1 (en) * | 2016-05-11 | 2017-11-16 | Rivada Research, Llc | Method and System for Using Enhanced Location-Based Information to Guide Munitions |
US20170328680A1 (en) * | 2016-05-11 | 2017-11-16 | Rivada Research, Llc | Method and System for Using Enhanced Location-Based Information to Guide Munitions |
US20170328683A1 (en) * | 2016-05-11 | 2017-11-16 | Rivada Research, Llc | Method and System for Using Enhanced Location-Based Information to Guide Munitions |
US20170328681A1 (en) * | 2016-05-11 | 2017-11-16 | Rivada Research LLC | Method and System for Using Enhanced Location-Based Information to Guide Munitions |
Also Published As
Publication number | Publication date |
---|---|
US11035649B2 (en) | 2021-06-15 |
US20210293511A1 (en) | 2021-09-23 |
US11614307B2 (en) | 2023-03-28 |
US10641582B1 (en) | 2020-05-05 |
WO2019217971A1 (en) | 2019-11-14 |
US20200271420A1 (en) | 2020-08-27 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US10192451B2 (en) | Low altitude aircraft identification system | |
US11614307B2 (en) | Seamless smart munitions system and method | |
US20210064021A1 (en) | Flight management system for uavs | |
KR101990886B1 (en) | Big data-based autonomous flight drone system and its autonomous flight method | |
US20200372808A1 (en) | Secure unmanned aerial vehicle flight planning | |
US9752878B2 (en) | Unmanned aerial vehicle control handover planning | |
US20190149322A1 (en) | Verifying identity identifier transmitted by an aerial vehicle | |
US20190235489A1 (en) | System and method for autonomous remote drone control | |
US20200154426A1 (en) | Optimization of radio resource allocation based on unmanned aerial vehicle flight path information | |
KR20180038231A (en) | System and method for control of multi drone | |
WO2017120110A1 (en) | Utilization of national cellular infrastructure for uav command and control | |
KR102181741B1 (en) | Server, method and computer program for controlling drone | |
US20210039781A1 (en) | Drone proximity charging | |
US9372053B2 (en) | Autonomous weapon effects planning | |
KR20160074895A (en) | The method and apparatus for updating flight path of drone | |
US11104437B1 (en) | Updating virtual aerial map using sensors associated with aerial vehicles | |
CN107450586B (en) | Method and system for adjusting air route and unmanned aerial vehicle system | |
US20210343165A1 (en) | Systems, methods, apparatuses, and devices for identifying, tracking, and deterring unmanned aerial vehicles via ads-b signals | |
CN110113106B (en) | Wireless communication method for laser energy supply unmanned aerial vehicle with multiple base stations and multiple laser transmitters | |
He et al. | How to govern the non-cooperative amateur drones? | |
KR101473739B1 (en) | System and method for controlling unmaned aerial vehicle | |
KR20220075682A (en) | Automatic Driving AI DRONE and the automatic driving method thereof | |
US20240046800A1 (en) | Device, system, and method for incident air space management | |
KR102047356B1 (en) | MANAGEMENT METHOD AND SYSTEM FOR unmanned aerial vehicle | |
US11972009B2 (en) | Systems and methods of identifying and managing remotely piloted and piloted air traffic |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
FEPP | Fee payment procedure |
Free format text: ENTITY STATUS SET TO UNDISCOUNTED (ORIGINAL EVENT CODE: BIG.); ENTITY STATUS OF PATENT OWNER: SMALL ENTITY |
|
FEPP | Fee payment procedure |
Free format text: ENTITY STATUS SET TO SMALL (ORIGINAL EVENT CODE: SMAL); ENTITY STATUS OF PATENT OWNER: SMALL ENTITY |
|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |
|
MAFP | Maintenance fee payment |
Free format text: PAYMENT OF MAINTENANCE FEE, 4TH YR, SMALL ENTITY (ORIGINAL EVENT CODE: M2551); ENTITY STATUS OF PATENT OWNER: SMALL ENTITY Year of fee payment: 4 |
|
FEPP | Fee payment procedure |
Free format text: ENTITY STATUS SET TO UNDISCOUNTED (ORIGINAL EVENT CODE: BIG.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |