Service Rules for the 698-746, 747-762 and 777-792 MHz Bands, Implementing a Nationwide, Broadband, Interoperable Public Safety Network in the 700 MHz Band

Federal RegisterMay 21, 2008

Ask Donna

What actually matters in this document.

Text

FEDERAL COMMUNICATIONS COMMISSION

47 CFR Parts 0, 1, 2, 27, 90

[WT Docket No. 06-150; PS Docket No. 06-229; FCC 08-128]

Service Rules for the 698-746, 747-762 and 777-792 MHz Bands, Implementing a Nationwide, Broadband, Interoperable Public Safety Network in the 700 MHz Band

AGENCY:

Federal Communications Commission.

ACTION:

Proposed rule.

SUMMARY:

In the

Second Further Notice of Proposed Rulemaking (Second FNPRM)

, the Commission seeks comment on clarifications or revisions to the rules governing the Public Safety Broadband Licensee and the Upper 700 MHz D Block licensee. The Commission seeks comment on whether to continue to require these licensees to enter into a 700 MHz Public/Private Partnership for the purpose of enabling the construction of a nationwide, interoperable broadband network, and if so, what clarifications or revisions to adopt to the rules governing the licensees and the 700 MHz Public/Private Partnership. Further, the Commission seeks comment on what rules to adopt if it determines that the public/private partnership obligation should not be retained. This

Second Further Notice

is another step in the Commission's ongoing efforts to develop a regulatory framework in which to meet current and future public safety communications needs.

DATES:

Written comments are due on or before June 20, 2008, and reply comments are due on or before July 7, 2008.

ADDRESSES:

You may submit comments, identified by WT Docket No. 06-150 and PS Docket No. 06-229, by any of the identified methods:

• Federal eRulemaking Portal:

http:// www.regulations.gov

. Follow the instructions for submitting comments.

• Federal Communications Commission's Web Site:

http:// www.fcc.gov/cgb/ecfs/

. Follow the instructions for submitting comments.

• Mail: Follow the instructions for paper filers below.

• People with Disabilities: Contact the Commission to request reasonable accommodations (accessible format documents, sign language interpreters, CART, etc.) by e-mail:

FCC504@fcc.gov

or phone: 202-418-0530 or TTY: 202-418-0432.

For detailed instructions for submitting comments and additional information on the rulemaking process, see the

SUPPLEMENTARY INFORMATION

section of this document.

FOR FURTHER INFORMATION CONTACT:

Peter Trachtenberg at (202) 418-7369, at

peter.trachtenberg@fcc.gov

, Spectrum and Competition Policy Division, Wireless Telecommunications Bureau; Jeffrey S. Cohen at (202) 418-0799,

jeff.cohen@fcc.gov

, Public Safety and Homeland Security Bureau.

SUPPLEMENTARY INFORMATION:

This is a summary of the Commission's

Second Further Notice of Proposed Rulemaking

, WT Docket No. 06-150, PS Docket No. 06-229, adopted on May 14, 2008 and released May 14, 2008. The full text of

the Second Further Notice of Proposed Rulemaking

is available for public inspection on the Commission's Internet site at

http://www.fcc.gov

. It is also available for inspection and copying during regular business hours in the FCC Reference Center (Room CY-A257), 445 12th Street, SW., Washington, DC 20554. The full text of this document also may be purchased from the Commission's duplication contractor, Best Copy and Printing Inc., Portals II, 445 12th St., SW., Room CY-B402, Washington, DC 20554; telephone (202) 488-5300; fax (202) 488-5563; e-mail

FCC@BCPIWEB.COM

.

Synopsis

In the

Second Report and Order,

72 FR 48814, August 24, 2007, the Commission adopted rules for the establishment of a mandatory public/private partnership (the 700 MHz Public/Private Partnership) in the upper portions of the 698-806 MHz band (700 MHz Band) as the means for promoting the rapid construction and deployment of a nationwide, interoperable broadband public safety network that would serve public safety and homeland security needs. Specifically, the Commission required that the winning bidder of the commercial license in the Upper 700 MHz D Block (758-763/788-793 MHz) (D Block) enter into the 700 MHz Public/Private Partnership with the nationwide licensee of the public safety broadband spectrum (763-768/793-798 MHz) (Public Safety Broadband Licensee) to enable construction of this interoperable broadband network, which would span both the commercial D Block and public safety spectrum. In the recently concluded auction of commercial 700 MHz licenses, bidding for the D Block license did not meet the applicable reserve price of $1.33 billion and, pursuant to the Commission's rules, there was no winning bid for that license. Accordingly, in this Second FNPRM, the Commission revisits its decisions concerning the 700 MHz Public/Private Partnership—considering revisions to this partnership as well as alternative rules the Commission should adopt in the event the D Block licensee is no longer required to enter into a mandatory public/private partnership.

First, the Commission considers whether to adopt clarifications and revisions to the public safety component of the 700 MHz Public/Private Partnership to better promote its public interest goals. In particular, the Commission seeks comment regarding what entities are eligible under Section 337 of the Communications Act as amended and the Commission's rules to use the public safety spectrum in the shared wireless broadband network as public safety users rather than as commercial users, and whether such users should be required to use or subscribe to the shared network. The Commission also seeks comment on possible clarifications of or changes to the rules governing the structure and criteria of the Public Safety Broadband Licensee, whether to clarify further the requirement that the Public Safety Broadband Licensee must be a non-profit organization, what measures to adopt to provide adequate Commission oversight, whether providing a nationwide, interoperable broadband network might be more effectively and efficiently accomplished by allowing State governments to assume responsibility for coordinating the participation of the public safety providers in their jurisdictions, and whether the Commission should rescind the current Public Safety Broadband License and seek new applicants.

In addition, the Commission seeks comment on whether it remains in the public interest to require a public/private partnership between the nationwide D Block licensee and the Public Safety Broadband Licensee for the purpose of creating a nationwide, interoperable broadband network for both commercial and public safety network services. To ensure a thorough consideration of the Commission's options in the event that it does continue to require a public/private partnership between these licensees, the Commission seeks comment broadly on possible revisions to the 700 MHz Public/Private Partnership, including revisions regarding the respective obligations of the D Block licensee and the Public Safety Broadband Licensee. In particular, it seeks comment on the following issues: (1) The technical requirements of the shared wireless broadband network to be constructed by the D Block licensee, (2) the rules governing public safety priority access

to the D Block spectrum during emergencies, and whether the Commission should continue to require the D Block licensee to provide such access; (3) the D Block performance requirements and license term; (4) the respective roles and responsibilities of the D Block licensee and Public Safety Broadband Licensee in connection with the 700 MHz Public/Private Partnership and the shared wireless broadband network; (5) the various fees associated with the shared network; (6) the process for negotiating and establishing the Network Sharing Agreement, including the consequences of a failure to reach agreement; (7) certain auction-related issues, including whether to restrict who may participate in the new auction of the D Block license, whether and how to set any reserve price for such an auction, whether to adopt an exception to the impermissible material relationship rule for the determination of designated entity eligibility with respect to arrangements for the lease or resale (including wholesale) of the spectrum capacity of the D Block license, and whether the Commission should modify the auction default payment rules with respect to the D Block winning bidder; and (8) rules governing the relocation of the public safety narrowband operations. In this

Second FNPRM,

the Commission includes an appendix that serves as a possible framework for establishing the technical requirements for the 700 MHz Public/Private Partnership shared wireless broadband network. This appendix is intended to solicit detailed comment and result in a final set of technical requirements that will provide greater certainty for bidders for the D Block license while ensuring that the network meets public safety's needs; the appendix is not intended to prejudge any of the issues identified for comment in the

Second FNPRM.

Finally, the Commission seeks comment on any other revisions or clarifications that may be appropriate with regard to the 700 MHz Public/Private Partnership, including whether to license the D Block and public safety broadband spectrum on a nationwide or adopt a regional geographic service area basis such as Regional Economic Area Grouping (REAG).

In addition to considering possible revisions to the 700 MHz Public/Private Partnership, the Commission considers its options if the D Block is licensed without this 700 MHz Public/Private Partnership condition. For any circumstances where the Commission determines that the 700 MHz Public/Private Partnership condition on the D Block should not be retained, it seeks comment on revisions to the rules that would be appropriate with respect to the D Block license as well as revisions with regard to the Public Safety Broadband License that would ensure the development and deployment of a nationwide interoperable broadband network for public safety users. With respect to the D Block, the Commission seeks comment in particular on the service rules that should apply in this event, including the appropriate geographic license area, performance requirements, technical limits, and whether to adopt alternate conditions, such as an open access or wholesale requirement. The Commission seeks comments on the appropriate revisions to the rules that would still enable the Commission to achieve the goal of a nationwide, interoperable public safety broadband network. For example, the Commission seeks comment on: (1) Whether the Commission should adopt, possibly with modifications, the approach proposed in the

Public Safety Ninth Notice of Proposed Rulemaking,

72 FR 1201, January 10, 2007, which, among other aspects, would allow commercial providers to enter into voluntary arrangements with the Public Safety Broadband Licensee to provide public safety services through access to their commercial network infrastructure and/or through new network build-out in exchange for preemptible access to public safety spectrum; (2) whether to require the adoption of a common broadband standard, and permit regional, state and local entities to build public safety broadband networks built to that standard, either through a spectrum lease with the Public Safety Broadband Licensee or by reassigning the public safety broadband spectrum for regional, state, or local licensing; (3) whether the Commission, in the absence of the public/private partnership, should continue to obligate the D Block winner to fund the relocation of those public safety narrowband systems operating in the lower portion of the public safety spectrum; and (4) whether, in the absence of a public safety/private partnership, there are viable options for funding network construction.

The Commission initiates this

Second FNPRM

with the following principles and goals: (1) To identify concerns in the existing structure of the 700 MHz Public/Private Partnership to inform the Commission's decision making going forward; (2) to promote wireless innovation and broadband network penetration while meeting the communications needs of the first responder community in a commercially viable manner; (3) to facilitate public safety access to a nationwide, interoperable broadband network in a timely manner; (4) to identify funding opportunities for the public safety community to realize the promise of a broadband communications infrastructure with a nationwide level of interoperability; and (5) to maximize the commercial and public safety benefits of this unique piece of 700 MHz spectrum. The Commission invites comment broadly on these principles and goals, as well as the other subjects discussed. While this

Second FNPRM

raises a number of specific questions, it should not be seen as providing any limitation on the issues that the Commission seeks comment upon. The Commission is interested in any and all perspectives from interested parties on how it can develop rules and procedures that will achieve the multiple goals enumerated above.

Discussion

I. Introduction

1. In the

Second Report and Order,

we adopted rules for the establishment of a mandatory public/private partnership (“the 700 MHz Public/Private Partnership”) in the upper portions of the 698-806 MHz band (“700 MHz Band”) as the means for promoting the rapid construction and deployment of a nationwide, interoperable broadband public safety network that would serve public safety and homeland security needs.

1

Specifically, we required that the winning bidder of the commercial license in the Upper 700 MHz D Block (758-763/788-793 MHz) (“D Block”) enter into the 700 MHz Public/Private Partnership with the nationwide licensee of the public safety broadband spectrum (763-768/793-798 MHz)

(“Public Safety Broadband Licensee”) to enable construction of this interoperable broadband network, which would span both the commercial D Block and public safety spectrum. As essential components of this partnership, the D Block licensee would be chiefly responsible for the construction and operation of a state-of-the-art shared wireless broadband network that would be used by public safety users as well as commercial users. In exchange for taking on these responsibilities, the D Block licensee would gain access to the public safety broadband spectrum for use by its commercial customers on a secondary preemptible basis. In turn, public safety users, through the Public Safety Broadband Licensee, would benefit from obtaining access to a state-of-the-art broadband network on their 700 MHz spectrum that would incorporate their unique requirements, which would not otherwise be possible given the limited availability of public funding.

2

In Auction 73, the recently concluded auction of commercial 700 MHz licenses, bidding for the D Block license did not meet the applicable reserve price of $1.33 billion and, pursuant to the Commission's rules, there was no winning bid for that license.

3

In the

D Block Post-Auction Order

released shortly after the close of Auction 73, we determined not to re-offer the D Block license immediately in order to “provide additional time to consider options with respect to the D Block spectrum.”

4

Accordingly, in this Second FNPRM of Proposed Rulemaking (“Second FNPRM”), we revisit our decisions concerning the 700 MHz Public/Private Partnership—considering revisions to this partnership as well as alternative rules we should adopt in the event the D Block licensee is no longer required to enter into a mandatory public/private partnership.

1

See Service Rules for the 698-746, 747-762 and 777-792 MHz Bands, WT Docket No. 06-150, Revision of the Commission's Rules to Ensure Compatibility with Enhanced 911 Emergency Calling Systems, CC Docket No. 94-102, Section 68.4(a) of the Commission's Rules Governing Hearing Aid-Compatible Telephones, WT Docket No. 01-309, Biennial Regulatory Review—Amendment of Parts 1, 22, 24, 27, and 90 to Streamline and Harmonize Various Rules Affecting Wireless Radio Services, WT Docket 03-264, Former Nextel Communications, Inc. Upper 700 MHz Guard Band Licenses and Revisions to Part 27 of the Commission's Rules, WT Docket No. 06-169, Implementing a Nationwide, Broadband, Interoperable Public Safety Network in the 700 MHz Band, PS Docket No. 06-229, Development of Operational, Technical and Spectrum Requirements for Meeting Federal, State and Local Public Safety Communications Requirements Through the Year 2010, WT Docket No. 96-86, Declaratory Ruling on Reporting Requirement under Commission's Part 1 Anti-Collusion Rule, WT Docket No. 07-166,

Second Report and Order,

22 FCC Rcd 15289 (2007) (

Second Report and Order

)

recon. pending.

2

Id.

at 15295 para. 13, 15431 para. 396.

3

The auction of these 700 MHz licenses, designated Auction 73, began on January 24, 2008, and concluded March 18, 2008.

See http://wireless.fcc.gov/auctions/default.htm?job=auction_summary&id=73.

4

Auction of the D Block License in the 758-763 and 788-793 MHz Bands, AU Docket No. 07-157,

Order,

FCC 08-91, para. 3 (rel. Mar. 20, 2008) (

D Block Post-Auction Order

). In the

Second Report and Order,

the Commission decided that, if the reserve price for the D Block was not satisfied in the initial auction results, the Commission might either re-offer the license on the same terms in an immediate second auction, or re-evaluate the license conditions.

See Second Report and Order,

22 FCC Rcd at 15404 para. 314.

2. First, we consider clarifications and revisions to the public safety component of the 700 MHz Public/Private Partnership that would better promote our public interest goals.

5

More specifically, we seek comment on whether, under Section 337 of the Communications Act of 1934, as amended (“Act”),

6

and Section 90.523 of the Commission's rules,

7

only entities that are providing public safety services, as defined in the Act, are eligible to use the public safety spectrum portion of the shared network established under the 700 MHz Public/Private Partnership, and whether such entities should be required to subscribe to the network. We also seek comment on whether to clarify the requirement that the Public Safety Broadband Licensee be a non-profit organization and specify that entities associated with the public safety component of the 700 MHz Public/Private Partnership, apart from outside advisors or counsel with no debt or equity relationship to the Public Safety Broadband Licensee, may not be for-profit entities. We seek comment on these and other clarifications or changes to the structure of the Public Safety Broadband Licensee and the criteria adopted in the

