Patent Description:
As the number of applications and services for digital data continues to explode, the demands and challenges placed on network resources and operators will continue to increase. Being able to deliver a wide variety of network performance characteristics that future services will demand is one of the primary technical challenges faced by service providers today.

Timing for random access may be dependent upon an amount of delay time that communications are in transition between a transmitter and receiver. Current techniques for random access may account for delay time within terrestrial networks (e.g., communications between devices on the Earth) but not for non-terrestrial networks (e.g., communications between a satellite orbiting the Earth and a device not orbiting the Earth). Therefore, current techniques for random access may not be entirely satisfactory.

3GPP Draft R2-<NUM>, <NPL> and 3GPP Draft R1-<NUM> are related prior art documents, addressing the problem of how to achieve power saving in random access response monitoring, when considering the propagation delay for mobile communications in Non-Terrestrial Networks, or NTN.

The exemplary embodiments disclosed herein are directed to solving the issues relating to one or more of the problems presented in the prior art, as well as providing additional features that will become readily apparent by reference to the following detailed description when taken in conjunction with the accompany drawings. In accordance with various embodiments, exemplary systems, methods, devices and computer program products are disclosed herein. It is understood, however, that these embodiments are presented by way of example and not limitation.

Thus, the invention is described by the combination of the embodiments related to <FIG> and <FIG>.

Various exemplary embodiments of the invention are described below with reference to the accompanying figures to enable a person of ordinary skill in the art to make and use the invention.

Additionally, the specific order or hierarchy of steps in the methods disclosed herein are merely exemplary approaches. Based upon design preferences, the specific order or hierarchy of steps of the disclosed methods or processes can be re-arranged while remaining within the scope of the present invention. Thus, those of ordinary skill in the art will understand that the methods and techniques disclosed herein present various steps or acts in a sample order, and the invention is not limited to the specific order or hierarchy presented unless expressly stated otherwise.

The discussion below may refer to functional entities or processes which are similar to those mentioned above with respect to conventional communication systems. As would be understood by persons of ordinary skill in the art, however, such conventional functional entities or processes do not perform the functions described below, and therefore, would need to be modified or specifically configured to perform one or more of the operations described below. Additionally, persons of skill in the art would be enabled to configure functional entities to perform the operations described herein after reading the present disclosure.

<FIG> illustrates an exemplary wireless communication network <NUM> in which techniques disclosed herein may be implemented, in accordance with an embodiment of the present disclosure. Such an exemplary network <NUM> includes a base station <NUM> (hereinafter "BS <NUM>") and multiple user equipment devices <NUM> (hereinafter "UEs <NUM>") that can communicate with each other via respective communication links <NUM> (e.g., a wireless communication channel), and a cluster of notional cells <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM> and <NUM> overlaying a geographical area with a network <NUM>. Each UE <NUM> may undergo a random access procedure to join the network <NUM>. In <FIG>, the BS <NUM> and each UE <NUM> are contained within a respective geographic boundary of cell <NUM>. Each of the other cells <NUM>, <NUM>, <NUM>, <NUM>, <NUM> and <NUM> may include at least one BS operating at its allocated bandwidth to provide adequate radio coverage to its intended users. Accordingly, reference to a cell may be a short hand reference to a BS with an associated coverage region or area (e.g., cell). In certain embodiments, a cell may be interchangeably referred to as a BS or a node.

For example, the BS <NUM> may operate at an allocated channel transmission bandwidth (e.g., spectrum) to provide adequate coverage to each UE <NUM>. The spectrum may be regulated to define a licensed range and/or an unlicensed range. The BS <NUM> and each UE <NUM> may communicate via a downlink radio frame <NUM>, and an uplink radio frame <NUM> respectively. The radio frames may also be referred to more simply as a frame. Each frame <NUM>/<NUM> may be further divided into sub-frames <NUM>/<NUM> which may include data symbols <NUM>/<NUM>. In the present disclosure, the BS <NUM> and each UE <NUM> are described herein as non-limiting examples of "communication nodes," generally, which can practice the methods disclosed herein. Such communication nodes may be capable of wireless and/or wired communications, in accordance with various embodiments of the invention. In certain embodiments, a communication device may refer more specifically to a UE in relationship to a BS and a communication node may refer more specifically to a BS in relation to the UE.

