NPSBN_Section_J-19_State_Plan_Template_AMEND_009.pdf

Solicitation No. D15PS00295 – Section J, Attachment J-19 State Plan Template

Page J-19 – i Amendment 009

Table of Contents

1 Purpose

2 FirstNet Overview and Mission

3 State Consultation

3.1 State Governing Body

3.2 [State Name] Consultation Process

3.3 Outreach and Education Support

3.4 State Plan Inputs and Outcomes

3.4.1 Minimum Criteria for a State Plan

3.4.2 Coverage Objectives

3.4.3 User Profiles/Statistics

3.4.4 Capacity Planning

3.4.5 Current Mobile Data Usage

3.5 State Decision Process

3.5.1 Summary/Timeline of Actions Required by the State

3.5.2 Changes to State Plan Following Decision to Proceed with FirstNet-Deployed

Radio Access Network

4 State Radio Access Network Plan

4.1 Radio Access Network Partner

4.2 Network Design and Key Assumptions

4.2.1 Coverage Objectives and Requirements

4.2.2 RESERVED

4.2.3 Link Budget Specifications

4.2.4 Equipment Performance Specifications

4.2.5 Early Builder Integration

4.2.6 Temporary Coverage Related to Incidents and Planned Events

4.3 State Coverage Summary

4.3.1 Persistent Coverage

4.3.2 Coverage Extension Assets for Purchase by Public Safety Entities

4.3.3 Non-Persistent Cellular Service and Devices

4.4 Deployment Phases and Timelines

4.5 Rural Milestones

4.6 Network Upgrade and Expansion

4.7 State Assets

4.7.1 Memorandum of Understanding/ Memorandum of Agreement Requirements .. 6

4.7.2 Tower Sites

4.7.3 Backhaul

4.7.4 Other State Assets

4.8 Spectrum Clearing

5 Public Safety Grade

5.1 Coverage and Hardening

5.2 Installation

Page J-19 – ii

5.3 Operations and Maintenance

5.3.1 Service Availability

5.3.2 Customer Care and Support

5.3.3 Services Management Center

5.3.4 Status Reporting to States and Territories

5.3.5 Public Safety Enterprise Network/Public Safety Answering Point Integration

5.4 Network Reliability

5.5 Network Resiliency

5.6 Network Redundancy

5.7 Environmental Factors

5.8 Security

5.8.1 Security Architecture Plan

5.8.2 Security Integration and Test Plan

5.8.3 Applications Security Plan

5.8.4 Security Monitoring Plan

5.8.5 Security Configuration Management Plan

5.8.6 Technical Analysis and Security Review of Security Tools

5.8.7 Physical Security Plan

5.8.8 Cybersecurity Incident Response Plan

6 Network Operator/User Training Requirements

7 State Decision Process/Requirements/Timeline

7.1 Proceeding with FirstNet-Deployed RAN – Next Steps and Process to Submit

Questions

7.2 Consultation Roles and Responsibilities after the Plan is Accepted

7.3 Decision to Proceed with State-Deployed RAN – Procedures

7.3.1 Decision to Proceed with State-Deployed RAN Plan Requirements

7.3.2 Decision to Proceed with State-Deployed RAN Plan Criteria

7.3.3 Decision to Proceed with State-Deployed RAN Plan Submission Process

7.4 Timeline

APPENDIX A FirstNet Nationwide Design A.1 End-to-End Network Architecture

A.1.1 State RAN Architecture A.1.2 Nationwide Core Architecture A.1.3 Backhaul, Aggregation, Transport, and National Transmission Network

Architecture A.1.4 Operational Support System Architecture A.1.5 Business Support System Architecture A.1.6 Applications Architecture A.1.7 Interconnection Architecture

A.2 End-to-End Network Design (Logical and Physical) A.2.1 Radio Access Network Design A.2.2 Core Design A.2.3 Backhaul and Transport Design A.2.4 Operational Support System Design A.2.5 Business Support System Design

Page J-19 – iii

A.2.6 Applications and Services Design A.2.7 Interconnection Design

A.3 Products and Services A.3.1 Products Roadmap A.3.2 Services Roadmap

A.4 Nationwide Core Network A.4.1 Roaming Strategy A.4.2 Roaming Partner Integration A.4.3 Network Specifications A.4.4 Session Continuity

A.5 Logical Architecture (System Views for User and Control Plane) A.5.1 Covered Leasing Agreement User Integration A.5.2 Compliance to 3GPP Standards MVNO Strategy A.5.3 Key Core Network Locations A.5.4 Radio Access Network Backhaul Architecture and Topology A.5.5 Radio Access Network Backhaul Aggregation Transport Network A.5.6 National Transmission Network A.5.7 Transport Security A.5.8 Routing and DRA strategy A.5.9 Transport Service Prioritization

A.6 Network Services A.6.1 Basic Services A.6.2 Mission Critical Services A.6.3 Quality of Service, Priority, and Preemption

A.7 Network Implementation A.7.1 Integration Partners A.7.2 Network Naming and Identification A.7.3 Design Assumptions A.7.4 IP Strategy A.7.5 Heterogeneous Network Integration A.7.6 Numbering Plan A.7.7 PSEN and PSAP Integration A.7.8 PSTN, ISP and Peering Integration A.7.9 PLMN and Roaming Partner Integration A.7.10 State-Deployed RAN Integration A.7.11 Support for LMR Network Integration