Second Report and Order.

5

We use the term “700 MHz Public/Private Partnership” to refer specifically to a mandatory public/private partnership between the D Block licensee and the Public Safety Broadband Licensee, along the general lines initially set forth in the

Second Report and Order.

6

47 U.S.C. 337.

7

47 CFR 90.523.

3. In addition, we seek comment on possible modifications to the various rules governing the D Block licensee and the Public Safety Broadband Licensee within the framework of the 700 MHz Public/Private Partnership (as revised or clarified). First, we seek comment on whether it remains in the public interest to require a public/private partnership between the nationwide D Block licensee and the Public Safety Broadband Licensee for the purpose of creating a nationwide, interoperable broadband network for both commercial and public safety network services. Next, to ensure a thorough consideration of the Commission's options in the event that we do continue to require a public/private partnership between these licensees, we seek comment on a broad set of possible revisions to the 700 MHz Public/Private Partnership, including revisions regarding the respective obligations of the D Block licensee and the Public Safety Broadband Licensee. In particular, we seek comment on the following issues: (1) The technical requirements of the shared wireless broadband network to be constructed by the D Block licensee, (2) the rules governing public safety priority access to the D Block spectrum during emergencies; (3) the D Block performance requirements and license term; (4) the respective roles and responsibilities of the D Block licensee and Public Safety Broadband Licensee in connection with the 700 MHz Public/Private Partnership and the shared wireless broadband network, including whether the Public Safety Broadband Licensee may assume responsibilities akin to a “mobile virtual network operator”

8

; (5) the various fees associated with the shared network; (6) the process for negotiating and establishing the Network Sharing Agreement, including the consequences of a failure to reach agreement; (7) certain auction-related issues, including whether to restrict who may participate in the new auction of the D Block license, how to determine any reserve price for such an auction, whether to adopt an exception to the impermissible material relationship rule for the determination of designated entity eligibility with respect to arrangements for the lease or resale (including wholesale) of the spectrum capacity of the D Block license, and whether we should modify the auction default payment rules with respect to the D Block winning bidder; and (8) relocation of the public safety narrowband operations. Finally, we seek comment on other revisions or clarifications that may be appropriate with regard to the 700 MHz Public/Private Partnership, including whether to license the D Block and public safety broadband spectrum on a nationwide or adopt a regional geographic service area basis such as Regional Economic Area Grouping (REAG).

9

8

A mobile virtual network operator is a non-facility-based mobile service provider that resells service to the public for profit.

See

Implementation of Section 6002(B) of the Omnibus Budget Reconciliation Act of 1993, WT Docket No. 05-71,

Tenth Report,

20 FCC Rcd 15908, 15920 para. 27 (2005).

9

As licensing the D Block on a REAG basis would result in issuing multiple D Block licenses, references herein to “the” D Block license and licensee should be understood to incorporate reference to any of multiple D Block licenses or licensees and vice versa, as appropriate.

4. In addition to considering possible revisions to the 700 MHz Public/Private Partnership, we consider our options if the D Block is licensed without this 700 MHz Public/Private Partnership condition. We note that there are several circumstances where such options might be relevant. First, we might determine that we should not re-auction the D Block with the 700 MHz Public/Private Partnership condition, and instead immediately conduct an auction to license the D Block without such a

condition. In addition, we might conclude that, even if we should retain the 700 MHz Public/Private Partnership condition in the next D Block auction, the condition should be removed if the next D Block auction fails to produce a winning bidder, or the winning bidder defaults or fails to negotiate a successful Network Sharing Agreement with the Public Safety Broadband Licensee. Therefore, for any circumstances where we determine that the 700 MHz Public/Private Partnership condition on the D Block should not be retained, we seek comment on revisions to the rules that would be appropriate with respect to the D Block license as well as revisions with regard to the Public Safety Broadband License that would ensure the development and deployment of a nationwide interoperable broadband network for public safety users.

5. Finally, we note that, in adopting the

Second Report and Order,

we took an innovative approach to addressing a vitally important problem: Promoting interoperability, on a nationwide basis, for public safety communications. We intended that the mandatory public/private partnership model between two nationwide licensees—the commercial D Block licensee and the non-profit Public Safety Broadband Licensee—would facilitate access for public safety to a robust, advanced communications infrastructure and produce economies of scale inherent in a nationwide footprint. Importantly, we also found that this approach was the best means available to address the issue of funding for construction of a public safety communications infrastructure, which has proven a significant impediment to date. At the same time, however, we anticipated that the partnership would involve a balance between the commercial partner's obligation to construct a shared network infrastructure and the commercial partner's secondary access to the 700 MHz public safety broadband spectrum. By partnering these two spectrum assets, we intended to promote spectrum efficiency and innovation. Thus, we aimed to have the 700 MHz Public/Private Partnership between the D Block licensee and the Public Safety Broadband Licensee be complementary, and we designed this framework to strike the appropriate balance such that the maximum benefits accrued to both parties.

6. Although the initial sale of the D Block license did not result in a winning bidder, these goals remain. In reexamining our approach to the D Block following Auction 73, we continue to proceed with these objectives in mind. Accordingly, we initiate this Second FNPRM with the following principles and goals:

• To identify concerns in the existing structure of the 700 MHz Public/Private Partnership to inform our decision making going forward;

• To promote wireless innovation and broadband network penetration while meeting the communications needs of the first responder community in a commercially viable manner;

• To facilitate public safety access to a nationwide, interoperable broadband network in a timely manner;

• To identify funding opportunities for the public safety community to realize the promise of a broadband communications infrastructure with a nationwide level of interoperability; and

• To maximize the commercial and public safety benefits of this unique piece of 700 MHz spectrum.

7. We invite comment broadly on these principles and goals, as well as the specific subjects discussed herein. While today's item raises a number of specific questions, it should not be seen as providing any limitation on the public safety issues that we seek comment upon. We are interested in any and all perspectives from interested parties on how the Commission can develop rules and procedures that will achieve the multiple goals enumerated above. Finally, before ultimately adopting final rules in response to this Second FNPRM, we plan to present for public comment, in a subsequent FNPRM of Proposed Rulemaking, a detailed proposal regarding the specific proposed rules.

10

10

In this subsequent Further Notice of Proposed Rulemaking, we plan to seek comment on an expedited basis, with comments due fourteen days after publication in the

Federal Register

, and reply comments due twenty-one days after such publication.

II. Background

8. In the

Second Report and Order,

released August 10, 2007, we adopted a band plan and service rules affecting the upper portions of the 700 MHz Band in order to promote the creation of a nationwide, interoperable broadband public safety network through the establishment of the 700 MHz Public/Private Partnership. Specifically, with regard to the public safety spectrum in the 700 MHz Band, we designated the lower half of this spectrum (the 763-768 MHz and 793-798 MHz bands) for public safety broadband communications, and we consolidated existing narrowband allocations to the upper half of the spectrum (the 769-775 MHz and 799-805 MHz bands).

11

We also created a single nationwide license for the public safety broadband spectrum, and we specified the criteria, selection process, and responsibilities of the licensee assigned this spectrum, the Public Safety Broadband Licensee.

12

We required, for example, that no commercial interest may be held in the Public Safety Broadband Licensee, that no commercial interest may participate in the management of the licensee, and that the licensee must be a non-profit organization.

13

With regard to the commercial spectrum in the 700 MHz Band, we designated one block—the D Block (the 758-763 MHz and 788-793 MHz bands) located adjacent to the public safety broadband spectrum block—for use as part of the 700 MHz Public/Private Partnership. As set forth in the

Second Report and Order,

we required the D Block licensee, working with the Public Safety Broadband Licensee in a public/private partnership, to construct and operate a nationwide network shared by both commercial and public safety users.

14

11

See Second Report and Order,

22 FCC Rcd at 15406. We also created an internal guard band in the 768-769 MHz and 798-799 MHz bands located between the broadband and narrowband allocations.

Id.

12

See id.

13

See id.

at 15421.

14

Id.

at 15428.

9.

The 700 MHz Public/Private Partnership.

In the

Second Report and Order,

we determined that promoting commercial investment in the build-out of a shared network infrastructure for both commercial and public safety users through the 700 MHz Public/Private Partnership would address “the most significant obstacle to constructing a public safety network—the limited availability of public funding.”

15

We concluded that providing for a shared infrastructure using the D Block and the public safety broadband spectrum would help achieve significant cost efficiencies. We noted that this would allow public safety agencies “to take advantage of commercial, off-the-shelf technology and otherwise benefit from commercial carriers' investments in research and development of advanced wireless technologies.”

16

We also stated that this approach could benefit the public safety community by providing it with access to an additional 10 megahertz of broadband spectrum during emergencies, when it is needed most. Most importantly, it was our view that this particular public/private partnership approach would provide all of these benefits on a nationwide basis and thus provide the most practical means of speeding deployment of a

nationwide, interoperable, broadband network for public safety service that is designed to meet their needs in times of crisis. At the same time, we pointed out that the 700 MHz Public/Private Partnership would provide the D Block licensee with rights to operate commercial services in the 10 megahertz of public safety broadband spectrum on a secondary, preemptible basis, which would both help to defray the costs of build-out and ensure that the spectrum is used efficiently.

17

15

Id.

at 15431.

16

Id.

(citing Sprint Nextel

700 MHz Further Notice

Comments at 7-8).

17

Id.

10. We established various features of the 700 MHz Public/Private Partnership. First, we set forth the essential components of this partnership.

18

In particular, we specified certain parameters for the shared wireless broadband network, including features relating to the technology platform, signal coverage, robustness and reliability, capacity, security, operational capabilities and control, and certain equipment specifications.

19

With regard to the spectrum shared by the common network, we required that the Public Safety Broadband Licensee lease the public safety broadband spectrum for commercial use by the D Block licensee on a secondary, preemptible basis and provided that the public safety entities would have priority access to the D Block spectrum during emergencies.

20

We also established certain minimal performance requirements relating to construction and build-out of the shared 700 MHz Public/Private Partnership network.

21

18

Id.

at 15432.

19

Id.

at 15432, 15433-44.

20

Id.

at 15432, 15434-43.

21

Id.

at 15432, 15443-46.

11. Next, we established that the terms of the 700 MHz Public/Private Partnership would be governed both by Commission rules and by a Network Sharing Agreement (“NSA”) to be negotiated by the winning bidder for the D Block license and the Public Safety Broadband Licensee.

22

Throughout the

Second Report and Order

we identified certain elements that the parties were required to address in the NSA. These included, for instance, the details of certain mandatory network specifications established in the order and a detailed build-out schedule as jointly agreed upon by the Public Safety Broadband Licensee and the D Block licensee.

23

We also determined that the NSA should include, among other things, specification of all service fees that public safety entities would pay with respect to access and use of the shared network, both in terms of fees applicable for normal network service and fees for priority access to the D Block spectrum in an emergency.

24

22

Id.

at 15432, 15447-49.

23

Id.

at 15448-49.

24

Id.

at 15448-49.

12. We established rules governing the establishment of the NSA to ensure timely completion of the negotiations and to resolve any disputes that may arise.

25

Among other rules, we required the winning bidder of the D Block license and the Public Safety Broadband Licensee to negotiate in good faith, and we provided that the D Block license application would not be granted until the parties obtained Commission approval of the agreement, executed, and then filed the NSA with the Commission.

26

We also required the negotiations to begin by a date certain and conclude within six months. Further, we specified rules to govern in the event of a negotiation dispute. Specifically, we provided that if, at the end of the six month negotiation period, or on their own motion at any time, the Chiefs of the Public Safety and Homeland Security Bureau (“PSHSB”) and the Wireless Telecommunications Bureau (“WTB”) found that negotiations had reached an impasse, they could take a variety of actions to resolve any disputes, including but not limited to issuing a decision on the disputed issues and requiring the submission of a draft agreement consistent with their decision.

27

25

Id.

at 15448.

26

Id.

at 15448.

27

Id.

at 15465.

13.

Narrowband Relocation.

In the

Second Report and Order,

we found that, in order to maximize the benefits of the 700 MHz Public/Private Partnership to deploy a nationwide, interoperable broadband communications network, the current 700 MHz narrowband public safety operations must be consolidated and cleared no later than the DTV transition date.

28

To effectuate the consolidation of the narrowband channels, we required the D Block licensee to pay the costs of relocating narrowband radios to the newly consolidated portion of the band and capped the disbursement amount for such relocation costs at $10 million.

29

We also cautioned that any narrowband equipment deployed in the 764-770 MHz and 794-800 MHz bands (channels 63 and 68), or in the 775-776 MHz and 805-806 MHz bands (the upper one megahertz of channels 64 and 69), more than 30 days following the adoption date of the

Second Report and Order

would be ineligible for relocation funding.

30

In addition, we prohibited authorization of any new narrowband operations in that spectrum, as of 30 days following the adoption date of the

Second Report and Order.

31

28

Id.

at 15410.

29

Id.

at 15412.

30

Id.

at 15412.

31

Id.

14.

Rules for an Auction to License the D Block.

In addition to adopting service rules for the 700 MHz commercial spectrum, including the D Block, we also made several determinations regarding the auction of the 700 MHz commercial licenses. In particular, we concluded that block-specific aggregate reserve prices should be established for each commercial license block—the A, B, C, D, and E Blocks—to be auctioned in Auction 73, and directed WTB to adopt and publicly disclose those reserve prices prior to the auction, pursuant to its existing delegated authority and consistent with our directions.

32

For the D Block, we concluded that WTB should consider certain factors in setting the D Block reserve price, including the 700 MHz Public/Private Partnership conditions, which might suggest a reserve price of $1.33 billion. We provided that, in the event that bids for the D Block license did not meet the reserve price, we would leave open the possibility of offering the license on the same terms or re-evaluating the D Block license conditions.

33

32

See id.

at 15400.

33

See id.

at 15404.

15. In an effort to encourage the widest range of potentially qualified applicants to participate in bidding for the D Block license, in the

Second Report and Order,

we enabled eligible applicants for this license to seek designated entity bidding credits for small businesses as a means to create incentives for investors to provide innovative small businesses with the capital necessary to compete for the D Block license at auction.

34

We subsequently decided to waive, on our own motion, the application of our “impermissible material relationship” rule

35

for purposes of determining an applicant's or licensee's designated entity eligibility solely with respect to arrangements for lease or resale (including wholesale) of the spectrum capacity of the D Block license.

36

Given the unique characteristics of the regulations governing the D Block

license, we concluded that a waiver of the impermissible material relationship rule served the public interest.

37

34

47 CFR 27.502.

35

47 CFR 1.2110(b)(3)(iv)(A).

36

See generally

Waiver of Section 1.2110(b)(3)(iv)(A) of the Commission's Rules for the Upper 700 MHz Band D Block License,

Order,

22 FCC Rcd 20354 (2007) (

D Block Waiver Order

)

recon. pending.

37

Id.

at 20354.

16.

Petitions for Reconsideration.

Ten parties filed petitions for reconsideration seeking review of various aspects of the

Second Report and Order.

