Networked battle system or firearm

Information

  • Patent Grant
  • 10470010
  • Patent Number
    10,470,010
  • Date Filed
    Friday, October 17, 2014
    10 years ago
  • Date Issued
    Tuesday, November 5, 2019
    5 years ago
Abstract
A firearm includes one or more rails to which accessories may be mounted. The rails provide a communication path over which data may be transferred between the accessories and a processor located in the rails or in the firearm. The processor may cause the data to be sent to another location and may receive other data from other locations to provide a network of intercommunicating firearms that may deployed in a battlefield environment.
Description
BACKGROUND

Embodiments of the invention relate generally to systems and method of providing information between one or more different battlefield participants.


Communication of information between different battlefield participants (e.g., soldiers) may improve battle results. Further, the more information communicated, the more the improvement.


During battle several different components may be used. These include, for example, rifles, scopes, grenade launchers and communication devices. Some of these components may provide for different views and angles of attack in a battlefield situation.


SUMMARY OF THE INVENTION

In one exemplary embodiment, a weapon is disclosed that provides information regarding its position and orientation to a central location that can interpret and display this information.


In one embodiment, a networked battle system is disclosed. The system includes: a communication network; a first rifle that includes at least one accessory coupled thereto that determines a bearing of the first rifle; a communication element coupled to the rifle allowing the at least one accessory to provide bearing information to the communication network; and a battle management system in communication with the first rifle through the communication network that receives the bearing information from the accessory and updates a battle plan based on the bearing information to form an updated battle plan.


In another embodiment, a rifle is disclosed. The rifle includes: a rail system carried by an upper receiver of the rifle; at least one accessory coupled to the rail system that determines a bearing of the rifle; a communication element coupled to the rail system; at least one sensor coupled to the rail; and a microprocessor carried in either the rail system or a portion of the rifle. In this embodiment, information is provided from the sensor to the microprocessor through the rail system and then provided to the communication element through the rail system for transmission to a communication network.


In another embodiment, a battlefield system that includes a bearing sensor that determines a bearing of a battlefield device is disclosed. The system also includes a microprocessor in communication with the bearing sensor and carried either on or in the battlefield device and a communication element carried by the battlefield device. In this system information is provided from the sensor to the microprocessor and then provided to the communication element for transmission to a communication network.


Other aspects and features of embodiments of the invention will become apparent to those ordinarily skilled in the art upon review of the following description of specific embodiments of the invention in conjunction with the accompanying figures.





BRIEF DESCRIPTION OF THE DRAWINGS

Embodiments of the present invention will now be described, by way of example only, with reference to the attached Figures, wherein:



FIG. 1 is a perspective view of firearm embodied as a rifle according to one embodiment;



FIG. 2 shows an example of a rail configuration according to one embodiment;



FIG. 3 is high-level system diagram illustrating a network formed between a firearm and another device;



FIG. 4 is an example of display screen of an accessory that may be coupled to a firearm;



FIG. 5 is a diagram illustrating different possible communication paths in a firearm;



FIG. 6 is a dataflow diagram illustrating data transfer from rifle accessories to a central location and back;



FIG. 7 illustrates an alternative example of a scope; and



FIG. 8 illustrates multiple battlefield devices networked together.





DETAILED DESCRIPTION

The term “firearm” as used herein, refers at least to a rifle, machine gun, weapon, and pistol and may be automatic, semi-automatic or otherwise. Another example of a firearm includes a grenade launcher, mortar launcher or the like. A power or non-powered rail on a firearm may have certain accessories attached to it. The accessories include, for example, telescopic sights, tactical sights, laser sighting modules, Global Positioning Systems (GPS), bearing sensors, inclination sensors, laser distance measuring devices, accelerometers, microphones, video cameras, cameras and night vision scopes. This list is not meant to be exclusive, merely an example of accessories that may utilize a rail. Any of the devices (e.g., rifles, firearms, spotter scopes, etc.) disclosed herein may be referred to from time to time as a battlefield device.


Referring now to FIG. 1, a perspective view of a rifle, weapon, firearm, (automatic, semi-automatic or otherwise) 10 is illustrated. Rifle, weapon, firearm, etc. 10 has a plurality of rails 12. In one embodiment, rails 12 may be anyone of a MIL-STD-1913 rail, Weaver rail, NATO STANAG 4694 accessory rail or equivalents thereof. Rails 12 are configured to allow a plurality of accessories 14 to the rifle 10. Rails 12 are mounted at the 12 o'clock, 3 o'clock, 6 o'clock and 9 o'clock positions with respect to a longitudinal or firing axis of the rifle and/or a barrel 16 of the rifle 10.


Accessories 14 may be any one of telescopic sights, tactical sights, laser sighting modules, Global Positioning Systems (GPS) and night vision scopes or any type of sensor. The aforementioned accessories are merely an example of contemplated accessories for use with rifle or firearm 10. A specific example of an attached accessory is shown as personal data assistant (PDA) 140 or cellular telephone in FIG. 1. This PDA may have a screen to display information (e.g., maps, target locations, video or other visual information) and receive information from a user (e.g., a touch screen or other input devices). In accordance with an exemplary embodiment, accessories 14 are items that require a source of power and/or require data communication with another component of the rifle or firearm 10 or a system in which rifle or firearm 10 is employed. Of course, one or more the accessories may have its own power supply and may be able to communicate data independent of the firearm.


A portion of a powering rail configured as a MIL-STD-1913 rail is shown generally as 12. Rail 12 is a MIL-STD-1913 rail, such as a Weaver rail, NATO STANAG 4694 accessory rail or the like. Sliding over rail 12 is a powered or powering rail 18.


With reference to FIG. 2, rail 12 has a plurality of rail slots 20 and rail ribs 22, which are utilized in receiving an accessory of another rail such as powering rail 18. Powering rail 18 comprises a plurality of rail slots 24 and rail ribs 26 in a configuration that allows for the mating of accessories with powering rail 18.


