<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Archiving and Interchange DTD v1.0 20120330//EN" "JATS-archivearticle1.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink">
  <front>
    <journal-meta />
    <article-meta>
      <title-group>
        <article-title>Analysis of technological requirements for IP-based modernization of aeronautical telecommunication network in Ukraine</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Georgiy Konakhovych</string-name>
          <email>heorhii.konakhovych@npp.kai.edu.ua</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Oleksii Holubnychyi</string-name>
          <email>oleksii.holubnychyi@npp.kai.edu.ua</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Viktoriia Lukashenko</string-name>
          <email>viktoriia.lukashenko@npp.nau.edu.ua</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Iryna Kozliuk</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Semen Doroshenko</string-name>
          <email>semendoroshen@gmail.com</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>State University "Kyiv Aviation Institute"</institution>
          ,
          <addr-line>Liubomyra Huzara Ave., 1, Kyiv, 03058</addr-line>
          ,
          <country country="UA">Ukraine</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>The aviation infrastructure of Ukraine constantly needs to modernize telecommunication networks, especially in the context of the upcoming end of the war and the opening of airspace over Ukraine. A comprehensive analysis of technical and regulatory standards established by international organizations ICAO and EUROCAE, and systematization of their requirements in the direction of implementing a convergent network architecture ATN/IPS is a fundamental task. This work considers the need to replace outdated TDM-based networks with modern IP technologies. The main requirements for protocols at key levels of the OSI model, including IPv6, TCP/UDP, IPsec, IKEv2, SIP and RTP, as well as recommendations for quality of service. The optimal selection of network equipment parameters aimed at minimizing packet transmission delays to meet performance standards necessary for reliable operation of the ATC system is recommended. A mathematical model based on a discrete Markov system is proposed for predicting the load on the aviation telecommunications network of Ukraine using data on passenger trafic between regional airports.</p>
      </abstract>
      <kwd-group>
        <kwd>eol&gt;aeronautical telecommunications</kwd>
        <kwd>ATN/IPS</kwd>
        <kwd>voice quality</kwd>
        <kwd>E-model</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>1. Introduction</title>
      <p>The advancement of aviation infrastructure and information transmission technologies underscores the
critical role of network communication in ensuring air trafic safety and operational eficiency.</p>
      <p>Following the end of the war and the reopening of Ukrainian airspace, restoring and modernizing
the country’s aviation infrastructure will be a strategic priority to guarantee safe and eficient flight
operations. A crucial component of this efort involves integrating advanced data transmission
technologies into the Aeronautical Telecommunications Network (ATN). Transitioning to the modern ATN/IPS
(Aeronautical Telecommunications Network over Internet Protocol Suite) architecture will be essential
for this upgrade.</p>
      <p>The aviation telecommunications network, based on the integrated ATN/IPS system, serves as the
foundation for organizing the exchange of operational information among air trafic control services,
airlines, and other airspace participants. In this context, ensuring high-quality and secure data
transmission is essential. The International Civil Aviation Organization (ICAO) and the European Organization
for Aviation Equipment (EUROCAE) have established a set of requirements and standards aimed at
enhancing the reliability, security, and eficiency of network systems. They address a wide range of
issues, from architectural solutions and data transmission protocols to mechanisms for protecting against
cyber threats and other forms of external influence. Analyzing the ICAO and EUROCAE requirements
enables not only the assessment of the current state of the ATN/IPS network but also the identification
of areas for modernization and enhancement. The integration of the traditional ATN aviation network
with modern packet data transmission technologies opens up new opportunities for optimizing air
trafic control processes. Contemporary trends in aviation demand that existing solutions adapt to
new operating conditions, which requires a thorough analysis and comparative assessment of the
requirements of international organizations.</p>
    </sec>
    <sec id="sec-2">
      <title>2. Analysis of research and publications</title>
      <p>
        A review of recent publications reveals that the transition to ATN/IPS in Ukraine remains an
underexplored topic. While some documents, such as in [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ], provide a broad analysis of global IP migration
requirements for aviation networks, others, like in [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ], specifically focus on cybersecurity and data
protection. However, detailed research on Ukraine’s specific challenges and implementation strategies
is lacking. This gap presents a significant opportunity for further investigation and the development of
practical recommendations tailored to the Ukrainian aviation sector.
      </p>
    </sec>
    <sec id="sec-3">
      <title>3. Statement of the task</title>
      <p>The objective of this article is to conduct a comprehensive analysis and systematization of ICAO and