A.8 Project Plan/Schedule A.8.1 MVNO to NPSBN Core/RAN Migration A.8.2 Number Portability

APPENDIX B Device Strategy, Roadmap, and Support B.1 Device Portfolio Available to PSE B.2 Device Acceptance Process B.3 Users B.4 Bring Your Own Device Policy B.5 Device Pricing B.6 Device Support and Life-Cycle Management

Page J-19 – iv

B.7 Local Control and Management of User Devices B.8 Device Support of Network Services B.9 Device Support of Commercial Band Access to Cellular Service B.10 Roadmap for Device Support of New Features and Services B.11 SIM/UICC Distribution Process and Management

APPENDIX C Application Strategy and Operations

C.1 Baseline Launch Applications C.2 Applications Storefront C.3 Applications Management C.4 Applications Security C.5 Local Control C.6 Applications Certification C.7 Public Safety Entity Home Page C.8 Applications Developer and Publication C.9 API Taxonomy C.10 Applications Product Roadmap

APPENDIX D Deployable Assets D.1 Deployable Operations D.2 Fleet Management D.3 Activation D.4 Incident Management D.5 Deployable Integration/Backhaul D.6 Roles and Responsibilities (State or Territory/FirstNet)

APPENDIX E Financials E.1 Covered Leasing Agreement/Excess Network Capacity Value E.2 FirstNet Value Proposition E.3 User Fees/Costs E.4 Procurement Vehicles E.5 Funding Allocation for Buildout within the State or Territory E.6 Core Network User Fee E.7 Infrastructure Leasing Fee

List of Tables

Table 1 Map Deliverables for Coverage and Capacity Table 2 Network Statistics Deliverables

Page J-19 – 1

1 Purpose

Text for this section will be provided by the First Responder Network Authority (FirstNet).

2 FirstNet Overview and Mission

Text for this section will be provided by FirstNet.

3 State Consultation

Text for this section will be provided by FirstNet.

3.1 State Governing Body

Text for this section will be provided by FirstNet.

3.2 [State Name] Consultation Process

Text for this section will be provided by FirstNet.

3.3 Outreach and Education Support

Text for this section will be provided by FirstNet.

3.4 State Plan Inputs and Outcomes

Text for this section will be provided by FirstNet.

3.4.1 Minimum Criteria for a State Plan

Text for this section will be provided by FirstNet.

3.4.2 Coverage Objectives

Text for this section will be provided by FirstNet.

3.4.3 User Profiles/Statistics

Text for this section will be provided by FirstNet.

3.4.4 Capacity Planning

Text for this section will be provided by FirstNet.

3.4.5 Current Mobile Data Usage

Text for this section will be provided by FirstNet.

Page J-19 – 2

3.5 State Decision Process

Text for this section will be provided by FirstNet.

3.5.1 Summary/Timeline of Actions Required by the State

Text for this section will be provided by FirstNet.

3.5.2 Changes to State Plan Following Decision to Proceed with FirstNet-Deployed Radio Access Network

Text for this section will be provided by FirstNet.

4 State Radio Access Network Plan

Text for this section will be provided by FirstNet.

4.1 Radio Access Network Partner

Identify key network partners and their projected roles within the deployment of the Nationwide Public Safety Broadband Network (NPSBN). Consider including equipment and infrastructure vendors, backhaul services vendors, roaming network partners, network development partners, and state or county partners. Describe any plans to use existing assets, such as existing infrastructure, state, local, tribal, federal land parcels, or other assets.

4.2 Network Design and Key Assumptions

Provide the network planning and design information used for any submissions related to Band 14, including coverage and capacity submissions. Include the following information:

Link Curve – Provide a detailed link curve along with system simulation data showing the relationship between Signal-to-Interference-Plus-Noise Ratio (SINR), code rate, Modulation and Coding Scheme (MCS), and throughput.

Planning Tool Settings – Describe the settings used in the planning tool, including Multiple Input, Multiple Output (MIMO) gains; clutter weights/losses; and environment configurations.

Geo-Data – Provide a detailed description of the geo-data used (e.g., clutter, terrain, clutter height, buildings) including vintage, source, and resolution.

Propagation Models – Provide a detailed description of how the propagation models for planning were generated, noting if they were calibrated or un-calibrated. If calibrated models are utilized, describe how the models were calibrated.

Describe the general design methodologies used to provide indoor and outdoor coverage. Specifically, address the following topics:

• In-building Strategy Solutions – Articulate, with metrics, the level of in-building coverage available at each Initial Operational Capability (IOC)/Final Operational Capability (FOC) milestone for Band 14 and any non-Band 14. Within the metrics, include the area covered (in square miles), population covered, and proportion of footprint coverage with useable in-building signal levels. In areas where in-building penetration from the macro network is inadequate, describe

Page J-19 – 3 Amendment 009 the techniques that will be used to enhance in-building coverage. Identify which in-building solutions will be served with or without Band 14 and include a list of locations for each in-building solution. Take into consideration the size of the in-building location to be covered, expected traffic, and types of services to be supported in the area of interest when selecting the type of in-building systems to be used.

Transportation Infrastructure – Describe the deployment strategy to serve different modes of transportation (e.g., tunnels, railways, ports and waterways, airports, roads). Provide the design, methodologies, sources, and methods used to identify transportation infrastructure coverage requirements and the methodology to determine the appropriate level of indoor, outdoor, and underground service. Provide details on the approach to integration of in-building solutions with the NPSBN.

