The Florida 700 MHz Public Safety Interoperability Channel Plan. Division of Telecommunications

Transcription

1 The Florida 700 MHz Public Safety Interoperability Channel Plan Division of Telecommunications

2

3 DEPARTMENT OF MANAGEMENT SERVICES DIVISION OF TELECOMMUNICATIONS 4030 ESPLANADE WAY, SUITE TALLAHASSEE, FLORIDA MEMORANDUM: TO: FROM: FLORIDA 700 MHz PUBLIC SAFETY INTEROPERABILITY CHANNEL PLAN RECIPIENTS CHARLES GHINI, DIRECTOR DIVISION OF TELECOMMUNICATIONS DATE: NOVEMBER 23, 2010 SUBJECT: FLORIDA 700 MHz PUBLIC SAFETY INTEROPERABILITY CHANNEL PLAN The Florida 700 MHz Public Safety Interoperability Channel Plan has been created as a First Edition and is now available online at: _communication_plans This First Edition addresses the Interoperable Use portion of the 700 MHz public safety spectrum allocated by the Federal Communications Commission. If you have any comments or questions regarding this edition, please call Carlton Wells at (850) or via at carlton.wells@dms.myflorida.com. CG:cww:ldm 700I IO Plan Final v3 05.doc

4 Document History Version Date Modifications V1.0 3/24/09 Original Draft V1.01 3/26/09 Formatting and Appendix B Frequency Chart V1.1 4/14/09 Corrections, Authoritative References, Draft Policies V1.2 5/18/09 Plan Architecture Adjustments and Additions V1.21 5/21/09 DES/AES Encryption Standards Update V1.25 5/23/09 Draft Peer Review and Acronyms Section V2.0 5/06/10 Re-start on Plan Revisions- DivTel Governance Changes V2.1 5/10/10 Edits from action list of 5/7/10 V2.2 5/11/10 Edits from action list of 5/10/10 V2.3 5/12/10 Edits from action list of 5/11/10 V2.4 5/13/10 Edits from action list of 5/13/10 V2.5 5/13/10 Edits from action list of 5/13/10 V2.6 5/18/10 Edits from action list of 5/13/10 V2.7 5/20/10 Edits from action list of 5/18/10 V2.8 5/25/10 Edits from action list of 5/20/10 V2.9 5/27/10 Edits from action list of 5/25/10 V3.0 5/28/10 Final Draft Plan V3.01 6/1/10 Modified Appendix G V3.02 6/2/10 App. G & H references swapped and minor modifications by State of Florida V3.03 7/16/10 SOF final changes before vetting the Plan. V3.04 9/10/10 Incorporated feedback from first round of vetting. V3.05 Final First Edition. No feedback received from second round of vetting. 700 IO Plan Document 3.05 i

5 Contents 1.0 Introduction Purpose Background Governance Geographic Description Geographic Coverage Geographic Environment Demographic Data Public Safety Providers Use of the 700MHz Interoperability Channels within Florida Licensing When Licenses are Required Statewide License Custodian and License Approver Application Procedures Channel Definitions Channel Standards Calling Channel Sets Monitoring of Calling Channel Sets Tactical Channel Sets Deployable Systems Additional Spectrum Set Aside for Interoperability within Florida Operational Procedures Usage Limitations Plain English Usage IO Plan Document 3.05 ii

6 4.3 NIMS ICS Compliance Standard Nomenclature Subscriber Operational Procedures Calling Channel Set Usage Direct (Simplex) Mode Minimum Channel Quantity Infrastructure Operational Procedures Mode of Operation Trunking on the Interoperability Channel Sets Standard Operating Procedures on the Secondary Trunked Interoperability Channel Sets for Interoperability Situations Above Level Technical Parameters Frequency Utilization Fixed Stations Mobiles and Portables Vehicular Repeaters Common Channel Access Parameters Encryption Calling Channel Sets Tactical Channel Sets Data Only Use of the Interoperability Channels Wideband Data Standards Channel Implementation Procedures Fixed Station Control Single Supervisory Control for Repeaters IO Plan Document 3.05 iii

7 6.1.2 Local Control Procedure for Build-out Approval and Notification Build-out Approval Build-out Notification Procedure for Build-out Coordination Dispatch Control Priority Matrix Implementation Dispute Resolution Process Channel Control Dispute Resolution Process Low Speed Data Channels Agreement Formalization System Design/Efficiency Requirements Interference Protection-vs.-Interoperability Continuity Interoperability Channel Coverage Requirements Spectrum Efficiency Standards Orphaned Channels Coordination with Adjacent States Procedure for Build-out Approval and Notification Build-out Approval Build-out Notification Procedure for Build-out Coordination Dispatch Control Priority Matrix Implementation Dispute Resolution Process Channel Control Dispute Resolution Process Low Speed Data Channels Agreement Formalization IO Plan Document 3.05 iv

8 9.0 Certification FCC Plan Approval Appendix A Appendix B Appendix C Appendix D Appendix E Appendix F Appendix G Appendix H Appendix I Acronym List IO Plan Document 3.05 v

9 1.0 Introduction 1.1 Purpose This document, The Florida 700 MHz Public Safety Interoperability Channel Plan, serves to define the method of administration and oversight for the Interoperability Tactical Channels, National Interoperability Calling Channels and the Low Speed Data Interoperability channels designated for use by Public Safety entities in the 700 MHz Band within Florida. The Plan serves as a contributing component of the Florida Statewide Communications Interoperability Plan (SCIP) and to the overall 700 MHz planning effort within Florida (National Public Safety Planning Advisory Council (NPSPAC) Region 9). Planning documents for the remaining portions of the 700 MHz Public Safety Spectrum can be found as follows: General Use Frequencies Refer to Region 9 Committee 700 MHz Plan State License Frequencies Call Sign WPTZ787. A 700 MHz State-use Channel Plan is under development at the Division of Telecommunications. Broadband Data Frequencies Refer to Region 9 Committee 700 MHz Plan, Section Background 1. In the early 1990 s public safety officials testified before the United States Congress regarding the lack of spectrum for public safety agencies throughout the country. The determination was made that insufficient spectrum was available to meet current requirements or accommodate future technologies necessary for the advancement of public safety programs. As a result, the Federal Communications Commission (FCC) and National Telecommunications and Information Administration (NTIA) established the Public Safety Wireless Advisory Committee (PSWAC) on June 25, 1995 to provide advice on the specific wireless communications requirements of public safety agencies. The PSWAC, made up of a cross-section of public safety officials, was charged with studying the problem and making recommendations for remedies to Congress. The PSWAC report recommended that new spectrum be allocated to public safety to meet future needs. PSWAC further recommended that interoperability within and among public safety and public service providers be a basic, essential requirement. In 1997 Congress directed the FCC to allocate spectrum to public safety. This spectrum was to be allocated from the 60 MHz of spectrum located between television Channels 60 and 69 (746 MHz to 806 MHz) that would become available due to the transition of broadcast television from analog to digital TV. On December 31, 1997, the FCC allocated MHz paired with MHz to public safety use. On July 31, 2007, the FCC adopted a Second Report and Order revising the rules governing wireless licenses in the 700 MHz band and adopting a plan for the 700 MHz band to establish a nationwide, interoperable public safety broadband communications network for the benefit of state and local public safety users. This FCC action divided the overall spectrum into narrowband and wideband segments. The FCC designated the lower half of the 700 MHz public safety band for 700 IO Plan Document

10 broadband communications ( / MHz) and consolidating existing narrowband allocations in the upper half of the public safety 700 MHz band ( / MHz). This organization of the 700 MHz Public Safety narrowband spectrum is detailed in Appendix A and B. 1.3 Governance By FCC mandate as defined in Part 90, Section 525 (Appendix C), the State is responsible for the administration of the 700 MHz interoperability channels ( (a)). The FCC also requires that license applications must be approved by a state-level agency or organization responsible for administration of state emergency communications or the state may delegate this authority to another entity ( (b)). In accordance with Chapters 252, 282, 318, 395, and 401 Florida Statutes, the State of Florida through the Department of Management Services (DMS), Division of Telecommunications (DivTel), which was formerly known as the State Technology Office, will have oversight of the administration, technical standards and operational policies for the 700 MHz interoperability spectrum within Florida and will not delegate the authority per the letter of intent provided to the FCC on September 10, 2001 (Appendix D). The Department of Homeland Security (DHS) in the National Emergency Communications Plan (NECP), as part of the governance initiatives, calls for the establishment of State Interoperability Executive Committees (SIECs) (or their equivalents) in all 56 States and territories. (SIECs) should be established via legislation or executive order by an individual State s governor. 1 SIECs are recommended to administer SCIPs in each of the states. These plans include, but are not limited to, interoperability operations on the 700 MHz interoperability channels. The committees should include an equal number of representatives each providing regional representation from state, county (where applicable), and local governments, with additional representation from special districts, tribal entities and federal agencies, as appropriate. Such committees may represent all disciplines, in which case emergency medical, fire, law enforcement, forestry, general government, and transportation agencies from each level of government shall be represented equally. DivTel serves as co-chair of the Florida Executive Interoperability Technologies Committee (FEITC) with the Florida Division of Emergency Management (FDEM) which is the equivalent of an SIEC for the benefit of the citizens of Florida. DivTel will coordinate with and seek cooperation from the Florida Domestic Security Oversight Council (DSOC), the Region 9 Committee, and associated adjacent States in the development, implementation and continued maintenance of this plan for the benefit of public safety within Florida. DivTel is used throughout this plan with the knowledge that a parallel governance initiative that may evolve administration of this plan into the oversight of a Statewide Interoperability Governing Board (SIGB) or equivalent. 1 National Emergency Communications Plan, page 13, Initiative 1.1, Milestone 5, Department of Homeland Security, August 7, IO Plan Document

11 Should any part of this Plan be found to be in conflict with FCC rules and regulations now or in the future, the FCC rules and regulations shall supersede. However, all provisions of this document, except those affected by the conflict, shall remain in effect. 2.0 Geographic Description 2.1 Geographic Coverage This plan shall encompass the entire State of Florida to include its territorial waters. A listing of Florida counties is provided in Appendix E. 2.2 Geographic Environment The Florida terrain is flat and sub-tropical in the south to pine woods and rolling hills in the north. Elevations range from sea level to less than 300 feet naturally. 80% of the population is concentrated in the Miami-West Palm Beach corridor, and the Tampa-Orlando-Jacksonville corridor. 2.3 Demographic Data Summary Demographic State Data (and Source) Population (2008 Census Bureau estimate): 18,328,340 Population (2000 Census): 15,982,378 Foreign-Born Population (2003 CB estimate): 2,995,400 Foreign-Born Population (2000 Census): 2,670,828 Share Foreign-Born (2003): 17.6% Share Foreign-Born (2000): 16.7% Immigrant Stock* (2000 CB estimate): 4,637,000 Share Immigrant Stock (2000 estimate): 29.0% Naturalized U.S. Citizens (2000 Census): 1,207,502 Share Naturalized (2000 estimate): 45.2% Legal Immigrant Admission (INS ): 754,692 Refugee Admission (2001 HHS): 16,775 Illegal Alien Population (CIS 2005): 780,000 Projected Population** (2001 FAIR): 27,100,400 *defined by the U.S. Census Bureau as immigrants and first generation children of immigrants. **If population growth rates of continue 2.4 Public Safety Providers All forms of public safety agencies and services are located in Florida. The majority of these providers are concentrated in the population centers noted above. The diversity of the public safety agencies is reflected in the DSOC membership. The most immediate impact of this plan will be on the population centers that have exhausted all other available spectrum resources and generate a majority of the requests for additional voice and interoperability spectrum. 700 IO Plan Document

