AeroMACS QOS

Contents QOS concepts Applications & QOS mapping Device Classes AeroMACS QOS IP – QOS Diffserv Concepts Applications & QOS mapping Device Classes Device Identification & Provisioning

AeroMACS service flows Type of Service Features Applications Unsolicited Grant Service (UGS) Periodic B/W of equal size allocated as per the request made during connection establishment. No dynamic negotiations possible Less B/W management overheads Suitable for real-time traffic of fixed data length at periodic intervals Examples: Voice, T1/E1 service, VOIP etc., Critical sensor traffic Real-time Polling Service (rtPS) Periodic B/W negotiation opportunities are provided and B/W size is negotiated at every opportunity SS provided with uni-cast request opportunities. SS can request for variable data size when the opportunity is available. Suitable for real-time with variable data sizes or critical applications that requires guaranteed service Examples: MPEG Video Streams, Periodic Broadcasts like ADS-B/TIS-B , Air Traffic Control messages, Non Real-Time Polling Service nrtPS Suitable for non real-time traffic BS typically polls SS in regular basis with intervals of 1 sec or lesser ( Minimum Guaranteed) . SS can use contention based request for bandwidth allocation Suitable for non-real-time lesser critical applications. Example : File transfer , AOC applications Best Effort Suitable for general low priority traffic which does not require any guaranteed service level Example : Web Browsing , Mail transfer

IP- Quality Of Service Re assigned for Diffserv However TOS is not generally implemented. Instead reassigned to Diffserv (RFC 2474) . IPv4 & IPv6 use Diffserv definitions.

Diffserv concepts Diffserv is used to classify and mark the packets so that packets are treated with different QOS . TOS bits of IP header is redefined for Diffserv Expedited Forwarding (EF) Low delay, Low Jitter & Low Loss Assured Forwarding (AF) BW assured for this traffic Packet drop precedence can be defined within this class. Default (BE) Generic traffic with best effort transmission AF packet drop precedence definition Assured Forwarding (AF) Behavior Group Class 1 Class 2 Class 3 Class 4 Low Drop AF11 (DSCP 10) AF21 (DSCP 18) AF31 (DSCP 26) AF41 (DSCP 34) Med Drop AF12 (DSCP 12) AF22 (DSCP 20) AF32 (DSCP 28) AF42 (DSCP 36) High Drop AF13 (DSCP 14) AF23 (DSCP 22) AF33 (DSCP 30) AF43 (DSCP 38)

ATN-IPS QOS Model Applications Mark IP packets (Set DSCP bits) depending upon the criticality . TOS – in case of IP v4 & Traffic Class - in case of v6 Radios shall map IP Level Diffserv QOS to their MAC level QOS AC End Systems Air- Ground Network Aircraft Network Datalink Radios Ground Station Ground Network AC End Systems Network prioritizes packets depending upon the DSCP settings All network components Handle packets as per Diffser settings

Message Priority Definitions Priority Mapping as per 9896 Class of Service IP Drop ATN Priority Applications Very High (EF)   Voice High (AF) 1 2 3 ADS-C, CPDLC Normal (AF) 4 AIDC, FIS, ATIS 5 METAR 6 CM(DLIC) 7 8 to 14 Best Effort (BE) ICAO Recommended Practices COCR RTCP Requirements Delay in Secs Applications 0.13 ATC-VOICE 0.4 AOC-VOICE 1.2 SURV, WAKE 3 ACC,ACM, DLL, D_RVR 5 D-ATIS, D-FLIP,D-ALERT,D-TAXI, D-SIGMAT 8 10 D-SIG, PPD 30 AOC-High 60 AOC-low

Eurocontrol AeroMACS Manual CoS Scheduling QoS paremeters values in the AeroMACS service flows Traffic priority Maximum Sustained Traffic Rate (kbps) Minimum Reserved Traffic Rate (kbps) Maximum Latency (s) Voice ertPS N/A DL/UL: 64 64* DL/UL: 0.150 NET rtPS DL/UL: 34 32 DL/UL: 1 ATS1 1 DL/UL: 1.5 ATS2 2 ATS3 nrtPS AOC1 DL: 67 UL: 134 DL: 64 UL: 128 AOC2 BE DL: (8100 – 0.267 x A/C)/2 UL: (3300 – 0.334 x A/C)/2 APT1 DL: 1000 APT2

Service Flow and QOS Mapping AeroMACS supports Classification rules based on DSCP CoS Scheduling IP QOS Traffic priority PHB DSCP bits Voice ertPS (UGS) N/A EF 101110 NET rtPS AF31 011010 ATS1 1 AF32 011100 ATS2 2 AF33 011110 Emergency Video   AF23 010XXX ATS3 nrtPS AF11 001010, 001100 AOC1 AF13 001110 AOC2 BE DF 000000 APT1 APT2 Newly Added which is used for emergency purpose only. Normal video will be treated as “Best Efforts) AF4X , AF21, AF22, AF12 are reserved for future traffic categories

Default Supported by all devices Device Classes CoS Scheduling IP QOS Aircarft Surface Vehicle Video Sensors Ground Crtical Ground Default Traffic priority PHB Voice ertPS N/A EF X   NET rtPS AF31 ATS1 1 AF32 ATS2 2 AF33 Video (E) AF23 ATS3 nrtPS AF11, AF12 x AOC1 AF13 AOC2 BE DF Default Supported by all devices APT1 APT2 Considering the RTCP requirements, Is it possible to reduce the number of Service flows.

Device Type Identification “tbsCertificate.subject” shall be used to distinguish different types of certificates During Logon AAA server identifies the device type and based on user profile provisions the set of service flows Certificates have device Type Identified AAA tbsCertificate.subject : <Device Type><Id> ASN AeroMACS CPE ASN / BS configured to support all service flows identified

Thank You