I Introduction
The future radio access networks (RAN) is expected to provide ubiquitous connectivity for any users or devices at any time with diversified service requirements [1]. However, coverage holes (CH) of terrestrial RAN prevail in both urban and rural scenarios due to the lack of infrastructures or deeply blocking by obstacles [2]. Specifically, as the terrestrial RAN are statically fixed in certain geographical locations, it is normally hard to ensure the quality of service (QoS) of users that are uneven and dynamically distributed in both spatial and temporal domain [3]. One solution to address those CHs is to deploy massive small cells, which, however, is inefficient and costly for RAN operators [4]. To overcome the coverage and flexibility challenges faced by current RAN, the emerging drone, a.k.a. unmanned aerial vehicle (UAV), communication technology is proposed as a promising solution.
Equipped with specific wireless transceivers, drones can communicate with both terrestrial users and cellular base stations (BSs) using WiFi [5] or LTE [6] technologies. By integrating drone communication with terrestrial RAN, the drone assisted radio access networks (DARAN), in which drones perform as drone base stations (DBSs) to relay data between users in areas of interests (AoIs) and the associated terrestrial BS^{1}^{1}1In this paper, the abbreviation BS means the terrestrial base station and DBS is referred to as drone base station., has been proposed and verified by field experiments [7]
. In DARAN, AoI includes both the CHs and the traffic dense spots (TDBs) where the allocated RAN spectrum resources are temporarily inadequate, e.g. congested road, concerts and sports events, etc. Compared with the terrestrial RAN, DARAN advances in following four aspects: 1) The lineofsight (LoS) probability for the DBStoground (D2G) wireless link is higher than the terrestrial BStouser wireless link
[4]. Experiments indicate that LoS links probability is the dominating factor to increase network performance [8]; 2) DBSs can be dynamically deployed and dispatched to different controllers/users with respect to the spatial and temporal traffic variations [9]; 3) unlike connected vehicles whose mobility is controlled by drivers or autonomous driving controller, the trajectories of DBSs can be fully controlled by system providers, which empowers DBSs with the dynamic deployment feature [10] [11]; 4) DBS are capable of executing computing tasks by equipping with CPU or caching modules [12] [13]. However, it is challenging to fully utilize the potential of DBSs due to the following two reasons. First, the 3D mobility of DBS poses great complexity on the DBS spatial placement, especially in multiDBS scenarios [14]. Second, specific channel models are required to highlight the unique features of DBStouser (D2U) and DBStoBS (D2B) channels[15].Several studies optimizing the multiDBS spatial placements to support terrestrial users emerges in recent year, which can be divided into two categories, i.e., static DBS deployment and DBS trajectory planning. The static DBS deployment research focus on optimizing the hovering positions of DBSs to maximize terrestrial users QoS. However, the static deployment fails to guarantee the fairness for users, in which the users located at the edge of the DBS’s radio coverage suffer relatively higher pathloss compared with the users located at the center of the DBS’s coverage. In addition, most existing DBS deployment works focus on optimizing the D2U communication, while ignore or idealize the D2B link quality constraints.
To promote the fairness for all users and maintain low deployment cost, some researchers further propose the DBS trajectory planning approach that allows DBSs fly over and serve AoIs periodically according to designed trajectories. The purpose of DBS trajectory planning is optimizing AoIs association and trajectory for each DBS to maximize user QoS [16] [17]. However, three issues remain unsolved in current works. First, to reduce the complexity of optimization problems, most existing works assume that all DBSs fly at a predefined constant height, which shrinks the 3D trajectory planning into a 2D horizontal trajectory planning, and fails to realize the performance improvements by adjusting DBS flying heights. Second, the commonly used assumption of Friis free space propagation model cannot reflect the unique D2G channel features. Third, the D2B link quality constraint is also omitted by most DBS trajectory planning works.
To address those issues, in this paper, we investigate the 3D trajectory planning and scheduling for multiple DBSs in the DARAN. Considering the stateoftheart D2U [18] and D2B [6] channel models, and constraints of D2B link qualities, the multiDBS 3D trajectory planning problem is formulated as a mixed integer nonlinear programming (MINLP) problem which aims at minimizing the average D2U pathloss for all users within one trajectory period. By decoupling the MINLP problem into multiple quasiconvex or integer linear programming (ILP) subproblems, we can separately optimize the AoI association, D2U communication scheduling, DBS horizontal trajectories and flying heights in each subproblem, respectively. In essence, we adopt the block coordinate descent (BCD) mechanism to devise a multiDBS 3D trajectory planning and scheduling algorithm, in which the subproblems are iteratively optimized and converge to the optima. The main contributions of this work are listed as follows:

