Draft Lab Spectrum Testing Modeling PWS.docx

Draft October 2015

Office of Operations

Performance Work Statement

For

Laboratory Spectrum Testing Modeling and Emulation

HOIT200091PR

1.0 Overview

This is a non-personal services contract to provide Next Generation Spectrum Research: Support spectrum testing modeling and emulation. The Government will not exercise any supervision or control over the contract service providers performing the services herein. Such service providers shall be accountable solely to the Contractor who, in turn is responsible to the Government as defined in this Performance Work Statement (PWS). The Contractor shall perform to the standards herein.

1.1 Background

The US Department of Transportation (USDOT), also called USDOT in this PWS, is seeking to utilize Northeastern’s Colosseum Radio Frequency (RF) Testbed to conduct complex spectrum research in the 5.9GHz Safety Band for Vehicle-to-everything (V2X) communications.

Safety Band is 75 MHz of radio spectrum (5.850-5.925 GHz) reserved specifically for transportation safety. In 1999, the FCC allocated this spectrum in 5.9 GHz range to be used by Intelligent Transportation Systems (ITS), which is currently being used by the Dedicated Short-Range Communication (DSRC) technology under the IEEE 802.11p standard (published in 2010). In parallel, the 3GPP has defined the Cellular V2X (CV2X) in Release 14 (published in 2017) and above, which is promising to be a more reliable system by supporting wide area communication over a cellular network (V2N) in addition to the medium- and short-range communication which are inherently supported by IEEE 802.11p.

The USDOT has developed a Planned Test Schedule to prepare for testing the safety and effectiveness of wireless devices designed to operate in the Safety Band. This Planned Test Schedule is mostly targeted for evaluation of the coexistence between the DSRC devices and the Unlicensed National Information Infrastructure (UNII-4) devices. Using field data and by utilizing the Colosseum, the USDOT is further seeking to model real-world RF spectrum scenarios for V2X technologies to assess critical performance metrics including safety, system efficiency, and mobility. Moreover, the USDOT is seeking to expand this research by adding the evaluation of safety, effectiveness, and scalability of the emerging CV2X technology (considering both the LTE and 5G NR devices), and its interoperability in co-presences of the DSRC and UNII devices. This real-world modeling is required to assess the safest and most efficient use in allocating the 5.9GHz spectrum and to accommodate transportation needs with repeatable test results. The test results and findings of this project will be used by USDOT to inform decision makers.

1.2 Objective

The purpose of the USDOT Spectrum Sharing analysis is to develop test procedures, establish urban, Manhattan grid, semi-urban and rural scenarios on Colosseum, and perform the necessary analyses by modeling real-world RF spectrum scenarios to evaluate coexistence between DSRC, CV2X and UNII devices.

1.3 Detailed Requirement

The Contractor shall provide all personnel, equipment, supplies, facilities, transportation, tools, materials, supervision, and other items and non-personal services necessary to achieve the following objectives:

A) To conduct Spectrum Sharing, LTE-CV2X Testing, and 5G NR Testing as outlined in the USDOT ITS-JPO’s Planned Test Schedule[footnoteRef:1] [1: The provided Planned Test Schedule does not include any test plans for the LTE-CV2X and 5G NR technologies. Therefore, a new plan should be drafted in consistence with the existing plan for the DSRC-UNII scenarios.]

B) Based on field data and emulated channel models, there is a need to model real-world communication conditions for

i) LTE-CV2X (based on the 3GPP LTE specifications and the emerging SAE J3016 standard) devices

ii) Dual-mode DSRC and LTE-CV2X devices

iii) 5G New Radio (5G NR) devices C) Modeling the coexistence between different types of V2X devices and the UNII devices

The controactor shall complete the following tasks in meeting the objectives stated above.

1.3.1 Project Management

The Contractor shall provide project management practices.

The Contractor’s Program Manager (PM) shall schedule a kickoff meeting with FHWA’s Contract Officer’s Representative (COR) within two weeks of the award date.

The Contractor shall submit a project management plan (PMP) which consists of but not limited to:

· Project scope

· Deliverables and Milestones

· Schedule (e.g. Gantt chart or equivalent timeline)

