Launch Requirements - PSCR
Launch Requirements - PSCR
Launch Requirements - PSCR
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
Executive Summary<br />
Public Safety Broadband<br />
public safety requires a very robust prioritization scheme that can be enacted at the local level. This is <br />
especially true in large-‐scale events that have established hierarchy with role-‐based levels of priority. <br />
Some situations are of such critical importance that certain network traffic should be able to pre-‐empt <br />
lower level traffic. Strict controls and national standards need to exist for this type of pre-‐emption to <br />
curtail any potential abuse. <br />
Resiliency<br />
Public safety responders need to be able to exchange information even when any piece of the network <br />
is unavailable due to failure, such as in the event of a natural disaster. This makes off-‐network, peer-‐to-peer,<br />
and self-‐healing capabilities critically important. Redundancy is one traditional approach to <br />
building high availability networks, but high network availability could be achieved by designing the <br />
network with resiliency, which could result in a lower deployment cost. <br />
Security<br />
Public safety processes sensitive information on a daily basis, which requires robust security measures <br />
to ensure integrity, confidentially, privacy protection, and information assurance. A nationwide public <br />
safety broadband network would be an obvious target for cyber attack. This fact requires that extensive <br />
security measures be enacted to prevent attacks on the network to include but not be limited to cyber-attacks,<br />
physical site security, and denial of service. <br />
NPSBN High-Level <strong>Requirements</strong><br />
The establishment of high-‐level technical and administrative launch requirements for the NPSBN will <br />
form a firm foundation for subsequent detailed requirements for the NPSBN and expected support <br />
activities that FirstNet will undertake. <br />
The high-‐level launch requirements defined in this document are intended for FirstNet consideration in <br />
its design, development, deployment, operation, and evolution of the NPSBN. <br />
Managing Expectations<br />
Although this Statement of <strong>Requirements</strong> document describes the “<strong>Launch</strong> Day” needs of public safety, <br />
there are features and functionality not listed that require the attention of FirstNet. Any Request for <br />
Proposal (RFP) issued by FirstNet should be written to leverage the efficiency of a long-‐term vision <br />
during the initial build out. For example, if mission critical voice is envisioned to become part of the <br />
NPSBN, the RFP should consider this in defining coverage requirements. <br />
Various requirements in this document refer to public safety grade (PSG). While the meaning of this <br />
terminology was not defined at the time of this document’s completion, the NPSTC Broadband Working <br />
Group (BBWG) plans to define the terminology as quickly as possible, for use by FirstNet in system <br />
design. For now, the intent of the PSG terminology is to convey the need for design choices that support <br />
a greater overall network reliability and resiliency to network disruptions compared to commercial <br />
<strong>Launch</strong> Statement of <strong>Requirements</strong><br />
viii for FirstNet Consideration, December 2012