12 3.0 Use of the 700MHz Interoperability Channels within Florida 3.1 Licensing When Licenses are Required Per FCC CFR Title 47, Part (a) Base and control stations must be licensed individually. A public safety entity meeting the requirements of Sec may operate mobile or portable units on the Interoperability channels in the MHz and MHz frequency bands without a specific authorization from the Commission provided it holds a part 90 license. All persons operating mobile or portable units under this authority are responsible for compliance with part 90 of these rules and other applicable federal laws. Anyone not licensed under Part 90 for public safety frequencies will require a sharing agreement with a Part 90 public safety licensee. A sample sharing agreement is provided in Appendix F. Per FCC CFR Title 47, Part (b) License applications for Interoperability channels in the MHz and MHz frequency bands must be approved by a state-level agency or organization responsible for administering state emergency communications. States may hold the licenses for Interoperability channels or approve other qualified entities to hold such licenses. Per Section 1.3 DivTel is authorized to administer these channels and approve other qualified entities to hold such licenses Statewide License Custodian and License Approver DivTel does not plan to hold a custodial statewide license for all the interoperability channels, but will consider and approve the applications for licenses to other qualified entities within Florida Application Procedures Applications for fixed stations, mobile-relay stations, or mobile stations, must be submitted to DivTel and must include the required eligibility showings and written mutual agreement, as to the technical and operational standards defined herein. Following a favorable determination by DivTel, a letter of concurrence (signed by the Director of DivTel or a designee) will be prepared and attached as an exhibit to the application. The entire application will then be returned for submission to the appropriate FCC-certified frequency coordinating organization for further processing, as specified by FCC rules. 3.2 Channel Definitions The 700 MHz narrowband (6.25 khz) voice and data interoperability channels are defined on a nationwide basis by the 700 MHz National Coordination Committee (NCC). Appendix B contains the complete listing of these channels and their designations. Standardization at the national level ensures that each channel will have the same usage within each region and across regional borders to maximize national interoperability. These channels have been sub-divided into 2 As an exception, DivTel may apply for and hold an FCC license for FBT and FB2T station class for mobile repeater systems (MRS) on the TAC channels identified for secondary trunked operation per section 3.7 on behalf of MRS equipment statewide. Agencies would have the option to request a Sharing Agreement from DivTel or choose to seek their own license. 700 IO Plan Document

13 The Florida 700 MHz Public Safety Interoperability Channel Plan different service categories. There are two Calling Channel Sets and 30 Tactical Channel Sets. The tactical channel sets are further subdivided into the following categories: 12 for Public Safety General Services 4 for Emergency Medical Services 4 for Fire Services 4 for Law Enforcement Services 2 for Mobile Repeater operation 2 for Data 2 for Other Public Services Channel sets are comprised of two 6.25 khz channels each. For example, if you consider the first calling channel set 7CALL50 it is comprised of base channels 39 & 40 and mobile channels 999 & Consider the detail in Figure 1 taken from the spectrum chart in Appendix A. Each channel has a bandwidth of 6.25 khz providing for a channel set bandwidth of 12.5 khz. Therefore, the channel set can be defined as having a start frequency and a center frequency, where the center frequency is 6.25 khz higher than the start frequency, as shown in Table 1. Base Channel Detail Mobile Channel Detail Figure 1 Narrowband Channel Detail for Calling Channel 7CALL IO Plan Document

14 Base Channel Sets Mobile Channel Sets I/O Channel Direct (Simplex /Mobile) Channel No Frequency (MHz) Channel No Frequency (MHz) Lower Upper Lower Center Lower Upper Lower Center 7CALL50 7CALL50D Table 1 Narrowband Channel Set Parameters for Calling Channel 7CALL50 The interoperability channel set parameters for all 32 channel sets are shown in Table B.1 of Appendix B. 3.3 Channel Standards The NCC has adopted the American National Standards Institute (ANSI)/ Telecommunications Industry Association (TIA), ANSI/TIA 102 Standard (i.e., Project 25 digital protocols) as the Digital Interoperability Standard for the conventional-only mode of operation on the narrowband voice and data interoperability channels. Associated Public Communications Officers (APCO)/National Public Safety Telecommunications Council (NPSTC) APCO/NPSTC ANS is a channel naming nomenclature for the public safety interoperability channels. DivTel supports this standard and has incorporated it in this Plan for compliance. 3.4 Calling Channel Sets Because the 700 MHz band will be initially occupied by broadcast television stations and then vacated at a later time, two of the interoperability channels sets are reserved as "Calling Channel Sets". Geographies where interoperability systems are deployed will define when and where the two calling channel sets are to be utilized until broadcast stations have fully vacated the spectrum to ensure availability of at least one calling channel set. 3.5 Monitoring of Calling Channel Sets The calling channel sets, 7CALL50 and 7CALL70 must be monitored, as appropriate, by dispatch agencies (or Network Control Centers) that operate or control the interoperability infrastructure in the associated channel group in order to derive the desired benefit. In addition to the usual calling channel operations (as defined in section 4 below), the calling channel sets may be used to notify users when a priority is declared on one or more of the tactical interoperability channel sets. 3 APCO/NPSTC ANS was approved by ANSI on June 6, 2010, and can be found at IO Plan Document

15 3.6 Tactical Channel Sets Users requesting Tactical channels will contact a local or regional dispatch center on one of the "Calling Channel Sets" and be assigned an available tactical channel. Deployable narrowband operations (voice, data, trunking) shall be afforded access to the same pool of channels used for similar fixed infrastructure operations within the licensee s area of operation. In the event of conflict between multiple activities, prioritized use shall also occur as similarly defined in section Deployable Systems Deployable systems are prepackaged systems that can be deployed by ground or air to an incident to provide additional coverage and capacity on interoperability channel sets. The use of deployable systems minimizes the expense of installing extensive fixed infrastructure and recognizes the difficulty of providing complete coverage of portions of the geography due to environmental constraints. The NCC mandates consideration for the need for both "deployable trunked" and "deployable conventional" systems. This Plan supports use of both conventional and trunked deployable systems. Agencies with conventional deployable 700 MHz systems must be capable of being tuned to any of the interoperability channel sets. Deployable systems shall use base station radios capable of being programmed for conventional, digital operation, regardless of secondary trunked operation. Deployable systems shall be capable of reprogramming at least one base station radio for conventional, digital operation on 7CALL50 in the event a calling channel is not available for use in the area of incident. Those agencies that are part of a multi-agency trunking system and commonly provide mutual aid to each other are encouraged to have conventional and trunked deployable systems that operate on the interoperability channel sets designated by the Plan for this use. If deployed in your licensed operational area, use of deployable resources should be covered under an FCC license or sharing agreement the agency with an FCC license for that area or a special temporary authority from the FCC should be obtained. If deployed outside your licensed operational area, a sharing agreement from the agency with an FCC license for that area or a special temporary authority from the FCC should be obtained. The sharing agreements should be pre-planned and a formal written agreement for commonly supported areas, but may also be verbal agreements if no preplanning has occurred for a region. The State of Florida will offer each public safety agency operating within Florida, the opportunity to obtain a sharing agreement under its FCC callsign. General Public Safety Services Channel Sets labeled 7TAC51 through 7TAC54 or 7TAC71 through 7TAC74, or both, shall be made available statewide for "deployable" equipment used during disasters and other emergency events that place a heavy, unplanned burden upon in-place radio systems. Channel sets labeled 7TAC71 through 7TAC74 in deployable equipment shall only be used where fixed systems do not provide the required coverage and priority access conventional or trunked. Hence, channel sets 7TAC51 through 7TAC54 will be held in reserve for deployable equipment. Whereas, channel sets 7TAC71 through 7TAC74 will be held in reserve for deployable and fixed equipment. 700 IO Plan Document

16 It is expected that the tactical channel sets set aside for secondary trunked operation will be heavily used by deployable systems. Therefore, the tactical channel sets 7TAC51 through 7TAC54 cannot be assigned to augment General Use or State Use trunked systems. Operational procedures for use of these channel sets are detailed in Section 4.0 below. 3.8 Additional Spectrum Set Aside for Interoperability within Florida DivTel working with the approval of the Region 9 Committee shall have the ability to assign additional spectrum out of the General Use spectrum for interoperability should the need arise. After seeking concurrence from adjoining regions, this Plan could designate additional channels to be used out of the General Use spectrum and would update Computer Assisted Pre-coordination Resource and Database (CAPRAD) to reflect any such designations. If designated, the spectrum would only be designated for interoperability use within Florida and would not emulate the nationwide interoperability of the 32 channel sets defined in the NCC report. DivTel is in concurrence with the Region 9 Committee and sees no need for additional interoperability channels at this time. 4.0 Operational Procedures 4.1 Usage Limitations Usage of these channel sets are limited to situations in which radio communications between otherwise separate entities is essential for safeguarding life, health, or property within the State of Florida. Regardless of the ownership or licensee responsibility of the equipment comprising a station on these channel sets, use of these channel sets will be available on a non-exclusive basis to any eligible entity. No owner or licensee has claim to exclusive use of a fixed station on these channel sets. It is the policy of DivTel to continue to use and specify the standards and criteria listed above for the design and implementation of public safety interoperability channel sets. 4.2 Plain English Usage Plain ENGLISH will be used at all times on all interoperability channel sets. The use of unfamiliar terms or codes is not permitted. 700 IO Plan Document

17 4.3 NIMS ICS Compliance The Incident Command System (ICS) was used as a guideline in developing this interoperability plan and DivTel expects usage of the 700 MHz spectrum within Florida will be in compliance with National Incident Management System (NIMS) ICS Standard Nomenclature Standard nomenclature will be used so that all 700 MHz public safety subscriber equipment using an alphanumeric display only, are permitted to show the recommended label when the radio is programmed to operate on the associated 700 MHz channel set. The standard nomenclature is taken from the NPSTC Channel Naming Report. 5 This report was adopted at the SAFECOM Executive Committee Meeting that was held on June 14, On June 9, 2010, ANSI approved APCO/NPSTC ANS as the channel naming standard. 6 Recommended labels are found in Table B.2 in Appendix B. The Table shows the recommended label for equipment operating in the mobile relay (repeater) mode and direct (simplex) mode. Note that with the direct mode channel sets the letter D is appended to the end of the corresponding relay mode label. 4.5 Subscriber Operational Procedures Calling Channel Set Usage Direct mode is permitted in the absence of repeat operation or upon prior dispatch center coordination. If the local calling channel set is not known, 7CALL50 shall be attempted first, then 7CALL70. Attempts shall be made on the repeater mode first then on the direct (simplex) mode Direct (Simplex) Mode In direct (simplex) mode, transmitting and receiving on the output (transmit) side of the repeater pair for scene communications between subscriber units does not congest the repeater station with unnecessary traffic. However, should someone need the repeater to communicate with the party who is in direct mode, the party would hear the repeated message, switch back to the repeater channel set, and join the communications. Therefore, operating in direct (simplex) mode shall only be permitted on the repeater output side of the voice interoperability channel sets Minimum Channel Quantity Subscriber units which routinely roam through more than one jurisdiction will require more than the minimum channel set quantity and those with potential nationwide mobility should consider 4 For information on NIMS ICS refer to the Federal Emergency Management Agency (FEMA) Emergency Management Institutes ICS Resource Center at 5 National Public Safety Telecommunications Council s Channel Naming Report, NPSTC, June 12, APCO/NPSTC ANS can be found at IO Plan Document