· Management and staffing plan

· Other relevant information

The PMP shall be submitted to the COR one week after the kickoff meeting. The Government will review materials and provide comments to the Contractor. The contractor shall submit a revised project management plan within one week after receiving comments from the Government.

The Contractor shall hold monthly conference calls with FHWA’s COR and FHWA GTMs, key personnel and only necessary personnel to discuss topics of immediate relevance to monitor progress.

The Contractor shall submit a monthly project progress report that includes costs and labor hours to date, accomplishments, anticipated activities for the next reporting period, and problems/issues and recommended actions.

1.3.2 Channel Modeling through Field-Test and Software Models The contractor shall develop new channel models for the technologies of interest. Field-test data for the DSRC-UNII scenarios will be provided by the USDOT from the outcomes of their previous project. For the LTE-CV2X and 5G NR scenarios, field-tests need to be conducted in collaboration with USDOT. The contractor shall submit the channel models to USDOT for approval. The contractor shall submit a draft outline of the channel models for review and feedback by the USDOT before submitting a final document describing the channel models.

To fulfill the required goals in the scope of current project, LTE and 5G NR channel models will be developed by the contractor by using software-based tools, which will be then utilized for generating scenarios in the test bed as explained in Task 1.3.3. The obtained field-data from DSRC-UNII tests and the software-based simulation data for LTE and 5G NR devices will be used to develop required channel models for each of the testable technologies. The channel models (if approved by USDOT) will then be used as the input for generating RF Scenarios for the testbed emulator in Task 1.3.3.

Note: For the DSRC-UNII analysis, a field-test is deemed to be already performed by USDOT. However, an in-depth documentation of the acquired test data is required to enable parsing the data and preparing it for the purposes of the RF Scenario definition which can be used as the input for the Colosseum channel emulator. Based on the level of convenience/feasibility of pre-processing the existing dataset, the same or a different format may be adopted for the new measurements of CV2X and 5G NR technologies in future.

1.3.3 Data Pre-processing, Custom Software Profiles for Vehicular Technologies and Scenario Generation The channel models that were developed and approved by USDOT in Task 1.3.2 will be evaluated and new RF Scenarios and Traffic Scenarios will be defined accordingly to be used as the input for Colosseum testbed.