In one embodiment, powering rail 18 is mounted to rail 12 via a cross pin 28 or other device received within a pin hole 30 of powering rail 18. The pin hole 30 accepts the cross pin 28 so that the pin 28 locks and secures the rails 12 and 18 together. Although FIG. 1 illustrates rail 18 secured to a top rail 12 of an upper receiver 31 of rifle or firearm 10 rail 18 can also be secured in additional locations such as the 3, 6 and 9 o'clock rail 12 locations. Still further, rail 18 may be secured to anyone or any combination of the 3, 6 and 9 o'clock rail 12 locations. In addition and in one alternative embodiment, powering rail 18 may be formed into anyone of rails 12 such that a separate rail 18 is not necessary. In other words and in this embodiment, the rail 12 is now the networked power and/or data transmitting rail.


As discussed further below, the rail 18 may also provide a path for transferring data from any or all of the accessories 14 to one or more processors carried in the firearm 10. Such processors may be located, for example, in the rail 18 or the pistol grip 212 or both. Also, the accessories themselves may have the ability to receive information back from the processors and transmit to a location remove from the firearm 10. For instance, information from sensors on the firearm 10 may be routed to the processors and then provided to the PDA 140 for transmission to an external location. This communication may be through a rail or direct in which case a rail may be omitted entirely.


Referring now to FIG. 3, a schematic illustration of a system 130, using various embodiments of the present invention is illustrated. As illustrated, a firearm 10 includes a barrel 1 and has a plurality of powering rails 18 (e.g., 3 o'clock, 6 o'clock, 9 o'clock and 12 o'clock locations with respect to a longitudinal axis of the firearm 10 are provided, of course, any other locations are also contemplated). The powering rails 18 are attached, in one embodiment, to rail 12.


Each of the powering rails 18 are configured to transmit power to an associated accessory 14 via conductive couplings. The same or different couplings may also allow for the transmission of data though the rails 18 to/from the accessories. The couplings can be any type of coupling including, for example, inductive couplings and/or galvanic couplings including direct contact between two conductive materials. In one embodiment, one of data or power is transmitted via inductive couplings and the other of data or power is transmitted via galvanic couplings. More detailed description of the powering rails 18 and the manner in which power/data may be transferred is described in one or more the patents/patent applications mentioned above.


Each of the rails 18 are also configured to communicate with a rail master control unit or processor 42 via a data bus, which in turn allows all of the accessories 14 to communicate information to other processors in the firearm. For example, the firearm 10 may further include a processor 51 disposed in the grip 212 (FIG. 1) of the firearm. As discussed more fully below, the processor 51 may serve as the master control unit. In one embodiment, the processor 42 may be omitted.


To the extent that the processor 42 is included, it may be referred to as a bus processor herein and it controls access to the data bus formed by the powering rails to allow for the processor 51 to communicate information to and from the accessories 14. The bus processor 42 may be located in either the upper or lower receiver of the firearm 10 or may be disposed in/on rails 12 or power rails 18.


As illustrated, processor 51 is coupled via communication link 133 to a communication device 132 that may be worn, for example, in backpack or vest. This allows for the processor 51 to communicate with other devices 136/200 in the system as more fully described below. The communication link 133 may be wired or wireless or a combination thereof. The communication device 132 may communicate in any known manner including, but not limited to, rf communications, cellular communications, Bluetooth, and ZigBee and the communication path is generally shown as passing through a communication network 131. The communication network 131 can be any type of now known or later created network and may include one or more additional processors for routing or storing the information.


In one embodiment, the PDA 140 may also be able to provide information to and receive information from the communication network 131. For instance, accessories 14 in the form of sensors may provide information to the processor (42 or 51 or both) and receive information back from the processor and transmit it off the rifle 10 to the communication network 131. In one embodiment, the communication from the PDA 140 is direct to the communication network 131 via path 141 and in another embodiment, the PDA 140 communicates with the communication device 132 (path 142) which in turn provides communication to the communication network 131. It shall be further understood that any of the processors 51/42 or the PDA may operate as a server in communication with each other or external server. For instance, the PDA 140 may operate as a server that connects the processors 42/51 to a battle management system. As a server, the PDA may also be able to process map or coordinate date received from an external source such as a battle management system. The same may be true of the tablet 200 discussed below. In addition, while the sensors/accessories 14 are shown as connected to rails, it shall be understood these elements can be integral or embedded in the upper receiver (or any other portion) of a firearm.


In one non-limiting embodiment the observer system is a spotter scope 136 that may be able to determine the location of a potential target. This may include determining the location of the scope 136 and the distance/direction to the target for instance, by combining a GPS location of the scope 136 with distance from a laser range finder and means for determining pointing direction as discussed below this information may then be transferred from the scope 136 to the firearm 10 and then routed through the rails and a location of the target displayed on a map shown on an accessory 14 such as a PDA. In this embodiment, firearm 10 of the system 130 is a sniper rifle, which is networked or communicates with observer system 136 through the communication network 131. In one embodiment, the communication between the firearm and the scope 136 (or the tablet 200 discussed below) may be direct point-to-point contact. It shall be understood that one or more of the accessories 14 may also communicate directly to the communication network 131 in any known manner including, but not limited to, rf communications, cellular communications, Bluetooth, and ZigBee and these communication devices may be any one of accessories 14 or peripheral device 132 which may be worn by an operator of one of the components. In one embodiment, the communication network is a wireless LAN network. The communication devices also being networked or in communication with other devices coupled to the powered rail(s) 18. Although only two items (e.g., firearm 10 and observer system 136) are illustrated it is understood that numerous items (e.g., more than two) may be networked to communicate with each other. For example, multiple firearms 10, observer systems 136 and numerous other devices or items may be networked through system 130 and data can be exchanged between any of the items through the communication network 131. Each item may target, identify, or exchange data (either unique to that item or common between items) with respect to multiple targets, locations, persons, or other items.


Another example of a spotter system 136 is illustrated as scope in FIG. 7. In this embodiment, the spotter system 136 may have a device 138 that communicates with an associated accessory 14 or device 140 illustrated in at least FIG. 1. For example, devices 138 and 140 may be GPS, laser range finder, PDA or targeting devices capable of communicating (e.g., wireless or otherwise) with each other and thus exchanging data and information.