We investigate the 3D trajectory planning of multiple DBSs in which both the flying heights and horizontal trajectories of DBS are optimized together instead of optimizing horizontal trajectories on a 2D plane. As far as we know, this is the first work considering the real 3D trajectory in which the flying height of any DBS can be adjusted at different slots on its trajectory.

To make the system model more practical, we employ the stateoftheart D2U and D2B pathloss models rather than the traditional pathloss models (e.g., Friis equation) in the system model. We formulate the multiDBS trajectory planning problem, which turn to be an MINLP, and decouple it into multiple subproblems to resolve the nonconvexity. A protect distance constraint between any two DBSs at every time slots is considered in the problem formulation to suppress the physical collision and mutual interference of DBSs. Instead of modifying the 3D trajectories, we ensure the protect distance constraint by scheduling the start slot of each trajectory to avoid introducing nonconvex constraints in trajectoryrelated subproblems.

A BCD based algorithm is proposed to separately optimize AoI association, D2U communication scheduling, horizontal trajectories and flying heights of DBSs in different subproblems, respectively. Besides, a kmeansbased scheme is devised to generate the DBS initial trajectories for further improvements on performance.

We conduct extensive simulations and results demonstrate that the proposed 3D trajectory planning and scheduling algorithm can reduce the average D2U pathloss by , and lower the D2U pathloss standard deviation by
, in comparison with the static DBS deployment algorithm based on particle swarm optimization (PSO).
The remainder of this paper is organized as follows. The literature review is conducted in Section II. In Section III the system model for DBS trajectory planning and scheduling in DARAN is introduced. Then the multiDBS 3D trajectory planning and scheduling problem is formulated in Section IV. In Section V the MINLP problem in Section IV is decoupled into subproblems and the BCD based algorithm is proposed to solve it. Simulation and numerical results are carried out in Section VI, and the conclusion is given in Section VII.
Ii Related Works
Promoted by the advancements in the flying control and communication technologies, both industry and academia are devoting many efforts to exploit the full potential of DARAN [4]. As the foundation for drone communication and DARAN research, AlHourani et al. built the D2U pathloss model for DBS according to abundant field test data in various scenarios [18]. A closeform expression of D2U pathloss model suiting different scenarios is proposed in which the probabilities of both LoS and NLoS D2U links are considered. As the extension work, they further formulated the pathloss model for D2B communication in suburban scenario [6] where the D2B links are dominated by LoS links. Leveraging the pathloss model in [18] and [6], various studies have emerged in both static DBS deployment and DBS trajectory planning.
Iia Static DBS Deployment
In most static DBS deployment works, the terrestrial user QoS or network performance is improved through optimizing the hovering position of single or multiple DBSs. For instance, through a clustering based approach, Mozaffari et al. designed the optimal locations of DBSs that maximize the information collection gain from terrestrial IoT devices [19]. In [20], Zhang et al. optimized the DBS density in DBS network to maximize the network throughput while satisfying the efficiency requirements of the cellular network. Zhou et al. studied the downlink coverage features of DBS using Nakagamim fading models, and calculated the optimal height and density of multiple DBSs to achieve maximal coverage probability [21]. Although various works have investigated the static DBS deployments in different scenarios with different methods, the D2B link quality constraint is simplified or ignored by most works. In the works considering the D2B links, the D2B channel models are either as same as the D2U pathloss model [22] or traditional terrestrial channel models [23]. In this paper, we further implement the specific D2B channel model derived in [6] to highlight the D2B channel features.
IiB DBS Trajectory Planning
In [24], Li et al. proposed an cooperative relaying scheme in which multiple DBSs relay data from terrestrial sensors to the BS using time division multiple access (TDMA). As a pioneer work, the trajectories of all DBSs are assumed to be preoptimized for simplicity. Mozaffari et al studied both the static and mobile DBSenabled wireless networks underlaid with a devicetodevice communication network [25]. Though the trajectory optimization is considered in this work, the D2U communications are only permitted at predefined stop points, which fails to exploit the impact of DBS mobility feature on the network performance. Motivated by [25], Zeng et al. proposed a general framework for joint trajectory and communication optimization in D2U pointtopoint communication scenario [26]. For DBSenabled multiuser networks, Lyu et al. proposed a cyclical multiple access scheme in [27], where the DBS forms a cyclical trajectory and periodically serves each terrestrial users using TDMA. Wu et al. formulated the DBS trajectory planning as a mixed integer nonconvex optimization problem in which the user association, DBSs’ trajectories planning and DBS transmitting power control schemes are jointly optimized [16]. Considering the delay constraints, Wu et al. further studied a DBSenabled OFDMA network where a single DBS is dispatched to serve a group of delaysensitive users on the ground [17]. The DBS trajectory planning and OFDMA resource allocation are jointly optimized through an iterative parameterassisted BCD method. As the pioneer works of trajectory planning, [16] [17] set the foundation models for DBS trajectory planning. To dynamically deploy multiple DBSs while maintaining the connectivity among them, Zhao et al. proposed both the centralized and distributed DBS motion control algorithms for scenarios with or without global information of users [28]. However, in those works the flying height of all DBS are treated as a predefined constant, and most of them idealize the D2B link quality constraints. In this paper, not only the D2B link quality constraint is introduced in problem formulation and optimization, but also the flying heights of each DBS at every slots are jointly optimized with the horizontal trajectory.
Iii System Model
In this section, we introduce the DARAN scenario, D2U and D2B channel models, as well as the DBS trajectory model used for further analyses and problem formulation.
Iiia Drone Assisted Radio Access Networks
Fig. 1 shows the system model and the DBS photograph for the multiDBS 3D trajectory planning and scheduling. The DBS is supported by the quadcopter or multirotor drones, which is regarded as low altitude platform (LAP) with the low flying height (below 300m) [14], limited communication coverage (less than 3km) [14] and static hovering capability. Based on the DARAN architecture, we investigate the scenario in which multiple DBSs are controlled by a single BS to support users in AoI through the stateoftheart wireless relay techniques [30] [31]. The radio coverage area of the BS is a circle with radius , and is divided into a mesh consisting of multiple grids on XY plane. The sidelength of each grid is denoted as . Without loss of generality, the average D2U pathloss for any users in one grid can be treated as equal since is far smaller than
. Assuming that users are uniformly distributed over
, and each grid can be chosen as AoI with same probability. Therefore, the user association is equal to AoI association in this work. Both users in AoIs and DBSs are considered as identical devices with identical transmit power and uplink/downlink bandwidth. Considering the fact that AoIs change their distribution in a relatively low frequency, the dynamic distribution of AoIs can be treated as a quasistatic scenario between successive trajectory planning. Based on the current snapshot of AoIs distribution, the BS running trajectory planning and scheduling algorithm to calculate optimal trajectories for all DBSs, and update them to the DBSs via D2B links. When the BS senses significant changes of AoIs distribution, replanning process is triggered to design new trajectories for DBSs, otherwise, the trajectory planning result keeps constant. The set of AoIs to be served and the set of DBSs to be deployed are denoted as and , respectively. Their cardinalities, and , represent the number of AoIs and DBSs, respectively.IiiB D2U and D2B Channel Models
Based on the stateoftheart DronetoGround (D2G) channel research [18] [6], both the D2U and D2B links are modeled in our work, respectively. For D2U links, the LoS probability is calculated as [18]
(1) 
where is the horizontal distance between DBS and the AoI, represents the flying heights of the DBS. and are environmentbased constant values. The average D2U pathloss can be derived based on (1) [18]:
(2)  
where (Hz) and (m/s) are carrier frequency and speed of light, respectively. and are additional losses for LoS and NLoS links obtained through field test data, which involves the impacts of shadowing components. , , and are all environmentbased parameters.
D2B links are designed to provide highreliability data transmission between DBSs and their corresponding BS. The average D2B pathloss is calculated as follow by implementing the D2B channel model in [6]:
(3) 
where and denote the horizontal distance and the vertical angle between the DBS and the BS antenna, respectively. , , , , and are the terrestrial pathloss exponent, excess pathloss scalar, angle offset, angle scalar, and excess pathloss offset, respectively. All of them are environmentbased parameters and involving impacts of shadowing components. Except and , all other parameters in (3) are environmentbased constants. Since the D2B channel model in [6] use LTE bands, (3) contains no parameter representing carrier frequency.
Both the D2U [18] and D2B [6] pathloss models are largescale pathloss models. For the small scale fading and multipath effects, currently there is no specific model for the dronetoground communication links. Moreover, since the objective of our multiDBS trajectory planning is to minimize the mean D2U pathloss of the system, the smallscale pathloss can be average out at zero or a constant offset during the analysis. Therefore, based on the assumptions in D2U and D2B channel models, in this work we do not focus on the small scale fading and multipath effects in D2U and D2B links.
IiiC DBS Trajectory Model
For an arbitrary DBS , we design its trajectory such that the DBS serves the associated AoI set periodically. Within one period , flies over all its associated AoI and serves them sequentially according to the scheduling result. Since the continuous time can introduce infinite number of position variables to describe the DBS trajectory, we discrete the period into equaltime slots to simplify the formulation. The length of each slot can be set as small as possible to approximate the continuous optimal trajectory. Based on this model, the trajectory of DBS within each can be modeled as a
length sequence composed by threedimensional vectors:
(4) 
where , and denote the 3D coordinates of DBS at slot . DBS is considered to follow the same trajectory over consecutive periods until the replanning process is triggered. For multiple DBSs working simultaneously, they share the same trajectory period length to simplify the trajectory planning and scheduling.
Several trajectory constraints are considered in our work: 1) Each DBS needs to return to its initial location by the end of each period , which implies that the trajectory of each DBS is a closed curve in 3D space. 2) Within any slot , the horizontal and vertical shifts of any DBS cannot exceed the maximal horizontal distance , and the maximal height difference , respectively. and are maximum allowed horizontal and vertical speeds. 3) For any slot , the 3D distance between any two DBSs cannot be smaller than a predefined protect distance , which prevents the physical collision, disturbance and mutual interference among DBSs. Since calculating interference from nonassociated DBSs to any AoI based on D2U pathloss model is highly complex and makes the trajectory planning problem unsolvable, in this work, we assume that the mutual interference (to AoIs) among DBSs can be effectively avoided by ensuring the protect distance constraint.
IiiD AoI Association and D2U Communication Scheduling
In this work, the DBSAoI association is denoted by the binary variable
. when AoI is associated to DBS , and otherwise . The U2D communication scheduling is denoted by the binary variable for . If AoI is severed by DBS in slot , is set as ; otherwise, . For each DBS with predefined trajectory planning and AoI association results, a D2U communication scheduling scheme is designed to allocate each slot to the corresponding AoI, and guarantee the fairness among all associated AoIs. Several constraints are considered in the AoI association and scheduling model: 1) One DBS can serve maximal number of AoIs. 2) In any slot , one DBS can serve at most one AoI ; in all slots, one AoI can only be associated to one DBS. 3) For any given and , the total slots are uniformly scheduled to each to ensure fairness. 4) The slot amount scheduled to every AoIs cannot be smaller than a predefined threshold , which indicates the minimal user service time constraint. 5) To prevent the overloads and delay caused by frequent switching between associated AoIs, all slots scheduled to one within have to be consecutive.Iv Problem Formulation
In this section we formulate the multiDBS 3D trajectory planning problem based on the aforementioned system model.
According to (4), the the 3D distance from the DBS to AoI in time slot can be expressed as
(5)  
where is the 3D coordinate of AoI . is ’s 2D projection on XY plane . denotes the horizontal distance between DBS and AoI . Without loss of generality, we set the BS at the original point of coordinate system. By substituting for the D2U and D2B distances in (2) and (3), we can calculate the D2U pathloss between DBS and AoI in slot
(6)  
as well as the D2B pathloss between the BS and DBS in slot
(7)  
where in degree.
Since all users and DBSs are identical devices with fixed transmission power and transmission bandwidth in each period, the achievable D2U data rate between DBS and AoI is negative correlated with the D2U pathloss. Therefore, the aim of the multiDBS 3D trajectory planning and scheduling problem is minimizing the average D2U pathloss of the network over one period .
Define , and , the trajectory planning and scheduling problem can be formulated as
(8)  
(8a)  
(8b)  
(8c)  
(8d)  
(8e)  
(8f)  
(8g)  
(8h)  
(8i)  
(8j)  
(8k)  
(8l)  
(8m) 
In (8), is the number of AoIs associated to DBS . represents the 3D distance between DBS and at slot . is the modulo operation between and . is the pathloss threshold for D2B communication. (8a)(8h) are AoI association and D2U communication scheduling constraints, in which (8a) is constraint 1); (8b)(8d) represent the constraint 2); (8e) and (8f) corresponds to constraint 3) and 4), respectively; (8g) indicates constraint 5). (8i)(8l) correspond to DBS trajectory constraints 1), 2) and 3). (8m) is the D2B pathloss constraint.
V MultiDBS 3D Trajectory Planning and Scheduling Algorithm
Although the objective and constraints in problem (8) are nonconvex or nonlinear for the decision variables, the problem can still be transformed into solvable forms (e.g. quasiconvex or ILP) by setting parts of the decision variables as constants. Then, the MINLP problem can be decoupled into multiple subproblems which are solvable for parts of the decision variables. Specifically, for the multiDBS 3D trajectory planning and scheduling problem, we divide the decision variable set into four blocks (i.e. , , and ), and propose multiple subproblems in which all blocks or their subblocks are optimized, respectively. However, the problem (8) remains nonconvex to DBS trajectory variable even with given and . Therefore, we further divide into two independent blocks, i.e. the horizontal DBS trajectory and the DBS flying height .
Va AoI Association Optimization
Given the constant , and , which indicate the predefined trajectories of multiple DBSs, the AoI association subproblem can be written as an ILP problem:
(9)  
Since exact can only be determined with given , an initial D2U communication scheduling , in which , is defined for the first AoI association optimization. The branch and bound method supported by various solvers (e.g. Gurobi [33]) can be used to solve problem (9) efficiently.
VB D2U Communication Scheduling Optimization
Based on the optimized , as well as the constant and , the D2U communication scheduling subproblem is an ILP problem too:
(10)  
It is worth noting that constraint (8e) and (8g) turn to be linear constraint to given constant . Same as problem (9), problem (10) can be efficiently solved by the branch and bound method.
VC DBS Horizontal Trajectory Optimization
The subproblem to optimize with constant , and can be expressed as
(11)  
According to (6), (11) is nonconvex for . Instead of jointly optimizing , we further divide the block into its element variable and revise (11) as
(12)  
Keeping other fixed, the second part of (12) turns to be constant. With the given , we can prove that is a quasiconvex and nondecreasing function to D2U horizontal distance . Therefore, minimizing the objective function in (12) equals minimizing , which is a quadratic convex optimization problem for :
(13)  
It is worth noting that the feasible region of constrained by (8m) can form a convex set in any XY plane by ignoring the workingzone burst close to the BS antenna [34].
VD DBS Flying Height Optimization
Similar to problem (11), the subproblem optimizing is also nonconvex with given , and . Further decoupling into , the subproblem to optimize each is
(14)  
To solve (14), we first transform (6) as the summation of one function of and one function of :
(15) 
where
(16)  
Since is predefined with given , (15) is constant and optimizing equals optimizing in (14) by substituting for corresponding . Fig. 2 shows the curves of versus under different . We can prove that the (15) is quasiconvex to and has only one global minimum. The detail proof can be found in Appendix 25.
To obtain the optimal at which reaches the global minimum, we let the firstorder derivation of to equals zero:
(17)  
(17) is a transcendental equation without closedform solution. However, considering the fact that (15) has only one global minimum which is the single solution for (17), we can further calculate the secondorder derivation of to :
(18)  
Then, the can be calculated through the NewtonRaphson method:
(19) 
where the iteration stops when and . The calculation of is constrained by where and are upper and lower bounds of due to D2B link quality constraint. After obtaining for each , the optimal can be calculated as
(20) 
VE Protect Distance Constraint
Given the assumption that all trajectories are closed curves in 3D space, the start slot of each trajectory can be any slots on the trajectory. Because all trajectories are assumed to have same length of period , for any trajectory, different start slots can lead to different interDBS distances at all following slots. Since that, it is efficient to schedule the start slot of each DBS to prevent violating protect distance constraint (8l) in following slots. We address protect distance constraint in the start slot scheduling process due to two reasons: First, the feasible set of constraint (8l) is nonconvex for trajectory related variables, i.e., and , optimizing them in horizontal trajectory or height optimization problems can significantly increase the problem complexity. Besides, by ensuring the protect distance constraint through start slot scheduling, the DBS trajectory planning result can be maintained, which achieves better average D2U pathloss than modifying those optimized trajectories. Since the start slot scheduling is not an optimization problem, we can accept any start slots set as long as it ensures constraint (8l). In this work, we apply a greedybased searching algorithm, as shown in Algorithm 1, to iteratively schedule the start slots of all DBSs . In each iteration, sequentially sets its start slot as and calculate the 3D distances between and previous scheduled at every slots.
If any start slot ensures protect distance constraint at every slots, the start slot of is temporally scheduled to and break to the iteration. If all on ’s trajectory cannot ensure protect distance constraint, the algorithm abandons the current and all previous scheduled DBSs and rerun the first iteration of with updated start slot . Algorithm 1 stops until all are scheduled with feasible start slots.
VF Proposed Algorithm
By decoupling the decision variable set into multiple blocks, i.e., , , , , each block’s subproblem can be optimized respectively with other blocks keeping constant. Therefore, the problem (8) can be solved through iteratively optimizing those subproblems until the results converge, which yields to the classic BCD method. Based on the BCD method, we propose the algorithm to solve the multiDBS 3D trajectory planning and scheduling problem, which shows in Algorithm 2. , , denote the AoI association, D2U communication scheduling and DBS trajectories after each iteration , respectively. is composed by and . According to the BCD method, the proposed algorithm ensures convergence since the global optimal results of all subproblem are accurately achieved [16] [35].
Initial trajectories are required for the first iteration of AoI association. Without loss of generality, we set the same initial height for all DBS. For each DBS, we apply a circle initial trajectory with radius . Given the assumption in subsection A that the initial D2U communication scheduling equals one for , it is better to deploy the center of each circle trajectory to the position where the summation of D2U pathloss between its adjacent AoIs (will be associated to the DBS with high probability) is minimized. Therefore, the classic kmeans algorithm can be effectively applied to determine the initial trajectory center of each DBS by substituting D2U pathloss for the geometric distance in original algorithm. To reduce the convergence time and improve the result quality, we apply the kmeans ++ algorithm which prefers centroid seeds with large mutual distances [36].
Vi Numerical Results
We conduct extensive simulations to verify the performance of our proposed algorithm in minimizing average D2U pathloss of the network. The simulations are link level without simulating specific MAC or upper layers protocols. The BS is located at the origin point (coordinate ) and the sidelength of grid is set to . Both U2D and D2B pathloss models are configured in suburban scenario. To provide additional spectrum resources for DARAN and reduce the interference to terrestrial RAN users, the frequency band of D2U communication is expected to be different from the licensed cellular band. Like most commercial drone products [37] [38] and DBS related works [39] [7] [19] [28], we use the unlicensed band as the carrier for D2U communications. D2B communications use the LTE band according to the D2B pathloss model [6]. By allocating different carrier frequencies, the interference between D2U and D2B communication can be prevented. Initial height is set to within the workingzone of DBS over the whole BS radio coverage area [34]. We treat as the minimal time unit to calculate related variables including , , etc. There is no need to assign specific value for in the simulation, however, according to the general specifications of commercial drones ( for horizontal speed, for ascent/descent speed) [40], the approximate value of is around . Table. I shows detail simulation parameters.
Parameters  Numerical Values 