4.2.1 Coverage Objectives and Requirements

Text for this section will be provided by FirstNet.

4.2.2 RESERVED

[This section was removed in its entirety.]

4.2.3 Link Budget Specifications

Provide the detailed link budget information utilized in the development of the provided coverage maps.

The link budget should be provided for all morphologies (dense urban, urban, suburban, and rural) and for each of the 56 states and territories. Within the link budget, include the following information:

• Assumptions, margins, and gains accounted for in downlink and uplink

• Impacts due to various device types

• Maximum allowable path loss, design thresholds, and cell radius

4.2.4 Equipment Performance Specifications

Describe the proposed Radio Access Network (RAN) vendor portfolio, scope of equipment, and feature interoperability to be included with the NPSBN. Provide specifications where applicable and, at a minimum, include the following information:

• A diagram and description of the Long Term Evolution (LTE) base station and sectors, including the antenna system and backhaul components. Identify areas of resource aggregation or redundancy. Describe redundancy mechanisms available in the event a radio fails

• A description of variants of Enhanced Node Base station (eNodeB) platforms available in the current architecture, including specifications for each platform

• Hardware or software techniques utilized to maximize coverage and capacity (e.g., MIMO, carrier aggregation)

• A dimensioning guide for all capacity-dependent hardware and software in the eNodeB. Within the guide, describe the traffic load used in the dimensioning calculation as well as any assumptions made for redundancy

• Solution details if antennae are shared with another frequency band

• The maximum number of radio bearers supported by each variant eNodeB platform

Page J-19 – 4

• Details for configurations in which remote radio is involved (e.g., integrated antenna, separate antenna)

• A description of the RAN’s congestion management capabilities that would be leveraged in heavy traffic situations

• A description of which of the 16 3GPP-defined Random Access Resource configurations are supported by each eNodeB platform

• A description of all RAN security features

4.2.5 Early Builder Integration

If the proposed solution includes early builder assets, describe the level of effort, strategy, and timelines required to acquire, integrate, and assimilate the early builder equipment and services (“assets”) in the respective geographic areas. Describe the early builder assets and how they will be acquired, integrated, and assimilated.

4.2.6 Temporary Coverage Related to Incidents and Planned Events

Describe the strategy for providing temporary incident-level coverage (Band 14 and non-Band 14) and addressing capacity issues using deployable units, satellite, direct mode, or a combination thereof.

Describe how temporary coverage and capacity will be provided for areas that are not covered with persistent LTE services. Describe the temporary coverage strategy and solution(s) tailored for each of the individual states and territories.

4.3 State Coverage Summary

Provide descriptions for the state coverage elements listed below.

4.3.1 Persistent Coverage

Submit coverage maps and network statistics, as defined in Table 1 Map Deliverables for Coverage and Capacity and Table 2 Network Statistics Deliverables below, for each of the 56 states and territories to address public safety’s needs for coverage and capacity. The coverage maps should depict the cell edge—as defined in Section J, Attachment J-1, Coverage and Capacity Definitions—and service area coverage (i.e., minimum achievable throughput) for the following areas:

• Non-Band 14 Area Coverage

• Non-Band 14 Population Coverage

• Band 14 Network Capacity

• Band 14 Area Coverage

• Band 14 Population Coverage

Table 1 Map Deliverables for Coverage and Capacity

Level Band Phase Number of Maps Required Format

Nationwide Non-Band 14 IOC-1, IOC-2, IOC-3, IOC-4, IOC-5, and FOC

Six (6) maps of each file type, depicting coverage by technology:

LTE, 3G, 2G, and roaming.

Esri shapefiles (.shp) and MapInfo (.grd/.tab) files

Nationwide Band 14 IOC-1, IOC-2, IOC-3, IOC-4, IOC-5, and FOC

Six (6) maps of each file type with the LTE analysis layers

Esri shapefiles (.shp) and MapInfo (.grd/.tab) files

Page J-19 – 5

Table 2 Network Statistics Deliverables

Coverage Type Level Phase

Non-Band 14 Area Covered ** State/Territory IOC-1, IOC-2, IOC-3, IOC-4, IOC-5, and FOC

Non-Band 14 Population Covered State/Territory IOC-1, IOC-2, IOC-3, IOC-4, IOC-5, and FOC

Band 14 Area Covered State/Territory IOC-1, IOC-2, IOC-3, IOC-4, IOC-5, and FOC

Band 14 Population Coverage State/Territory IOC-1, IOC-2, IOC-3, IOC-4, IOC-5, and FOC

Band 14 Network Capacity County IOC-1, IOC-2, IOC-3, IOC-4, IOC-5, and FOC

** Note: Area coverage statistics should be broken down by technology—LTE, 3G, 2G, and roaming.

Provide the following LTE analysis layers for all Band 14 coverage maps, as noted in Table 1 Map Deliverables for Coverage and Capacity:

Reference Signal Receive Power (RSRP)

Best Server

Downlink SINR

Uplink SINR

MCS

Downlink Average Data Rate

Uplink Average Data Rate

Provide a composite coverage map with tiered bands to represent areas of expected in-building, in-vehicular, and handheld outdoor coverage.

4.3.2 Coverage Extension Assets for Purchase by Public Safety Entities