18 maximizing the number of interoperability channel sets to increase interoperability when roaming (i.e., all 30 voice channel sets). The calling channel sets ( 7CALL50 and 7CALL70 ) shall be implemented in all voice subscriber units in repeat-mode and direct (simplex) mode. This plan calls for a minimum of eight interoperability channel sets in each subscriber unit. Therefore, in addition to the two calling channel sets a minimum of six sets of tactical channel sets shall be implemented in every voice subscriber unit. Including direct (simplex) mode on these channel sets, 16 sets shall be programmed in each radio for interoperability purposes. Specific channel sets are shown below: 7CALL50 and 7CALL70 7TAC55 and 7TAC75 7TAC56 and 7TAC76 7GTAC57 and 7GTAC Infrastructure Operational Procedures Mode of Operation The supervisory control point must normally maintain the associated fixed (mobile-relay) station in repeat-disabled mode. The supervisory control point will affect the repeat-enable mode only upon the specific request of a mobile (vehicular or hand-held) or radio frequency control station user. Upon completion of mobile-relay communications, the fixed (mobile-relay) station must be returned to the repeat-disabled mode. Supervisory control points must be staffed 24 hours per day, year-round, and must have means for immediate contact with law enforcement, rescue, fire fighting, and/or emergency medical services agencies in the coverage area of the station controlled Trunking on the Interoperability Channel Sets Trunking the Interoperability channel sets on a secondary basis shall be limited to operation on eight specific 12.5 khz channel sets, divided into two subsets of four 12.5 khz channel sets. One subset is defined by 7TAC51 through 7TAC54 and the other by 7TAC71 through 7TAC74. While this section affords permanent fixed location to be licensed on four channel sets 7TAC71 through 7TAC74, all eight channels have been identified for statewide operation in mobile repeater systems per section 3.7 (Deployable Systems). In addition to the paragraphs that follow, a showing of absolute need and justification for fixed stations on 7TAC71 through 7TAC74 will be required demonstrating why State Use and General Use channels cannot be used. Furthermore, priority for deployable systems will prevail over fixed systems in conjunction with when the fixed system cannot serve the need for interoperable communications of the event. Any licensee implementing base station operation in a trunking mode on these interoperability channel sets shall provide and maintain on a continuous (24 hr x seven day per week) basis at its primary dispatch facility the capability to easily and immediately remove one or more of these interoperability channel sets (up to the maximum number of such trunking channel sets 700 IO Plan Document

19 implemented) from trunking operation when a conventional access priority that is equal to or higher than their current priority is implemented (see Section 4.6.3). Use of the interoperability channel sets for day-to-day operations is not allowed. FCC Part (b)(1)(iii) limits the number of interoperability channel sets that may be integrated into any single trunked system. For systems having 10 or fewer "general use" voice paths allocated, one (1) trunked interoperability channel set is permitted. For systems having more than 10 "general use" voice paths allocated, two (2) trunked interoperability channel sets are permitted. This plan may consider allotting additional interoperability channel set(s) for trunked systems having more than 20 "general use" voice paths allocated upon a showing of need and upon a determination that assignment of the interoperability channel set(s) will not adversely impact availability of those channels to other trunked and/or conventional radio systems in the area (e.g., a single consolidated trunked system servicing all public safety agencies in an area might satisfy this criterion). The maximum number of interoperability channel sets for trunked systems permitted for use by an individual licensee is four. Per FCC (b)(1)(iii), channel sets immediately adjacent to the 7TAC channel sets where secondary trunking is permitted [(21, 22), (101, 102), etc.] are available for secondary trunking, but only in conjunction with the adjacent Interoperability 12.5 khz channel pair in a trunked system. As they are limited to combination with the existing interoperability channel sets they will be included in this plan as part of the interoperability spectrum and be administered by DivTel. Should 25 khz trunking on interoperability channel sets be approved and licensed, these channel sets become part of those trunking channel sets, but still on a secondary basis. The aforementioned priority shall apply. The additional channel sets are, in effect, guard band channels between Interoperable Use channels and General Use channels. Accordingly, the interference criteria described in Appendix G will be applied, with preference toward safeguarding the 12.5 khz allotments and primary system operations Standard Operating Procedures on the Secondary Trunked Interoperability Channel Sets for Interoperability Situations Above Level 4 The safety and security of life and property determines appropriate interoperable priorities of access and/or reverting from secondary trunked to conventional operation. In the event secondary trunked access conflicts with conventional access for the same priority, conventional access shall take precedence. Access priority for mission critical communications is recommended as follows: 1. Disaster and extreme emergency operations for mutual aid and interagency communications; 2. Emergency or urgent operation involving imminent danger to life or property; 3. Special event control, generally of a preplanned nature (including Task Force operations); 4. Single agency secondary communications. [This is the default priority when no higher priority has been declared.] It is premature to establish a common trunked system key and other system parameters (including interoperable talk groups) for secondary trunked operation of these eight tactical channels at this time. Nationally, there is effort to do so. Accordingly, for those systems employing interoperability channel sets in the trunked mode, DivTel may establish Florida-specific 700 IO Plan Document