BS radio coverage radius  
AoI number  
D2U parameters  (0.1,21,4.88,0.43) 
D2B parameters  (3.04,23.29,3.61,4.14,20.7) 
Carrier frequencies (D2U, D2B)  
Slots amount in one period  
D2B pathloss constraint  
Minimal perAoI slot number  
Maximal perDBS AoI number  
Maximal horizontal speed  
Maximal vertical speed  
Protect Distance  
Trajectory difference  for each slot 
Via 3D Trajectory Planning for Multiple DBSs
Fig. 3 shows the scenario where the trajectories of five DBSs are optimized to serve twenty AoIs with . The closed curves dotted by different markers in Fig. 3(a) and Fig. 3(b) denote different DBS trajectories; the squares on the XY plane represent AoIs. AoIs are associated to corresponding DBSs with same colors. Fig. 3(c) illustrates the changes of flying height within one period. As shown in Fig. 3(a) and 3(b), for each DBS, the optimized trajectory can fly over all its associated AoIs and form a closed curve in 3D space. In Fig. 3(c), all DBS flying height curves are lower bounded around , which is the lower bound of due to the D2B pathloss constraint.
Note that for each trajectory in Fig. 3(b), the summation of dots on the section between two AoIs is less than of the total slots number . Besides, the height curves in Fig. 3(c) show the trend to maintain fixed values for consecutive slots. Combining Figs. 3(b) and 3(c), we can justify that the remaining dots in Fig. 3(b) are overlapped above the associated AoIs, and those overlapped dots corresponds to the consecutive slots have fixed heights in Fig. 3(c). In other word, the proposed algorithm prefers hovering DBSs above the associated AoIs, while leave minimal slots for the travelling process between adjacent hovering positions. Such a “hovering effect” can be explained as follows. For any slot , the proposed algorithm is prone to small which minimizes the D2U pathloss with given . On the contrary, the smaller the is, the higher the probability that . Based on (20), if , the optimal height equals the lower bound of flying height at current position. Since the minimal equals zero, the minimal average D2U pathloss can be achieved by the trajectory with most slots hovering above the AoIs. From Fig. 3(c), we can see that several height bursts occur when each DBS is flying between two AoI with a long interAoI distance. At those slots, the DBS is relatively far from the scheduled AoI and can fall in the feasible height range between and constrained by D2B pathloss threshold. Therefore, the optimal heights prefer to approach the value of in those slots, which leads to the height bursts. Fig. 3
(d) shows the cumulative distribution function (CDF) of interDBS distance within one period
. The red dotted line is the protect distance constraint. It can be seen that all interDBS distances of the final trajectory planning result are larger than the protect distance threshold , which indicates the effectiveness of the start slots scheduling algorithm to ensure protect distance constraint.Fig. 4 presents two groups of trajectory planning results with and , respectively. The available DBS number equals four for both groups. As shown in Fig. 4, the AoI associations are same under different . The trajectories in Fig. 4(a) cannot fly over every associated AoI since the maximal horizontal speed is too small to ensure the DBSs to approach every associated AoIs within one period. In Fig. 4(c) where is high enough, the DBSs can even hovering on each associated AoI for few slots since the flying interval between two hovering positions requires less slots. Comparing Fig. 4(b) and 4(d), we can see that the variation of flying height with is larger than the height variation with . Because in low scenario, the travelling process between two AoIs requires more slots than that in the high scenario, the optimal height in small has higher probability to fall into the feasible flying height range. Considering the four DBSs trajectory planning scenario, the CDF of D2U pathloss under different are compared in Fig. 6. Given any pathloss threshold, We can see that the probability of D2U pathloss less than the threshold raises as the increases.
Fig. 5 compares the trajectory planning results when and . The horizontal speed is set as for both scenarios. As the number of available DBS increases, the average number of AoI associated to one DBS is reduced, some trajectories can even degenerate to one static deployment position when the corresponding DBS is associated with only one AoI. On the other hand, since the average length is also reduced with the decreasing of associated AoI number for each DBS, the variation of flying height can be reduced with the increasing of . Fig. 7 shows the CDF of D2U pathloss under different . Similar to Fig. 6, the probability of D2U pathloss less than any given threshold increases as more numbers of DBS are provided.
Fig. 6 and Fig. 7 indicate that the D2U pathloss performance can be influenced by both and . In Fig. 8, we further investigate the average pathloss performance with different and . From preceding analyses, we know that both the higher and larger can lead to smaller average , which eventually reduces the average pathloss level. According to Fig. 8, given the same number of DBS, the average pathloss level decreases slightly as the increases; while significant average pathloss level reduction occurs as the increases under fixed maximal horizontal speed. Therefore, we can conclude that both raising the horizontal speed and increasing the number of available DBS can promote the average D2U pathloss performance of DBS trajectory planning, while increasing the number of available DBSs is proved to be more efficient than raising horizontal flying speed. Note that this conclusion is valid for the average D2U pathloss performance of the whole network only. Since the standard deviations of pathloss (errorbars) plotted in Fig. 8 are highly overlapped with each other, the D2U pathloss performance of specific DBStoAoI pair can vary a lot. Nevertheless, as the horizontal speed and available DBS number increase, the standard deviation is reduced, which indicates that the user fairness can also be promoted by raising and .
We further analyze the impacts of different initial trajectories (ITs) to the achieved average D2U pathloss performance. We compare four types of ITs, i.e., 1) circle IT with the center location determined by kmeans ++; 2) point IT (where the trajectory shrinks to one hovering point) with the point location determined by kmeans ++; 3) circle IT with the center location uniformly distributed over ; 4) point IT with the point location uniformly distributed over . Fig. 9 shows the comparison result. We can see that the kmeansbased circle IT used in the proposed algorithm achieves minimal average D2U pathloss and pathloss standard deviation. Comparing the performance gaps between ITs, we note that applying kmeans ++ algorithm has more significant impact to both average D2U pathloss and pathloss standard deviation than using circleshaped IT.
ViB Performance Comparison
To highlights the efficiency of the proposed multiDBS 3D trajectory planning and scheduling, we compare the average D2U pathloss performance achieved by our proposed trajectory planning algorithm, as well as the static DBS deployment scheme in Fig. 10 and Table II. For static DBS deployment algorithm, we use the perdrone iterated particle swarm optimization (DIPSO) algorithm proposed in [34]. Without loss of generality, we use all data achieved by to calculate the average D2U pathloss of the proposed trajectory planning algorithm. From Fig. 10, we can see that the average D2U pathloss of both algorithms are reduced as the available DC number increases. However, the D2U pathloss performance achieved by our trajectory planning algorithm maintains smaller than that achieved by the DIPSO algorithm.
The user fairness promotion provided by the proposed trajectory planning algorithm is indicated by the errorbars in Fig. 10 and the D2U pathloss standard deviation comparison in Table II. and are D2U pathloss standard deviations for DBS trajectory planning and static DBS deployment, respectively. In Fig. 10, we can see that the standard deviation of D2U pathloss achieved by both algorithms are reduced as the available DBS number increases. While the maintains less than half of the , there is no overlap between the errorbars achieved by two algorithms. From Table II, we can calculate that the DBS trajectory planning can lower the D2U pathloss standard deviation by on average compared with the static DBS deployment.
To highlight the costefficiency of the trajectory planning algorithm, and provide a guideline to determine the number of required DBS, we compare the minimal required DBS number under different D2U pathloss thresholds in Table III. The D2U pathloss threshold is a strict constraint, which means that for any DBS at any slot, the D2U pathloss to any AoI cannot exceed it. As shown in Table III, under the same D2U pathloss threshold, the minimal required DBS amount is decreased as the maximal horizontal speed of DBS increases. Besides, given any threshold levels, the static DBS deployment always requires two to four more DBSs than the DBS trajectory planning algorithm, which implies that the DBS trajectory planning algorithm is more economical than the static DBS deployment.
DBS number  

D2U pathloss threshold ()  
Comments
There are no comments yet.