Outcome of Web meeting Draft Manual as at end of Day 2 V2

9 . . 2.10.2 Siting Procedures

Note: The procedures recommended for siting are outlined in this area. This area will cover specific work activities, descriptions and procedures recommended for siting.

2.10.2.1 Preliminary Data Acquisition
2.10.2.1.1 Coverage Requirements
(for the area to be served including area/volume, traffic patterns, handoff boundaries, RSSI, CINR, etc)
2.10.2.1.2 Maps and Charts
(includes future airport planning e.g. taxiways, runways, buildings that may obstruct)

Airport Master Plan

Others???
2.10.2.1.3 System Architecture Considerations
Availability Requirements

Transaction times, nominal times, 95% percentile

Safety and Performance Requirements:

1. 
   COCR
   

COCR provides very straigthforward input. It derives certain requirements for the FRS (which corresponds to our AeroMACS access network). Find these requirements below together with figure for the most stringent services (except for safety nets or surv, which have exceptionally high requirements).

• 
  Expiration time RCTP (ET - 1 way): 5.0
  
• 
  Latency RCTP (TT95 - 1 way): 1.2
  
• 
  Continuity: 0.9996
  
• 
  Integrity: 5.0E-08
  
• 
  Availability of provision: 0.999995
  
• 
  Availability of use: 0.9995
  

2. 
   MASPS
   

The MASPS has safety and performance requirements for the ACSP (careful!! This is not the same boundary as the FRS considered in the COCR). Figures are in the following tables:

	Communication		Surveillance
	ET (sec) C = 99.9%	TT (sec) C = 95%	OT (sec) C = 99.9%	DT (sec) C = 95%
Maximum ACSP contribution	18 (two way transaction)	10 (two way transaction)	12 (one way transaction)	5 (one way transaction)

NOTE: These performance requirements are based on most constraining performance labels specified in ED-228 (RCP130 and RSP160).

Table 9: ACSP Availability Requirements [40]

	ACSP requirements
Availability	0.9995
Maximum Unplanned service outage duration (min)	6
Maximum number of service unplanned outages	40
Maximum accumulated service unplanned outage time(min/yr)	240
Unplanned service outage notification delay (min)	5

 NOTE: These performance requirements are based on most constraining performance labels specified in ED-228 (RCP130 and RSP160).
2.10.2.2 Preliminary Site Selection
Siting Area Boundaries

(This is for the BS in question, but consideration is given to other base station equipment that is part of the whole system)

2.10.2.2.1 Coverage Requirements and Limitations
(Range)
2.10.2.2.2 Airport Site Investigation
(Objectives here are to locate and identify available siting property on airport grounds to host BS and SS equipment.)

environmental considerations

Interfaces to power

Interfaces to wired communications network

2.10.2.2.3 Safety Considerations

2.10.2.2.4 Preliminary Site Analysis

(The purpose here is to determine the most promising candidate site locations for BS & SS. This considers if coverage requirements can be met, can maintenance be conducted from the location, power, telco, grounding access etc. )

Antenna height and tilt for LOS

Cost Estimates ???

2.10.2.3 Site Analysis
Note: In here methods and procedures for processing and analyzing information gathered from early sections are presented. I suspect that at this point there are a couple or more candidate sites selected, so the analysis procedures should be conducted for each site.
2.10.2.3.1 Site Panoramic Survey
(go to the site and take pictures from where the BS will be deployed for analysis. We did this with Hitachi for ARFF BS siting and some SS sites.)
2.10.2.3.2 Coverage Analysis
(using modeling software and analytical computations e.g. link budget, sensitivity, link margin recommendations, simulation tool recommendations)

2.10.2.3.3 Traffic Analysis

(capacity consideration are handled here e.g. symmetry of the DL/UL ratio, service flows configuration per BS, etc.)
2.10.2.3.4 Frequency Assignment Analysis
(frequency use and reuse)
2.11 Capacity Planning
2,11.1 This Section provides the results of a qualitative investigation of the capacity of an AeroMACS access network in terms of the maximum number of users able to be accommodated in such a network under normal conditions. The constraints on the number of users are analyzed according to two possible limitations: a) maximum number of registered users in AeroMACS BS and ASN-GW, and b) number of users considering the maximum throughput supported by the access network and compared to the required throughput per user. This information is provided as guidance for future implementers of AeroMACS systems.
2.11.2 Guidance is provided on the overall system capacity and in particular in relation to the number of users that can be supported by an AeroMACS access network under an acceptable level of service.

2.11.3 Acceptable level of service is defined here as a situation where the system is not under congested status. In the context of this paper, congestion occurs when the system cannot offer enough capacity for an additional user and it will reject any additional user entry. The level of available capacity reaching congestion differs with the scenarios and the assumptions for the communication requirements of the serviced users.

2.11.4 In this analysis, “user” is defined as the application client connected to the AeroMACS service network through a Mobile Station (MS). Each user runs a number of services described in the scenarios considered in section 3.2. In this analysis, users can be aircraft, surface vehicles and various types of fixed stations.

2.11.5 It needs to be noted that this study is a qualitative analysis on the capacity that an AeroMACS access network can provide under a number of assumptions. The objective is not to quantify the absolute maximum number of users that can be supported, neither to derive operational or technical requirements.

2.11.6 In general in an AeroMACS network, user access constraints may result from two possible factors:

• 
  User registration constraints: The BS and ASN-GW are the two types of devices that enable the AeroMACS access network. These two devices are limited by design to a number of supported users that are given access service. This limitation depends on the manufacturer design.
  

• 
  Throughput constraints: Radio access provided by a BS to the MSs covered in the corresponding cell uses the limited throughput resources of the 5 MHz-wide radio channel configured in the cell. Assumptions are taken about the types of MS devices that consume different levels of throughput and modulation scheme in order to calculate a number of users that allows all the MSs in the cell to be given an acceptable level of service.
  

2.11.7 This section addresses the two constraints mentioned above. For the throughput constraint analysis, a user characterization and scenario definition is worked out before the analytic results are presented.

2.11.8 User registration constraints

2.11.8.1 The maximum number of users that can be supported per ASN-GW and BS is limited due to the size of the database used to register the number of MS (MAC addresses or other parameters). From ASN-GW perspective, some products are scalable meaning in number of boards and distributed architecture, hence proposing configurations for thousands of users. Thus, the limitation in number of registered users will probably not be an issue airport-wide.

2.11.8.2 BS may impose stricter limits in the number of subscribers registered to operate in the BS radio channel. Data from one manufacturer indicate 64 units supported per BS⁰.

To be further discussed and completed with data from other manufacturers.

2.11.9 Throughput constraints

2.11.9.1 The throughput limitation of the AeroMACS access network occurs at the cell level on its specific radio channel, i.e. it is driven by each BS in the network independently. The analysis of this limitation is performed here qualitatively and provides a general guidance of the order of magnitude of this figure given certain assumptions. If a detailed figure needs to be achieved, simulation or field test should be performed for a specific deployment.

2.11.9.2 In order to calculate the maximum number of users in a cell limited by throughput, a three-process step is followed:

• 
  First, the throughput needs are defined depending on the type of user, and the throughput supported by BS is defined depending on the type of BS.
  
• 
  Second, scenarios are defined which specify the ratio of each type of user is foreseen per BS.
  
• 
  Third, results are calculated analytically indicating the maximum number of users supported in each scenario.