<FIG> illustrates a block diagram of an exemplary wireless communication system <NUM> for transmitting and receiving wireless communication signals (e.g., OFDM/OFDMA signals) in accordance with some embodiments of the invention. The system <NUM> may include components and elements configured to support known or conventional operating features that need not be described in detail herein. In one exemplary embodiment, system <NUM> can be used to transmit and receive data symbols in a wireless communication environment such as the wireless communication environment or network <NUM> of <FIG>, as described above.

The BS <NUM> communicates with the UE <NUM> via a communication channel <NUM>, which can be any wireless channel or other medium known in the art suitable for transmission of data as described herein.

In accordance with some embodiments, the UE transceiver module <NUM> may be referred to herein as an "uplink" transceiver module <NUM> that includes a RF transmitter and receiver circuitry that are each coupled to the antenna <NUM>. Similarly, in accordance with some embodiments, the BS transceiver module <NUM> may be referred to herein as a "downlink" transceiver module <NUM> that includes RF transmitter and receiver circuity that are each coupled to the antenna <NUM>. The operations of the two transceiver modules <NUM> and <NUM> are coordinated in time such that the uplink receiver is coupled to the uplink antenna <NUM> for reception of transmissions over the wireless transmission link <NUM> at the same time that the downlink transmitter is coupled to the downlink antenna <NUM>.

The UE transceiver module <NUM> and the BS transceiver module <NUM> are configured to communicate via the wireless data communication link <NUM>, and cooperate with a suitably configured RF antenna arrangement <NUM>/<NUM> that can support a particular wireless communication protocol and modulation scheme. In some exemplary embodiments, the UE transceiver module <NUM> and the BS transceiver module <NUM> are configured to support industry standards such as the Long Term Evolution (LTE) and emerging <NUM> standards, and the like. It is understood, however, that the invention is not necessarily limited in application to a particular standard and associated protocols. Rather, the UE transceiver module <NUM> and the BS transceiver module <NUM> may be configured to support alternate, or additional, wireless data communication protocols, including future standards or variations thereof.

The memory modules <NUM> and <NUM> may be realized as RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, a hard disk, a removable disk, a CD-ROM, or any other form of storage and/or computer-readable medium known in the art. In this regard, memory modules <NUM> and <NUM> may be coupled to the transceiver modules <NUM> and <NUM>, respectively, such that the transceiver modules <NUM> and <NUM> can read information from, and write information to, memory modules <NUM> and <NUM>, respectively. The memory modules <NUM> and <NUM> may also be integrated into their respective transceiver modules <NUM> and <NUM>. In some embodiments, the memory modules <NUM> and <NUM> may each include a cache memory for storing temporary variables or other intermediate information during execution of instructions to be executed by transceiver modules <NUM> and <NUM>, respectively. Memory modules <NUM> and <NUM> may also each include non-volatile memory for storing instructions to be executed by the transceiver modules <NUM> and <NUM>, respectively.

The network communication module <NUM> generally represents the hardware, software, firmware, processing logic, and/or other components of the base station <NUM> that enable bidirectional communication between the BS transceiver module <NUM> and other network components and communication nodes configured to communication with the base station <NUM>. In a typical deployment, without limitation, network communication module <NUM> provides an <NUM> Ethernet interface such that the BS transceiver module <NUM> can communicate with a conventional Ethernet based computer network. The terms "configured for," "configured to" and conjugations thereof, as used herein with respect to a specified operation or function, refer to a device, component, circuit, structure, machine, signal, etc., that is physically or virtually constructed, programmed, formatted and/or arranged to perform the specified operation or function.

With the development of the <NUM> new radio (NR) access technologies, a broad range of use cases including enhanced mobile broadband, massive machine-type communications (MTC), critical MTC, and the like can be realized. To expand the utilization of NR access technologies, <NUM> connectivity via satellites is being considered as a promising new application. In contrast to the terrestrial networks where all communication nodes (e.g., BSes) are located on the Earth, a network incorporating satellites in orbit or within airborne vehicles (e.g., a high altitude platform station (HAPS)) that perform some or all of the functions of terrestrial base stations is referred to as a non-terrestrial network (NTN).