38

Three of the petitions sought reconsideration of the rules governing the 700 MHz Public/Private Partnership specifically,

39

and two petitioners sought reconsideration of the aggregate reserve prices set for the commercial license blocks, including the D Block.

40

These petitioners presented related arguments in the pre-auction process.

41

After considering the arguments, WTB established reserve prices consistent with the direction of the

Second Report and Order.

42

Two other parties filed petitions seeking reconsideration of some or all of the requirements regarding public safety narrowband relocation, and also filed requests for waiver of some of these requirements.

43

All of the petitions remain pending.

38

AT&T Inc. Petition for Reconsideration and Clarification, WT Docket No. 06-150; PS Docket No. 06-229 (filed Sept. 24, 2007); Blooston Rural Carriers Petition for Partial Reconsideration and/or Clarification (filed Sept. 24, 2007); Petition for Reconsideration of the Ad Hoc Public Interest Spectrum Coalition (filed Sept. 24, 2007); Cyren Call Communications Corporation Petition for Reconsideration and for Clarification (filed Sept. 24, 2007); Frontline Wireless, LLC Petition for Reconsideration (filed Sept. 24, 2007); Pierce Transit Petition for Reconsideration (filed Sept. 24, 2007); Rural Telecommunications Group, Inc. Petition for Reconsideration (filed Sept. 24, 2007); Commonwealth of Virginia Petition for Reconsideration (filed Sept. 24, 2007); NTCH, Inc. Petition for Partial Reconsideration (filed Sept. 21, 2007); MetroPCS Communications, Inc. Petition for Clarification and Reconsideration (filed Sept. 20, 2007).

39

See

AT&T Petition for Reconsideration; Cyren Call Petition for Reconsideration; Frontline Petition for Reconsideration. The Frontline September 20, 2007 Request also seeks changes to the rules governing the 700 MHz Public/Private Partnership.

See

Request to Further Safeguard Public Safety Service by Frontline Wireless, WT Docket No. 06-150 (filed Sept. 20, 2007) (Frontline September 20, 2007 Request).

40

See

Frontline Petition for Reconsideration; MetroPCS Petition for Reconsideration.

41

See

Auction of 700 MHz Band Licenses Scheduled for January 24, 2008; Notice and Filing Requirements, Minimum Opening Bids, and other Procedures for Auctions 73 and 76,

Public Notice,

22 FCC Rcd 18141, 18194-95 (2007) (

Auction 73/76 Procedures Public Notice

).

42

See id.

at 18193-96.

43

See

Commonwealth of Virginia Petitions for Reconsideration; Pierce Transit Petition for Reconsideration. Pierce Transit and Virginia have been granted limited waiver relief.

See

Implementation of a Nationwide, Broadband, Interoperable Public Safety Network in the 700 MHz Band; Development of Operational, Technical and Spectrum Requirements for Meeting Federal, State and Local Public Safety Communications Requirements Through the Year 2010, PS Docket No. 06-229, WT Docket No. 96-86,

Order,

22 FCC Rcd 20290 (2007); Implementing a Nationwide, Broadband, Interoperable Public Safety Network in the 700 MHz Band; Development of Operational, Technical and Spectrum Requirements for Meeting Federal, State and Local Public Safety Communications Requirements Through the Year 2010; Request for Waiver of Pierce Transit, PS Docket No. 06-229, WT Docket No. 96-86,

Order,

23 FCC Rcd 433 (PSHSB 2008).

17.

Auction 73.

The auction of 700 MHz Band licenses, designated Auction 73, commenced on January 24, 2008, and closed on March 18, 2008.

44

While the bids for licenses associated with the other 700 MHz Band blocks (the A, B, C, and E Blocks) exceeded the applicable reserve prices, bids for the D Block license did not meet the reserve price and there was no winning bid for that license.

45

44

See

http://wireless.fcc.gov/auctions/default.htm?job=auction_summary&id=73

.

45

See id.

;

see also

“Auction of 700 MHz Band Licenses Closes,”

Public Notice,

DA 08-595 (rel. Mar. 20, 2008) (

700 MHz Auction Closing Public Notice

).

18.

D Block Post-Auction Order.

On March 20, 2008, we determined that we would not proceed immediately to re-auction the D Block license.

46

We made this decision in order to provide additional time to consider our various options with respect to the D Block spectrum.

47

46

See D Block Post-Auction Order

at para. 5.

47

See id.

19.

Inspector General's Report.

On April 25, 2008, the Office of Inspector General (OIG) issued a report on its investigation relating to allegations relating to whether certain statements made by an advisor to the Public Safety Broadband Licensee to potential bidders for the D Block license in Auction 73, particularly those regarding the spectrum lease payments that the Public Safety Broadband Licensee would request from the D Block licensee for use of public safety spectrum, had the effect of deterring various companies from bidding on the D Block.

48

The OIG determined that the statements in question were “not the only factor in the companies' decision not to bid on the D Block.” Rather, it concluded that “the uncertainties and risks associated with the D Block, including, but not limited to, the negotiation framework with [the Public Safety Broadband Licensee], the potential for default payment if negotiations failed, and the costs of the build-out and the operations of the network, taken together, deterred each of the companies from bidding on the D Block.”

49

48

See Office of Inspector General Report,

from Kent R. Nilsson, Inspector General, to Chairman Kevin J. Martin (OIG rel. Apr. 25, 2008) (

OIG Report

).

49

OIG Report

at 2.

III. Discussion

20. In this Second FNPRM, we revisit our decisions concerning the public safety broadband spectrum, the 700 MHz Public/Private Partnership, and the shared wireless broadband network it is intended to create, as we move toward a new auction to license the D Block spectrum in the near future.

50

50

As noted above, before ultimately adopting final rules in response to this Second FNPRM, we plan to present for public comment, in a subsequent FNPRM of Proposed Rulemaking, a detailed proposal regarding the specific proposed rules.

21. First, in reevaluating the 700 MHz Public/Private Partnership in light of the results of Auction 73, we find it appropriate to consider clarifications and revisions to the public safety component of the partnership that would better promote our public interest goals. More specifically, in section A, we seek comment on our proposed clarifications regarding the entities that are eligible to use the public safety spectrum in the shared wireless broadband network as public safety users rather than as commercial users. We also seek comment on possible clarifications of or changes to the rules governing the structure and criteria of the Public Safety Broadband Licensee,

51

including whether to clarify further the requirement that the Public Safety Broadband Licensee must be a non-profit organization.

51

See

47 U.S.C. 316 (permitting the Commission to modify any license if, in the judgment of the Commission, such action will promote the public interest, convenience, or necessity).

22. In section B, we seek comment on possible changes to the rules requiring and governing the 700 MHz Public/Private Partnership. As noted above, we seek comment on whether the 700 MHz Public/Private Partnership between the D Block licensee and the Public Safety Broadband Licensee, with appropriate revisions and clarifications, would best serve the public interest in ensuring the development of a nationwide, interoperable broadband network for public safety users. We therefore explore a variety of possible revisions to the 700 MHz Public/Private Partnership to provide greater assurance to potential bidders for the D Block license that the shared wireless broadband network will be commercially viable and to help ensure that this partnership will be successful in making a nationwide, interoperable, broadband network available to public safety users. We also seek comment on issues related to the negotiation of the Network Sharing Agreement. In addition, we request comment on select issues relating to auctioning the D Block license, including eligibility to participate in the

auction, a reserve price, and potential default payments. Finally, we seek comment on issues relating to narrowband relocation and on whether to continue to license the D Block on a nationwide basis or adopt a regional geographic service area basis such as REAGs.

23. Finally, in section C, we examine our options in the event we decide not to condition the D Block on the establishment of the 700 MHz Public/Private Partnership with the Public Safety Broadband Licensee, either immediately in the next auction or if the next auction fails to produce a winning bidder. First, we seek comment on various revisions that might be appropriate with respect to the D Block spectrum. Then we invite comment on what additional revisions might be appropriate with regard to the Public Safety Broadband License in order to ensure the development and deployment of a nationwide interoperable broadband network for public safety users.

A. The Public Safety Broadband License

1. Eligible Users of the Public Safety Spectrum in the Shared Network

24.

Background.

To meet anticipated public safety and homeland security needs, we proposed a comprehensive plan in the

Second Report and Order

to promote the rapid deployment of a nationwide, interoperable, broadband public safety network. This plan was based on taking “a centralized and national approach to maximize public safety access to interoperable, broadband spectrum in the 700 MHz Band.”

52

In particular, we required that a single, nationwide public safety broadband license be assigned to the Public Safety Broadband Licensee. That licensee would be responsible for negotiating a Network Sharing Agreement with the winning bidder of the D Block licensee, pursuant to which the D Block licensee would construct and operate a shared, nationwide 700 MHz interoperable broadband network that serves the public safety entities seeking access to the network, and the D Block licensee would, in turn, gain access to the 700 MHz public safety broadband spectrum for use by its commercial users on a secondary preemptible basis.

53

52

See Second Report and Order,

22 FCC Rcd at 15419.

53

See id.

at 15419.

25. The eligibility rules for the 700 MHz public safety band, including both the narrowband and broadband segments, are contained in Section 90.523 of our rules.

54

By linking eligibility to the provision of statutorily-defined “public safety services,” Section 90.523 attempts to ensure compliance with the statutory mandate of Section 337(a)(1) of the Communications Act, which requires the Commission to allocate 24 megahertz of spectrum between 746 MHz and 806 MHz for “public safety services.”

55

The statutory definition of “public safety services,” which is set forth in Section 337(f) of the Act, provides as follows:

54

47 CFR 90.523.

55

47 U.S.C. 337(a)(1).

(f) Definitions

For purposes of this section:

(1) Public safety services

The term “public safety services” means services—

(A) The sole or principal purpose of which is to protect the safety of life, health, or property;

(B) That are provided—

(i) By State or local government entities; or

(ii) By nongovernmental organizations that are authorized by a governmental entity whose primary mission is the provision of such services; and

(C) That are not made commercially available to the public by the provider.

56

56

47 U.S.C. 337(f).

26. The eligibility rules of Section 90.523 that apply to the narrowband licensees of the 700 MHz public safety band limit operations to the provision of public safety services, as defined in Section 337(f)(1). Thus, all such licensees are either state or local governmental entities

57

or authorized non-governmental organizations (NGOs),

58

which provide services that are not made commercially available to the public and are for the sole or principal purpose of protecting the safety of life, health, or property.

59

57

See

47 CFR 90.523(a).

58

See

47 CFR 90.523(b).

59

See

47 CFR 90.523(a)-(d).

27. With respect to the broadband licensee—

i.e.

, the Public Safety Broadband Licensee—the Commission crafted eligibility requirements that were also intended to limit operations to the statutorily defined public safety services in order to ensure that the band remained allocated to such services, as required by Section 337(a)(1), and to focus the Public Safety Broadband Licensee exclusively upon the needs of public safety entities that stand to benefit from the interoperable broadband network.

60

Specifically, we required that the Public Safety Broadband Licensee satisfy the following eligibility criteria: (1) No commercial interest may be held in this licensee, and no commercial interest may participate in the management of the licensee, (2) the licensee must be a non-profit organization, (3) the licensee must be as broadly representative of the public safety radio user community as possible, including the various levels (

e.g.

, state, local, county) and types (

e.g.

, police, fire, rescue) of public safety entities, and (4) to ensure that the Public Safety Broadband Licensee is qualified to provide public safety services, an organization applying for the Public Safety Broadband License was required to submit written certifications from a total of at least ten geographically diverse state and local governmental entities, with at least one certification from a state government entity and one from a local government entity.

61

The written certifications from these state and local governmental entities were required to verify that: (1) They have authorized the applicant to use spectrum at 763-768 MHz and 793-798 MHz to provide the authorizing entity with public safety services; and (2) the authorizing entities' primary mission is the provision of public safety services.

62

60

Second Report and Order,

22 FCC Rcd at 15421.

61

See

47 CFR 90.523(e).

62

See

47 CFR 90.523(e)(i), (ii).

28.

Discussion.

As a preliminary matter, our review of the eligibility provisions that apply to the narrowband licensees and those that apply to the Public Safety Broadband Licensee have led us to identify two elements of the statutory definition of “public safety services” that the rules do not appear to apply explicitly enough to the Public Safety Broadband Licensee: (a) The Section 337(f)(1)(A) element that requires the “sole or principal purpose [of the services to be for the] protect[ion of] the safety of life, health, or property,” and (2) the Section 337(f)(1)C) element that bars such services from being “made commercially available to the public by the provider.”

63

In addition, there is some degree of ambiguity as to the applicability of the narrowband eligibility provisions in Sections 90.953(a)-(d) to the Public Safety Broadband Licensee. Accordingly, we seek comment on whether to make minor amendments to Section 90.523 to (a) clarify that the services provided by the Public Safety Broadband Licensee must conform to all the elements of the Section 337(f)(1) definition of “public safety services,” and (b) clearly delineate the differences and overlap in the respective eligibility requirements of

the narrowband licensees and the Public Safety Broadband Licensee.

63

47 U.S.C. 337(f)(1)(A), (C).

29. As discussed in more detail below, it would appear that, under Section 337 of the Act and in furtherance of the policies that have led to the creation of the Public Safety Broadband Licensee, the eligible users of the public safety broadband network that are represented by the Public Safety Broadband Licensee should be restricted to entities that would be eligible to hold licenses under Section 90.523. Thus, only entities providing public safety services, as defined in the Act, would be eligible to use the public safety spectrum of the shared network of the 700 MHz Public/Private Partnership on a priority basis, pursuant to the representation of the Public Safety Broadband Licensee. Accordingly, we also seek comment on whether all other users of the shared network, including critical infrastructure users, should consequently be treated as commercial users who would obtain access to spectrum only through commercial services provided solely by the D Block licensee.

30.

Eligible Users of the Public Safety Broadband Network.

As the licensee of the broadband portion of spectrum within the 700 MHz public safety band, the Public Safety Broadband Licensee occupies a somewhat unique position insofar as it will not use its licensed spectrum to serve its own communications needs. Rather, the Public Safety Broadband Licensee will ensure the provision of public safety service by providing spectrum access to others via the nationwide shared public/private network.

64

Thus, the question of whether the Public Safety Broadband Licensee's service qualifies as a “public safety service” under Section 337(f)(1) will turn (in part) on the nature of the spectrum use by the entities that it permits to gain access to the network. To the extent that these entities are public safety entities that use this access to provide themselves with communications services in furtherance of their mission to protect the safety of life, health or property, the Public Safety Broadband Licensee's services related to the public safety broadband spectrum would fall well within the Section 337(f)(1) definition of “public safety services” and would comport with the Commission's obligation under Section 337(a)(1) to allocate a certain amount of spectrum to such services.

64

See

Second Report and Order, 22 FCC Rcd at 15426.

31. We note that, pursuant to the statutory definition, a service can still be considered a “public safety service” even if its purpose is not solely for protecting the safety of life, health or property, so long as this remains its “principal” purpose.

65

Accordingly, the service provided by the Public Safety Broadband Licensee—providing public safety entities access to the spectrum for safety-of-life/health/property communications operations—could conceivably include the provision of spectrum access to public safety entities for uses that do not principally involve the protection of life, health or property, so long as it can be said that the principal purpose of the Public Safety Broadband Licensee's services is to protect the safety of life, health or property.