Provide a comprehensive list of coverage extension assets, such as a Vehicular Network Systems (VNSs) that will be available to Public Safety Entities (PSEs) for purchase via the customer-facing Web-based portal.

4.3.3 Non-Persistent Cellular Service and Devices

Provide a comprehensive list of non-persistent cellular services, and associated devices, that will be available to a PSE for purchase via the customer-facing Web-based portal. This list may include but is not limited to a VNS with satellite fallback connectivity, a VNS with local eNodeB, Evolved Packet Core (EPC) and applications support, devices that support direct mode (D2D), devices that support Wi-Fi, and devices that support Bluetooth.

4.4 Deployment Phases and Timelines

Provide a schedule noting the timeline for achieving the IOC/FOC milestones for coverage and capacity.

Provide a schedule that aligns with the IOC/FOC milestones and describes the planned deployment of coverage by state/territory. Describe roaming networks that may be used in addition to the NPSBN and other networks such as a Mobile Virtual Network Operator (MVNO) network (if applicable).

4.5 Rural Milestones

Page J-19 – 6

4.6 Network Upgrade and Expansion

The Offeror shall describe the strategy to support necessary network expansion. The strategy shall address coverage, quality, and capacity improvements to the NPSBN and include methodologies and thresholds used to trigger Offeror-defined actions. Improvements may be needed to address the following areas:

Coverage – Extension of coverage to serve new areas (e.g., increase of service area footprint)

Capacity – Additional capabilities to address network congestion (e.g., cell density)

Quality – Improvement of existing capabilities to meet local performance objectives (e.g., strengthening indoor and outdoor coverage)

Provide a framework to facilitate collaboration with local, state, tribal, and federal governments to improve the NPSBN service area and capabilities. Within the framework, address shared or independent efforts to align the NPSBN demand and services. Detail the proposed expansion of in-building coverage via government-owned/supplied equipment.

Describe the strategy, methodologies, and decision thresholds needed to improve:

• Equipment/System Overlays – Describe the process for repairing or replacing NPSBN equipment due to feature additions or changes in equipment vendors.

• Technology Migration – Describe the process for system-wide migration (e.g., 4G to 5G).

4.7 State Assets

Text for this section will be provided by FirstNet.

4.7.1 Memorandum of Understanding/ Memorandum of Agreement Requirements

Text for this section will be provided by FirstNet.

4.7.2 Tower Sites

Text for this section will be provided by FirstNet.

4.7.3 Backhaul

Text for this section will be provided by FirstNet.

4.7.4 Other State Assets

Text for this section will be provided by FirstNet.

4.8 Spectrum Clearing

Text for this section will be provided by FirstNet.

5 Public Safety Grade

Page J-19 – 7

5.1 Coverage and Hardening

Describe the network coverage and capacity hardening strategy to be implemented in order to achieve the service availability objectives noted in Section C, Statement of Objectives. Describe plans to exceed local building codes/standards (e.g., deployable strategy, selective site hardening, self-organizing network). Provide a concise summary of the methodology to be employed to ensure that the RAN components, sites structures, radio equipment, and interconnection are designed and implemented to be resilient against failures that can disrupt services to first responders.

5.2 Installation

Provide a schedule noting the timeline for achieving the IOC/FOC milestones for coverage and capacity.

Provide a schedule that aligns with the IOC/FOC milestones and describes the planned installation of the NPSBN by state/territory. Describe roaming networks that may be used in addition to the NPSBN and or other existing networks, such as an MVNO network (if applicable).

5.3 Operations and Maintenance

Text for this section will be provided by FirstNet.

5.3.1 Service Availability

Describe the solution to achieve the service availability objectives identified in Section C, Statement of Objectives. Address proposed methods for all layers of the network and associated quality improvement metrics gained as a result of the solution, especially in highly vulnerable key network nodes.

Describe how an integrated service support model that aligns with the Information Technology Infrastructure Library (ITIL®) or commercial equivalent will be delivered. Within the model, include configuration, change, incident, and release management processes.

Describe the National Incident Management System (NIMS) processes and how the processes facilitate communication with the incident commander and emergency operations center (EOC) during localized, regional, or national emergencies or incidents. These processes shall be consistent with Federal Emergency Management Agency guidelines and best practices and include:

A description of specific support organizations that are stood up in times of localized, regional, or national incidents that must interface, coordinate, and support on-site incident commanders and EOCs

A plan for reporting and communicating status and performance levels for local, state, tribal, and federal users

A plan for reporting and communicating impairments and resolution status levels for local, state, tribal, and federal users

A description of the release management processes in place to introduce features, functionality, and applications into the NPSBN without impacting user services

A description of the business continuity management processes in place, including provisions of disaster recovery and major event support to local, state, tribal, and federal agencies

Page J-19 – 8

A description of the ongoing service-level management processes that provide a continued baseline of system and per service performance, including proactive improvement plans for increased performance, service, and support of NPSBN users

A description of the availability management processes in place, including ongoing analysis of availability failures, contingency planning, and other activities and processes to ensure service availability objectives are met

A description of the capacity management processes in place to meet current and future NPSBN objectives. Include descriptions of how NPSBN utilizations, including computing, storage, network, and application sizing, will be managed to ensure ongoing service levels

A description of the national and local support structure to provide on-site support for both reactive and proactive configuration, maintenance, and monitoring activities. Include network optimization activities and quality assurance activities for the NPSBN

