N241-056 TITLE: Autonomous, Mission-based Traffic Engineering
OUSD (R&E) CRITICAL TECHNOLOGY AREA(S): Integrated Network Systems-of-Systems; Trusted AI and Autonomy
OBJECTIVE: Develop autonomous, mission-based traffic prioritization mechanisms/techniques and orchestration to ensure network priorities are aligned with the Commander’s Intent – especially during contested operations when there will not be sufficient network resources to satisfy all of the operational needs.
DESCRIPTION: Tactical networks typically contain an admixture of critical, essential, and non-essential traffic. Criticality of the traffic depends on the types of missions that are currently being executed, mission phase, etc. and is, consequently, highly dynamic. Reference (1) outlines command and control (C2) constructs for the U.S. Navy and Army. These constructs have different warfare commanders, functional commanders, and coordinators – with different network applications / priorities – that must be synchronized to achieve operational objectives. The Navy seeks technical solutions for (1) identifying different types of traffic, (2) associating each traffic type with specific platforms as well as functions/missions, (3) enabling the Commander to prioritize these functions/missions, and (4) translating the Commander’s prioritization into network policies that can be implemented across the network to ensure, to the extent possible, end-to-end delivery of mission-critical traffic.
There are two main technical challenges that must be solved:
(1). Reliable mapping of Commander’s intent and mission objectives into structured data forms that can be combined with policy representations and reasoned with by machines. Supervised Natural Language Processing (NLP) training requires more exemplars than may be available given the highly dynamic nature of Commander’s intent or mission objectives. Machine representations need to precisely capture the original human meaning within the intent as well. Reference 2 provides an overview of the application of artificial intelligence in different areas of the private sector.
(2). How to combine machine representations of policies? Ontologies can be used to capture schema but live tactical feeds for situation awareness, which may be ad hoc, are also critical.
PHASE I: Develop a framework/approach to address the challenges outlined above. Prepare a report documenting the proposed framework/approach along with any preliminary results or data that help demonstrate the viability of the proposed approach. Include in the report a proposed set of benchmarks for assessing performance of the framework and a clear articulation on how the framework is viable with incomplete training data sets. The latter is important because warfare commanders are individuals who have different preferences for receiving and displaying information to support a decision.
PHASE II: Implement the proposed framework using representative data sets for different functions or missions. Demonstrate how the framework correctly interprets intent and then translates that intent into traffic engineering policies. Show how this intent is met both with dynamic network demand and changing circumstances (e.g., priorities change due to a triggering event). Prepare a report documenting the framework implemented, how it was tested, the resulting performance, and recommendations or lessons learned for future implementations.
PHASE III DUAL USE APPLICATIONS: Integration and transition into ADNS is the objective of Phase III. The commercial sector has historically relied on fixed, terrestrial networks and can either easily procure more bandwidth to alleviate congestion or add redundancy. For truly mission critical traffic, the commercial sector builds dedicated networks with dedicated resources to guarantee performance. However, the push towards 5G deployment and increasing need for real-time control systems for autonomous vehicles, automated manufacturing, smart city concepts, etc. are pushing the commercial sector to develop prioritization mechanisms and how to orchestrate their employment across the network to ensure end-to-end delivery of mission-critical traffic. A potential commercial transition option that can be explored is to integrate the algorithms developed into the zero-touch network management solutions developed for 4G/5G mobile services by ZTouch.
KEYWORDS: Command, Control, Network, Prioritization, Mission, Automated, Dynamic, artificial intelligence/machine learning, AI/ML
** TOPIC NOTICE **
The Navy Topic above is an "unofficial" copy from the Navy Topics in the DoD 24.1 SBIR BAA. Please see the official DoD Topic website at www.defensesbirsttr.mil/SBIR-STTR/Opportunities/#announcements for any updates.
The DoD issued its Navy 24.1 SBIR Topics pre-release on November 28, 2023 which opens to receive proposals on January 3, 2024, and now closes February 21, (12:00pm ET).
Direct Contact with Topic Authors: During the pre-release period (November 28, 2023 through January 2, 2024) proposing firms have an opportunity to directly contact the Technical Point of Contact (TPOC) to ask technical questions about the specific BAA topic. Once DoD begins accepting proposals on January 3, 2024 no further direct contact between proposers and topic authors is allowed unless the Topic Author is responding to a question submitted during the Pre-release period.
SITIS Q&A System: After the pre-release period, until January 24, 2023, at 12:00 PM ET, proposers may submit written questions through SITIS (SBIR/STTR Interactive Topic Information System) at www.dodsbirsttr.mil/topics-app/ by logging in and following instructions. In SITIS, the questioner and respondent remain anonymous but all questions and answers are posted for general viewing.
Topics Search Engine: Visit the DoD Topic Search Tool at www.dodsbirsttr.mil/topics-app/ to find topics by keyword across all DoD Components participating in this BAA.