WhitepaperonAeroMACSdeploymentscenariosandderived白皮方案AeroMACS部署资料和来源.doc

WG82 White paper on AeroMACS deployment scenarios and derived requirements SITA - Aircraft Services Issue 3 10 July 2013  Deployment models This section defines the preferred deployment models for AeroMACS – it is extracted from Draft 10 of Eurocae AeroMACS MASPs. Assumptions The following applications have been identified as target by RTCA SC223 and/or Eurocae WG82: Fixed users (RTCA only) (fix information rate: eg UGS, on separate LANs, or network) Airport LAN extensions Unique equiment (terminals, cameras,…) Or Multiple equipment behing MS ANSP managed equipment Integration of RNAV systems, radar… into ANSP network Mobile users Airport trucks (catering, maintenance, fuel….) Luggage terminals,….. Single users (= user terminal) belonging to different networks or LANs (!) (airport, MRO, catering, fuel……) Support for VoiP (RTCA only) Aircraft ATC, AOC direct operational impact and/or safety impact AAC applications no direct operational impact The following entities can be involved in AeroMACS service: ANSPs Airport telco operator Airport ACSP =Aeronautical communication service provider (AVICOM, SITA, ARINC, ADCC) CSP (Communication - Mobility Service Providers)(new-other global service provider) Reminder of NAP/V-NSP/H-NSP services and possible actors Airport telco operator ANSP ACSP CSP Airline NAP x x x V-NSP x x x H-NSP x x x NAP sharing by multiple NSP This deployment model should be preferred by NSP and NAP in order to rationalize infrastructure, ease cell planning at a given airport, and minimize interference on legacy systems (e.g. GlobalStar) with probably less Base Stations due to a more efficient use of the spectrum Figure 14: Single NAP - Multiple NSP . Several ASNs might be connected to a single CSN and vice-versa i.e., several CSNs might share the same ASN. The most common deployment expected is one single ASN within the airport and multiple operators (CSNs) connected. Hence, this is the most likely business scenar