In NTNs, the satellites may be Geostationary Earth Orbit (GEO) satellites, Low Earth Orbit (LEO) satellites or Medium Earth Orbit (MEO) satellites. A GEO satellite may run in an orbit with altitude of, for example, <NUM>,<NUM> kilometers (km), which implies a minimum round trip delay (RTD) that may be <NUM>*<NUM>*35786e3/3e8 = <NUM> milliseconds (ms) with a bentpipe GEO payload. For a LEO satellite with, for example, a <NUM> orbit altitude, a corresponding minimum round trip delay (RTD) may be <NUM>*600e3/3e8 = <NUM> with a regenerative LEO payload. Accordingly, a challenge brought by the large RTD of NTNs is how to handle random access given the large RTD.

Furthermore, a satellite beam footprint diameter could be, for example, <NUM> or even larger in diameter. Also, a minimum elevation angle for a satellite beam could be, for example, as small as <NUM>°. Either or both large beam footprints and small elevation angles may result in significantly different RTDs in a single beam.

Accordingly, systems and methods in accordance with various embodiments include random access timing with an adaptive scheme (e.g., an adaptive random access response monitoring window) for different orbit altitudes, beam footprint sizes and elevation angles. In various embodiments, the minimum and maximum time delay (or corresponding minimum and maximum distance) may be broadcast in system information. Also, in various embodiments, a differential delay in a specific beam may be used to determine the monitoring window length in a random access procedure. Advantageously, an adaptive random access response monitoring window length can be calculated for satellites with different orbit altitudes, satellite payload types, beam footprint sizes, and elevation angles. Thus, users (e.g., UEs) can derive their random access monitoring window length according to their own capability (e.g., on a per UE basis), which saves on both power and dedicated signaling for random access.

<FIG> is a sequence diagram illustrating a contention based random access procedure <NUM>, in accordance with some embodiments. The procedure <NUM> may be performed by a UE <NUM> and a BS <NUM>. It is noted that the procedure <NUM> is merely an example, and is not intended to limit the present disclosure. Accordingly, it is understood that additional operations (e.g., blocks) may be provided before, during, and after the procedure <NUM> of <FIG>, certain operations may be omitted, certain operations may be performed concurrently with other operations, and that some other operations may only be briefly described herein.

At operation <NUM>, a random access preamble message may be sent from the UE <NUM> to the BS <NUM>. In certain embodiments, the random access preamble message of operation <NUM> may be referred to as a Message <NUM> of random access. At operation <NUM>, a random access response message may be sent from the BS <NUM> to the UE <NUM>. In certain embodiments, the random access response message of operation <NUM> may be referred to as a Message <NUM> of random access. At operation <NUM>, a scheduled transmission message may be sent from the UE <NUM> to the BS <NUM>. In certain embodiments, the scheduled transmission message of operation <NUM> may be referred to as a Message <NUM> of random access. At operation <NUM>, a contention resolution message may be sent from the BS <NUM> to the UE <NUM>. In certain embodiments, the contention resolution message of operation <NUM> may be referred to as a Message <NUM> of random access.

In various embodiments, once the random access preamble (e.g., the Message <NUM>) is transmitted, the UE may start a timer (e.g., a ra-ResponseWindow timer) at the first physical downlink control channel (PDCCH) occasion from the end of the random access preamble message transmission. Thus, the UE monitors the PDCCH while ra-ResponseWindow is running. The ra-ResponseWindow may have an enumerated type with range (e.g., noted with index values as sl1, sl2, sl4, sl8, sl10, sl20, sl40, sl80 defined in certain communication standards).

In particular embodiments, a network may configure a value for the ra-ResponseWindow that is lower than or equal to <NUM>. However, taking GEO as an example, the maximum delay difference experienced by different UEs (e.g., a near UE and a far UE) in a beam can be as large as <NUM>, if a <NUM> degree minimum elevation is assumed. Therefore the current ra-ResponseWindow range may not be enough to cover different UEs (e.g., the near UE and the far UE) in a same beam. Accordingly, each UE may adopt an adaptive random access response monitoring window so that the random access response monitoring window at each UE will be sufficient for each UE to receive the same transmission from the BS (e.g., no matter if the UE is the near UE closest to the BS or the far UE farthest from the BS).