65

See

47 U.S.C. 337(f)(1)(A).

32. Taken to an extreme, this reasoning could even permit the Public Safety Broadband Licensee to provide spectrum access to small numbers of entities with no connection to public safety under the rationale that the bulk of the Public Safety Broadband Licensee's services would remain that of providing the public safety entities access to spectrum for use in safeguarding life, health or property. Moreover, the Public Safety Broadband Licensee could arguably leave entire pockets within its nationwide service area served only by such non-public safety entities, based on this same rationale that the small amount of non-public safety use—relative to the nature of the overall use across the country—does not alter the fact that the principal purpose of the service remains public safety. Such a result appears patently inconsistent with the spirit of Section 337(f)(1)(A), and we seek comment on whether, or to what degree, the Public Safety Broadband Licensee would be statutorily precluded by that subsection from representing and allowing any entity to use the network for services that are not principally for public safety purposes. We also seek comment on whether there are other grounds—specifically, the authorization requirement of Section 337(f)(1)(B)(ii) and policy reasons—for prohibiting the Public Safety Broadband Licensee from providing network access to non-public safety entities or from permitting public safety entities that it represents to use the network for services that do not have as their principal purpose the protection of the safety of life, heath or property. With respect to Section 337(f)(1)(B)(ii), we observe that, in order for the Public Safety Broadband Licensee's services to meet the public safety services definition, the Public Safety Broadband Licensee, as a nongovernmental organization, must receive authorization from “a governmental entity whose primary mission is the provision of [public safety] services.” We believe it unlikely that the intended scope of the authorization from such governmental entity or entities would include providing spectrum access, even on an occasional or limited basis, to entities that provide no public safety services.

66

On the policy front, the finite amount of spectrum available to the public safety community—particularly for interoperability purposes—strongly argues against any provision of spectrum access by the Public Safety Broadband Licensee to entities the sole or principal purpose of which is not the protection of the safety of life, health, or property. For these reasons, we seek comment on whether the public interest would be served by prohibiting the Public Safety Broadband Licensee from providing an entity with access to the network if that entity fails to meet the eligibility requirements of Section 90.523 of our rules.

66

47 U.S.C. 337(f)(1)(B)(ii).

33. We seek comment on which types of public safety users can be expected to use the national public safety broadband network (rather than legacy or new local networks) and on what timeframes. Which public safety communication functions (e.g., voice, remote data access, video upload, video download, photo download) are likely to migrate to the new broadband network (in the short- and- or long-term) and which will remain on existing networks? What factors will local jurisdictions weigh when making such decisions?

34. We seek comment on the extent to which the public safety broadband network will or should be interoperable with existing voice and data networks. How can the Commission encourage interoperability with legacy public safety systems and should interoperability with existing voice and data networks be a mandatory feature of the new broadband network? Can the use of multi-mode handsets (that support legacy networks and the new public safety broadband network) enhance interoperability? How can the Commission encourage or mandate the development and use of such handsets? How would any proposed policies in this regard affect the cost of handsets and network construction/operation? How does the use of 10 or 20 megahertz of shared spectrum affect the throughput of the broadband network and the functions it can support? What throughput can reasonably be expected on a network with this amount of spectrum? What functionalities can only

be supported on a network with additional spectrum?

35. We also seek comment on issues arising from the possibility that in some areas a local jurisdiction may not elect to make use of the public safety broadband network. How extensive are such areas likely to be in the short- and long-term? Should the D Block licensee be permitted to use the entire 20 megahertz of shared spectrum for commercial service in such areas? Should the local jurisdiction receive compensation in these instances? Could such compensation discourage local jurisdictions to ever make use of the public safety broadband network? Would restriction of such compensation to use in purchasing public safety equipment such as radios for the public safety broadband network be an appropriate policy? What incentives can the Commission give the D Block licensee to encourage and facilitate use of the broadband network by local jurisdictions?

36.

Potential Pool of Users of the Public Safety Broadband Network.

We seek comment on the number of public safety providers in the country that have no interoperable broadband network. What is the size of the potential pool of public safety providers that may work with the Public Safety Broadband Licensee? We also seek comment on the extent to which some public safety providers already have established interoperable broadband networks. We especially encourage comment from parties that may have an inventory or database that collects this information. Where have such networks been established, and under what types of arrangements? To what extent are current interoperable public safety systems able to obtain lower prices and/or superior quality for commercially available, off-the-shelf technologies? Have public safety and commercial operations been developed on shared/parallel systems, and if so, how have they addressed network security issues? We further seek comment on how previously developed systems have addressed issues such as network reliability, including hardening of the network, provisions for back up power, etc. How do such developed networks envision connecting to an interoperable, nationwide network? Finally, to the extent some public safety providers already have established interoperable broadband networks, might these providers have less incentive to participate with the Public Safety Broadband Licensee? If this is the case, how might the rules established in this proceeding help provide a nationwide, interoperable network?

37.

Mandatory Usage of the Public Safety Broadband Network.

While we seek comment above regarding what users of the network are eligible to receive service from the public safety spectrum, we also seek comment on whether such eligible public safety users should be required to subscribe to the network for service, at reasonable rates or be subject to some alternative obligation or condition promoting public safety network usage in order to provide greater certainty to the D Block licensee. For example, should we require the purchase of a minimum number of minutes and, if so, on whom and in what way would this obligation be imposed? We seek comment on whether any such obligation should be conditioned on the availability of government funding for access, for example, through interoperability grant money from the United States Department of Homeland Security, and whether we should require public safety users to pay for access with such money. We ask further questions below regarding whether and how we should regulate the fees charged to public safety users for network access. Would it be possible to ensure that small public safety providers pay a “Most Favored Nation” rate for broadband services, or for equipment? How should the Commission ensure that smaller public safety entities can participate in the network?

38. We note that the State of Arizona used a grant from the Department of Homeland Security (“DHS”) to build a broadband network for both public safety and commercial purposes using WiFi technology.

67

This network serves a portion of the I-19 corridor running north of the Mexican border, a sparsely populated area that previously had little or no coverage for commercial or public safety communications.

68

We seek comment on this and similar programs, especially those instituted by State agencies, and by both large and small municipalities. What specifications (

e.g.

, reliability of service, network hardening, etc.) have been required for this and similar projects to promote broadband communications for public safety providers

69

What lessons have been learned from these projects, and how might these lessons be applied to a variety of public safety providers, including those in very rural areas and those in urban areas? For example, do network congestion issues make sharing between commercial and public safety users more of a challenge in urban areas, and are such concerns lessened in rural areas?

67

See

http://www.dhs.gov/xnews/releases/press_release_0515.shtm

(last visited May 12, 2008).

68

See

http://gita.state.az.us/tech_news/2006/7_19_06.htm

(last visited May 12, 2008).

69

We note, however, that use of Part 15 devices may not be appropriate for mission-critical public safety communications, in light of the requirement for Part 15 devices to accept interference from other Part 15 devices and from licensed operations.

See,

e.g.

, Continental Airlines Petition for Declaratory Ruling Regarding the Over-the-Air Reception Devices (OTARD) Rules, ET Docket No. 05-247,

Memorandum Opinion and Order,

21 FCC Rcd 13201, 13214 (2006).

2. Provisions Regarding the Public Safety Broadband Licensee

a. Non-Profit Status

39.

Background.

Among other criteria for eligibility to hold the Public Safety Broadband License that we established in the

Second Report and Order

, we provided that no commercial interest may be held in the Public Safety Broadband Licensee, that no commercial interest may participate in the management of the licensee, and that the licensee must be a non-profit organization.

70

We indicated, however, that, as part of its administration of public safety access to the shared wireless broadband network, the Public Safety Broadband Licensee might assess “usage fees to recoup its expenses and related frequency coordination duties.”

71

70

See Second Report and Order,

22 FCC Rcd at 15421.

71

Id.

at 15426.

40.

Discussion.

With respect to the requirements that the Public Safety Broadband Licensee must be a non-profit organization, we seek comment on whether to clarify this non-profit requirement by specifying that the Public Safety Broadband Licensee and all of its members (in whatever form they may hold their legal or beneficial interests in the Public Safety Broadband Licensee) must be non-profit entities. We further seek comment on whether to clarify that the Public Safety Broadband Licensee may not obtain debt or equity financing from any source, whether debt or equity, unless such source is also a non-profit entity. We also seek comment more generally on whether the Commission should restrict the Public Safety Broadband Licensee's business relationships pre- and post-auction with commercial entities, and if so, what relationships should and should not be permitted.

41. We do anticipate that the Public Safety Broadband Licensee may contract with attorneys, engineers, accountants, and other similar advisors or service providers to fulfill its responsibilities to represent the interests of the public safety community, as required by the

Commission. Under the approach on which we seek comment above, capital or operational funding mechanisms for the Public Safety Broadband Licensee involving private equity firms or other commercial or financial entities would not be permitted, unless they are non-profit entities and are controlled, if at all, by non-profit entities, in order to ensure that the financial considerations of the Public Safety Broadband Licensee remain aligned with serving the public safety community, and that no “for-profit” incentives inadvertently influence the Public Safety Broadband Licensee's priorities. We seek comment on these restrictions. In particular, are the restrictions on financing warranted to ensure that the Public Safety Broadband Licensee is not unduly influenced by for-profit motives or outside commercial influences in carrying out its official functions within the 700 MHz Public/Private Partnership? If so, in what ways might we allow necessary financing while still ensuring the independence of the Public Safety Broadband Licensee? Specifically, should we allow working capital financing from commercial banks and, if so, should we restrict the assets of the Public Safety Broadband Licensee that can be pledged as security for such a loan? Are there other types of loans or alternative funding sources that we should allow the Public Safety Broadband Licensee to employ? How can the Commission establish incentive-compatible rules for the Public Safety Broadband Licensee and parties with which it may have a relationship, such as advisors, contractors, and investors?

42. More generally, we seek comment on the best way to fund Public Safety Broadband Licensee operations. For example, should the D Block licensee or license winner be required to pay the Public Safety Broadband Licensee's administrative costs? If so, should we limit the D Block licensee's maximum obligations in this regard, and what would be a reasonable cap or limitation on expenses? Assuming government-allocated funding were available, would this be the best solution for funding the Public Safety Broadband Licensee? In addition, we seek comment on the extent to which we can adopt incentive-compatible rules for the Public Safety Broadband Licensee and the public safety providers it represents. What set of rules would encourage most or all public safety providers to collaborate with the Public Safety Broadband Licensee to establish a nationwide, interoperable broadband network? Under what circumstances might some public safety providers choose not to participate in a relationship with the Public Safety Broadband Licensee?

72

72

See Second Report and Order

, 22 FCC Rcd at 15454.

43. We seek comment on whether the Commission has legal authority to use the Universal Service Fund to support the Public Safety Broadband Licensee's operational expenses.

73

If the Commission has legal authority to do so, should it exercise this authority? What degree of support would be appropriate? Similarly, can the Commission facilitate funding of the Public Safety Broadband Licensee's operational expenses through entities such as the Telecommunications Development Fund?

74

73

See,

e.g.

, 47 U.S.C. 254(c)(1), (h).

74

See,

e.g.

, 47 U.S.C. 614.

44. We also seek comment on how any excess revenue generated by the fees or other sources of financing obtained by the Public Safety Broadband Licensee from non-profit entities should be used. First, we seek comment on whether any excess revenues should be permitted at all. If we do allow any excess revenue generation, should we limit this amount? How should we determine what that amount should be? Should we allow the Public Safety Broadband Licensee to hold a certain amount of excess income as a reserve against possible future budget shortfalls or should we require that excess income be used for the direct benefit of the public safety users of the network, such as for the purchase of handheld devices? Should we further specify what would be a “direct benefit” or permissible use of such funds? In this regard, we note that the quarterly financial accounting we required in the

Second Report and Order

will enable the Commission to continually monitor the finances of the Public Safety Broadband Licensee.

75

75

Second Report and Order,

22 FCC Rcd at 15425.

45. Finally, we seek comment on whether the Public Safety Broadband Licensee may legitimately incur certain reasonable and customary expenses incurred by a business, consistent with the constitution of the Public Safety Broadband Licensee and the nature of its obligations as established by the Commission.

b. Other Essential Components

46.

Background.

In the

Second Report and Order,

we instituted certain minimum criteria that the Public Safety Broadband Licensee must meet in order to ensure that it “focuses exclusively on the needs of public safety entities that stand to benefit from the interoperable broadband network.”

76

To that end, we established certain criteria for the Public Safety Broadband Licensee eligibility, including a requirement that the Public Safety Broadband Licensee must be broadly representative of the public safety community.

77

Further, we required that the Public Safety Broadband Licensee be governed by a voting board consisting of eleven members, one each from the nine organizations representative of public safety, and two at-large members selected by the Public Safety and Homeland Security Bureau and the Wireless Telecommunications Bureau, jointly on delegated authority.

78

On reconsideration, we revised and expanded the voting board, and increased the at-large membership to four.

79

76

Id.

at 15421-22.

77

Id.

at 15421-25.

78

The nine organizations included: the Association of Public Safety Communications Officials (APCO); the National Emergency Number Association (NENA); the International Association of Chiefs of Police (IACP); the International Association of Fire Chiefs (IAFC); the National Sheriffs' Association; the International City/County Management Association (ICMA); the National Governor's Association (NGA); the National Public Safety Telecommunications Council (NPSTC); and the National Association of State Emergency Medical Services Officials (NASEMSO).

Second Report and Order,

22 FCC Rcd at 15422-23.

79

On reconsideration, we removed NPSTC and included the Forestry Conservation Communications Association (FCCA), the American Association of State Highway and Transportation Officials (AASHTO), and the International Municipal Signal Association (IMSA), and added two additional at-large positions. Service Rules for the 698-746, 747-762 and 777-792 MHz Bands, WT Docket No. 96-86,

Order on Reconsideration,

22 FCC Rcd 19935 (2007). The Chiefs of the Public Safety and Homeland Security Bureau and Wireless Telecommunications Bureau jointly appointed to the voting board the American Hospital Association (AHA), the National Fraternal Order of Police (NFOP), the National Association of State 9-1-1 Administrators (NASNA), and the National Emergency Management Association (NEMA).

See

“Public Safety and Homeland Security Bureau and Wireless Telecommunications Bureau Announce the Four At-Large Members of the Public Safety Broadband Licensee's Board of Directors,”

Public Notice,

22 FCC Rcd 19475 (2007).

47. In the

Second Report and Order,

we further required that certain procedural safeguards be incorporated into the articles of incorporation and bylaws of the Public Safety Broadband Licensee.

80

For example, in the

Second Report and Order

we specified that the term of the Public Safety Broadband Licensee officers would be two years, and that election would be by a two-thirds majority vote. A two-thirds majority was also required for certain other Public Safety Broadband Licensee decisions, including amending the articles of incorporation or bylaws. In

addition, we recognized that Commission oversight in the affairs of the Public Safety Broadband Licensee would be necessary and appropriate in light of the nature of the public safety broadband spectrum licensed to the Public Safety Broadband Licensee as a national asset, and in furtherance of the Commission's role in ensuring the protection and efficient use of such asset for the benefit of the safety of the public.