To generate new RF Scenario files, the contractor shall develop software scripts to extract the required information from the channel models and convert it to the desirable format of the Colosseum testbed. For each of the scenarios described in Sections 5 to 8 of the USDOT Planned Test Schedule[footnoteRef:2], a Colosseum compatible RF Scenario file will be created which includes the channel coefficients at defined timeslots for the entire duration of a testable scenario. The contractor shall develop additional scenarios based on needs identified between the contractor and USDOT. [2: The USDOT’s Spectrum Test Plan can be found here:

https://www.its.dot.gov/research_archives/connected_vehicle/dsrc_testplan.htm]

The contractor shall provide the USDOT with evidence (test scripts, test results) that the RF Scenario files were installed and tested in Colosseum to assure the correct representation of the channel models and real-world environment.

Similarly, the contractor shall develop Traffic Scenarios that need to be defined based on requirements of different traffic behaviors of various V2X technologies as well as the coexistence scenarios of unlicensed radios operating in the Safety Band. The contractor shall submit a draft outline of the traffic scenarios for review and feedback by the USDOT before submitting a final document describing the traffic scenarios. Upon approval by USDOT, the verified RF and Traffic scenarios will be released to be used for running the emulations of the real-world models.

Note: The development of the DSRC, C-V2X and UNII devices is envisioned to be a software centric approach, where implementations will be developed, configured and deployed on Universal Software Radio Peripheral (USRP) devices. Colosseum has the ability to add real “hardware in the loop” radios. This feature allows adding actual UNII, DSRC, and C-V2X (when commercially available) devices directly into the infrastructure (see Section 11, Extended Plan). There is a significant development effort to “translate” the real RF devices and signals to be loaded into the Standard Radio Nodes (SRN’s) and the Massive Channel Emulator (MCHEM) within Colosseum that can provide high fidelity data.

1.3.4 Development of the Scenario Models in the Colosseum and Running the Emulations In this task, the actual real-world channel emulation will be conducted. Based on the defined scenarios developed and approved by USDOT in Task 1.3.3, the contractor shall deploy, test, and evaluate the different RF Scenarios and various Traffic Scenarios through extensive emulations and repeated testing. This includes the interference scenarios at the coexistence of such technologies along with the unlicensed devices operating in the same spectrum, i.e., the Safety Band. The contractor shall provide a draft and final report that evaluates the effectiveness, scalability, and safety of different V2X technologies through their testing.

In addition, the contractor shall consider different suggested approaches for effective use of the spectrum, such as the Detect and Vacate vs Re-channelization, will be evaluated through the appropriately defined RF and Traffic scenarios that are created in Task 1.3.2 and tested in Task 1.3.3. Iterations of modifying the scenarios in Task 1.3.3 and running new tests in Task 1.3.4 can be envisioned to conclude the best practices for spectrum sharing in the Safety Band.

Note: For the DSRC-UNII tests where the field-test data is available, the results of Task 1.3.3 can be validated with the obtained field-test data to verify and assess the accuracy of the real-world emulated models used in the Colosseum.

1.3.5 OPTION YEAR 1: Adding Technology-Specific Commodity Hardware to the Laboratory testing enviroment This represents the work that would be completed at the discretion of the USDOT as an option year beginning after the base year work is complete.

If the laboratory testing environment has the ability of adding real “hardware in the loop” radios (when commercially available), this option year task includes adding actual radios for the technologies of interest, i.e., LTE-CV2X, 5G NR, DSRC, and UNII, directly into the infrastructure. These added radios will take the place of the existing Software Defined Radios that are defaultly used by the lab test bed.

In the scope of the base year tasks, the development of the DSRC, C-V2X and UNII devices is envisioned to be entirely a software-centric approach, where implementations will be developed, configured and deployed on USRP devices. If the USDOT exercises this optional task, the contractor shall acquire new commodity hardware equipment, i.e., CV2X, DSRC, 5G NR and UNII radios and the contractor shall physically add the hardware to the test bed infrastructure. This allows for performing all the scenario emulations done in the software-defined testing, but now with actual commodity radios that are customized for different technologies. This indeed will be one step closer to the real-world implementation of coexistence of V2X and UNII devices where the spectrum sharing will be handled based on the built-in algorithms of these radios.

If this task is exercised, the contractor shall complete hardware acquisition and software integration and testing for the new commodity radios within 12 months of the task being exercised. If the USDOT exercises any additional option year tasks, each task will be repeated with the newly added radios.

The contractor shall provide a final report on the emulation results by utilizing the new commodity radios.

NOTE: New off-the-shelf radios for all V2X scenarios under the test as well as UNII radios will be procured. This will include any additional accessories (TBD) for connecting the new radios to the Colosseum. A detailed budget will be provided within the first year for subsequent years.

1.3.6 OPTION YEAR 2: Extensive Scenario Generation for a Variety of Urban, Mobility and Traffic Settings This represents the work that would be completed at the discretion of the USDOT as an option year beginning after the base year work is complete.

Under this task, the contractor shall develop new RF Scenario Files and Traffic Scenarios based on a variety of urban, mobility, and traffic settings. The contractor shall submit a draft outline of each RF Scenario for review and feedback by the USDOT before submitting a final document describing the RF Scenario.

There are two approaches that can be adopted for obtaining channel models to be used for generating RF-Tap files: One is to use the existing channel models or develop new software-based channel models and build the RF Scenarios based upon them; the second approach is to preform field-test and develop channel models based upon the real-world data. The accuracy of these models can be then benchmarked against the field-test results. The contractor shall develop channel models based on the approach approved by the USDOT.

The field-test approach requires modification of the USDOT Planned Test Schedule (referenced earlier in this document) and making necessary adjustments of the test scenarios accordingly to include the CV2X technology and LTE / 5G NR devices. Moreover, one of the major differences between the DSRC and CV2X is the long-range communication capability of the CV2X when compared to the DSRC. This requires careful consideration and introduces new scenarios to be tested.

In addition to the field-test data acquisition, the contractor shall consider open source simulation tools for scenario generation. In particular, new environment and mobility/traffic scenarios can be generated by utilizing the ‘Simulation of Urban Mobility’ (SUMO) tool and integrating it with network simulator (ns-3) which is a discrete-event network simulator for communication systems.

The purpose of this optional task is the generation and implementation of new RF and Traffic Scenario files for the test bed. These include an extended list of models to fully emulate a broad range of different V2X real-world scenarios, including (but not limited to), rural, semi-urban, urban, and dense-urban (Manhattan grid) environments with various traffic settings.

1.3.7 OPTION YEAR 3: Active Monitoring and Potential Participation in Standard Working Groups of IEEE and 3GPP This represents the work that would be completed at the discretion of the USDOT as an option year beginning after the base year work is complete.

The contractor shall actively monitor changes in the IEEE and 3GPP standard releases for DSRC and CV2X technologies, respectively. The contractor shall highlight significant IEEE and 3GPP standard updates in the form of reports submitted to the USDOT.

2.0 Period of Performance

The period of performance shall be for one (1) base period of 12 months and three (3) option periods of 12 months each.

The Period of Performance for the base year (Tasks 1.3.1 – 1.3.4) is 12 months. After the base year is complete, the period of performance for Option Year 1: Task 1.3.5 is 12 months from option exercise; the period of performance for Option Year 2: Task 1.3.6 is 12 months from option exercise; the period of performance for Option Year 3: Task 1.3.7 is 12 months from option exercise.

3.0 General

The Contractor shall develop and maintain an effective Quality Control Plan (QCP) to ensure services are performed in accordance with this PWS. The Contractor shall develop and implement procedures to identify, prevent, and ensure non-recurrence of defective services. The Contractor’s QCP is the means by which he/her assures that his/her work complies with the requirement of the task order. This shall be submitted by the contractor within 21 days of Award Date along with Project Management Plan described in Task 1.3.1. After government acceptance of the QCP, the Contractor shall receive the Contract Officer’s (CO) acceptance in writing of any proposed change to the government accepted QCP.

3.1 Hours of Operation

N/A

3.2 Place of Performance

The work to be performed under this task order shall be performed at the facility where the testbed is located, as well as the contractor facility (if technical experts are required to complete work at a location separate from where the testbed is physically located).

In case of required field-test data for the LTE and 5G NR technologies, measurement equipment as well as site access (similar to the Planned Test Schedule for DSRC-UNII) is required. However, this is currently deemed to be out of the scope of the first year of the project and can be considered in the optional tasks (1.3.5 – 1.3.7).

3.3 Physical Security

The Contractor shall be responsible for safeguarding all government equipment, information, and property provided for Contractor use.

3.4 Special Qualifications

N/A

3.5 Periodic Progress Meetings

The contractor agrees to attend progress meetings. The Contracting Officer or Contracting Officer’s Representative (COR), and other Government personnel, as appropriate, may meet periodically with the Contractor to review the Contractor's performance. At these meetings, the CO will apprise the Contractor of how the government views the Contractor's performance and the Contractor will apprise the Government of problems, if any, being experienced. Appropriate action shall be taken to resolve outstanding issues. These meetings shall be at no additional cost to the government.

3.6 Identification of Contractor Employees

All contractor personnel attending meetings, answering Government telephones, and working in other situations where their Contractor status is not obvious to third parties are required to identify themselves as such to avoid creating an impression in the minds of members of the public that they are Government officials. They must also ensure that all documents or reports produced by Contractors are suitably marked as Contractor products or that Contractor participation is appropriately disclosed.

3.7 Contractor Travel

Contractor shall be required to travel throughout CONUS during the performance of this task in order to attend meetings, conferences, and training. The Contractor may be required to travel to off-site testing locations in support of this PWS. All travel requires Government approval/authorization and notification to the COR.

3.8 Materials

If Option Year 1 (Task 1.3.5) is exercised, new off-the-shelf radios for all V2X scenarios under the test as well as UNII radios will be procured (number of radios to be determined by USDOT). This will include any additional accessories (TBD) for connecting the new radios to the Colosseum. A detailed budget will be provided within the first year for subsequent years.

3.9 Organizational Conflict of Interest

Contractor and subcontract personnel performing work under this award may receive, have access to, or participate in the development of proprietary or source selection information (e.g., cost or pricing information, budget information or analyses, specifications or work statements, etc.), or perform evaluation services which may create a current or subsequent Organizational Conflict of Interests (OCI) as defined in FAR Subpart 9.5. The Contractor shall notify the CO immediately whenever he/she becomes aware that such access or participation may result in any actual or potential OCI, and may merit the submittal of a plan to the CO to avoid or mitigate any such OCI. This mitigation plan would be determined to be acceptable solely at the discretion of the CO, and in the event the CO unilaterally determines that any such OCI cannot be satisfactorily avoided or mitigated, the Contracting Officer may effect other remedies as he or she deems necessary, including prohibiting the Contractor from participation in subsequent contracted requirements which may be affected by the OCI.

3.10 Phase In /Phase out Period

N/A

4.0 Government Furnished Equipment and Services

4.1 Services

N/A

4.2 Facilities

N/A

4.3 Materials

N/A

5.0 Applicable Publications (Current Editions)

REQUIREMENTS FOR IMPLEMENTING SECTION 508 STANDARDS

NOTE: The following applies to all FHWA contracts and assistance agreements containing Information and Communication Technology (ICT) as a deliverable.

In addition to the work requirements specified in this statement of work, the Contractor shall ensure that all ICT deliverables meet the requirements of Section 508 of the Rehabilitation Act and the ICT Final Standards and Guidelines (508 Refresh) at 36 CFR Part 1194.

As defined in the 508 Refresh, at 36 CFR Part 1194, Appendix A, E103.4, ICT is “Information technology and other equipment, systems, technologies, or processes, for which the principal function is the creation, manipulation, storage, display, receipt, or transmission of electronic data and information, as well as any associated content. Examples of ICT include, but are not limited to: computers and peripheral equipment; information kiosks and transaction machines; telecommunications equipment; customer premises equipment; multifunction office machines; software; applications; Web sites; videos; and, electronic documents.”

Section 508 requires that all electronic products prepared for the Federal Government be accessible to persons with disabilities, including those with vision, hearing, cognitive, and mobility impairments.

Applicable Standards:

· Appendix A to Part 1194 – Section 508 of the Rehabilitation Act: Application and Scoping Requirements

· Appendix B to Part 1194 – Section 255 of the Communications Act: Application and Scoping Requirements

· Appendix C to Part 1194 – Functional Performance Criteria and Technical Requirements Section 508 Refresh standards are available at https://www.access-board.gov/guidelines-and-standards/communications-and-it/about-the-ict-refresh.

The Contractor shall adhere to the terms and requirements in FHWA Form 4260 Section 508 Information and Communication Technology (ICT) Conformance Criteria for Section 508 conformance. The Conformance Criteria document does not need to be completed when submitting a deliverable.

6.0 Attachment/Exhibit List

6.1 TECHNICAL EXHIBIT 1

PERFORMANCE REQUIREMENTS SUMMARY

The Contractor service requirements are summarized into performance objectives that relate directly to mission essential items. The performance threshold briefly describes the minimum acceptable levels of service required for each requirement. These thresholds are critical to mission success.

Performance Objective (The Service required—usually a shall statement)

PRS # 1.

The Contractor shall provide a document describing the channel models that will be used in testing and emulation.

The Contractor provided the documents on time, in the required format, containing all necessary information, and addresses all required information as defined in the task and incorporated appropriate changes/comments suggested by USDOT.

PRS # 2

The Contractor shall develop RF Scenario files to extract the required information from the channel models designed and approved in Task 1.3.2 and convert them to the desirable format of the testbed. These RF Scenario files shall be summarized in document format and delivered to USDOT.

The Contractor provided the documents on time, in the required format, containing all necessary information, and addresses all required information as defined in the task and incorporated appropriate changes/comments suggested by USDOT.

PRS # 3

The Contractor shall provide the USDOT with evidence (test scripts, test results) that the RF Scenario files were installed and tested in the testbed.

The Contractor provided the documents on time, in the required format, containing all necessary information, and addresses all required information as defined in the task and incorporated appropriate changes/comments suggested by USDOT.

PRS # 4

The Contractor shall provide a document describing the traffic scenarios to be used in testing.

The Contractor provided the documents on time, in the required format, containing all necessary information, and addresses all required information as defined in the task and incorporated appropriate changes/comments suggested by USDOT.

PRS # 5

The contractor shall provide a final report that evaluates the effectiveness, scalability, and safety of different V2X technologies through their testing.

The Contractor provided the documents on time, in the required format, containing all necessary information, and addresses all required information as defined in the task and incorporated appropriate changes/comments suggested by USDOT.

PRS # 6 for Option Year 1 (Task 1.3.5) Upon execution of this optional task and approval by USDOT, the contractor shall acquire and implement new hardware for testing.

The Contractor acquires the correct hardware (as defined by USDOT), on time, and provides proof of implementation in the testbed.

PRS # 7 for Option Year 1 (Task 1.3.5) Upon execution of this optional task and approval by USDOT, the contractor shall provide emulation results by utilizing new commodity radios.

The Contractor shall submit results in a final report that characterizes the test results and incorporates appropriate changes/comments suggested by USDOT.

PRS # 8 for Option Year 2 (Task 1.3.6) Upon execution of this optional task and approval by USDOT, the Contractor shall provide the USDOT with evidence (test scripts, test results) that updated RF Scenario files were installed and tested in the testbed utilizing the new radios The Contractor provided the documents on time, in the required format, containing all necessary information, and addresses all required information as defined in the task and incorporated appropriate changes/comments suggested by USDOT.

PRS # 9 for Option Year 3 (Task 1.3.7) Upon execution of this optional task and approval by USDOT, the Contractor shall provide documentation that highlights significant IEEE and 3GPP standard updates.

The Contractor provided the documents on time, in the required format, containing all necessary information, and addresses all required information as defined in the task and incorporated appropriate changes/comments suggested by USDOT.

6.2 TECHNICAL EXHIBIT 2

DELIVERABLES SCHEDULE

And/or 508

Project Management Plan

PWS paragraph #1.3.1 Print Yes

No Within three weeks of Award Date, or one week following kick-off meeting

Electronic copy sent to COR

PDF or Microsoft Word

COR

Status Updates

PWS paragraph #1.3.1 Print Yes

No Monthly, beginning four weeks after Award Date

Electronic copy sent to COR

PDF or Microsoft Word

COR

Channel models

PWS paragraph #1.3.2 Print Yes

NO

Draft: within 60 days of Award

Final: within 120 days of award

Electronic copy sent to COR

PDF or Microsoft Word

COR

RF Scenario Files Installation

PWS paragraph #1.3.3 Print N/A

N/A Within 10 Months of Award

N/A

The contractor shall provide the USDOT with evidence (test scripts, test results) that the RF Scenario files were installed and tested in testbed.

COR

Traffic Scenarios

PWS paragraph #1.3.3 Print Yes

NO

Draft: within 6 Months of Award

Final: within 7 months of Award

Electronic copy sent to COR

PDF or Microsoft Word

COR

Test Report

PWS paragraph #1.3.4 Print Yes

Yes Draft: within 11 Months of Award

Final: within 12 months of award

Electronic copy sent to COR

PDF or Microsoft Word

COR

Acquire and implement new hardware for testing

OPTION YEAR 1, PWS paragraph #1.3.5 Print N/A

N/A Within 12 months of optional task execution

N/A

Provide proof of hardware procurement and implementation

COR

Emulate results by utilizing new commodity radios

OPTION YEAR 1, PWS paragraph #1.3.5 Print Yes

No Draft: Within 10 months of optional task execution

Final: Within 12 months of optional task execution

Electronic copy sent to COR

PDF or Microsoft Word

COR

RF Scenario Files

OPTION YEAR 2, PWS paragraph #1.3.6 Print Yes

No Within 12 months of optional task execution

Electronic copy sent to COR

PDF or Microsoft Word

COR

Standard/Working Groups Reports

OPTION YEAR 3, PWS paragraph #1.3.7 Print Yes

No At the discretion of the USDOT

Electronic copy sent to COR

PDF or Microsoft Word

COR

image1.jpeg