The system illustrated in FIG. 3 shows a version of the system 130 capable of communication with and/or part of a battlefield management system (BMS) illustrated as tablet computer 200. Of course, the BMS could be implanted on other types of devices. Further, it shall be understood that the PDA 140 could be part of the system. In general, a battlefield management system is a system that integrates information acquired from multiple inputs and can be used coordinate movement/actions of multiple actors (e.g., soldiers).


As illustrated, one of the accessories 14 is coupled to an adapter 205 that allows it to communicate with the rail. The adapter 205 could condition power into a form desired by the accessory. For example, the adapter could be utilized to convert power into a form or particular pin layout used by a PDA or scope. Further, the adapter could include formatting logic to convert PDA or scope data into a form conductive for transmission through the rail 18. For example, parallel data could be converted into serial format.


In one embodiment, the system 130 includes a sensor 220 capable of determining a bearing of firearm 10. Such a sensor may be a compass or part of a GPS device or other device. In one embodiment, the angular (bearing, pitch and roll) information may be determined from sensors contained in PDA 140. In other embodiments, the angular sensors may be formed by one or more rotationally sensitive sensors such as inclinometers, rate gyros, accelerometers and magnometer mounted on the firearm 10. In one embodiment the firearm 10 includes at least one set of angular sensors 222 to determine the inclination, roll and bearing with respect to the horizontal axis of the firearm. The processor 51 may combine the data from the sensors (e.g., 220, 222) as well as information from another other accessory 14 on the firearm and then cause it to be transmitted via communication device 132 to the battle management system 200 or any other observer system 136. It shall be understood that any of the capabilities disclosed herein with respect to the rifle 10 may be applicable to the scope 136 or any other device included in system 130.


In one embodiment, the processor 51 collects data from the accessories 14 (herein, accessories will also include any sensor on the firearm) in either a polled or interrupt method via the data bus. The data bus can be either wired or wireless interfaces. The processor 51 may utilize a real time clock to routinely interrogate accessories 14 at a predetermined schedule. During these predetermined intervals the processor 51 reads the data and stores it into memory. In one embodiment, the data is tagged with a real time clock stamp to facilitate data processing. In one embodiment, one or more of the accessories 14 are interrupt driven. In such a case, an event causes the accessory 14 to send an interrupt to the processor 51 which, in turn, causes the processor 51 to collect data from the accessory 14.


Regardless of how collected, the data is transmitted from communication device 132 to the tablet 200, the observer system 136 or both. Further, either of observer 136 or the tablet 200 can send information back to the firearm 10.


In operation, processor 51 draws power from the power supply 84 and may discover connected accessories 14. In one embodiment, the discovery may include verifying that the accessory 14 is operable. In the case that the accessory 14 is a sensor, the processor 51 may configure the sensor based on its location on the firearm and function. The sensors can be navigation, acoustic or optical devices. The sensors all communicate to the processor via the data bus and report sensor data and status. The navigation sensors could be individual or integrated into a single package, and are GPS (military or commercial), accelerometer, rate gyro, magnometer (compass) or gyro scope and may sense and report in all three axial planes (x, y & z). The acoustic sensor may provide an acoustic signature of the environment around the firearm as well as of the firearm itself. The optical sensor may capture the optical spectrum in front of the weapon. The optical spectrum could be the visual, infrared, thermal, Short Wave Length, Medium Wave Length and Long Wave Length, etc.


It shall be understood that the format of the data stored/transmitted by the processor 51 can be varied and adapted to meet any preferred receiving performance. Further, while there are several different accessories 14 disclosed above, it shall be understood that the processor 51 may include the ability to synthesize the data from these accessories before transmitting the data. For example, if a camera is used to form a digital image of a target, the time and the position and orientation of the rifle 10 can be attached to that image before it is transmitted. Further, in some cases, the rifle 10 may include a video camera attached as an accessory. In such a case, the data (e.g., images or video) could be streamed in real-time with time/position data appended thereto or sent in periodic or interrupt driven intervals.


In some cases, the processor 51 may include the ability to process the data collected from the accessories 14. For example, the processor 51 may include instructions that allow it perform ballistics calculations, target range and angular offset calculation, and target tracking. Further, based on collected data, the number of shots taken, remaining ammunition, firearm performance and maintenance determinations and other firearm related calculations may be made. In one embodiment, the accessories 14/processor 51 monitor the internal ballistic life cycle and internal mechanisms of the firearm. As a firearm's mechanisms wear or become fouled, previously recorded events can be compared to determine the percentage of difference. Dependent on the parameter be monitored, such comparisons may determine the usefulness of the firearm.


Either in real time or at a prior time, map information related to an area in which the firearm 10 is, or in the future may be, located is provided to one or more of: microprocessor 42/51, PDA 140, and tablet 200. The map information may be in the form of an overhead aerial view in one embodiment and may be received from any source including, but not limited to reconnaissance information taken by satellite or other overhead device such as a drone. Of course, publicly available maps could be used in one embodiment. Based on a GPS location of the firearm 10, a portion of the map may be selected. Given the bearing of the firearm 10, a view of the map in the region in front of the firearm 10 may be selected and displayed on the PDA 140. Further, with the information the location of “friendlies” can be displayed on the maps as the table 200 includes information from all of the weapons in the system 130 and can place indicators on the map at those locations. Further, as an example, the location of a hostile party may be added to the map based, for example, the location of a friendly and a distance measured to the hostile by a laser range finder.


In one embodiment, the firearm 10 includes an inclinometer as one of the accessories 14. Assuming that ballistic information is known about a projectile (e.g., a bullet or grenade) that the firearm 10 (or an attachment thereto) fires, a projected impact point on the map be displayed.


With reference to FIG. 4, an example of a display 201 of PDA 140 is illustrated. The bearing information (shown by compass 203) described above can be used to position a possible impact location 202 of the projectile in along the y axis. Similarly, information from an angular sensors and the ballistic information can be used to determine how far the projectile will travel and the, thus, determines the location of the impact location 202. As the firearm as raised upward, the impact location 202 translates up on the map 201.