81

Meaningful oversight in this respect requires a level of transparency, and to that end we required the Public Safety Broadband Licensee to submit certain reports to the Commission, including quarterly financial disclosures.

82

80

Second Report and Order,

22 FCC Rcd at 15423-26.

81

Id.

at 15426.

82

Id.

at 15426.

48.

Discussion.

In light of the scope of the subjects discussed elsewhere herein addressing a number of aspects of the 700 MHz Public/Private Partnership between the D Block licensee and the Public Safety Broadband Licensee, we believe it appropriate to reexamine the structure of the Public Safety Broadband Licensee and the criteria adopted in the

Second Report and Order

to ensure they are most optimal for establishing and sustaining a partnership with a commercial entity, as well as efficiently and equitably conducting the business of the Public Safety Broadband Licensee. We seek comment on whether we should reevaluate any of these criteria, whether we should clarify or increase the Commission's oversight of the Public Safety Broadband Licensee, and, aside from retaining its nationwide scope, whether we should make other changes to the license or license eligibility criteria. We further seek comment on how the Commission can ensure an oversight role for Congress, both in the operations of the Public Safety Broadband Licensee and the 700 MHz Public/Private Partnership. Should Congress designate some of the Public Safety Broadband Licensee's board members?

49.

Articles of Incorporation and By-laws.

Specifically, with respect to the articles of incorporation and bylaws, we seek comment on the adequacy of the provisions specified. Should we require additional provisions, and if so, what should they be? Should we amend or eliminate any of the current requirements? Should we require a unanimous vote in certain instances? For example, should a unanimous vote be required for a major undertaking of the Public Safety Broadband Licensee? What would such an undertaking include? In the alternative, should we require a supermajority vote in such instances instead of a unanimous vote? In addition, should we provide for Commission review of decisions requiring a unanimous or supermajority vote, or should the Commission make certain decisions for the Public Safety Broadband Licensee if unanimity or supermajority is not achieved?

50. With respect to the voting board, we seek comment on the composition of the board, and its size. Should we include additional or fewer entities? If so, what qualifications should we require of such entities? We also seek comment on whether we should eliminate altogether the requirement of inclusion of specific voting board members. If we eliminate this requirement, how should we ensure that broad representation of the public safety community is adequately addressed? With respect to the leadership of the board, should we revise the terms of the officers? Should we require a unanimous vote for appointment of officers? Should we require a rotating chairmanship among the voting board members? Should the Commission appoint a chairperson if unanimous consent cannot be attained?

51.

Commission oversight.

We also seek comment on how the Commission can better exercise oversight over the activities of the Public Safety Broadband Licensee and the commercial partner. Is quarterly financial reporting adequate, or are additional disclosures by the Public Safety Broadband Licensee or commercial partner necessary? What additional measures, if any, should the Commission take to ensure the appropriate level of oversight? For example, should Commission approval of certain activities be required before the Public Safety Broadband Licensee may undertake them? For example, should Commission approval be required before the Public Safety Broadband Licensee enters into contracts of a particular duration or cumulative dollar amount? Should we require or reserve the right to have Commission staff attend meetings of the voting board?

52.

Role of State Governments.

We seek comment on whether providing a nationwide, interoperable broadband network might be more effectively and efficiently accomplished by allowing State governments (or other entities that have or plan interoperable networks for the benefit of public safety) to assume responsibility for coordinating the participation of the public safety providers in their jurisdictions. To the extent commenters believe the State governments should assume such a role, we seek comment on the proper relationship between the State governments and the Public Safety Broadband Licensee and on our authority to establish such a role for State governments. Should the Public Safety Broadband Licensee be authorized to choose a minimum standard for any public safety broadband operation, with the State governments given the responsibility to work with public safety providers to implement operations in their jurisdictions? Would such an approach allow State governments wanting higher-grade networks to implement separately these more-advanced systems, while those wanting networks at the minimum standard avoid what they may consider unnecessary expenses? Are State governments better situated to address implementation challenges that cross public safety jurisdictions (

e.g.

, coordinating use by sheriffs departments in neighboring counties) as well as intra-jurisdictional challenges (

e.g.

, coordinating use by the police versus fire departments)? On the other hand, if different jurisdictions chose different grades of networks, would there be a lack of economies of scale and thus higher equipment costs for all public safety users?

53.

Reissuance of the Public Safety Broadband License and selection process.

In light of the changes contemplated above and the corresponding changes contemplated with respect to the D Block, we seek comment on whether we should rescind the current 700 MHz Public Safety Broadband License and seek new applicants. If so, should we use the same procedures as before,

i.e.

, delegating authority to the Chief, Public Safety and Homeland Security Bureau to solicit applications, specifying any changed criteria that may be adopted following this Second FNPRM, and having the Commission select the licensee? Are there considerations other than those above or previously considered that should be taken into account in selecting the licensee? Recognizing the need to identify the licensee quickly to enable the effective development of the 700 MHz Public/Private Partnership, what mechanism should the Commission use to assign the license if there is more than one qualified applicant?

B. Possible Revisions/Clarifications Relating to the 700 MHz Public/Private Partnership

54. As a preliminary matter, we seek comment on whether the public interest would best be served by the development of a nationwide, interoperable wireless broadband network for both commercial and public

safety services through the 700 MHz Public/Private Partnership between the D Block licensee and the Public Safety Broadband Licensee, and whether we should therefore continue to require that the D Block licensee and Public Safety Broadband Licensee enter into the 700 MHz Public/Private Partnership. Below, we consider in detail the Commission's options in the event that we continue this requirement. We seek comment on a broad set of possible revisions to the 700 MHz Public/Private Partnership, including revisions and/or clarifications with regard to the respective obligations of the D Block licensee and the Public Safety Broadband Licensee.

55. First, we address the terms of the 700 MHz Public/Private Partnership, including (1) what the D Block licensee is required to construct; and (2) the operational roles of the D Block licensee and Public Safety Broadband Licensee once the network is constructed. With regard to network construction requirements, we seek comment on (1) the technical specifications of the network; (2) whether to provide public safety users with access to D Block spectrum during emergencies and, if so, under what terms; and (3) the build-out obligations of the D Block licensee, and whether such obligations should be revised in conjunction with a modification to the D Block license term. Regarding operational roles, we seek comment on the respective roles and responsibilities of the D Block licensee and Public Safety Broadband Licensee with regard to the operation of the network, including the management of users on the network, and we seek comment regarding service or spectrum usage fees.

56. Next, we address the procedures by which the winning bidder of the D Block license will enter into a Network Sharing Agreement (NSA) with the Public Safety Broadband Licensee that will further define and govern the 700 MHz Public/Private Partnership. Specifically, we seek comment on possible revisions to the rules relating to both the negotiation of the NSA and the dispute resolution procedures applicable in the event the parties are unable to reach agreement on NSA terms. In particular, we seek comment on whether, following a default due to the failure of a winning bidder for the D Block license to execute an NSA with the Public Safety Broadband Licensee, we either should offer the license to the party with the next highest bid, in descending order, or promptly auction alternative license(s) for the D Block spectrum without the 700 MHz Public/Private Partnership conditions and subject to alternative service rules.

57. We then seek comment on a number of issues related to the auction of the D Block license, including (1) whether to restrict who may participate in the new auction of the D Block license; (2) how to determine any reserve price for such an auction; (3) whether to adopt an exception to the impermissible material relationship rule for the determination of designated entity eligibility with respect to arrangements for the lease or resale (including wholesale) of the spectrum capacity of the D Block license; and (4) whether we should modify the auction default payment rules with respect to the D Block winning bidder. We also seek comment on the rules governing the relocation of public safety narrowband operations and the D Block license winner's obligations to fund that relocation, and on any other revisions that may be appropriate with regard to the 700 MHz Public/Private Partnership. Finally, we seek comment on other revisions or clarifications that may be appropriate with regard to the 700 MHz Public/Private Partnership, including whether to license the D Block and public safety broadband spectrum on a nationwide or REAG basis.

1. The 700 MHz Public/Private Partnership

a. Network/System Requirements

58. Assuming that we determinate that we should continue to require the 700 MHz Public/Private Partnership, in this section, we seek comment on whether to adopt changes to the requirements of the network that the D Block licensee is required to construct, and whether to modify the required schedule for that construction.

83

We seek comment on what changes will best serve the Commission's goal of making a broadband, interoperable network available on a nationwide basis to public safety entities, which requires providing sufficient assurances to bidders for the D Block license that the required shared network will be commercially viable. We also are seeking comment below on the costs to build and operate such a broadband, interoperable network, including the specific costs necessary to meet public safety needs and the additional costs of covering remote areas.

83

47 CFR 27.1305, 27.14(m).

(i) Technical Requirements for the Shared Wireless Broadband Network

59.

Background.

In the

Second Report and Order,

we found that in order to ensure a successful public/private partnership between the D Block licensee and the Public Safety Broadband Licensee, with a shared nationwide interoperable broadband network infrastructure that meets the needs of public safety, we must adopt certain technical network requirements.

84

Accordingly, among other requirements, we mandated that the network incorporate the following technical specifications:

84

Second Report and Order,

22 FCC Rcd at 15433.

• Specifications for a broadband technology platform that provides mobile voice, video, and data capability that is seamlessly interoperable across agencies, jurisdictions, and geographic areas. The platform should also include current and evolving state-of-the-art technologies reasonably made available in the commercial marketplace with features beneficial to the public safety community (

e.g.

, increased bandwidth).

• Sufficient signal coverage to ensure reliable operation throughout the service area consistent with typical public safety communications systems (

i.e.

, 99.7 percent or better reliability).

• Sufficient robustness to meet the reliability and performance requirements of public safety. To meet this standard, network specifications must include features such as hardening of transmission facilities and antenna towers to withstand harsh weather and disaster conditions, and backup power sufficient to maintain operations for an extended period of time.

• Sufficient capacity to meet the needs of public safety, particularly during emergency and disaster situations, so that public safety applications are not degraded (

i.e.

, increased blockage rates and/or transmission times or reduced data speeds) during periods of heavy usage. In considering this requirement, we expect the network to employ spectrum efficient techniques, such as frequency reuse and sectorized or adaptive antennas.

• Security and encryption consistent with state-of-the-art technologies.

85

85

Id.

60. We required that the parties determine more specifically what these technical specifications would be and implement them through the NSA. In addition, we required that the parties determine and implement other detailed specifications of the network that the D Block licensee would construct.

86

We determined that allowing the parties to determine specific details, including the technologies that would be used, subject to approval by the Commission, would provide the parties with flexibility to

evaluate the cost and performance of all available solutions while ensuring that the shared wireless broadband network has all the capabilities and attributes needed for a public safety broadband network.

87

86

Id.

at 15434.

87

Id.

at 15426.

61.

Discussion.

We seek comment on whether we should clarify or modify any aspect of the technical network requirements adopted in the

Second Report and Order

or otherwise establish with more detail the technical requirements of the network. To guide the discussion that follows, and to enable more focused comment that better assists the Commission as we address these technical requirements, we attach as an appendix a possible technical framework (“Technical Appendix”) that identifies in greater detail potential technical parameters for the shared wireless broadband network. We thus seek detailed comment on this Technical Appendix, as well as on the following discussion points.

62. Would clarifications in this regard provide appropriate additional certainty, prior to re-auction, regarding the obligations of the D Block licensee and the costs of the network that this licensee would be expected to construct? Would such specification enhance the abilities of the winning bidder of the D Block license and the Public Safety Broadband Licensee to negotiate the NSA? Would modifications provide greater assurance that the required network would be economically viable? Conversely, would greater specificity hinder the NSA negotiations or otherwise inadvertently impact the success of the 700 MHz Public/Private Partnership?

63. We seek comment on whether, as a general matter, maintaining parties' flexibility to negotiate most details of the network specifications would best serve the public interest goals of the partnership. We seek comment on what technical requirements should be specified in advance, rather than being left to be negotiated after the auction, and whether there are any critical aspects of the network, either in the existing requirements or beyond those already addressed, that it would be beneficial to specify or clarify in the rules in order to increase bidder certainty regarding the cost of the D Block obligations. In addition, are there network specifications that would be particularly difficult to negotiate in the absence of further clarification by the Commission?

64. Are any changes to requirements needed to reflect the practical differences between the architecture of traditional local wireless public safety systems and the architecture of nationwide commercial broadband network systems? If so, we seek comment on what requirements, modifications, or clarifications we should adopt. Conversely, we seek comment on whether to require national standardization in the implementation of these network requirements, and the extent to which national standardization will help the network to achieve efficiency and economies of scale and scope.

65. We also welcome comments on other specifications we required of the network. These included:

• A mechanism to automatically prioritize public safety communications over commercial uses on a real-time basis and to assign the highest priority to communications involving safety of life and property and homeland security consistent with the requirements adopted in the

Second Report and Order;

• Operational capabilities consistent with features and requirements specified by the Public Safety Broadband Licensee that are typical of current and evolving state-of-the-art public safety systems (such as connection to the PSTN, push-to-talk, one-to-one and one-to-many communications, etc.);

• Operational control of the network by the Public Safety Broadband Licensee to the extent necessary to ensure public safety requirements are met; and

• A requirement to make available at least one handset that would be suitable for public safety use and include an integrated satellite solution, rendering the handset capable of operating both on the 700 MHz public safety spectrum and on satellite frequencies.

88

88

Id.

at 15433-34. We seek comment on the responsibilities of the D Block licensee with regard to the operation of the shared network elsewhere herein.

66. Commenters with proposals should provide detailed information regarding their proposed technical network specifications, and the extent to which such proposals are typical of current wireless public safety or commercial systems. For example, with regard to any particular network requirement, are there any established public safety standards in the broadband context? To what extent have these standards been implemented in commercial networks? Commenters should also discuss how such proposals will ensure that the goals of the 700 MHz Public/Private Partnership are met, in particular by enabling the creation of a viable commercial network that addresses the unique needs of the public safety community.

67. We seek comment on how the technical specifications of existing or anticipated future public safety networks differ from existing or anticipated commercial networks. Commenters are encouraged to be as specific as possible in answering these questions, providing detailed technical data where possible. How different are the technical specifications of existing or anticipated public safety networks from other public safety networks? How do the technical requirements of different public safety networks differ based upon factors such as intended user base and local morphology (e.g., urban vs. rural environments; fire, police, emergency medical service, and other first responders; in-building vs. outdoor usage; high-speed vehicular vs. pedestrian public safety users, etc.)? How do these technical requirements differ based upon factors such as type of use (mission-critical voice and data versus non-mission-critical communications)? What purposes, if any, do public safety users make of commercial wireless networks today for mission-critical and/or non-mission-critical communications? How distinct in practice is the line between mission-critical and non-mission-critical communications? How do network construction and operation costs vary among different types of public safety networks and between public safety and commercial networks? To what extent can a commercial provider make use of publicly-owned or leased property, and how could use of such facilities affect the cost of constructing and operating a public safety broadband network?

