Working paper wg i/Meeting 3/wp 306 aeronautical communications panel (acp)
Download 0.77 Mb.
|
- Navigate this page:
- Annex 1 Example Implementation Guide
- Scope of this document
- Differences to previous edition
- Use of the Document
- General context
- Organisation of the Document
2VoIP GuidanceThere are two standardized frame works for implementing optional VoIP services; H.323 and SIP. Either or both protocols may be used to provide VoIP services however, the original focus of each protocol is different. The focus of H.323 is to handle voice and multimedia calls, including supplementary services, while SIP was designed as a generic transaction protocol for session initiation not bound to any specific media (e.g., audio or video). Details for the relevant protocols are contained in the Voice over IP Handbook, Annex 2 of this document. Refer to this document for detailed information on the deployment of this service. Annex 1 Example Implementation GuideIn order to ensure a uniform and consistent implementation of the ATN across state or regional boundaries an implementation guide should be developed to document the minimum network services, protocol provisioning parameters, and implementation sequence that should be performed to maintain the integrity of the network. The following document is an example Implementation Guide Scope of this documentThe document describes requirements of the various communications protocols to ensure transmission and reception of surveillance data in an IP network environment. These requirements are presented in the form of a Protocol Requirements List (PRL) A Protocol Implementation Conformance Statements (PICS) proforma is attached as Annex 1 to facilitate the interaction with potential suppliers. The purpose of this document is to ensure compatibility of different IPv4 multicast implementations of surveillance data transmission over an IPv4 network service and to ensure compatibility of different IPv6 multicast implementations of surveillance data transmission over an IPv6 network service. Other networking techniques that achieve the same multicast objective may consider certain provisions within this implementation guide but are not further considered within the scope of this document. It is the intention of the concerned ANSPs that the procurement of a system based on commercial-of-the-shelf (COTS) products will provide the maximum benefit/cost ratio with the minimum risk of timescale overrun. The organisation and content of this document and the instructions are designed to facilitate the interaction with potential suppliers.
Since the previous edition, significant technical progress has been made in the field of IP multicast, namely source specific multicast (SSM). SSM provides added simplicity and resiliency to the routing of IP multicast traffic, which is of particular interest for inter-ANSP communications. SSM is recommended within this guideline for that purpose. In this new edition of the guideline, the default maximum message size has been reduced from 512 bytes to 256 bytes.
a) As a checklist by the protocol implementers, to reduce the risk of failure during surveillance data exchanges in IP multicast; b) As a detailed specification of the requirements, to assist the procurement of an IP multicast implementation for surveillance data exchange; c) As a basis for initially checking the possibility of interworking with another implementation. (Note that, while interworking can never be guaranteed, failure to interwork can often be predicted from incompatible PICS); d) As the basis for selecting appropriate tests by a protocol tester, to assess the conformance of the implementation. This implementation guide describes the characteristics of transmitters and receivers using an IP multicast network. Furthermore, this implementation guide facilitates the introduction of multicast within an international context through the use of source specific multicast (SSM). Mandatory capabilities are denoted with the terms “shall” or “must”; desired capabilities are denoted with the term “should”. Suppliers are encouraged to propose COTS systems that provide all the mandatory capabilities and as many desired capabilities that are available with a minimum amount of development. The terms "SHALL", "SHALL NOT", “MUST”, “MUST NOT”, "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY" and "OPTIONAL" in this document are to be interpreted as described in RFC 2119.
b) Network layer: The compliant systems shall implement the IPv4 and IPv6 protocols (as well as ICMP and ICMPv6) as described in the references presented in this document. c) Transport layer: User Datagram Protocol (UDP) shall be the transport layer for IP multicast services. (TCP is used by surveillance systems but is not within the scope of this implementation guide).
Section 1: provides an introduction including information about the document structure, instructions to Suppliers, conformance with the ECAC Strategy and reference documents. Section 2: describes the "Communication protocols" and the associated technical requirements. Section 3: describes the "Implementation requirements" (interface between applicative layer et communication layer) Annex 1 provides Protocol Implementation Conformance Statements (PICS) proforma to facilitate the process of technical offers by Suppliers. Annex 2 provides an abbreviation list of terms used within the document. Directory: safety -> acp -> ACPWGF ACPWGF -> Information paper ACPWGF -> Joint meeting of the ACPWGF -> Working paper ACPWGF -> Amcp wgm/WP19 19 August 2002 Aeronautical Mobile Communication Panel (amcp) Working Group-m meeting Fifth Meeting Saint Petersburg, Russia, 19 to 23 August 2002 Agenda Item 4: satcom ACPWGF -> Acp wgf/16 wp 27 Rev. 1 International Civil Aviation Organization ACPWGF -> Working paper ACPWGF -> Working paper ACPWGF -> Airborne collision avoidance systems working group-a ACPWGF -> Working paper Download 0.77 Mb. Share with your friends:
|