FIG. 5 schematically illustrates communication between various components on a firearm as disclosed herein. The firearm includes at least one rail 18 onto which several accessories 14 are coupled. The system includes three different communication channels shown as a low speed channel 502, a medium speed channel 504 and a high speed channel 506. The low speed channel 502 extends from and allows communication between the master processor 76 and any of the accessories 14. The low speed channel 502 can be driven by a low speed transmitter/receiver 510 in processor 51 that includes selection logic 512 for selecting which of the accessories 14 to route the communication to.


Each accessory 14 includes low speed decoding/encoding logic 514 to receive and decode information received over the low speed channel 502. Of course, the low speed decoding/encoding logic 514 can also include the ability to transmit information from the accessories 14 as described above.


In one embodiment, the low speed channel 502 carries data at or about 100 kB/s. Of course, other speeds could be used. The low speed channel 502 passes through a coupling 520. The coupling 520 could be galvanic or via inductive coil pairs. In one embodiment, the inductive coil pair could be replaced include a two or more core portions about which the coil pair is wound. In another embodiment, the cores can be omitted and the inductive coil pair can be implemented as an air core transformer. As illustrated, the couplings 520 are contained within the powering rail 18. Of course, one or more of the portions of the coupling can be displaced from the rail 18.


The medium speed channel 504 is connected to couplings 520 and shares them with low speed channel 502. For clarity, branches of the medium speed channel 504 as illustrated in dashed lines. As one of ordinary skill will realize, data can be transferred on both the low speed channel 502 and the medium speed channel at the same time. The medium speed channel 504 is used to transmit data between the accessories 14.


Both the low and medium speed channels 502, 504 can also be used to transmit data to or receive data from an accessory (e.g. a tether) not physically attached to the rail 18 as illustrated by element 540. The connection between the processor 51 can be either direct or through an optional inductive coil pair 520′. In one embodiment, the optional inductive coil pair 520′ couples power or data or both to processor 51 which may be located in or near a handle portion (e.g., pistol grip) of a firearm.


To allow for communication between accessories 14 over the medium speed channel 504, the processor 51 can include routing logic 522 that couples signals from one accessory to another based on information either received on the medium speed channel 504. Of course, in the case where two accessories coupled to the rail 18 are communicating via the medium speed channel 502, the signal can be boosted or otherwise powered to ensure is can drive couplings 520 between the accessories.


In another example, the accessory that is transmitting the data first utilizes the low speed channel 502 to cause the processor 51 sets the routing logic 522 to couple the medium speed channel 504 to the desired receiving accessory. Of course, the processor 51 itself (or an element coupled to it) can be used to separate low and medium speed communications from one another and provide them to either the low speed transmitter/receiver 510 or the routing logic 522, respectively. In one embodiment, the medium speed channel 504 carries data at 10 MB/s.



FIG. 5 also illustrates a high speed channel 506. In one embodiment, the high speed channel 506 is formed by an optical data line and runs along at least a portion of the length of the rail 18. For clarity, however, the high speed channel 506 is illustrated separated from the rail 18. Accessories 14 can include optical transmitter/receivers 542 for providing signals to and receiving signals from the high speed channel 506. In one embodiment, a high speed signal controller 532 is provided to control data flow along the high speed channel 506. It shall be understood that the high speed signal controller 532 can be located in any location and may be provided, for example, as part of the processor 51. In one embodiment, the high speed signal controller 532 is an optical signal controller such as, for example, an optical router.



FIG. 6 shows a dataflow of information as it may be transferred according to one embodiment. Accessory data 1200a, 1200b and 1200c is representative of data that may be transferred to or from accessories coupled to a rail system 1202 coupled to a firearm. The rail system 1202 may be formed as herein described. Of course other rail systems capable of supporting one or more accessories on a firearm may be utilized. The rail system 1202 may provide power to the accessories in one embodiment but that is not required. The rail system 18 may also provide a physical conduit for transmitting data to and from the accessories. As mentioned above and as more fully discussed below, the data 1200a-1200c passes through a coupling 520 that provides for inductive or galvanic transfer of the data from the accessory to the communication pathway (e.g., bus) 1204 provided by the rail system 1202. Of course, other energy transfer methods such as capacitive coupling may be utilized. Processor 42 controls communication over the bus 1204 and as such may be referred to as a bus processor in one embodiment. The bus processor 42 may be located in the rail system 1202 itself or in the upper or lower receiver of a firearm. The bus processor may be able to determine, in one embodiment, when an accessory is coupled to the rail system 1202. It should be noted that another processor (e.g. processor 51) may perform the bus control functions in one embodiment and, in such and embodiment, the bus processor 42 may be omitted.


The bus processor can allow, for example, for first accessory data 1200a to be transferred to the processor 51 first, followed by data 1200b and then 1200c in one embodiment. Of course, any ordering a data can be provided for. The data reaches processor 51 and then transformed into an output data set 1200d. In one embodiment, the output data set is a compilation of portions of the data 1200a-c. Output data set 1200d could also include additional information such as a time stamp. For example, assume data 1200a is GPS data from a GPS device coupled to the rail system 1200, data 1200b is bearing information and data 1200c is a target distance value. This data could be combined and time stamped to provide an accurate time sensitive location of a potential target. Data 1200d may also include manipulated data as well. Regardless, data 1200d is provided to computing device 200 (e.g., a battle management system). Data 1200d may be transmitted off of the rifle 10 in any manner including through one of the accessories (e.g., PDA 140).


Computing device 200 may also receive data from other battlefield devices (e.g., other rail systems) as generally indicated by data 1200n. The computing device takes some or all of the data that it has received and may, in one embodiment create mission data 1200e. This data is then transferred to processor 51 and subsequently provided to one or more of the accessories. An example (following from above) includes mission data 1200e that includes a map showing all of the targets identified by any of the rifles and data 1200e could be sent to any or all of the rifles that are connected to a particular network. The format and content of the each of the different data elements shown in FIG. 6 may be platform agnostic in one embodiment so that the system 1202 may integrated into any preexisting or later developed battle management system.


The skilled artisan will realize that any number of rifles 10, spotter scopes 136, tablets 200 and the like may communicate with one another as shown in FIG. 8, other battlefield devices may also be included an indicated by reference numeral 201. For instance, grenade launchers, mortar launchers or any other element used to determine information or launch a projectile could communicate through network 131.