A description of the protocols and processes to address state and local support of natural disasters and major events requiring deployable assets. Include quantities of deployable assets and the default distribution of assets to support rapid response; procedures to request assets (both proactively and reactively); and a description of deployment, operations, and support during such events.

5.3.2 Customer Care and Support

Describe the proposed customer care strategy, including how the strategy minimizes churn and promotes customer retention among public safety users. Describe how an integrated customer care model will be delivered for public safety users. Provide a description of the customer care organization(s) that will support the NPSBN, including the organization’s function, size, structure, geographic distribution (e.g., whether resources are based in the United States; the location and number of employees/subcontractors located outside of the United States), and relation to the Offeror (i.e., in-house, contracted out). Describe the proposed solution for resolving customer service requests or issues with service delivery or products, including how the Contractor will provide responsive corrective actions for service impairments and service restoral when corrective action involves direct contact with the customer. Describe training the customer will be provided for devices and services.

Describe the proposed strategies for recruitment and retention of the customer care workforce, including how to train staff on existing and emerging products, services, and applications. Additionally, describe any customer care systems and tools that will be used in support of public safety customer care.

5.3.3 Services Management Center

Provide a clear, concise description that demonstrates how the Services Management Center (SMC) is structured. Include the following details:

• Describe the SMC location(s) and structure(s) that support the various network and service support functions, including applications, billing and provisioning, content services, devices, network (Core, RAN, Wide Area Network [WAN]), security, surveillance, and service desk.

• Describe the technical support staff and resources available among each network and service function and how service troubleshooting is orchestrated by the SMC for varying levels of service. Detail how the SMC is made aware of all on-call staff spanning local/on-site locations to Core/national locations.

• Describe the process of how public safety users originate a request or service issue into the SMC and how staff correlate and assess if a larger issue affecting users exists.

Page J-19 – 9

• Describe the network and element management systems that provide real-time monitoring and dashboards of the end-to-end network. Detail how individual alarms are rolled up and correlated to service-based events. Include how SMC staff members are effectively prepared to respond, resolve, or route events to the appropriate next tier of support.

• Detail how incidents are effectively managed and communicated based on the severity and location. Describe how an incident life cycle is managed and effectively handed off between SMC shifts. Describe how states and agencies can access and understand incident information in real time.

• Describe the management and Key Performance Indicators (KPIs) around messaging of service status as well as its effectiveness in the identification and resolution of service degradation issues.

• Training plan for all SMC staff.

• Continuity staffing plan for key SMC positions.

5.3.4 Status Reporting to States and Territories

Describe the mechanisms that will be used to report the status of the NPSBN to each of the 56 states and territories. A sampling of potential reports that Contractor may make available is listed below.

Deployment Status Report

Planned Maintenance Report

Planned Upgrade Report

Customer Care Summary Report

Customer Service Issue Resolution Report

Network Performance

Key performance indicators regarding coverage and capacity

Hardware and Software Change Management Report

Service Availability Report

Business Continuity Testing Report

Disaster Recovery After-Action Report

Hardware and Software (Past and Future) Release Management Report

5.3.5 Public Safety Enterprise Network/Public Safety Answering Point Integration

Describe the approach to integrating Public Safety Enterprise Networks (PSENs) and Public Safety Answering Point (PSAPs) with the Core network across all integrated networks (i.e., any MVNO, Core, roaming partners, and state-deployed RANs). Provide the details of the solution to grow, manage, maintain, and report on PSEN and PSAP connections, including ongoing network additions, upgrades, updates, configuration changes, rearrangements, assignments and removals. This should include an architecture, design, maintenance, and management plan that aligns with the IOC/FOC milestones and continues after FOC. Within the plan, include the following information:

• Integration and testing schedule

• Integration test plan

• Integration performance report

• Risk and jeopardy mitigation report

• Integration and testing completion report

• Roadmap

Page J-19 – 10

Describe how the status of actual and planned PSEN and PSAP integration will be reported to the state or territory.

5.4 Network Reliability

Describe the strategy for addressing network reliability and maximizing availability of all network elements.

5.5 Network Resiliency

Provide the network design including survivability assumptions to maintain an acceptable level of service in the face of natural disasters, faults and other challenges, which may include but are not limited to any natural or man-made events that adversely impact Public Safety Entities’ access to or use of the NSPBN pertaining to normal operation. Outline the process to maintain and improve network resiliency for the NPSBN.

5.6 Network Redundancy

Provide the design and redundancy detailed needed to achieve the service availability objectives. This may be accomplished through local and geo-redundancy for all NPSBN components, systems, and links or via other means. This should cover proposed methods for all layers of the network and any associated quality improvement metrics gained as a result of these solutions especially in highly vulnerable key network nodes. Include strategies that, at a minimum, address the following:

• Backup Power –Provide, on a per state basis, the percentage and location of sites to be configured with the backup power systems, the types of backup systems, and the average runtime between service and refueling. Include detail plans about portable generators.

• Resilient Interconnection –Provide, on a per state basis, the percentage of site infrastructures hardened against backhaul failure with multiple independent interconnections capable of individually handling the expected traffic from the wireless facilities.

5.7 Environmental Factors

Document and provide specific actions being taken in the design and implementation of the NPSBN to mitigate environmental factors that could have an adverse effect on the NPSBN performance.

