Loren Data's SAM Daily™

FBO DAILY ISSUE OF MAY 20, 2007 FBO #2001
MODIFICATION

58 -- 700MHz Wireless Broadband

Notice Date

5/17/2007
 

Notice Type

Modification
 

NAICS

517212 — Cellular and Other Wireless Telecommunications
 

Contracting Office

Department of Commerce, National Oceanic and Atmospheric Administration (NOAA), Mountain Region Acquisition Division, 325 Broadway - MC3, Boulder, CO, 80305-3328, UNITED STATES
 

ZIP Code

00000
 

Solicitation Number

Reference-Number-NISTOLES00001JW
 

Response Due

6/22/2007
 

Archive Date

7/7/2007
 

Point of Contact

Jacqueline Wright, Contract Specialist, Phone (303) 497-5282, Fax (303) 497-3163, - Nancy Gertler, Contracting Officer, Phone 303-497-5133, Fax 303-497-3163,
 

E-Mail Address

Jacqueline.S.Wright@noaa.gov, nancy.gertler@noaa.gov
 

Description

700MHz Wireless Broadband The National Institute of Standards and Technology Office of Law Enforcement Standards (NIST/OLES), Boulder Laboratories, Boulder CO, is in the process of analyzing wireless broadband technologies for use by public safety agencies in the 700MHz spectrum. The first step in this process is to determine what companies offer products that may fulfill the needs of public safety. This is a Request For Information (RFI) announcement and NOT A SOLICITATION. Respondents are not limited to NAICS Code 517212. The responses provided by the vendors will allow us to compile the necessary information to help public safety make informed choices on broadband equipment as well as help NIST/OLES better understand the available technologies better. Disclaimer It should be fully understood by all companies who provide responses to this document that this is in no way is an endorsement from NIST/OLES. The information given to NIST/OLES is strictly for research purposes. At no time should press releases or any type of sales brochures references be made with regards to this process. It should also be understood that any and all information provided, unless specifically noted by the company, will eventually be made available to the public safety community. If specific information is covered by an existing NDA, this should be clearly described in the reply. Spectrum 24MHz of spectrum has been allocated to public safety use. This spectrum is a result of digital television channel clearing that is taking place and will be completed nationwide by 2009. The proposed FCC rulings allocate 12MHz of paired spectrum (24MHz total) for nationwide public safety use. Public Safety broadband will occupy 5~6MHz per channel (10~12MHz total) of the 24MHz allocated. The FCC has many proposals that have been submitted for comment. In general the broadband frequencies cover the following spectrum and any equipment specified in the RFI should be able to operate within this frequency range. ? First band covers 763 ? 776MHz (Typically Basestation Tx) ? Second band covers 793 ? 806MHz (Typically Basestation Rx) NOTE: Broadband references channel sizes greater than 1Mhz The 700MHz A, C & D blocks are spectrum that may be auctioned off for commercial use or for use in a public/private trust for public safety broadband use. There are several proposals for use of this spectrum from industry. At the time of this RFI it is unknown what the outcome will be on these spectrum blocks. However, it should be noted that whatever analysis and recommendations are created from this project will, and should, be compatible and interoperable within this spectrum block. Wireless Broadband Technologies Several known technologies could satisfy the needs in this spectrum ? others may be viable but are not part of this project scope. It is the desire to take advantage of COTS products and the economies of scale to help advance the technology into the marketplace quicker and reduce costs to public safety. ? IEEE 802.16e ?Mobile WiMax? o Both Time Division Duplex (TDD) and Frequency Division Duplex (FDD) should be considered ? IEEE 802.11xx ?Mobile WiFi? ? IS-856 ?EV-DO Revision A & B? ? 3GPP2 ?UMB ? Ultra Mobile Broadband? or EV-DO Revision C ? 3GPP Release 5/6 ?WCDMA, UMTS, HSPA? o Both TDD and FDD should be considered ? 3GPP Release 8 ?LTE ? Long Term Evolution? o Both TDD and FDD should be considered IP Convergence The RFI is inclusive of the entire ecosystem required for a broadband network. In addition to the radio technologies being investigated, the IP ?backbone? is also being explored. Due to potential frequency spectrum issues and the cost of deploying a nationwide wireless network ? the broadband network will need to be shared across agencies and likely jurisdictions. The convergence of subscriber user information, applications and overall IP access will need to take place. There seems to be overall acceptance of the IP Multimedia Subsystem (IMS) architecture by the prevailing broadband standards bodies. Request For Information Questions The next nine sections contain questions and requirement statements on the specific information we need to gather on 700MHz broadband equipment. Please provide as much information about your current or future products that can address these questions and statements. Minimum Feature & Functionality Requirements The following chart is an example of the typical wireless data services required by public safety. This is only an example is not necessarily representative of all of the wireless data requirements for public safety. Please note that the information provided should be for packet switched data networks only. Circuit switched services and data are not part o this RFI. Figure 2 1. Infrastructure and subscriber devices must operate in the 700MHz spectrum as noted in the previous section. Center channels shall be 765.25MHz and 794.75MHz respectively. 2. Full mobility from pedestrian to 160 km/hr, including seamless handover/handoff without loss of data (including streaming media and VOIP) as observed by the user a. Maximum 2% Packet Loss can be assumed b. 1% Blocking Probability can be assumed c. Maximum 30% soft/softer handoff can be assumed 3. Meet the throughput requirements for public safety for various applications, even at the edge of coverage (cell edge) 4. Support end-to-end Quality of Service - QoS (based on application and/or users) 5. Full system Operations and Maintenance (O&M) to all network nodes 6. Support end-to-end multicast/broadcast both on uplink and downlink (1 to many) 7. Integrated AAA and HSS functionality. Should support multiple user profiles and provide AES encryption and key management. 8. Over the air service programming and re-keying 9. Scaleable infrastructure for very small rural systems to large metro/urban systems 10. Ten year Mean Time Before Failure (MTBF) Cost In order to determine general cost of the network for budgetary purposes, there are several pricing factors that need to be known. Any pricing information shall be general in nature, and will be used to help the Government formulate an independent cost estimate. Pricing will not be negotiated or considered at this time. 1. System dimensioning rules for the network and their interfaces, including but not limited to: a. Air interface and its spectrum requirements b. Base station/access point/radio sites c. Backhaul d. Radio Network Controllers , Base Station Controllers, OSS, ASN e. GPRS Node or PDSN (Home Agent) ? Mobile IP will need to be supported f. IMS ? including CSCF, HSS (including AAA functionality), SLF, AS, BGCF, MRF, PSTN/CS Gateway, MGW 2. Provide the cost of each component of the network and also the incremental costs to increase system capacity. 3. The network elements? costs will include the redundant parts (cards, interfaces, etc.) that will avoid single point of failures. N+1 redundancy schemes are preferred 4. Provide any performance and capabilities of the vendor?s implementation of broadband wireless technologies. 5. Provide information on when the various components and technology will be available. Air Interface 1. Provide the bandwidth for one channel. If it is a FDD technology provide both uplink and downlink channel sizes and minimum spacing required for transmit and receive bands. 2. If the proposed technology has several channel bandwidth options, please answer this section?s questions for each of those options when applicable. 3. What is the required guard band to meet out of band emissions limitations of the 700MHz band (76 + 10 log (P) dB in a 6.25 kHz band segment) for the ?typical? base station? 4. What is the required guard band to meet out of band emissions limitations of the 700MHz band (65 + 10 log (P) dB in a 6.25 kHz band segment) for the ?typical? subscriber device? 5. What is the minimum number of channels required to deploy a Jurisdictional Area Network (JAN) or wide area wireless broadband network using the proposed technology? 6. What is the minimum frequency reuse for the proposed technology? 7. What is the recommended frequency reuse for the proposed technology? 8. Provide a curve depicting a single user link, the throughput achieved as a function of Signal-to-Noise Ratio (Eb/No) for the downlink. 9. Provide a curve depicting a single user link, the throughput achieved as a function of Signal-to-Noise Ratio (Eb/No) for the uplink. 10. Provide a curve depicting a BER and or PER versus Signal-to-Noise Ratio (Eb/No) for the uplink. 11. Provide for SNR (C/N) = 0dB, 5 dB, 8 dB, 10 dB, 15 dB the aggregated throughput achievable per sector for 1 user, 5 users, 10 users, 20 users, 30 users for the uplink. 12. Provide for SNR (C/N) = 0dB, 5 dB, 8 dB, 10 dB, 15 dB the aggregated throughput achievable per sector for 1 user, 5 users, 10 users, 20 users, 30 users for the downlink. 13. Based on optimum frequency reuse, for each data service offered on the uplink, provide a link budget assuming a 30% load & 70 % load. 14. Provide an aggregated uplink throughput for the sector. To how many users does this throughput correspond to? 15. Based on optimum frequency reuse, for each data service offered on the downlink, provide a link budget assuming a 30% load & 70 % load. 16. Provide the maximum achievable throughput for one user at cell-edge (with cell-edge defined as the point where two different sectors, from non-co-located sites, have equal power). 17. Provide the maximum achievable aggregated throughput for multi-users at cell-edge. To how many users does this throughput correspond to? 18. Provide information on what geographic information system is inherent to the technology. (i.e. not relying on an external technology such as GPS) or will be available; specifically give details (including vertical and horizontal accuracy). 19. Is the ability to use a RF repeater supported? Indicate if the vendor?s implementation can support in-band coverage (i.e. within the core network?s frequency use). 20. Provide detail on QoS mechanisms within the air interface. 21. Provide detail on how broadcast and multicast functionality is achieved on the uplink and downlink. 22. Provide any formulas/graphs/whitepapers showing spectral efficiency for the proposed technology. a. Please provide the link spectral efficiency (bit/s/Hz) for each technology proposed. b. Please provide the net bit rate per channel for each technology (throughput and goodput) in Mbit/s and if possible the system spectral efficiency (bit/s/Hz/sector). Base Station/Access Point (BTS) The term Base Station Transceiver (BTS) will be used generically to describe the radio interface. ex. Node B, Access Point, Radio Node 1. Please provide overall physical/mechanical information on your BTS for each technology. (weight, size, power supply AC/DC requirements?etc) 2. Please provide details on peak data throughput performance. 3. Does your BTS support multiple sectors? 4. How many sectors can a BTS support? 5. How many carriers can a BTS support per sector? 6. What is the cost of a BTS with one sector, one carrier? 7. What is the cost of a BTS with three sectors, one carrier? 8. What is the cost of a BTS with three sectors, three carriers? 9. Does your BTS offer different RF power output options or power amplifiers? 10. What is the RF power output per channel/carrier? 11. Describe your support for MIMO and if supported when it will be available? If details about your specific MIMO implementation are available please provide those also and how they affect the link budget. 12. Indicate what backhaul interfaces are supported in your BTS? (Mesh, T1, E1, Satellite?etcetera). 13. Is the protocol used on the backhaul interface proprietary or open interface ? please provide a detailed description. 14. Provide any n+1 redundancy options available for your BTS. 15. List and explain cost differentials that affect the overall cost by more than 5% Controller; if applicable (RNC, BSC, ASN, etc.) 1. Please provide overall physical/mechanical information on your controller for each technology. (weight, size, power supply AC/DC requirements?etc) 2. If applicable please describe and provide detail on interconnection and the functionality between multiple controllers. a. What is the maximum number of controllers that can be linked together? 3. What is the maximum throughput manageable by a controller (uplink and downlink) 4. What is the maximum throughput for each BTS through the controller? 5. What is the maximum number of BTS? / sectors a controller can support? 6. What is the maximum number of simultaneous users a controller can support? 7. Is the controller scaleable for amount of BTS?, throughput or other factors? a. If so provide the different configurations and their costs (be sure to indicate all dimensioning parameters). b. What is the cost of a controller supporting 10 BTS, 2000 users? c. What is the cost of a controller supporting 50 BTS, 10,000 users? d. What is the cost of a controller supporting 100 BTS, 20,000 users? e. What is the cost of a controller supporting 500 BTS, 50,000 users? 8. List or describe (as applicable) the maximum number of simultaneous handoff/handovers for each configuration and the rate at which they can occur. 9. What vocoders do you support? Core network elements The elements that make up the IMS core network (CSCF, HSS, etc.) 1. Please provide overall physical/mechanical information on your IMS for each technology component. (weight, size, power supply AC/DC requirements?etc) 2. Provide detailed information on the following: (HW, SW, SIP & protocol configuration, cost, availability, support for multiple protocols?etc) a. CSCF ? Call/Session Control Function (Proxy, Interrogating, Serving) b. HSS ? Home Subscriber Server c. AAA ? If included in HSS please provide overall product description d. MRFC ? Media Resource Function Controller e. MRFP ? Media Resource Function Processor f. BGCF ? Breakout Gateway Control Function g. MGCF ? Media Gateway Controller Function h. MGW ? Media Gateway i. SGW ? Signaling Gateway j. AS ? Application Server (PoC, LBS..etc) ? Please provide specific details on application software (e.g. video server) as applicable. k. GPRS/PDSN ? As applicable to the IMS and RAN implementation 3. What is the maximum throughput manageable by the core network elements (uplink and downlink)? 4. Is the IMS core scaleable for amount of BTS?, throughput or other factors ? provide details? a. Provide information of the parameters that impact the dimensioning of the core network elements, and the thresholds that trigger the implementation of hw/sw when those parameters increase, and the associated costs 5. What is the maximum number of BTS? / sectors the core network elements can support? 6. What is the maximum number of users the IMS core network elements can support? a. What is the cost of core network elements supporting 10 BTS, 2000 users? b. What is the cost of core network elements supporting 50 BTS, 10,000 users? c. What is the cost of core network elements supporting 100 BTS, 20,000 users? d. What is the cost of core network elements supporting 500 BTS, 50,000 users? 7. What encryption implementations are supported and available? 8. Can any elements support n+1 redundancy ? if so please list them? 9. Several standards bodies describe gateway interfaces from the access network to the IMS network. Please provide details on the following: a. WAG ? Wireless Access Gateway b. PDG ? Packet Data Gateway 10. Provide details on QoS implementation and levels of QoS. List any specific applications as necessary. O&M elements The elements that allow the management of the network elements 1. Can O&M be managed for the RAN and IMS from a single interface or does each node require its own interface? 2. What is the maximum amount of nodes the O&M interface can support? a. What is the maximum number of BTS? / sectors the O&M elements can support? b. What is the maximum number of users the O&M elements can support? 3. What user levels are supported on the O&M interface? a. Provide information of the parameters that impact the dimensioning of the O&M elements, and the thresholds that trigger the implementation of hw/sw when those parameters increase, and the associated costs b. What is the cost of O&M elements supporting 10 BTS, 2000 users? c. What is the cost of O&M elements supporting 50 BTS, 10,000 users? d. What is the cost of O&M elements supporting 100 BTS, 20,000 users? e. What is the cost of O&M elements supporting 500 BTS, 50,000 users? 4. What external interfaces for O&M are supported (SNMP..etc)? 5. Can all system provisioning take place from the O&M interface ? provide details? 6. Can all system upgrades take place from the O&M interface ? provide details? Network Architecture The 700MHz public safety broadband network will likely be based upon a mobile IP (MIP) network and will require a higher level of redundancy than typical wireless networks. The use of IPv6 is the preferred option and to deploy with this type of implementation. All network equipment must be upgradeable to IPv6 from IPv4. It is understood that IP migration may need to take place. Please provide any information pertinent to this subject. Most of the architecture for wireless and cellular based networks do not provide redundancy for the IP network. The project is also investigating the concept of a ?flat IP? implementation. A ?flat? network would have the home agent (HA) at the network edge ? likely collocated within the BTS. This would allow significant IP routing capabilities and support the use of multiple backhaul facilities (fiber, microwave) and offer another level of redundancy to support redundant core networks. Please provide any information pertinent to a ?flat IP? network implementation. 1. Provide a network or system architecture diagram showing interconnects from the BTS through to the core network. 2. What QoS levels are supported 3. Provide end to end call setup and teardown delays for different QoS levels 4. Provide details on broadcast and multicast services/channels a. How is the message structure setup b. How are the channels managed differently c. What impact on capacity does using this service have 5. What priority access levels are allowed in the proposed system and how are they implemented? 6. Provide information on how the proposed system would handle the following priority and overload condition issue: In a single sector of coverage you have a large number of users. The number of users is much, much larger than what the system is designed. In an emergency/overload situation where everyone in sector tries to setup a call at nearly the same time how does the system handle this and in particular: a. If the ?access channel? (used generically) is overloaded with requests, how are collisions avoided or mitigated? b. How are users with priority access (public safety) given that priority access when this situation happens? Subscriber Options 1. Do you manufacture subscriber devices for each protocol proposed? Provide details on availability and cost. a. If you do not manufacture devices please provide any vendors that you interoperate with. 2. What type of subscriber devices are available for each protocol proposed? (PDA, handheld/cell phone form factor..etc) a. Do you or will you have available ?ruggedized? devices e.g. MIL-STD801F...etc. 3. What is the RF output and RX sensitivity for each subscriber device? a. Will a ?high? power mobile subscriber device be available? (e.g. Class I Mobile Station Class 4dBW ERP) b. If no ?high? power device is currently forecasted or planned, address the feasibility of modifications to standards to support such a mode. 4. Do you support authentication in the subscriber device? a. Provide details on interface (R-UIM, SIM?etc) 5. What encryption is available on the subscriber devices? 6. Indicate whether direct peer-to-peer communication in the absence of infrastructure is or will be supported between access terminals or handsets; provide details, e.g. mode of communication, in-band. a. If no peer-to-peer communication is currently forecasted or planned, address the feasibility of modifications to standards to support such a mode. 7. What vocoders do you support? Request For Information Response The responses to this Market Research document are due no later than June 8, 2007. Responses/questions should be sent to the attention of the Contract Specialist, Jacqueline Wright @ email jacqueline.s.wright@noaa.gov. Acronyms 3GPP ? Third Generation Partnership Project 3GPP2 ? Third Generation Partnership Project 2 AAA ? Authentication Authorization Accounting AC/DC ? Alternating Current/Direct Current AES - Advanced Encryption Standard ANC ? Access Network Controller AS ? Application Server BER ? Bit Error Rate BGCF ? Breakout Gateway Control Function BOP ? Broadband Optimization Plan BSC ? Base Station Controller BTS ? Base station Transceiver System COTS ? Common Off The Shelf CS ? Circuit Switched CSCF ? Call Session Control Functions E1 ? E-carrier level 1 EAN ? Extended Area Network Eb/No ? Energy per bit/Noise ERP ? Effective Radiated Power EVDO ? Evolution Data Only FA ? Foreign Agent FCC ? Federal Communications Commission FDD ? Frequency Division Duplex GPRS ? General Packet Radio Service GPS ? Global Positioning System HA ? Home Agent HSPA ? High Speed Packet Access HSS ? Home Subscriber Server HW ? Hardware IAN ? Incident Area Network IEEE ? Institute of Electrical and Electronics Engineers IMS ? IP Multimedia Subsystem IP ? Internet Protocol JAN ? Jurisdiction Area Network LBS ? Location Based Service LTE ? Long Term Evolution MGW ? Media GateWay MHz ? Megahertz MIMO ? Multiple Input Multiple Output MIP ? Mobile IP MRFC ? Media Resource Function Controller MRFP - Media Resource Function Processor MTBF ? Mean Time Before Failure NDA ? Non Disclosure Agreement NIST ? National Institute of Standards O&M ? Operation & Maintenance OLES ? Office of Law Enforcement Standards PDA ? Personal Digital Assistant PDG ? Packet Data Gateway PDSN ? Packet Data Switched Network PER ? Packet Error Rate POC ? Push to talk On Cellular PSTN ? Public Switched Telephone Network QoS ? Quality of Service RAN ? Radio Access Network RF ? Radio Frequency RNC ? Radio Network Controller R-UIM ? Removable User Identity Module SGW ? Signaling Gateway SIM ? Subscriber Identity Module SIP ? Session Initiation Protocol SLF ? Subscriber Locator Function SNR ? Signal to Noise Ratio SW ? Software T1 ? Transmission level 1 TDD ? Time Division Duplex UMB ? Ultra Mobile Broadband UMTS ? Universal Mobile Telephone System VoIP ? Voice Over IP WAG ? Wireless Access Gateway WCDMA ? Wideband Code Division Multiple Access WiFi- Wireless Local Area Network (brand name) References Figure 1: ?Second Report of the 700 MHz Technical Working Group?, January 26, 2007 Figure 2: Various reference material from ?Request For Information ? 700MHz Wireless Wide-Area Networks?, 12 September 2005, Version: 3.1 Respondents to this RFI shall identify their company name, address, email address, telephone number and a point of contact having the authority and knowledge to clarify responses. This is ONLY Market Research, no RFP, RFQ, or IFB will be issued to this response. NOTE: THIS NOTICE WAS NOT POSTED TO FEDBIZOPPS ON THE DATE INDICATED IN THE NOTICE ITSELF (17-MAY-2007). IT ACTUALLY APPEARED OR REAPPEARED ON THE FEDBIZOPPS SYSTEM ON 18-MAY-2007. PLEASE CONTACT fbo.support@gsa.gov REGARDING THIS ISSUE.
 

Place of Performance

Address: DOC/NIST/MRAD, M/S MC3, 325 Broadway, Boulder, CO

Zip Code: 80305

Country: UNITED STATES
 

Record

SN01298555-W 20070520/070518222153 (fbodaily.com)
 

Source

FedBizOpps Link to This Notice
(may not be valid after Archive Date)

---

| FSG Index  |  This Issue's Index  |  Today's FBO Daily Index Page |