As referred to above, the rails 18 can be used to deliver power and/or data to the accessories 14. The power and/or data can be transferred bidirectionally to and from the rail to the accessory inductively or via a direct electrical (galvanic) connection.


While the invention has been described with reference to an exemplary embodiment, it will be understood by those skilled in the art that various changes may be made and equivalents may be substituted for elements thereof without departing from the scope of the invention. In addition, many modifications may be made to adapt a particular situation or material to the teachings of the invention without departing from the essential scope thereof. Therefore, it is intended that the invention not be limited to the particular embodiment disclosed as the best mode contemplated for carrying out this invention, but that the invention will include all embodiments falling within the scope of the present application.

Claims
  • 1. A networked battle system comprising: a communication network;a first rifle that includes at least one accessory coupled thereto that determines a bearing of the first rifle;a communication element coupled to the rifle allowing the at least one accessory to provide bearing information to the communication network;a battle management system in communication with the first rifle through the communication network that receives the bearing information from the accessory and updates a battle plan based on the bearing information to form an updated battle plan; anda display screen coupled to the first rifle that displays the updated battle plan.
  • 2. The networked battle system of claim 1, further comprising: a battlefield device including a display device attached thereto;wherein the battle management system provides the updated battle plan to the display device through the communication network.
  • 3. The networked battle system of claim 2, wherein the battlefield device includes a microprocessor that receives the updated battle plan and provides it to the display device.
  • 4. The networked battle system of claim 3, wherein the microprocessor is located in a grip of the battlefield device.
  • 5. The networked battle system of claim 3, wherein the communication element is in communication with a radio device in communication with the communication network.
  • 6. The networked battle system of claim 5, wherein the radio device is wirelessly coupled to the communication element.
  • 7. The networked battle system of claim 1, wherein the updated battle plan is a map that includes an indication of a location of a target.
  • 8. The networked battle system of claim 1, wherein the first rifle further includes a laser distance measurement device and the updated battle plan is formed in part based on distance information received by the battle management system from the laser distance measurement device through the communications network.
  • 9. The networked battle system of claim 1, wherein the communication network is a wireless local area network (WLAN).
  • 10. The networked battle system of claim 9, wherein the WLAN connects directly to the communication element and is part of the at least one accessory.
  • 11. A rifle comprising: a rail system carried by an upper receiver of the rifle;at least one accessory coupled to the rail system;a communication element coupled to the rail system;at least one sensor coupled to the rail that determines a bearing of the rifle; anda microprocessor carried in either the rail system or a portion of the rifle;wherein information is provided from the sensor to the microprocessor through the rail system and then provided to the communication element through the rail system for transmission to a communication network.
  • 12. The rifle of claim 11, wherein the sensor is a bearing sensor.
  • 13. The rifle of claim 11, wherein the microprocessor is located in a grip of the rifle.
  • 14. The rifle of claim 11, wherein the communication element is a personal digital assistant (PDA).
  • 15. The rifle of claim 11, wherein the communication element is in communication with a radio device in communication with the communication network.
CROSS REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of U.S. Provisional Patent Application No. 61/976,157, filed Apr. 7, 2014 and U.S. Provisional Patent Application No. 62/003,006, filed May 26, 2014, the contents each of which are incorporated herein by reference thereto. This application is a continuation-in-part of U.S. patent application Ser. No. 14/476,210, filed Sep. 3, 2014 the contents of which is incorporated herein by reference thereto. This application is a continuation-in-part of U.S. patent application Ser. No. 14/481,542, filed Sep. 9, 2014 the contents of which is incorporated herein by reference thereto. Reference is also made to U.S. patent application Ser. No. 13/968,882 filed Aug. 16, 2013, which claims the benefit of U.S. Provisional Patent Application Ser. No. 61/684,062, filed Aug. 16, 2012, the contents each of which are incorporated herein by reference thereto. Reference is also made to U.S. patent application Ser. No. 13/956,582 filed Aug. 1, 2013, which claims the benefit of U.S. Provisional Patent Application Ser. No. 61/684,062, filed Aug. 16, 2012, the contents each of which is incorporated herein by reference thereto. Reference is also made to the following applications, U.S. patent application Ser. No. 12/688,256 filed Jan. 15, 2010; U.S. patent application Ser. No. 13/372,825 filed Feb. 14, 2012; U.S. Provisional Patent Application Ser. No. 61/443,085 filed Feb. 15, 2011; and U.S. Provisional Patent Application Ser. No. 61/528,728 filed Aug. 29, 2011, the contents each of which are also incorporated herein by reference thereto.