68. We seek comment on the payment and funding models employed by public safety users when building and operating dedicated public safety networks (e.g., construction and operation by municipal employees, construction and operation by private subcontractors). Similarly, we seek comment on the payment and funding models employed by public safety users when they rely upon commercial wireless services. Are fees assessed based on usage, number of users, or other factors? What provisions are typically made for unanticipated demand for services and how are these reconciled with fixed budgets? Again, commenters are encouraged to be as specific as possible in answering these questions, providing specific cost data or concrete numerical estimates where possible.

69. We note that the Public Safety Spectrum Trust (“PSST”), after it was

designated Public Safety Broadband Licensee by the Commission, released what it referred to as a Bidders Information Document (“BID”), which, it stated, was offered to provide “high-level information regarding the PSST's expectations of the D Block partner in building and operating the shared Public/Private network” and “to define and detail certain expectations that the PSST has for this partnership.”

89

We emphasize that the BID has no formal legal role in the development of the nationwide, broadband public safety network under the existing rules and we express no view on the positions taken by the PSST as reflected in the BID. We take this opportunity, however, to seek comment on the impact of the BID on the previous auction, whether any particular aspects of the PSST's “expectations” were of particular concern to potential bidders or of particular importance to public safety entities, whether the release of the BID was helpful in clarifying costs, what role the BID played in pre-auction discussions and what formal role, if any, that a document similar to the BID such as a statement of requirements should play in establishing or clarifying the technical requirements of the nationwide, broadband public safety network under revised rules. We note, for example, that one commercial entity has suggested that the Public Safety Broadband Licensee should be required to release a statement of requirements before auction, and that the statement of requirements should constrain the elements that the Public Safety Broadband Licensee can require in the shared network.

90

We seek comment on this suggestion.

89

See

Letter from Harlin R. McEwen, Chairman, Public Safety Spectrum Trust to Prospective D Block Bidders (Nov. 30, 2007) (

available at

http://www.psst.org/documents/BID2_0.pdf

) at 3. The PSST released an initial version of this document on November 15, 2007, and released version 2.0, the final version, on November 30, 2007. See

http://www.psst.org/bidsummary.jsp.

90

See

AT&T Petition for Reconsideration at 4-5.

70. With these questions and issues in mind, we seek comment on whether the Commission should itself establish in a detailed and comprehensive fashion the technical obligations of the D Block licensee with regard to the network, and if so, what specifications it should adopt. For example, we seek comment on whether the attached Technical Framework could, following comment on its specific components, provide for establishing an appropriate set of requirements for the shared wireless broadband network. We also seek comment on a number of particular technical issues, as set forth below.

71.

Specification for broadband technology platform.

We seek comment on whether we should modify or further clarify any aspect of the broadband technology platform specifications provided in the

Second Report and Order.

Would clarifying that the D Block winning bidder has the right to make the final technical determinations with regard to the network platform serve the public interest? Should the Commission specify the precise public safety services and applications that must be carried or that need not be carried, beyond typical broadband applications (

e.g.

, Internet access, video, multimedia), such as cellular telephony, dispatch voice service, push-to-talk, etc., and if so, what should they be? Should we establish limits on the obligation to accommodate applications similar to those established in the C Block? For example, should we provide that there is no obligation to carry customized applications where accommodating such applications would require modifying network infrastructure or back-office systems?

91

What impact might any of these determinations have on the utility of the network for public safety purposes?

91

See Second Report and Order,

22 FCC Rcd at 15371 n.502.

72. We ask commenters to provide detailed information regarding any proposed broadband platform solution. How can we establish a set of requirements that will meet public safety's needs while providing prospective bidders with sufficient certainty that it will be possible to construct a system that is economically viable? How can we best meet this objective without impeding flexibility regarding network design or inadvertently deterring potential bidders from participating in the auction?

73.

Reliability.

We seek comment on whether we should modify any aspect of the reliability standard established in the

Second Report and Order.

Should we eliminate the specific requirement of 99.7 percent network reliability and impose only the general requirement of “reliable operation throughout the service area consistent with typical public safety communications,” leaving the specific level of reliability to negotiations? Should we specify a different level of reliability, such as 95 percent reliability over 95 percent of a defined area?

92

Does the latter standard better reflect a typical level of reliability in public safety communications systems? Further, is the typical level of reliability in public safety systems a relevant factor for cellularized broadband systems? Are there any real-world examples of reliability based on cellularized broadband systems used by public safety?

92

See

Cyren Call Petition for Reconsideration at 8; Frontline Petition for Reconsideration at 23.

74. We also seek comment on whether, in the event we continue to require a specific level of reliability, we should nevertheless expressly provide that the parties have flexibility to mutually agree to a different level in particular geographic areas. Are there specific provisions related to reliability that would create unreasonable challenges in establishing the network? If so, what limitations should we establish? Finally, we seek comment on how the reliability standard impacts the performance requirement,

e.g.

, might it effectively transform the population-based performance requirements into geographic benchmarks?

75.

Robustness and hardening.

We seek comment on whether to further specify or modify the requirements of the network regarding robustness and hardening. For example, should we further specify the particular environmental conditions (temperature range, wind, vibration, etc.) that the installations must be designed to withstand? Should we specify the minimal number of hours that base stations and network equipment must be capable of operating in the event of a power outage? Should we require an onsite power generator and a specific supply of fuel for each base station? Should we simply provide that the network must meet the same requirements regarding backup power applicable to commercial mobile radio service providers, given that these requirements were themselves established to meet homeland security and public safety goals?

93

Should we address whether and to what extent redundant infrastructure must be provided, such as provisions for overlapping cell sites that could provide backup coverage in an emergency, and if so, how would such provisions impact the viability of the system and its cost? Should we establish minimum obligations to have access to backup equipment and systems, such as cellular systems on wheels, or minimum timeframes for system restoration? Alternatively or additionally, should we establish ceilings on the extent of robustness and hardening that may be required of the D Block licensee?

93

See,

e.g.

, Recommendations of the Independent Panel Reviewing the Impact of Hurricane Katrina on Communications Networks, EB Docket No. 06-119, WC Docket No. 06-63,

Order on Reconsideration,

22 FCC Rcd 18013 (2007).

76. We also seek comment on whether these requirements should be subject to variation. Should we specify circumstances in which the robustness and hardening obligations may vary, such as to account for local zoning restrictions, geography, or patterns of weather? Should we alternatively specify that the extent and circumstances of variation will be left to the parties to negotiate? Commenters advocating particular requirements relative to robustness and hardening should also explain how their proposals compare to the standards for current public safety wireless systems.

77.

Capacity, throughput, and quality of service.

As stated in the

Second Report and Order,

NPSTC contended that capacity is a key consideration, arguing that “the Commission should require a detailed capacity plan as one of the central elements in the negotiated agreement * * *”

94

Should we further specify the minimum levels of capacity or throughput (

i.e.

data transmission rates), or ceilings on such levels, that the network must provide? If so, how should such levels be defined? Should they vary by geographic location, or other conditions? Should we establish other quality of service parameters, such as resource reservation and session control mechanisms? What means should be made available by the D Block licensee to enable public safety to monitor the quality of service in an unobtrusive way and without the addition of significant cost to the network? Should the means be nationally standardized and/or be limited to those provided by the D Block licensee? Is there a need for a formal process to address future increases in demand?

94

Second Report and Order,

22 FCC Rcd at 15433 ¶ 404 (quoting NPSTC

700 MHz Further Notice

Comments at 13).

78. As we have emphasized throughout this Second FNPRM, one of the key elements of the 700 MHz Public/Private Partnership is the D Block licensee's access to the public safety broadband spectrum on a secondary basis to defray the cost of building a nationwide network serving both commercial and public safety users. We thus invite comment as to whether there are any particular services or applications that might be too inefficient or far removed from typical public safety communications needs, or that may overburden or otherwise not be viable for a broadband network, such that they may frustrate this key element by excessively limiting or precluding the secondary access to this spectrum contemplated in the

Second Report and Order.

For example, would it be appropriate to prohibit or restrict use of the network for continuous or routine video surveillance from fixed locations as being an inefficient or inappropriate use of the capacity of the shared wireless broadband network?

95

Would such use create undue uncertainty concerning network availability for either the D Block licensee or for public safety users? If there are such concerns, how else should they be addressed? Are other frequencies available to public safety users more appropriate for fixed video applications? Could such networks be made interoperable with the public safety broadband network using 700 MHz spectrum? What are the relative costs of using alternative frequencies? What cost savings, if any, would there be to incorporating video into the 700 MHz network as compared to allowing individual jurisdictions to develop their own fixed video wireless networks? Should we set certain parameters to determine or predict capacity needs of public safety users? We could, for example, base the capacity needs on the levels of authority within the public safety community, the existence or absence of an “emergency” (further discussed below), or type, time, or location of communication. Are there any technical, operational, or cost-based means to monitor or regulate capacity needs of certain public safety entities? Should we require the Public Safety Broadband Licensee to forecast public safety use on a regular basis (monthly, quarterly), or otherwise provide the assistance needed for the D Block licensee to make such predictions? Commenters proposing any limits to address such capacity concerns should provide detailed information on how such limitations could be implemented without compromising public safety. Would payment obligations of public safety users for network use be sufficient incentive for users to voluntarily limit use? Would a rate-of-return or cost-plus pricing mechanism provide the appropriate incentives? Alternatively, should we vary the obligations of the D Block licensee, its right to recover costs from public safety, or other terms of the NSA, based on the extent to which the public safety broadband spectrum is available for commercial operations? Or is it sufficient to clarify that the parties may negotiate such variations?

95

See

,

e.g.

, “DC OCTO Wireless Broadband Network Wins Police Chiefs' Technology Award,”

http://newsroom.dc.gov/show.aspx/agency/octo/section/2/release/6342

(stating that the DC wireless broadband network is designed to provide, among other applications, “remote video surveillance”);

see also http://govtsecurity.com/state_local_security/close_watch/