EUROCAE requirements related to ensuring high-quality data transmission in converged ATN/IPS
networks. Additionally, the study explores practical approaches for implementing these standards
within Ukraine’s aviation infrastructure, particularly in the post-war recovery phase. The findings will
help identify critical challenges and propose solutions for modernizing Ukraine’s aviation
telecommunications network, aligning it with global best practices. Given the ongoing shift from traditional
TDM-based voice communications (used in air trafic control) to Voice over IP (VoIP) and converged
IP networks, this research is both timely and essential. International organizations, including ICAO,
EUROCAE, SESAR, and the FAA’s NextGen program, have already established frameworks for this
transition. Ukraine’s successful adoption of these standards will enhance aviation safety, operational
eficiency, and interoperability with global air trafic management systems once airspace reopens.</p>
    </sec>
    <sec id="sec-4">
      <title>4. Key study</title>
      <p>
        As stipulated in [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ], the following requirements must be met:
• IPv6 serves as the primary network protocol to enable global addressing and scalability [
        <xref ref-type="bibr" rid="ref3 ref4">3, 4</xref>
        ]
with IPv4 permitted only in limited scenarios;
• TCP is mandated at the transport layer for reliable communication [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ];
• UDP is employed for latency-sensitive services, such as voice communications;
• Security measures are enforced through IPsec and IKEv2 protocols, with detailed security
requirements analyzed in [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ] ;
• Air trafic control (ATC) voice communications must utilize VoIP technology;
• BGP is designated for inter-domain routing;
• Integration with System Wide Information Management (SWIM) must be ensured;
• Support for SATCOM, terrestrial radio links, and VPNs (Virtual Private Networks) is required.
      </p>
      <p>
        For VoIP-based voice transmission, the EUROCAE WG-67 working group has developed a series
of guidance documents [
        <xref ref-type="bibr" rid="ref10 ref6 ref7 ref8 ref9">6, 7, 8, 9, 10</xref>
        ]. These documents align with the "Vienna Agreement," which
outlines the components of the VoIP ATM (Air Trafic Management) system and their interconnections,
as illustrated in Figure 1.
      </p>
      <p>
        The requirements for VoIP ATM systems must be clearly defined at every level of interaction, whether
through radio or telephone communications. This includes specifying physical interfaces, functional
capabilities, integration with existing systems, verification against established protocols such as Session
Initiation Protocol (SIP) [
        <xref ref-type="bibr" rid="ref11">11</xref>
        ] and H.323 [
        <xref ref-type="bibr" rid="ref12">12</xref>
        ], as well as implementing robust monitoring, security
protections, and quality of service measures.
      </p>
      <p>An analysis of the relevant documentation allows for the systematization of minimum requirements
that manufacturers and users of VoIP components in ATM systems must meet. These requirements are
designed to guarantee performance, security, and seamless interoperability across diferent systems.
They encompass both technical specifications and operational considerations for voice and data
communications, whether between air navigation service providers (ground-ground communications) or
between air trafic controllers and aircraft (air-ground communications).</p>
      <p>A fundamental requirement for VoIP ATM systems is ensuring minimal latency in the transmission
of critical aviation messages. This necessitates a structured approach to network trafic prioritization,
where data streams are categorized based on their operational importance, ranging from critical and
high-priority to medium- and low-priority communications. Maintaining signal integrity is equally
vital to prevent distortion or loss of voice transmissions. Additionally, control signals must be delivered
with high precision, adhering to stringent latency limits where the maximum permissible delay does
not exceed 100 milliseconds in terrestrial network environments, as illustrated in Figure 2.</p>
      <p>Additionally, jitter should not exceed 30ms to maintain high voice quality, and packet loss should be
less than 1 % to ensure acceptable voice clarity. The key indicator, MOS (Mean Opinion Score), should
be no less than 4.0 for high voice quality.</p>
      <p>These performance benchmarks are crucial for supporting real-time decision-making in air trafic
control operations. The system must guarantee reliable data transmission through mechanisms that
prevent packet loss and compensate for network jitter, while consistently meeting the rigorous demands
of modern air trafic management in terms of both security and operational reliability. The
implementation of these standards ensures that VoIP-based communications in ATM systems maintain the highest
levels of eficiency, security, and uninterrupted service required for critical aviation operations.</p>
      <sec id="sec-4-1">
        <title>4.1. Security and protection</title>
        <p>The Secure Real-Time Transport Protocol (SRTP) should be used to encrypt voice trafic. Authentication
and access control procedures are provided by the Transport Layer Security (TLS) and IPSec protocols.
It is also necessary to provide protection against Denial of Service (DoS) attacks and implement
mechanisms for detecting trafic anomalies to ensure reliable system operation in the event of a
connection loss or emergencies.</p>
      </sec>
      <sec id="sec-4-2">
        <title>4.2. Interoperability requirements between IP components of the VoIP ATM system</title>
        <p>
          The ATN/IPS network must support interaction with air trafic control systems of the European Union
countries and comply with SESAR (Single European Sky ATM Research) standards. The key point is
the support of IPv6 protocols to ensure long-term scalability of the network, detailed in [
          <xref ref-type="bibr" rid="ref3">3</xref>
          ].
        </p>
      </sec>
      <sec id="sec-4-3">
        <title>4.3. Protocols and standards</title>
        <p>
          The SIP should be used to establish, manage, and terminate calls. Provide support for Real-Time
