US20200149845A1 - Seamless smart munitions system and method - Google Patents

Abstract

Systems and methods for deploying smart munitions may provide targeting metadata generated by surveillance networks to munitions deployment and guidance systems for smart munitions. Targeting metadata may be received by a conduit system and automatically processed to generate guidance and deployment data actionable by a munitions deployment platform.

Description

CROSS-REFERENCE
• 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.
TECHNICAL FIELD
• 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.
BACKGROUND
• 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.
SUMMARY
• 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.
BRIEF DESCRIPTION OF THE DRAWINGS
• 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.
DETAILED DESCRIPTION
• 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 environment100 andmunitions targeting method200, respectively. Smartmunitions operating environment100 can include a network across which sensor systems and munitions may communicate, demarcated here as a sensorsside network portion101A and a munitionsside network portion101B. A link between aUAV102, or other COT capable sensor system, and amunition108 can be established across the network (operation202). 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 smartmunitions operating environment100. 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 environment100 as a communications plane.
• UAV102 acquires COT metadata for a target, such as 10-digit MGRS information, through sensors onboard UAV102 (operation204). The COT metadata may be associated withparticular targets104 which may, in some examples, be identified byonboard UAV102 systems such as computer vision, targeting systems, and the like. In some examples, a remote processor or service may provide target identification and tracking forUAV102.
• Nevertheless,UAV102 transmits COTmetadata referencing targets104 to aGCS106 vianetwork portion101A for downstream provision of the COT metadata to munition108 (operation206).GCS106 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 toGCS106. 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).
• GCS106, having received COT metadata fromUAV102, may transmit all or a portion of the received COT metadata to munition108 (linked to UAV102) vianetwork portion101B. In some examples, multiple munitions may be linked toUAV102 through either a direct peer-to-peer linkage or viaGCS106. In some examples,GCS106 can initially linkUAV102 andmunition108, which may thereafter communicate directly with each other over a shared network.
• Munition108 can then be deployed totargets104 using the received COT metadata (operation208).Munition108 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.Munition108 may receive additional updates fromUAV102 orGCS106 while in-flight totargets104.Munition108 can then use the additional updates to adjust a flight trajectory and the like in order to increase the chance of successfully strikingtargets104.
• The in-flight updates may comprise COT metadata similarly to above. In some examples,GCS106 may preprocess the COT metadata in order to provide streamlined data to munition108 so as to hasten in-flight computing. In other examples,UAV102 may provide COT metadata directly tomunition108 over a shared network so as to reduce latency and increase accuracy of the provided COT metadata as the munition travels totargets104.
• FIG. 1B is a block diagram depicting a smartmunitions targeting system150 which seamless connects asurveillance network152 and amunitions network154 to provide rapid target resolution and support. In some examples, smartmunitions targeting system150 may be deployed in smartmunitions operating environment100 discussed above in reference toFIG. 1A. Whilesurveillance network152 andmunitions network154 are depicted here as distinct networks, it is understood that this is for explanatory purposes only and, in some examples,surveillance network152 andmunitions network154 may be sub-networks or abstracted segregated network traffic flows of a larger shared network or the like. Either or bothsurveillance network152 andmunitions network154 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 network152 includes a fleet of one ormore UAVs151 in communication with a UAV ground controller and/or each other. In some examples,UAVs151 may all be the same type UAV (e.g., predator drone, etc.) communicating over a dedicated network. In some examples, the fleet ofUAVs151 may include multiple types of drones within a shared control group and may communicate with each other via the ground controller or the like.UAV151A 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,UAV151A transmits targeting metadata to alogistics conduit system156 for deploying munitions to the munitions target.
• Logistics conduit system156 includes aradio160A for interfacing withsurveillance network152 and aradio160B for interfacing withmunitions network154. In some examples,radios160A-B can be software radios or may include one or more additional radios.
• Munitions networks154 includes a communications network or mesh between one ormore munitions155 and a ground munitions controller. In some examples, eachmunition155 communicates withlogistics conduit system156 for deploying and guidingrespective munitions155. Here, amunition155A has established a link withlogistics conduit system156 viaradio160B to receive appropriate targeting metadata for deployingmunition155A to a tracked target, etc.
• Logistics conduit system156 receives targeting metadata fromsurveillance network152 and provides appropriate targeting and guidance data tomunition155A based on the received target metadata. Received metadata is provided to acontrol box158 for further processing. In some examples,logistics conduit system156 may include preprocessing and or analytic processes (not depicted) for processing the received metadata prior to being provided to controlbox158.
• Control box158 includes ametadata exchange process162 for converting metadata received fromsurveillance network152 to a format actionable by one or more munitions155 (e.g.,munition155A). 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 system156.
• Control box158 further includes aninternal core network161 which may include, for example and without imputing limitation, one or more virtual networks and/or virtual network endpoints. In some examples,internal core network161 may bind togethersurveillance network152 andmunitions network154.Internal core network161 may include endpoint bindings, viaradios160A-B, tosurveillance network152 and/ormunitions network154.
• In some examples,logistics conduit system156 may communicate with avalidation data store165 to validate an identity ofmunition155A and/orUAV151A. In some examples,validation data store165 may further store conversion schema or the like formetadata exchange process162. For example,metadata exchange process162 may retrieve the conversion schema based on a retrieved identity ofUAV151A andmunitions155A.Validation data store165 may include one ormore databases166 for storing, managing, and retrieving data.
• FIG. 2B is amethod250 for guiding a munition based on targeting data provided by a targeting (e.g., COT) system. Whilemethod250 is depicted as initiating fromstep252, in someexamples method250 may initiate fromstep256 followingstep206 ofmethod200 discussed above in reference toFIG. 2A.
• Atstep252, 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.
• Atstep254, 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.
• Atstep256, 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.
• Atstep258, COT metadata is received for a target. For example, the COT metadata may be received directly from a UAV, such asUAV151 discussed above in reference toFIG. 1B. In some examples, the COT metadata may be preprocessed to identify appropriate formats and/or perform validation procedures.
• Atstep260, 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 atstep254.
• Atstep262, 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 system300 which may be used in implementing the embodiments of the components of the systems and methods disclosed above. For example, thecomputing system300 ofFIG. 3 may belogistics conduit system156 discussed above. The computer system (system) includes one or more processors302-306. Processors302-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 bus312.Processor bus312, also known as the host bus or the front side bus, may be used to couple the processors302-306 with the system interface314. System interface314 may be connected to theprocessor bus312 to interface other components of thesystem300 with theprocessor bus312. For example, system interface314 may include a memory controller314 for interfacing amain memory316 with theprocessor bus312. Themain memory316 typically includes one or more memory cards and a control circuit (not shown). System interface314 may also include an input/output (I/O)interface320 to interface one or more I/O bridges or I/O devices with theprocessor bus312. One or more I/O controllers and/or I/O devices may be connected with the I/O bus326, such as I/O controller328 and I/O device340, as illustrated.
• I/O device340 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 processors302-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 processors302-306 and for controlling cursor movement on the display device.
• System300 may include a dynamic storage device, referred to asmain memory316, or a random access memory (RAM) or other computer-readable devices coupled to theprocessor bus312 for storing information and instructions to be executed by the processors302-306.Main memory316 also may be used for storing temporary variables or other intermediate information during execution of instructions by the processors302-306.System300 may include a read only memory (ROM) and/or other static storage device coupled to theprocessor bus312 for storing static information and instructions for the processors302-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 bycomputer system300 in response toprocessor304 executing one or more sequences of one or more instructions contained inmain memory316. These instructions may be read intomain memory316 from another machine-readable medium, such as a storage device. Execution of the sequences of instructions contained inmain memory316 may cause processors302-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 asmain memory316. 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)