Document and provide the solutions for different regions impacted based on specific environmental factors relevant for each of the 56 states and territories. Include a weatherization strategy of how cell sites located in areas prone to specific adverse weather conditions are addressed. This shall include but is not limited to flooding, storm surges, tornados, earthquakes, hurricanes, ice storms, and wild fires.

5.8 Security

Text for this section will be provided by FirstNet.

5.8.1 Security Architecture Plan

The Contractor shall provide a complete functional and physical depiction of the security layout of the NPSBN across and within each of the respective security subdomains including RAN, Core, User

Page J-19 – 11

Equipment (UE), Application, and backhaul. This architectural plan will include at a minimum specifications and methods for ensuring security for each of the respective security subdomains and the interfaces both internal and internal affecting each.

5.8.2 Security Integration and Test Plan

The Contractor shall deliver a written plan that covers, at a minimum, the methods and approach to onboarding updates, hardware, operating systems, LTE updates, and related systems and with associated testing to ensure optimal functionality within the approved security architecture. This document should also provide mitigation strategies for required updates that potentially introduce operational impacts.

5.8.3 Applications Security Plan

The Contractor shall deliver a formal plan detailing the means, methods, and strategy for securing the application ecosystem and the inherent functions of application creation, delivery, updating, and validation. At a minimum, this will also include validation of authorized access to the application ecosystem and protection of data in transit from/to applications to external databases and on the local device data storage.

5.8.4 Security Monitoring Plan

The Contractor shall provide a plan that details the methods and techniques to conduct security monitoring across the FirstNet environment. At a minimum, this plan will include technologies employed, reports provided, a logging approach and related forensic analysis of those logs, and incident response capability and timeliness, as well as a mitigation process and related escalation/de-escalation notification processes and criteria.

5.8.5 Security Configuration Management Plan

The Contractor shall conduct tracking, planning, development, and implementation of new Computer Network Defense/Cybersecurity capabilities into all FirstNet NPSBN systems. The contractor shall provide documented methods, techniques, processes in a written plan to ensure configurations of device level, network, applications, and related components are known and changes captured prior to implementation.

5.8.6 Technical Analysis and Security Review of Security Tools

The contractor shall provide technical and management support to FirstNet in planning, development and testing of security technologies; provide technical analysis in support of development and test activities for new systems and emerging technologies; facilitate development of future requirements and architectures that enable transition of new systems and technologies into the operational baseline.

The contractor shall provide the methods, processes, and procedures to document suitability, security validation and integration activities.

5.8.7 Physical Security Plan

The Contractor shall provide FirstNet with a documented plan covering the processes, procedures, and technologies to provide for the physical security and physical monitoring of sites of the FirstNet NPSBN.

The plan will include but is not limited to intrusion monitoring (facility and cabinets/racks), power and power levels, water and humidity monitoring, access controls and heating/cooling.

Page J-19 – 12

5.8.8 Cybersecurity Incident Response Plan

The Contractor shall provide FirstNet with a documented Cyber Incident Response Plan that includes but is not limited to computer security monitoring to rapidly detect incidents, vulnerability detection and analysis, log collection and analysis, tracking and reporting of incidents and restoration of IT operations after an incident occurs. The plan shall include specific technical processes, techniques, checklists, and forms to be used by the incident response teams. The Contractor shall document methods to report and escalate incidents to FirstNet in a timely fashion.

6 Network Operator/User Training Requirements

Provide a training plan describing the level of assistance provided to First Responders to utilize the full capabilities of the NPSBN and MVNO. This assistance may include training on equipment, features, and services available for normal and emergency operations.

7 State Decision Process/Requirements/Timeline

Text for this section will be provided by FirstNet.

7.1 Proceeding with FirstNet-Deployed RAN – Next Steps and Process to Submit Questions

Text for this section will be provided by FirstNet.

7.2 Consultation Roles and Responsibilities after the Plan is Accepted

Text for this section will be provided by FirstNet.

7.3 Decision to Proceed with State-Deployed RAN – Procedures

Text for this section will be provided by FirstNet.

7.3.1 Decision to Proceed with State-Deployed RAN Plan Requirements

Text for this section will be provided by FirstNet.

7.3.2 Decision to Proceed with State-Deployed RAN Plan Criteria

Text for this section will be provided by FirstNet.

7.3.3 Decision to Proceed with State-Deployed RAN Plan Submission Process

Text for this section will be provided by FirstNet.

7.4 Timeline

Page J-19 – 13

APPENDIX A FirstNet Nationwide Design

Text for this section will be provided by FirstNet.

A.1 End-to-End Network Architecture

Describe and document the NPSBN end-to-end architecture solution—RAN, EPC, infrastructure, services, application platforms, and OSS/BSS—that is dedicated for public safety users. The solution shall be capable of integrating with existing non-Band 14 RAN, where applicable as well as with state deployed RANs.

Provide evidence in achieving the quality metrics noting past performance or that of partners.

Include in the NPSBN end-to-end architecture:

• Architecture descriptions and diagrams including physical, logical and geographic architectures

• High Level Design criteria, objectives and components utilized

• Software releases and 3GPP standards implemented

• External interfaces to align with Section J, Attachment J-4, System and Standards Views

• Roadmap of network architecture evolution based on IOC/ FOC target milestones including components, functionalities and design criteria evolutions

