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.
Technical <strong>Requirements</strong><br />
Public Safety Broadband<br />
Following are requirements to prevent the unintentional disclosure of NPSBN-‐U information while using <br />
the telephony service. The intent of these requirements is to prevent the NPSBN-‐U’s telephone number <br />
and addressing information from being shared under certain circumstances. <br />
Table 27. Telephony Confidentiality <strong>Requirements</strong><br />
# Requirement<br />
1 The NPSBN SHALL allow authorized PSE O&M Users to configure with which networks an <br />
NPSBN-‐U’s calling address (e.g., telephone number) is shared. <br />
This requirement allows the blocking or sharing of caller ID information on a network-‐to-network<br />
basis based upon the operational desires of the PSE. If the PSE desires to control the <br />
sharing of caller ID information on a per network granularity, it is undesirable to require an <br />
NPSBN-‐U, on a per-‐call basis, to enable or disable “Caller ID Block.” <br />
2 The NPSBN SHALL allow authorized PSE O&M Users to configure which NPSBN user classes an <br />
NPSBN-‐U’s calling address (e.g., telephone number) is shared. <br />
The intent of this requirement, for example, is to prevent the NPSBN-‐U’s telephone number <br />
and addressing information from being shared with secondary users on the NPSBN. For <br />
example, federal users may only want to share their telephone number with other federal <br />
users. ‘User classes’ can be groupings such as ‘primary users’, ‘secondary users’, ‘federal users’, <br />
etc. <br />
3 Should the PSE O&M user block transmission of an NPSBN-‐U’s calling address to another <br />
network, user class, or device, the receiving system SHALL be presented with a caller <br />
identification of “Unknown.” <br />
4 PSE O&M users SHALL have the ability to configure a NPSBN-‐U such that a per call block, will <br />
block all data being sent regardless of network or user class. <br />
5 The NPSBN SHALL provide confidentiality for all VoIP signaling traffic from the NPSBN-‐U device <br />
to the telephony application server. <br />
The intent is that signaling information for an NPSBN-‐U’s telephony session not be viewable <br />
while in transit; especially when the NPSBN-‐U is roaming outside the NPSBN. <br />
6 For telephony calls between two or more NPSBN-‐Us homed to the NPSBN (i.e., NPSBN <br />
subscribers), it SHALL be possible for the originating NPSBN-‐U to choose end-‐to-‐end encryption <br />
of a voice conversation on a per-‐call basis. <br />
In this context, end-‐to-‐end means from the source device to the destination device(s) in the <br />
NPSBN network. Encryption on an end-‐to-‐end basis will likely require both end devices to <br />
support the desired encryption. <br />
28 <strong>Launch</strong> Statement of <strong>Requirements</strong><br />
for FirstNet Consideration, December 2012
Change language