Loren Data's SAM Daily™

fbodaily.com
Home Today's SAM Search Archives Numbered Notes CBD Archives Subscribe
FBO DAILY - FEDBIZOPPS ISSUE OF AUGUST 28, 2014 FBO #4660
SOLICITATION NOTICE

58 -- LTE Radio Access Network (RAN) load tester. - Synopsis/Solicitation

Notice Date
8/26/2014
 
Notice Type
Cancellation
 
NAICS
541512 — Computer Systems Design Services
 
Contracting Office
Department of the Army, National Guard Bureau, USPFO for Colorado, Attn: Mail Stop 53, 660 South Aspen Street, Building 1005, Aurora, Colorado, 80011-9511
 
ZIP Code
80011-9511
 
Solicitation Number
NB620010-14-03472
 
Point of Contact
Marc Zurasky, Phone: 3034973246
 
E-Mail Address
marc.zurasky@nist.gov
(marc.zurasky@nist.gov)
 
Small Business Set-Aside
N/A
 
Description
This is the Statement of Work. Please follow. This is a detailed Evaluation Criteria, please follow. This is the Synopsis / Solicitation. RAN Load Tester Evaluation Criteria - BLDRNB620010-14-03472 PSCR will evaluate the RAN load tester based on the equipment specifications in the statement of work as follows: The RAN load tester must support all LTE 700MHz bands PSCR will perform tests using band class 14 eNodeBs. The RAN load tester must have proven interoperability with at least 3 leading LTE eNodeB manufacturers. The RAN load tester must be guaranteed to interoperate with all eNodeB vendors in use by PSCR PSCR will perform tests using an eNodeB selected by PSCR and verify interoperability. The RAN load tester vendor will supply a list of eNodeB manufacturers with which their equipment has been proven to interoperate. The RAN load tester vendor must provide a plan for solving any interoperability issues discovered by PSCR during the term of the support contract. The RAN load tester must support 3GPP releases 8, 9 and 10. Support for 3GPP releases 11 and 12 must be on the roadmap for the product. PSCR will perform tests using eNodeBs that are certified compliant to 3GPP release 10. The RAN load tester vendor will certify that 3GPP releases 11 and 12 are on the roadmap. The RAN load tester must be able to test 2 eNodeB cells simultaneously including handover between two cells on the same LTE band or different LTE bands. The two cells may be on one eNodeB or separate eNodeBs PSCR will perform tests where a handover is attempted between cells of band 14 eNodeB equipment. The vendor will certify that handovers are supported in and between other 3GPP bands. The RAN load tester must be able to simulate 400 UEs per sector on 2 sectors simultaneously PSCR will verify that all 400 simulated UEs are simultaneously attached to 2 sectors of a band 14 eNodeB. Simulated UEs must be able to simulate UE categories 2, 3 and 4. It must be possible to simulate groups of all available UE categories simultaneously during a single test. PSCR will verify that simulated UEs of categories 2, 3 and 4 can be attached and sustain downlink and uplink traffic. Simulated UEs must be able to use IPv4 or IPv6 addressing. PSCR will test using IPv4 addressing. The vendor will certify that IPv6 addressing is supported. The RAN load tester must be able to generate ping, UDP, TCP, FTP, HTTP, and VoLTE traffic on the UEs to simulate various applications. PSCR will test using all supported traffic types. The RAN load tester must be capable of using noncompressible (random) data for the generation of UDP, TCP and FTP traffic types. PSCR will use wireshark traces to verify that data appears to be random for the aforementioned traffic types. The RAN load tester must be capable of generating all traffic types in the uplink and downlink directions either simultaneously in both directions or one direction at a time. PSCR will verify that tests can be performed that send traffic downlink only, uplink only and in both directions at the same time. The RAN load tester must be capable of using uncorrelated up-link and downlink traffic for the generation of UDP, TCP and FTP traffic. PSCR will use wireshark traces to verify that uplink and downlink traffic can be sent that are uncorrelated with each other. The RAN load tester must be capable of testing LTE multi-operator core network (MOCN) features. This includes the ability to simulate groups of UEs using multiple PLMN IDs simultaneously and to allow each group of UEs to use an independent OP value for authentication. PSCR will provide two PLMN IDs and two OP values to be used simultaneously during testing. The RAN load tester must allow the simulated UEs using the IDs and OP values to attach to the same cell at the same time. Digits of a PLMN ID must be entered in the order supplied by PSCR. For example, if the mobile country code is 310, it is not acceptable to enter the digits in any other order than 3 followed by 1, followed by 0. The RAN load tester must allow each simulated UE to use a unique Ki value for authentication. PSCR will provide a list of unique Ki values for 800 UEs. It will be verified that all 800 UEs can attach (on 2 cells) at the same time. The RAN load tester must be able to test quality of service features of LTE. This includes the ability to request bearers with specific QCI parameters and to accept network assigned bearers with specific QCI parameters. PSCR will verify that up to eight bearers can be established on a single UE with varying QCI parameters. Guaranteed bit rate and non-guaranteed bit rate bearers will be tested. The RAN load tester must support reading of SIB messages in support of testing access class barring. PSCR will verify that the ability of a simulated UE to attach is affected by changes to eNodeB access class barring. Script changes to simulate the reading of SIB messages are not allowed. The RAN load tester must be able to test allocation and retention priority features of LTE The preemption of bearers under control of allocation and retention priority will be demonstrated. PSCR will verify that the RAN load tester can detect the time of preemption and number of bearers that have been preempted. Simulated UEs must be able to simultaneously use multiple APNs and bearers PSCR will provide the ability to use two APNs on a single simulated UE and verify that the RAN load tester can use both APNs simultaneously. APNs must be entered in human readable format (not hexadecimal). The RAN load tester must be able to create tests that will vary the number of UEs and over the air traffic for tests running up to 72 hours At the discretion of PSCR, equipment requiring reboots or restarts during the evaluation can be considered a failure. The RAN load tester must be capable of simulating UEs that support preamble formats 0, 1, 2 and 3. The vendor will certify that preamble formats 0, 1, 2 and 3 are fully supported. Detailed statistics must be provided at test completion to evaluate performance of eNodeB under test. Statistics must be recorded at intervals of 30 seconds or less during the test. Statistics must include (but are not limited to): Number of UEs attached Number of failed attaches Number of active bearers per UE group RRC messages sent and received RRC connection success rate NAS messages sent and received Amount of data sent and received IPv4 packets sent and received IPv6 packets sent and received PSCR will review logs from RAN load tester to verify completeness. The RAN load tester must support RF fading as a simulated UE moves within and between cells. The support of 3GPP fading models EPA5, EVA5, EVA70, ETU70, and ETU300 by the RAN load tester is desired. PSCR will verify through eNodeB logs and load tester logs that uplink and downlink signal levels vary appropriately as the simulated UE moves through near cell, far cell, and handover conditions. Operation of the RAN load tester must chiefly be accomplished through the use of a graphical user interface. Scripting or command line control must be kept to a minimum if used at all. Usage of scripting or command lines must be less than 5% of the effort to create and run tests. PSCR will use best judgement to determine the effort required for scripting or command lines. Technical support for one year including software updates and technical assistance must be included. The RAN load tester vendor will provide support contacts and timelines for resolving issues identified by PSCR. The equipment must have the capability to be expanded to at least 1000 UEs per sector and up to 12 sectors. The RAN load tester vendor will provide current costs for upgrading the system to 12 sectors with 1000 UEs per sector.
 
Web Link
FBO.gov Permalink
(https://www.fbo.gov/spg/USA/NGB/DAHA05/NB620010-14-03472/listing.html)
 
Place of Performance
Address: 325 Broadway, Boulder, Colorado, 80305, United States
Zip Code: 80305
 
Record
SN03481428-W 20140828/140826235816-8df2515d04742ec6956e613a6bfaf90b (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 |
ECGrid: EDI VAN Interconnect ECGridOS: EDI Web Services Interconnect API Government Data Publications CBDDisk Subscribers
 Privacy Policy  Jenny in Wanderland!  © 1994-2024, Loren Data Corp.