1. A method comprising:

establishing a link between one or more unmanned aerial vehicles and a smart munition;

validating the smart munition by checking for a device entry in a database;

transmitting, over the link, target coordinates from the one or more unmanned aerial vehicles to the smart munition;

programming the smart munition with targeting information based in part on the target coordinates; and

deploying the smart munition based on the programming.

2. The method ofclaim 1, wherein the link further comprising a connection over a common wireless network and the smart munition comprising a munition with a radio receiver.

3. The method ofclaim 1, wherein the link is established through a control box comprising a radio, processor, and virtual core network.

4. The method ofclaim 1, wherein the grid coordinates are for a Military Grid Reference System (MGRS).

5. The method ofclaim 1, further comprising transmitting, from the one or more unmanned aerial vehicles to the smart munition and over the link, metadata.

6. The method ofclaim 1, wherein the coordinates are grid coordinates.

7. The method ofclaim 2, wherein the network is a combination of one or more dynamic mesh networks and one or more hub and spoke networks.

8. (canceled)

9. A system comprising:

a processor; and

a computer readable medium storing instructions, which when executed by the processor causes the processor to:

establish a link between one or more unmanned aerial vehicles and a smart munition;

transmit, over the link, coordinates from the one or more unmanned aerial vehicles to the smart munition;

program the smart munition with targeting information including at least in part the coordinates; and

deploy the smart munition based on the programming.

10. The system ofclaim 9, wherein the link further comprising a connection over a common wireless network and the smart munition comprising a munition with a radio receiver.

11. The system ofclaim 9, wherein the link is established through a control box comprising a radio, a processor, and a virtual core network, the link including a virtualized network management system.

12. The system ofclaim 9, wherein the grid coordinates are for a Military Grid Reference System (MGRS).

13. The system ofclaim 9, the computer readable medium storing further instructions which when executed by the processor causes the processor to transmit metadata over the link.

14. The system ofclaim 9, wherein the coordinates are grid coordinates.

15. The system ofclaim 10, wherein the network is a combination of one or more dynamic mesh networks and one or more hub and spoke networks.

16. (canceled)

17. A non-transitory computer readable medium storing instructions, which when executed by the processor causes the processor to:

establish a link between one or more unmanned aerial vehicles and a smart munition;

transmit, over the link, coordinates from the one or more unmanned aerial vehicles to the smart munition;

program the smart munition with targeting information including at least in part the coordinates; and

deploy the smart munition based on the programming.

18. The non-transitory computer readable medium ofclaim 17, wherein the link further comprising a connection over a common wireless network and the smart munition comprising a munition with a radio receiver.

19. The non-transitory computer readable medium ofclaim 17, wherein the link is established through a control box comprising a radio, processor, and virtual core network.

20. The non-transitory computer readable medium ofclaim 17, wherein the grid coordinates are for a Military Grid Reference System (MGRS).

21. The non-transitory computer readable medium ofclaim 17, the computer readable medium storing further instructions which when executed by the processor causes the processor to transmit metadata over the link.

22. The non-transitory computer readable medium ofclaim 17, wherein the coordinates are grid coordinates.

23. The non-transitory computer readable medium ofclaim 18, wherein the network is a combination of one or more dynamic mesh networks and one or more hub and spoke networks.

24. (canceled)

Images