(stating, with regard to Baltimore, Maryland, video surveillance system, that “[m]any of the city's surveillance cameras and all of its housing cameras are wireless” and that “[w]ireless camera signals from groups of cameras are brought back to a fiber node * * *.”).

79.

Security and encryption.

Should we provide greater specificity regarding what the D Block licensee must provide with regard to security and encryption, or establish an alternate requirement? Should we identify further what constitutes “state-of-the-art” security and encryption technology? Should we limit the requirement to technical network solutions or standards for security and encryption implemented on a nationwide basis? We seek comment on the costs and practical challenges of implementing such measures in the public/private network to be constructed by the D Block licensee, particularly in the event that we permit local variation in the security solutions and standards.

80.

Combined use of spectrum.

We seek comment on whether, in order to provide the D Block licensee with appropriate flexibility to achieve an efficient and effective implementation of the 700 MHz Public/Private Partnership obligations, we should amend our rules to clarify that the D Block licensee may construct and operate the shared wireless broadband network using the entire 20 megahertz of D Block spectrum and public safety broadband spectrum as a combined, blended resource. In particular, we seek comment on whether, in designing and operating the shared network, the 10 megahertz of D Block spectrum and the 10 megahertz of public safety broadband spectrum may be combined, in effect, into a single and integrated 20 megahertz pool of fungible spectrum that may be assigned to users without regard to whether a public safety user is being assigned frequencies in the D Block or a commercial user is being assigned frequencies in the public safety broadband spectrum, so long as the network provides commercial and public safety users with service that is consistent with the respective capacity and priority rights of the D Block license and Public Safety Broadband License and with our rules. For example, such a network would have to guarantee that public safety users have priority access to at least 10 megahertz of spectrum capacity consistent with the 10 megahertz associated with the Public Safety Broadband License, but, at any particular time, the network might be using frequencies associated with either the D Block license or the Public Safety

Broadband License to provide that capacity.

96

96

We note that, under current rules for the 700 MHz Public/Private Partnership, public safety users would be entitled in emergencies to the full combined 20 megahertz of capacity on a priority basis. Elsewhere in this Second Further Notice, we seek comment on whether to eliminate or clarify this requirement.

81. We seek comment on whether permitting the combined use of spectrum in this fashion would provide for a more efficient and effective use of spectrum, whether it provides further flexibility to evaluate and use all available wireless broadband technologies to build and operate the network and thus promote our ultimate goal of making available a nationwide interoperable broadband network for public safety users. We also seek comment on whether such combined use would be consistent with the different rights and obligations associated with the D Block license and the Public Safety Broadband License, respectively, and whether, in light of these and other considerations, it would be in the public interest to allow such use. Commenters should also discuss whether permitting such combined use of the spectrum associated with these two licenses would be consistent with the requirements of Sections 337(a) and (f) and the Commission rules allotting specific frequencies for use by the Public Safety Broadband Licensee and the D Block licensee.

82.

Power flux density, and related notification, and coordination requirements.

In the text of the

Second Report and Order

, we indicated that we would not adopt any power flux density (PFD) limit requirement in the public safety broadband segment, based on the limited record received on this issue.

97

We also noted that, should additional facts be presented, we might revisit this issue.

98

The applicable rules adopted by the

Second Report and Order

, however, require the Public Safety Broadband Licensee to meet a PFD limit when operating base stations at power levels above 1 kW ERP.

99

In light of this discrepancy between the text of the order and the rules, we seek comment on whether we should retain this PFD requirement for the public safety broadband spectrum.

100

Further, we note that Verizon Wireless (“Verizon”) filed a petition for reconsideration of the

First Report and Order

101

with regard to certain of the notification and coordination obligations placed on commercial 700 MHz licensees.

102

First, Verizon requests that we eliminate the PFD/notification requirement for Upper 700 MHz C and D Block licensees when operating base stations at power levels above 1 kW ERP in non-rural areas. And second, with respect to Upper 700 MHz C and D Block licensees operating in rural areas, Verizon requests that such licensees: (1) Should only have to coordinate with adjacent block licensees (

i.e.

, not all other 700 MHz licensees) when seeking to operate at power levels greater than 1 kW ERP; (2) should be permitted to use a power level of “1 kW ERP and 1 kW/MHz ERP” as the trigger for coordination instead of 1 kW ERP;

103

and finally, (3) should be subject to a PFD/notification requirement, rather than a coordination requirement, when operating base stations at power levels greater than 1 kW ERP and 1 kW/MHz ERP.

104

In light of this petition, we seek comment on whether to apply any or all of Verizon's proposed rule changes to the public safety broadband spectrum.

97

See id.

, 22 FCC Rcd at 15417 para. 358.

98

Id.

99

See

47 CFR. 90.542(a)(5), (b).

100

This requirement had initially been imposed on Upper 700 MHz C and D Block licensees to protect public safety narrowband licensees from interference.

101

See

Service Rules for the 698-746, 747-762 and 777-792 MHz Bands, WT Docket No. 06-150, Revision of the Commission's Rules to Ensure Compatibility with Enhanced 911 Emergency Calling Systems, CC Docket No. 94-102, Section 68.4(a) of the Commission's Rules Governing Hearing Aid-Compatible Telephones, WT Docket No. 01-309, Biennial Regulatory Review—Amendment of Parts 1, 22, 24, 27, and 90 to Streamline and Harmonize Various Rules Affecting Wireless Radio Services, WT Docket 03-264, Former Nextel Communications, Inc. Upper 700 MHz Guard Band Licenses and Revisions to Part 27 of the Commission's Rules, WT Docket No. 06-169, Implementing a Nationwide, Broadband, Interoperable Public Safety Network in the 700 MHz Band, PS Docket No. 06-229, Development of Operational, Technical and Spectrum Requirements for Meeting Federal, State and Local Public Safety Communications Requirements Through the Year 2010, WT Docket No. 96-86,

Report and Order and Further Notice of Proposed Rulemaking,

22 FCC Rcd 8064 (2007) (

First Report and Order

).

102

Petition for Reconsideration of Verizon Wireless, WT Docket No. 06-150 (filed June 14, 2007) (Verizon Petition).

103

Upper 700 MHz C and D Block licensees may operate base stations at power levels up to 2 kW/MHz ERP in rural areas.

104

Verizon Petition at 8-12.

83.

Other technical requirements.

As noted above, we also seek comment on whether to establish, modify, or clarify the requirements with regard to any other critical aspect of the network that may significantly affect its commercial viability or its ability to meet the needs of public safety. For example, should we further specify the technical requirements and standards with regard to interoperability or network availability?

(ii) Priority Public Safety Access to Commercial Spectrum During Emergencies

84.

Background.

In addition to requiring that the network meet certain technical specifications, we also required that the D Block licensee provide the Public Safety Broadband Licensee with priority access, during emergencies, to the spectrum associated with the D Block license (in addition to the 700 MHz public safety broadband spectrum). At the same time, we noted that the potential disruption of commercial service in the D Block, while appropriate in an emergency situation, must be limited to the most serious occasions in order to avoid jeopardizing the commercial viability of the 700 MHz Public/Private Partnership. To balance these competing concerns, we thus required the parties to define “emergency” for purposes of priority access to D Block license spectrum as part of the NSA.

105

We also provided that in the event that the parties are unable to agree that an emergency situation requires priority access to the D Block license spectrum, especially in circumstances that do not clearly fall within the definition of “emergency” negotiated by the parties in the NSA, the Public Safety Broadband Licensee may request that the Commission declare, on an expedited basis, that particular circumstances warrant emergency priority access.

106

105

Second Report and Order

, 22 FCC Rcd at 15441-42 ¶ 426.

106

Id.

at 15442. We delegated authority to the Defense Commissioner to decide these requests. See 47 CFR 0.181.

85.

Discussion.

We seek comment on whether we should continue to require that the D Block licensee provide the Public Safety Broadband Licensee with priority access, during emergencies, to the spectrum associated with the D Block license. We seek comment on whether this obligation is essential to ensure that the network capacity will meet public safety wireless broadband needs, or whether removing the obligation could significantly improve the chances that this proceeding will succeed in achieving our goal of making available to public safety users a nationwide, interoperable, broadband network that incorporates the greater levels of reliability, robustness, security, and other features required for public safety services.

86. If we continue to require that the D Block licensee provide the Public Safety Broadband Licensee with priority access, during emergencies, to the spectrum associated with the D Block license, we seek comment on whether

we should provide more clarity on the circumstances that would constitute an “emergency” for this purpose. If so, we ask whether any or all of the following events should define an “emergency:”

• The declaration of a state of emergency by the President or a state governor.

• The issuance of an evacuation order by the President or a state governor impacting areas of significant scope.

• The issuance by the National Weather Service of a hurricane or flood warning likely to impact a significant area.

• The occurrence of other major natural disasters, such as tornado strikes, tsunamis, earthquakes, or pandemics.

• The occurrence of manmade disasters or acts of terrorism of a substantial nature.

• The occurrence of power outages of significant duration and scope.

• The elevation of the national threat level, as determined by the Department of Homeland Security, to either orange or red for any portion of the United States, or the elevation of the threat level in the airline sector or any portion thereof, as determined by the Department of Homeland Security, to red.

87. Are there any other events, or modifications to the above, that would assist in removing uncertainty in reaching a definition of “emergency?” Would this proposed definition of “emergency” be too burdensome on the D Block licensee? If we adopted some or all of the above event-defining emergencies, should we permit the parties to the NSA to propose different or additional scenarios that should be considered emergencies? Further, should we make explicit that priority access in emergency situations be limited to the geographic and/or jurisdictional area directly affected by the emergency? Should we establish time limits on the duration of priority access? If so, how should such time limits be based? Alternatively, should we establish limits on the priority access given to the D Block spectrum capacity, for example by limiting public safety's priority access to D Block spectrum capacity in emergencies to 50 percent?

(iii) Performance Requirements Relating to Construction of the Network

88.

Background.

In the

Second Report and Order

, we decided that the D Block license would be issued for a period of 10 years and imposed unique performance requirements for the D Block license in connection with the construction of the shared wireless broadband network. Specifically, we required the D Block licensee to provide signal coverage and offer service to at least 75 percent of the population of the nationwide D Block license area by the end of the fourth year, 95 percent by the end of the seventh year, and 99.3 percent by the end of the tenth year.

107

We further specified that “the network and signal levels employed to meet these benchmarks be adequate for public safety use * * * and that the services made available be appropriate for public safety entities in those areas.”

108

107

Second Report and Order

, 22 FCC Rcd at 15445.

108

Id.

at 15446.

89. Certain other requirements were imposed to further ensure coverage of highways and certain other areas such as incorporated communities with a population in excess of 3000.

109

We concluded that these build-out requirements “will ensure that public safety needs are met.”

110

We also required, however, that, “to the extent that the D Block licensee chooses to provide commercial services to population levels in excess of the relevant benchmarks, the D Block licensee will be required to make the same level of service available to public safety entities.”

111

109

See id.

at 15445, 15446.

110

Id.

at 15445.

111

Id.

at 15446.

90.

Discussion.

We seek comment on whether we should revise the performance requirements that we imposed on the D Block licensee with regard to building out the nationwide, interoperable broadband network and, if so, how those requirements should be revised. We also invite comment on whether to extend the license term for that license, and possibly the Public Safety Broadband License, if we determine to provide for construction benchmarks that extend past the initial license term that we established for the D Block license.

91. We seek comment on whether we should retain the existing end-of-term population benchmark of 99.3 percent or whether instead we should adopt a lower population benchmark that is equal to or more aggressive than the 75 percent benchmark that is applicable to the C Block. We note that each of the top four nationwide carriers is currently providing coverage to approximately 90 percent or more of the U.S. population.

112

Given that existing commercial wireless infrastructure already covers approximately 90 percent of the population, we seek comment on whether it is reasonable to expect that the D Block licensee would be able to meet at least a 90 percent of the population coverage requirement or more, or whether some other coverage requirement is appropriate.

112

UBS Warburg Investment Research, U.S. Wireless 411, at 17 (Mar. 18, 2008).

92. Based on extrapolations from one estimate in the record, it appears that reducing the population coverage level from 99.3 to 98 percent would result in a potential cost savings for the D Block licensee of approximately $3.1 billion in capital expenditures and reducing the coverage level to 95 percent would result in a potential cost savings of approximately $6.1 billion in capital expenditures.

113

Even assuming that a more reasonable estimate of potential cost savings may amount to around half these figures, reducing the coverage level to 98 percent would result in a potential cost savings of approximately $1.6 billion and reducing the coverage level to 95 percent would result in a potential cost savings of around $3.1 billion.

114

We seek comment on these specific estimates, as well as any other estimates that commenters can provide relating to the incremental additional costs associated with covering each percentage (in whole or part) of the

population above 95 percent. We also note that reducing the population coverage level for the end-of-term benchmark from 99.3 percent to 98 percent or 95 percent would also reduce the geographic area covered by the network. We estimate, for example, that under the current 99.3 percent end-of-term build-out benchmark, approximately 61 percent of the geographic area of the country would be covered by the network. By contrast, with a 95 percent end-of-term build-out benchmark, we estimate that approximately 40 percent of the geographic area of the country would be covered.

115

We seek comment on these estimates, or on any related estimates.

113

See

Frontline Petition for Reconsideration at 22 (stating that increasing the 10-year coverage requirement from 99 percent of the population to 99.3 percent added $1 billion in costs to the network). Commission staff extrapolated from Frontline's analysis to estimate potential cost savings associated with various coverage levels. First, Commission staff estimated Frontline's implied network cost per square mile by taking the difference in square miles between CONUS population coverage at 99.3 percent and 99 percent (149,048 square miles), and then dividing Frontline's $1 billion cost savings by this difference in square miles. Using this methodology, Commission staff estimated Frontline's implied network cost per square mile to be approximately $6,700. In estimating the difference in square miles between population coverage at 99 percent and 99.3, Commission staff used U.S. Census-based population data by county, starting with the county that has the highest population density, and working down in counties to arrive at 99 and 99.3 percent of the U.S. population. Using the implied network cost per square mile derived from the Frontline data, Commission staff estimated that reducing the CONUS population coverage level from 99.3 to 98 percent would result in a reduction of 913,612 square miles covered by the network. This reduction in square miles is multiplied by the implied cost of $6,700 to arrive at potential network cost savings for the D Block licensee of approximately $3.1 billion. Similarly, Commission staff estimated that reducing the CONUS population coverage level from 99.3 to 95 percent would result in a reduction of 462,591 square miles covered by the network. This reduction in square miles is multiplied by the implied cost of $6,700 to arrive at potential network cost savings for the D Block licensee of approximately $6.1 billion.

114

By reducing this estimated implied network cost per square mile by 50 percent (from $6,700 to $3,355), Commission staff estimated a potential cost savings of approximately $1.6 billion if the coverage level were reduced to 98 percent, and a potential cost savings of $3.1 billion if the coverage level were reduced to 95 percent.

115

See

Implementation of Section 6002(b) of the Omnibus Budget Reconciliation Act of 1993; Annual Report and Analysis of Competitive Market Conditions with Respect to Commercial Mobile Services,

Twelfth Report,

23 FCC Rcd 2241, at 5 (2008) (Twelfth CMRS Competition Report).

93. More generally, we seek comment on how much a dedicated, nationwide, interoperable broadband network for public safety, built to the requirements outlined in the

Second Report and Order

, costs to build and operate. We seek as much detail on these costs as commenters can provide. How should the Commission balance the potential savings associated with adopting less stringent performance requirements with our goal of establishing a nationwide interoperable public safety network?

94. As we consider appropriate construction benchmarks for the D Block license, we note that for the 22 megahertz C Block we required licensees to provide signal coverage and offer service to at least 40 percent of the population in each EA of the license area within four years and to at least 75 percent of the population in each EA of the license area by the end of the ten-year license term.

116

Given that the licenses in the C Block were successfully auctioned in Auction 73, and that at least one bidder has put together a nearly nationwide geographic footprint with these licenses, we assume that the D Block licensee should, at the very minimum, be able to meet these benchmarks with respect to its nationwide license. We seek comment on this assumption.

116

Second Report and Order,

22 FCC Rcd at 15351.

95. Depending on which performance benchmarks we may ultimately adopt, should we include benchmarks that extend beyond the end of the initial 10 year license term? If so, should we also extend the term of the D Block license accordingly? Would doing so make it easier for the D Block licensee to meet the performance requirements the Commission adopted? If, for example, we were to adopt a 15 year license term, would such a modification increase the commercial viability of the required network while still meeting public safety needs? If we were to adopt a 15 year license term, how should the interim build-out benchmarks be modified? We could, for example, require the D Block licensee to provide signal coverage and offer service to at least 50 percent of the population of the nationwide license area by the end of the fifth year, 80 percent of the population of the nationwide license area by the end of the tenth year, and 95 percent of the population of the nationwide license area by the end of the fifteenth year. Would modifying the license term and performance requirements in this way, or similar way, serve the public interest? Alternatively, if we extend the overall license term, should we add additional interim benchmarks to reflect the longer deployment period? What potential impact would these revised terms and benchmarks have on the near-term and long-term needs of public safety? Would roaming be a possible solution to increased coverage needs?

96. We also seek comment on how making changes to the license term and performance requirements as described above would affect other aspects of the rules that we adopted, such as the requirement that the D Block licensee and Public Safety Broadband Licensee negotiate inclusion into the build-out schedule coverage of major highways and interstates, as well as incorporated communities with a population in excess of 3,000 people?

117

In addition, we seek comment on whether any aspect of the renewal requirements for the D Block licensee should be revised. In the

Second Report and Order

, we determined that, at the end of the 10 year license term, the D Block licensee will be allowed to apply for license renewal that will be subject to its success in meeting the material requirements set forth in the NSA as well as all other license conditions, including meeting the performance benchmark requirements.

118

Because the initial NSA term will expire at the same time, we also required the D Block licensee to file a renewed or modified NSA for Commission approval at the time of its license renewal application.

119

Should we make any changes to these requirements?

117

We do not revisit our decision to prohibit geographic partitioning and spectrum disaggregation for the D Block licensee in the context of the 700 MHz Public Private Partnership. We continue to find that such restriction is necessary to ensure the integrity of the public/private partnership and nationwide broadband network.

118

Second Report and Order,

22 FCC Rcd at 15450.

119

Id.

97. How will the possibility of NSA re-negotiation at some point in the future affect the incentives of public safety users to develop reliance on the public safety broadband network? What steps could provide public safety users with confidence that using the broadband network will remain attractive after potential changes to the NSA at renewal time?

120

What are the downsides to such an approach?

120

See

A New Proposal for a Commercially Run Nationwide Broadband System Serving Public Safety by Jon M. Peha, Associate Director, Center for Wireless and Broadband Networking, Professor of Electrical Engineering and Public, PS Docket No. 06-229, WT Docket No. 96-86 (filed Feb. 27, 2007), at 9.

98. As discussed above, we are seeking comment on whether the license term of the D Block should be revised. In adopting the ten-year license term for the Public Safety Broadband Licensee, we sought to harmonize the license terms to facilitate the contemplated leasing arrangement and build out requirements. Accordingly, should we determine to extend the term of the D Block license, we seek comment on whether we also should extend the Public Safety Broadband Licensee term in a corresponding manner. Further, we determined in the

Second Report and Order

that the NSA was to have a term not to exceed 10 years from February 17, 2009, to coincide with the term of the D Block license. Thus, we also ask whether we should extend the term of the NSA to be co-extensive with any extended term we may adopt for the D Block.

99. We also seek comment on whether we should revise our rules to permit the D Block licensee to use Mobile Satellite Service to help it meet its build-out benchmarks. In the

Second Report and Order

, we found that satellite services can enable public safety users to communicate in rural and remote areas that terrestrial services do not reach. We also stated that satellite technology can provide the only means of communicating where terrestrial communications networks have been damaged or destroyed by wide-scale natural or man-made disasters.

121

As a result, we required that the D Block licensee make available to public safety users at least one handset that includes a seamlessly integrated satellite solution.

122

In addition, we strongly

encouraged the D Block licensee and the Public Safety Broadband Licensee to negotiate large-scale satellite service agreements that could be used to either expand or expedite build-out in rural areas and to replace terrestrial services where terrestrial facilities are damaged or destroyed.

123

121

Second Report and Order

at 15452.

122

Id.

at 15452.

123

Id.

at 15453.

100. In light of the potential for Mobile Satellite Services to supplement the D Block licensee's coverage, we seek comment in this Second FNPRM on whether it would serve the public interest to permit the D Block licensee to utilize Mobile Satellite Service as a way to meet, in part, its build-out requirements. We seek comment on whether this proposal could better enable the D Block licensee to meet its performance requirements by providing the licensee with additional means for ensuring that broadband public safety services are available in remote and rural areas. If the D Block licensee is able to make use of Mobile Satellite Service coverage, we seek comment on whether satellite coverage would make it easier to cover gaps in rural areas in the terrestrial 700 MHz public safety network. We seek comment on whether this additional flexibility in infrastructure deployment would serve to bolster the availability, robustness, and survivability of the public safety communications network. If we permit the D Block licensee to use Mobile Satellite Services to help it meet the build-out benchmarks, we seek comment on whether we should limit the extent to which it can rely upon such services and, if so, how its reliance on Mobile Satellite Services should be limited.

101. We also seek comment on whether the D Block licensee's obligation to meet its build-out requirements should be delayed or relaxed if the licensee ensures that handsets with terrestrial and mobile satellite components are available in areas that have not been built out with a terrestrial network, but are covered by a Mobile Satellite Service footprint. Alternatively, we seek comment on whether we should retain the terrestrial build-out requirement, but provide the D Block licensee with more flexibility if it makes terrestrial/mobile satellite handsets available for public safety use. We seek comment, for example, on whether the D Block licensee should be provided scaled flexibility based on the substitutability of the satellite offering for terrestrial services to be used by public safety users. Factors that we could consider in assessing such an offering might include: (1) The capabilities of the satellite component (

e.g.

, voice, data, video, interoperability, priority/preemption); (2) the availability of terrestrial/mobile satellite data devices, in addition to handheld voice devices; and (3) geographic coverage. To the extent we determine to lower the population coverage level for the end-of-term benchmark from 99.3 percent to 98 percent or 95 percent, is there some other way than Mobile Satellite Service to provide service to 99.3 percent of the population?