Transport Protocol (RTP) [
          <xref ref-type="bibr" rid="ref13">13</xref>
          ] for voice trafic transmission and compatibility with ITU-T G.711 [
          <xref ref-type="bibr" rid="ref14">14</xref>
          ],
G.729 [
          <xref ref-type="bibr" rid="ref15">15</xref>
          ], and other audio codecs. Simple Network Management Protocol (SNMP) is used to monitor
the status of components.
        </p>
      </sec>
      <sec id="sec-4-4">
        <title>4.4. Equipment compatibility</title>
        <p>The ability to connect ATS consoles, gateways, and signaling servers should be provided. Integration
with existing ATM voice communication systems and support for routing and load balancing protocols
(OSPF, BGP, MPLS).</p>
      </sec>
      <sec id="sec-4-5">
        <title>4.5. Quality of Service (QoS)</title>
        <p>Voice trafic packets should have a higher priority compared to other types of trafic to avoid delays
during network congestion. The system should be suficiently robust to prevent voice data loss even in
the event of individual component failure. It is also essential to provide support for Climax mode, which
allows you to choose the best available signal source to obtain a high-quality signal. It is advisable to use
DifServ and MPLS-TE trafic prioritization mechanisms to maintain the proper level of performance.
It is necessary to guarantee a minimum bandwidth of 64 kbit/s for voice trafic per call. In addition,
efective queue management and bufering are essential, which allow avoiding packet loss and ensuring
the stability of voice message transmission.</p>
      </sec>
      <sec id="sec-4-6">
        <title>4.6. Reliability and fault tolerance</title>
        <p>
          Ensuring the reliable functioning of air trafic control systems involves continuous and stable data
exchange between ground air trafic control centers (ATC) and aircraft [
          <xref ref-type="bibr" rid="ref16 ref17">16, 17</xref>
          ]. For this, it is necessary
to implement a communication channel redundancy, as well as mechanisms for automatic switching
in the event of failure (failover, redundancy), which minimizes the risk of communication loss. The
system must guarantee stable operation even under high-load conditions, which requires an efective
organization of resources and adaptive solutions [
          <xref ref-type="bibr" rid="ref18 ref19">18, 19</xref>
          ]. Constant monitoring of network parameters
allows you to detect deviations in operation and promptly eliminate problems. The implementation of
automatic recovery mechanisms ensures a swift return of the system to regular operation in the event
of failures.
        </p>
      </sec>
      <sec id="sec-4-7">
        <title>4.7. Testing methodology and compliance criteria</title>
        <p>It is necessary to use laboratory tests to check delays, packet losses, and system performance, as well as
simulate real operating conditions and network loads. Provide for testing for protection against attacks
and communication security. There must be compatibility with ITU-T, ETSI standards, and EUROCAE
recommendations. Fulfillment of requirements for QoS, security, and compatibility of components to
ensure reliable operation in a real ATM environment.</p>
      </sec>
    </sec>
    <sec id="sec-5">
      <title>5. Calculation of elementary parameters that can afect voice data quality in VoIP ATM networks</title>
      <sec id="sec-5-1">
        <title>5.1. General methodology</title>
        <p>
          It is necessary to maintain voice transmission quality that meets the ITU-T criteria [
          <xref ref-type="bibr" rid="ref20">20</xref>
          ] for high-quality
communication. The voice quality of radio communication is determined using the voice quality
assessment methodology of the nominal rating MOS. The MOS scale was formulated as a result of
subjective research. In subjective testing, subjects were asked to classify the perceived voice quality
according to the voice signal categories: excellent (5), good (4), satisfactory (3), poor (2), and very poor
(1). To minimize the efects of voice quality degradation, the MOS value of the radio call over the
terrestrial segment “to” and “from” the radio equipment MUST be equal to or greater than 4. The most
common approach to quantifying speech quality (and therefore its intelligibility) in VoIP networks is
to use the E-model (Figure 4) [
          <xref ref-type="bibr" rid="ref21">21</xref>
          ]. This model calculates the transmission rating factor, so-called “R
value”, which takes into account both the efects of delay and the impact of packet loss (along with
other factors).
        </p>
        <p>One of the basic representations of this model has the form of a formula</p>
        <p>= 0 −   −   −   + ,
where
• 0 is a baseline value that takes into account noise efects and the overall signal-to-noise situation.
•  is the simultaneous quality degradation factor.
•  is the delay impairment factor.
•  is the equipment impairment factor.</p>
        <p>•  is the advantage factor (e.g., mobility).</p>
        <p>Baseline Value 0 is a baseline value that takes into account noise efects and the overall
signal-tonoise situation.</p>
        <p>0 = 15 − 1.5(SLR +  ),
• SLR — Transmission loudness indicator
•  — Total power of diferent noise sources</p>
        <p>Simultaneous Quality Degradation Factor  is the simultaneous quality degradation factor,