US Referenced Citations (271)
Number Name Date Kind
1950835 Zajac Mar 1934 A
4533980 Hayes Aug 1985 A
5033219 Johnson et al. Jul 1991 A
5142806 Swan Sep 1992 A
5237773 Claridge Aug 1993 A
5345707 Randall Sep 1994 A
5360949 Duxbury Nov 1994 A
5555662 Teetzel Sep 1996 A
5557872 Langner Sep 1996 A
5654594 Bjornsen, III et al. Aug 1997 A
5669174 Teetzel Sep 1997 A
5822905 Teetzel Oct 1998 A
5826363 Olson Oct 1998 A
5831841 Nishino Nov 1998 A
6163131 Gartstein et al. Dec 2000 A
6219952 Mossberg et al. Apr 2001 B1
6237271 Kaminski May 2001 B1
6412207 Crye et al. Jul 2002 B1
6430861 Ayers et al. Aug 2002 B1
6490822 Swan Dec 2002 B1
6499245 Swan Dec 2002 B1
6508027 Kim Jan 2003 B1
6513251 Huang et al. Feb 2003 B2
6618976 Swan Sep 2003 B1
6622416 Kim Sep 2003 B2
6779288 Kim Aug 2004 B1
6792711 Battaglia Sep 2004 B2
6847587 Patterson et al. Jan 2005 B2
6849811 Heflin et al. Feb 2005 B1
6854206 Oz Feb 2005 B2
6865599 Zhang Mar 2005 B2
6895708 Kim et al. May 2005 B2
6899539 Stallman et al. May 2005 B1
6918066 Dutta et al. Jul 2005 B2
6925744 Kincel Aug 2005 B2
6931775 Burnett Aug 2005 B2
7007586 Larroque-Lahitette et al. Mar 2006 B2
7059076 Stoner et al. Jun 2006 B2
7096619 Jackson et al. Aug 2006 B2
7121036 Florence et al. Oct 2006 B1
7124531 Florence et al. Oct 2006 B1
7131228 Hochstrate Nov 2006 B2
7144830 Hill et al. Dec 2006 B2
RE39465 Swan Jan 2007 E
7216451 Troy May 2007 B1
7231606 Miller et al. Jun 2007 B2
7243454 Cahill Jul 2007 B1
D556289 Yu Nov 2007 S
7316003 Dulepet et al. Jan 2008 B1
RE40216 Swan Apr 2008 E
7363741 DeSomma et al. Apr 2008 B2
7421817 Larsson Sep 2008 B2
7421818 Houde-Walter Sep 2008 B2
7438430 Kim Oct 2008 B2
7458179 Swan Dec 2008 B2
7461346 Fildebrandt Dec 2008 B2
7464495 Cahill Dec 2008 B2
7523580 Tankersley Apr 2009 B1
7525203 Racho Apr 2009 B1
7548697 Hudson et al. Jun 2009 B2
7551121 O'Connell et al. Jun 2009 B1
7554316 Stevens et al. Jun 2009 B2
7559169 Hung et al. Jul 2009 B2
7562483 Hines Jul 2009 B2
7584569 Kallio et al. Sep 2009 B2
7605496 Stevens et al. Oct 2009 B2
7627975 Hines Dec 2009 B1
7640690 Hines Jan 2010 B2
7676975 Phillips et al. Mar 2010 B2
7698983 Pinto et al. Apr 2010 B1
D616521 Starnes May 2010 S
7707762 Swan May 2010 B1
7712241 Teetzel et al. May 2010 B2
7750814 Fisher et al. Jul 2010 B2
7775150 Hochstrate et al. Aug 2010 B2
7793452 Samson et al. Sep 2010 B1
7818910 Young Oct 2010 B2
7841120 Teetzel et al. Nov 2010 B2
7866083 Teetzel Jan 2011 B2
7868587 Stevens et al. Jan 2011 B2
7908784 Kim Mar 2011 B2
7909490 Chou et al. Mar 2011 B2
7953369 Baarman May 2011 B2
7954971 Kincaid et al. Jun 2011 B1
7975419 Darian Jul 2011 B2
7985527 Tokunaga Jul 2011 B2
7990147 Driemel et al. Aug 2011 B2
7994752 Soar Aug 2011 B2
8001715 Stokes Aug 2011 B2
8005995 Ito et al. Aug 2011 B2
8028459 Williams Oct 2011 B2
8028460 Williams Oct 2011 B2
8035340 Stevens et al. Oct 2011 B2
8039995 Stevens et al. Oct 2011 B2
8042967 Hikmet et al. Oct 2011 B2
8063773 Fisher Nov 2011 B2
8091265 Teetzel et al. Jan 2012 B1
8104211 Darian Jan 2012 B2
8141288 Dodd et al. Mar 2012 B2
8146282 Cabahug et al. Apr 2012 B2
8151505 Thompson Apr 2012 B2
8225542 Houde-Walter Jul 2012 B2
8251288 Woitalla et al. Aug 2012 B2
8311757 Lin Nov 2012 B2
8336776 Horvath et al. Dec 2012 B2
8347541 Thompson Jan 2013 B1
8371729 Sharrah et al. Feb 2013 B2
8453369 Kincaid et al. Jun 2013 B1
8458944 Houde-Walter Jun 2013 B2
8464459 Summers Jun 2013 B1
8485085 Goree et al. Jul 2013 B2
8495945 Kirchner et al. Jul 2013 B1
8516731 Cabahug et al. Aug 2013 B2
8528244 Scallie et al. Sep 2013 B2
8572292 Ito et al. Oct 2013 B2
8635798 Mulfinger Jan 2014 B2
8668496 Nolen Mar 2014 B2
8739672 Kelly Jun 2014 B1
8826575 Ufer et al. Sep 2014 B2
9010002 Popa-Simil Apr 2015 B2
9151564 Baxter Oct 2015 B1
20020174588 Danner et al. Nov 2002 A1
20030029072 Danielson et al. Feb 2003 A1
20030074822 Faifer Apr 2003 A1
20030106251 Kim Jun 2003 A1
20040121292 Chung et al. Jun 2004 A1
20040198336 Jancic et al. Oct 2004 A1
20040241622 White Dec 2004 A1
20050000142 Kim et al. Jan 2005 A1
20050018041 Towery et al. Jan 2005 A1
20050033544 Brooks et al. Feb 2005 A1
20050109201 Larroque-Lahitette et al. May 2005 A1
20050204603 Larsson Sep 2005 A1
20050217161 Haugen et al. Oct 2005 A1
20050241206 Teetzel et al. Nov 2005 A1
20050241211 Swan Nov 2005 A1
20050268521 Cox et al. Dec 2005 A1
20060005447 Lenner et al. Jan 2006 A1
20060204935 McAfee et al. Sep 2006 A1
20060288626 Kim Dec 2006 A1
20070006509 DeSomma et al. Jan 2007 A1
20070150556 Fukuda et al. Jun 2007 A1
20070216392 Stevens et al. Sep 2007 A1
20070228833 Stevens et al. Oct 2007 A1
20080010890 Vice et al. Jan 2008 A1
20080039962 McRae Feb 2008 A1
20080040965 Solinsky et al. Feb 2008 A1
20080063400 Hudson et al. Mar 2008 A1
20080092422 Daniel et al. Apr 2008 A1
20080108021 Slayton et al. May 2008 A1
20080134562 Teetzel Jun 2008 A1
20080170838 Teetzel et al. Jul 2008 A1
20080190002 Hines Aug 2008 A1
20080204361 Scales et al. Aug 2008 A1
20080216380 Teetzel Sep 2008 A1
20080219100 Fisher et al. Sep 2008 A1
20080301994 Langevin et al. Dec 2008 A1
20090044439 Phillips et al. Feb 2009 A1
20090058361 John Mar 2009 A1
20090108589 Racho et al. Apr 2009 A1
20090134713 Stevens et al. May 2009 A1
20090218884 Soar Sep 2009 A1
20090249216 Charka et al. Oct 2009 A1
20090255160 Summers et al. Oct 2009 A1
20090305197 Lim et al. Dec 2009 A1
20090322158 Stevens et al. Dec 2009 A1
20100031552 Houde-Walter et al. Feb 2010 A1
20100083553 Montgomery et al. Apr 2010 A1
20100095574 Abst et al. Apr 2010 A1
20100122485 Kincel May 2010 A1
20100126054 Daniel et al. May 2010 A1
20100154276 Kim Jun 2010 A1
20100154280 Lafrance et al. Jun 2010 A1
20100175293 Hines Jul 2010 A1
20100180485 Cabahug et al. Jul 2010 A1
20100181933 Langovsky et al. Jul 2010 A1
20100186278 Daniel Jul 2010 A1
20100192443 Cabahug et al. Aug 2010 A1
20100192444 Cabahug et al. Aug 2010 A1
20100192446 Darian Aug 2010 A1
20100192447 Cabahug et al. Aug 2010 A1
20100192448 Darian et al. Aug 2010 A1
20100196859 Saugen et al. Aug 2010 A1
20100218410 Cabahug et al. Sep 2010 A1
20100229448 Houde-Walter et al. Sep 2010 A1
20100242332 Teetzel et al. Sep 2010 A1
20100275489 Cabahug et al. Nov 2010 A1
20100279544 Dodd et al. Nov 2010 A1
20100281725 Arbouw Nov 2010 A1
20110000120 Thompson et al. Jan 2011 A1
20110006613 Stevens et al. Jan 2011 A1
20110010979 Houde-Walter et al. Jan 2011 A1
20110030257 Gwillim, Jr. et al. Feb 2011 A1
20110031928 Soar Feb 2011 A1
20110036337 Freitag et al. Feb 2011 A1
20110061284 Cabahug et al. Mar 2011 A1
20110089894 Soar Apr 2011 A1
20110099876 Bentley May 2011 A1
20110126622 Turner Jun 2011 A1
20110131858 Darian et al. Jun 2011 A1
20110162245 Kamal Jul 2011 A1
20110162251 Houde-Walter Jul 2011 A1
20110173865 Compton et al. Jul 2011 A1
20110214328 Williams et al. Sep 2011 A1
20110239354 Celona et al. Oct 2011 A1
20110252741 Travez et al. Oct 2011 A1
20110264257 Travez et al. Oct 2011 A1
20110271822 Myr Nov 2011 A1
20110283585 Cabahug et al. Nov 2011 A1
20110283586 Scallie et al. Nov 2011 A1
20110285214 Stevens et al. Nov 2011 A1
20110306251 Mulfinger et al. Dec 2011 A1
20120021385 Belenkii et al. Jan 2012 A1
20120068536 Stevens et al. Mar 2012 A1
20120085331 Lang et al. Apr 2012 A1
20120097741 Karcher Apr 2012 A1
20120125092 Downing May 2012 A1
20120125189 McLean, III et al. May 2012 A1
20120131837 Cabahug et al. May 2012 A1
20120143368 Travez et al. Jun 2012 A1
20120144714 Cabahug et al. Jun 2012 A1
20120144716 Cabahug et al. Jun 2012 A1
20120180363 Frascati et al. Jul 2012 A1
20120180364 Berntsen et al. Jul 2012 A1
20120192476 Compton et al. Aug 2012 A1
20120214137 Goree Aug 2012 A1
20120233901 Kim et al. Sep 2012 A1
20120285064 Houde-Walter et al. Nov 2012 A1
20120317706 Lebel et al. Dec 2012 A1
20130047482 Mulfinger et al. Feb 2013 A1
20130047486 Ding et al. Feb 2013 A1
20130061504 Malherbe et al. Mar 2013 A1
20130061509 Allen et al. Mar 2013 A1
20130104438 Hines et al. May 2013 A1
20130104439 Hines et al. May 2013 A1
20130105579 Miller May 2013 A1
20130185978 Dodd et al. Jul 2013 A1
20130286239 Lupher et al. Oct 2013 A1
20130329211 McHale et al. Dec 2013 A1
20130337415 Huet Dec 2013 A1
20130344461 Tello Dec 2013 A1
20140007485 Castejon, Sr. Jan 2014 A1
20140028856 Ehrlich Jan 2014 A1
20140047754 Compton et al. Feb 2014 A1
20140052578 Redwood Feb 2014 A1
20140052878 Ito et al. Feb 2014 A1
20140059911 Oh et al. Mar 2014 A1
20140068990 Cabahug et al. Mar 2014 A1
20140130392 Oh et al. May 2014 A1
20140184476 McHale et al. Jul 2014 A1
20140360081 Lupher et al. Dec 2014 A1
20140378088 Goel et al. Dec 2014 A1
20150020427 Compton et al. Jan 2015 A1
20150026588 Turcotte Jan 2015 A1
20150041538 Teetzel Feb 2015 A1
20150108215 Ehrlich Apr 2015 A1
20150176949 Varshneya Jun 2015 A1
20150285593 Dribben Oct 2015 A1
20150285599 Downing Oct 2015 A1
20150300786 Downing et al. Oct 2015 A1
20150345887 Shneorson Dec 2015 A1
20150345906 Varshneya Dec 2015 A1
20150369554 Kramer Dec 2015 A1
20160025462 Downing Jan 2016 A1
20160254462 Downing et al. Jan 2016 A1
20160033221 Schmehl Feb 2016 A1
20160084617 Lyren Mar 2016 A1
20160169627 Northrup Jun 2016 A1
20160216082 Downing Jul 2016 A1
20160223278 Schechter Aug 2016 A1
20160316128 Teich Oct 2016 A1
Foreign Referenced Citations (26)
Number Date Country
2547081 Jun 2005 CA
2537839 Sep 2005 CA
2756018 Sep 2010 CA
2754852 Nov 2010 CA
2754869 Nov 2010 CA
2923506 Mar 2015 CA
2251670 May 1974 DE
102004045753 Mar 2006 DE
2587659 May 2013 EP
200715159 Apr 2007 TW
2005080908 Sep 2005 WO
2005109597 Nov 2005 WO
2007107975 Sep 2007 WO
2008048116 Apr 2008 WO
2008108818 Sep 2008 WO
2009127354 Oct 2009 WO
2009151713 Dec 2009 WO
2010004470 Jan 2010 WO
2010107324 Sep 2010 WO
2011079233 Jun 2011 WO
2011162245 Dec 2011 WO
2013066472 May 2013 WO
2013112242 Aug 2013 WO
2013120015 Aug 2013 WO
2014026274 Feb 2014 WO
2015031993 Mar 2015 WO
Non-Patent Literature Citations (38)
Entry
English Abstract of DE102004045753.
International Preliminary Report on Patentability of the International Searching Authority, or the Declaration for PCT/CA2012/050080; dated Aug. 29, 2013, 6 pages.
International Search Report and the Written Opinion of the International Searching Authority, or the Declaration; for PCT/CA2012/005080; dated May 16, 2012, 13 pages.
International Search Report and the Written Opinion of the International Searching Authority, or the Declaration; for PCT/CA2014/050837; dated Oct. 27, 2014, 20 Pages.
International Search Report and the Written Opinion of the International Searching Authority, or the Declaration; for PCT/CA2014/050854; dated Nov. 6, 2014, 8 Pages.
International Search Report and the Written Opinion of the International Searching Authority, or the Declaration; for PCT/CA2010/000039 dated Oct. 15, 2010, 9 Pages.
Corrected International Search Report and the Written Opinion of the International Searching Authority, or the Declaration; for PCT/CA2012/050080; dated Jun. 4, 2012, 16 pages.
International Search Report and the Written Opinion of the International Searching Authority, or the Declaration; for PCT/CA2013/050598; dated Nov. 8, 2013, 13 Pages.
International Preliminary Report on Patentability of the International Searching Authority, or the Declaration for PCT/CA2013/050598; dated Sep. 4, 20014, 52 pages.
Machine Translation of claims of DE102004045753.
Machine Translation of Specification of DE102004045753.
Notification of Transmittal of the International Search Report and the Written Opinion of the International Searching Authority, or the Declaration; PCT/CA2014/051006; dated Dec. 23, 2014, 9 Pages.
Singapore Search Report dated Oct. 15, 2013 for Application No. 201205195-9, 18 Pages.
Notification of Transmittal of the International Preliminary Report on Patentability and the Written Opinion of the International Searching Authority, or the Declaration; PCT/CA2015/0051369; dated Mar. 8, 2016, 8 pages.
Supplementary European Search Report for application No. EP13829390; dated Mar. 2, 2016, 2 pages.
International Search Report for International Application No: PCT/CA2015/0051369; International Filing Date: Dec. 23, 2015; dated Mar. 8, 2016; 8 pgs.
Supplementary European Search Report for application No. EP13829390.7; dated Mar. 9, 2016; 9 pgs.
“Interoperability and Integration of Dismounted Soldier System Weapon Systems Update”; Mr. Mark Richter; Chairman; SCI-178 RTG-043; May 21, 2008, 38 Pages.
“Interoperability and Integration of Dismounted Soldier System Weapon Systems”; Major Bruce Gilchrist on behalf of Mr. Mark Richter; SCI-178 RTG-043; May 20, 2009.
“NATO Small Arms Weapons Research & Technology Study”; Per G. Arvidsson; Team Leader Technical Interfaces; NATO RTO Study SCI-178/RTG-043, 13 Pages.
“Powered Rail”; Presentation to Intl Infantry & Joint Service Small Arms System Symposium; May 20, 2009; Torbjoern Eld, Chairman; Powered rail team; NATO SCI-178/RTG-043, 9 Pages.
CA Examination report for Application No. 2014331482, dated Mar. 22, 2017, 4 pages.
CA Offfice Action for Application No. 2,923,513, dated Apr. 28, 2017, 5 pages.
European Search Report for Application No. 15878323, dated Aug. 9, 2018, 3 pages.
European Search Report for Application No. EP 14 84 1869; dated Aug. 22, 2017.
European Search Report for Application No. EP 14 85 1134; dated Aug. 23, 2017, 3 pages.
European Search Report for Application No. EP 14 88 9015; dated Aug. 23, 2017.
European Search Report for Application No. EP 16 19 5258, dated Mar. 29, 2017, 4 pages.
European Written Opinion for Application No. 16162291.5; dated Jun. 22, 2016; 3 pgs.
Extended European Search Report for EP Application No. 16162291.5; dated Jun. 22, 2016.
Hoffman, Mike, “DARPA Develops Infantry Helmet Heads Up Displau”, Kit Up!, Oct. 5, 2017, 9 pages.
International Search Report for International Application No. PCT/CA2016/050591; International Filing Date: May 26, 2016; dated Jul. 21, 2016; 4 pgs.
Supplementary European Search Report for Application No. 15878323.3-1206, dated Aug. 9, 2018 3 pages.
Supplementary European Search Report for Application No. 16798995, dated Nov. 30, 2018, 3 pages.
Written Opinion for Application No. EP 14 85 1134; dated Aug. 23, 2017, 4 pages.
Written Opinion for Application No. EP 14 88 9015; dated Aug. 23, 2017.
Written Opinion for International Application No. PCT/CA2016/050591; International Filing Date: May 26, 2016; dated Jul. 21, 2016; 6pgs.
Written Opinion of Application No. 16798995.3, dated Nov. 30, 2018, 6 pages.
Related Publications (1)
Number Date Country
20150285599 A1 Oct 2015 US
Provisional Applications (2)
Number Date Country
62003006 May 2014 US
61976157 Apr 2014 US
Continuation in Parts (2)
Number Date Country
Parent 14481542 Sep 2014 US
Child 14517334 US
Parent 14476210 Sep 2014 US
Child 14481542 US