20 interoperability talk groups and priority levels for those talk groups so that it is easy for dispatch to determine whether the trunked interoperability conversation in progress has priority over the requested conventional interoperability use. DivTel may also determine whether a wide-area interoperability conversation has priority over a local interoperability conversation. The aforementioned will likely occur after it has been established nationally. Secondary trunking on interoperability channels sets will be permitted in fixed systems and subscriber units capable of altered trunked channel assignments without physically touching the equipment 7 when each respective interoperability channel is removed from secondary trunked operation in the fixed or deployable system. This promotes more immediate relinquishment from secondary trunked operation during times demanding immediate need of conventional interoperability channels. Priority use will be announced on the applicable tactical channel or secondary trunked talk group by the dispatcher, network control center or incident commander. 5.0 Technical Parameters 5.1 Frequency Utilization Fixed Stations In accordance with the band plan (Part ), fixed station transmitters must operate on the designated base frequencies ( MHz) of the implemented channel set and fixed station receivers must operate on the designated mobile frequencies ( MHz) of the implemented channel set for mobile relay purposes. Voice interoperability channels incorporated in fixed infrastructure equipment shall adhere to the minimum channel sets first (7CALL50 and/or 7CALL70, and one or more of the tactical channel set(s) specified in section An exception to implementing 7CALL50 and 7CALL70 will be considered where the applicant can demonstrate equivalent coverage with 8CALL90 for the same coverage area as the 700 MHz tactical channel sets implemented or to be implemented by the applicant, and 8CALL90 is or will be controlled by the applicant or designated Network Control Center per sections and 6.4. After the minimum channel sets have been fully implemented, other voice interoperability channels will be permitted for area-specific needs. This promotes interoperability on a statewide basis and limits the minimum channel sets in vehicular mobile units and hand-held portables on a statewide basis. Vehicular mobile units and hand-held portables associated with area-specific needs become likely the only ones exceeding the minimum channel requirement. 7 Other than turning off a trunked radio base station and turning on a conventional radio base station, or switching the subscriber unit to the conventional interoperability channel. 700 IO Plan Document

21 5.1.2 Mobiles and Portables Vehicular mobile units and hand-held portable units are to be configured for repeater operation on channel sets ( MHz transmit, MHz receive) and for direct talk-around operation on channel sets ( MHz transmit and receive) Vehicular Repeaters Vehicular repeaters (MO3 station class) and associated portable radios (MO station class) are to be configured on channel sets 7MOB59 and 7MOB79 as follows: 7MOB59 7MOB79 MO3 TX MHz MHz MO3 RX MHz MHz MO TX MHz MHz MO RX MHz MHz MO Direct MHz MHz These systems must maintain compliance with applicable FCC rules and regulations (47 CFR, Part 90), including but not limited to: Digital modulation (analog modulation permitted in a secondary mode in addition to the primary digital mode) per (a). Transmitter minimum data (non-voice) rate of 4.8 kbps per 6.25 khz of bandwidth per (b). Frequency stability per (c). Mobile radio transmitters must not exceed 30 watts per (b). This also associates with the VRS transmitter. Portable radio transmitters must not exceed three watts per (c). Mobile and portable radio transmitters must comply with emission limitations per TV/DTV interference protection criteria per , as applicable. Per , mobile and portable radios must be capable of operating on all narrowband Interoperability channels, except as provided in (a)(1), (2), and (3). Project 25 FDMA common air interface per (a)(1). Per , encryption is permitted, but "... must have a readily accessible switch or other readily accessible control that permits the radio user to disable encryption. 5.2 Common Channel Access Parameters Common channel access parameters will provide uniform interoperability communications regardless of jurisdiction, system, manufacturer, etc. This national requirement shall apply to base stations and subscriber units 8 for both fixed and temporary operations. Tactical, voice, or other mutual aid conventional interoperability use shall also utilize these common channel access 8 The NCC recommended that States who choose to administer the 700 MHz interoperability channels should use the recommendations provided in the 700 MHz Regional Planning Guidebook produced by NPSTC. A copy of the 700 MHz Regional Planning Guidebook is available at the NPSTC website, IO Plan Document

22 parameters. The secondary trunked interoperability channel sets are excluded from using the following parameters when in the trunked mode. Common channel access parameters for all voice interoperability shall utilize the default values provided in every radio regardless of manufacturer. 9 Any common channel access parameters not provided shall be programmed accordingly. These parameters include the following: P25 Network Access Code - $293 (default value) P25 Manufacturers ID - $00 (default value) P25 Designation ID - $FFFFFF (designates everyone) P25 Talkgroup ID - $0001 (default value) P25 Message Indicator $ (unencrypted) P25 Key ID - $0000 (default value) P25 Algorithm ID - $80 (unencrypted) Any deviation from P25 Network Access Code - $293 (default value) will not be permitted unless the applicant can demonstrate a need and obtain FCC approval. The intent of P25 Network Access Code - $293 (default value) shall be preserved on ALL conventional voice Interoperability channels transmit and receive. 5.3 Encryption Calling Channel Sets Per FCC Part (a)(1)(ii), use of encryption is prohibited on 7CALL50 and 7CALL Tactical Channel Sets Per FCC Part (a), encryption is permitted on all interoperability channels, except the two nationwide interoperability calling channel sets. Radios employing encryption must have a readily accessible switch or other readily accessible control that permits the radio user to disable encryption. Per FCC Part (b), if encryption is employed then the following encryption protocol must be used: Project 25 Data Encryption Standard (DES) Encryption Protocol, approved January 23, 2001, Telecommunications Industry Association, ANSI/TIA/EIA-102.AAAA-A Any equipment utilizing Advanced Encryption Standard (AES) encryption shall also implement DES encryption for backward compatibility with DES equipment. This Plan recommends the additional implementation of Project 25 AES Block Encryption Protocol, November 03, 2008 Telecommunications Industry Association, TIA/EIA-102.AAAD-A. Also per the Project 25 Statement of Requirements (dated March 3, 2010) for AES and DES: 9 Per the ANSI/TIA/EIA-102,BAAC-B August 18,2008, TIA/EIA 102.AAAD-A Block Encryption Protocol, Draft, November 3, IO Plan Document

23 AES For interoperability purposes, all Project 25 equipment implementing Type 3 encryption shall utilize the Advanced Encryption Standard (AES) algorithm. Key length for the AES shall be 256 bits DES For backwards interoperability purposes, the Data Encryption Standard (DES) algorithm may be optionally available in Project 25 equipment implementing Type 3 encryption. (NOTE: The DES algorithm has reached the end of its useful cryptographic life. The use of DES in new systems is strongly discouraged.) 5.4 Data Only Use of the Interoperability Channels Per Part (b)(1)(i), channel sets 7DATA69 and 7DATA89 are reserved nationwide for the express purpose of data transmission only. 5.5 Wideband Data Standards Within the 700 MHz band, spectrum has been designated for high capacity, wide bandwidth (50 to 150 khz) channel usage; this spectrum is outside the scope of this Plan at this time due to the ongoing nationwide effort. 6.0 Channel Implementation Procedures 6.1 Fixed Station Control Single Supervisory Control for Repeaters For each fixed station established, one supervisory control point must be designated by DivTel. A control point may be designated as supervisory for multiple fixed stations. Each supervisory control point, in addition to having the control functions of associated non-supervisory control points, must have an override function, enabling supervisory control of the repeat enable/disable function of supervised fixed stations.in the event of a power interrupt, the fixed (mobile-relay) station shall default to repeat-disable mode. In the event of a power outage, the repeater (fixed, mobile-relay) should return to the curent state of the repeater immediately prior to the outage (repeat enabled/disabled) if the repeater is capable of that mode of operation. If it is not capable of returning to current state, the repeater should return to service in repeat disabled mode. Radio frequency control stations transmitting on the designated mobile frequencies ( MHz) must not be authorized for supervisory control points. Radio frequency control stations for non-supervisory control points will be granted upon an exhibition of need. Any supervisory or non-supervisory control points may alternatively operate via either local or remote (leased) wire-line links, or on radio frequencies that may be authorized for such use Local Control Interoperability is most effective when implemented at the incident level. The intent of this Plan is to ensure each interoperability fixed station shall be directly controlled by a local Network Control 700 IO Plan Document

24 Center (NCC) under the jurisdiction of the primary Public Safety agency of that county or area. The primary Public Safety agency in each county or area shall be the County Sheriff's Department or Public Safety Department, unless another agency has been designated as a Network Control Center by DivTel. The responsibilities of these centers include ensuring responses to calls for assistance from any vehicle or dispatch point within their coverage area. Network Control Centers will coordinate assignments for subsequent use of the Tactical Channels for ongoing emergency operations, consistent with the geographic vicinity of the incident. A Network Control Center may request unknown field units to identify themselves and their authorization to use the mutual aid tactical channels. If there is no response, the NCC should call adjoining NCCs to identify the use of the mutual aid channel(s) where communication may be bleeding over. Officer safety may be compromised if the channel(s) are inadvertently disabled or otherwise altered. If unauthorized traffic is occurring, the primary or secondary NCC can disable the repeater to halt its use. The NCC should take follow-up action to ensure future unauthorized use in mitigated. Each Network Control Center must maintain a local map showing locations and contact information for adjoining NCCs and State Dispatch Centers, as well as showing the coverage areas and configurations of mutual aid fixed stations within the area. 6.2 Procedure for Build-out Approval and Notification Build-out Approval Most eligible public safety organizations are either of State and Local government, or else are subject to governmental regulation. The nature of governmental planning and budgeting processes, combined with difficult revenue constraints, prohibits most agencies from implementing newer technology systems in the normal time required by FCC Rules (8 months for construction of conventional stations, 12 months for trunked stations). In most cases, public safety systems will require multi-year phased-implementation schedules requiring three to five times as long to construct as private or commercial systems. Regional, wide-area, and statewide systems will require even longer periods to construct. In view of these known situations, this Plan establishes an extended implementation schedule in accordance with FCC Rules which is available to all eligible applicants, if requested by stating SLOW GROWTH on the license application. A SLOW GROWTH schedule will allow up to five years for completion of station construction. Applicants who request SLOW GROWTH are not required to submit the specific items of SLOW GROWTH justification normally required by FCC Rules. Build-out approval is provided by virtue of DivTel approval of the license application and FCC issuance of a license, or by virtue of DivTel recognizing a sharing agreement under another licensee s area of operation Build-out Notification The applicant shall notify DivTel upon successful licensing and implementation of 700 MHz interoperable channels. This will allow tracking the licensed and operational readiness status 700 IO Plan Document

25 of 700 MHz interoperable radio channel for interoperable use. DivTel will maintain a database similar to the Region 9 Committee database of 800 MHz mutual aid channels Procedure for Build-out Coordination Overlapping allotments, licensing, and implementation of channel sets may likely occur between local, regional and statewide systems. Overlap will be minimal between Local channel sets, increasing in potential for regional and statewide channel sets. Therefore, it will be necessary for agencies to understand and accept the need to coordinate implementation of their channel sets accordingly to prevent what will be referred to as co-channel chaos in lieu of co-channel interference. 11 Co-channel chaos will be further mitigated by the implementation of a dispatch priority matrix per section 6.4, establishing and recognizing primary and back-up NCCs. Allotment of channel sets for build-out will be established as follows: Statewide overlapping allotments will be continuous throughout the state for its channel sets. Regional overlapping allotments will be continuous throughout each regional area for its channel sets, but minimized between regions. Local overlapping allotments will be continuous throughout each local area for its channel sets, but minimized when implemented on a countywide basis by one agency. The limited number of channel sets and need for statewide, regional, and local allotments will determine the extent of overlap between systems. 6.4 Dispatch Control Priority Matrix Use during a real time event (emergency or planned) can be coordinated with the Incident Commander, Communications Unit Leader, State Working Group Interoperable Communications Committee (SWG-ICC), or FDEM as appropriate. During times of a State-declared emergency, communications protocol and procedures for use of an interoperability channel must be coordinated in conjunction with the State Emergency Operations Center Emergency Support Function 2 (SEOC-ESF2). Regardless of ownership or licensee responsibility of the equipment comprising a station on an interoperability channel set, any eligible entity may apply for and be granted authorization to operate a parallel control point for purposes of remotely controlling any existing fixed station. 10 Until the 700 MHz tab is developed in CAPRAD for the Interoperable Use channels, DivTel will be the host agency for the database. 11 Interoperable communications inherently requires channel sets be common among agencies, and in the systems implemented. Hence, the lack of coordination for use of a common resource (interoperable channel sets) can create chaos between agencies and users of the interoperable channel sets. Accordingly, there cannot be interference inasmuch as chaos between systems. 700 IO Plan Document

26 This applies where a showing of need has been demonstrated to DivTel. No owner or licensee of a fixed station shall claim exclusive rights to the control of that station. To the extent practicable, primary and back-up NCCs shall be established. A primary NCC is normally a county Sheriff s Office dispatch center acting as the answering point for a local mutual aid coverage area or cluster. A primary NCC is responsible for answering the mutual aid calling channel 24 hours a day, seven days a week, and assigning the appropriate mutual aid tactical channel for mobile units, as well as enabling the repeat-enable function of fixed stations if needed. A back-up 12 NCC can be another Local agency or a State of Florida Regional Communications Center (RCC). Each RCC is responsible for a multi-county area that comprises its dispatch jurisdiction, which may encompass multiple primary NCCs Control point operation of any fixed station must be consistent with the operational procedures found in Section 4. Should a local radio repeater site be established within the coverage of a proposed wide-area system, the local agency shall accept and cooperate with the wide-area coverage and the local system enhances the wide-area channel sets. Conversely, should a wide area radio system intersect the coverage of a local radio system, the wide area system agency shall accept and cooperate with the local system and enhance the local area channel sets. 6.5 Implementation Dispute Resolution Process If an agency disputes the implementation of this plan after the FCC approves it, then the agency must notify DivTel in writing of the nature of the dispute. DivTel will attempt to resolve the dispute. If this cannot be accomplished, then the dispute will be brought before the SWG-ICC to decide the issue. When a dispute involves an agency that employs any member of the SWG-ICC that person may participate in the resolution of that dispute but not act as the mediator and may not vote on the outcome of the resolution. If no common ground can be found in settling the dispute then all pertinent information will be forwarded to the National Regional Planning Council (NRPC). 13 As a last resort, the dispute will be forward to the Federal Communications Commission for final resolution. 6.6 Channel Control Dispute Resolution Process Disputes will be handled in the same manner as Section Low Speed Data Channels The channel sets designated as 7DATA69 & 7DATA89 are limited to low speed interoperability data applications. While this spectrum will provide potential for the coordination of low speed 12 The term back-up is used as opposed to the term secondary. The term secondary is used for a different context in this plan IO Plan Document

27 data, most existing data systems will not be dynamically configurable or switchable from their existing frequencies and if so would not provide for information or system interoperability without additional higher level coordination. It is expected that initial applications of this spectrum will be limited to self-contained, deployable or transportable situational awareness systems such as Chemical, Biological, Radiation, Nuclear and Explosives (CBNRE) sensor or video relay systems. After this technology matures, standards materialize and vendors provide equipment, this section of the Plan will be further developed. 6.8 Agreement Formalization In order to ensure the long-term viability of interoperability systems, applicants are strongly encouraged to formally define the interoperability environment through the drafting of the following documents: Memorandum of Understanding (MOU) for Operating the 700 MHz Interoperability Channels (700 MHz Interoperability Usage Memorandum of Understanding) (Appendix H) Sharing Agreement (Agency Build-out Memorandum of Understanding) (Appendix F) 7.0 System Design/Efficiency Requirements 7.1 Interference Protection-vs.-Interoperability Continuity Development of design requirements leads to a set of opposing requirements, the need for local chatter free interoperability and wide-ranging, continuous coverage. With the exception of the channel sets specified in section 4.5.3, DivTel will develop a channel plan allotment that provides the proper operating environment for incidents of varying scopes. The reuse of local low power interoperability channels for geographically small incidents such as a small fire must be balanced with the need for large continuous coverage systems for geographically wide-ranging incidents such as a hurricane. The channel sets specified in sections 3.7 and are intended for deployable or mobile systems subject to use at any location statewide. The channel sets specified in section are intended for statewide, continuous coverage from the collective contributions of each jurisdiction. For other voice interoperability channels, CAPRAD 14 shall be the basis for allotting area-specific interoperability channels. 14 CAPRAD is currently designed for the General Use channels and the Region Planning Committee process. While Interoperable Use channels may be allotted in CAPRAD, applying for and approving these channels in CAPRAD currently does not support DivTel s administrative authority. 700 IO Plan Document

28 7.2 Interoperability Channel Coverage Requirements The intent of this plan is to establish, on a zone-by-zone basis, statewide coverage for vehicularmobile units and urban-metropolitan area coverage for hand-held portable units on all the interoperability channel sets as needed. Communications reliability for system design purposes is defined as having been engineered for a 95% probability of communications (Option A radio standard) 15 at the defined coverage contour (or 98.4% probability of communications over the defined coverage area). This is based on producing a Delivered Audio Quality (DAQ) of 3.4, which is comparable to an equivalent intelligibility of 20 db SINAD (TIA/EIA) for the worst case of either talk-out (base to mobile) or talk-back (mobile to base). A DAQ of 3.4 is defined as Speech understandable with repetition only rarely needed. Some Noise/Distortion. DAQ is defined in TIA Telecommunications Systems Bulletin (TSB) TIA-TSB-88.1-D Any application submitted to DivTel for authorization of a Fixed (Mobile-Relay) station must include detailed plans for the establishment of either a county-wide vehicular mobile system or an urban-metropolitan area hand-held portable system, or both. Such applications must also define the radio frequency control station communications paths to be established with agencies in adjacent counties and/or metropolitan areas. When interoperability channels are integrated into existing or proposed 700 MHz or 800 MHz infrastructure, the coverage of the interoperability channels must at least match the greater coverage of the other channels in the system. In absence of existing or proposed 700 MHz or 800 MHz infrastructure, a radio zone for vehicular mobile units is defined to be one county unless otherwise approved by DivTel. A radio zone for hand-held portable units is defined to be a specific urban metropolitan area, as agreed to by DivTel. 7.3 Spectrum Efficiency Standards Equipment using the interoperability channels must adhere to FCC Modulation and spectrum usage efficiency requirements (shown below) Modulation and spectrum usage efficiency requirements. Transmitters designed to operate in MHz and MHz frequency bands must meet the following modulation standards: (a) All transmitters in the MHz and MHz frequency bands must use digital modulation. Mobile and portable transmitters may have analog modulation capability only as a secondary mode in addition to its primary digital mode. Mobile and portable transmitters that only operate on the low power channels designated in (b)(3), (b)(4), are exempt from this digital modulation requirement. 15 Option A radio standards are defined in the State of Florida, Law Enforcement Communications Plan. 700 IO Plan Document

29 (b) Transmitters designed to operate in the narrowband segment using digital modulation must be capable of maintaining a minimum data (nonvoice) rate of 4.8 kbps per 6.25 khz of bandwidth. (c) Transmitters designed to operate in the wideband segment using digital modulation must be capable of maintaining a minimum data (non-voice) rate of 384 kbps per 150 khz of bandwidth. (d) The following provisions apply to licensees operating in the channels designated in (b)(5) or (b)(6). (1) With the exception of licensees designated in paragraph (d)(2) of this section, after December 31, 2014, licensees may only operate in voice mode in these channels at a voice efficiency of at least one voice path per 6.25 khz of spectrum bandwidth. (2) Licensees authorized to operate systems in the voice mode on these channels from applications filed on or before December 31, 2014, may continue operating in voice mode on these channels (including modification applications of such licenses granted after December 31, 2014, for expansion or maintenance of such systems) at a voice efficiency of at least one voice path per 12.5 khz of spectrum bandwidth until December 31, (3) The licensees designated in paragraph (d)(2) of this section must, no later than January 31, 2017, file a declaration through the Universal Licensing System that they are operating these channels at a voice efficiency of at least one voice path per 6.25 khz of spectrum bandwidth. 7.4 Orphaned Channels Part only permits certain groups of adjacent channels to be combined in the creation of channel sets (refer to footnotes in Appendix A 700MHz Band Plan per Second R&O in PS Docket ). Due to the nature of the 700 MHz band plan, it is possible that orphaned channels may be created as a result of partial implementation of any of the allowed channel sets. For example, channel set 7TAC51 consists of channels 23 and 24. Allotting channel 24 for use in a single voice path system would orphan or leave channel 23 unused. Partial use of the allowed channel sets would be spectrally inefficient and is strongly discouraged. The IO channel sets covered by this Plan are expected to be fully utilized and every effort will be made to ensure that no channel is orphaned as a result of any interoperability license issued and subsequent implementation. 8.0 Coordination with Adjacent States Florida shares borders with Georgia and Alabama and based on distance may require coordination with Mississippi. 16 With respect to 7.1, the borders of adjoining states should be handled in the 16 Escambia and Santa Rosa Counties are within 70 miles of the Mississippi State line. 700 IO Plan Document

30 CAPRAD 17 frequency database allotment process. In any event, adjacent States will be notified of any applications that potentially interfere with their States. 8.1 Procedure for Build-out Approval and Notification Build-out Approval Div-Tel will request associated adjacent States approval, prior to carrying out section As a guideline, associated adjacent State s will be determined by the following: Fixed station tower coordinates are 70 miles or closer to an adjacent State line. Deployable systems have an area of operation boundary common with an adjacent State. Vehicular repeater systems have an area of operation boundary common with an adjacent State line. DivTel will continue to regularly advise and seek coordination with these adjacent States as to the implementation of systems on these channels, as well as regarding any changes to this or the adjacent States plans for use of these channels. All mutual agreements between these adjacent States will be documented and retained with the Plan records Build-out Notification DivTel will notify associated adjacent States upon successful licensing and implementation of 700 MHz interoperable channels. This will allow tracking the licensed and operational readiness status of 700 MHz interoperable radio channel for interoperable use. 8.2 Procedure for Build-out Coordination Referring to the procedure in section 6.3, overlapping allotments, licensing, and implementation of channel sets may likely occur between adjacent States. Overlap between adjacent States will be minimal for Local channel sets, increasing in potential for regional and statewide channel sets. Therefore, it will be necessary for agencies to understand and accept the need to coordinate implementation of their channel sets accordingly to prevent what will be referred to as cochannel chaos in lieu of co-channel interference. 18 Co-channel chaos will be further mitigated by the implementation of a dispatch priority matrix per section 6.4, establishing and recognizing primary and back-up NCCs between adjacent States albeit, operational control of systems in each State may likely be limited to the respective agency(ies) in each respective State rather than inter-state control of each State s system(s). Allotment of channel sets for build-out will be established as follows: Statewide overlapping allotments will be continuous along the adjacent State areas for respective channel sets. 17 Ibid., pg Ibid., pg IO Plan Document

31 Regional overlapping allotments will be continuous along the adjacent State areas for the each regional area common to the state line for each region s channel sets. Local overlapping allotments will be continuous along the adjacent State areas for the each local area common to the state line for each local area s channel sets. The limited number of channel sets and the need for statewide, regional, and local allotments will determine the extent of overlap between adjacent States. 8.3 Dispatch Control Priority Matrix In addition to Section 6.4, use of an interoperability channel set must be coordinated with the adjacent State s Department responsible for administering the interoperability channels when mutual interests exist, particularly within 70 miles distance of the common State line. In absence of the State s Departments, use during a real time event can be coordinated with the FDEM, SEOC- ESF2, SWG-ICC, or as appropriate between the incident commander(s) involved in the event. 8.4 Implementation Dispute Resolution Process In the event that a dispute arises between Florida and an adjacent State or States, regarding spectrum allocations or implementation, which cannot be resolved within 60 days, the parties to the dispute will request a hearing by the NRPC. See Appendix I for details and Dispute Resolution Agreements signed by adjacent States. 8.5 Channel Control Dispute Resolution Process In the event that a dispute arises between Florida and an adjacent State or States, regarding interoperability channel control which cannot be resolved within 60 days, the parties to the dispute will request a hearing by the NRPC. See Appendix I for details and Dispute Resolution Agreements signed by adjacent States. 8.6 Low Speed Data Channels In the event that a dispute arises between Florida and an adjacent State or States, regarding interoperability low speed data channels which cannot be resolved within 60 days, the parties to the dispute will request a hearing by the NRPC. See Appendix I for details and Dispute Resolution Agreements signed by adjacent States. 8.7 Agreement Formalization In order to ensure the long-term viability of interstate interoperability systems, applicants are strongly encouraged to formally define the interoperability environment through the drafting of the following documents: Memorandum of Understanding (MOU) for Operating the 700 MHz Interoperability Channels (700 MHz Interoperability Usage Memorandum of Understanding) (Appendix H) Sharing Agreement (Agency Build-out Memorandum of Understanding) (Appendix F) 700 IO Plan Document

32 9.0 Certification Until CAPRAD is fully functional for Interoperability Use channel sets and DivTel s administration of the same, any applications shall be hardcopy or.pdf when submitting to DivTel for approval. Completed applications shall be submitted to DivTel at the following address. Charles Hadley, Supervisor Local Public Safety Section State of Florida, DMS-DivTel, Public Safety Bureau 4030 Esplanade Way, Suite 180 Tallahassee, Florida, Following application approval by DivTel, a copy of the application shall be retained by DivTel. The original application will then be returned to the applicant with instructions to send the application to an approved FCC Frequency Coordinator accompanied by payment of the required fees. DO NOT send any payment with the initial application to DivTel. Applications shall be submitted using the latest versions of FCC Form 601 "Application for Wireless Telecommunications Bureau Radio Service Authorization", and any supplementary form required by the FCC certified Frequency Coordinator. In addition, each application shall include all supplementary documentation and exhibits as required by this Plan. Applications received by DivTel, which are incomplete, shall be subject to being returned to the applicant without further action. Copies of the necessary forms and FCC instructions, as well as general assistance in completing applications may be obtained by written request to Charles Hadley at the address above or at Charles.Hadley@dms.myflorida.com. 10. FCC Plan Approval In accordance with the governance of this Plan, as defined in Section 1.3, DivTel will submit this Plan and any amendments to the FCC for approval. 700 IO Plan Document

33 Appendix A Public Safety 700 MHz Narrowband Spectrum Allocations 700 IO Plan Document

34 Taken from FCC web site at IO Plan Document

35 Taken from FCC web site at IO Plan Document

36 Public Safety Narrowband Spectrum Allocations Designated Purpose General Use State License Interoperability Secondary Trunking Low Power I/O Nationwide Call I/O Low Speed Data Reserve Total Amount of Spectrum 7.7 MHz (64.0%) 2.4 MHz (20.0%) 0.7 MHz (5.8%) 0.2 MHz (1.7%) 0.3 MHz (2.5%) 50 KHz (.42%) 50 KHz (.42%) 0.6 MHz (5.0%) 12 MHz (100%) Channels (12.5 KHz) 616 Channels 192 Channels 56 Channels 16 Channels 24 Channels 4 Channels 4 Channels 48 Channels 960 Channels Taken from CAPRAD web site at IO Plan Document

37 Appendix B 700 MHz Interoperability Channel Nomenclature 700 IO Plan Document

38 Base Channel Sets Mobile Channel Sets I/O Channel Direct (Simplex /Mobile) Channel No Frequency (MHz) Channel No Frequency (MHz) Lower Upper Lower Center Lower Upper Lower Center 7TAC51 7TAC51D CALL50 7CALL50D MED65 7MED65D MED66 7MED66D TAC52 7TAC52D TAC55 7TAC55D FIRE63 7FIRE63D FIRE64 7FIRE64D TAC53 7TAC53D TAC56 7TAC56D LAW61 7LAW61D LAW62 7LAW62D TAC54 7TAC54D DATA69 7DATA69D MOB59 7MOB59D GTAC57 7GTAC57D MED86 7MED86D TAC71 7TAC71D CALL70 7CALL70D MED87 7MED87D FIRE83 7FIRE83D TAC72 7TAC72D TAC75 7TAC75D FIRE84 7FIRE84D LAW81 7LAW81D TAC73 7TAC73D TAC76 7TAC76D LAW82 7LAW82D MOB79 7MOB79D TAC74 7TAC74D DATA89 7DATA89D GTAC77 7GTAC77D Table B MHz Interoperability Channel Set Frequencies 700 IO Plan Document

39 12.5 khz Channel Set Label Radio Service Direct Label 01 Pair 23-24/ TAC51* General Public Safety Service (secondary trunked) 7TAC51D 02 Pair 39-40/ CALL50 Calling Channel 7CALL50D 03 Pair 63-64/ MED65 EMS 7MED65D 04 Pair 79-80/ MED66 EMS 7MED66D 05 Pair / TAC52* General Public Safety Service (secondary trunked) 7TAC52D 06 Pair / TAC55 General Public Safety Service 7TAC53D 07 Pair / FIRE63 Fire 7FIRE63D 08 Pair / FIRE64 Fire 7FIRE64D 09 Pair / TAC53* General Public Safety Service (secondary trunked) 7TAC53D 10 Pair / TAC56 General Public Safety Service 7TAC56D 11 Pair / LAW61 Police 7LAW61D 12 Pair / LAW62 Police 7LAW62D 13 Pair / TAC54* General Public Safety Service (secondary trunked) 7TAC54D 14 Pair / DATA69 Mobile Data 7DATA69D 15 Pair / MOB59 Mobile Repeater 7MOB59D 16 Pair / GTAC57 Other Public Service 7GTAC57D 17 Pair / MED86 EMS 7MED86D 18 Pair / TAC71* General Public Safety Service (secondary trunked) 7TAC71D 19 Pair / CALL70 Calling Channel 7CALL70D 20 Pair / MED87 EMS 7MED87D 21 Pair / FIRE83 Fire 7FIRE83D 22 Pair / TAC72* General Public Safety Service (secondary trunked) 7TAC72D 23 Pair / TAC75 General Public Safety Service 7TAC75D 24 Pair / FIRE84 Fire 7FIRE84D 25 Pair / LAW81 Police 7LAW81D 26 Pair / TAC73* General Public Safety Service (secondary trunked) 7TAC73D 27 Pair / TAC76 General Public Safety Service 7TAC76D 28 Pair / LAW82 Police 7LAW82D 29 Pair / MOB79 Mobile Repeater 7MOB79D 30 Pair / TAC74* General Public Safety Service (secondary trunked) 7TAC74D 31 Pair / DATA89 Mobile Data 7DATA89D 32 Pair / GTAC77 Other Public Service 7TGAC77D * Trunked operation permitted on a secondary basis per Section 4.5. Table B MHz Interoperability Channel Set Nomenclature Taken from the National Public Safety Telecommunications Council s Channel Naming Report, June IO Plan Document

40 Appendix C FCC CFR Title 47, Part 90, Section 525 Administration of Interoperability Channels (Taken from The Electronic Code of Federal Regulations at IO Plan Document

41 Sec Administration of interoperability channels. (a) States are responsible for administration of the Interoperability channels in the MHz and MHz frequency bands. Base and control stations must be licensed individually. A public safety entity meeting the requirements of Sec may operate mobile or portable units on the Interoperability channels in the MHz and MHz frequency bands without a specific authorization from the Commission provided it holds a part 90 license. All persons operating mobile or portable units under this authority are responsible for compliance with part 90 of these rules and other applicable federal laws. (b) License applications for Interoperability channels in the MHz and MHz frequency bands must be approved by a state-level agency or organization responsible for administering state emergency communications. States may hold the licenses for Interoperability channels or approve other qualified entities to hold such licenses. States may delegate the approval process for interoperability channels to another entity, such as regional planning committees. [72 FR 48860, Aug. 24, 2007] 700 IO Plan Document

42 Appendix D 700 MHz Interoperability Channels Administrative Notice 700 IO Plan Document

43 700 IO Plan Document

44 Appendix E Florida Counties 700 IO Plan Document

45 Alachua Franklin Lee Pinellas Baker Gadsden Leon Polk Bay Gilchrist Levy Putnam Bradford Glades Liberty Santa Rosa Brevard Gulf Madison Sarasota Broward Hamilton Manatee Seminole Calhoun Hardee Marion Suwannee Charlotte Hendry Martin St. Johns Citrus Hernando Miami-Dade St. Lucie Clay Highlands Monroe Sumter Collier Hillsborough Nassau Taylor Columbia Holmes Okaloosa Union Desoto Indian River Okeechobee Wakulla Dixie Jackson Orange Walton Duval Jefferson Osceola Washington Escambia Lake Palm Beach Volusia Flagler Lafayette Pasco 700 IO Plan Document

46 Appendix F Sample Sharing Agreement 700 IO Plan Document

47 Rules governing sharing of the 700 MHz Interoperability Channels Mobile Unit Communications rules are established in FCC for the operation of mobile units in vehicles not under the control of the licensee. The 700 MHz Interoperability channels are specifically addressed in (a)(3) as follows: (3) On the Interoperability Channels in the 700 MHz Public Safety Band (See (b)(1)), hand-held and vehicular transmitters may be operated by any licensee holding a license in the 700 MHz Public Safety Band or by any licensee holding a license for any other public safety frequency pursuant to part 90 of the Commission s rules. Therefore, individual licenses are not required for hand-held and vehicular transmitters in the 700 MHz Band. Arrangements for mobile unit use are normally made by means of written agreement between the local fixed station license holder and mobile user to determine channel loading. Refer to the sample sharing agreement below. The written agreement should include the following: 1. Typed on the agency's letterhead granting the sharing agreement. 2. State the quantity of mobile, or portable radios covered in the agreement. 3. State the call sign, frequency(ies), and maximum power output associated with the written agreement, and other technical parameters authorized on the granting agency's radio station license. 4. State the written agreement applies to operations in cooperation and coordination with the activities of the licensee per FCC State the granting agency's reserved right to effectively eliminate the possibility of unauthorized operation that ultimately could result in terminating the written agreement. Example of a written agreement (grantor) authorizes (grantee) to operate (quantity) mobile (or portable) radios. Such operation shall be per the following parameters. Call Sign Frequency(ies) Max. Power Other Technical Parameters (Use additional attachments as necessary for more frequencies/channels) This written agreement applies to operations in cooperation and coordination with activities of the licensee per FCC Furthermore, grantor reserves the right to effectively eliminate the possibility of unauthorized operation that ultimately could result in terminating this written agreement. (authorized signor) (typed signor's name) (authorizing agency) (date) 700 IO Plan Document

48 Appendix G NCC 700 MHz Pre-Assignment Rules/Recommendations (Taken from NPSTC 700 MHz Regional Planning Guidebook, Ver. 2.01, APPENDIX K - Simplified 700 MHz Pre-Assignment Rules Recommendation IO Plan Document

49 Simplified 700 MHz Pre-assignment Rules Introduction This paper describes a process for coordinating the initial block assignments of 700 MHz channels before details of actual system deployments is available. In this initial phase, there is little actual knowledge of the specific equipment to be deployed and the exact antenna sites locations. As a result, a simple, high-level method is proposed to establish guidelines for frequency coordination. When actual systems are deployed, additional details will be known and the system designers will be required to select specific sites and supporting hardware to control interference. Overview Assignments will be based on a defined service area for each applicant. This will normally be an area defined by geographical or political boundaries such as city, county or by a data file consisting of line segments creating a polygon that encloses the defined area. The service contour is normally allowed to extend slightly beyond the geo/political boundaries such that systems can be designed for maximum signal levels within the boundaries, or coverage area. Systems must also be designed to minimize signal levels outside their geo/political boundaries to avoid interference into the coverage area of other cochannel users. For co-channel assignments, the 40 db service contour will be allowed to extend beyond the defined service area by 3 to 5 miles, depending on the type of environment: urban, suburban or rural. The cochannel 5 db interfering contour will be allowed to touch but not overlap the 40 db service contour of the system being evaluated. All contours are (50,50). For adjacent and alternate channels, the 60 db interfering contour will be allowed to touch but not overlap the 40 db service contour of the system being evaluated. All contours are (50,50). Discussion Based upon the ERP/HAAT limitations referenced in 47CFR (a), the maximum field strength will be limited to 40 db relative to 1 V/m (customarily denoted as 40 db ). It is assumed that this limitation will be applied similar to the way it is applied in the / MHz band. That is, a 40 db field strength can be deployed up to a defined distance beyond the edge of the service area, based on the size of the service area or type of applicant, i.e. city, county or statewide system. This is important that public safety systems have adequate margins for reliability within their service area in the presence of interference, including the potential for interference from CMRS infrastructure in adjacent bands. The value of 40 db in the 700 MHz band corresponds to a signal of dbm, received by a halfwavelength dipole ( /2) antenna. The thermal noise floor for a 6.25 khz bandwidth receiver would be in the range of -126 dbm, so there is a margin of approximately 33 db available for noise limited reliability. Figure 1 shows show the various interfering sources and how they accumulate to form a composite noise floor that can be used to determine the reliability or probability of achieving the desired performance in the presence of various interfering sources with differing characteristics. 700 IO Plan Document

50 If CMRS out-of-band emissions (OOBE) noise is allowed to be equal to the original thermal noise floor, there is a 3 db reduction 19 in the available margin. This lowers the reliability and/or the channel performance of Public Safety systems. The left side of Figure 1 shows that the original 33 db margin is reduced by 3 db to only 30 db available to determine noise + CMRS OOBE limited performance and reliability. There are also different technologies with various channel bandwidths and different performance criteria. C/N in the range of db is required to achieve channel performance. Desired Signal Level Joint Probability C/N Determines performance & reliability C/N - 3 db Determines ultimate performance & reliability C/I, 1% Multiple Sources Multiple bandwidths Receiver ktb + NF (db) -126 dbm (6.25 khz) CMRS Site Noise) Figure 1 - Interfering Sources Create A Noise Level Influencing Reliability In addition, unknown adjacent and alternate channel assignments need to be accounted for. The cochannel and adjacent/alternate sources are shown in the right hand side of Figure 1. At the edge of the service area, there would normally be only a single co-channel source, but there could potentially be several adjacent or alternate channel sources involved. It is recommended that co-channel assignments limit interference to <1% at the edge of the service area (worst case mile). A C/I ratio of 26.4 db plus the required capture value (~10 db) is required to achieve this goal. 20 The ultimate performance and reliability has to take into consideration both the noise sources (thermal & CMRS OOBE) and all the interference sources. The center of Figure 1 shows that the joint probability that the both performance criteria and interference criteria are met must be determined. 19 TIA TR8 made this 3 db allowance for CMRS OOBE noise during the meetings in Mesa, AZ, January See Appendix A for an explanation of how the 1% interference value is defined and derived. 700 IO Plan Document

51 Table 1 shows estimated performance considering the 3 db rise in the noise floor at the 40 db signal level. Performance varies due to the different Cf/N requirements and noise floors of the different modulations and channel bandwidths. Note that since little is known about the affects of terrain, an initial lognormal standard deviation of 8 db is used. Comparison of Joint Reliability for various configurations Channel Bandwidth 6.25 khz 12.5 khz 12.5 khz 25.0 khz Receiver ENBW (khz) Noise Figure(10 db) Receiver Noise Floor (dbm) Rise in Noise Floor (db) New Receiver Noise Floor (db) dbu = dbm Receiver Capture (db) Noise Margin (db) C/N Required for DAQ = C/N Margin (db) Standard deviation (8 db) Z Noise Reliability (%) 95.45% 95.45% 91.06% 76.37% C/I for <1% prob of capture I (dbu) I (dbm) Joint Probability (C & I) 94.7% 94.7% 90.4% 76.1% 40 dbu = MHz Table 1 Joint Probability For Project 25, 700 MHz Equipment Configurations. These values are appropriate for a mobile on the street, but are considerably short to provide reliable communications to portables inside buildings. Portable In-Building Coverage Most Public Safety communications systems, today, are designed for portable in-building 21 coverage and the requirement for >95 % reliable coverage. To analyze the impact of requiring portable in building coverage and designing to a 40 db service contour, several scenarios are presented. The different scenarios involve a given separation from the desired sites. Whether simulcast or multi-cast is used in wide-area systems, the antenna sites must be placed near the service area boundary and directional antennas, directed into the service area, must be used. The impact of simulcast is included to show that the 40 db service contour must be able to fall outside the edge of the service area in order to meet coverage requirements at the edge of the service area. From the analysis, recommendations are made on how far the 40 db service contour should extend beyond the service area. Table 2 estimates urban coverage where simulcast is required to achieve the desired portable in building coverage. Several assumptions are required to use this estimate. 21 Building penetration losses typically required for urban = 20 db, suburban = 15 db, rural = 10 db. 700 IO Plan Document

52 Distance from the location to each site. Equal distance is assumed. CMRS noise is reduced when entering buildings. This is not a guarantee as the type of deployments is unknown. It is possible that CMRS units may have transmitters inside buildings. This could be potentially a large contributor unless the CMRS OOBE is suppressed to TIA s most recent recommendation and the site isolation is maintained at 65 db minimum. The 40 db service contour is allowed to extend beyond the edge of the service area boundary. Other configurations may be deployed utilizing additional sites, lower tower heights, lower ERP and shorter site separations. Estimated Performance at 2.5 miles from each site Channel Bandwidth 6.25 khz 12.5 khz 12.5 khz 25.0 khz Receiver Noise Floor (dbm) Signal at 2.5 miles (dbm) Margin (db) C/N Required for DAQ = Building Loss (db) Antenna Loss (dbd) Reliability Margin Z Single Site Noise Reliability (%) 85.60% 85.60% 76.58% 39.17% Simulcast with 2 sites 97.93% 97.93% 94.51% 62.99% Simulcast with 3 sites 99.70% 99.70% 98.71% 77.49% Simulcast with 4 sites 99.96% 99.96% 99.70% 86.30% Table 2, Estimated Performance From Site(s) 2.5 Miles From Typical Urban Buildings. Table 2 shows for the example case of 2.5 miles a single site cannot provide >95% reliability. Either more sites must be used to reduce the distance or other system design techniques must be used to improve the reliability. For example, the table shows that simulcast can be used to achieve public safety levels of reliability at this distance. Table 2 also shows that the difference in performance margin requirements for wider bandwidth channels requires more sites and closer site-to-site separation. 700 IO Plan Document

53 Figures 2 and 3 show how the configurations would potentially be deployed for a typical site with 240 Watts ERP. This is based on: 75 Watt transmitter, dbw 200 foot tower 10 dbd 180 degree sector antenna dbd 5 db of cable/filter loss db dbw 240 Watts (ERPd) Figure 2 - Field Strength From Left Most Site. 700 IO Plan Document

54 Figure 3 - Antenna Configuration Required To Limit Field Strength Off Backside Figure 2 is for an urbanized area with a jurisdiction defined as a 5 mile circle. To provide the necessary coverage to portables in buildings at the center of the jurisdiction requires that the sites be placed along the edge of the service area and utilize directional antennas oriented toward the center of the service area (Figure 3). In this case, at 5 miles beyond the edge of the service area, the sites would produce a composite field strength of approximately 40 db. Since one site is over 10 db dominant, the contribution from the other site is not considered. The control of the field strength behind the site relies on a 20 db antenna with a Front to Back Ratio (F/B) specification as shown in Figure 3. This performance may be optomistic due to back scatter off local obstructions in urbanized areas. However, use of antennas on the sides of buildings can assist in achieving better F/B ratios and the initial planning is not precise enough to prohibit using the full 20 db. The use of a single site at the center of the service area is not normally practical. To provide the necessary signal strength at the edge of the service area would produce a field strength 5 miles beyond in excess of 44 db. However, if the high loss buildings were concentrated at the service area s center, then potentially a single site could be deployed, assuming that the building loss sufficiently decreases near the edge of the service area allowing a reduction in ERP to achieve the desired reliability. Downtilting of antennas, instead of directional antennas, to control the 40 db is not practical, in this scenario. For a 200 foot tall tower, the center of radiation from a 3 db down-tilt antenna hits the ground at ~ 0.75 miles. 22 The difference in angular discrimination from a 200 foot tall tower at service area boundary at 5 miles and service contour at 10 miles is approximately 0.6 degrees, so ERP is basically the same as ERP toward the horizon. It would not be possible to achieve necessary signal strength at service area boundary and have 40 db service contour be less than 5 miles away. 22 Use of high gain antennas with down-tilt on low-level sites is one of the causes of far-near interference experienced in the 800 MHz band. 700 IO Plan Document

55 Tables 3 and 4 represent the same configuration, but for less dense buildings. In these cases, the distance to extend the 40 db service contour can be determined from Table 5. Estimated Performance at 3.5 miles from each site Channel Bandwidth 6.25 khz 12.5 khz 12.5 khz 25.0 khz Receiver Noise Floor (dbm) Signal at 3.5 miles (dbm) Margin (db) C/N Required for DAQ = Building Loss (db) Antenna Loss (dbd) Reliability Margin Z Single Site Noise Reliability (%) 85.60% 85.60% 76.58% 39.17% Simulcast with 2 sites 97.93% 97.93% 94.51% 62.99% Simulcast with 3 sites 99.70% 99.70% 98.71% 77.49% Simulcast with 4 sites 99.96% 99.96% 99.70% 86.30% Table 3 - Lower Loss Buildings, 3.5 Mile From Site(s) Estimated Performance at 5.0 miles from each site Channel Bandwidth 6.25 khz 12.5 khz 12.5 khz 25.0 khz Receiver Noise Floor (dbm) Signal at 5.0 miles (dbm) Margin (db) C/N Required for DAQ = Building Loss (db) Antenna Loss (dbd) Reliability Margin Z Single Site Noise Reliability (%) 85.60% 85.60% 76.58% 39.17% Simulcast with 2 sites 97.93% 97.93% 94.51% 62.99% Simulcast with 3 sites 99.70% 99.70% 98.71% 77.49% Simulcast with 4 sites 99.96% 99.96% 99.70% 86.30% Table 4 - Low Loss Buildings, 5.0 Miles From Site(s) Note that the receive signals were adjusted to offset the lowered building penetration loss. This produces the same numerical reliability results, but allows increasing the site to building separation and this in turn lowers the magnitude of the overshoot across the service area. Table 5 shows the field strength for a direct path and for a path reduced by a 20 db F/B antenna. This allows the analysis to be simplified for the specific example being discussed. 700 IO Plan Document

56 Site A Direct Path Site B Back Side of Overshoot Distance (mi) Field Strength (db ) 20 db F/B Antenna Field Strength (db ) Table 5 - Field Strength Vs. Distance From Site For the scenarios above, the composite level at the Service Contour is the sum of the signals from the two sites. The sum can not exceed 40 db. Table 5 allows you to calculate the distance to Service Contour given the distance from one of the sites. Scenario 1: Refer to Figure 3a. Site B is just inside the Service Area boundary and Service Contour must be <5 Miles outside Service Area boundary. Signal level at Service Contour from Site B is 30.1 db. Signal level for Site A can be up to 40 db, since when summing two signals with >10 db delta, the lower signal level has little effect (less than 0.4 db in this case). Therefore, Site A can be 10 miles from the Service Contour, or 5 miles inside the Service Area boundary. The coverage perfomance for this scenario is shown in Table 2, above, for 20 db building loss typical of urban areas. 700 IO Plan Document

57 Site A Site B Service Contour < 40 db 30.1 db 40.1 db Jurisdiction Figure 3a. Scenario 1 on of Use of Table 5 Scenario 2: Refer to bold data in Table 5. Site B is just inside the Service Area boundary and Service Contour must be <4 Miles outside Service Area boundary. Signal level at Service Contour from Site B is 33.5 db. Signal level for Site A can be up to 38.4 db. (See Appendix B for simple method to sum the powers of signals expressed in decibels.) The composite power level is 39.7 db. Therefore, Site A can be slightly less than 11 miles from the Service Contour, or ~7 miles inside the Service Area boundary. The coverage perfomance for this example is shown in Table 3, above, for 15 db building loss typical of suburban areas. Scenario 3: Site B is just inside the Service Area boundary and Service Contour must be <3 Miles outside Service Area boundary. Signal level at Service Contour from Site B is 37.5 db. Signal level for Site A can be up to 36.4 db. (See Appendix B simple method to sum signals expressed in decibels.) The composite power level is 40.0 db. Therefore, Site A can be ~13 miles from the Service Contour, or ~10 miles inside the Service Area boundary. The coverage perfomance for this example is shown in Table 4, above, for 10 db building loss typical of rural areas. Service Contour Extension Recommendation The resulting recommendation for extending the 40 db service contour beyond the service area boundary is: 700 IO Plan Document

58 Type of Area Extension (mi.) Urban (20 db Buildings) 5 Suburban (15 db Buildings) 4 Rural (10 db Buildings) 3 Table 6 - Recommended Extension Distance Of 40 db Field Strength Using this recommendation the 40 db service contour can then be constructed based on the defined service area without having to perform an actual prediction. Interfering Contour Table 1 above shows that 36.4 db of margin is required to provide 10 db of co-channel capture and <1% probability of interference. Since the 40 db service contour is beyond the edge of the service area, some relaxation in the level of interference is reasonable. Therefore, a 35 db co-channel C/I ratio is recommended and is consistent with what is currently being licensed in the / MHz Public Safety band. Co-Channel Interfering Contour Recommendation Allow the constructed 40 db (50,50) service contour to extend beyond the edge of the defined service area by the distance indicated in Table 6. Allow the 5 db (50,50) interfering contour to intercept but not overlap the 40 db service contour. 700 IO Plan Document

59 Figure 4 - Co-Channel Reuse Criterion Adjacent and Alternate Channel Considerations Adjacent and alternate channels are treated as being noise sources that alter the composite noise floor of a victim receiver. Using the 47 CFR values of ACCP can facilitate the coordination of adjacent and alternate channels. The C/I requirements for <1% interference can be reduced by the value of ACCPR. For example to achieve an X db C/I for the adjacent channel that is -40 dbc a C/I of [X-40] db is required. Where the alternate channel ACP value is -60 dbc, then the C/I = [X-60] db is the goal for assignment(s). There is a compounding of interference energy, as there are numerous sources, i.e. co channel, adjacent channels and alternate channels plus the noise from CMRS OOBE. There is insufficient information in 47 CFR to include the actual receiver performance. Receivers typically have skirts that allow energy outside the bandwidth of interest to be received. In addition, the FCC defines ACCP differently than does the TIA. The term used by the FCC is the same as the TIA definition of ACP. The subtle difference is that ACCP defines the energy intercepted by a defined receiver filter (e.g., 6 khz ENBW). ACP defines the energy in a measured bandwidth that is typically wider than the receiver (e.g., 6.25 khz channel bandwidth). As a result, the FCC values are optimistic at very close spacing and somewhat pessimistic at wider spacings, as the typical receiver filter is less than the channel bandwidth. In addition, as channel bandwidth is increased, the total amount of noise intercepted rises compared to the level initially defined in a 6.25 khz channel bandwidth. However, the effect is diminished at very close spacings as the slope of the noise curve falls off rapidly. At greater spacings, the slope of the noise curve is essentially flat and the receiver s filter limits the noise to a rise in the thermal noise floor. Digital receivers tend to be less tolerant to interference than analog. Therefore, a 3 db reduction in the C/(I+N) can reduce a DAQ = 3 to a DAQ = 2, which is threshold to complete muting in digital receivers. Therefore to maintain a DAQ = 3, at least 17 db of fading margin plus the 26.4 db margin for keeping the interference below 1% probability is required, for a total margin of 43.4 db. However, this margin 700 IO Plan Document

60 would be at the edge of the service area and the 40 db service contour is allowed to extend past the edge of the service area. Frequency drift is controlled by the FCC requirement for 0.4-ppm stability when locked. This equates to approximately a 1 db standard deviation, which is negligible when associated with the recommended initial lognormal standard deviation of 8 db and can be ignored. Project 25 requires that a transceiver receiver have an ACIPR of 60 db. This implies that an ACCPR 65 db will exist for a companion receiver. A companion receiver is one that is designed for the specific modulation. At this time the highest likelihood is that receivers will be deploying the following receiver bandwidths at the following channel bandwidths. Estimated Receiver Parameters Channel Bandwidth Receiver Bandwidth 6.25 khz 5.5 khz 12.5 khz 5.5 or 9 khz 25 khz 18.0 khz Table 7 - Estimated Receiver Parameters Based on 47 CFR and the P25 requirement for an ACCPR 65 db into a 6.0 khz channel bandwidth and leaving room for a migration from Phase 1 to Phase 2, allows for making the simplifying assumption that 65 db ACCPR is available for both adjacent 25 khz spectrum blocks. The assumption is that initial spectrum coordination sorts are based on 25 khz bandwidth channels. This provides the maximum flexibility by using 65 db ACCPR for all but one possible combination of 6.25 khz channels within the 25 khz allotment. A B Figure 5, Potential Frequency Separations 700 IO Plan Document

61 Case Spacing ACCPR 25 khz to 25 khz 25 khz 65 db 25 khz to 12.5 khz khz 65 db 25 khz to 6.25 khz khz >40 db 12.5 khz to 12.5 khz 12.5 khz 65 db 12.5 khz to 6.25 khz khz >40 db 6.25 khz to 6.25 khz 6.25 khz 65 db Table 8 - ACCPR Values For Potential Frequency Separations All cases meet or exceed the FCC requirement. The most troublesome cases occur where the wider bandwidths are working against a Project 25 Phase 2 narrowband 6.25 khz channel. This precoordination based upon 25 khz spectrum blocks still works if system designers and frequency coordinators keep this consideration in mind and move the edge 6.25 khz channels inward away from the edge of the system. This approach allows a constant value of 65 db ACCPR to be applied across all 25 khz spectrum blocks regardless of what channel bandwidth is eventually deployed. There will also be additional coordination adjustments when exact system design details and antenna sites are known. For spectrum blocks spaced farther away, it must be assumed that transmitter filtering, in addition to transmitter performance improvements due to greater frequency separation, will further reduce the ACCPR. Therefore it is recommended that a consistent value of 65 db ACCPR be used for the initial coordination of adjacent 25 khz channel blocks. Rounding to be conservative due to the possibility of multiple sources allows the Adjacent Channel Interfering Contour to be approximately 20 db above the 40 db service contour, at 60 db. Interfering Signal [I] Allowable I 40 db db Desired Signal [C] 40 db ACCPR = 65 db Requirement for <1% = 43.4 db Figure 6 - Adjusted Adjacent 25 khz Channel Interfering Contour Value 700 IO Plan Document

62 Figure 7 - Example Of Adjacent/Alternate Overlap Criterion Adjacent Channel Interfering Contour Recommendation An adjacent (25 khz) channel shall be allowed to have its 60 db (50,50) interfering contour touch but not overlap the 40 db (50,50) service contour of a system being evaluated. Evaluations should be made in both directions. Final Detailed Coordination This simple method is only adequate for presorting large blocks of spectrum to potential entities. A more detailed analysis should be executed in the actual design phase to take all the issues into consideration. Additional factors that should be considered include: Degree of Service Area Overlap Different size of Service Areas Different ERPs and HAATs Actual Terrain and Land Usage Differing User Reliability Requirements Migration from Project 25 Phase 1 to Phase 2 Actual ACCP Balanced Systems Mobiles vs. Portables Use of voting 700 IO Plan Document

63 Use of simulcast Radio specifications Simplex Operation Future unidentified requirements. Special attention needs to be paid to the use of simplex operation. In this case, an interferer can be on an offset adjacent channel and in extremely close proximity to the victim receiver. This is especially critical in public safety where simplex operations are frequently used at a fire scene or during police operation. This type operation is also quite common in the lower frequency bands. In those cases, evaluation of base-to-base as well as mobile-to-mobile interference should be considered and evaluated. 700 IO Plan Document

64 Appendix A- Carrier to Interference Requirements There are two different ways that Interference is considered. Co Channel Adjacent and Alternate Channels Both involve using a C/I ratio. The C/I ratio requires a probability be assigned. For example, if 10% Interference is specified, the C/I implies 90% probability of successfully achieving the desired ratio. 1% interference means that there is a 99% probability of achieving the desired C/I. C I % 1 2 erfc C I margin 2 (1) This can also be written in a form using the standard deviate unit (Z). In this case the Z for the desired probability of achieving the C/I is entered. For example, for a 90% probability of achieving the necessary C/I, Z = C % Z 2 (2) I The most common requirements for several typical lognormal standard deviations ( ) are included in the following table based on Equation (2). Location Standard Deviation ( ) db Probability % 10% db db db db 5% db db db db 4% db db db db 3% db db db db 2% db db db db 1% db db db db Table A1 - Probability Of Not Achieving C/I For Various Location Lognormal Standard Deviations These various relationships are shown in Figure A1, a continuous plot of equation(s) 1 and IO Plan Document

65 Interference Probability (%) The Florida 700 MHz Public Safety Interoperability Channel Plan 100 Probability of Achieving Required C/I verses Mean C/I as a Funcation of Location Lognormal Standard deviation (does not include C/N requirement) C/I (db) Figure A1, Probability Of Achieving Required C/I As A Function Of Location Standard Deviation For co-channel the margin needs to include the capture requirement. When this is done, then a 1% probability of co channel interference can be rephrased to mean, there is a 99% probability that the capture ratio will be achieved. The capture ratio varies with the type of modulation. Older analog equipment has a capture ratio of approximately 7 db. Project 25 FDMA is specified at 9 db. Figure A1 shows the C/I requirement without including the capture requirement. The 8 db value for lognormal location standard deviation is reasonable when little information is available. Later when a detailed design is required, additional details and high-resolution terrain and land usage databases will allow a lower value to be used. The TIA recommended value is 5.6 db. Using 8 db initially and changing to 5.6 db provides additional flexibility necessary to complete the final system design. To determine the desired probability that both the C/N and C/I will be achieved requires that a joint probability be determined. Figure A2 shows the effects of a family of various levels of C/N reliability and the joint probability (Y-axis) in the presence of various probabilities of Interference. Note that at 99% reliability with 1% interference (X-axis) that the reduction is nearly the difference. This is because the very high noise reliability is degraded by the interference, as there is little probability that the noise criterion will not be satisfied. At 90%, the 1% interference has a greater likelihood that it will occur simultaneously when the noise criterion not being met, resulting in less degradation of the 90%. 700 IO Plan Document

66 Joint Probability [%] The Florida 700 MHz Public Safety Interoperability Channel Plan Joint Probability [8 db Standard Deviation] % 91% 92% 93% 94% 95% 96% 97% 98% 99% Probability of Interference [%] Figure A2 - Effect Of Joint Probability On The Composite Probability For adjacent and alternate channels, the channel performance requirement must be added to the C/I ratio. When this is applied, then a 1% probability of adjacent/alternate channel interference can be rephrased to mean, there is a 99% probability that the channel performance ratio will be achieved. 700 IO Plan Document

67 Add to the largest known power (db) The Florida 700 MHz Public Safety Interoperability Channel Plan Appendix B Adding Two Known Non-Coherent Powers Adding Two Known Non-Coherent Powers Difference between two known powers (db) In order to sum the power of two or more signals expressed in dbm or db, they level should be converted to a voltage level or a power level, summed (root of the sum of the squares), and then converted back to dbm or db. The chart above provides simple method to sum two power levels expressed in dbm or db. First find the difference between the two signals on the horizontal axis. Go up to the curve and across to the vertical axis to find the power delta. Add the power delta to the larger of the two original signal levels. Example 1: Signal A is 36.4 db. Signal B is 37.5 db. Difference is 1.1 db. Power delta is about 2.5 db. Composite signal level is 37.5 db db = 40 db. Example 2: Signal is 96.3 dbm. Signal B is 95.2 dbm. Difference is 1.1 db. Power delta is about 2.5 db. Composite signal level is 95.2 dbm db = dbm. 700 IO Plan Document

68 Appendix H Sample Memorandum of Understanding (Taken from APCO RPC 700 MHz Plan Template v9, Appendix G Interoperability Channel MOU Template RPC 700 MHz Plan Template v9.pdf) 700 IO Plan Document

69 (On State of Florida Letterhead) TO: FROM: DATE: SUBJECT: (signor of application and title) (agency name) Charles Ghini, Director State of Florida, Dept. of Management Services, Division of Telecommunications (mm/dd/yyyy) Memorandum of Understanding for Operating on the 700 MHz Interoperability Channels This memorandum of understanding (hereafter referred to as MOU) shall be attached to the application when submitting it. By virtue of signing and submitting the application and this MOU, (agency name) (hereafter referred to as APPLICANT) affirms its willingness to comply with the proper operation of the Interoperability (IO) channels as dictated by the State of Florida, Department of Management Services, Division of Telecommunications (hereafter referred to as DivTel) as approved by the Federal Communications Commission (hereafter referred to as FCC) and by the conditions of this MOU. The APPLICANT shall abide by the conditions of this MOU which are as follows: To operate by all applicable State, County, and City laws/ordinances. To utilize plain language for all transmissions. To monitor the Calling Channel(s) and coordinate the use of the Tactical Channels. To identify inappropriate use and migrate the same from occurring in the future. To limit secondary Trunked operation to the Interoperability channels specifically approved on the application and limited to channels listed below. To relinquish secondary Trunked operation of approved interoperability channels to requests for primary conventional access with same or higher priority. To mitigate contention for channels by exercising the Priority levels identified in this MOU. The preceding conditions are the primary, though not complete, requirements for operating in the interoperability channels. Refer to the 700 MHz Interoperability Channel Plan for the complete requirements. Priority Levels: 1. Disaster or extreme emergency operation for mutual aid and interagency communications; 2. Emergency or urgent operation involving imminent danger to life or property; 3. Special event control, generally of a preplanned nature (including Task Force operations) 4. Single agency secondary communications (default priority). 700 IO Plan Document

70 To resolve contention within the same priority, the channel should go to the organization with the wider span of control/authority. This shall be determined by DivTel for the operation or by the levels of authority/government identified in the contention. For clarification purposes and an aid to operate as authorized, any fixed base or mobile relay stations identified on the license for temporary locations (FCC station class FBT or FB2T, respectively) shall remain within the licensed area of operation. Similarly, vehicular/mobile repeater stations (FCC station class MO3) shall remain within the licensed area of operation. Federal agencies are permitted access to interoperability channels only as authorized by 47 CFR (c) & and Part 7.12 of the NTIA Manual. Any violation of this MOU, the Plan, or FCC Rule shall be addressed immediately. The first level of resolution shall be between the parties involved, next DivTel, next the National Regional Planning Council, and finally the FCC. (typed or printed name of authorized signer) (authorized signer identified above and consistent with application) (date) (agency name) (agency address) (agency address) (agency address) (signer phone) (signer s address, if available) 700 IO Plan Document

71 Appendix I Interstate Coordination Procedures and Procedures for Resolution of Disputes That May Arise Under FCC Approved Plans for the 700 MHz Interoperability Channels (Adapted from APCO RPC 700 MHz Plan Template v9, Appendix L Inter-Regional Coordination Procedures and Resolution of Disputes Template RPC 700 MHz Plan Template v9.pdf) 700 IO Plan Document

72 PROCESS FOR INTERSTATE DISPUTE RESOLUTION Counties or other geographic subdivisions within 70 miles of the State border need to share spectrum with the adjacent State(s). A 12.5 khz building block will be used to distribute spectrum between the States. Should disputes arise between interstate agencies concerning channel set allotments the following agreement defines the resolution process and has been agreed to by the adjacent authorities within Alabama, Georgia and Mississippi. 23 For the purposes of interstate coordination, Authority(ies) referenced herein refer to the agencies responsible for administration of the 700 MHz interoperability channels in each State. Therefore, within Florida this refers to DivTel. 23 Escambia and Santa Rosa Counties are within 70 miles of the Mississippi State line. 700 IO Plan Document

73 Interstate Coordination Procedures and Procedures for Resolution of Disputes That May Arise Under FCC Approved Plans for the 700 MHz Interoperability Channels I. INTRODUCTION 1. This is a mutually agreed upon Interstate Coordination Procedures Agreement (Agreement) by and between the following 700 MHz Interoperability Channel Authorities, [list Authorities here]. II. INTER-REGIONAL COORDINATION AGREEMENT 2. The following is the specific procedure for interstate coordination which has been agreed upon by [list Authorities here] and which will be used by the Authorities to coordinate with adjacent Authorities in the States of [list states here]. a. An application-filing window is opened or the Authority announces that it is prepared to begin accepting applications on a first-come/first-served basis. b. Applications by eligible entities are accepted. c. An application-filing window (if this procedure is being used) is closed after appropriate time interval. d. Intra- Authority review and coordination takes place, including a technical review resulting in assignment of channels. e. After intra-authority review, a copy of those frequency-specific applications requiring adjacent Authority approval, including a definition statement of proposed service area, shall then be forwarded to the adjacent Authority (ies) for review. 24 This information will be sent to the adjacent Authority chairperson(s). f. The adjacent Authority reviews the application. If the application is approved, a letter of concurrence shall be sent to the initiating Authority chairperson within thirty (30) calendar days. III. DISPUTE RESOLUTION 1. If the adjacent Authority(ies) cannot approve the request, the adjacent Authority shall document the reasons for partial or non-concurrence, and respond within 10 (Ten)-calendar days via . If the applying Authority cannot modify the application to satisfy the objections of the adjacent Authority 24 If an applicant s proposed service area extends into an adjacent State (s), the affected Authority(ies) must approve the application. Service area shall normally be defined as the area included within the geographical boundary of the applicant, plus three (3) miles. Other definitions of service area shall be justified with an accompanying Memorandum of Understanding (MOU) or other application documentation between agencies, i.e. mutual aid agreements. 700 IO Plan Document

74 then, a working group comprised of representatives of the two Authorities shall be convened within thirty (30) calendar days to attempt to resolve the dispute. The working group shall then report its findings within thirty (30) calendar days to the Authority chairperson s . Findings may include, but not be limited to: i. Unconditional concurrence; ii. Conditional concurrence contingent upon modification of Applicant s technical parameters; or iii. Partial or total denial of proposed frequencies due to inability to meet co-channel/adjacent channel interference free protection to existing licensees within the adjacent State. 2. If the Interstate Working Group cannot resolve the dispute, then the matter shall be forwarded for evaluation to the National Regional Planning Council (NRPC). Each Authority involved in the dispute shall include a detailed explanation of its position, including engineering studies and any other technical information deemed relevant. The NRPC will, within thirty (30) calendar days, report its recommendation(s) to the Authority chairpersons. The NRPC s decision may support either of the disputing Authorities or it may develop a proposal that it deems mutually advantageous to each disputing Authority. Where adjacent Authority concurrence has been secured, and the channel assignments would result in no change to the Authority s currently Commission approved channel assignment matrix. The initiating Authority may then advise the applicant(s) that their application may be forwarded to a frequency coordinator for processing and filing with the Commission. Upon Commission issuance of an Order adopting the amended channel assignment matrix, the initiating Authority chairperson will send a courtesy copy of the Order to the adjacent Authority chairperson(s) and may then advise the applicant(s) that they may forward their applications to the frequency coordinator for processing and filing with the Commission. IV. CONCLUSION IN AGREEMENT HERETO, [list Authorities here] do hereunto set their signatures the day and year first above written. Respectfully, [all signatories to agreement] Date: 700 IO Plan Document

75 Acronym List AES ANSI APCO CBRNE CAPRAD DES DAQ DHS DMS DivTel FCC FDEM FEITC FEMA ICS MOU MRS NCC NCC NECP NIMS NPSPAC Advanced Encryption Standard American National Standards Institute Association of Public Safety Communications Officials Chemical, Biological, Radiation, Nuclear and Explosives Computer Assisted Pre-coordination Resource and Database Data Encryption Standard Delivered Audio Quality Department of Homeland Security Department of Management Services Division of Telecommunications Federal Communications Commission Florida Division of Emergency Management Florida Executive Interoperability Technologies Committee Federal Emergency Management Agency Incident Command System Memorandum of Understanding mobile repeater systems National Coordination Committee Network Control Center National Emergency Communications Plan National Incident Management System National Public Safety Planning Advisory Council 700 IO Plan Document

76 NPSTC NRPC NTIA PSWAC RCC National Public Safety Telecommunications Council National Regional Planning Council National Telecommunications and Information Administration Public Safety Wireless Advisory Committee Regional Communications Center SEOC-ESF2 State Emergency Operations Center Emergency Support Function 2 SIEC SWG-ICC SCIP TIA TSB State Interoperability Executive Committee State Working Group Interoperable Communications Committee Statewide Communications Interoperability Plan Telecommunications Industry Association Telecommunications Systems Bulletin 700 IO Plan Document

77

78