determined as:</p>
        <p>=  +  + ,
•  — Coeficient representing the decrease in quality due to low Overall Loudness Rating (OLR)
•  — Coeficient for degradation caused by suboptimal sidetone
•  — Coeficient for degradation due to quantization noise
Delay Coeficient  is the delay impairment coeficient, calculated as the sum of three components:
 =  +  + ,
•  — Estimates the quality degradation due to the echo heard by the speaker
•  — Estimates the quality degradation due to the echo heard by the listener
•  — Represents the degradation caused by excessive absolute delay</p>
        <p>In the context of the critical requirements for signal propagation delays within the ground segment
of the Aeronautical Telecommunication Network (ATN), a detailed analysis of the contributing factors
to voice data delay is essential.</p>
        <p>The total transmission delay total consists of several components:</p>
        <p>total = net + enc + sec + buf,
• net — Network delay (includes routing time and inter-node transmission)
• enc — Encoding delay (time required to convert an analog signal to digital)
• sec — Delay due to encryption and decryption
• buf — Bufering delay (used to smooth out jitter, but may cause synchronization issues)</p>
        <sec id="sec-5-1-1">
          <title>The bufering delay is further defined as:</title>
          <p>buf =  · ,
•  — Jitter (variation in packet arrival time)
•  — Bufering coeficient (depends on jitter compensation algorithm)
Typically, if jitter  ≥ 30 ms, bufering delay 
buf starts to noticeably degrade speech quality.</p>
        </sec>
      </sec>
      <sec id="sec-5-2">
        <title>5.2. Example: Delay calculation and codec selection</title>
        <p>In ATN, the maximum delay of voice packet transmission should not exceed 130 ms in two critical
sections: “before the radio transmitter” (ground network delay) and “after the radio receiver” (ground
network delay after receiving a packet from the air segment).</p>
        <p>
          To minimize the impact on this parameter, we analyze the permissible audio codecs [
          <xref ref-type="bibr" rid="ref14 ref15 ref22">14, 15, 22</xref>
          ] based
on the recommendations in [
          <xref ref-type="bibr" rid="ref7">7</xref>
          ]. A summary of their key characteristics is provided in Table 1.
We select G.711 (A-law) as it provides the highest Mean Opinion Score (MOS) and the lowest delay
among listed codecs. The total network delay net includes:
• Packet transit time through routers,
• Processing time at switching devices,
• Transmission time across terrestrial links.
        </p>
        <p>
          According to recent studies [
          <xref ref-type="bibr" rid="ref23">23</xref>
          ], taking into account full-scale intrusion and route adjustments, typical
delays for the regional IP network of Ukraine are in the range of 15–20 ms, while delays for the European
domain are typically 40–50 ms.
        </p>
        <p>To ensure robustness and include a margin for error, we assume a total network delay of:
Encryption delay. The use of VPN or IPSec introduces an additional delay of approximately 10–15 ms.
For the purposes of this analysis, we select:</p>
        <p>Bufering delay. Bufering is used to compensate for jitter but contributes to overall transmission
delay. For VoIP applications, a recommended bufering delay is:</p>
        <p>Total delay and compliance check. Assuming an encoding delay of:
the total estimated one-way delay is:</p>
        <p>total = net + enc + sec + buf = 70 + 1 + 12 + 20 = 103 ms.</p>
        <p>The obtained total delay of 103 ms is less than the 130 ms threshold defined by EUROCAE
requirements. Therefore, the selected parameters meet the performance criteria for ATN (Aeronautical
Telecommunication Network) communications.</p>
      </sec>
      <sec id="sec-5-3">
        <title>5.3. Equipment quality influence coeficient</title>
        <p>It primarily reflects the impact of packet loss due to reduced codec bitrate. This value is based on results
from subjective quality assessments (Mean Opinion Score, MOS) and empirical observations in network
environments.</p>
        <p>Historically, the Ie values (equipment impairment factors) were determined using tabulated data
that related codec performance to packet loss. Today, this parameter is often described analytically
as a function that considers the baseline impedance of the codec and the efective packet loss rate, as
follows:</p>
        <p>= 0 + (95 −  0) ·  ef ,
• 0 is the baseline equipment impairment factor for the codec under ideal (lossless) conditions.
• ef is the efective percentage of packet loss, expressed as a value between 0 and 1.</p>
        <p>The resulting R value can be converted into a MOS (Mean Opinion Score) scale or directly interpreted
to assess speech intelligibility.</p>
        <p>This model enables the assessment of voice communication quality, taking into account the primary
network parameters, such as latency and packet loss, which directly impact speech intelligibility.</p>
      </sec>
      <sec id="sec-5-4">
        <title>5.4. Relationship between information transmission and e-model parameters</title>
        <p>
          The relationship between the amount of transmitted information and the parameters of the E-model can
be described using Information Theory. The formula for the information transmission rate is determined
through entropy [
          <xref ref-type="bibr" rid="ref24">24</xref>
          ]:
•  is the phoneme pronunciation rate (in phonemes per second),
• () is the entropy of speech (in bits per phoneme).
        </p>
        <p>To estimate the amount of information contained in a single phoneme, Shannon entropy is applied:
where  is the number of distinct phonemes in the language.</p>
        <p>For English, which contains approximately 44 phonemes:</p>
        <p>() = log 2(44) ≈ 5.46 bits/phoneme.</p>
        <p>However, due to the natural correlation between phonemes (resulting from syntactic and semantic
constraints), the actual entropy is lower than the theoretical maximum. For English, which is the oficial
language of ICAO communications, this efective entropy is typically estimated in the range of:
ef () ≈ 3.5–4.0 bits/phoneme.</p>
      </sec>
      <sec id="sec-5-5">
        <title>5.5. Impact of information loss on the R-factor</title>
        <p>The amount of information lost due to packet loss, noise, and signal distortion contributes to a reduction
in the overall R-factor. This information loss can be expressed as:</p>
        <p>lost = inf · PLR,
• inf is the total information rate (bits per second),
• PLR is the packet loss rate (a value from 0 to 1).</p>
        <p>The impairment factor due to codec losses, , can be modeled using the following expression:
 = 1 · PLR +  2 ·
︂(
1</p>
        <p>out )︂
− inf
• 1, 2 are codec-dependent coeficients reflecting sensitivity to packet loss and compression
• out is the amount of information preserved and successfully transmitted after codec processing.</p>
        <p>Thus, a smaller output information value out leads to a higher impairment factor , which in turn
reduces both the R-factor and the MOS (Mean Opinion Score). This highlights the importance of codec
eficiency and network reliability in preserving speech quality.</p>
      </sec>
      <sec id="sec-5-6">
        <title>5.6. Analysis of the impact of bandwidth and noise</title>
        <p>
          The formula for the amount of information at the output of the codec [
          <xref ref-type="bibr" rid="ref24">24</xref>
          ]:
out = 2maxΔ log2 1 +
︂(
 2 )︂
 2
.
        </p>
        <sec id="sec-5-6-1">
          <title>It shows:</title>
          <p>losses.
• If  22 is low (high noise level), then out drops →  decreases.</p>
          <p>• If  (quantization bit depth) is low, then information loss increases → MOS decreases.
This is consistent with the E-model, where  accounts for noise, and  accounts for compression
The main conclusion: The more information lost in the codec, the higher  and the lower MOS.</p>
        </sec>
      </sec>
      <sec id="sec-5-7">
        <title>5.7. The impact of packet loss on MOS</title>
        <p>Packet loss without recovery mechanisms can significantly afect voice intelligibility. The ratio of loss
to quality can be expressed in terms of a special variable , which depends on the codec:
 loss =  max −  · 
