Milestone 2

Project Plan

 

Execution 

The team intends to produce a device which will be capable of scanning the nearby area for friendlies and displaying any detected friendlies on a map. Scans will be performed using multipath reflective signaling. The device will also allow the user to scan a specific target if LOS is established. Friendlies may choose not to respond using a manual response mode. Signals will be largely untraceable. 

The team currently plans to implement the following features (see the Intended Features document for more detail): 

Testing of the device will primarily be performed in Hoboken, NJ. We expected the device to be used in urban/suburban areas. 

Constraints to be added 

  Refer to Concepts section 

MATLAB may be used to simulate the design in a virtual environment. Signals using OFDM, various mapping techniques, and data encryption may be simulated using MATLAB. Power loss due to reflections and other environmental conditions may also be simulated. The degraded signal will be demodulated and decrypted, allowing for error rate estimations. A MATLAB prototype may serve as proof of concept of the system. 

NI-USRP/LabVIEW Prototype

The system will be simulated using NI-USRP 2901 software-defined radio kits and LabVIEW virtual instruments. Instead of just simulating path-loss, signals may be truly wirelessly transmitted between SDRs. The prototype may be iterated to allow for multiple transceivers. This prototype should be relatively accurate to the final deliverable but will be larger and less convenient to use. 

Scan mode: A small digital map (on a tablet or helmet-based display) will display the surrounding area. When a scan is initiated, any identified allies will appear as glowing points on the map 

Targeting mode: When line of sight exists between the user and a potential ally, the user will aim at the target and press a button to initiate a targeted scan. A positive response will result in a small LED on the weapon lighting up. Alternatively, the device will vibrate. We are aware of the issues with requiring the user to aim at a potential ally. 

Manual Response Mode: When set to manual-response mode, whenever the user is scanned, a small LED will light up. Pressing a button will respond to the scan. Alternatively, the scan’s user ID will be displayed on the map. If the request comes from a compromised user, it may be ignored.  

 

See Concepts Section


See system block diagram. Additional detail to be added. 

See above. Additional detail to be added. 

John Jobin McAuliffe – Team leader responsible for team organization, decision making, and contact with customers. Will also lead development of physical and mechanical systems (antenna adjustment, weapon mounts, wearable components, etc.) and will oversee any testing, ensuring safety guidelines are followed. 

Benjamin Holko – Will direct user interface design, taking input from military contacts. Additionally, will contribute to signal processing systems (modulation, prefixing, etc.)  

Drew Pearlstein – Will contribute to signal processing systems as described above. Will also lead development and integration of any hardware systems. 

Kenneth Kim – Will perform data encryption and decryption. Will also integrate radio systems with existing software (ATAK) and take the lead on any software-related aspects of the project. 

Matthew Petrin – Responsible for documentation of team activities. Will also calculate and model ray propagation and develop cognitive radio models. 

Kickoff Meeting: Project plan, quad chart, Gantt chart, and intended features list in rough forms will be provided. It is expected that these documents will be iterated on as the concept is refined. 

Design Reviews: 

The team will deliver an updated project plan, descriptions of any developments in the design, and any demonstrations as described below. 

Milestones:  

End Items: We expect to deliver a set of transceivers, batteries, antennae, and user interfaces, as described in the Scope of Work. The team also expects to deliver a program, series of programs, and/or ATAK plugin alongside the physical system. The system should be capable of performing all functions specified within this document. The system should be capable of requesting GPS data from nearby users via reflected and encrypted signals and should also be capable of receiving GPS data from nearby allied devices using the same signaling method. An effective range of 1 km and a battery life of 3 days is expected.  

Video Summary: The team will deliver a video summary of the project, demonstrating and explaining the devices basic functions and uses. 

We plan to demonstrate that we can: 

Physical deliverables will be delivered either to William Shepherd, a nearby DoD contact, or to the DoD via physical mail. Software, videos, documents, and data deliverables will be delivered via email, Microsoft Teams, and/or GitHub. Functionality of design elements may also be demonstrated via video conferences with the customer. 

Upon completion of the project in April 2023, all hardware associated with the project paid for by the DoD will be delivered via mail or a physical contact. Any software developed for the project will also be delivered to the DoD via its preferred method. Hardware and equipment owned/provided by Stevens Institute of Technology and team members will not be delivered to the DoD. Copies of Capstone team documents and media shall be archived at Stevens Institute at the conclusion of each review and during closeout. Copies of all team documents will also be provided to the DoD at its request.  

Concept of Operations Alpha

Concept of Operations Beta 

Concept of Operations/Operations Flowchart

Concept of Systems/System Flowchart