102. What would be the marginal cost to public safety entities of using Mobile Satellite Service-based communications services? To what extent would these marginal costs be comparable to the marginal cost of using the terrestrial component of the public safety broadband network? Is it reasonable to require the D Block licensee to ensure some degree of comparability of costs for public safety end users if the D Block licensee relies upon Mobile Satellite Service to fulfill a network build-out requirement? How could such comparability be defined and enforced?

103. We also seek comment on whether there are other terrestrial or non-terrestrial technologies or services that the D Block licensee may utilize to satisfy its performance requirements.

124

We reiterate the questions asked of Mobile Satellite Services above with regard to other such non-terrestrial technologies, and we seek comment on the costs and benefits of such technologies, particularly in comparison to Mobile Satellite Service, and whether permitting the use of such technologies to satisfy in part the D Block licensee's performance requirements would raise any other issues that should be addressed by the Commission.

124

See,

e.g.

, Letter from Gerald Knoblach, CEO, Space Data Corporation, to Marlene H. Dortch, Secretary, FCC, AU Docket No. 07-157, ET Docket No. 04-186,

Ex Parte

(filed April 29, 2008) (arguing that wide area technologies such as Space Data's SkySite Platforms, which “create a wireless network consisting of transceivers on weather balloons that operate in near space from 60,000 to 100,000 feet,” can “address issues associated with build-out and landmass coverage for the 700 MHz D Block. * * *”); Interoperable Communications: Hearing Before the H. Subcomm. on Telecommunications and the Internet, 110th Congress (2008) (statement of Robert F. Duncan, Rear Admiral, United States Coast Guard (ret.), Senior Vice President, Rivada Networks).

See also

Letter from Cheryl A. Tritt, Counsel to Space Data Corp., to Marlene H. Dortch, Secretary, FCC, WT Docket Nos. 96-86, 05-211, and 06-150, PS Docket No. 06-229, AU Docket No. 07-157,

Ex Parte Notice

(filed Oct. 24, 2007).

104. We further seek comment on whether, to reduce the cost of meeting our build-out requirements, we should adopt rules to promote or facilitate access by the D Block licensee to public safety towers and/or rights of way, and if so, what measures would be appropriate? We might, for example, obligate the licensees in the 700 MHz Public/Private Partnership to make “reasonable, good-faith efforts to obtain access” to both public safety towers and public safety rights of way, as earlier proposed by one party in this proceeding.

125

We seek comment on this option, and on whether measures should be adopted to provide public safety entities with some degree of obligation or incentive to provide such access. Commenters proposing such a measure should also discuss the Commission's authority to adopt it. Alternatively, should we clarify that the D Block licensee has flexibility to provide this type of incentive, such as by agreeing to reduced rates for services to public safety entities that provide access to their towers, and otherwise leave the issue to be negotiated between the two licensees and the relevant public safety entities? Are there impediments that might limit the ability of public safety entities to enter into such arrangements? If so, what steps can the Commission take to address such impediments that are within its authority and consistent with the public interest?

125

See

Notice by Frontline Wireless, LLC, WT Docket No. 06-150 and 06-169, PS Docket No. 06-229 (filed Mar. 27, 2007), Draft Rules at 5.

105. Finally, as an alternative approach for establishing construction requirements, we seek comment on whether we should employ a “two tiered” build out obligation, such that the D Block licensee would be allowed to incrementally enhance its network. Under this approach, the D Block licensee could satisfy its “first tier” build out requirement by meeting a subset, or some lower-cost aspects, of the technical requirements we adopt for the public-private partnership, and later enhance the network to meet public safety needs. The D Block licensee would then be required to satisfy a “second tier” requirement and fully upgrade portions of the network to meet all technical requirements adopted for the shared wireless broadband network based on certain temporal and/or public safety take-rate-based triggering mechanisms. Would adopting this two tiered performance requirement serve our goals to ensure a commercially viable opportunity for the D Block licensee to construct a shared wireless broadband network suitable for public safety use? If so, what “first tier” requirements or capabilities should the D Block be required to meet? When should the D Block licensee be required to fully upgrade to the entire set of

technical requirements? Should we specify a certain amount of time following each construction benchmark, or after a certain take-rate is achieved by public safety entities?

b. Respective Roles and Responsibilities of the D Block Licensee and Public Safety Broadband Licensee With Regard to Construction, Management, Operations, and Use of the Network

106. In adopting the 700 MHz Public/Private Partnership in the

Second Report and Order,

we sought to delineate the respective roles and responsibilities of the D Block licensee and the Public Safety Broadband Licensee in a manner that would ensure that the construction and operation of a shared, interoperable broadband network infrastructure that operated on the 20 megahertz of spectrum associated with the D Block license and the Public Safety Broadband License and that served both the needs of commercial and public safety users.

126

Under this plan, the D Block licensee and its related entities would finance, construct, and operate the shared network,

127

while the Public Safety Broadband Licensee would represent the interests of public safety community and ensure that the shared network meets their needs.

128

126

See,

e.g.

, 22 FCC Rcd at 15426 ¶ 383, 15431 ¶ 396.

127

See,

e.g.

,

id.

at 15428 ¶ 386, 15431 ¶¶ 395-96, 15432 ¶ 399, 15437 ¶ 415, 15441 ¶ 425, 15445-46 ¶¶ 437-43, 15450 ¶ 457, 15449 ¶ 452, 15467 ¶ 517.

128

See,

e.g.

,

id.

at 15421-25 ¶¶ 373-75, 15426-27 ¶ 383, 15433-34 ¶ 405, 15437-38 ¶ 416.

107. In establishing the 700 MHz Public/Private Partnership, we determined that promoting commercial investment in the build-out of a shared network addressed the most significant obstacle to constructing a public safety network—the limited availability of public funding.

129

We concluded that providing for a shared infrastructure would help achieve significant cost efficiencies, provide the public safety community with priority access to commercial spectrum during emergencies, and speed deployment of a nationwide interoperable broadband network for public safety. At the same time, by providing the D Block licensee with rights to operate commercial services in the 10 megahertz of public safety broadband spectrum on a secondary, preemptible basis, this partnership would help defray the costs of build-out and ensure that the spectrum is used efficiently.

130

129

Id.

at 15431 ¶ 396.

130

Id.

108. We stated that the D Block licensee would have the “exclusive right and obligation to build out the shared network,” using both the spectrum associated with the D Block license as well as the public safety broadband spectrum leased from the Public Safety Broadband Licensee.

131

We determined that providing for “commercial operations” on the public safety broadband spectrum, on a secondary and preemptible basis, was “an integral part of a viable framework for enabling the 700 MHz Public/Private Partnership to finance construction of a nationwide, interoperable public safety broadband network.”

132

We also afforded the D Block licensee “operational flexibility” in using the leased spectrum to provide “an appropriate balance between the commercial and public safety operations in the public safety broadband spectrum.”

133

We stated that the spectrum leasing component of the partnership “permits the D Block licensee to construct a network to serve its business needs, yet preserves the network infrastructure required for primary public safety use in the Public Safety Broadband Licensee's band.”

134

We considered the D Block licensee's commercial operations throughout the 20 megahertz band of spectrum, including operations on a secondary basis with regard to public safety spectrum, as a necessary condition in order to “harness private sector resources to facilitate construction of a nationwide interoperable public safety broadband network.”

135

131

Id.

at 15432 ¶ 399.

See also,

e.g.

,

id.

at 15450 ¶ 457; 47 CFR 27.1303.

132

Id.

at 15437 ¶ 416.

133

Id.

at 15438 ¶ 417.

134

Id.

135

Id

. at 15438 ¶ 419.

109. Meanwhile, in the

Second Report and Order

we provided that the Public Safety Broadband Licensee's responsibilities would center around directly representing the public safety interests with respect to the 700 MHz Public/Private Partnership, negotiating on their behalf with the winning bidder of D Block license and ensuring that their interests are met in the NSA.

136

Among other things, as discussed above, we provided that no commercial interest may be held in the Public Safety Broadband Licensee, that no commercial interest may participate in the management of the licensee, and that the licensee must be a non-profit organization.

137

We assigned various general responsibilities that we considered in keeping with the Public Safety Broadband Licensee's responsibilities, as discussed more fully below. We afforded the Public Safety Broadband Licensee “significant flexibility and control in connection with the construction and use of the nationwide broadband public safety network,” while at the same time we sought “to balance that discretion with the concurrent and separate responsibilities” of the D Block licensee.

138

136

Id.

at 15437 ¶ 416 (role of the Public Safety Broadband Licensee “in ensuring that the public/private network established pursuant to the 700 MHz Public/Private Partnership serves the interests of public safety”), 15438 ¶ 417 (Public Safety Broadband Licensee, through its spectrum leasing arrangement with the D Block licensee, “has the regulatory means (and obligation) to preserve the fundamental public safety function of the band”).

137

Id.

at 15421-22 ¶¶ 373-374.

138

Id.

at 15426 ¶ 383.

110. Finally, we provided some guidance on the service fees that the D Block licensee could charge public safety users for their access to the shared network, both for “normal network service” using the public safety broadband spectrum and for priority access to the D Block spectrum.

139

We required that these fees, to be negotiated by the winning bidder of the D Block license and the Public Safety Broadband Licensee, be specified in the Network Sharing Agreement.

140

In addition, we indicated that the Public Safety Broadband Licensee, as part of its administration of public safety access to the shared wireless broadband network, might assess “usage fees to recoup its expenses and related frequency coordination duties.”

141

139

Id.

at 15448-49 ¶¶ 450-52.

140

Id.

at 15448 ¶ 450.

141

Id.

at 15426 ¶ 383.

111. Below, we seek comment on whether we should clarify or revise the roles and responsibilities relating to the D Block licensee and the Public Safety Broadband Licensee. We also seek comment on whether we should clarify or revise the guidance or requirements relating to fees, including both service fees and spectrum usage fees. Finally, we seek comment generally on whether additional revisions or clarifications regarding the construction, operation, management, or use of the shared network would help ensure that the goals of the 700 MHz Public/Private Partnership are achieved.

(i) Role and Responsibilities of the D Block Licensee

112.

Background.

As discussed above, the D Block licensee is generally responsible for financing, construction, and operation of the shared network, which will serve both commercial users and public safety users. Also as noted above, we considered the D Block

licensee's “commercial operations” throughout the 20 megahertz band of spectrum as a necessary condition in order to “harness private sector resources to facilitate construction” of the network.

142

142

Id.

at 15439 ¶ 419.

113.

Discussion.

We invite comment on whether additional clarity with regard to the role and responsibilities of the D Block licensee would be helpful to ensure that the 700 MHz Public/Private Partnership achieves its goal in creating a shared, interoperable broadband network. We further seek comment on the appropriate extent of the relationship between the D Block licensee and individual public safety entities with regard to either the establishment of service with those entities or ongoing customer care and billing, bearing in mind the role and responsibilities of the Public Safety Broadband Licensee, which we discuss below.

114. As we have indicated, the ability of the D Block licensee to finance construction of the shared network is critical. Have we established sufficient and appropriate incentives in the 700 MHz Public/Private Partnership that ultimately will enable the D Block licensee to finance and construct the shared network as contemplated? Are there additional steps we can take, or further clarifications, that would improve the likelihood of the success for this partnership?

115. With respect to management and operations of the network, we expect that the D Block licensee will establish a network operations system to support the network infrastructure that it deploys and uses to serve its commercial customers. Such network operations functions typically include a network operations/monitoring center, billing functions, customer care, and similar functions. Should these network operations functions be viewed, much like the build-out of a common network infrastructure, as responsibilities to be assumed solely by the D Block licensee for the benefit of both its commercial customers and the public safety users represented by the Public Safety Broadband Licensee? If the D Block licensee were to assume all traditional network service provider operations, would this better enable the Public Safety Broadband Licensee to administer access to the national public safety broadband network by individual public safety entities, coordinate frequency usage, assess usage fees, and exercise its sole authority to approve equipment and applications for use by public safety entities?

116. We also seek comment on the factors that will affect and determine the D Block licensee's commercial operations and anticipated profitability. Commenters are encouraged to be as specific as possible and to provide detailed projections and figures where possible. What types of commercial customers can the licensee be expected to serve (e.g., critical infrastructure industries, commercial wireless carriers seeking additional spectrum or roaming capacity, commercial wireless customers, automotive companies and service providers, large enterprise customers)? How might current trends and recent developments in the commercial wireless market and the general financial markets affect the D Block licensee's financial model?

(ii) Role and Responsibilities of the Public Safety Broadband Licensee

117.

Background.

As discussed above, the Public Safety Broadband Licensee generally is charged with representing the interests of the public safety community to ensure that the shared interoperable broadband network meets their needs. In the

Second Report and Order

, we assigned the following responsibilities to the Public Safety Broadband Licensee concerning its partnership with the D Block licensee:

• General administration of access to the national public safety broadband network by individual public safety entities, including assessment of usage fees to recoup its expenses and related frequency coordination duties.

• Regular interaction with and promotion of the needs of the public safety entities that would utilize the national public safety broadband network, within the technical and operational confines of the NSA.

• Use of its national level of representation of the public safety community to interface wit

This text is long and has been trimmed here. Open the source document for the complete record.

This is a copy of a public record, reproduced as it was published. It is not legal advice, and it may not be the version a court would rely on. Check the official source before you cite it.

A word about cookies

We need a few to keep you signed in and the library working. The rest help us see which pages people use and where they get stuck. They stay off unless you say yes.