• Design criteria and objectives utilized for each of the 56 states and territories, in separate documents, to maximize system availability, resilience, and reliability.

A.1.1 State RAN Architecture

The RAN strategy and solutions shall encompass the architecture, design, and deployment strategies that effectively use resources, skillsets, organizational structure, and tools. Demonstrate the following capabilities with respect to RAN solutions and potentially include a combination of maps and tables showing relevant statistics and brief descriptions of features and services.

Provide a reference list of air interface standards and/or non-standard interfaces to be implemented in the proposed network for communication between the eNodeB and User Equipment. These shall comport with those outlined in Section J, Attachment J-4, System and Standard Views. The description for the RAN architecture should include:

• Architecture descriptions and diagrams including physical, logical, and geographic architectures.

• High Level Design criteria, objectives and components utilized

• Software releases and 3GPP standards implemented

• External interfaces to align with Section J, Attachment J-4, System and Standards Views

• Roadmap of network architecture evolution based on IOC/ FOC target milestones including components, functionalities and design criteria evolutions

• Design criteria and objectives utilized for each of the 56 states and territories, in separate documents, to maximize system availability, resilience, and reliability.

Page J-19 – 14

A.1.2 Nationwide Core Architecture

Describe and document a Core network solution—EPC, services, application platforms, and OSS/BSS— that is dedicated for public safety users. The solution shall be capable of integrating with FirstNet NPSBN RANs (Band 14 and Offerors’ bands) as well as state-deployed RANs.

The description of the NPSBN Core network should include:

• Architecture descriptions and diagrams including physical, logical and geographic architectures

• High Level Design criteria, objectives and components utilized

• Software releases and 3GPP standards implemented

• External interfaces to align with Section J, Attachment J-4, System and Standards Views

• Roadmap of network architecture evolution based on IOC/ FOC target milestones including components, functionalities and design criteria evolutions

• Design criteria and objectives utilized for each of the 56 states and territories, in separate documents, to maximize system availability, resilience, and reliability.

A.1.3 Backhaul, Aggregation, Transport, and National Transmission Network Architecture

Describe and document a transmission network solution— backhaul, aggregation, transport and national transmission network. The descriptions of the NPSBN backhaul, aggregation, transport and national transmission network should include:

• Architecture descriptions and diagrams including physical, logical and geographic architectures

• High Level Design criteria, objectives and components utilized

• Software releases and 3GPP standards implemented

• External interfaces to align with Section J, Attachment J-4, System and Standards Views

• Roadmap of network architecture evolution based on IOC/ FOC target milestones including components, functionalities and design criteria evolutions

• Design criteria and objectives utilized for each of the 56 states and territories, in separate documents, to maximize system availability, resilience, and reliability.

• A roadmap according to IOC/ FOC target milestones for the transmission systems strategy

A.1.4 Operational Support System Architecture

Describe and document an OSS solution—EMS, NMS, workflow, change management, trouble ticketing, troubleshooting support and diagnostic platforms that are utilized for the NPSBN. Provide a description of the NPSBN OSSs and include:

• Architecture descriptions and diagrams including physical, logical and geographic architectures

• High Level Design criteria, objectives and components utilized

• Software releases and 3GPP standards implemented where applicable

• External interfaces to align with Section J, Attachment J-4, System and Standards Views

• Roadmap of network architecture evolution based on IOC/ FOC target milestones including components, functionalities and design criteria evolutions

• Design criteria and objectives utilized to maximize system availability, resilience, and reliability.

Page J-19 – 15

A.1.5 Business Support System Architecture

Describe and document a BSS solution—Customer Relationship Management (CRM), billing, accounting/finance, asset management, logistics management, customer trouble ticketing, customer trouble shooting support and diagnostic platforms that are utilized for the NPSBN. Provide a description of the NPSBN BSSs and include:

Architecture descriptions and diagrams including physical, logical and geographic architectures

High Level Design criteria, objectives and components utilized

Software releases

External interfaces to align with Section J, Attachment J-4, System and Standards Views

Roadmap of network architecture evolution based on IOC/ FOC target milestones including components, functionalities and design criteria evolutions

Design criteria and objectives utilized to maximize system availability, resilience, and reliability.

A.1.6 Applications Architecture

Provide the architecture for the NPSBN Applications, which includes the service delivery platform, application development platform, hosting and cloud services, application store, application life cycle management, application certification and security. The description of the applications architecture should include, but not be limited to:

Overall architecture with descriptions and diagrams

High Level Design criteria and objectives/capabilities

Application development environment

Application APIs and SDKs

External interfaces and specific dependencies to include but not limited to the following: cloud services, Core components, devices and database access

A.1.7 Interconnection Architecture

Provide the interconnection and interworking architecture supporting state-deployed RAN backhaul aggregation integration, PSEN and PSAP integration, PSTN integration, PLMN integration, and roaming to the Core systems across all integrated networks (MVNO, Core, Roaming partners, and state-deployed RANs) to form a seamless network implementation and operation. Describe the interconnect and interworking architecture nothing how it will be maintained and managed and how the state will be informed as to its status. Provide a roadmap according to IOC/ FOC target milestones for their interconnection and interworking strategy.

The description of the NPSBN interconnection architecture should include:

Architecture descriptions and diagrams including physical, logical and geographic architectures

High-level design criteria and objectives and components utilized

Software releases

