Launch Requirements - PSCR

Technical Requirements
Public Safety Broadband
public safety multimedia messaging. The report describes capabilities that build upon concepts
associated with NG9-­‐1-­‐1 for public safety emergency and non-­‐emergency text and multimedia
messaging. See also Section 4.1.6 for requirements associated with NG9-­‐1-­‐1 messaging.
4.1.9 Video Services
The use of video technology by public safety is extensive, and is expected to grow significantly over the
next 10 years. NPSTC’s Public Safety Communications Assessment 2012 – 2022, June 5, 2012 [8],
explored numerous video needs. The following text is referenced from NPSTC’s June 2012 assessment:
“Incident command staff and supervisors identified the need to access vehicle-­‐mounted video
cameras in fire/rescue and law enforcement vehicles on an as-­‐needed basis (versus a continual
video feed). The video feed would allow command post and Emergency Operations Center (EOC)
personnel to visualize the incident scene in relation to damage and apparent needs when
compared to other incident scenes. Vehicle-­‐mounted video also enhances on-­‐scene safety by
allowing third parties to check on the incident scene, verify that personnel are accounted for, and
monitor the success or failure of the incident mitigation plan. Vehicle-­‐mounted video also allows
the Incident Command team to “see” the incident and develop a better perspective of the
operational requirements. In the absence of video, the command staff must rely on a radio
transmission description of the scene from first arriving units.”
Nearly all current video applications are localized. That is, the source cameras and responders using the
video information are localized to the areas they serve. While video is not typically sourced from one
location across the country, video is more often shared between responding agencies (PSEs) for a given
incident.
The NPSTC Video Quality in Public Safety (VQiPS) group is investigating methods to define and quantify
public safety video. For example, tactical video may be determined to require a given CODEC, frame
rate, resolution, etc. This section will not focus on those application-­‐specific CODECs and parameters. It
is understood that CODEC technology will evolve over time, potentially altering the parameters
(bandwidth, latency, packet loss) used by the NPBSN.
The NPSBN only “sees” attributes such as bandwidth, latency, packet loss, etc. These attributes should
be taken advantage of as the system is built out over time. However, in concentrating on what is critical
for launch, the requirements in this section focus on the ability of the NPSBN to provide functionality for
one or more PSENs to stream video traffic in real-­‐time to one or more other PSENs.
This section focuses on two primary sets of needs for NPSBN-­‐Us:
! The NPSBN enabling PSEN-­‐deployed video applications
! NPSBN-­‐deployed video services
Following are requirements for the NPSBN to enable local PSEN video applications.
34 Launch Statement of Requirements
for FirstNet Consideration, December 2012