3

Click here to load reader

NVS VoIP - Background and Purpose

Embed Size (px)

Citation preview

Page 1: NVS VoIP - Background and Purpose

Market Survey Request for Information (RFI) NAS Voice System (NVS)

Background:

The mission of the Federal Aviation Administration (FAA) is to provide the safest, most efficient aerospace system in the world. A major initiative in support of this mission is NextGen – the Next Generation Air Transportation System. NextGen is a transformation of the National Airspace System (NAS) using 21st century technologies to ensure that future safety, capacity and environmental needs are met.

The NAS Voice System (NVS) is one of five transformational NextGen programs. The NVS program will allow the FAA’s air traffic control to achieve a network-based infrastructure. NVS will support a more flexible voice communications system that includes dynamic re-sectorization, resource reallocation, and airspace redesign. The NVS program will replace current voice switches and radio control equipment with new equipment capable of operating in Voice over Internet Protocol (VoIP) mode.

The FAA engages in extensive multilateral consultation in forums such as the International Civil Aviation Organization (ICAO) and with global partners such as EUROCONTROL. The focus on harmonization of international standards for Air Traffic Management (ATM) services such as frequency allocations and new communications systems is integral to the core business of supporting the safe, secure, and efficient operation of the NAS. EUROCAE Working Group 67 (WG-67) has developed the following attached VoIP ATM documents for European States: ED-136 – VoIP ATM System Operational and Technical Requirements, ED-137 – Interoperability Standards for VoIP ATM Components, and ED-138 – Network Requirements and Performances for VoIP ATM Systems. As part of the process in establishing a VoIP standard for NVS that is in harmony with an international standard for VoIP, the FAA is reviewing the EUROCAE WG-67 VoIP documents.

Purpose:

In this RFI, the FAA is seeking industry comments and insights to the EUROCAE WG-67 documents noted above as they relate to FAA-centric voice communication requirements. RFI responders should consider the following questions:

Can you identify any current FAA voice communication operational requirements that are not supported by the EUROCAE standards? If so, can you suggest alternative approaches, modifications, or extensions to these standards to overcome these limitations?

Do you see any problems in meeting the end-to-end Signaling and Voice Delay Requirements currently listed in ED-136 and ED-137? If so, please provide a detailed description of the issues and the necessary changes to overcome these limitations?

Page 1 of 2

Page 2: NVS VoIP - Background and Purpose

Market Survey Request for Information (RFI) NAS Voice System (NVS)

ED-136 currently defines four PTT priorities (Normal, Coupling, Priority, and Emergency). Do you have any comments on the suitability of these priorities to satisfy current FAA operational requirements?

Do you have any comments regarding the suitability of the protocols adopted by the WG-67 standards (e.g., SIP, RTP/RTCP) to satisfy NVS requirements?

ED-138 makes no clear recommendation in the QoS protocol area, but seems to favor implementation of Differentiated Service Protocols.  Based on industry experience with the implementation of multimedia packet networks that support voice, data, and video, what is your recommendation regarding the implementation of QoS protocols for NVS network focusing on the need to support high-priority voice communication links that require 99.999% availability? 

In October 2009, the EUROCONTROL Communications Team created a sub-group entitled VOTE (VoIP in ATM Implementation and Transition Expert Group). The general mission of VOTE is to address VoIP in ATM implementation and transition-related issues to identify solutions and deliver recommendations to interested parties (i.e., Air Navigation Service Providers (ANSPs), industry, telecommunications companies, and standardization bodies. The FAA is a member of VOTE and encourages interested parties to participate in order to ensure that FAA voice communications requirements are adequately addressed and incorporated.

Please submit your responses to this RFI on/by 12:00 Noon EST on Friday, February 19th

2010. Responses should be submitted electronically to Kathy St. Hill, Contracting Officer, at [email protected]. Questions may be directed to the Contracting Officer at 202-493-1408.

Page 2 of 2