<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Publishing DTD v1.0 20120330//EN" "JATS-journalpublishing1.dtd">
<article xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xlink="http://www.w3.org/1999/xlink" article-type="research-article">
<front>
<journal-meta>
<journal-id journal-id-type="publisher-id">INFORMATICA</journal-id>
<journal-title-group><journal-title>Informatica</journal-title></journal-title-group>
<issn pub-type="epub">1822-8844</issn><issn pub-type="ppub">0868-4952</issn><issn-l>0868-4952</issn-l>
<publisher>
<publisher-name>Vilnius University</publisher-name>
</publisher>
</journal-meta>
<article-meta>
<article-id pub-id-type="publisher-id">INFOR585</article-id>
<article-id pub-id-type="doi">10.15388/25-INFOR585</article-id>
<article-categories><subj-group subj-group-type="heading">
<subject>Research Article</subject></subj-group></article-categories>
<title-group>
<article-title>A Traffic Trajectory Recommendation Scheme Based on Edge-Cloud Computing Driver-Car-Road Preferences</article-title>
</title-group>
<contrib-group>
<contrib contrib-type="author">
<name><surname>Yu</surname><given-names>Jing</given-names></name><email xlink:href="yujingellemma@gmail.com">yujingellemma@gmail.com</email><xref ref-type="aff" rid="j_infor585_aff_001">1</xref><bio>
<p><bold>J. Yu</bold> received the MSc degree from Huazhong University of Science and Technology in 2012 and the PhD degree from Wonkwang University in 2021. She is currently an associate professor in School of Management, Jiujiang University, China. Her research interests include tensor algebra, privacy-preserving, personalized recommendation, information management, etc.</p></bio>
</contrib>
<contrib contrib-type="author">
<name><surname>Huang</surname><given-names>Jinzhou</given-names></name><email xlink:href="huangjinzhou@hbuas.edu.cn">huangjinzhou@hbuas.edu.cn</email><xref ref-type="aff" rid="j_infor585_aff_002">2</xref><xref ref-type="corresp" rid="cor1">∗</xref><bio>
<p><bold>J. Huang</bold> received the PhD degree in computer system architecture from Huazhong University of Science and Technology (HUST), in 2015. He is currently an associate professor in the School of Computer Engineering, Hubei University of Arts and Science, China. His research interests include online social networking, intelligent transportation, internet of things, computer networking and information security.</p></bio>
</contrib>
<contrib contrib-type="author">
<name><surname>Chi</surname><given-names>Lianhua</given-names></name><email xlink:href="L.chi@latrobe.edu.au">L.chi@latrobe.edu.au</email><xref ref-type="aff" rid="j_infor585_aff_003">3</xref><bio>
<p><bold>L. Chi</bold> received the dual PhD degrees in computer science from the University of Technology Sydney, Australia, and the Huazhong University of Science and Technology, Wuhan, China, in 2015. She was a Post-Doctoral Research Scientist in IBM Research Melbourne. Dr. Chi was a recipient of the Best Paper Award in PAKDD in 2013. Currently, she is a lecturer with the Department of Computer Science and Information Technology at La Trobe University since 2018. Her current research interests include data mining, machine learning and big data hashing.</p></bio>
</contrib>
<contrib contrib-type="author">
<name><surname>Wei</surname><given-names>Wei</given-names></name><email xlink:href="weiwei@xaut.edu.cn">weiwei@xaut.edu.cn</email><xref ref-type="aff" rid="j_infor585_aff_004">4</xref><xref ref-type="aff" rid="j_infor585_aff_005">5</xref><bio>
<p><bold>W. Wei</bold> received his MS and PhD degrees from Xi’an Jiaotong University in 2005 and 2010, respectively. He is currently a professor with School of Computer Science and Engineering, Xi’an University of Technology. His research interests include wireless networks, internet of things, image processing, mobile computing, distributed computing, pervasive computing, and tensor computing.</p></bio>
</contrib>
<contrib contrib-type="author">
<name><surname>Cui</surname><given-names>Zongmin</given-names></name><email xlink:href="cuizm01@gmail.com">cuizm01@gmail.com</email><xref ref-type="aff" rid="j_infor585_aff_006">6</xref><bio>
<p><bold>Z. Cui</bold> received the BE degree from Southeast University in 2002. He received the ME degree and PhD degree from Huazhong University of Science and Technology in 2006 and 2014 respectively. He is currently a professor at Jiujiang University. His research interests include tensor computing, privacy-preserving, and data analysis.</p></bio>
</contrib>
<aff id="j_infor585_aff_001"><label>1</label>School of Management, <institution>Jiujiang University</institution>, Jiujiang, Jiangxi 332005, <country>China</country></aff>
<aff id="j_infor585_aff_002"><label>2</label>School of Computer Engineering, <institution>Hubei University of Arts and Science</institution>, Xiangyang, Hubei 441053, <country>China</country></aff>
<aff id="j_infor585_aff_003"><label>3</label>Department of Computer Science and Information Technology, <institution>La Trobe University</institution>, Melbourne, Victoria 3086, <country>Australia</country></aff>
<aff id="j_infor585_aff_004"><label>4</label>School of Computer Science and Engineering, <institution>Xi’an University of Technology</institution>, Xi’an, Shaanxi 710048, <country>China</country></aff>
<aff id="j_infor585_aff_005"><label>5</label>Chongqing Key Laboratory of Computational Intelligence, <institution>Chongqing University of Posts and Telecommunications</institution>, Chongqing, 400065, <country>China</country></aff>
<aff id="j_infor585_aff_006"><label>6</label>School of Computer and Big Data Science, <institution>Jiujiang University</institution>, Jiujiang, Jiangxi 332005, <country>China</country></aff>
</contrib-group>
<author-notes>
<corresp id="cor1"><label>∗</label>Corresponding author.</corresp>
</author-notes>
<pub-date pub-type="ppub"><year>2025</year></pub-date><pub-date pub-type="epub"><day>19</day><month>2</month><year>2025</year></pub-date><volume>36</volume><issue>1</issue><fpage>223</fpage><lpage>240</lpage><history><date date-type="received"><month>6</month><year>2024</year></date><date date-type="accepted"><month>1</month><year>2025</year></date></history>
<permissions><copyright-statement>© 2025 Vilnius University</copyright-statement><copyright-year>2025</copyright-year>
<license license-type="open-access" xlink:href="http://creativecommons.org/licenses/by/4.0/">
<license-p>Open access article under the <ext-link ext-link-type="uri" xlink:href="http://creativecommons.org/licenses/by/4.0/">CC BY</ext-link> license.</license-p></license></permissions>
<abstract>
<p>Most existing traffic trajectory recommendation methods don’t consider the driver-car-road preferences, resulting in the poor ability to meet the driver-car-road requirements. To address this issue, we propose a traffic Trajectory Recommendation scheme based on Edge-cloud computing Driver-car-road Preferences (named as TREDP). TREDP reduces the computational, storage, and energy burden on the edge through edge-cloud collaborative computing. TREDP enhances the recommended accuracy by considering driver-car-road requirements and the relationship among driver-car-road in different traffic trajectories. Meanwhile, TREDP increases the computational efficiency through edge-cloud computing. Thus, it improves the driver experience of intelligent traffic trajectory recommendation systems.</p>
</abstract>
<kwd-group>
<label>Key words</label>
<kwd>traffic trajectory</kwd>
<kwd>trajectory recommendation</kwd>
<kwd>driver-car-road preference</kwd>
<kwd>personalized recommendation</kwd>
<kwd>edge-cloud computing</kwd>
</kwd-group>
<funding-group><funding-statement>This work was supported in part by the National Nature Science Foundation of China (No. 62362042); in part by the Hubei Natural Science Foundation Innovation and Development Joint Fund Project (Nos. 2022CFD101 and 2022CFD103); in part by the Xiangyang High-tech Key Science and Technology Plan Project (No. 2022ABH006848); in part by the Hubei Superior and Distinctive Discipline Group of “New Energy Vehicle and Smart Transportation”; in part by the Jiangxi Provincial Natural Science Foundation of China (No. 20224BAB202012); in part by the Jiangxi Provincial Social Science Foundation of China (No. 23GL52D); in part by the Scientific and Technological Research Project of Jiangxi Provincial Education Department of China (No. GJJ2401835); and in part by the Open Fund for Chongqing Key Laboratory of Computational Intelligence (No. 2020FF02).</funding-statement></funding-group>
</article-meta>
</front>
<body>
<sec id="j_infor585_s_001">
<label>1</label>
<title>Introduction</title>
<p>The purpose of personalized recommendation is to recommend information and products that users are interested in according to their interests and purchasing behaviours (Guo <italic>et al.</italic>, <xref ref-type="bibr" rid="j_infor585_ref_006">2024</xref>; Kurnianto and Sfenrianto, <xref ref-type="bibr" rid="j_infor585_ref_012">2024</xref>; bin Zulkiflee <italic>et al.</italic>, <xref ref-type="bibr" rid="j_infor585_ref_001">2024</xref>). Traffic trajectory recommendation is an important part of intelligent transportation (Li <italic>et al.</italic>, <xref ref-type="bibr" rid="j_infor585_ref_015">2023</xref>). It can be applied in many scenarios, including automatic driving (Cao <italic>et al.</italic>, <xref ref-type="bibr" rid="j_infor585_ref_002">2024</xref>), multi-task trajectory (Lei <italic>et al.</italic>, <xref ref-type="bibr" rid="j_infor585_ref_014">2025</xref>), automated parking (Dudakli and Baykasoğlu, <xref ref-type="bibr" rid="j_infor585_ref_005">2024</xref>), path planning (Jian <italic>et al.</italic>, <xref ref-type="bibr" rid="j_infor585_ref_008">2024</xref>), travel trajectory (Deng <italic>et al.</italic>, <xref ref-type="bibr" rid="j_infor585_ref_004">2025</xref>), etc. The high-quality traffic trajectory recommendation system can provide drivers with fast, safe and personalized travel, which indirectly affects the urban environment (Kalaivani Jayaraman and Malarvizhi, <xref ref-type="bibr" rid="j_infor585_ref_011">2024</xref>) and economic development (Jin and Choi, <xref ref-type="bibr" rid="j_infor585_ref_010">2024</xref>) in smart cities. Therefore, more and more researchers pay attention to the research of traffic trajectory recommendation.</p>
<p>At present, the main content of traffic trajectory recommendation research includes how to save energy, reduce driving time (Xing and Hao, <xref ref-type="bibr" rid="j_infor585_ref_026">2022</xref>), enhance safety, and even improve the profitability of commercial cars (Liu <italic>et al.</italic>, <xref ref-type="bibr" rid="j_infor585_ref_019">2024</xref>). The traffic trajectory recommendation model may be divided into three categories: traffic trajectory recommendation model for connected automated vehicles (Yang <italic>et al.</italic>, <xref ref-type="bibr" rid="j_infor585_ref_027">2021</xref>; Yao <italic>et al.</italic>, <xref ref-type="bibr" rid="j_infor585_ref_028">2024</xref>; Cheng <italic>et al.</italic>, <xref ref-type="bibr" rid="j_infor585_ref_003">2023</xref>; Zhang <italic>et al.</italic>, <xref ref-type="bibr" rid="j_infor585_ref_030">2023</xref>; Zhao <italic>et al.</italic>, <xref ref-type="bibr" rid="j_infor585_ref_031">2023</xref>; Jiang <italic>et al.</italic>, <xref ref-type="bibr" rid="j_infor585_ref_009">2024</xref>), traffic trajectory recommendation model based on multi-objective optimization (Ning <italic>et al.</italic>, <xref ref-type="bibr" rid="j_infor585_ref_020">2024</xref>; Xiao <italic>et al.</italic>, <xref ref-type="bibr" rid="j_infor585_ref_025">2024</xref>; Nishida <italic>et al.</italic>, <xref ref-type="bibr" rid="j_infor585_ref_021">2024</xref>; Li <italic>et al.</italic>, <xref ref-type="bibr" rid="j_infor585_ref_016">2024</xref>; Peng <italic>et al.</italic>, <xref ref-type="bibr" rid="j_infor585_ref_022">2024</xref>) and traffic trajectory recommendation model based on trajectory similarity (Qu <italic>et al.</italic>, <xref ref-type="bibr" rid="j_infor585_ref_023">2019</xref>; Lim <italic>et al.</italic>, <xref ref-type="bibr" rid="j_infor585_ref_017">2021</xref>; Yu <italic>et al.</italic>, <xref ref-type="bibr" rid="j_infor585_ref_029">2023</xref>; Liu <italic>et al.</italic>, <xref ref-type="bibr" rid="j_infor585_ref_018">2023</xref>; Lai <italic>et al.</italic>, <xref ref-type="bibr" rid="j_infor585_ref_013">2024</xref>). These models are proposed to improve various problems in daily traffic and enhance drivers’ satisfaction with the trajectory recommendation system.</p>
<p>However, the existing models cannot personalize traffic trajectory recommendations based on driver-car-road preferences. In fact, the preferences have a crucial impact on their traffic trajectories. Unexpected real-time factors from driver-car-road may make the driver dissatisfied with the current recommended trajectory. For example, a driver may suddenly feel ill and need to go to the nearest hospital, a sudden air leak on the tire may force the driver to go to the nearest repair shop, a road section may collapse suddenly, etc. However, existing recommendation models do not take these sudden driver-car-road situations into account.</p>
<p>Therefore, this paper proposes a traffic Trajectory Recommendation scheme based on Edge-cloud computing Driver-car-road Preferences (named as TREDP). TREDP improves the problems in a practical application of traffic trajectory recommendation systems by considering driver-car-road requirements and the relationship among driver-car-road in different traffic trajectories. Thus, it improves the driver experience of intelligent traffic trajectory recommendation systems. The calculation of TREDP can be divided into the following three categories. (1) TREDP considers the relationship among driver-car-road based on the traffic trajectory analysis on the cloud. (2) TREDP analyses driver-car-road requirements on the edge. (3) TREDP computes driver-car-road preferences based on edge-cloud collaborative computing. Through the above edge-cloud computing driver-car-road preferences, we could enhance recommended accuracy, reduce computational overhead and save traffic consumption (including fuel consumption, electricity consumption, driving time, etc). Meanwhile, via the edge-cloud collaborative computing, TREDP could achieve the real-time recommendation for providing drivers with better trajectory recommendation services.</p>
<p>Our contributions are summarized as follows.</p>
<list>
<list-item id="j_infor585_li_001">
<label>•</label>
<p>We design an edge-cloud computing traffic trajectory recommendation framework. The framework has two modules to support each other. The two modules provide drivers with timely and continuously updated traffic trajectory recommendation services through iterative analysis.</p>
</list-item>
<list-item id="j_infor585_li_002">
<label>•</label>
<p>We propose a lightweight computing method on the edge to reflect the driver-car-road real-time requirements for enhancing the recommended accuracy.</p>
</list-item>
<list-item id="j_infor585_li_003">
<label>•</label>
<p>We provide a traffic trajectory analytic method on the cloud for analysing the relationship among driver-car-road based on historical trajectory data.</p>
</list-item>
<list-item id="j_infor585_li_004">
<label>•</label>
<p>We construct a traffic trajectory recommendation scheme based on edge-cloud collaborative computing. Extensive experimental results show that our scheme significantly outperforms the existing methods with regard to the recommended accuracy and computational efficiency. The results further verify the validity of our framework.</p>
</list-item>
</list>
<p>The rest of this paper is organized as follows. Section <xref rid="j_infor585_s_002">2</xref> discusses related works. Section <xref rid="j_infor585_s_006">3</xref> designs our framework. Section <xref rid="j_infor585_s_007">4</xref> shows our scheme TREDP. Section <xref rid="j_infor585_s_013">5</xref> provides the experimental analysis and Section <xref rid="j_infor585_s_017">6</xref> concludes this paper.</p>
</sec>
<sec id="j_infor585_s_002">
<label>2</label>
<title>Related Work</title>
<p>The current traffic trajectory recommendation models may be divided into the following three categories.</p>
<sec id="j_infor585_s_003">
<label>2.1</label>
<title>Traffic Trajectory Recommendation Model for Connected Automated Vehicles</title>
<p>For Connected Automated Vehicles (CAVs), the traffic trajectory recommendation model (Wang <italic>et al.</italic>, <xref ref-type="bibr" rid="j_infor585_ref_024">2019</xref>; Jaurker and Pradhan, <xref ref-type="bibr" rid="j_infor585_ref_007">2023</xref>) tries to optimize CAV trajectories, while reducing the total travel time and CAV fuel consumption. Secondly, the model is iteratively optimized in order to use real-time data. The model takes traffic sensor data and CAV trajectory information as input based on a large number of traffic data flows. It aims to minimize the total travel time of the trajectory to obtain the expected velocity profile of CAV. Then, with the goal of reducing fuel consumption, the quadratic optimization is carried out to generate the optimal CAV trajectory conforming to the velocity profile.</p>
<p>Meanwhile, Yang <italic>et al.</italic> (<xref ref-type="bibr" rid="j_infor585_ref_027">2021</xref>) take advantage of advances in CAV technology to design an ecological driving and queuing system that could improve fuel efficiency and operational efficiency of cars on highways. Yao <italic>et al.</italic> (<xref ref-type="bibr" rid="j_infor585_ref_028">2024</xref>) present a full-sample trajectory reconstruction method for the mixed traffic flow of common cars and connected cars. Cheng <italic>et al.</italic> (<xref ref-type="bibr" rid="j_infor585_ref_003">2023</xref>) provide a deep reinforcement learning model for hybrid traffic flow control based on Adam optimization to guide the longitudinal trajectory of CAV on a typical urban road with signal-controlled intersections. Zhang <italic>et al.</italic> (<xref ref-type="bibr" rid="j_infor585_ref_030">2023</xref>) introduce CAVSim, which is a micro-traffic simulator that emphasizes feedforward decision-making, planning components and collaborative decision in the CAV environment. Zhao <italic>et al.</italic> (<xref ref-type="bibr" rid="j_infor585_ref_031">2023</xref>) propose a strategy that allows CAV to remain safe with respect to the car in front and behind. Jiang <italic>et al.</italic> (<xref ref-type="bibr" rid="j_infor585_ref_009">2024</xref>) design an optimal control strategy to coordinate the forced lane change of autonomous cars from the common lane to the special lane. Deng <italic>et al.</italic> (<xref ref-type="bibr" rid="j_infor585_ref_004">2025</xref>) constructs a trajectory reconstruction method that makes full use of CAV debris observation data.</p>
</sec>
<sec id="j_infor585_s_004">
<label>2.2</label>
<title>Traffic Trajectory Recommendation Model Based on Multi-Objective Optimization</title>
<p>Traffic trajectory recommendation model based on multi-objective optimization could generally be divided into two modules. The first module is the function optimization module, which uses a multi-objective optimization function to optimize multiple objectives such as minimizing travel time, improving traffic safety and minimizing fuel consumption. It recommends driver trajectory through the ideal value of each target represented in the optimization function. The second module is the traffic track prediction module. This module realizes the prediction of future traffic state by analysing the recent traffic track condition, and timely feedback to the function optimization module to evaluate the future traffic track driving cost.</p>
<p>Ning <italic>et al.</italic> (<xref ref-type="bibr" rid="j_infor585_ref_020">2024</xref>) present a multi-objective optimization model for autonomous car traffic light intersections based on the near-end strategy optimization algorithm. Xiao <italic>et al.</italic> (<xref ref-type="bibr" rid="j_infor585_ref_025">2024</xref>) propose a sustainable and stable trajectory planning scheme for smart city public transportation based on multi-objective optimization. Nishida <italic>et al.</italic> (<xref ref-type="bibr" rid="j_infor585_ref_021">2024</xref>) design an improved version of Pareto Deep Q-Network (PDQN), which is a multi-objective deep reinforcement learning method for optimizing crowd trajectory guidance strategies, etc. Li <italic>et al.</italic> (<xref ref-type="bibr" rid="j_infor585_ref_016">2024</xref>) provide an improved non-dominated sorting genetic algorithm based on considering the travel intentions of drivers and passengers, which is a multi-objective optimization model with the goal of minimizing the loss of time for drivers and passengers. Peng <italic>et al.</italic> (<xref ref-type="bibr" rid="j_infor585_ref_022">2024</xref>) develop an improved constrained multi-objective evolutionary algorithm based on designing an improved genetic operator and repairing constraint processing technique to enhance the overall performance of the algorithm in seeking the Pareto optimal solution. Zhao <italic>et al.</italic> (<xref ref-type="bibr" rid="j_infor585_ref_032">2025</xref>) construct a multi-objective model for system optimization of dynamic traffic guidance.</p>
</sec>
<sec id="j_infor585_s_005">
<label>2.3</label>
<title>Traffic Trajectory Recommendation Model Based on Trajectory Similarity</title>
<p>The core content of the traffic trajectory recommendation model based on trajectory similarity is how to sketch the driven trajectory, so as to recommend the high satisfaction trajectory to the driver. The model can collect massive traffic trajectory data mainly based on the online filtering sampling method and offline filtering sampling method. The online filtering sampling method is primarily aimed at the traffic trajectory data that can be collected in real-time, and these data often require rapid analysis. The online filtering sampling method mainly adopts intermittent sampling, which requires the acquisition device to record the data once every fixed period of time and record the data in the cache area. When the data in the cache area reaches a certain amount, the data would be calculated to get the average value of the trajectory data in the window.</p>
<p>The difficulty of this model lies in how to measure the driver’s satisfaction with a certain trajectory and how to measure the similarity between different trajectories. Measurement of satisfaction with a certain trajectory includes the measurement of a variety of driver concerns, including time cost, economic cost, convenience of driving and road conditions. It is necessary to find a reasonable measurement method to measure it and take them into comprehensive consideration. Similarity measurement between trajectories is also a difficulty in this model. Trajectory states are different in different time and space, and real-time changes in trajectory states may bring difficulties in algorithm complexity and trajectory complexity.</p>
<p>Qu <italic>et al.</italic> (<xref ref-type="bibr" rid="j_infor585_ref_023">2019</xref>) propose an adaptive shortest-range cruising trajectory method ASER for personalized traffic trajectory recommendation. In ASER, a probabilistic network model is established, which uses Kalman filter method to predict the picking probability and picking capacity of each position. It also considers the load balance between passengers and cars, and introduces the shortest expected cruising distance to calculate the potential cruising distance of cars. In addition, it utilizes MapReduce and KDS-Tree to improve recommendation efficiency. Lim <italic>et al.</italic> (<xref ref-type="bibr" rid="j_infor585_ref_017">2021</xref>) provide a hybrid trajectory planning method that combines the advantages of sampling and optimization. The sampling method of transverse motion is used to deal with different trajectories of various maneuvers. This helps generating response trajectories in dynamically changing environments. Yu <italic>et al.</italic> (<xref ref-type="bibr" rid="j_infor585_ref_029">2023</xref>) design a diverse sensory trajectory publication/subscription framework that performs query trajectory matching between continuous location set queries on the trajectory data stream. Liu <italic>et al.</italic> (<xref ref-type="bibr" rid="j_infor585_ref_018">2023</xref>) develop a spatiotemporal dependency and similarity perception method called dependency and similarity perception temporal graph convolutional network. Lai <italic>et al.</italic> (<xref ref-type="bibr" rid="j_infor585_ref_013">2024</xref>) solve the problem of insufficient labels by effectively using the knowledge from several existing measurement methods as the source measurement method.</p>
<p>All kinds of personalized recommendation models mentioned above do solve some problems encountered in real life. However, as ignoring driver-car-road preferences, the above models are difficult to carry out personalized recommendations flexibly and timely for drivers with different driver-car-road needs. Meanwhile, the lack of edge-cloud computing results in insufficient computing efficiency of these models when used in our framework.</p>
</sec>
</sec>
<sec id="j_infor585_s_006">
<label>3</label>
<title>Framework</title>
<p>Our edge-cloud computing traffic trajectory recommendation framework is shown in Fig. <xref rid="j_infor585_fig_001">1</xref>. The framework has two modules: the edge module and cloud module. The edge module has three submodules: data collection, driver-car-road requirements, and traffic trajectory recommendation. The cloud module also has three submodules: data preprocessing, analytic method, and traffic trajectory analysis.</p>
<fig id="j_infor585_fig_001">
<label>Fig. 1</label>
<caption>
<p>Edge-cloud computing traffic trajectory recommendation framework.</p>
</caption>
<graphic xlink:href="infor585_g001.jpg"/>
</fig>
<p>First, driver-car-road in the driver-car-road requirements submodule generates massive traffic data for the data collection submodule. Meanwhile, the submodule also generates real-time driver-car-road requirements for the traffic trajectory recommendation submodule. Second, the data collection submodule collects the massive traffic data for the data preprocessing submodule based on GPS, car sensors, traffic websites, history trajectories, etc. Third, the traffic data is represented, transformed, cleaned and integrated by the data preprocessing submodule for the analytic method submodule. Fourth, based on suitable analytic methods, the traffic trajectory analysis submodule analyses historical trajectory data to find valuable knowledge such as the relationship among driver-car-road. When the traffic trajectory recommendation submodule receives the feedback analysed results, the submodule combines the edge-cloud analytic results to get the edge-cloud computing driver-car-road preferences. Fifth, the submodule recommends traffic trajectories to drivers based on the driver-car-road preferences. Finally, driver-car-road generates new traffic data based on the recommended results, and the new traffic data can provide the latest services via analysis. Through the above iterations, the framework could continuously improve service quality.</p>
</sec>
<sec id="j_infor585_s_007">
<label>4</label>
<title>TREDP</title>
<p>The main symbols and corresponding explanations used for TREDP are given in Table <xref rid="j_infor585_tab_001">1</xref>.</p>
<table-wrap id="j_infor585_tab_001">
<label>Table 1</label>
<caption>
<p>The main symbols for TREDP.</p>
</caption>
<table>
<thead>
<tr>
<td style="vertical-align: top; text-align: left; border-top: solid thin; border-bottom: solid thin">Symbol</td>
<td style="vertical-align: top; text-align: left; border-top: solid thin; border-bottom: solid thin">Explanation</td>
</tr>
</thead>
<tbody>
<tr>
<td style="vertical-align: top; text-align: left"><italic>D</italic></td>
<td style="vertical-align: top; text-align: left">a set of drivers in the system</td>
</tr>
<tr>
<td style="vertical-align: top; text-align: left"><italic>d</italic></td>
<td style="vertical-align: top; text-align: left">a driver in <italic>D</italic></td>
</tr>
<tr>
<td style="vertical-align: top; text-align: left"><italic>T</italic></td>
<td style="vertical-align: top; text-align: left">a set of historical trajectory data with the same beginning and ending point</td>
</tr>
<tr>
<td style="vertical-align: top; text-align: left"><italic>S</italic></td>
<td style="vertical-align: top; text-align: left">a set of road sections in <italic>T</italic></td>
</tr>
<tr>
<td style="vertical-align: top; text-align: left"><inline-formula id="j_infor585_ineq_001"><alternatives><mml:math>
<mml:mo stretchy="false">|</mml:mo>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">T</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">s</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">i</mml:mi>
</mml:mrow>
</mml:msub>
</mml:mrow>
</mml:msub>
<mml:mo stretchy="false">|</mml:mo></mml:math><tex-math><![CDATA[$|{T_{{s_{i}}}}|$]]></tex-math></alternatives></inline-formula></td>
<td style="vertical-align: top; text-align: left">the total number of trajectories containing road section <inline-formula id="j_infor585_ineq_002"><alternatives><mml:math>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">s</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">i</mml:mi>
</mml:mrow>
</mml:msub></mml:math><tex-math><![CDATA[${s_{i}}$]]></tex-math></alternatives></inline-formula> in <italic>T</italic></td>
</tr>
<tr>
<td style="vertical-align: top; text-align: left"><inline-formula id="j_infor585_ineq_003"><alternatives><mml:math>
<mml:mo stretchy="false">|</mml:mo>
<mml:msubsup>
<mml:mrow>
<mml:mi mathvariant="italic">t</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">j</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">s</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">i</mml:mi>
</mml:mrow>
</mml:msub>
</mml:mrow>
</mml:msubsup>
<mml:mo stretchy="false">|</mml:mo></mml:math><tex-math><![CDATA[$|{t_{j}^{{s_{i}}}}|$]]></tex-math></alternatives></inline-formula></td>
<td style="vertical-align: top; text-align: left">the total number of road sections included in trajectory <inline-formula id="j_infor585_ineq_004"><alternatives><mml:math>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">t</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">j</mml:mi>
</mml:mrow>
</mml:msub></mml:math><tex-math><![CDATA[${t_{j}}$]]></tex-math></alternatives></inline-formula> that contains road section <inline-formula id="j_infor585_ineq_005"><alternatives><mml:math>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">s</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">i</mml:mi>
</mml:mrow>
</mml:msub></mml:math><tex-math><![CDATA[${s_{i}}$]]></tex-math></alternatives></inline-formula></td>
</tr>
<tr>
<td style="vertical-align: top; text-align: left"><inline-formula id="j_infor585_ineq_006"><alternatives><mml:math>
<mml:mo stretchy="false">|</mml:mo>
<mml:mi mathvariant="italic">T</mml:mi>
<mml:mo stretchy="false">|</mml:mo></mml:math><tex-math><![CDATA[$|T|$]]></tex-math></alternatives></inline-formula></td>
<td style="vertical-align: top; text-align: left">the total number of trajectories in <italic>T</italic></td>
</tr>
<tr>
<td style="vertical-align: top; text-align: left"><inline-formula id="j_infor585_ineq_007"><alternatives><mml:math>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">C</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">s</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">i</mml:mi>
</mml:mrow>
</mml:msub>
</mml:mrow>
</mml:msub></mml:math><tex-math><![CDATA[${C_{{s_{i}}}}$]]></tex-math></alternatives></inline-formula></td>
<td style="vertical-align: top; text-align: left">the number of cars on road section <inline-formula id="j_infor585_ineq_008"><alternatives><mml:math>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">s</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">i</mml:mi>
</mml:mrow>
</mml:msub></mml:math><tex-math><![CDATA[${s_{i}}$]]></tex-math></alternatives></inline-formula></td>
</tr>
<tr>
<td style="vertical-align: top; text-align: left"><inline-formula id="j_infor585_ineq_009"><alternatives><mml:math>
<mml:mo stretchy="false">|</mml:mo>
<mml:mi mathvariant="italic">C</mml:mi>
<mml:mo stretchy="false">|</mml:mo></mml:math><tex-math><![CDATA[$|C|$]]></tex-math></alternatives></inline-formula></td>
<td style="vertical-align: top; text-align: left">the total number of cars in <italic>T</italic></td>
</tr>
<tr>
<td style="vertical-align: top; text-align: left"><inline-formula id="j_infor585_ineq_010"><alternatives><mml:math>
<mml:mo stretchy="false">|</mml:mo>
<mml:msubsup>
<mml:mrow>
<mml:mi mathvariant="italic">d</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">s</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">i</mml:mi>
</mml:mrow>
</mml:msub>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">j</mml:mi>
</mml:mrow>
</mml:msubsup>
<mml:mo stretchy="false">|</mml:mo></mml:math><tex-math><![CDATA[$|{d_{{s_{i}}}^{j}}|$]]></tex-math></alternatives></inline-formula></td>
<td style="vertical-align: top; text-align: left">the number of times driver <inline-formula id="j_infor585_ineq_011"><alternatives><mml:math>
<mml:msup>
<mml:mrow>
<mml:mi mathvariant="italic">d</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">j</mml:mi>
</mml:mrow>
</mml:msup></mml:math><tex-math><![CDATA[${d^{j}}$]]></tex-math></alternatives></inline-formula> has passed through road section <inline-formula id="j_infor585_ineq_012"><alternatives><mml:math>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">s</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">i</mml:mi>
</mml:mrow>
</mml:msub></mml:math><tex-math><![CDATA[${s_{i}}$]]></tex-math></alternatives></inline-formula></td>
</tr>
<tr>
<td style="vertical-align: top; text-align: left"><inline-formula id="j_infor585_ineq_013"><alternatives><mml:math>
<mml:mo stretchy="false">|</mml:mo>
<mml:msubsup>
<mml:mrow>
<mml:mi mathvariant="italic">d</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">S</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">j</mml:mi>
</mml:mrow>
</mml:msubsup>
<mml:mo stretchy="false">|</mml:mo></mml:math><tex-math><![CDATA[$|{d_{S}^{j}}|$]]></tex-math></alternatives></inline-formula></td>
<td style="vertical-align: top; text-align: left">the total number of times driver <inline-formula id="j_infor585_ineq_014"><alternatives><mml:math>
<mml:msup>
<mml:mrow>
<mml:mi mathvariant="italic">d</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">j</mml:mi>
</mml:mrow>
</mml:msup></mml:math><tex-math><![CDATA[${d^{j}}$]]></tex-math></alternatives></inline-formula> has passed through the road sections in <italic>S</italic></td>
</tr>
<tr>
<td style="vertical-align: top; text-align: left"><inline-formula id="j_infor585_ineq_015"><alternatives><mml:math>
<mml:msubsup>
<mml:mrow>
<mml:mi mathvariant="italic">I</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">s</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">i</mml:mi>
</mml:mrow>
</mml:msub>
</mml:mrow>
<mml:mrow>
<mml:msup>
<mml:mrow>
<mml:mi mathvariant="italic">d</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">j</mml:mi>
</mml:mrow>
</mml:msup>
</mml:mrow>
</mml:msubsup></mml:math><tex-math><![CDATA[${I_{{s_{i}}}^{{d^{j}}}}$]]></tex-math></alternatives></inline-formula></td>
<td style="vertical-align: top; text-align: left">the average time for driver <inline-formula id="j_infor585_ineq_016"><alternatives><mml:math>
<mml:msup>
<mml:mrow>
<mml:mi mathvariant="italic">d</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">j</mml:mi>
</mml:mrow>
</mml:msup></mml:math><tex-math><![CDATA[${d^{j}}$]]></tex-math></alternatives></inline-formula>’s car to pass through road section <inline-formula id="j_infor585_ineq_017"><alternatives><mml:math>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">s</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">i</mml:mi>
</mml:mrow>
</mml:msub></mml:math><tex-math><![CDATA[${s_{i}}$]]></tex-math></alternatives></inline-formula></td>
</tr>
<tr>
<td style="vertical-align: top; text-align: left"><inline-formula id="j_infor585_ineq_018"><alternatives><mml:math>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">r</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">d</mml:mi>
</mml:mrow>
</mml:msub></mml:math><tex-math><![CDATA[${r_{d}}$]]></tex-math></alternatives></inline-formula></td>
<td style="vertical-align: top; text-align: left">driver <italic>d</italic>’s requirement</td>
</tr>
<tr>
<td style="vertical-align: top; text-align: left"><inline-formula id="j_infor585_ineq_019"><alternatives><mml:math>
<mml:msubsup>
<mml:mrow>
<mml:mi mathvariant="italic">g</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">d</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">s</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">i</mml:mi>
</mml:mrow>
</mml:msub>
</mml:mrow>
</mml:msubsup></mml:math><tex-math><![CDATA[${g_{d}^{{s_{i}}}}$]]></tex-math></alternatives></inline-formula></td>
<td style="vertical-align: top; text-align: left">driver <italic>d</italic>’s requirement for road section <inline-formula id="j_infor585_ineq_020"><alternatives><mml:math>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">s</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">i</mml:mi>
</mml:mrow>
</mml:msub></mml:math><tex-math><![CDATA[${s_{i}}$]]></tex-math></alternatives></inline-formula></td>
</tr>
<tr>
<td style="vertical-align: top; text-align: left"><inline-formula id="j_infor585_ineq_021"><alternatives><mml:math>
<mml:msubsup>
<mml:mrow>
<mml:mi mathvariant="italic">g</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">c</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">d</mml:mi>
</mml:mrow>
</mml:msub>
</mml:mrow>
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">s</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">i</mml:mi>
</mml:mrow>
</mml:msub>
</mml:mrow>
</mml:msubsup></mml:math><tex-math><![CDATA[${g_{{c_{d}}}^{{s_{i}}}}$]]></tex-math></alternatives></inline-formula></td>
<td style="vertical-align: top; text-align: left">the requirements of <italic>d</italic>’s car for road section <inline-formula id="j_infor585_ineq_022"><alternatives><mml:math>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">s</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">i</mml:mi>
</mml:mrow>
</mml:msub></mml:math><tex-math><![CDATA[${s_{i}}$]]></tex-math></alternatives></inline-formula></td>
</tr>
<tr>
<td style="vertical-align: top; text-align: left"><inline-formula id="j_infor585_ineq_023"><alternatives><mml:math>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">g</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">s</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">i</mml:mi>
</mml:mrow>
</mml:msub>
</mml:mrow>
</mml:msub></mml:math><tex-math><![CDATA[${g_{{s_{i}}}}$]]></tex-math></alternatives></inline-formula></td>
<td style="vertical-align: top; text-align: left">the emergency of road section <inline-formula id="j_infor585_ineq_024"><alternatives><mml:math>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">s</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">i</mml:mi>
</mml:mrow>
</mml:msub></mml:math><tex-math><![CDATA[${s_{i}}$]]></tex-math></alternatives></inline-formula></td>
</tr>
<tr>
<td style="vertical-align: top; text-align: left"><inline-formula id="j_infor585_ineq_025"><alternatives><mml:math>
<mml:mo movablelimits="false">max</mml:mo>
<mml:mo mathvariant="normal" fence="true" stretchy="false">(</mml:mo>
<mml:mi mathvariant="italic">f</mml:mi>
<mml:mo mathvariant="normal" fence="true" stretchy="false">(</mml:mo>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">b</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">d</mml:mi>
</mml:mrow>
</mml:msub>
<mml:mo mathvariant="normal" fence="true" stretchy="false">)</mml:mo>
<mml:mo mathvariant="normal" fence="true" stretchy="false">)</mml:mo></mml:math><tex-math><![CDATA[$\max (f({b_{d}}))$]]></tex-math></alternatives></inline-formula></td>
<td style="vertical-align: top; text-align: left">the maximum value of section preferences among all road sections closest to beginning point <inline-formula id="j_infor585_ineq_026"><alternatives><mml:math>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">b</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">d</mml:mi>
</mml:mrow>
</mml:msub></mml:math><tex-math><![CDATA[${b_{d}}$]]></tex-math></alternatives></inline-formula></td>
</tr>
<tr>
<td style="vertical-align: top; text-align: left; border-bottom: solid thin"><inline-formula id="j_infor585_ineq_027"><alternatives><mml:math>
<mml:mo movablelimits="false">max</mml:mo>
<mml:mo mathvariant="normal" fence="true" stretchy="false">(</mml:mo>
<mml:mi mathvariant="italic">δ</mml:mi>
<mml:mo mathvariant="normal" fence="true" stretchy="false">(</mml:mo>
<mml:mi mathvariant="italic">T</mml:mi>
<mml:mo mathvariant="normal" fence="true" stretchy="false">)</mml:mo>
<mml:mo mathvariant="normal" fence="true" stretchy="false">)</mml:mo></mml:math><tex-math><![CDATA[$\max (\delta (T))$]]></tex-math></alternatives></inline-formula></td>
<td style="vertical-align: top; text-align: left; border-bottom: solid thin">the maximum value of trajectory references among all trajectories</td>
</tr>
</tbody>
</table>
</table-wrap>
<sec id="j_infor585_s_008">
<label>4.1</label>
<title>Sectioned Trajectory</title>
<fig id="j_infor585_fig_002">
<label>Fig. 2</label>
<caption>
<p>A running example of traffic trajectories.</p>
</caption>
<graphic xlink:href="infor585_g002.jpg"/>
</fig>
<p>Figure <xref rid="j_infor585_fig_002">2</xref> shows a running example of traffic trajectory. The definitions and formulas in this paper could be more easily understood by referring to this example.</p><statement id="j_infor585_stat_001"><label>Definition 1</label>
<title>(<italic>Sectioned trajectory</italic>)<italic>.</italic></title>
<p>Let <italic>T</italic> be a set of historical trajectory data with the same beginning and ending point, i.e. <inline-formula id="j_infor585_ineq_028"><alternatives><mml:math>
<mml:mi mathvariant="italic">T</mml:mi>
<mml:mo>=</mml:mo>
<mml:mo fence="true" stretchy="false">{</mml:mo>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">t</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mn>1</mml:mn>
</mml:mrow>
</mml:msub>
<mml:mo mathvariant="normal">,</mml:mo>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">t</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mn>2</mml:mn>
</mml:mrow>
</mml:msub>
<mml:mo mathvariant="normal">,</mml:mo>
<mml:mo>…</mml:mo>
<mml:mo mathvariant="normal">,</mml:mo>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">t</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">n</mml:mi>
</mml:mrow>
</mml:msub>
<mml:mo fence="true" stretchy="false">}</mml:mo></mml:math><tex-math><![CDATA[$T=\{{t_{1}},{t_{2}},\dots ,{t_{n}}\}$]]></tex-math></alternatives></inline-formula>. Meanwhile, <italic>S</italic> denotes a set of road sections in <italic>T</italic>, i.e. <inline-formula id="j_infor585_ineq_029"><alternatives><mml:math>
<mml:mi mathvariant="italic">S</mml:mi>
<mml:mo>=</mml:mo>
<mml:mo fence="true" stretchy="false">{</mml:mo>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">s</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mn>1</mml:mn>
</mml:mrow>
</mml:msub>
<mml:mo mathvariant="normal">,</mml:mo>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">s</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mn>2</mml:mn>
</mml:mrow>
</mml:msub>
<mml:mo mathvariant="normal">,</mml:mo>
<mml:mo>…</mml:mo>
<mml:mo mathvariant="normal">,</mml:mo>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">s</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">n</mml:mi>
</mml:mrow>
</mml:msub>
<mml:mo fence="true" stretchy="false">}</mml:mo></mml:math><tex-math><![CDATA[$S=\{{s_{1}},{s_{2}},\dots ,{s_{n}}\}$]]></tex-math></alternatives></inline-formula>. <inline-formula id="j_infor585_ineq_030"><alternatives><mml:math>
<mml:mo>∀</mml:mo>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">t</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">i</mml:mi>
</mml:mrow>
</mml:msub>
<mml:mo stretchy="false">∈</mml:mo>
<mml:mi mathvariant="italic">T</mml:mi>
<mml:mo>∧</mml:mo>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">s</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">j</mml:mi>
</mml:mrow>
</mml:msub>
<mml:mo stretchy="false">∈</mml:mo>
<mml:mi mathvariant="italic">S</mml:mi>
<mml:mo>∧</mml:mo>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">s</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">k</mml:mi>
</mml:mrow>
</mml:msub>
<mml:mo stretchy="false">∈</mml:mo>
<mml:mi mathvariant="italic">S</mml:mi>
<mml:mo>∧</mml:mo>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">s</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">j</mml:mi>
</mml:mrow>
</mml:msub>
<mml:mo stretchy="false">≠</mml:mo>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">s</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">k</mml:mi>
</mml:mrow>
</mml:msub></mml:math><tex-math><![CDATA[$\forall {t_{i}}\in T\wedge {s_{j}}\in S\wedge {s_{k}}\in S\wedge {s_{j}}\ne {s_{k}}$]]></tex-math></alternatives></inline-formula>, <inline-formula id="j_infor585_ineq_031"><alternatives><mml:math>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">t</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">i</mml:mi>
</mml:mrow>
</mml:msub>
<mml:mo>=</mml:mo>
<mml:mo fence="true" stretchy="false">{</mml:mo>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">s</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">j</mml:mi>
</mml:mrow>
</mml:msub>
<mml:mo mathvariant="normal">,</mml:mo>
<mml:mo>…</mml:mo>
<mml:mo mathvariant="normal">,</mml:mo>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">s</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">k</mml:mi>
</mml:mrow>
</mml:msub>
<mml:mo fence="true" stretchy="false">}</mml:mo></mml:math><tex-math><![CDATA[${t_{i}}=\{{s_{j}},\dots ,{s_{k}}\}$]]></tex-math></alternatives></inline-formula>.</p></statement>
<p>Corresponding to Fig. <xref rid="j_infor585_fig_002">2</xref>, the set of sectioned trajectories is shown in Fig. <xref rid="j_infor585_fig_003">3</xref>. For example, <inline-formula id="j_infor585_ineq_032"><alternatives><mml:math>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">t</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mn>1</mml:mn>
</mml:mrow>
</mml:msub>
<mml:mo>=</mml:mo>
<mml:mo fence="true" stretchy="false">{</mml:mo>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">s</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mn>1</mml:mn>
</mml:mrow>
</mml:msub>
<mml:mo mathvariant="normal">,</mml:mo>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">s</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mn>2</mml:mn>
</mml:mrow>
</mml:msub>
<mml:mo mathvariant="normal">,</mml:mo>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">s</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mn>7</mml:mn>
</mml:mrow>
</mml:msub>
<mml:mo fence="true" stretchy="false">}</mml:mo></mml:math><tex-math><![CDATA[${t_{1}}=\{{s_{1}},{s_{2}},{s_{7}}\}$]]></tex-math></alternatives></inline-formula> and <inline-formula id="j_infor585_ineq_033"><alternatives><mml:math>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">t</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mn>2</mml:mn>
</mml:mrow>
</mml:msub>
<mml:mo>=</mml:mo>
<mml:mo fence="true" stretchy="false">{</mml:mo>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">s</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mn>1</mml:mn>
</mml:mrow>
</mml:msub>
<mml:mo mathvariant="normal">,</mml:mo>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">s</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mn>3</mml:mn>
</mml:mrow>
</mml:msub>
<mml:mo mathvariant="normal">,</mml:mo>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">s</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mn>8</mml:mn>
</mml:mrow>
</mml:msub>
<mml:mo fence="true" stretchy="false">}</mml:mo></mml:math><tex-math><![CDATA[${t_{2}}=\{{s_{1}},{s_{3}},{s_{8}}\}$]]></tex-math></alternatives></inline-formula> denote two different trajectories, respectively.</p>
<fig id="j_infor585_fig_003">
<label>Fig. 3</label>
<caption>
<p>Sectioned trajectories.</p>
</caption>
<graphic xlink:href="infor585_g003.jpg"/>
</fig>
</sec>
<sec id="j_infor585_s_009">
<label>4.2</label>
<title>Traffic Trajectory Analysis on the Cloud</title><statement id="j_infor585_stat_002"><label>Definition 2</label>
<title>(<italic>Importance of road section</italic>)<italic>.</italic></title>
<p>If road section <inline-formula id="j_infor585_ineq_034"><alternatives><mml:math>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">s</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">i</mml:mi>
</mml:mrow>
</mml:msub></mml:math><tex-math><![CDATA[${s_{i}}$]]></tex-math></alternatives></inline-formula> is included in multiple trajectories, it indicates that the importance of section <inline-formula id="j_infor585_ineq_035"><alternatives><mml:math>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">s</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">i</mml:mi>
</mml:mrow>
</mml:msub></mml:math><tex-math><![CDATA[${s_{i}}$]]></tex-math></alternatives></inline-formula> for the distance from the beginning point to the ending point is relatively high. The recommended traffic trajectory for drivers may include <inline-formula id="j_infor585_ineq_036"><alternatives><mml:math>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">s</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">i</mml:mi>
</mml:mrow>
</mml:msub></mml:math><tex-math><![CDATA[${s_{i}}$]]></tex-math></alternatives></inline-formula> as much as possible. We use Mean Specific Gravity (MSG) to record how important <inline-formula id="j_infor585_ineq_037"><alternatives><mml:math>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">s</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">i</mml:mi>
</mml:mrow>
</mml:msub></mml:math><tex-math><![CDATA[${s_{i}}$]]></tex-math></alternatives></inline-formula> is to the distance. The calculation process of MSG is shown in equation (<xref rid="j_infor585_eq_001">1</xref>), where <inline-formula id="j_infor585_ineq_038"><alternatives><mml:math>
<mml:mo stretchy="false">|</mml:mo>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">T</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">s</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">i</mml:mi>
</mml:mrow>
</mml:msub>
</mml:mrow>
</mml:msub>
<mml:mo stretchy="false">|</mml:mo></mml:math><tex-math><![CDATA[$|{T_{{s_{i}}}}|$]]></tex-math></alternatives></inline-formula> denotes the total number of trajectories that contain road section <inline-formula id="j_infor585_ineq_039"><alternatives><mml:math>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">s</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">i</mml:mi>
</mml:mrow>
</mml:msub></mml:math><tex-math><![CDATA[${s_{i}}$]]></tex-math></alternatives></inline-formula> in trajectory set <italic>T</italic> and <inline-formula id="j_infor585_ineq_040"><alternatives><mml:math>
<mml:mo stretchy="false">|</mml:mo>
<mml:msubsup>
<mml:mrow>
<mml:mi mathvariant="italic">t</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">j</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">s</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">i</mml:mi>
</mml:mrow>
</mml:msub>
</mml:mrow>
</mml:msubsup>
<mml:mo stretchy="false">|</mml:mo></mml:math><tex-math><![CDATA[$|{t_{j}^{{s_{i}}}}|$]]></tex-math></alternatives></inline-formula> denotes the total number of road sections included in trajectory <inline-formula id="j_infor585_ineq_041"><alternatives><mml:math>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">t</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">j</mml:mi>
</mml:mrow>
</mml:msub></mml:math><tex-math><![CDATA[${t_{j}}$]]></tex-math></alternatives></inline-formula> that contains road section <inline-formula id="j_infor585_ineq_042"><alternatives><mml:math>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">s</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">i</mml:mi>
</mml:mrow>
</mml:msub></mml:math><tex-math><![CDATA[${s_{i}}$]]></tex-math></alternatives></inline-formula>. 
<disp-formula id="j_infor585_eq_001">
<label>(1)</label><alternatives><mml:math display="block">
<mml:mtable displaystyle="true">
<mml:mtr>
<mml:mtd>
<mml:msub>
<mml:mrow>
<mml:mtext mathvariant="italic">MSG</mml:mtext>
</mml:mrow>
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">s</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">i</mml:mi>
</mml:mrow>
</mml:msub>
</mml:mrow>
</mml:msub>
<mml:mo>=</mml:mo><mml:mstyle displaystyle="true">
<mml:mfrac>
<mml:mrow>
<mml:mo stretchy="false">|</mml:mo>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">T</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">s</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">i</mml:mi>
</mml:mrow>
</mml:msub>
</mml:mrow>
</mml:msub>
<mml:mo stretchy="false">|</mml:mo>
</mml:mrow>
<mml:mrow>
<mml:msubsup>
<mml:mrow>
<mml:mo largeop="false" movablelimits="false">∑</mml:mo>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">j</mml:mi>
<mml:mo>=</mml:mo>
<mml:mn>1</mml:mn>
</mml:mrow>
<mml:mrow>
<mml:mo stretchy="false">|</mml:mo>
<mml:mi mathvariant="italic">T</mml:mi>
<mml:mo stretchy="false">|</mml:mo>
</mml:mrow>
</mml:msubsup>
<mml:mo stretchy="false">|</mml:mo>
<mml:msubsup>
<mml:mrow>
<mml:mi mathvariant="italic">t</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">j</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">s</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">i</mml:mi>
</mml:mrow>
</mml:msub>
</mml:mrow>
</mml:msubsup>
<mml:mo stretchy="false">|</mml:mo>
</mml:mrow>
</mml:mfrac>
</mml:mstyle>
<mml:mo>.</mml:mo>
</mml:mtd>
</mml:mtr>
</mml:mtable></mml:math><tex-math><![CDATA[\[ {\textit{MSG}_{{s_{i}}}}=\frac{|{T_{{s_{i}}}}|}{{\textstyle\textstyle\sum _{j=1}^{|T|}}|{t_{j}^{{s_{i}}}}|}.\]]]></tex-math></alternatives>
</disp-formula>
</p></statement>
<p>Larger <inline-formula id="j_infor585_ineq_043"><alternatives><mml:math>
<mml:mo stretchy="false">|</mml:mo>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">T</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">s</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">i</mml:mi>
</mml:mrow>
</mml:msub>
</mml:mrow>
</mml:msub>
<mml:mo stretchy="false">|</mml:mo></mml:math><tex-math><![CDATA[$|{T_{{s_{i}}}}|$]]></tex-math></alternatives></inline-formula> causes larger <inline-formula id="j_infor585_ineq_044"><alternatives><mml:math>
<mml:msub>
<mml:mrow>
<mml:mtext mathvariant="italic">MSG</mml:mtext>
</mml:mrow>
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">s</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">i</mml:mi>
</mml:mrow>
</mml:msub>
</mml:mrow>
</mml:msub></mml:math><tex-math><![CDATA[${\textit{MSG}_{{s_{i}}}}$]]></tex-math></alternatives></inline-formula>, indicating that road section <inline-formula id="j_infor585_ineq_045"><alternatives><mml:math>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">s</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">i</mml:mi>
</mml:mrow>
</mml:msub></mml:math><tex-math><![CDATA[${s_{i}}$]]></tex-math></alternatives></inline-formula> is more important.</p><statement id="j_infor585_stat_003"><label>Definition 3</label>
<title>(<italic>Trajectory fluency</italic>)<italic>.</italic></title>
<p>As the traffic on the important road section may often be busy, simply relying on MSG to mine the traffic trajectory may ignore the impact of the trajectory fluency. For this reason, TREDP uses Inverse Document Frequency (IDF) to measure the trajectory fluency. The calculation process of IDF is shown in equation (<xref rid="j_infor585_eq_002">2</xref>), where <inline-formula id="j_infor585_ineq_046"><alternatives><mml:math>
<mml:mo stretchy="false">|</mml:mo>
<mml:mi mathvariant="italic">T</mml:mi>
<mml:mo stretchy="false">|</mml:mo></mml:math><tex-math><![CDATA[$|T|$]]></tex-math></alternatives></inline-formula> denotes the total number of trajectories in <italic>T</italic>. 
<disp-formula id="j_infor585_eq_002">
<label>(2)</label><alternatives><mml:math display="block">
<mml:mtable displaystyle="true">
<mml:mtr>
<mml:mtd>
<mml:msub>
<mml:mrow>
<mml:mtext mathvariant="italic">IDF</mml:mtext>
</mml:mrow>
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">s</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">i</mml:mi>
</mml:mrow>
</mml:msub>
</mml:mrow>
</mml:msub>
<mml:mo>=</mml:mo>
<mml:mo movablelimits="false">log</mml:mo>
<mml:mo mathvariant="normal" fence="true" maxsize="2.03em" minsize="2.03em">(</mml:mo><mml:mstyle displaystyle="true">
<mml:mfrac>
<mml:mrow>
<mml:mo stretchy="false">|</mml:mo>
<mml:mi mathvariant="italic">T</mml:mi>
<mml:mo stretchy="false">|</mml:mo>
</mml:mrow>
<mml:mrow>
<mml:mo stretchy="false">|</mml:mo>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">T</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">s</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">i</mml:mi>
</mml:mrow>
</mml:msub>
</mml:mrow>
</mml:msub>
<mml:mo stretchy="false">|</mml:mo>
<mml:mo>+</mml:mo>
<mml:mn>1</mml:mn>
</mml:mrow>
</mml:mfrac>
</mml:mstyle>
<mml:mo mathvariant="normal" fence="true" maxsize="2.03em" minsize="2.03em">)</mml:mo>
<mml:mo>.</mml:mo>
</mml:mtd>
</mml:mtr>
</mml:mtable></mml:math><tex-math><![CDATA[\[ {\textit{IDF}_{{s_{i}}}}=\log \bigg(\frac{|T|}{|{T_{{s_{i}}}}|+1}\bigg).\]]]></tex-math></alternatives>
</disp-formula>
</p></statement>
<p>If there are fewer trajectories containing section <inline-formula id="j_infor585_ineq_047"><alternatives><mml:math>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">s</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">i</mml:mi>
</mml:mrow>
</mml:msub></mml:math><tex-math><![CDATA[${s_{i}}$]]></tex-math></alternatives></inline-formula> (i.e. smaller <inline-formula id="j_infor585_ineq_048"><alternatives><mml:math>
<mml:mo stretchy="false">|</mml:mo>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">T</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">s</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">i</mml:mi>
</mml:mrow>
</mml:msub>
</mml:mrow>
</mml:msub>
<mml:mo stretchy="false">|</mml:mo></mml:math><tex-math><![CDATA[$|{T_{{s_{i}}}}|$]]></tex-math></alternatives></inline-formula>), then the <inline-formula id="j_infor585_ineq_049"><alternatives><mml:math>
<mml:msub>
<mml:mrow>
<mml:mtext mathvariant="italic">IDF</mml:mtext>
</mml:mrow>
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">s</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">i</mml:mi>
</mml:mrow>
</mml:msub>
</mml:mrow>
</mml:msub></mml:math><tex-math><![CDATA[${\textit{IDF}_{{s_{i}}}}$]]></tex-math></alternatives></inline-formula> is larger, indicating that section <inline-formula id="j_infor585_ineq_050"><alternatives><mml:math>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">s</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">i</mml:mi>
</mml:mrow>
</mml:msub></mml:math><tex-math><![CDATA[${s_{i}}$]]></tex-math></alternatives></inline-formula> has a better trajectory fluency. In other words, trajectories containing this section may provide smooth traffic.</p><statement id="j_infor585_stat_004"><label>Definition 4</label>
<title>(<italic>Section frequency</italic>)<italic>.</italic></title>
<p>Calculating the trajectory fluency alone is not enough, and it is also necessary to calculate the usage frequency of the road section itself. Thus, our Section FreQuency (SFQ) is calculated as equation (<xref rid="j_infor585_eq_003">3</xref>), where <inline-formula id="j_infor585_ineq_051"><alternatives><mml:math>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">C</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">s</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">i</mml:mi>
</mml:mrow>
</mml:msub>
</mml:mrow>
</mml:msub></mml:math><tex-math><![CDATA[${C_{{s_{i}}}}$]]></tex-math></alternatives></inline-formula> denotes the number of cars on section <inline-formula id="j_infor585_ineq_052"><alternatives><mml:math>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">s</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">i</mml:mi>
</mml:mrow>
</mml:msub></mml:math><tex-math><![CDATA[${s_{i}}$]]></tex-math></alternatives></inline-formula> and <inline-formula id="j_infor585_ineq_053"><alternatives><mml:math>
<mml:mo stretchy="false">|</mml:mo>
<mml:mi mathvariant="italic">C</mml:mi>
<mml:mo stretchy="false">|</mml:mo></mml:math><tex-math><![CDATA[$|C|$]]></tex-math></alternatives></inline-formula> denotes the total number of cars in <italic>T</italic>. 
<disp-formula id="j_infor585_eq_003">
<label>(3)</label><alternatives><mml:math display="block">
<mml:mtable displaystyle="true">
<mml:mtr>
<mml:mtd>
<mml:msub>
<mml:mrow>
<mml:mtext mathvariant="italic">SFQ</mml:mtext>
</mml:mrow>
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">s</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">i</mml:mi>
</mml:mrow>
</mml:msub>
</mml:mrow>
</mml:msub>
<mml:mo>=</mml:mo><mml:mstyle displaystyle="true">
<mml:mfrac>
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">C</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">s</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">i</mml:mi>
</mml:mrow>
</mml:msub>
</mml:mrow>
</mml:msub>
</mml:mrow>
<mml:mrow>
<mml:mo stretchy="false">|</mml:mo>
<mml:mi mathvariant="italic">C</mml:mi>
<mml:mo stretchy="false">|</mml:mo>
</mml:mrow>
</mml:mfrac>
</mml:mstyle>
<mml:mo>.</mml:mo>
</mml:mtd>
</mml:mtr>
</mml:mtable></mml:math><tex-math><![CDATA[\[ {\textit{SFQ}_{{s_{i}}}}=\frac{{C_{{s_{i}}}}}{|C|}.\]]]></tex-math></alternatives>
</disp-formula>
</p></statement>
<p>The smaller <inline-formula id="j_infor585_ineq_054"><alternatives><mml:math>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">C</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">s</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">i</mml:mi>
</mml:mrow>
</mml:msub>
</mml:mrow>
</mml:msub></mml:math><tex-math><![CDATA[${C_{{s_{i}}}}$]]></tex-math></alternatives></inline-formula> brings smaller <inline-formula id="j_infor585_ineq_055"><alternatives><mml:math>
<mml:msub>
<mml:mrow>
<mml:mtext mathvariant="italic">SFQ</mml:mtext>
</mml:mrow>
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">s</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">i</mml:mi>
</mml:mrow>
</mml:msub>
</mml:mrow>
</mml:msub></mml:math><tex-math><![CDATA[${\textit{SFQ}_{{s_{i}}}}$]]></tex-math></alternatives></inline-formula>, which indicates that the usage frequency of section <inline-formula id="j_infor585_ineq_056"><alternatives><mml:math>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">s</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">i</mml:mi>
</mml:mrow>
</mml:msub></mml:math><tex-math><![CDATA[${s_{i}}$]]></tex-math></alternatives></inline-formula> is lower. That is, the road section may be more smooth for a more possible recommendation.</p><statement id="j_infor585_stat_005"><label>Definition 5</label>
<title>(<italic>Driver attention</italic>)<italic>.</italic></title>
<p>Besides the above definitions, TREDP also considers the Driver Attention Degree (DAD) of road section <inline-formula id="j_infor585_ineq_057"><alternatives><mml:math>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">s</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">i</mml:mi>
</mml:mrow>
</mml:msub></mml:math><tex-math><![CDATA[${s_{i}}$]]></tex-math></alternatives></inline-formula>. To a certain extent, DAD measures the driver’s preference for section <inline-formula id="j_infor585_ineq_058"><alternatives><mml:math>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">s</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">i</mml:mi>
</mml:mrow>
</mml:msub></mml:math><tex-math><![CDATA[${s_{i}}$]]></tex-math></alternatives></inline-formula>. The calculation process of DAD is shown in equation (<xref rid="j_infor585_eq_004">4</xref>), where <inline-formula id="j_infor585_ineq_059"><alternatives><mml:math>
<mml:mo stretchy="false">|</mml:mo>
<mml:msubsup>
<mml:mrow>
<mml:mi mathvariant="italic">d</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">s</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">i</mml:mi>
</mml:mrow>
</mml:msub>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">j</mml:mi>
</mml:mrow>
</mml:msubsup>
<mml:mo stretchy="false">|</mml:mo></mml:math><tex-math><![CDATA[$|{d_{{s_{i}}}^{j}}|$]]></tex-math></alternatives></inline-formula> denotes the number of times driver <inline-formula id="j_infor585_ineq_060"><alternatives><mml:math>
<mml:msup>
<mml:mrow>
<mml:mi mathvariant="italic">d</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">j</mml:mi>
</mml:mrow>
</mml:msup></mml:math><tex-math><![CDATA[${d^{j}}$]]></tex-math></alternatives></inline-formula> has passed through section <inline-formula id="j_infor585_ineq_061"><alternatives><mml:math>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">s</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">i</mml:mi>
</mml:mrow>
</mml:msub></mml:math><tex-math><![CDATA[${s_{i}}$]]></tex-math></alternatives></inline-formula> and <inline-formula id="j_infor585_ineq_062"><alternatives><mml:math>
<mml:mo stretchy="false">|</mml:mo>
<mml:msubsup>
<mml:mrow>
<mml:mi mathvariant="italic">d</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">S</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">j</mml:mi>
</mml:mrow>
</mml:msubsup>
<mml:mo stretchy="false">|</mml:mo></mml:math><tex-math><![CDATA[$|{d_{S}^{j}}|$]]></tex-math></alternatives></inline-formula> denotes the total number of times driver <inline-formula id="j_infor585_ineq_063"><alternatives><mml:math>
<mml:msup>
<mml:mrow>
<mml:mi mathvariant="italic">d</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">j</mml:mi>
</mml:mrow>
</mml:msup></mml:math><tex-math><![CDATA[${d^{j}}$]]></tex-math></alternatives></inline-formula> has passed through the road sections in <italic>S</italic>. 
<disp-formula id="j_infor585_eq_004">
<label>(4)</label><alternatives><mml:math display="block">
<mml:mtable displaystyle="true">
<mml:mtr>
<mml:mtd>
<mml:msub>
<mml:mrow>
<mml:mtext mathvariant="italic">DAD</mml:mtext>
</mml:mrow>
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">s</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">i</mml:mi>
</mml:mrow>
</mml:msub>
</mml:mrow>
</mml:msub>
<mml:mo>=</mml:mo><mml:mstyle displaystyle="true">
<mml:mfrac>
<mml:mrow>
<mml:msubsup>
<mml:mrow>
<mml:mo largeop="false" movablelimits="false">∑</mml:mo>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">j</mml:mi>
<mml:mo>=</mml:mo>
<mml:mn>1</mml:mn>
</mml:mrow>
<mml:mrow>
<mml:mo stretchy="false">|</mml:mo>
<mml:mi mathvariant="italic">D</mml:mi>
<mml:mo stretchy="false">|</mml:mo>
</mml:mrow>
</mml:msubsup>
<mml:mo stretchy="false">|</mml:mo>
<mml:msubsup>
<mml:mrow>
<mml:mi mathvariant="italic">d</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">s</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">i</mml:mi>
</mml:mrow>
</mml:msub>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">j</mml:mi>
</mml:mrow>
</mml:msubsup>
<mml:mo stretchy="false">|</mml:mo>
<mml:mo>+</mml:mo>
<mml:mn>1</mml:mn>
</mml:mrow>
<mml:mrow>
<mml:msubsup>
<mml:mrow>
<mml:mo largeop="false" movablelimits="false">∑</mml:mo>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">j</mml:mi>
<mml:mo>=</mml:mo>
<mml:mn>1</mml:mn>
</mml:mrow>
<mml:mrow>
<mml:mo stretchy="false">|</mml:mo>
<mml:mi mathvariant="italic">D</mml:mi>
<mml:mo stretchy="false">|</mml:mo>
</mml:mrow>
</mml:msubsup>
<mml:mo stretchy="false">|</mml:mo>
<mml:msubsup>
<mml:mrow>
<mml:mi mathvariant="italic">d</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">S</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">j</mml:mi>
</mml:mrow>
</mml:msubsup>
<mml:mo stretchy="false">|</mml:mo>
</mml:mrow>
</mml:mfrac>
</mml:mstyle>
<mml:mo>.</mml:mo>
</mml:mtd>
</mml:mtr>
</mml:mtable></mml:math><tex-math><![CDATA[\[ {\textit{DAD}_{{s_{i}}}}=\frac{{\textstyle\textstyle\sum _{j=1}^{|D|}}|{d_{{s_{i}}}^{j}}|+1}{{\textstyle\textstyle\sum _{j=1}^{|D|}}|{d_{S}^{j}}|}.\]]]></tex-math></alternatives>
</disp-formula>
</p></statement>
<p>Larger <inline-formula id="j_infor585_ineq_064"><alternatives><mml:math>
<mml:mo stretchy="false">|</mml:mo>
<mml:msubsup>
<mml:mrow>
<mml:mi mathvariant="italic">d</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">s</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">i</mml:mi>
</mml:mrow>
</mml:msub>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">j</mml:mi>
</mml:mrow>
</mml:msubsup>
<mml:mo stretchy="false">|</mml:mo></mml:math><tex-math><![CDATA[$|{d_{{s_{i}}}^{j}}|$]]></tex-math></alternatives></inline-formula> indicates driver <inline-formula id="j_infor585_ineq_065"><alternatives><mml:math>
<mml:msup>
<mml:mrow>
<mml:mi mathvariant="italic">d</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">j</mml:mi>
</mml:mrow>
</mml:msup></mml:math><tex-math><![CDATA[${d^{j}}$]]></tex-math></alternatives></inline-formula> prefers road section <inline-formula id="j_infor585_ineq_066"><alternatives><mml:math>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">s</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">i</mml:mi>
</mml:mrow>
</mml:msub></mml:math><tex-math><![CDATA[${s_{i}}$]]></tex-math></alternatives></inline-formula>.</p><statement id="j_infor585_stat_006"><label>Definition 6</label>
<title>(<italic>Driving time</italic>)<italic>.</italic></title>
<p>Driving time is also important in traffic trajectory recommendations. Thus, the calculation process of Average Driving Time (ADT) on road section <inline-formula id="j_infor585_ineq_067"><alternatives><mml:math>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">s</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">i</mml:mi>
</mml:mrow>
</mml:msub></mml:math><tex-math><![CDATA[${s_{i}}$]]></tex-math></alternatives></inline-formula> is shown in equation (<xref rid="j_infor585_eq_005">5</xref>), where <inline-formula id="j_infor585_ineq_068"><alternatives><mml:math>
<mml:msubsup>
<mml:mrow>
<mml:mi mathvariant="italic">I</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">s</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">i</mml:mi>
</mml:mrow>
</mml:msub>
</mml:mrow>
<mml:mrow>
<mml:msup>
<mml:mrow>
<mml:mi mathvariant="italic">d</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">j</mml:mi>
</mml:mrow>
</mml:msup>
</mml:mrow>
</mml:msubsup></mml:math><tex-math><![CDATA[${I_{{s_{i}}}^{{d^{j}}}}$]]></tex-math></alternatives></inline-formula> denotes the average time for driver <inline-formula id="j_infor585_ineq_069"><alternatives><mml:math>
<mml:msup>
<mml:mrow>
<mml:mi mathvariant="italic">d</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">j</mml:mi>
</mml:mrow>
</mml:msup></mml:math><tex-math><![CDATA[${d^{j}}$]]></tex-math></alternatives></inline-formula>’s car to pass through road section <inline-formula id="j_infor585_ineq_070"><alternatives><mml:math>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">s</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">i</mml:mi>
</mml:mrow>
</mml:msub></mml:math><tex-math><![CDATA[${s_{i}}$]]></tex-math></alternatives></inline-formula>. 
<disp-formula id="j_infor585_eq_005">
<label>(5)</label><alternatives><mml:math display="block">
<mml:mtable displaystyle="true">
<mml:mtr>
<mml:mtd>
<mml:msub>
<mml:mrow>
<mml:mtext mathvariant="italic">ADT</mml:mtext>
</mml:mrow>
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">s</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">i</mml:mi>
</mml:mrow>
</mml:msub>
</mml:mrow>
</mml:msub>
<mml:mo>=</mml:mo>
<mml:mtext mathvariant="italic">Average</mml:mtext>
<mml:mo mathvariant="normal" fence="true" maxsize="2.45em" minsize="2.45em">(</mml:mo>
<mml:munderover accentunder="false" accent="false">
<mml:mrow>
<mml:mstyle displaystyle="true">
<mml:mo largeop="true" movablelimits="false">∑</mml:mo></mml:mstyle>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">j</mml:mi>
<mml:mo>=</mml:mo>
<mml:mn>1</mml:mn>
</mml:mrow>
<mml:mrow>
<mml:mo stretchy="false">|</mml:mo>
<mml:mi mathvariant="italic">D</mml:mi>
<mml:mo stretchy="false">|</mml:mo>
</mml:mrow>
</mml:munderover>
<mml:msubsup>
<mml:mrow>
<mml:mi mathvariant="italic">I</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">s</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">i</mml:mi>
</mml:mrow>
</mml:msub>
</mml:mrow>
<mml:mrow>
<mml:msup>
<mml:mrow>
<mml:mi mathvariant="italic">d</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">j</mml:mi>
</mml:mrow>
</mml:msup>
</mml:mrow>
</mml:msubsup>
<mml:mo mathvariant="normal" fence="true" maxsize="2.45em" minsize="2.45em">)</mml:mo>
<mml:mo>.</mml:mo>
</mml:mtd>
</mml:mtr>
</mml:mtable></mml:math><tex-math><![CDATA[\[ {\textit{ADT}_{{s_{i}}}}=\textit{Average}\Bigg({\sum \limits_{j=1}^{|D|}}{I_{{s_{i}}}^{{d^{j}}}}\Bigg).\]]]></tex-math></alternatives>
</disp-formula>
</p></statement>
<p>Drivers certainly want less driving time. Therefore, the road section with less driving time is more likely to be recommended.</p>
</sec>
<sec id="j_infor585_s_010">
<label>4.3</label>
<title>Driver-Car-Road Requirements on the Edge</title>
<p>The real-time and unexpected driver-car-road requirements are performed on the edge as follows.</p><statement id="j_infor585_stat_007"><label>Definition 7</label>
<title>(<italic>Driver requirement</italic>)<italic>.</italic></title>
<p>Driver <italic>d</italic>’s requirement <inline-formula id="j_infor585_ineq_071"><alternatives><mml:math>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">r</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">d</mml:mi>
</mml:mrow>
</mml:msub>
<mml:mo>=</mml:mo>
<mml:mo fence="true" stretchy="false">⟨</mml:mo>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">b</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">d</mml:mi>
</mml:mrow>
</mml:msub>
<mml:mo mathvariant="normal">,</mml:mo>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">e</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">d</mml:mi>
</mml:mrow>
</mml:msub>
<mml:mo mathvariant="normal">,</mml:mo>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">g</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">d</mml:mi>
</mml:mrow>
</mml:msub>
<mml:mo fence="true" stretchy="false">⟩</mml:mo></mml:math><tex-math><![CDATA[${r_{d}}=\langle {b_{d}},{e_{d}},{g_{d}}\rangle $]]></tex-math></alternatives></inline-formula>, where <inline-formula id="j_infor585_ineq_072"><alternatives><mml:math>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">b</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">d</mml:mi>
</mml:mrow>
</mml:msub></mml:math><tex-math><![CDATA[${b_{d}}$]]></tex-math></alternatives></inline-formula> denotes <italic>d</italic>’s beginning point, <inline-formula id="j_infor585_ineq_073"><alternatives><mml:math>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">e</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">d</mml:mi>
</mml:mrow>
</mml:msub></mml:math><tex-math><![CDATA[${e_{d}}$]]></tex-math></alternatives></inline-formula> denotes <italic>d</italic>’s ending point and <inline-formula id="j_infor585_ineq_074"><alternatives><mml:math>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">g</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">d</mml:mi>
</mml:mrow>
</mml:msub></mml:math><tex-math><![CDATA[${g_{d}}$]]></tex-math></alternatives></inline-formula> denotes <italic>d</italic>’s road section requirements, i.e. <inline-formula id="j_infor585_ineq_075"><alternatives><mml:math>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">g</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">d</mml:mi>
</mml:mrow>
</mml:msub>
<mml:mo>=</mml:mo>
<mml:mo fence="true" stretchy="false">{</mml:mo>
<mml:msubsup>
<mml:mrow>
<mml:mi mathvariant="italic">g</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">d</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">s</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">i</mml:mi>
</mml:mrow>
</mml:msub>
</mml:mrow>
</mml:msubsup>
<mml:mo mathvariant="normal">,</mml:mo>
<mml:mo>…</mml:mo>
<mml:mo mathvariant="normal">,</mml:mo>
<mml:msubsup>
<mml:mrow>
<mml:mi mathvariant="italic">g</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">d</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">s</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">j</mml:mi>
</mml:mrow>
</mml:msub>
</mml:mrow>
</mml:msubsup>
<mml:mo fence="true" stretchy="false">}</mml:mo></mml:math><tex-math><![CDATA[${g_{d}}=\{{g_{d}^{{s_{i}}}},\dots ,{g_{d}^{{s_{j}}}}\}$]]></tex-math></alternatives></inline-formula>. <inline-formula id="j_infor585_ineq_076"><alternatives><mml:math>
<mml:mo>∀</mml:mo>
<mml:msubsup>
<mml:mrow>
<mml:mi mathvariant="italic">g</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">d</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">s</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">i</mml:mi>
</mml:mrow>
</mml:msub>
</mml:mrow>
</mml:msubsup>
<mml:mo stretchy="false">∈</mml:mo>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">g</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">d</mml:mi>
</mml:mrow>
</mml:msub></mml:math><tex-math><![CDATA[$\forall {g_{d}^{{s_{i}}}}\in {g_{d}}$]]></tex-math></alternatives></inline-formula>, <inline-formula id="j_infor585_ineq_077"><alternatives><mml:math>
<mml:msubsup>
<mml:mrow>
<mml:mi mathvariant="italic">g</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">d</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">s</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">i</mml:mi>
</mml:mrow>
</mml:msub>
</mml:mrow>
</mml:msubsup></mml:math><tex-math><![CDATA[${g_{d}^{{s_{i}}}}$]]></tex-math></alternatives></inline-formula> denotes driver <italic>d</italic>’s requirement for road section <inline-formula id="j_infor585_ineq_078"><alternatives><mml:math>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">s</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">i</mml:mi>
</mml:mrow>
</mml:msub></mml:math><tex-math><![CDATA[${s_{i}}$]]></tex-math></alternatives></inline-formula>.</p></statement>
<p>For example, if driver <italic>d</italic> has already entered fatigued driving, they may need to stay and rest at a hotel on road section <inline-formula id="j_infor585_ineq_079"><alternatives><mml:math>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">s</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">i</mml:mi>
</mml:mrow>
</mml:msub></mml:math><tex-math><![CDATA[${s_{i}}$]]></tex-math></alternatives></inline-formula>. In this case, <inline-formula id="j_infor585_ineq_080"><alternatives><mml:math>
<mml:msubsup>
<mml:mrow>
<mml:mi mathvariant="italic">g</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">d</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">s</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">i</mml:mi>
</mml:mrow>
</mml:msub>
</mml:mrow>
</mml:msubsup></mml:math><tex-math><![CDATA[${g_{d}^{{s_{i}}}}$]]></tex-math></alternatives></inline-formula> may be a larger value. Larger <inline-formula id="j_infor585_ineq_081"><alternatives><mml:math>
<mml:msubsup>
<mml:mrow>
<mml:mi mathvariant="italic">g</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">d</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">s</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">i</mml:mi>
</mml:mrow>
</mml:msub>
</mml:mrow>
</mml:msubsup></mml:math><tex-math><![CDATA[${g_{d}^{{s_{i}}}}$]]></tex-math></alternatives></inline-formula> indicates the more urgent need of driver <italic>d</italic> for road section <inline-formula id="j_infor585_ineq_082"><alternatives><mml:math>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">s</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">i</mml:mi>
</mml:mrow>
</mml:msub></mml:math><tex-math><![CDATA[${s_{i}}$]]></tex-math></alternatives></inline-formula>.</p><statement id="j_infor585_stat_008"><label>Definition 8</label>
<title>(<italic>Car requirement</italic>)<italic>.</italic></title>
<p><inline-formula id="j_infor585_ineq_083"><alternatives><mml:math>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">g</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">c</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">d</mml:mi>
</mml:mrow>
</mml:msub>
</mml:mrow>
</mml:msub></mml:math><tex-math><![CDATA[${g_{{c_{d}}}}$]]></tex-math></alternatives></inline-formula> denotes the requirements of <italic>d</italic>’s car for road sections, i.e. <inline-formula id="j_infor585_ineq_084"><alternatives><mml:math>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">g</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">c</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">d</mml:mi>
</mml:mrow>
</mml:msub>
</mml:mrow>
</mml:msub>
<mml:mo>=</mml:mo>
<mml:mo fence="true" stretchy="false">{</mml:mo>
<mml:msubsup>
<mml:mrow>
<mml:mi mathvariant="italic">g</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">c</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">d</mml:mi>
</mml:mrow>
</mml:msub>
</mml:mrow>
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">s</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">i</mml:mi>
</mml:mrow>
</mml:msub>
</mml:mrow>
</mml:msubsup>
<mml:mo mathvariant="normal">,</mml:mo>
<mml:mo>…</mml:mo>
<mml:mo mathvariant="normal">,</mml:mo>
<mml:msubsup>
<mml:mrow>
<mml:mi mathvariant="italic">g</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">c</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">d</mml:mi>
</mml:mrow>
</mml:msub>
</mml:mrow>
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">s</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">j</mml:mi>
</mml:mrow>
</mml:msub>
</mml:mrow>
</mml:msubsup>
<mml:mo fence="true" stretchy="false">}</mml:mo></mml:math><tex-math><![CDATA[${g_{{c_{d}}}}=\{{g_{{c_{d}}}^{{s_{i}}}},\dots ,{g_{{c_{d}}}^{{s_{j}}}}\}$]]></tex-math></alternatives></inline-formula>. <inline-formula id="j_infor585_ineq_085"><alternatives><mml:math>
<mml:mo>∀</mml:mo>
<mml:msubsup>
<mml:mrow>
<mml:mi mathvariant="italic">g</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">c</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">d</mml:mi>
</mml:mrow>
</mml:msub>
</mml:mrow>
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">s</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">i</mml:mi>
</mml:mrow>
</mml:msub>
</mml:mrow>
</mml:msubsup>
<mml:mo stretchy="false">∈</mml:mo>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">g</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">c</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">d</mml:mi>
</mml:mrow>
</mml:msub>
</mml:mrow>
</mml:msub></mml:math><tex-math><![CDATA[$\forall {g_{{c_{d}}}^{{s_{i}}}}\in {g_{{c_{d}}}}$]]></tex-math></alternatives></inline-formula>, <inline-formula id="j_infor585_ineq_086"><alternatives><mml:math>
<mml:msubsup>
<mml:mrow>
<mml:mi mathvariant="italic">g</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">c</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">d</mml:mi>
</mml:mrow>
</mml:msub>
</mml:mrow>
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">s</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">i</mml:mi>
</mml:mrow>
</mml:msub>
</mml:mrow>
</mml:msubsup></mml:math><tex-math><![CDATA[${g_{{c_{d}}}^{{s_{i}}}}$]]></tex-math></alternatives></inline-formula> denotes the requirements of <italic>d</italic>’s car for road section <inline-formula id="j_infor585_ineq_087"><alternatives><mml:math>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">s</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">i</mml:mi>
</mml:mrow>
</mml:msub></mml:math><tex-math><![CDATA[${s_{i}}$]]></tex-math></alternatives></inline-formula>.</p></statement>
<p>For example, driver <italic>d</italic>’s car needs to be charged or refueled at the gas station on road section <inline-formula id="j_infor585_ineq_088"><alternatives><mml:math>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">s</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">i</mml:mi>
</mml:mrow>
</mml:msub></mml:math><tex-math><![CDATA[${s_{i}}$]]></tex-math></alternatives></inline-formula>. In this case, <inline-formula id="j_infor585_ineq_089"><alternatives><mml:math>
<mml:msubsup>
<mml:mrow>
<mml:mi mathvariant="italic">g</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">c</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">d</mml:mi>
</mml:mrow>
</mml:msub>
</mml:mrow>
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">s</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">i</mml:mi>
</mml:mrow>
</mml:msub>
</mml:mrow>
</mml:msubsup></mml:math><tex-math><![CDATA[${g_{{c_{d}}}^{{s_{i}}}}$]]></tex-math></alternatives></inline-formula> may be a larger value. Larger <inline-formula id="j_infor585_ineq_090"><alternatives><mml:math>
<mml:msubsup>
<mml:mrow>
<mml:mi mathvariant="italic">g</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">c</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">d</mml:mi>
</mml:mrow>
</mml:msub>
</mml:mrow>
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">s</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">i</mml:mi>
</mml:mrow>
</mml:msub>
</mml:mrow>
</mml:msubsup></mml:math><tex-math><![CDATA[${g_{{c_{d}}}^{{s_{i}}}}$]]></tex-math></alternatives></inline-formula> indicates the more urgent need of <italic>d</italic>’s car for road section <inline-formula id="j_infor585_ineq_091"><alternatives><mml:math>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">s</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">i</mml:mi>
</mml:mrow>
</mml:msub></mml:math><tex-math><![CDATA[${s_{i}}$]]></tex-math></alternatives></inline-formula>.</p><statement id="j_infor585_stat_009"><label>Definition 9</label>
<title>(<italic>Road emergency</italic>)<italic>.</italic></title>
<p><inline-formula id="j_infor585_ineq_092"><alternatives><mml:math>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">g</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">S</mml:mi>
</mml:mrow>
</mml:msub></mml:math><tex-math><![CDATA[${g_{S}}$]]></tex-math></alternatives></inline-formula> denotes the road emergencies of road section set <italic>S</italic>, i.e. <inline-formula id="j_infor585_ineq_093"><alternatives><mml:math>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">g</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">S</mml:mi>
</mml:mrow>
</mml:msub>
<mml:mo>=</mml:mo>
<mml:mo fence="true" stretchy="false">{</mml:mo>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">g</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">s</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">i</mml:mi>
</mml:mrow>
</mml:msub>
</mml:mrow>
</mml:msub>
<mml:mo mathvariant="normal">,</mml:mo>
<mml:mo>…</mml:mo>
<mml:mo mathvariant="normal">,</mml:mo>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">g</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">s</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">j</mml:mi>
</mml:mrow>
</mml:msub>
</mml:mrow>
</mml:msub>
<mml:mo fence="true" stretchy="false">}</mml:mo></mml:math><tex-math><![CDATA[${g_{S}}=\{{g_{{s_{i}}}},\dots ,{g_{{s_{j}}}}\}$]]></tex-math></alternatives></inline-formula>. <inline-formula id="j_infor585_ineq_094"><alternatives><mml:math>
<mml:mo>∀</mml:mo>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">g</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">s</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">i</mml:mi>
</mml:mrow>
</mml:msub>
</mml:mrow>
</mml:msub>
<mml:mo stretchy="false">∈</mml:mo>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">g</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">S</mml:mi>
</mml:mrow>
</mml:msub></mml:math><tex-math><![CDATA[$\forall {g_{{s_{i}}}}\in {g_{S}}$]]></tex-math></alternatives></inline-formula>, <inline-formula id="j_infor585_ineq_095"><alternatives><mml:math>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">g</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">s</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">i</mml:mi>
</mml:mrow>
</mml:msub>
</mml:mrow>
</mml:msub></mml:math><tex-math><![CDATA[${g_{{s_{i}}}}$]]></tex-math></alternatives></inline-formula> denotes the emergency of road section <inline-formula id="j_infor585_ineq_096"><alternatives><mml:math>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">s</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">i</mml:mi>
</mml:mrow>
</mml:msub></mml:math><tex-math><![CDATA[${s_{i}}$]]></tex-math></alternatives></inline-formula>.</p></statement>
<p>For example, if an accident occurs on road section <inline-formula id="j_infor585_ineq_097"><alternatives><mml:math>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">s</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">i</mml:mi>
</mml:mrow>
</mml:msub></mml:math><tex-math><![CDATA[${s_{i}}$]]></tex-math></alternatives></inline-formula>, causing certain traffic congestion, <inline-formula id="j_infor585_ineq_098"><alternatives><mml:math>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">g</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">s</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">i</mml:mi>
</mml:mrow>
</mml:msub>
</mml:mrow>
</mml:msub></mml:math><tex-math><![CDATA[${g_{{s_{i}}}}$]]></tex-math></alternatives></inline-formula> is a relatively large value.</p><statement id="j_infor585_stat_010"><label>Definition 10</label>
<title>(<italic>Real-time unexpected factor</italic>)<italic>.</italic></title>
<p>The calculation on the cloud in Section <xref rid="j_infor585_s_009">4.2</xref> only includes the historical relationships among driver-car-road. However, drivers’ physical conditions, car operating conditions and road conditions are all constantly changing, so the cloud calculations lack the calculation of real-time unexpected factors (such as suddenly discovering that the car is out of battery, unstable vital signs of the owner during safety checks, and accidents on the road ahead). Therefore, our calculation method for Real-time Unexpected Factors (RUF) is shown in equation (<xref rid="j_infor585_eq_006">6</xref>). 
<disp-formula id="j_infor585_eq_006">
<label>(6)</label><alternatives><mml:math display="block">
<mml:mtable displaystyle="true">
<mml:mtr>
<mml:mtd>
<mml:msub>
<mml:mrow>
<mml:mtext mathvariant="italic">RUF</mml:mtext>
</mml:mrow>
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">s</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">i</mml:mi>
</mml:mrow>
</mml:msub>
</mml:mrow>
</mml:msub>
<mml:mo>=</mml:mo><mml:mstyle displaystyle="true">
<mml:mfrac>
<mml:mrow>
<mml:msubsup>
<mml:mrow>
<mml:mi mathvariant="italic">g</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">d</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">s</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">i</mml:mi>
</mml:mrow>
</mml:msub>
</mml:mrow>
</mml:msubsup>
<mml:mo>+</mml:mo>
<mml:msubsup>
<mml:mrow>
<mml:mi mathvariant="italic">g</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">c</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">d</mml:mi>
</mml:mrow>
</mml:msub>
</mml:mrow>
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">s</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">i</mml:mi>
</mml:mrow>
</mml:msub>
</mml:mrow>
</mml:msubsup>
</mml:mrow>
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">g</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">s</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">i</mml:mi>
</mml:mrow>
</mml:msub>
</mml:mrow>
</mml:msub>
</mml:mrow>
</mml:mfrac>
</mml:mstyle>
<mml:mo>.</mml:mo>
</mml:mtd>
</mml:mtr>
</mml:mtable></mml:math><tex-math><![CDATA[\[ {\textit{RUF}_{{s_{i}}}}=\frac{{g_{d}^{{s_{i}}}}+{g_{{c_{d}}}^{{s_{i}}}}}{{g_{{s_{i}}}}}.\]]]></tex-math></alternatives>
</disp-formula>
</p></statement>
<p>Larger <inline-formula id="j_infor585_ineq_099"><alternatives><mml:math>
<mml:msub>
<mml:mrow>
<mml:mtext mathvariant="italic">RUF</mml:mtext>
</mml:mrow>
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">s</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">i</mml:mi>
</mml:mrow>
</mml:msub>
</mml:mrow>
</mml:msub></mml:math><tex-math><![CDATA[${\textit{RUF}_{{s_{i}}}}$]]></tex-math></alternatives></inline-formula> indicates a more possible recommendation for road section <inline-formula id="j_infor585_ineq_100"><alternatives><mml:math>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">s</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">i</mml:mi>
</mml:mrow>
</mml:msub></mml:math><tex-math><![CDATA[${s_{i}}$]]></tex-math></alternatives></inline-formula>.</p>
</sec>
<sec id="j_infor585_s_011">
<label>4.4</label>
<title>Edge-Cloud Computing</title><statement id="j_infor585_stat_011"><label>Definition 11</label>
<title>(<italic>Section preference</italic>)<italic>.</italic></title>
<p>Section preference refers to the importance of road section <inline-formula id="j_infor585_ineq_101"><alternatives><mml:math>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">s</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">i</mml:mi>
</mml:mrow>
</mml:msub></mml:math><tex-math><![CDATA[${s_{i}}$]]></tex-math></alternatives></inline-formula> in trajectory set <italic>T</italic>. Its calculation process is shown in equation (<xref rid="j_infor585_eq_007">7</xref>): 
<disp-formula id="j_infor585_eq_007">
<label>(7)</label><alternatives><mml:math display="block">
<mml:mtable displaystyle="true">
<mml:mtr>
<mml:mtd>
<mml:mi mathvariant="italic">f</mml:mi>
<mml:mo mathvariant="normal" fence="true" stretchy="false">(</mml:mo>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">s</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">i</mml:mi>
</mml:mrow>
</mml:msub>
<mml:mo mathvariant="normal" fence="true" stretchy="false">)</mml:mo>
<mml:mo>=</mml:mo><mml:mstyle displaystyle="true">
<mml:mfrac>
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mtext mathvariant="italic">MSG</mml:mtext>
</mml:mrow>
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">s</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">i</mml:mi>
</mml:mrow>
</mml:msub>
</mml:mrow>
</mml:msub>
<mml:mo>×</mml:mo>
<mml:msub>
<mml:mrow>
<mml:mtext mathvariant="italic">IDF</mml:mtext>
</mml:mrow>
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">s</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">i</mml:mi>
</mml:mrow>
</mml:msub>
</mml:mrow>
</mml:msub>
<mml:mo>×</mml:mo>
<mml:msub>
<mml:mrow>
<mml:mtext mathvariant="italic">DAD</mml:mtext>
</mml:mrow>
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">s</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">i</mml:mi>
</mml:mrow>
</mml:msub>
</mml:mrow>
</mml:msub>
<mml:mo>×</mml:mo>
<mml:msub>
<mml:mrow>
<mml:mtext mathvariant="italic">RUF</mml:mtext>
</mml:mrow>
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">s</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">i</mml:mi>
</mml:mrow>
</mml:msub>
</mml:mrow>
</mml:msub>
</mml:mrow>
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mtext mathvariant="italic">SFQ</mml:mtext>
</mml:mrow>
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">s</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">i</mml:mi>
</mml:mrow>
</mml:msub>
</mml:mrow>
</mml:msub>
<mml:mo>×</mml:mo>
<mml:msub>
<mml:mrow>
<mml:mtext mathvariant="italic">ADT</mml:mtext>
</mml:mrow>
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">s</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">i</mml:mi>
</mml:mrow>
</mml:msub>
</mml:mrow>
</mml:msub>
</mml:mrow>
</mml:mfrac>
</mml:mstyle>
<mml:mo>.</mml:mo>
</mml:mtd>
</mml:mtr>
</mml:mtable></mml:math><tex-math><![CDATA[\[ f({s_{i}})=\frac{{\textit{MSG}_{{s_{i}}}}\times {\textit{IDF}_{{s_{i}}}}\times {\textit{DAD}_{{s_{i}}}}\times {\textit{RUF}_{{s_{i}}}}}{{\textit{SFQ}_{{s_{i}}}}\times {\textit{ADT}_{{s_{i}}}}}.\]]]></tex-math></alternatives>
</disp-formula>
</p></statement>
<p>Larger <inline-formula id="j_infor585_ineq_102"><alternatives><mml:math>
<mml:mi mathvariant="italic">f</mml:mi>
<mml:mo mathvariant="normal" fence="true" stretchy="false">(</mml:mo>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">s</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">i</mml:mi>
</mml:mrow>
</mml:msub>
<mml:mo mathvariant="normal" fence="true" stretchy="false">)</mml:mo></mml:math><tex-math><![CDATA[$f({s_{i}})$]]></tex-math></alternatives></inline-formula> indicates that more drivers may prefer road section <inline-formula id="j_infor585_ineq_103"><alternatives><mml:math>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">s</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">i</mml:mi>
</mml:mrow>
</mml:msub></mml:math><tex-math><![CDATA[${s_{i}}$]]></tex-math></alternatives></inline-formula>. However, as more and more cars enter <inline-formula id="j_infor585_ineq_104"><alternatives><mml:math>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">s</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">i</mml:mi>
</mml:mrow>
</mml:msub></mml:math><tex-math><![CDATA[${s_{i}}$]]></tex-math></alternatives></inline-formula>, <inline-formula id="j_infor585_ineq_105"><alternatives><mml:math>
<mml:mi mathvariant="italic">f</mml:mi>
<mml:mo mathvariant="normal" fence="true" stretchy="false">(</mml:mo>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">s</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">i</mml:mi>
</mml:mrow>
</mml:msub>
<mml:mo mathvariant="normal" fence="true" stretchy="false">)</mml:mo></mml:math><tex-math><![CDATA[$f({s_{i}})$]]></tex-math></alternatives></inline-formula> would become smaller, resulting in fewer drivers choosing <inline-formula id="j_infor585_ineq_106"><alternatives><mml:math>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">s</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">i</mml:mi>
</mml:mrow>
</mml:msub></mml:math><tex-math><![CDATA[${s_{i}}$]]></tex-math></alternatives></inline-formula>. This is a game process that continuously updates recommendations through our framework.</p><statement id="j_infor585_stat_012"><label>Definition 12</label>
<title>(<italic>Trajectory preference</italic>)<italic>.</italic></title>
<p>According to driver-car-road preferences for different trajectories, TREDP finds out the trajectories with high driver satisfaction. The computing method of trajectory <inline-formula id="j_infor585_ineq_107"><alternatives><mml:math>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">t</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">j</mml:mi>
</mml:mrow>
</mml:msub></mml:math><tex-math><![CDATA[${t_{j}}$]]></tex-math></alternatives></inline-formula>’s preference is shown in equation (<xref rid="j_infor585_eq_008">8</xref>): 
<disp-formula id="j_infor585_eq_008">
<label>(8)</label><alternatives><mml:math display="block">
<mml:mtable displaystyle="true">
<mml:mtr>
<mml:mtd>
<mml:mi mathvariant="italic">δ</mml:mi>
<mml:mo mathvariant="normal" fence="true" stretchy="false">(</mml:mo>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">t</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">j</mml:mi>
</mml:mrow>
</mml:msub>
<mml:mo mathvariant="normal" fence="true" stretchy="false">)</mml:mo>
<mml:mo>=</mml:mo>
<mml:munder>
<mml:mrow>
<mml:mstyle displaystyle="true">
<mml:mo largeop="true" movablelimits="false">∑</mml:mo></mml:mstyle>
</mml:mrow>
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">s</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">i</mml:mi>
</mml:mrow>
</mml:msub>
<mml:mo stretchy="false">∈</mml:mo>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">t</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">j</mml:mi>
</mml:mrow>
</mml:msub>
</mml:mrow>
</mml:munder>
<mml:mi mathvariant="italic">f</mml:mi>
<mml:mo mathvariant="normal" fence="true" stretchy="false">(</mml:mo>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">s</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">i</mml:mi>
</mml:mrow>
</mml:msub>
<mml:mo mathvariant="normal" fence="true" stretchy="false">)</mml:mo>
<mml:mo>.</mml:mo>
</mml:mtd>
</mml:mtr>
</mml:mtable></mml:math><tex-math><![CDATA[\[ \delta ({t_{j}})=\sum \limits_{{s_{i}}\in {t_{j}}}f({s_{i}}).\]]]></tex-math></alternatives>
</disp-formula>
</p></statement>
<p>After getting the section preference and trajectory preference list according to equation (<xref rid="j_infor585_eq_007">7</xref>) and equation (<xref rid="j_infor585_eq_008">8</xref>) respectively, TREDP could recommend personalized traffic trajectories to drivers.</p>
</sec>
<sec id="j_infor585_s_012">
<label>4.5</label>
<title>Algorithm</title>
<p>Algorithm <xref rid="j_infor585_fig_004">1</xref> takes driver-car-road requirements (<inline-formula id="j_infor585_ineq_108"><alternatives><mml:math>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">r</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">d</mml:mi>
</mml:mrow>
</mml:msub>
<mml:mo mathvariant="normal">,</mml:mo>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">g</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">c</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">d</mml:mi>
</mml:mrow>
</mml:msub>
</mml:mrow>
</mml:msub>
<mml:mo mathvariant="normal">,</mml:mo>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">g</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">S</mml:mi>
</mml:mrow>
</mml:msub></mml:math><tex-math><![CDATA[${r_{d}},{g_{{c_{d}}}},{g_{S}}$]]></tex-math></alternatives></inline-formula>), a set of historical trajectories <italic>T</italic> and a set of drivers <italic>D</italic> as input. Meanwhile, it takes a recommended trajectory <inline-formula id="j_infor585_ineq_109"><alternatives><mml:math>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">T</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">d</mml:mi>
</mml:mrow>
</mml:msub></mml:math><tex-math><![CDATA[${T_{d}}$]]></tex-math></alternatives></inline-formula> for driver <italic>d</italic> as output.</p>
<fig id="j_infor585_fig_004">
<label>Algorithm 1</label>
<caption>
<p>TREDP</p>
</caption>
<graphic xlink:href="infor585_g004.jpg"/>
</fig>
<p>First, Algorithm <xref rid="j_infor585_fig_004">1</xref> calculates the importance of road section <inline-formula id="j_infor585_ineq_110"><alternatives><mml:math>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">s</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">i</mml:mi>
</mml:mrow>
</mml:msub></mml:math><tex-math><![CDATA[${s_{i}}$]]></tex-math></alternatives></inline-formula> as equation (<xref rid="j_infor585_eq_001">1</xref>) (Steps 2–7). Second, it generates the section preference of <inline-formula id="j_infor585_ineq_111"><alternatives><mml:math>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">s</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">i</mml:mi>
</mml:mrow>
</mml:msub></mml:math><tex-math><![CDATA[${s_{i}}$]]></tex-math></alternatives></inline-formula> as equation (<xref rid="j_infor585_eq_007">7</xref>) (Steps 8–19). Third, it computes driver <italic>d</italic>’s driver-car-road preferences for traffic trajectory <inline-formula id="j_infor585_ineq_112"><alternatives><mml:math>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">t</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">j</mml:mi>
</mml:mrow>
</mml:msub></mml:math><tex-math><![CDATA[${t_{j}}$]]></tex-math></alternatives></inline-formula> (i.e. <inline-formula id="j_infor585_ineq_113"><alternatives><mml:math>
<mml:mi mathvariant="italic">δ</mml:mi>
<mml:mo mathvariant="normal" fence="true" stretchy="false">(</mml:mo>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">t</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">j</mml:mi>
</mml:mrow>
</mml:msub>
<mml:mo mathvariant="normal" fence="true" stretchy="false">)</mml:mo></mml:math><tex-math><![CDATA[$\delta ({t_{j}})$]]></tex-math></alternatives></inline-formula>) (Steps 22–25). Fourth, if road section <inline-formula id="j_infor585_ineq_114"><alternatives><mml:math>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">s</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">i</mml:mi>
</mml:mrow>
</mml:msub></mml:math><tex-math><![CDATA[${s_{i}}$]]></tex-math></alternatives></inline-formula> satisfies the following three conditions, <inline-formula id="j_infor585_ineq_115"><alternatives><mml:math>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">t</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">j</mml:mi>
</mml:mrow>
</mml:msub></mml:math><tex-math><![CDATA[${t_{j}}$]]></tex-math></alternatives></inline-formula> is the best trajectory for driver <italic>d</italic> (Steps 28–31). (1) <inline-formula id="j_infor585_ineq_116"><alternatives><mml:math>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">s</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">i</mml:mi>
</mml:mrow>
</mml:msub></mml:math><tex-math><![CDATA[${s_{i}}$]]></tex-math></alternatives></inline-formula> is closest to beginning point <inline-formula id="j_infor585_ineq_117"><alternatives><mml:math>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">b</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">d</mml:mi>
</mml:mrow>
</mml:msub></mml:math><tex-math><![CDATA[${b_{d}}$]]></tex-math></alternatives></inline-formula> (Step 28). (2) The section preference of <inline-formula id="j_infor585_ineq_118"><alternatives><mml:math>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">s</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">i</mml:mi>
</mml:mrow>
</mml:msub></mml:math><tex-math><![CDATA[${s_{i}}$]]></tex-math></alternatives></inline-formula> is the maximum value among all road sections that are closest to <inline-formula id="j_infor585_ineq_119"><alternatives><mml:math>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">b</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">d</mml:mi>
</mml:mrow>
</mml:msub></mml:math><tex-math><![CDATA[${b_{d}}$]]></tex-math></alternatives></inline-formula> (Step 28). (3) The trajectory preference of <inline-formula id="j_infor585_ineq_120"><alternatives><mml:math>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">t</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">j</mml:mi>
</mml:mrow>
</mml:msub></mml:math><tex-math><![CDATA[${t_{j}}$]]></tex-math></alternatives></inline-formula> containing <inline-formula id="j_infor585_ineq_121"><alternatives><mml:math>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">s</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">i</mml:mi>
</mml:mrow>
</mml:msub></mml:math><tex-math><![CDATA[${s_{i}}$]]></tex-math></alternatives></inline-formula> is the maximum value among all trajectories (Step 29). Otherwise, we could only recommend to driver <italic>d</italic> one section (i.e. <inline-formula id="j_infor585_ineq_122"><alternatives><mml:math>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">s</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">i</mml:mi>
</mml:mrow>
</mml:msub></mml:math><tex-math><![CDATA[${s_{i}}$]]></tex-math></alternatives></inline-formula>) step by step by iteratively calling Algorithm <xref rid="j_infor585_fig_004">1</xref> with new <inline-formula id="j_infor585_ineq_123"><alternatives><mml:math>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">r</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">d</mml:mi>
</mml:mrow>
</mml:msub>
<mml:mo mathvariant="normal">,</mml:mo>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">g</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">c</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">d</mml:mi>
</mml:mrow>
</mml:msub>
</mml:mrow>
</mml:msub>
<mml:mo mathvariant="normal">,</mml:mo>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">g</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">S</mml:mi>
</mml:mrow>
</mml:msub>
<mml:mo mathvariant="normal">,</mml:mo>
<mml:mi mathvariant="italic">T</mml:mi></mml:math><tex-math><![CDATA[${r_{d}},{g_{{c_{d}}}},{g_{S}},T$]]></tex-math></alternatives></inline-formula> and <italic>D</italic> (Steps 32–37).</p>
<p>Actually, Algorithm <xref rid="j_infor585_fig_004">1</xref> can serve a group of drivers with the same beginning/ending point at the same time. And it could be naturally extended for serving various drivers with random beginning/ending points. The scheme proposed in this paper has a high requirement for data updates, and only the preferred trajectories calculated according to the latest data could provide drivers with timely recommendation services. Therefore, our framework and scheme are integrated to provide drivers with intelligent transportation services. The continuous iteration of the framework could bring timely data updates to the scheme and real-time personalized services to the driver.</p>
</sec>
</sec>
<sec id="j_infor585_s_013">
<label>5</label>
<title>Experimental Analysis</title>
<sec id="j_infor585_s_014">
<label>5.1</label>
<title>Experimental Setup</title>
<p>We first establish our experiments from the following three aspects.</p>
<p><bold>Dataset.</bold> The experimental dataset used in our experiments is the actual trajectory data of taxis in Shanghai, China during a certain period of time. This dataset uses GPS to record the longitude, dimension, direction, and passenger information of taxis at regular intervals. This dataset contains 4316 taxi drivers, each recording approximately 1800 records, totaling approximately 7.8 million records.</p>
<p><bold>Experimental environment.</bold> Table <xref rid="j_infor585_tab_002">2</xref> shows the experimental environment.</p>
<p><bold>Compared method.</bold> ASER (Qu <italic>et al.</italic>, <xref ref-type="bibr" rid="j_infor585_ref_023">2019</xref>) is a traffic trajectory recommendation model based on trajectory similarity. As ASER is most relevant to our scheme, we compare our scheme TREDP with ASER in recommended accuracy and computational efficiency.</p>
<table-wrap id="j_infor585_tab_002">
<label>Table 2</label>
<caption>
<p>Hardware parameters.</p>
</caption>
<table>
<thead>
<tr>
<td style="vertical-align: top; text-align: left; border-top: solid thin; border-bottom: solid thin">Device</td>
<td style="vertical-align: top; text-align: left; border-top: solid thin; border-bottom: solid thin">Cloud</td>
<td style="vertical-align: top; text-align: left; border-top: solid thin; border-bottom: solid thin">Edge</td>
</tr>
</thead>
<tbody>
<tr>
<td style="vertical-align: top; text-align: left">Core frequency</td>
<td style="vertical-align: top; text-align: left">3.2 GHz</td>
<td style="vertical-align: top; text-align: left">2.2 GHz</td>
</tr>
<tr>
<td style="vertical-align: top; text-align: left">RAM</td>
<td style="vertical-align: top; text-align: left">32 GB</td>
<td style="vertical-align: top; text-align: left">4 GB</td>
</tr>
<tr>
<td style="vertical-align: top; text-align: left; border-bottom: solid thin">Cores</td>
<td style="vertical-align: top; text-align: left; border-bottom: solid thin">8</td>
<td style="vertical-align: top; text-align: left; border-bottom: solid thin">2</td>
</tr>
</tbody>
</table>
</table-wrap>
</sec>
<sec id="j_infor585_s_015">
<label>5.2</label>
<title>Recommended Accuracy</title>
<p>The dataset is divided into two parts in chronological order, with 70% of the older data used for data analysis and the remaining newer data used for verifying recommended accuracy. When the recommended trajectory is consistent with the actual trajectory, the recommendation is accurate. The calculation method is shown in equation (<xref rid="j_infor585_eq_009">9</xref>), where <italic>T</italic> denotes a set of trajectories with the same beginning and ending point, <inline-formula id="j_infor585_ineq_124"><alternatives><mml:math><mml:mover accent="true">
<mml:mrow>
<mml:mi mathvariant="italic">T</mml:mi>
</mml:mrow>
<mml:mo stretchy="true">˜</mml:mo></mml:mover></mml:math><tex-math><![CDATA[$\widetilde{T}$]]></tex-math></alternatives></inline-formula> denotes all trajectories with different beginning and ending points in the system, <inline-formula id="j_infor585_ineq_125"><alternatives><mml:math>
<mml:msubsup>
<mml:mrow>
<mml:mi mathvariant="italic">t</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">d</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">i</mml:mi>
</mml:mrow>
</mml:msub>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">A</mml:mi>
</mml:mrow>
</mml:msubsup></mml:math><tex-math><![CDATA[${t_{{d_{i}}}^{A}}$]]></tex-math></alternatives></inline-formula> denotes the number of actual trajectories (based on the newer data) of driver <inline-formula id="j_infor585_ineq_126"><alternatives><mml:math>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">d</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">i</mml:mi>
</mml:mrow>
</mml:msub></mml:math><tex-math><![CDATA[${d_{i}}$]]></tex-math></alternatives></inline-formula> in <italic>T</italic>, <inline-formula id="j_infor585_ineq_127"><alternatives><mml:math>
<mml:msubsup>
<mml:mrow>
<mml:mi mathvariant="italic">t</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">d</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">i</mml:mi>
</mml:mrow>
</mml:msub>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">R</mml:mi>
</mml:mrow>
</mml:msubsup></mml:math><tex-math><![CDATA[${t_{{d_{i}}}^{R}}$]]></tex-math></alternatives></inline-formula> denotes the number of the recommended trajectories (based on the older data) that are the same as the actual trajectories for driver <inline-formula id="j_infor585_ineq_128"><alternatives><mml:math>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">d</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">i</mml:mi>
</mml:mrow>
</mml:msub></mml:math><tex-math><![CDATA[${d_{i}}$]]></tex-math></alternatives></inline-formula> in <italic>T</italic>, <inline-formula id="j_infor585_ineq_129"><alternatives><mml:math>
<mml:mo stretchy="false">|</mml:mo>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">D</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">T</mml:mi>
</mml:mrow>
</mml:msub>
<mml:mo stretchy="false">|</mml:mo></mml:math><tex-math><![CDATA[$|{D_{T}}|$]]></tex-math></alternatives></inline-formula> denotes the set of drivers in <italic>T</italic>, and <inline-formula id="j_infor585_ineq_130"><alternatives><mml:math>
<mml:mtext mathvariant="italic">Average</mml:mtext>
<mml:mo maxsize="1.19em" minsize="1.19em" fence="true" mathvariant="normal">(</mml:mo>
<mml:msubsup>
<mml:mrow>
<mml:mo largeop="false" movablelimits="false">∑</mml:mo>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">i</mml:mi>
<mml:mo>=</mml:mo>
<mml:mn>1</mml:mn>
</mml:mrow>
<mml:mrow>
<mml:mo stretchy="false">|</mml:mo>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">D</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">T</mml:mi>
</mml:mrow>
</mml:msub>
<mml:mo stretchy="false">|</mml:mo>
</mml:mrow>
</mml:msubsup><mml:mstyle displaystyle="false">
<mml:mfrac>
<mml:mrow>
<mml:msubsup>
<mml:mrow>
<mml:mi mathvariant="italic">t</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">d</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">i</mml:mi>
</mml:mrow>
</mml:msub>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">R</mml:mi>
</mml:mrow>
</mml:msubsup>
</mml:mrow>
<mml:mrow>
<mml:msubsup>
<mml:mrow>
<mml:mi mathvariant="italic">t</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">d</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">i</mml:mi>
</mml:mrow>
</mml:msub>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">A</mml:mi>
</mml:mrow>
</mml:msubsup>
</mml:mrow>
</mml:mfrac>
</mml:mstyle>
<mml:mo maxsize="1.19em" minsize="1.19em" fence="true" mathvariant="normal">)</mml:mo></mml:math><tex-math><![CDATA[$\textit{Average}\big({\textstyle\sum _{i=1}^{|{D_{T}}|}}\frac{{t_{{d_{i}}}^{R}}}{{t_{{d_{i}}}^{A}}}\big)$]]></tex-math></alternatives></inline-formula> represents the average recommended accuracy of trajectory <italic>T</italic>. 
<disp-formula id="j_infor585_eq_009">
<label>(9)</label><alternatives><mml:math display="block">
<mml:mtable displaystyle="true">
<mml:mtr>
<mml:mtd>
<mml:mtext mathvariant="italic">Accuracy</mml:mtext>
<mml:mo>=</mml:mo>
<mml:mtext mathvariant="italic">Average</mml:mtext>
<mml:mo mathvariant="normal" fence="true" maxsize="2.45em" minsize="2.45em">(</mml:mo>
<mml:munder>
<mml:mrow>
<mml:mstyle displaystyle="true">
<mml:mo largeop="true" movablelimits="false">∑</mml:mo></mml:mstyle>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">T</mml:mi>
<mml:mo stretchy="false">∈</mml:mo><mml:mover accent="true">
<mml:mrow>
<mml:mi mathvariant="italic">T</mml:mi>
</mml:mrow>
<mml:mo stretchy="true">˜</mml:mo></mml:mover>
</mml:mrow>
</mml:munder>
<mml:mtext mathvariant="italic">Average</mml:mtext>
<mml:mo mathvariant="normal" fence="true" maxsize="2.45em" minsize="2.45em">(</mml:mo>
<mml:munderover accentunder="false" accent="false">
<mml:mrow>
<mml:mstyle displaystyle="true">
<mml:mo largeop="true" movablelimits="false">∑</mml:mo></mml:mstyle>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">i</mml:mi>
<mml:mo>=</mml:mo>
<mml:mn>1</mml:mn>
</mml:mrow>
<mml:mrow>
<mml:mo stretchy="false">|</mml:mo>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">D</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">T</mml:mi>
</mml:mrow>
</mml:msub>
<mml:mo stretchy="false">|</mml:mo>
</mml:mrow>
</mml:munderover><mml:mstyle displaystyle="true">
<mml:mfrac>
<mml:mrow>
<mml:msubsup>
<mml:mrow>
<mml:mi mathvariant="italic">t</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">d</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">i</mml:mi>
</mml:mrow>
</mml:msub>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">R</mml:mi>
</mml:mrow>
</mml:msubsup>
</mml:mrow>
<mml:mrow>
<mml:msubsup>
<mml:mrow>
<mml:mi mathvariant="italic">t</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mi mathvariant="italic">d</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">i</mml:mi>
</mml:mrow>
</mml:msub>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">A</mml:mi>
</mml:mrow>
</mml:msubsup>
</mml:mrow>
</mml:mfrac>
</mml:mstyle>
<mml:mo mathvariant="normal" fence="true" maxsize="2.45em" minsize="2.45em">)</mml:mo>
<mml:mo mathvariant="normal" fence="true" maxsize="2.45em" minsize="2.45em">)</mml:mo>
<mml:mo>.</mml:mo>
</mml:mtd>
</mml:mtr>
</mml:mtable></mml:math><tex-math><![CDATA[\[ \textit{Accuracy}=\textit{Average}\Bigg(\sum \limits_{T\in \widetilde{T}}\textit{Average}\Bigg({\sum \limits_{i=1}^{|{D_{T}}|}}\frac{{t_{{d_{i}}}^{R}}}{{t_{{d_{i}}}^{A}}}\Bigg)\Bigg).\]]]></tex-math></alternatives>
</disp-formula>
</p>
<fig id="j_infor585_fig_005">
<label>Fig. 4</label>
<caption>
<p>Comparison of the recommended accuracy with the change of <inline-formula id="j_infor585_ineq_131"><alternatives><mml:math>
<mml:mo stretchy="false">|</mml:mo>
<mml:mi mathvariant="italic">S</mml:mi>
<mml:mo stretchy="false">|</mml:mo></mml:math><tex-math><![CDATA[$|S|$]]></tex-math></alternatives></inline-formula> and <inline-formula id="j_infor585_ineq_132"><alternatives><mml:math>
<mml:mo stretchy="false">|</mml:mo>
<mml:mi mathvariant="italic">T</mml:mi>
<mml:mo stretchy="false">|</mml:mo></mml:math><tex-math><![CDATA[$|T|$]]></tex-math></alternatives></inline-formula>.</p>
</caption>
<graphic xlink:href="infor585_g005.jpg"/>
</fig>
<p>Experimental comparison results are shown in Fig. <xref rid="j_infor585_fig_005">4</xref>, where <inline-formula id="j_infor585_ineq_133"><alternatives><mml:math>
<mml:mo stretchy="false">|</mml:mo>
<mml:mi mathvariant="italic">S</mml:mi>
<mml:mo stretchy="false">|</mml:mo></mml:math><tex-math><![CDATA[$|S|$]]></tex-math></alternatives></inline-formula> denotes the number of road sections that need to be considered in personalized traffic trajectory recommendation.</p>
<p>As shown in Fig. <xref rid="j_infor585_fig_005">4</xref>, as more road sections <inline-formula id="j_infor585_ineq_134"><alternatives><mml:math>
<mml:mo stretchy="false">|</mml:mo>
<mml:mi mathvariant="italic">S</mml:mi>
<mml:mo stretchy="false">|</mml:mo></mml:math><tex-math><![CDATA[$|S|$]]></tex-math></alternatives></inline-formula> are considered by the personalized trajectory recommendation algorithm, the accuracy rate of trajectory recommendation is slightly decreasing. In addition, the preferred trajectories recommended by TREDP are mainly concentrated in the Top-30 part of the trajectory preference list. At the same time, when the number of <inline-formula id="j_infor585_ineq_135"><alternatives><mml:math>
<mml:mo stretchy="false">|</mml:mo>
<mml:mi mathvariant="italic">S</mml:mi>
<mml:mo stretchy="false">|</mml:mo></mml:math><tex-math><![CDATA[$|S|$]]></tex-math></alternatives></inline-formula> exceeds 25, TREDP has a 95% recommended accuracy. This proves the effectiveness of TREDP in intelligent traffic trajectory recommendation.</p>
<p>The number of road sections included in the trajectories gradually increases with the total number of trajectories <inline-formula id="j_infor585_ineq_136"><alternatives><mml:math>
<mml:mo stretchy="false">|</mml:mo>
<mml:mi mathvariant="italic">T</mml:mi>
<mml:mo stretchy="false">|</mml:mo></mml:math><tex-math><![CDATA[$|T|$]]></tex-math></alternatives></inline-formula> increases. This brings some challenges to TREDP and ASER, but they still maintain a good recommendation effect in Fig. <xref rid="j_infor585_fig_005">4</xref>. Moreover, TREDP has higher recommended accuracy than ASER method because it takes into account the driver-car-road preferences for numerous practical application requirements and scenarios.</p>
<fig id="j_infor585_fig_006">
<label>Fig. 5</label>
<caption>
<p>Comparison of the recommended accuracy with the change of <inline-formula id="j_infor585_ineq_137"><alternatives><mml:math>
<mml:mo stretchy="false">|</mml:mo>
<mml:mi mathvariant="italic">D</mml:mi>
<mml:mo stretchy="false">|</mml:mo></mml:math><tex-math><![CDATA[$|D|$]]></tex-math></alternatives></inline-formula>.</p>
</caption>
<graphic xlink:href="infor585_g006.jpg"/>
</fig>
<fig id="j_infor585_fig_007">
<label>Fig. 6</label>
<caption>
<p>Comparison of the computational efficiency with the change of <inline-formula id="j_infor585_ineq_138"><alternatives><mml:math>
<mml:mo stretchy="false">|</mml:mo>
<mml:mi mathvariant="italic">T</mml:mi>
<mml:mo stretchy="false">|</mml:mo></mml:math><tex-math><![CDATA[$|T|$]]></tex-math></alternatives></inline-formula>, <inline-formula id="j_infor585_ineq_139"><alternatives><mml:math>
<mml:mo stretchy="false">|</mml:mo>
<mml:mi mathvariant="italic">S</mml:mi>
<mml:mo stretchy="false">|</mml:mo></mml:math><tex-math><![CDATA[$|S|$]]></tex-math></alternatives></inline-formula> and <inline-formula id="j_infor585_ineq_140"><alternatives><mml:math>
<mml:mo stretchy="false">|</mml:mo>
<mml:mi mathvariant="italic">D</mml:mi>
<mml:mo stretchy="false">|</mml:mo></mml:math><tex-math><![CDATA[$|D|$]]></tex-math></alternatives></inline-formula>.</p>
</caption>
<graphic xlink:href="infor585_g007.jpg"/>
</fig>
<p>Figure <xref rid="j_infor585_fig_006">5</xref> shows the comparison of the recommended accuracy with the change of driver number <inline-formula id="j_infor585_ineq_141"><alternatives><mml:math>
<mml:mo stretchy="false">|</mml:mo>
<mml:mi mathvariant="italic">D</mml:mi>
<mml:mo stretchy="false">|</mml:mo></mml:math><tex-math><![CDATA[$|D|$]]></tex-math></alternatives></inline-formula>. When the number of drivers increases, the recommended accuracy of both TREDP and ASER decreases. This is because as <inline-formula id="j_infor585_ineq_142"><alternatives><mml:math>
<mml:mo stretchy="false">|</mml:mo>
<mml:mi mathvariant="italic">D</mml:mi>
<mml:mo stretchy="false">|</mml:mo></mml:math><tex-math><![CDATA[$|D|$]]></tex-math></alternatives></inline-formula> increases, a large number of drivers may result in game playing and interference among them. For example, a traffic-free road section may become less traffic-free after being recommended to many drivers, and the probability of this road section being recommended may decrease. The interference makes it more difficult for TREDP and ASER to determine the driver’s preferred trajectory. Meanwhile, TREDP considers the real-time relationship among driver-car-road, thus TREDP has better recommended accuracy than ASER.</p>
</sec>
<sec id="j_infor585_s_016">
<label>5.3</label>
<title>Computational Efficiency</title>
<p>Our computational overhead includes all computing and communication time for ASER and TREDP. The experimental results are shown in Fig. <xref rid="j_infor585_fig_007">6</xref>, where the X-axes denote <inline-formula id="j_infor585_ineq_143"><alternatives><mml:math>
<mml:mo stretchy="false">|</mml:mo>
<mml:mi mathvariant="italic">T</mml:mi>
<mml:mo stretchy="false">|</mml:mo></mml:math><tex-math><![CDATA[$|T|$]]></tex-math></alternatives></inline-formula>, <inline-formula id="j_infor585_ineq_144"><alternatives><mml:math>
<mml:mo stretchy="false">|</mml:mo>
<mml:mi mathvariant="italic">S</mml:mi>
<mml:mo stretchy="false">|</mml:mo></mml:math><tex-math><![CDATA[$|S|$]]></tex-math></alternatives></inline-formula> and <inline-formula id="j_infor585_ineq_145"><alternatives><mml:math>
<mml:mo stretchy="false">|</mml:mo>
<mml:mi mathvariant="italic">D</mml:mi>
<mml:mo stretchy="false">|</mml:mo></mml:math><tex-math><![CDATA[$|D|$]]></tex-math></alternatives></inline-formula> respectively, and Y-axes denote running time whose unit is millisecond (ms).</p>
<p>All calculations of ASER are on the edge. TREDP combines the computing resources of both edge and cloud. Even TREDP consumes the communication cost of edge-cloud, it still significantly reduces the computational overhead based on edge-cloud computing. Therefore, our scheme TREDP consumes less time than ASER in Fig. <xref rid="j_infor585_fig_007">6</xref>. This shows that our scheme is more suitable for large-scale traffic data. Meanwhile, rapid analysis can provide drivers with trajectory recommendation services in a more timely manner.</p>
</sec>
</sec>
<sec id="j_infor585_s_017">
<label>6</label>
<title>Conclusion</title>
<p>The trajectory recommendation in intelligent transportation systems has broad application value. This paper first proposes an edge-cloud computing traffic trajectory recommendation framework to update data and iterate services. We then propose a traffic trajectory recommendation scheme based on edge-cloud computing driver-car-road preferences for improving driver satisfaction when using the system based on the framework. The data analysed by this scheme is divided into two types. The first type is historical trajectory data analysed by the cloud, and the other type considers driver-car-road real-time requirements analysed by the edge. By edge-cloud collaborative computing of these two types of data, we provide drivers with timely and accurate trajectory recommendation services. Extensive experiments validate the effectiveness of our scheme and framework. Especially when facing a sharp increase in data, our scheme still has stable, accurate and efficient recommendation performance.</p>
<p>In the future, we plan to extend the scheme to more application scenarios and plan to introduce tensor algebra to consider more high-dimensional information, in order to further improve recommended accuracy.</p>
</sec>
</body>
<back>
<ref-list id="j_infor585_reflist_001">
<title>References</title>
<ref id="j_infor585_ref_001">
<mixed-citation publication-type="journal"><string-name><surname>bin Zulkiflee</surname>, <given-names>I.</given-names></string-name>, <string-name><surname>Haw</surname>, <given-names>S.-C.</given-names></string-name>, <string-name><surname>Palanichamy</surname>, <given-names>N.</given-names></string-name>, <string-name><surname>Yeoh</surname>, <given-names>E.-T.</given-names></string-name>, <string-name><surname>Tong</surname>, <given-names>Y.-C.</given-names></string-name> (<year>2024</year>). <article-title>Customer relationship management dashboard with descriptive analytics for effective recommendation</article-title>. <source>Journal of Logistics, Informatics and Service Science</source>, <volume>11</volume>(<issue>2</issue>), <fpage>301</fpage>–<lpage>323</lpage>.</mixed-citation>
</ref>
<ref id="j_infor585_ref_002">
<mixed-citation publication-type="journal"><string-name><surname>Cao</surname>, <given-names>J.</given-names></string-name>, <string-name><surname>Tao</surname>, <given-names>C.</given-names></string-name>, <string-name><surname>Zhang</surname>, <given-names>Z.</given-names></string-name>, <string-name><surname>Gao</surname>, <given-names>Z.</given-names></string-name>, <string-name><surname>Luo</surname>, <given-names>X.</given-names></string-name>, <string-name><surname>Zheng</surname>, <given-names>S.</given-names></string-name>, <string-name><surname>Zhu</surname>, <given-names>Y.</given-names></string-name> (<year>2024</year>). <article-title>Accelerating point-voxel representation of 3D object detection for automatic driving</article-title>. <source>IEEE Transactions on Artificial Intelligence</source>, <volume>5</volume>(<issue>1</issue>), <fpage>254</fpage>–<lpage>266</lpage>.</mixed-citation>
</ref>
<ref id="j_infor585_ref_003">
<mixed-citation publication-type="journal"><string-name><surname>Cheng</surname>, <given-names>Y.</given-names></string-name>, <string-name><surname>Hu</surname>, <given-names>X.</given-names></string-name>, <string-name><surname>Chen</surname>, <given-names>K.</given-names></string-name>, <string-name><surname>Yu</surname>, <given-names>X.</given-names></string-name>, <string-name><surname>Luo</surname>, <given-names>Y.</given-names></string-name> (<year>2023</year>). <article-title>Online longitudinal trajectory planning for connected and autonomous vehicles in mixed traffic flow with deep reinforcement learning approach</article-title>. <source>Journal of Intelligent Transportation Systems</source>, <volume>27</volume>(<issue>3</issue>), <fpage>396</fpage>–<lpage>410</lpage>.</mixed-citation>
</ref>
<ref id="j_infor585_ref_004">
<mixed-citation publication-type="journal"><string-name><surname>Deng</surname>, <given-names>J.</given-names></string-name>, <string-name><surname>Li</surname>, <given-names>T.</given-names></string-name>, <string-name><surname>Yang</surname>, <given-names>Z.</given-names></string-name>, <string-name><surname>Yuan</surname>, <given-names>Q.</given-names></string-name>, <string-name><surname>Chen</surname>, <given-names>X.</given-names></string-name> (<year>2025</year>). <article-title>Heterogeneity in route choice during peak hours: implications on travel demand management</article-title>. <source>Travel Behaviour and Society</source>, <volume>38</volume>, <fpage>100922</fpage>.</mixed-citation>
</ref>
<ref id="j_infor585_ref_005">
<mixed-citation publication-type="journal"><string-name><surname>Dudakli</surname>, <given-names>N.</given-names></string-name>, <string-name><surname>Baykasoğlu</surname>, <given-names>A.</given-names></string-name> (<year>2024</year>). <article-title>Performance evaluation of different dispatching rules and heuristics in a fully automated parking system</article-title>. <source>Informatica</source>, <volume>35</volume>(<issue>1</issue>), <fpage>99</fpage>–<lpage>129</lpage>.</mixed-citation>
</ref>
<ref id="j_infor585_ref_006">
<mixed-citation publication-type="journal"><string-name><surname>Guo</surname>, <given-names>S.</given-names></string-name>, <string-name><surname>Liao</surname>, <given-names>X.</given-names></string-name>, <string-name><surname>Meng</surname>, <given-names>F.</given-names></string-name>, <string-name><surname>Zhao</surname>, <given-names>Q.</given-names></string-name>, <string-name><surname>Tang</surname>, <given-names>Y.</given-names></string-name>, <string-name><surname>Li</surname>, <given-names>H.</given-names></string-name>, <string-name><surname>Zong</surname>, <given-names>Q.</given-names></string-name> (<year>2024</year>). <article-title>FSASA: sequential recommendation based on fusing session-aware models and self-attention networks</article-title>. <source>Computer Science and Information Systems</source>, <volume>21</volume>(<issue>1</issue>), <fpage>1</fpage>–<lpage>20</lpage>.</mixed-citation>
</ref>
<ref id="j_infor585_ref_007">
<mixed-citation publication-type="journal"><string-name><surname>Jaurker</surname>, <given-names>D.</given-names></string-name>, <string-name><surname>Pradhan</surname>, <given-names>M.K.</given-names></string-name> (<year>2023</year>). <article-title>Finite element modelling for electrical discharge machining of Ti-6Al-4V alloy and multi-objective optimisation using response surface modelling</article-title>. <source>International Journal of Simulation and Process Modelling</source>, <volume>20</volume>(<issue>1</issue>), <fpage>21</fpage>–<lpage>30</lpage>.</mixed-citation>
</ref>
<ref id="j_infor585_ref_008">
<mixed-citation publication-type="journal"><string-name><surname>Jian</surname>, <given-names>L.</given-names></string-name>, <string-name><surname>Jie</surname>, <given-names>L.</given-names></string-name>, <string-name><surname>Hongji</surname>, <given-names>F.</given-names></string-name>, <string-name><surname>Jiang</surname>, <given-names>J.</given-names></string-name> (<year>2024</year>). <article-title>Dynamic energy-efficient path planning for electric vehicles using an enhanced ant colony algorithm</article-title>. <source>Technical Gazette/Tehnički Vjesnik</source>, <volume>31</volume>(<issue>2</issue>), <fpage>434</fpage>–<lpage>441</lpage>.</mixed-citation>
</ref>
<ref id="j_infor585_ref_009">
<mixed-citation publication-type="journal"><string-name><surname>Jiang</surname>, <given-names>Y.</given-names></string-name>, <string-name><surname>Man</surname>, <given-names>Z.</given-names></string-name>, <string-name><surname>Wang</surname>, <given-names>Y.</given-names></string-name>, <string-name><surname>Yao</surname>, <given-names>Z.</given-names></string-name> (<year>2024</year>). <article-title>Cooperative lane-changing for connected autonomous vehicles merging into dedicated lanes in mixed traffic flow</article-title>. <source>Expert Systems with Applications</source>, <volume>252</volume>, <elocation-id>124163</elocation-id>.</mixed-citation>
</ref>
<ref id="j_infor585_ref_010">
<mixed-citation publication-type="journal"><string-name><surname>Jin</surname>, <given-names>X.</given-names></string-name>, <string-name><surname>Choi</surname>, <given-names>Y.-S.</given-names></string-name> (<year>2024</year>). <article-title>Coupling evaluation and spatial analysis of regional economy and logistics development based on digital twin</article-title>. <source>Journal of Logistics, Informatics and Service Science</source>, <volume>11</volume>(<issue>2</issue>), <fpage>10</fpage>–<lpage>26</lpage>.</mixed-citation>
</ref>
<ref id="j_infor585_ref_011">
<mixed-citation publication-type="journal"><string-name><surname>Kalaivani Jayaraman</surname>, <given-names>M.D.</given-names></string-name>, <string-name><surname>Malarvizhi</surname>, <given-names>C.A.N.</given-names></string-name> (<year>2024</year>). <article-title>Survey validation for the impact of environmental management systems on green innovation</article-title>. <source>Journal of System and Management Sciences</source>, <volume>14</volume>(<issue>5</issue>), <fpage>212</fpage>–<lpage>230</lpage>.</mixed-citation>
</ref>
<ref id="j_infor585_ref_012">
<mixed-citation publication-type="journal"><string-name><surname>Kurnianto</surname>, <given-names>D.D.</given-names></string-name>, <string-name><surname>Sfenrianto</surname></string-name> (<year>2024</year>). <article-title>Classification and recommendations for insurance products using Naïve Bayes classification based on customer data</article-title>. <source>Journal of System and Management Sciences</source>, <volume>14</volume>(<issue>6</issue>), <fpage>300</fpage>–<lpage>315</lpage>.</mixed-citation>
</ref>
<ref id="j_infor585_ref_013">
<mixed-citation publication-type="journal"><string-name><surname>Lai</surname>, <given-names>D.</given-names></string-name>, <string-name><surname>Qu</surname>, <given-names>J.</given-names></string-name>, <string-name><surname>Sang</surname>, <given-names>Y.</given-names></string-name>, <string-name><surname>Chen</surname>, <given-names>X.</given-names></string-name> (<year>2024</year>). <article-title>Transfer-learning-based representation learning for trajectory similarity search</article-title>. <source>GeoInformatica</source>, <volume>28</volume>, <fpage>631</fpage>–<lpage>648</lpage>.</mixed-citation>
</ref>
<ref id="j_infor585_ref_014">
<mixed-citation publication-type="journal"><string-name><surname>Lei</surname>, <given-names>D.</given-names></string-name>, <string-name><surname>Xu</surname>, <given-names>M.</given-names></string-name>, <string-name><surname>Wang</surname>, <given-names>S.</given-names></string-name> (<year>2025</year>). <article-title>A deep multimodal network for multi-task trajectory prediction</article-title>. <source>Information Fusion</source>, <volume>113</volume>, <elocation-id>102597</elocation-id>.</mixed-citation>
</ref>
<ref id="j_infor585_ref_015">
<mixed-citation publication-type="journal"><string-name><surname>Li</surname>, <given-names>J.</given-names></string-name>, <string-name><surname>Yu</surname>, <given-names>C.</given-names></string-name>, <string-name><surname>Shen</surname>, <given-names>Z.</given-names></string-name>, <string-name><surname>Su</surname>, <given-names>Z.</given-names></string-name>, <string-name><surname>Ma</surname>, <given-names>W.</given-names></string-name> (<year>2023</year>). <article-title>A survey on urban traffic control under mixed traffic environment with connected automated vehicles</article-title>. <source>Transportation Research Part C: Emerging Technologies</source>, <volume>154</volume>, <elocation-id>104258</elocation-id>.</mixed-citation>
</ref>
<ref id="j_infor585_ref_016">
<mixed-citation publication-type="journal"><string-name><surname>Li</surname>, <given-names>J.</given-names></string-name>, <string-name><surname>Zhang</surname>, <given-names>H.</given-names></string-name>, <string-name><surname>Liu</surname>, <given-names>H.</given-names></string-name>, <string-name><surname>Wang</surname>, <given-names>S.</given-names></string-name> (<year>2024</year>). <article-title>Multi-objective planning of commuter carpooling under time-varying road network</article-title>. <source>Sustainability</source>, <volume>16</volume>(<issue>2</issue>), <fpage>647</fpage>.</mixed-citation>
</ref>
<ref id="j_infor585_ref_017">
<mixed-citation publication-type="journal"><string-name><surname>Lim</surname>, <given-names>W.</given-names></string-name>, <string-name><surname>Lee</surname>, <given-names>S.</given-names></string-name>, <string-name><surname>Sunwoo</surname>, <given-names>M.</given-names></string-name>, <string-name><surname>Jo</surname>, <given-names>K.</given-names></string-name> (<year>2021</year>). <article-title>Hybrid trajectory planning for autonomous driving in on-road dynamic scenarios</article-title>. <source>IEEE Transactions on Intelligent Transportation Systems</source>, <volume>22</volume>(<issue>1</issue>), <fpage>341</fpage>–<lpage>355</lpage>.</mixed-citation>
</ref>
<ref id="j_infor585_ref_018">
<mixed-citation publication-type="journal"><string-name><surname>Liu</surname>, <given-names>M.</given-names></string-name>, <string-name><surname>Liu</surname>, <given-names>G.</given-names></string-name>, <string-name><surname>Sun</surname>, <given-names>L.</given-names></string-name> (<year>2023</year>). <article-title>Spatial-temporal dependence and similarity aware traffic flow forecasting</article-title>. <source>Information Sciences</source>, <volume>625</volume>, <fpage>81</fpage>–<lpage>96</lpage>.</mixed-citation>
</ref>
<ref id="j_infor585_ref_019">
<mixed-citation publication-type="journal"><string-name><surname>Liu</surname>, <given-names>M.</given-names></string-name>, <string-name><surname>Yazdanpanah</surname>, <given-names>V.</given-names></string-name>, <string-name><surname>Stein</surname>, <given-names>S.</given-names></string-name>, <string-name><surname>Gerding</surname>, <given-names>E.</given-names></string-name> (<year>2024</year>). <article-title>Sustainability-oriented route generation for ridesharing services</article-title>. <source>Computer Science and Information Systems</source>, <volume>21</volume>(<issue>1</issue>), <fpage>309</fpage>–<lpage>333</lpage>.</mixed-citation>
</ref>
<ref id="j_infor585_ref_020">
<mixed-citation publication-type="journal"><string-name><surname>Ning</surname>, <given-names>X.</given-names></string-name>, <string-name><surname>Tian</surname>, <given-names>H.</given-names></string-name>, <string-name><surname>Lin</surname>, <given-names>Y.</given-names></string-name>, <string-name><surname>Yao</surname>, <given-names>X.</given-names></string-name>, <string-name><surname>Hu</surname>, <given-names>F.</given-names></string-name>, <string-name><surname>Yin</surname>, <given-names>Y.</given-names></string-name> (<year>2024</year>). <article-title>Research on multi-objective optimization models for intersection crossing of connected autonomous vehicles with traffic signals</article-title>. <source>IEEE Access</source>, <volume>12</volume>, <fpage>36825</fpage>–<lpage>36840</lpage>.</mixed-citation>
</ref>
<ref id="j_infor585_ref_021">
<mixed-citation publication-type="journal"><string-name><surname>Nishida</surname>, <given-names>R.</given-names></string-name>, <string-name><surname>Tanigaki</surname>, <given-names>Y.</given-names></string-name>, <string-name><surname>Onishi</surname>, <given-names>M.</given-names></string-name>, <string-name><surname>Hashimoto</surname>, <given-names>K.</given-names></string-name> (<year>2024</year>). <article-title>Multi-objective deep reinforcement learning for crowd route guidance optimization</article-title>. <source>Transportation Research Record</source>, <volume>2678</volume>(<issue>5</issue>), <fpage>617</fpage>–<lpage>633</lpage>.</mixed-citation>
</ref>
<ref id="j_infor585_ref_022">
<mixed-citation publication-type="journal"><string-name><surname>Peng</surname>, <given-names>C.</given-names></string-name>, <string-name><surname>Wu</surname>, <given-names>Z.</given-names></string-name>, <string-name><surname>Huang</surname>, <given-names>X.</given-names></string-name>, <string-name><surname>Wu</surname>, <given-names>Y.</given-names></string-name>, <string-name><surname>Kang</surname>, <given-names>J.</given-names></string-name>, <string-name><surname>Huang</surname>, <given-names>Q.</given-names></string-name>, <string-name><surname>Xie</surname>, <given-names>S.</given-names></string-name> (<year>2024</year>). <article-title>Joint energy and completion time difference minimization for UAV-enabled intelligent transportation systems: a constrained multi-objective optimization approach</article-title>. <source>IEEE Transactions on Intelligent Transportation Systems</source>, <volume>25</volume>(<issue>10</issue>), <fpage>14040</fpage>–<lpage>14053</lpage>.</mixed-citation>
</ref>
<ref id="j_infor585_ref_023">
<mixed-citation publication-type="journal"><string-name><surname>Qu</surname>, <given-names>B.</given-names></string-name>, <string-name><surname>Yang</surname>, <given-names>W.</given-names></string-name>, <string-name><surname>Cui</surname>, <given-names>G.</given-names></string-name>, <string-name><surname>Wang</surname>, <given-names>X.</given-names></string-name> (<year>2019</year>). <article-title>Profitable taxi travel route recommendation based on big taxi trajectory data</article-title>. <source>IEEE Transactions on Intelligent Transportation Systems</source>, <volume>21</volume>(<issue>2</issue>), <fpage>653</fpage>–<lpage>668</lpage>.</mixed-citation>
</ref>
<ref id="j_infor585_ref_024">
<mixed-citation publication-type="journal"><string-name><surname>Wang</surname>, <given-names>Y.</given-names></string-name>, <string-name><surname>Li</surname>, <given-names>X.</given-names></string-name>, <string-name><surname>Yao</surname>, <given-names>H.</given-names></string-name> (<year>2019</year>). <article-title>Review of trajectory optimisation for connected automated vehicles</article-title>. <source>IET Intelligent Transport Systems</source>, <volume>13</volume>(<issue>4</issue>), <fpage>580</fpage>–<lpage>586</lpage>.</mixed-citation>
</ref>
<ref id="j_infor585_ref_025">
<mixed-citation publication-type="journal"><string-name><surname>Xiao</surname>, <given-names>M.</given-names></string-name>, <string-name><surname>Chen</surname>, <given-names>L.</given-names></string-name>, <string-name><surname>Feng</surname>, <given-names>H.</given-names></string-name>, <string-name><surname>Peng</surname>, <given-names>Z.</given-names></string-name>, <string-name><surname>Long</surname>, <given-names>Q.</given-names></string-name> (<year>2024</year>). <article-title>Sustainable and robust route planning scheme for smart city public transport based on multi-objective optimization: digital twin model</article-title>. <source>Sustainable Energy Technologies and Assessments</source>, <volume>65</volume>, <elocation-id>103787</elocation-id>.</mixed-citation>
</ref>
<ref id="j_infor585_ref_026">
<mixed-citation publication-type="journal"><string-name><surname>Xing</surname>, <given-names>Y.</given-names></string-name>, <string-name><surname>Hao</surname>, <given-names>Y.</given-names></string-name> (<year>2022</year>). <article-title>Research on travel time prediction of expressway in peak period based on Greenberg model</article-title>. <source>International Journal of Simulation and Process Modelling</source>, <volume>19</volume>(<issue>1–2</issue>), <fpage>54</fpage>–<lpage>61</lpage>.</mixed-citation>
</ref>
<ref id="j_infor585_ref_027">
<mixed-citation publication-type="journal"><string-name><surname>Yang</surname>, <given-names>X.T.</given-names></string-name>, <string-name><surname>Huang</surname>, <given-names>K.</given-names></string-name>, <string-name><surname>Zhang</surname>, <given-names>Z.</given-names></string-name>, <string-name><surname>Zhang</surname>, <given-names>Z.A.</given-names></string-name>, <string-name><surname>Lin</surname>, <given-names>F.</given-names></string-name> (<year>2021</year>). <article-title>Eco-driving system for connected automated vehicles: multi-objective trajectory optimization</article-title>. <source>IEEE Transactions on Intelligent Transportation Systems</source>, <volume>22</volume>(<issue>12</issue>), <fpage>7837</fpage>–<lpage>7849</lpage>.</mixed-citation>
</ref>
<ref id="j_infor585_ref_028">
<mixed-citation publication-type="journal"><string-name><surname>Yao</surname>, <given-names>Z.</given-names></string-name>, <string-name><surname>Liu</surname>, <given-names>M.</given-names></string-name>, <string-name><surname>Jiang</surname>, <given-names>Y.</given-names></string-name>, <string-name><surname>Tang</surname>, <given-names>Y.</given-names></string-name>, <string-name><surname>Ran</surname>, <given-names>B.</given-names></string-name> (<year>2024</year>). <article-title>Trajectory reconstruction for mixed traffic flow with regular, connected, and connected automated vehicles on freeway</article-title>. <source>IET Intelligent Transport Systems</source>, <volume>18</volume>(<issue>3</issue>), <fpage>450</fpage>–<lpage>466</lpage>.</mixed-citation>
</ref>
<ref id="j_infor585_ref_029">
<mixed-citation publication-type="journal"><string-name><surname>Yu</surname>, <given-names>X.</given-names></string-name>, <string-name><surname>Zhu</surname>, <given-names>S.</given-names></string-name>, <string-name><surname>Ren</surname>, <given-names>Y.</given-names></string-name> (<year>2023</year>). <article-title>Continuous trajectory similarity search with result diversification</article-title>. <source>Future Generation Computer Systems</source>, <volume>143</volume>, <fpage>392</fpage>–<lpage>400</lpage>.</mixed-citation>
</ref>
<ref id="j_infor585_ref_030">
<mixed-citation publication-type="journal"><string-name><surname>Zhang</surname>, <given-names>J.</given-names></string-name>, <string-name><surname>Chang</surname>, <given-names>C.</given-names></string-name>, <string-name><surname>He</surname>, <given-names>Z.</given-names></string-name>, <string-name><surname>Zhong</surname>, <given-names>W.</given-names></string-name>, <string-name><surname>Yao</surname>, <given-names>D.</given-names></string-name>, <string-name><surname>Li</surname>, <given-names>S.</given-names></string-name>, <string-name><surname>Li</surname>, <given-names>L.</given-names></string-name> (<year>2023</year>). <article-title>CAVSim: a microscopic traffic simulator for evaluation of connected and automated vehicles</article-title>. <source>IEEE Transactions on Intelligent Transportation Systems</source>, <volume>24</volume>(<issue>9</issue>), <fpage>10038</fpage>–<lpage>10054</lpage>.</mixed-citation>
</ref>
<ref id="j_infor585_ref_031">
<mixed-citation publication-type="journal"><string-name><surname>Zhao</surname>, <given-names>C.</given-names></string-name>, <string-name><surname>Yu</surname>, <given-names>H.</given-names></string-name>, <string-name><surname>Molnar</surname>, <given-names>T.G.</given-names></string-name> (<year>2023</year>). <article-title>Safety-critical traffic control by connected automated vehicles</article-title>. <source>Transportation Research Part C: Emerging Technologies</source>, <volume>154</volume>, <elocation-id>104230</elocation-id>.</mixed-citation>
</ref>
<ref id="j_infor585_ref_032">
<mixed-citation publication-type="journal"><string-name><surname>Zhao</surname>, <given-names>Y.</given-names></string-name>, <string-name><surname>Ma</surname>, <given-names>C.</given-names></string-name>, <string-name><surname>Zhao</surname>, <given-names>M.</given-names></string-name>, <string-name><surname>Xu</surname>, <given-names>X.</given-names></string-name>, <string-name><surname>Du</surname>, <given-names>B.</given-names></string-name> (<year>2025</year>). <article-title>An optimal multi-objective dynamic traffic guidance approach based on dynamic traffic assignment</article-title>. <source>Physica A: Statistical Mechanics and Its Applications</source>, <volume>657</volume>, <elocation-id>130257</elocation-id>.</mixed-citation>
</ref>
</ref-list>
</back>
</article>
