Search

By number By text StandardPublic Safety & Disaster

Categories (match all selected)Network Operators Service Providers Equipment Suppliers Property Managers Public Safety Government Cable Internet/Data Satellite Wireless Wireline Access Control Buildings Business Continuity Contractors & Vendors Corporate Ethics Cyber Security Disaster Recovery Documentation Emergency Preparedness Essential Services Facilities-Transport Fire Guard Services Hardware Human Resources Industry Cooperation Information Protection Liaison Materials Movement Network Design Network Elements Network Interoperability Network Operations Network Provisioning Pandemic Physical Security Management Policy Power Procedures Public Safety Service Security Systems Software Supervision Technical Support Training and Awareness Visitors Encryption Intrusion Detection

1098 matching practices

Number	Best Practice
13-12-3225	Network Operators, Service Providers and Public Safety should ensure that the utilization on either node is less than half of each node\\\'s capacity so that if one node fails the other node will absorb the load. This applies to those that deploy geographically diverse 9-1-1 location servers with dual load sharing nodes.
13-12-3226	Network Operators, Service Providers and Public Safety should provide 24x7 network operations support.
13-12-3227	Network Operators, Service Providers, Equipment Suppliers and Public Safety should deploy location solutions such that the 9-1-1 related data traffic between the Network Operator\\\'s location server and the mobile device should not degrade voice quality.
13-12-3229	Network Operators, Service Providers and Public Safety should maintain all 9-1-1 call data according to all applicable governmental data retention requirements. In the absence of governmental data retention requirements, the call datashould be retained in accordance with FCC guidelines.
13-12-3230	Network Operators, Service Providers and Public Safety should maintain location event records that include time-stamped call detail transactions according to all applicable governmental data retention requirements. In the absence of governmental data retention requirements, the call data should be retained in accordance with FCC guidelines.
13-12-3231	Network Operators, Service Providers should ensure that the GPS satellite location identification information (e.g., GPS ephemeris, almanac, etc.) is transmitted to the Phase II Mobile Subscriber or Position Determining Entities (PDE) as soon as is feasible after the 9-1-1 call commences in order to reduce the number of database query rebids. This applies to those that use Global Positioning System (GPS) enabled Phase II location solutions.
13-12-3232	Equipment Suppliers should ensure that the Phase II handsets commence Global Positioning System (GPS) acquisition before the GPS satellite location identification information is received so that GPS acquisition time is minimized and to reduce the number of database query rebids.
13-12-3234	Network Operators, Service Providers and Public Safety should use Policy-based Routing and/or other tactical routing functionality defined for Next Generation 9-1-1 (NG9-1-1) to handle call congestion and outages through diversion of calls to alternate Public Safety Answering Points (PSAP) that have the capabilities to effectively answer and provide assistance during periods of extreme overload or network failure scenarios.
13-12-3245	Network Operators, Service Providers and Public Safety should develop policy routing procedures that consider the full capability of NG9-1-1, including the rerouting of calls from other PSAPs as a result of overflow, backup, and disaster situations. Inter-agency agreements should be updated to reflect the updated procedures.
13-12-3246	Network Operators should where MSC capabilities exist, route calls based on the location of the cell tower, to the MSC-SR trunks designated for that cell site to the serving PSAP. Switch level defaulted calls shall be routed to a \"fast busy\" tone or, where that option is not available, to an appropriate recorded announcement.
13-12-3247	Public Safety should conduct on-going meetings with several bordering or nearby PSAPs to clarify the wireless 9-1-1 call routing determination process. For example, it may be appropriate to route a cell site/sector based on the area covered or where the highest density population exists.
13-12-3248	Public Safety should obtain GIS data from bordering PSAP jurisdictions and expand and test their transfer list to bordering PSAPs. This is necessary as the routing of wireless 9-1-1 calls may require a PSAP to receive and transfer calls for an area larger than the wireline coverage area.
13-12-3255	Network Operators, Service Providers and Public Safety should use secure network protocols such as TLS or IPsec for HTTP network interconnection for data acquisition of location and additional data provided by reference. This applies to Public Safety only in an NG9-1-1 environment.
13-12-3256	Network Operators, Service Providers should ensure that location information is made available to Public Safety as soon as is feasible after the 9-1-1 call commences.
13-12-3257	Service Providers should route calls to the appropriate NG9-1-1 Next Generation Core Services (NGCS) based on the most accurate location information available. When location information is unavailable, OSPs should default route calls according to their internal policy, such as to an alternate call center.
13-12-3258	Network Operators, Service Providers and Public Safety should design Emergency Services IP Networks (ESInets), where technically and financially viable, with redundant interconnectivity to PSAPs using the characteristics of IP routing to maintain connectivity in the face of extensive disaster damage. Public Safety ESInets may use diverse private facilities or their functional equivalent (e.g., MPLS, generic routing encapsulation (GRE) tunneling, virtual private network (VPN), or equally secure industry protocols) and where appropriate and supported by service level agreements.
13-12-3259	Network Operators, Service Providers should design networks with redundant interconnectivity to Public Safety Emergency Services IP Networks (ESInets) using the characteristics of IP routing to maintain connectivity in the face of extensive disaster damage. OSPs may use diverse private facilities or their functional equivalent (e.g., MPLS, generic routing encapsulation (GRE) tunneling, virtual private network (VPN), or equally secure industry protocols) and where appropriate and supported by service level agreements.
13-12-3260	Network Operators, Service Providers and Public Safety should ensure that the NG 9-1-1 system elements and the network elements between the OSP and the ESInet support the most accurate location information available to route 9-1-1 calls.
13-12-3261	Network Operators, Service Providers and Public Safety should implement applicable industry standards to achieve interoperability between Real Time Text and TTY Baudot in support of emergency calling during the transition to end-state NG9-1-1. This applies to Public Safety only in an NG9-1-1 environment.
13-12-3262	Public Safety should provide training to educate PSAP personnel as to the process to acquire/de-reference initial/updated/supplemental location information, as well as how to interpret location information received in an NG9-1-1 environment.

Download matching Best Practices

Next results