loss,
•  max – the maximum possible MOS level for the selected codec (e.g., 4.1 for G.711 or 3.9 for
• loss – packet loss rate in percent,
•  – sensitivity coeficient to packet loss (for G.711: 0.1, for G.729: 0.3).</p>
        <p>For example, if loss = 5% and the G.711 codec is used:</p>
        <p>loss = 4.5 − 0.1 × 5 = 4.0.</p>
        <p>That is, the voice quality is reduced due to the packet loss.</p>
      </sec>
      <sec id="sec-5-8">
        <title>5.8. Impact of equipment availability factor</title>
        <p>The equipment availability factor takes into account its reliability:</p>
        <p>final =  loss ×  eq,
 final = 4.0 × 0.98 = 3.92.
where eq is the equipment availability coeficient (from 0 to 1, where 1 is full availability).</p>
        <p>If, for example,  loss = 4.0, and equipment reliability eq = 0.98, then:
The lower the eq, the more speech intelligibility decreases.</p>
        <p>The final MOS formula, taking into account all parameters, looks like this:
  = ( max −  · 
loss) ×  eq.</p>
      </sec>
    </sec>
    <sec id="sec-6">
      <title>6. Load forecast for the Ukrainian ATN</title>
      <p>
        The basis for forecasting the load on the ATN/IPS network in Ukraine can be the mathematical model
of passenger trafic distribution on domestic airlines in Ukraine, which is proposed and considered in
detail in [
        <xref ref-type="bibr" rid="ref25">25</xref>
        ]. Since aviation telecommunications (voice and digital data exchange) serves passenger
trafic, the forecast of the load on it directly depends on passenger movements.
      </p>
      <p>In the current forecasting model, taking into account possible military-political situations, temporary
ceasefire with the presence of temporarily occupied territories, airports in the following cities are
considered: Dnipro (D), Kyiv (Kyiv + Boryspil) (K), Lviv (L), Odesa (O), Kharkiv (Kh) and potentially
Zhytomyr (Zh) and Uzhgorod (U).</p>
      <p>The model represents the transport system as a discrete Markov system, where city airports are
considered as possible states of the system, and flights between them are described as transitions
between these states. We assume that the transition from one state to another (a flight between some
pairs of airports) occurs with the corresponding time dependence of the local transition probability
 () , in the form of a system with a discrete number of states  = 7, transitions between which are
possible at discrete moments (for example, 1, 2, ..., 365). The indices  and  represent the departure
airport and the arrival airport, respectively.</p>
      <p>Model assumptions:
1. If a flight is made between certain airports, this means the transition of the system from state  to
state .
2. The probability of such a transition at a discrete time is denoted as  () ,
3. We conventionally assume that this indicator depends only on the very fact of the occurrence of
a transition-jump.</p>
      <p>The indexing of system states is as follows:</p>
      <p>D = 1,</p>
      <p>K = 2,</p>
      <p>L = 3,</p>
      <p>O = 4,</p>
      <p>Kh = 5,</p>
      <p>Zh = 6,</p>
      <p>U = 7.</p>
      <p>Since the system can be in one of  states, from which it may transition into one of the remaining
 − 1 states, then for each time point , it is necessary to specify  2 −  transition probabilities  () .
The transition system can be represented as an  ×  matrix:
⎡</p>
      <p>0
⎢  ()2,1
 () = ⎢⎢⎣ ...</p>
      <p>()1,2 · · ·  () 1, ⎤
0 · · ·  ()
... . . . ...</p>
      <p>2, ⎥
⎥ .
⎥
⎦
 (),1  (),2 · · ·
0</p>
      <p>This transition matrix can be represented as a discrete-state signal graph (Fig. 5), where system
transitions from state  to state  are interpreted as signal transmissions from one node to another, with
the transmission coeficient  ()  .</p>
      <p>The probability of a passenger transitioning from one state to another is determined using a function
depending on certain parameters:</p>
      <p>() =  (, ,  ,  ,   , ()),
where each parameter reflects the influence of various socio-economic and transport factors:
•  — City population: the relative share of the population of each city in the overall system is
taken into account.
•  — Wage coeficient: defined as the ratio of the average salary in the city to the total average
wage for all cities.
•  — Distance between cities: the normalized value of the distance between cities is used.
•  — Destination attractiveness: assessed by the level of business activity, tourist attractiveness,
the presence of industrial zones, etc.</p>
      <p>•   — Probability of choosing transport: takes into account travel time, ticket price, availability
of alternative modes of transport.
• () — The intensity of receipt of applications reflects variable seasonality and other time factors
that afect transport flows.</p>
      <p>The main parameters for assessing the load on air communication are:
• Data trafic volume: directly proportional to the number of flights between the nodes of the graph.
• Voice trafic intensity: depends on passenger trafic and travel time.
• Seasonal changes: peak loads on the communication network coincide with peak trafic periods.
• Capacity forecasting: the same transition probability matrix is used, but with special weighting
factors for communication.</p>
      <p>The proposed model allows for efective forecasting of passenger trafic distribution and load on
the aviation telecommunications network. It takes into account complex factors that afect route and
vehicle choices. Additionally, it enables the estimation of peak loads to optimize aviation infrastructure
and communication at both a specific airport and the network as a whole.</p>
    </sec>
    <sec id="sec-7">
      <title>7. Conclusions</title>
      <p>The analysis of ICAO and EUROCAE guidance documents systematizes the fundamental
requirements for VoIP systems in the aviation control field. Their compliance ensures high quality of voice
transmission, system reliability, and communication security. These requirements are mandatory for
implementing modern solutions in ATM systems and contribute to increasing the eficiency of air
navigation services.</p>
      <p>The implementation of ICAO and EUROCAE requirements in the ATN/IPS network is a strategically
important step in modernizing Ukraine’s aviation infrastructure following the end of the war. The
introduction of modern data transmission technologies will allow:
• To ensure high-quality communication between dispatching services, airports, and aircraft.
• To increase the level of cybersecurity of aviation infrastructure.</p>
      <p>• To integrate the Ukrainian ATN with the European air trafic control system.</p>
      <p>Thus, the gradual transition to ATN/IPS will enable Ukraine to restore its aviation sector, meet
international standards, and ensure the safe operation of airspace after its reopening.</p>
      <sec id="sec-7-1">
        <title>The authors have not employed any Generative AI tools.</title>
      </sec>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          <article-title>[1] ICAO, Manual on the Aeronautical Telecommunication Network (ATN) Using Internet Protocol Suite (IPS) Standards</article-title>
          and Protocols: Doc 9896,
          <year>2015</year>
          . 112pp.
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <string-name>
            <given-names>O.</given-names>
            <surname>Holubnychyi</surname>
          </string-name>
          ,
          <article-title>An Analysis of ICAO Requirements and Recommendations for Information Security of the ATN</article-title>
          ,
          <source>Information Protection</source>
          <volume>15</volume>
          (
          <year>2013</year>
          )
          <fpage>377</fpage>
          -
          <lpage>382</lpage>
          . In Ukrainian.
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [3]
          <string-name>
            <given-names>IETF</given-names>
            , RFC 8200:
            <surname>Internet</surname>
          </string-name>
          <string-name>
            <surname>Protocol</surname>
          </string-name>
          ,
          <source>Version</source>
          <volume>6</volume>
          (
          <issue>IPv6</issue>
          ) Specification,
          <year>2017</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          <source>[4] IETF, RFC 4291: IP Version 6 Addressing Architecture</source>
          ,
          <year>2006</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          [5]
          <string-name>
            <surname>IETF</surname>
          </string-name>
          , RFC 1323:
          <article-title>TCP Extensions for High Performance</article-title>
          ,
          <year>1992</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          [6] EUROCAE, ED-136:
          <article-title>Voice over IP ATM System Operational</article-title>
          and
          <string-name>
            <given-names>Technical</given-names>
            <surname>Requirements</surname>
          </string-name>
          ,
          <year>2009</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          [7] EUROCAE, ED-137:
          <article-title>Interoperability Standards for VoIP ATM Components</article-title>
          . Part 1:
          <string-name>
            <surname>Radio</surname>
          </string-name>
          ,
          <year>2009</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          [8] EUROCAE, ED-137:
          <article-title>Interoperability Standards for VoIP ATM Components</article-title>
          . Part 2:
          <string-name>
            <surname>Telephone</surname>
          </string-name>
          ,
          <year>2009</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          [9] EUROCAE, ED-137:
          <article-title>Interoperability Standards for VoIP ATM Components</article-title>
          . Part 3:
          <string-name>
            <surname>Recording</surname>
          </string-name>
          ,
          <year>2009</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          [10] EUROCAE, ED-138:
          <article-title>Network Requirements and Performances for VoIP ATM Systems</article-title>
          . Part 1:
          <string-name>
            <given-names>Network</given-names>
            <surname>Specification</surname>
          </string-name>
          ,
          <year>2009</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          <source>[11] IETF, RFC 3261: SIP: Session Initiation Protocol</source>
          ,
          <year>2002</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          [12]
          <string-name>
            <surname>ITU-T</surname>
            , Recommendation
            <given-names>H.</given-names>
          </string-name>
          <year>323</year>
          <source>: Packet-based multimedia communications systems</source>
          ,
          <year>2022</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          [13]
          <string-name>
            <surname>IETF</surname>
          </string-name>
          , RFC 3550:
          <article-title>RTP: A Transport Protocol for Real-Time Applications</article-title>
          ,
          <year>2003</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          [14]
          <string-name>
            <surname>ITU-T</surname>
          </string-name>
          , Recommendation G.
          <volume>711</volume>
          :
          <string-name>
            <surname>Pulse Code Modulation (PCM) of Voice</surname>
            <given-names>Frequencies</given-names>
          </string-name>
          ,
          <year>1988</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          [15]
          <string-name>
            <surname>ITU-T</surname>
          </string-name>
          , Recommendation G.
          <volume>729</volume>
          :
          <article-title>Coding of Speech Signals at 8 kbit/s using CS-ACELP,</article-title>
          <year>2007</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref16">
        <mixed-citation>
          [16]
          <string-name>
            <given-names>M.</given-names>
            <surname>Zaliskyi</surname>
          </string-name>
          , et al.,
          <article-title>Heteroskedasticity analysis during operational data processing of radio electronic systems</article-title>
          , in: S. Shukla,
          <string-name>
            <given-names>A.</given-names>
            <surname>Unal</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J. V.</given-names>
            <surname>Kureethara</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D. K.</given-names>
            <surname>Mishra</surname>
          </string-name>
          , D. S. Han (Eds.),
          <source>Data Science and Security</source>
          , volume
          <volume>290</volume>
          <source>of Lecture Notes in Networks and Systems</source>
          , Springer,
          <year>2021</year>
          , pp.
          <fpage>168</fpage>
          -
          <lpage>175</lpage>
          . doi:
          <volume>10</volume>
          .1007/
          <fpage>978</fpage>
          -981-16-4486-3_
          <fpage>18</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref17">
        <mixed-citation>
          [17]
          <string-name>
            <given-names>O.</given-names>
            <surname>Okoro</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Zaliskyi</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Dmytriiev</surname>
          </string-name>
          ,
          <string-name>
            <given-names>O.</given-names>
            <surname>Solomentsev</surname>
          </string-name>
          ,
          <string-name>
            <given-names>O.</given-names>
            <surname>Sribna</surname>
          </string-name>
          ,
          <article-title>Optimization of maintenance task interval of aircraft systems</article-title>
          ,
          <source>International Journal of Computer Network and Information Security</source>
          <volume>14</volume>
          (
          <year>2022</year>
          )
          <fpage>77</fpage>
          -
          <lpage>89</lpage>
          . doi:
          <volume>10</volume>
          .5815/ijcnis.
          <year>2022</year>
          .
          <volume>02</volume>
          .07.
        </mixed-citation>
      </ref>
      <ref id="ref18">
        <mixed-citation>
          [18]
          <string-name>
            <given-names>O.</given-names>
            <surname>Solomentsev</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Zaliskyi</surname>
          </string-name>
          ,
          <string-name>
            <given-names>T.</given-names>
            <surname>Herasymenko</surname>
          </string-name>
          ,
          <string-name>
            <given-names>O.</given-names>
            <surname>Kozhokhina</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Y.</given-names>
            <surname>Petrova</surname>
          </string-name>
          ,
          <article-title>Eficiency of operational data processing for radio electronic equipment</article-title>
          ,
          <source>Aviation</source>
          <volume>23</volume>
          (
          <year>2020</year>
          )
          <fpage>71</fpage>
          -
          <lpage>77</lpage>
          . doi:
          <volume>10</volume>
          .3846/aviation.
          <year>2019</year>
          .
          <volume>11849</volume>
          .
        </mixed-citation>
      </ref>
      <ref id="ref19">
        <mixed-citation>
          [19]
          <string-name>
            <given-names>O.</given-names>
            <surname>Solomentsev</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Zaliskyi</surname>
          </string-name>
          ,
          <string-name>
            <given-names>O.</given-names>
            <surname>Kozhokhina</surname>
          </string-name>
          , T. Herasymenko,
          <article-title>Eficiency of data processing for UAV operation system</article-title>
          ,
          <source>in: 2017 IEEE 4th International Conference on Actual Problems of Unmanned Aerial Vehicles Developments (APUAVD)</source>
          ,
          <year>2017</year>
          , pp.
          <fpage>27</fpage>
          -
          <lpage>31</lpage>
          . doi:
          <volume>10</volume>
          .1109/APUAVD.
          <year>2017</year>
          .
          <volume>8308769</volume>
          .
        </mixed-citation>
      </ref>
      <ref id="ref20">
        <mixed-citation>
          [20]
          <string-name>
            <surname>ITU-T</surname>
          </string-name>
          , Recommendation P.
          <volume>800</volume>
          :
          <article-title>Methods for subjective determination of transmission quality</article-title>
          ,
          <year>1996</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref21">
        <mixed-citation>
          [21]
          <string-name>
            <surname>ITU-T</surname>
          </string-name>
          , Recommendation G.
          <volume>107</volume>
          :
          <article-title>The E-model, a computational model for use in transmission planning</article-title>
          ,
          <year>2005</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref22">
        <mixed-citation>
          [22]
          <string-name>
            <surname>ITU-T</surname>
          </string-name>
          , Recommendation G.
          <volume>728</volume>
          : Coding of Speech at 16 Kbit/s
          <string-name>
            <given-names>Using</given-names>
            <surname>Low-delay</surname>
          </string-name>
          <string-name>
            <surname>CELP</surname>
          </string-name>
          ,
          <year>1992</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref23">
        <mixed-citation>
          [23]
          <string-name>
            <given-names>V.</given-names>
            <surname>Luconi</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Vecchio</surname>
          </string-name>
          ,
          <article-title>Impact of the first months of war on routing and latency in Ukraine</article-title>
          ,
          <source>Computer Networks</source>
          <volume>224</volume>
          (
          <year>2023</year>
          ). doi:
          <volume>10</volume>
          .1016/j.comnet.
          <year>2023</year>
          .
          <volume>109596</volume>
          .
        </mixed-citation>
      </ref>
      <ref id="ref24">
        <mixed-citation>
          [24]
          <string-name>
            <given-names>G.</given-names>
            <surname>Konakhovych</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Zaliskyi</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Tarasiuk</surname>
          </string-name>
          ,
          <string-name>
            <given-names>B.</given-names>
            <surname>Chumachenko</surname>
          </string-name>
          ,
          <string-name>
            <given-names>V.</given-names>
            <surname>Bosko</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Y.</given-names>
            <surname>Parhomenko</surname>
          </string-name>
          ,
          <article-title>Assessment of the availability of communication channels with UAVs</article-title>
          ,
          <source>in: CEUR Workshop Proceedings</source>
          , volume
          <volume>3732</volume>
          ,
          <year>2024</year>
          , pp.
          <fpage>45</fpage>
          -
          <lpage>57</lpage>
          . URL: https://ceur-ws.
          <source>org/</source>
          Vol-
          <volume>3732</volume>
          /paper04.pdf.
        </mixed-citation>
      </ref>
      <ref id="ref25">
        <mixed-citation>
          [25]
          <string-name>
            <given-names>I. O.</given-names>
            <surname>Kozliuk</surname>
          </string-name>
          ,
          <article-title>Ensuring the economic security of the aviation industry</article-title>
          , NAU, Kyiv,
          <year>2005</year>
          .
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>