External interfaces to align with Section J, Attachment J-4, System and Standards Views

Roadmap of network architecture evolution based on IOC/ FOC target milestones including components, functionalities and design criteria evolutions

Page J-19 – 16

Design criteria and objectives utilized to maximize system availability, resilience, and reliability

A.2 End-to-End Network Design (Logical and Physical)

Describe and document the NPSBN end-to-end detailed design solution—RAN, EPC, infrastructure, services, application platforms, and OSS/BSS.

The description of the NPSBN end-to-end design should include:

Detailed descriptions and diagrams including physical, logical and geographic designs for all components, links and systems

Detailed design criteria and objectives for each component utilized

Software releases implementation schedules and 3GPP standards implemented

External interface detailed designs and connections guidelines

Detailed Design criteria and objectives utilized for each of the 56 states and territories, in separate documents, to maximize system availability, resilience, and reliability.

Include the operational process, metrics, and thresholds associated with:

Failure restoration

Degradation restoration

All upgrade(s)/update(s) including 3GPP upgrade process to ensure timely deployment of public safety services that are being standardized in the future.

Deployment risk mitigation

Capacity and traffic growth performance

Capacity and traffic growth exhaust

Roaming performance between Band 14 and other networks

Network restoration for disaster recovery and reaction to major incident

A.2.1 Radio Access Network Design

Describe and document the NPSBN RAN detailed design solution. The description of the NPSBN RAN detailed design should include:

Detailed descriptions and diagrams including physical, logical and geographic designs for all components, links and systems

Detailed design criteria and objectives for each component utilized

Software releases implementation schedules and 3GPP standards implemented

External interface detailed designs and connections guidelines

Detailed Design criteria and objectives utilized for each of the 56 states and territories, in separate documents, to maximize system availability, resilience, and reliability.

Include the operational process, metrics, and thresholds associated with:

Failure restoration

Degradation restoration

All upgrade(s)/update(s) including 3GPP upgrade process to ensure timely deployment of public safety services that are being standardized in the future

Page J-19 – 17

Deployment risk mitigation

Capacity and traffic growth performance

Capacity and traffic growth exhaust

Roaming performance between Band 14 and other networks

Network restoration for disaster recovery and reaction to major incident

A.2.2 Core Design

Describe and document the NPSBN Core detailed design solution. The description of the NPSBN Core detailed design should include:

Detailed descriptions and diagrams including physical, logical and geographic designs for all components, links and systems

Detailed design criteria and objectives for each component utilized

Software releases implementation schedules and 3GPP standards implemented

External interface detailed designs and connections guidelines

Detailed design criteria and objectives to maximize system availability, resilience, and reliability.

Include the operational process, metrics, and thresholds associated with:

Failure restoration

Degradation restoration

All upgrade(s)/update(s) including 3GPP upgrade process to ensure timely deployment of public safety services that are being standardized in the future

Deployment risk mitigation

Capacity and traffic growth performance

Capacity and traffic growth exhaust

Roaming performance between Band 14 and other networks

Network restoration for disaster recovery and reaction to major incident

A.2.3 Backhaul and Transport Design

Provide the transmission systems detailed design plan supporting RAN backhaul, backhaul aggregation, a nationwide backbone transmission system and associated transmission security, routing methodologies and service prioritization including end-to-end Quality of Service and priority integrity across LTE and transport layers.

Descriptions of the Transmission systems should include a detailed design, maintenance and management plan for each year during IOC/FOC and after FOC including but not limited to the following:

Transmission systems traffic, capacity and growth plan

Detailed network designs

Description of reports that the state will receive which may include o Upgrades and update report o Configuration change report o Provisioning report (assignments, builds and removals) o Transmission network and link bandwidth utilization reports

Page J-19 – 18 o Transmission network and link SLA Report (availability, outage, etc.)

A.2.4 Operational Support System Design

Describe and document the NPSBN OSS detailed design solution. The description of the NPSBN OSS detailed design should include:

Detailed descriptions and diagrams including physical, logical and geographic designs for all components, links and systems

Detailed design criteria and objectives for each component utilized

Software releases implementation schedules

External interface detailed designs and connections guidelines

Detailed design criteria and objectives to maximize system availability, resilience, and reliability

Include the operational process, metrics, and thresholds associated with:

Failure restoration

Degradation restoration

All upgrade(s)/update(s)

Deployment risk mitigation

Capacity and traffic growth performance

Capacity and traffic growth exhaust

OSS restoration systems for disaster recovery and reaction to major incident

A.2.5 Business Support System Design

Describe and document the NPSBN BSS detailed design solution. The description of the NPSBN BSS detailed design should include:

Detailed descriptions and diagrams including physical, logical and geographic designs for all components, links and systems

Detailed design criteria and objectives for each component utilized

Software releases implementation schedules

External interface detailed designs and connections guidelines

Detailed design criteria and objectives utilized to maximize system availability, resilience, and reliability

Include the operational process, metrics, and thresholds associated with:

Failure restoration

Degradation restoration

All upgrade(s)/update(s)

Deployment risk mitigation

Capacity and traffic growth performance

Capacity and traffic growth exhaust

Network restoration for disaster recovery and reaction to major incident

Page J-19 – 19

A.2.6 Applications and Services Design

The Offeror shall provide a description of the architecture for the NPSBN applications ecosystem, which includes the service delivery platform, application…