In numerous embodiments, for a specific beam, a single trip propagation delay (e.g., between a UE and a BS that communicates using a satellite) may range from a minimum delay (also referred to as delay_min) and a maximum delay (also referred to as delay_max). As will be discussed further below, a delay differential between the delay_min and delay_max may be referred to as a delay_differential. The values may vary according to satellite orbit altitude, satellite payload type, beam footprint size, and elevation angle. To help UEs in a single beam to monitor for their random access responses, the following information may be broadcast in system information. Accordingly, a UE may receive the broadcast system information to determine its adaptive random access response window length. This broadcast system information may be referred to as among four different Options broadcast from a BS (e.g., a BS in a NTN), for ease of explanation.

In Option <NUM>, a delay_min and delay_max are broadcast. Alternatively, in Option <NUM>, a <NUM>*delay_min (e.g., two times delay_min) and <NUM>*delay_max (e.g., two times delay_max) are broadcast.

In Option <NUM>, a delay_min and delay_differential are broadcast, where delay _differential = delay_max - delay_min. Alternatively, in Option <NUM>, <NUM>*delay_min and <NUM>*delay_differential are broadcast, where <NUM>*delay_differential = <NUM>*(delay_max - delay_min).

In Option <NUM>, a current serving satellite orbit altitude (derivable from the satellite's ephemeris), a satellite payload type, a minimum elevation angle, and a maximum elevation angle of current serving beam are broadcast. From these parameters, delay_min, delay_max and delay_differential may be obtained (e.g., determined) at a receiving UE.

In Option <NUM>, a set of satellite parameters may be broadcast. This set of satellite parameters may include an orbit altitude (derivable from the satellite's ephemeris), a satellite payload type, a minimum elevation angle, and a maximum elevation angle. In particular embodiments, with Option <NUM>, the set of the serving beam parameters may be variable with time. Accordingly, the delay_min, delay_max and delay_differential may be obtainable (e.g., determined) by a receiving UE based on the set of satellite parameters.

In various embodiments, referred to for ease of explanation as Case <NUM>, a UE may not have access to situation information that characterizes a location of the UE, an ephemeris of a satellite or a trajectory of a HAPS used by a BS, and a payload type of the satellite or the HAPS used by the BS. Accordingly, the UE may not be able to determine the exact amount of propagation delay when the UE does not have such situation information. Thus, to save its power in random access response monitoring, the UE may start its monitoring window from T1+delay_min*<NUM> after its Message <NUM> transmission, where T1 is a Message <NUM> transmission time. Since the propagation delay of this UE ranges in from delay_min to delay_max, the random access response window length (also referred to as adapt RAR_win_len) may be be <NUM>*(delay_max - delay_min) + orig_RAR_win_len. In certain embodiments, an original random access response window (also referred to as orig_RAR_win_len), for example, may refer to a ra-ResponseWíndow parameter value defined in certain communication standards. If the broadcast system information includes the delay_min and delay_differential, the adaptive random access response window length can be referred to as adapt_RAR_win_len = <NUM>*delay_differential + orig_RAR_win_len.

<FIG> is a diagram that illustrates how an adaptive random access response window length is determined when a UE does not have access to situation information, in accordance with some embodiments. A consistent amount of time may pass along a horizontal axis but be broken up, for ease of explanation, among a first UE, a second UE, and a BS. The BS may be configured to receive a Message <NUM> from the first UE (also noted as UE <NUM>) and the second UE (also noted as UE <NUM>). So that both the Message <NUM> from the first UE and the second UE is received at the same time, the Message <NUM> from the first UE may be transmitted at a first time <NUM> and the Message <NUM> from the second UE may be transmitted at a second time <NUM>. Then, both the message <NUM> from the first UE and the second UE may arrive at the BS at a third time <NUM>. The BS may then transmit a respective Message <NUM> in response to receipt of the Message <NUM> from the first UE and the second UE at the third time <NUM>. Accordingly, the respective Message <NUM> may be received at the second UE at a fourth time <NUM> and the respective Message <NUM> may be received at the first UE at a fifth time <NUM>.

As illustrated, a delay_min may be between the second time <NUM> and the third time <NUM> or the third time <NUM> and the fourth time <NUM>. Also, a delay_max may be between the first time <NUM> and the third time <NUM> or the third time <NUM> and the fifth time <NUM>. Furthermore, an adapt_RAR_win_len 420A may begin for the first UE after two delay_mins have elapsed (e.g., after a minimum amount of round trip delay) after Message <NUM> transmission. In this manner, the fifth time <NUM> may occur during the adapt_RAR_win_len 420A of the first UE. Also, an adapt_RAR_win_len 420B for the second UE may also begin after two delay_mins have elapsed (e.g., after a minimum amount of round trip delay) after Message <NUM> transmission. Thus, the fourth time <NUM> may occur during the adapt_RAR_win_len 420B of the second UE.

As noted above, the delay_min and delay_max is determined from the broadcast system information of a BS. Also, the adapt_RAR_win_len may be determined from the delay_min and delay_max as <NUM>*delay_differential + orig_RAR_win_len, where the delay_differential is the differential between the delay_min and the delay_max and the orig_RAR_win_len is provided in system information.

In particular embodiments, referred to for ease of explanation as Case <NUM>, a UE has access to situation information that characterizes a location of the UE, an ephemeris of a satellite or a trajectory of a HAPS used by a BS, and a payload type of the satellite or the HAPS used by the BS. Accordingly, the UE may be able to determine the exact amount of propagation delay when the UE does have such situation information. The exact amount of propagation delay may be referred to as delay_calc. Accordingly, in certain optional embodiments, the UE can ignore the aforementioned Options in a system broadcast (e.g., the UE may ignore the broadcast system information to determine the delay_min and/or delay_max). The UE starts its monitoring window from T1+delay_calc*<NUM> after its Message <NUM> transmission, where T1 is the Message <NUM> transmission time. Accordingly, the adapt_RAR_win_len may be the orig_RAR_win_len. The orig_RAR_win_len may refer to, for example, a predetermined value (e.g., ra-ResponseWindow) defined in certain communication standards.

<FIG> is a diagram that illustrates how an adaptive random access response window length is determined when a UE has access to situation information, in accordance with some embodiments. A consistent amount of time may pass along a horizontal axis but be broken up, for ease of explanation, among a first UE (also noted as UE <NUM>), a second UE (also noted as UE <NUM>), and a BS. The BS may be configured to receive a Message <NUM> from the first UE and the second UE. So that both the Message <NUM> from the first UE and the second UE is received at the same time, the Message <NUM> from the first UE may be transmitted at a first time <NUM> and the Message <NUM> from the second UE may be transmitted at a second time <NUM>. Then, both the respective message <NUM> from the first UE and the second UE may arrive at the BS at a third time <NUM>. The BS may then transmit a respective Message <NUM> in response to receipt of the Message <NUM> from the first UE and the second UE at the third time <NUM>. Accordingly, the respective Message <NUM> may be received at the second UE at a fourth time <NUM> and the respective Message <NUM> may be received at the first UE at a fifth time <NUM>.

As illustrated, a delay_calc for the second UE (e.g., delay_calc, <NUM>) may be between the second time <NUM> and the third time <NUM> or the third time <NUM> and the fourth time <NUM>. Also, a delay_calc for the first UE (e.g., delay_calc, <NUM>) may be between the first time <NUM> and the third time <NUM> or the third time <NUM> and the fifth time <NUM>. Furthermore, an adapt_RAR_win_len 520A begins for the first UE after two instances of delay_calc <NUM> have elapsed (e.g., after a calculated amount of round trip delay) after Message <NUM> transmission. In this manner, the fifth time <NUM> may occur during the adapt_RAR_win_len 520A of the first UE. Also, an adapt_RAR_win_len 520B for the second UE may also begin after two instances of delay_calc <NUM> have elapsed (e.g., after a calculated amount of round trip delay) after Message <NUM> transmission. Thus, the fourth time <NUM> may occur during the adapt_RAR_win_len 520B of the second UE.

As noted above, the delay_min and delay_max need not be determined from the broadcast system information of a BS when the UE has access to situation information. Rather, the adapt_RAR_win_len may be determined as the orig_RAR_win_len is provided in system information since the delay time specific for the UE may be calculated. Furthermore, in particular embodiments, it can be seen from a comparasion between <FIG> and <FIG> that the adapt_RAR_win_len of Option <NUM> is longer than that of Option <NUM>.

In various embodiments, a UE may additionally determine the adapt_RAR_win_len as outlined in Option <NUM> when the UE has access to situation information that characterizes a location of the communication device, an ephemeris of the satellite, and a payload type of the satellite. The UE may utilize the determination of adapt_RAR_win_len as outlined in Option <NUM> to guarantee a more reliable random access response monitoring. In certain embodiments, this redundant determination of adapt_RAR_win_len may be applied for UEs that are on vehicles or in other situations for which power consumption (e.g., the available power supply) is not as important (e.g., not as constrained) as other issues such as accuracy. In particular embodiments, this redundant determination of adapt_RAR_win_len may be applied when the UE does not receive a random access response (e.g., Message <NUM>) within its expected adapt_RAR_win_len (e.g., in case the determination of adapt_RAR_win_len in Option <NUM> was incorrect).

In certain embodiments, certain UEs may have lower capabilities or limited resources. For example, certain more constrained UEs (e.g., low cost Internet of Things (IoT) UEs) may be more power or processing constrained than other UEs. These more constrained UEs may utilize, for example, a look up table (LUT) to determine values, such as a delay_min, delay_max, or a delay_differential. This LUT may also cover an epheremis. An example LUT is provided in table <NUM>, below:.

The more constrained UEs may search the LUT to find an appropriate delay_min, delay_max, or a delay_differential in accordance with the broadcast system information. Since the more constrained UEs may be produced for specific applications (e.g., only for GEO with a given minimum elevation angle), the predetermined or pre-stored LUT may be utilized so that the more constrained UEs may be able to determine the delay_min, delay_max, or delay_differential without actually performing calculations for delay_min, delay_max, or delay_differential. Then, the more constrained UEs may determine their adapt_RAR_win_len in accordance with Case <NUM>.

In certain embodiments, a NTN BS may utilize a steering beam. Accordingly, different sets of satellite parameters may be transmitted in the steering beam at different times. For example, a first set of satellite parameters, referred to as Set A, may include, for example, an orbit altitude/ephemeris, serving start time, serving duration, and satellite payload type. Set A may be broadcast during a first period of time, referred to as Period A. A second set of satellite parameters, refereed to as Set B, may include, for example, a minimum elevation angle and a maximum elevation angle. This Set B may be broadcast during a second period of time, referred to as Period B. Period B may immediately follow Period A. Also, Period A and Period B may be of a same amount of time in certain embodiments, or may be of a different amount of time in other embodiments. In particular embodiments, Set A may have static satellite parameter values while Set B may have varying satellite parameter values. Also, in further embodiments, Period A may be longer than Period B.

In various embodiments, a UE may receive (e.g., listen to) Set A when the UE accesses the NTN BS's network. Then, the UE may receive (e.g., listen to) Set B to track/update the satellite or beam specific parameters after receiving Set A. Accordingly, the UE may determine an appropriate delay_min and delay_max by receiving Set A and Set B from the NTN BS steering beam.

It is also understood that any reference to an element or embodiment herein using a designation such as "first," "second," and so forth does not generally limit the quantity or order of those elements.

Additionally, one or more of the functions described in this document may be performed by means of computer program code that is stored in a "computer program product", "computer-readable medium", and the like, which is used herein to generally refer to media such as, memory storage devices, or storage unit. These, and other forms of computer-readable media, may be involved in storing one or more instructions for use by processor to cause the processor to perform specified operations. Such instructions, generally referred to as "computer program code" (which may be grouped in the form of computer programs or other groupings), which when executed, enable the computing system to perform the desired operations.

Claim 1:
A method performed by a communication device, comprising:
receiving system information from a communication node, wherein the communication node communicates using a satellite in orbit or a high altitude platform station, HAPS; and
determining the start of a random access response window and monitoring for a signal from the communication node within the random access response window, wherein the determining the start of the random access response window comprising:
determining a minimum propagation delay, delay_min, for communications between the communication device and the communication node, based on the system information; or
determining a propagation delay, delay_calc, for communications between the communication device and the communication node, based on the system information and situation information, wherein the random access response window:
starts from T1+delay_min*<NUM>, where T1 is a Message <NUM> transmission finish time of the communication device, if the communication device does not have access to situation information; or
starts from T1+delay_calc*<NUM>, where T1 is a Message <NUM> transmission finish time of the communication device, if the communication device has access to situation information, wherein the situation information comprises at least one of:
a location of the communication device,
an ephemeris of the satellite, or
a trajectory of the HAPS, or
a payload type of the satellite or the HAPS.