2.8.1.3.5 The PHS are to be applied consistently at both SS and BS sides. Hence, this requires PHS information to be exchanged between BS and SS for the service flows. The diagram below shows the signalling for PHS information exchange. Figure CS -4 PHS Signalling 2.8.1.3.6 The signalling can happen at the time of service flow creation or subsequently in Dynamic Service Change (DSC) messages. 2.8.1.4 Ethernet Specific Part 2.8.1.4.1 In this configuration Ethernet is supported as the higher layer for AeroMACS. Ethernet packets are received at the CS SAP interface, which are then classified as per the classification rules, header suppression applied if PHS rules are defined and scheduled for transmission as per the QoS policies defined for the service flow. Classification shall be based on Ethernet Header information, IP Header Information in case of IP over Ethernet and/or VLAN Header information. 2.8.1.4.2 Robust Header Compression (ROHC) also be applied in addition to PHS to compress IP Header Portions in addition to Ethernet Header compression. ROHC operations shall be performed in accordance with RFC 3095, RFC3759, RFC 3243, RFC 4995, RFC 3843, RFC 4996. The figure below shows a typical AeroMACS configuration for Layer2 operations. Figure CS 5 Ethernet CS – 2.8.1.4.3 In this configuration BS and SS act as layer 2 devices forwarding the Ethernet packets to the other side. GRE tunnels are established between BS and ASN Gateway to extend the AeroMACS connections established between SS and BS. In this configuration SS does not perform any functions related Layer 3 (IP) related functions such as DHCP negotiations or IP address configurations. Such functionalities are to be handled by the aircraft edge router connected to SS. Basically, IP link is established between aircraft router and ASN gateway. 2.8.1.5 IP Specific Part 2.8.1.5.1 In this configuration IP packets are directly carried over AeroMACS link. Classification is based on IP Header Information. ROHC can also be used instead of PHS. The figure below shows IP CS configuration. Figure CS 6 IP CS –
2.8.1.3.5 The PHS are to be applied consistently at both SS and BS sides. Hence, this requires PHS information to be exchanged between BS and SS for the service flows. The diagram below shows the signalling for PHS information exchange. Figure CS -4 PHS Signalling 2.8.1.3.6 The signalling can happen at the time of service flow creation or subsequently in Dynamic Service Change (DSC) messages. 2.8.1.4 Ethernet Specific Part 2.8.1.4.1 In this configuration Ethernet is supported as the higher layer for AeroMACS. Ethernet packets are received at the CS SAP interface, which are then classified as per the classification rules, header suppression applied if PHS rules are defined and scheduled for transmission as per the QoS policies defined for the service flow. Classification shall be based on Ethernet Header information, IP Header Information in case of IP over Ethernet and/or VLAN Header information. 2.8.1.4.2 Robust Header Compression (ROHC) also be applied in addition to PHS to compress IP Header Portions in addition to Ethernet Header compression. ROHC operations shall be performed in accordance with RFC 3095, RFC3759, RFC 3243, RFC 4995, RFC 3843, RFC 4996. The figure below shows a typical AeroMACS configuration for Layer2 operations. Figure – CS 5 Ethernet CS 2.8.1.4.3 In this configuration BS and SS act as layer 2 devices forwarding the Ethernet packets to the other side. GRE tunnels are established between BS and ASN Gateway to extend the AeroMACS connections established between SS and BS. In this configuration SS does not perform any functions related Layer 3 (IP) related functions such as DHCP negotiations or IP address configurations. Such functionalities are to be handled by the aircraft edge router connected to SS. Basically, IP link is established between aircraft router and ASN gateway. 2.8.1.5 IP Specific Part 2.8.1.5.1 In this configuration IP packets are directly carried over AeroMACS link. Classification is based on IP Header Information. ROHC can also be used instead of PHS. The figure below shows IP CS configuration. Figure – CS 6 IP CS
Draft%20Manual%20V29%20changes%20accepted%20Dec%2023.docx