5G Vehicle Communications.rar_5G_文章/文档下载-pudn.com

<html xmlns="http://www.w3.org/1999/xhtml"> <head> <meta charset="utf-8"> <meta name="generator" content="pdf2htmlEX"> <meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1"> <link rel="stylesheet" href="https://static.pudn.com/base/css/base.min.css"> <link rel="stylesheet" href="https://static.pudn.com/base/css/fancy.min.css"> <link rel="stylesheet" href="https://static.pudn.com/prod/directory_preview_static/6251d63c74bc5c0105a47958/raw.css"> <script src="https://static.pudn.com/base/js/compatibility.min.js"></script> <script src="https://static.pudn.com/base/js/pdf2htmlEX.min.js"></script> <script> try{ pdf2htmlEX.defaultViewer = new pdf2htmlEX.Viewer({}); }catch(e){} </script> <title></title> </head> <body> <div id="sidebar" style="display: none"> <div id="outline"> </div> </div> <div id="pf1" class="pf w0 h0" data-page-no="1"><div class="pc pc1 w0 h0"><img class="bi x0 y0 w1 h1" alt="" src="https://static.pudn.com/prod/directory_preview_static/6251d63c74bc5c0105a47958/bg1.jpg"><div class="t m0 x1 h2 y1 ff1 fs0 fc0 sc0 ls0 ws0">1</div><div class="t m0 x2 h3 y2 ff1 fs1 fc0 sc0 ls1 ws0">5G Vehicle Communications</div><div class="t m0 x2 h4 y3 ff2 fs2 fc0 sc0 ls2 ws0">LaeYoung Kim</div><div class="t m0 x2 h5 y4 ff2 fs3 fc0 sc0 ls3 ws0">LG Electronics, Seoul, Korea</div><div class="t m0 x2 h6 y5 ff1 fs4 fc0 sc0 ls4 ws0">Introduction</div><div class="t m0 x2 h7 y6 ff3 fs5 fc0 sc0 ls5 ws0">e third generation partnership project (3GPP) started to investigate how</div><div class="t m0 x2 h7 y7 ff3 fs5 fc0 sc0 ls5 ws0">evolved packet system (EPS) and long-term evolution (LTE) network can deliver</div><div class="t m0 x2 h7 y8 ff3 fs5 fc0 sc0 ls6 ws0">vehicle-to-everything (V2X) services in 2015. is occurred because many consider</div><div class="t m0 x2 h7 y9 ff3 fs5 fc0 sc0 ls6 ws0">that widely deployed LTE-based infrastructure can provide the opportunity for the</div><div class="t m0 x2 h7 ya ff3 fs5 fc0 sc0 ls7 ws0">vehicle industry to realize the idea of the “connected car” by taking advantage of</div><div class="t m0 x2 h7 yb ff3 fs5 fc0 sc0 ls7 ws0">the strengths of EPS/LTE, such as higher data rate, low latency, and excellent cov-</div><div class="t m0 x2 h7 yc ff3 fs5 fc0 sc0 ls8 ws0">erage, as well as by leveraging various technologies and functionality of EPS/LTE</div><div class="t m0 x2 h7 yd ff3 fs5 fc0 sc0 ls6 ws0">such as direct communication for proximity-based services (ProSe) and multimedia</div><div class="t m0 x2 h7 ye ff3 fs5 fc0 sc0 ls5 ws0">broadcast/multicast service (MBMS).</div><div class="t m0 x3 h7 yf ff3 fs5 fc0 sc0 ls5 ws0">Section titled “First Activity on Vehicle Communications in Cellular Systems” dis-</div><div class="t m0 x2 h7 y10 ff3 fs5 fc0 sc0 ls6 ws0">cusses the ﬁrst step in standardization activity on vehicle communications in cellular</div><div class="t m0 x2 h7 y11 ff3 fs5 fc0 sc0 ls5 ws0">systems made by the 3GPP. Section titled “5G Activity on Vehicle Communications</div><div class="t m0 x2 h7 y12 ff3 fs5 fc0 sc0 ls5 ws0">in Cellular Systems” discusses 5G standardization activity on vehicle communications</div><div class="t m0 x2 h7 y13 ff3 fs5 fc0 sc0 ls5 ws0">in cellular systems made by the 3GPP. Lastly, section titled “Conclusions” provides con-</div><div class="t m0 x2 h7 y14 ff3 fs5 fc0 sc0 ls7 ws0">cluding remarks.</div><div class="t m0 x2 h6 y15 ff1 fs4 fc0 sc0 ls4 ws0">First Activity on Vehicle Communications in Cellular Systems</div><div class="t m0 x2 h8 y16 ff1 fs5 fc0 sc0 ls9 ws0">Use Cases for V2X Services and the Related Service Requirements</div><div class="t m0 x2 h7 y17 ff3 fs5 fc0 sc0 ls6 ws0">Before investigating vehicle communications standards in 5G cellular systems, it is</div><div class="t m0 x2 h7 y18 ff3 fs5 fc0 sc0 ls6 ws0">worthwhile to look into the ﬁrst activity on vehicle communications in cellular systems.</div><div class="t m0 x2 h7 y19 ff3 fs5 fc0 sc0 ls6 ws0">is activity is based on the EPS. 3GPP standardized vehicle communications in EPS in</div><div class="t m0 x2 h7 y1a ff3 fs5 fc0 sc0 ls5 ws0">Release 14, the ﬁnal release before standardization focus turned to 5G.</div><div class="t m0 x3 h7 y1b ff3 fs5 fc0 sc0 ls5 ws0">First, 3GPP identiﬁed various use cases for V2X services and the related service</div><div class="t m0 x2 h7 y1c ff3 fs5 fc0 sc0 ls5 ws0">requirements. is study is documented in technical report (TR) 22.885 (3GPP</div><div class="t m0 x2 h7 y1d ff3 fs5 fc0 sc0 ls6 ws0">TR 22.885 version 14.0.0 2015). Vehicle communications are categorized into four</div><div class="t m0 x2 h7 y1e ff3 fs5 fc0 sc0 lsa ws0">diﬀerent types:</div><div class="t m0 x2 h9 y1f ff4 fs6 fc0 sc0 lsb ws0">Wiley 5G Ref. Edited by Rahim Tafazolli, Chin-Liang Wang and Periklis Chatzimisios.</div><div class="t m0 x2 h9 y20 ff3 fs6 fc0 sc0 ls0 ws0">Copyright © 2019 John Wiley & Sons Ltd.</div><div class="t m0 x2 h9 y21 ff3 fs6 fc0 sc0 lsc ws0">DOI: 10.1002/9781119471509.w5GRef214</div><a class="l" rel='nofollow' onclick='return false;'><div class="d m1"></div></a><a class="l" rel='nofollow' onclick='return false;'><div class="d m1"></div></a><a class="l" rel='nofollow' onclick='return false;'><div class="d m1"></div></a><a class="l" rel='nofollow' onclick='return false;'><div class="d m1"></div></a></div><div class="pi" data-data='{"ctm":[1.961964,0.000000,0.000000,1.961964,0.000000,0.000000]}'></div></div> </body> </html>

<div id="pf2" class="pf w0 h0" data-page-no="2"><div class="pc pc2 w0 h0"><img class="bi x0 y0 w1 h1" alt="" src="https://static.pudn.com/prod/directory_preview_static/6251d63c74bc5c0105a47958/bg2.jpg"><div class="t m0 x4 h2 y1 ff1 fs0 fc0 sc0 ls0 ws0">2 5G Vehicle Communications</div><div class="t m0 x5 ha y22 ff5 fs7 fc1 sc0 ls0 ws0">Vehicle</div><div class="t m0 x6 ha y23 ff5 fs7 fc1 sc0 ls0 ws0">Vehicle</div><div class="t m0 x7 ha y24 ff5 fs7 fc1 sc0 ls0 ws0">Pedestrian</div><div class="t m0 x8 ha y25 ff5 fs7 fc1 sc0 ls0 ws0">RSU</div><div class="t m0 x9 ha y26 ff5 fs7 fc1 sc0 ls0 ws0">Application</div><div class="t m0 xa ha y27 ff5 fs7 fc1 sc0 ls0 ws0">server</div><div class="t m0 xb ha y28 ff5 fs7 fc1 sc0 ls0 ws0">V2V</div><div class="t m0 xc ha y29 ff5 fs7 fc1 sc0 ls0 ws0">V2P</div><div class="t m0 xd ha y2a ff5 fs7 fc1 sc0 ls0 ws0">V2I</div><div class="t m0 xe ha y2b ff5 fs7 fc1 sc0 ls0 ws0">V2N</div><div class="t m0 xf hb y2c ff1 fs8 fc0 sc0 lse ws0">Figure 1 Types of vehicle</div><div class="t m0 xf hb y2d ff6 fs8 fc0 sc0 lsf ws0">communications.</div><div class="t m0 x6 h7 y2e ff7 fs5 fc0 sc0 ls0 ws0">• Vehicle-to-vehicle (V2V) communications</div><div class="t m0 x6 h7 y2f ff7 fs5 fc0 sc0 ls0 ws0">• Vehicle-to-pedestrian (V2P) communications</div><div class="t m0 x6 h7 y30 ff7 fs5 fc0 sc0 ls0 ws0">• Vehicle-to-infrastructure (V2I) communications</div><div class="t m0 x6 h7 y31 ff7 fs5 fc0 sc0 ls0 ws0">• Vehicle-to-network (V2N) communications</div><div class="t m0 x10 h7 y32 ff3 fs5 fc0 sc0 ls6 ws0">In cellular systems, a vehicle is considered as a user equipment (UE). A pedestrian is</div><div class="t m0 x6 h7 y33 ff3 fs5 fc0 sc0 ls6 ws0">also expressed as a UE. In V2I communications, a road side unit (RSU) can be considered</div><div class="t m0 x6 h7 y34 ff3 fs5 fc0 sc0 ls7 ws0">as infrastructure. e RSU is an entity that can transmit to and receive from a UE for V2X</div><div class="t m0 x6 h7 y35 ff3 fs5 fc0 sc0 ls6 ws0">services. e RSU can be implemented as a stationary UE or implemented in a cellular</div><div class="t m0 x6 h7 y36 ff3 fs5 fc0 sc0 ls5 ws0">system (e.g. eNB-type RSU comprising an eNB, a collocated local gateway (L-GW), and</div><div class="t m0 x6 h7 y37 ff3 fs5 fc0 sc0 ls6 ws0">a V2X application server). e V2N communication is made via the cellular system.</div><div class="t m0 x10 h7 y38 ff3 fs5 fc0 sc0 ls5 ws0">e four types of vehicle communications described above can be collectively called</div><div class="t m0 x6 h7 y39 ff3 fs5 fc0 sc0 ls6 ws0">“V2X communications” (Figure 1).</div><div class="t m0 x10 h7 y3a ff3 fs5 fc0 sc0 ls5 ws0">e various use cases for V2X services identiﬁed by the 3GPP cover V2V commu-</div><div class="t m0 x6 h7 y3b ff3 fs5 fc0 sc0 ls6 ws0">nications, V2P communications, V2I communications, and V2N communications, and</div><div class="t m0 x6 h7 y3c ff3 fs5 fc0 sc0 ls6 ws0">mainly for basic road safety. e following use cases are examples:</div><div class="t m0 x6 h7 y3d ff7 fs5 fc0 sc0 ls0 ws0">• Forward Collision Warning (FCW). FCW warns a driver of a vehicle of an impending</div><div class="t m0 x11 h7 y3e ff3 fs5 fc0 sc0 ls6 ws0">rear-end collision with a vehicle ahead in traﬃc in the same lane and direction of</div><div class="t m0 x11 h7 y3f ff3 fs5 fc0 sc0 ls6 ws0">travel. FCW is intended to help drivers avoid or to mitigate rear-end vehicle collisions</div><div class="t m0 x11 h7 y40 ff3 fs5 fc0 sc0 ls11 ws0">in the forward path of travel.</div><div class="t m0 x6 h7 y41 ff7 fs5 fc0 sc0 ls0 ws0">• Control Loss Warning (CLW). CLW enables a vehicle to broadcast a self-generated</div><div class="t m0 x11 h7 y42 ff3 fs5 fc0 sc0 ls6 ws0">control loss event to surrounding vehicles. On receiving such event information, a</div><div class="t m0 x11 h7 y43 ff3 fs5 fc0 sc0 ls6 ws0">surrounding vehicle determines the relevance of the event and provides a warning to</div><div class="t m0 x11 h7 y44 ff3 fs5 fc0 sc0 ls7 ws0">the driver, if appropriate.</div><div class="t m0 x6 h7 y45 ff7 fs5 fc0 sc0 ls0 ws0">• Emergency Stop. In case of emergency stop of a vehicle, the vehicle triggers safer</div><div class="t m0 x11 h7 y46 ff3 fs5 fc0 sc0 ls6 ws0">behavior for other vehicles in proximity of the vehicle. erefore, the stationary vehi-</div><div class="t m0 x11 h7 y47 ff3 fs5 fc0 sc0 ls6 ws0">cle generates a “stationary vehicle warning” message. All vehicles within the trans-</div><div class="t m0 x11 h7 y48 ff3 fs5 fc0 sc0 ls5 ws0">mission range of the stationary vehicle are able to receive the message. When there is</div><div class="t m0 x11 h7 y49 ff3 fs5 fc0 sc0 ls7 ws0">an RSU in the stationary vehicle’s vicinity, the RSU is able to receive the message and</div><div class="t m0 x11 h7 y4a ff3 fs5 fc0 sc0 ls5 ws0">relay the message to its surrounding vehicles.</div><div class="t m0 x6 h7 y4b ff7 fs5 fc0 sc0 ls0 ws0">• Vulnerable Road User (V RU) Safety. is use case describes the scenario whereby a</div><div class="t m0 x11 h7 y4c ff3 fs5 fc0 sc0 ls7 ws0">vehicle detects any pedestrian’s presence and alerts the driver, if an imminent collision</div><div class="t m0 x11 h7 y4d ff3 fs5 fc0 sc0 ls7 ws0">risk is present.</div><a class="l" rel='nofollow' onclick='return false;'><div class="d m1"></div></a></div><div class="pi" data-data='{"ctm":[1.961964,0.000000,0.000000,1.961964,0.000000,0.000000]}'></div></div>

<div id="pf3" class="pf w0 h0" data-page-no="3"><div class="pc pc3 w0 h0"><img class="bi x0 y0 w1 h1" alt="" src="https://static.pudn.com/prod/directory_preview_static/6251d63c74bc5c0105a47958/bg3.jpg"><div class="t m0 x12 h2 y1 ff2 fs0 fc0 sc0 lsd ws0">5G Vehicle Communications 3</div><div class="t m0 x3 h7 y4e ff3 fs5 fc0 sc0 ls5 ws0">e V2X communications also provide intelligent transportation services including</div><div class="t m0 x2 h7 y4f ff3 fs5 fc0 sc0 ls13 ws0">road safety and traﬃc eﬃciency for end-users. Various entities that participate in the</div><div class="t m0 x2 h7 y50 ff3 fs5 fc0 sc0 ls6 ws0">V2X communications, such as vehicles, pedestrians, RSUs, and application servers,</div><div class="t m0 x2 h7 y51 ff3 fs5 fc0 sc0 ls6 ws0">can collect information related to their local environment (e.g. information received</div><div class="t m0 x2 h7 y52 ff3 fs5 fc0 sc0 ls5 ws0">from other vehicles or sensor equipment in proximity) to process and share that</div><div class="t m0 x2 h7 y53 ff3 fs5 fc0 sc0 ls6 ws0">knowledge, thereby to provide intelligent transportation services. To achieve this, the</div><div class="t m0 x2 h7 y54 ff3 fs5 fc0 sc0 ls5 ws0">UE periodically transmits V2X messages containing driving-related information (e.g.</div><div class="t m0 x2 h7 y55 ff3 fs5 fc0 sc0 ls5 ws0">location, dynamics, and attributes). In addition, V2X messages triggered by certain</div><div class="t m0 x2 h7 y56 ff3 fs5 fc0 sc0 ls6 ws0">events such as “stationary vehicle warning” can be transmitted by the UE.</div><div class="t m0 x3 h7 y57 ff3 fs5 fc0 sc0 ls5 ws0">Based on not only the use cases captured in 3GPP TR 22.885 version 14.0.0 (2015)</div><div class="t m0 x2 h7 y58 ff3 fs5 fc0 sc0 ls6 ws0">and the use cases contained in previous work done by many other organizations in</div><div class="t m0 x2 h7 y59 ff3 fs5 fc0 sc0 ls5 ws0">the ﬁelds of automotive such as the European Telecommunications Standards Institute</div><div class="t m0 x2 h7 y5a ff3 fs5 fc0 sc0 ls5 ws0">(ETSI) intelligent transport systems (ITS) (ETSI TR 102 638 V1.1.1 2009), 3GPP deﬁned</div><div class="t m0 x2 h7 y5b ff3 fs5 fc0 sc0 ls6 ws0">the following major service requirements for typical V2X services from cellular systems’</div><div class="t m0 x2 h7 y5c ff3 fs5 fc0 sc0 ls5 ws0">perspective in technical speciﬁcation (TS) 22.185 (3GPP TS 22.185 version 14.4.0 2018):</div><div class="t m0 x2 h7 y5d ff3 fs5 fc0 sc0 ls5 ws0">1) Message transfer latency no longer than 100 ms. For some speciﬁc use cases, maxi-</div><div class="t m0 x13 h7 y5e ff3 fs5 fc0 sc0 ls5 ws0">mum allowed message transfer latency is 20 ms.</div><div class="t m0 x2 h7 y5f ff3 fs5 fc0 sc0 ls5 ws0">2) Transfer of messages of size up to 1200 bytes.</div><div class="t m0 x2 h7 y60 ff3 fs5 fc0 sc0 ls6 ws0">3) Support of up to 10 message transfers per second in typical cases, while enabling a</div><div class="t m0 x13 h7 y61 ff3 fs5 fc0 sc0 ls5 ws0">maximum message transfer frequency of 50 Hz.</div><div class="t m0 x2 h7 y62 ff3 fs5 fc0 sc0 lsa ws0">4) Communication range suﬃcient for the driver to have enough response time</div><div class="t m0 x13 h7 y63 ff3 fs5 fc0 sc0 ls14 ws0">(e.g. 4 s).</div><div class="t m0 x2 h7 y64 ff3 fs5 fc0 sc0 ls6 ws0">5) Support of relative vehicle speeds up to 500 km h</div><div class="t m0 x14 hc y65 ff3 fs9 fc0 sc0 ls0 ws0">–1</div><div class="t m0 x15 h7 y66 ff3 fs5 fc0 sc0 ls0 ws0">.</div><div class="t m0 x2 h7 y67 ff3 fs5 fc0 sc0 ls5 ws0">6) Support of V2X communication both in and out of network coverage.</div><div class="t m0 x2 h7 y68 ff3 fs5 fc0 sc0 ls5 ws0">7) Support of security aspects such as privacy.</div><div class="t m0 x2 h8 y69 ff1 fs5 fc0 sc0 ls10 ws0">V2X Communication over PC5 Interface and LTE-Uu Interface</div><div class="t m0 x2 h7 y6a ff3 fs5 fc0 sc0 ls5 ws0">Based on the service requirements in 3GPP TS 22.185 version 14.4.0 (2018), EPS</div><div class="t m0 x2 h7 y6b ff3 fs5 fc0 sc0 ls7 ws0">architecture reference models for V2X services, functional entities involved for V2X</div><div class="t m0 x2 h7 y6c ff3 fs5 fc0 sc0 ls6 ws0">communications, interfaces and interactions between functional entities, provisioned</div><div class="t m0 x2 h7 y6d ff3 fs5 fc0 sc0 ls5 ws0">parameters, and procedures were speciﬁed in 3GPP TS 23.285 version 14.8.0 (2019).</div><div class="t m0 x3 h7 y6e ff3 fs5 fc0 sc0 ls6 ws0">ere are two modes of operation for V2X communication, as shown in Figure 2:</div><div class="t m0 x2 hd y6f ff1 fsa fc0 sc0 ls15 ws0">V2X Communication Over PC5 Interface</div><div class="t m0 x2 h7 y70 ff3 fs5 fc0 sc0 ls5 ws0">PC5 interface directly connects UEs so that over-the-air V2X message from a UE is</div><div class="t m0 x2 h7 y71 ff3 fs5 fc0 sc0 ls6 ws0">directly received by UEs in physical proximity of the transmitting UE. e PC5 interface</div><div class="t m0 x2 h7 y72 ff3 fs5 fc0 sc0 ls5 ws0">at the physical and link layers is also known as “sidelink.”</div><div class="t m0 x3 h7 y73 ff3 fs5 fc0 sc0 ls6 ws0">V2X communication over PC5 interface is supported using sidelink when the UE is in</div><div class="t m0 x2 h7 y74 ff3 fs5 fc0 sc0 ls5 ws0">LTE network coverage, i.e. “served by Evolved Universal Terrestrial Radio Access Net-</div><div class="t m0 x2 h7 y75 ff3 fs5 fc0 sc0 ls5 ws0">work (E-UTRAN)” as well as when the UE is out of network coverage, i.e. “not served</div><div class="t m0 x2 h7 y76 ff3 fs5 fc0 sc0 ls16 ws0">by E-UTRAN.”</div><div class="t m0 x3 h7 y77 ff3 fs5 fc0 sc0 ls5 ws0">When the UE is “served by E-UTRAN,” it can send V2X messages over PC5 interface</div><div class="t m0 x2 h7 y78 ff3 fs5 fc0 sc0 ls5 ws0">by using scheduled resource allocation mode (a.k.a. network scheduled operation</div><div class="t m0 x2 h7 y79 ff3 fs5 fc0 sc0 ls5 ws0">mode) and UE autonomous resources selection mode. When the UE is “not served</div><div class="t m0 x2 h7 y7a ff3 fs5 fc0 sc0 ls5 ws0">by E-UTRAN,” it can send V2X messages over PC5 interface only by using UE</div><a class="l" rel='nofollow' onclick='return false;'><div class="d m1"></div></a><a class="l" rel='nofollow' onclick='return false;'><div class="d m1"></div></a><a class="l" rel='nofollow' onclick='return false;'><div class="d m1"></div></a><a class="l" rel='nofollow' onclick='return false;'><div class="d m1"></div></a><a class="l" rel='nofollow' onclick='return false;'><div class="d m1"></div></a><a class="l" rel='nofollow' onclick='return false;'><div class="d m1"></div></a></div><div class="pi" data-data='{"ctm":[1.961964,0.000000,0.000000,1.961964,0.000000,0.000000]}'></div></div>

<div id="pf4" class="pf w0 h0" data-page-no="4"><div class="pc pc4 w0 h0"><img class="bi x0 y0 w1 h1" alt="" src="https://static.pudn.com/prod/directory_preview_static/6251d63c74bc5c0105a47958/bg4.jpg"><div class="t m0 x4 h2 y1 ff1 fs0 fc0 sc0 ls0 ws0">4 5G Vehicle Communications</div><div class="t m0 x16 he y7b ff5 fsb fc1 sc0 ls0 ws0">Evolved packet core</div><div class="t m0 x17 he y7c ff5 fsb fc1 sc0 ls0 ws0">V2X messages over PC5</div><div class="t m0 x18 he y7d ff5 fsb fc1 sc0 ls0 ws0">V2X application</div><div class="t m0 x19 he y7e ff5 fsb fc1 sc0 ls0 ws0">server</div><div class="t m0 x1a he y7f ff5 fsb fc1 sc0 ls0 ws0">Gateway</div><div class="t m0 x1b he y80 ff5 fsb fc1 sc0 ls0 ws0">Evolved</div><div class="t m0 x1c he y81 ff5 fsb fc1 sc0 ls0 ws0">Packet Core</div><div class="t m2 x1d hf y82 ff5 fsc fc1 sc0 ls0 ws0">V2X messages over PC5</div><div class="t m3 x1e h10 y83 ff5 fsd fc1 sc0 ls0 ws0">V2X messages</div><div class="t m3 x1f h10 y84 ff5 fsd fc1 sc0 ls0 ws0">over LTE-Uu</div><div class="t m4 x20 h11 y85 ff5 fse fc1 sc0 ls0 ws0">V2X messages</div><div class="t m4 x21 h11 y86 ff5 fse fc1 sc0 ls17 ws0">over LTE-Uu</div><div class="t m4 x12 h11 y87 ff5 fse fc1 sc0 ls0 ws0">(broadcast/</div><div class="t m4 x22 h11 y88 ff5 fse fc1 sc0 ls0 ws0">unicast)</div><div class="t m5 x23 h12 y89 ff5 fsf fc1 sc0 ls0 ws0">(unicast)</div><div class="t m0 x24 he y8a ff5 fsb fc1 sc0 ls0 ws0">"In coverage"</div><div class="t m0 x25 he y8b ff5 fsb fc1 sc0 ls0 ws0">"Out of coverage"</div><div class="t m0 x6 h13 y8c ff5 fs10 fc1 sc0 ls0 ws0">(a) (b)</div><div class="t m0 x26 he y8d ff5 fsb fc1 sc0 ls0 ws0">E-UTRAN</div><div class="t m0 x27 he y8e ff5 fsb fc1 sc0 ls0 ws0">E-UTRAN</div><div class="t m0 x6 hb y8f ff1 fs8 fc0 sc0 lse ws0">Figure 2 V2X communication over PC5 interface and LTE-Uu interface. (a) V2X communication over</div><div class="t m0 x6 hb y90 ff6 fs8 fc0 sc0 ls19 ws0">PC5 and (b) V2X communication over LTE-Uu.</div><div class="t m0 x6 h7 y91 ff3 fs5 fc0 sc0 ls5 ws0">autonomous resources selection mode. e scheduled resource allocation mode is</div><div class="t m0 x6 h7 y92 ff3 fs5 fc0 sc0 ls5 ws0">centralized scheduling mode, while the UE autonomous resources selection mode is</div><div class="t m0 x6 h7 y93 ff3 fs5 fc0 sc0 ls5 ws0">distributed scheduling mode (see 3GPP TS 36.300 version 14.9.0 2019).</div><div class="t m0 x10 h7 y94 ff3 fs5 fc0 sc0 ls6 ws0">Only broadcast mode of V2X communication over PC5 interface is supported for</div><div class="t m0 x6 h7 y95 ff3 fs5 fc0 sc0 ls1a ws0">LTE PC5.</div><div class="t m0 x6 hd y96 ff1 fsa fc0 sc0 ls1b ws0">V2X Communication Over LTE-Uu Interface</div><div class="t m0 x6 h7 y97 ff3 fs5 fc0 sc0 ls5 ws0">LTE-Uu interface connects UEs with an eNodeB (E-UTRAN NodeB), the base station in</div><div class="t m0 x6 h7 y98 ff3 fs5 fc0 sc0 ls6 ws0">the LTE networks. Unicast can be used for transmitting uplink traﬃc from the UE and</div><div class="t m0 x6 h7 y99 ff3 fs5 fc0 sc0 ls6 ws0">downlink traﬃc to the UE while MBMS can be used for transmitting downlink traﬃc to</div><div class="t m0 x6 h7 y9a ff3 fs5 fc0 sc0 ls1c ws0">the UEs.</div><div class="t m0 x10 h7 y9b ff3 fs5 fc0 sc0 ls6 ws0">V2X communication over LTE-Uu interface is supported only when the UE is inside</div><div class="t m0 x6 h7 y9c ff3 fs5 fc0 sc0 ls5 ws0">network coverage. A UE can send V2X messages over LTE-Uu interface destined to a</div><div class="t m0 x6 h7 y9d ff3 fs5 fc0 sc0 ls6 ws0">locally relevant V2X application server, and the V2X application server delivers the V2X</div><div class="t m0 x6 h7 y9e ff3 fs5 fc0 sc0 ls5 ws0">messages to the UE(s) in a target area using unicast delivery and/or MBMS delivery. e</div><div class="t m0 x6 h7 y9f ff3 fs5 fc0 sc0 ls7 ws0">V2X messages are delivered between the UE and the V2X Application Server through</div><div class="t m0 x6 h7 ya0 ff3 fs5 fc0 sc0 ls5 ws0">the E-UTRAN and evolved packet core (EPC).</div><div class="t m0 x10 h7 ya1 ff3 fs5 fc0 sc0 ls6 ws0">ese two communication interfaces may be used by a UE independently for trans-</div><div class="t m0 x6 h7 ya2 ff3 fs5 fc0 sc0 ls5 ws0">mission and reception. For example, a UE transmits the V2X messages only via PC5</div><div class="t m0 x6 h7 ya3 ff3 fs5 fc0 sc0 ls6 ws0">interface. An RSU implemented as a stationary UE receives the V2X messages via PC5</div><div class="t m0 x6 h7 ya4 ff3 fs5 fc0 sc0 ls6 ws0">interface and forwards the V2X messages to a V2X application server via LTE–Uu inter-</div><div class="t m0 x6 h7 ya5 ff3 fs5 fc0 sc0 ls5 ws0">face. e V2X application server can distribute the V2X messages to UEs via the MBMS</div><div class="t m0 x6 h7 ya6 ff3 fs5 fc0 sc0 ls5 ws0">system. In this manner, a UE can directly receive V2X messages from other UEs in close</div><div class="t m0 x6 h7 ya7 ff3 fs5 fc0 sc0 ls6 ws0">proximity and via MBMS as well. is combining of sources of information can increase</div><div class="t m0 x6 h7 ya8 ff3 fs5 fc0 sc0 ls0 ws0">the reliability of V2X message transmission.</div><a class="l" rel='nofollow' onclick='return false;'><div class="d m1"></div></a></div><div class="pi" data-data='{"ctm":[1.961964,0.000000,0.000000,1.961964,0.000000,0.000000]}'></div></div>

<div id="pf5" class="pf w0 h0" data-page-no="5"><div class="pc pc5 w0 h0"><img class="bi x0 y0 w1 h1" alt="" src="https://static.pudn.com/prod/directory_preview_static/6251d63c74bc5c0105a47958/bg5.jpg"><div class="t m0 x12 h2 y1 ff2 fs0 fc0 sc0 lsd ws0">5G Vehicle Communications 5</div><div class="t m0 x3 h7 y4e ff3 fs5 fc0 sc0 ls5 ws0">As illustrated in Figure 2, compared to V2X communication over PC5 interface, V2X</div><div class="t m0 x2 h7 y4f ff3 fs5 fc0 sc0 ls5 ws0">messages transferred via LTE–Uu interface traverse the mobile network, resulting in</div><div class="t m0 x2 h7 y50 ff3 fs5 fc0 sc0 ls6 ws0">more latency for message delivery when the sender is a UE and the receivers are UEs.</div><div class="t m0 x2 h7 y51 ff3 fs5 fc0 sc0 ls5 ws0">To meet the message transfer latency performance described above as one of the major</div><div class="t m0 x2 h7 y52 ff3 fs5 fc0 sc0 ls6 ws0">service requirements for typical V2X services, i.e. latency reduction for V2X message</div><div class="t m0 x2 h7 y53 ff3 fs5 fc0 sc0 ls6 ws0">transfer may be needed in the V2X communication over LTE–Uu interface. is can be</div><div class="t m0 x2 h7 y54 ff3 fs5 fc0 sc0 ls5 ws0">achieved by locating gateways (GWs) that user traﬃc is traversed close to radio access</div><div class="t m0 x2 h7 y55 ff3 fs5 fc0 sc0 ls6 ws0">network (RAN).</div><div class="t m0 x3 h7 y56 ff3 fs5 fc0 sc0 lsa ws0">For unicast, the related features have been already introduced as Selected IP Traf-</div><div class="t m0 x2 h7 ya9 ff3 fs5 fc0 sc0 ls5 ws0">ﬁc Oﬄoad (SIPTO) above RAN and SIPTO at the local network (SIPTO@LN) (see</div><div class="t m0 x2 h7 y58 ff3 fs5 fc0 sc0 ls6 ws0">3GPP TS 23.401 version 16.2.0 2019). erefore, V2X services can use these features</div><div class="t m0 x2 h7 y59 ff3 fs5 fc0 sc0 ls5 ws0">for latency reduction for V2X message transfer.</div><div class="t m0 x3 h7 y5a ff3 fs5 fc0 sc0 ls5 ws0">To minimize latency for V2X message broadcast, localized MBMS can be considered</div><div class="t m0 x2 h7 y5b ff3 fs5 fc0 sc0 ls5 ws0">for localized routing of V2X messages destined to UEs. Some localized MBMS deploy-</div><div class="t m0 x2 h7 y5c ff3 fs5 fc0 sc0 ls5 ws0">ment options introduced in 3GPP TS 23.285 version 14.8.0 (2019) are as follows:</div><div class="t m0 x2 h7 y5d ff7 fs5 fc0 sc0 ls0 ws0">• To move the MBMS core network functions (e.g. broadcast multicast service centre</div><div class="t m0 x28 h7 yaa ff3 fs5 fc0 sc0 ls0 ws0">(BM-SC), MBMS-GW) closer to the eNodeB.</div><div class="t m0 x2 h7 y5f ff7 fs5 fc0 sc0 ls0 ws0">• To move the user plane of MBMS core network functions (BM-SC, MBMS-GW)</div><div class="t m0 x28 h7 y60 ff3 fs5 fc0 sc0 ls1c ws0">closer to the eNodeB.</div><div class="t m0 x3 h7 yab ff3 fs5 fc0 sc0 ls6 ws0">When localized V2X application servers are deployed, Anycast may be used to conceal</div><div class="t m0 x2 h7 yac ff3 fs5 fc0 sc0 ls6 ws0">the server change from the UE. In this case, a fully qualiﬁed domain name (FQDN) is</div><div class="t m0 x2 h7 yad ff3 fs5 fc0 sc0 ls5 ws0">conﬁgured for a large region, e.g. the entire PLMN, and the UE only needs to resolve</div><div class="t m0 x2 h7 yae ff3 fs5 fc0 sc0 ls5 ws0">it once to an Anycast address. e packet data network gateway (PDN GW: P-GW) is</div><div class="t m0 x2 h7 yaf ff3 fs5 fc0 sc0 ls5 ws0">responsible for routing the traﬃc to the appropriate local V2X application servers based</div><div class="t m0 x2 h7 yb0 ff3 fs5 fc0 sc0 ls5 ws0">on Anycast address.</div><div class="t m0 x2 h8 yb1 ff1 fs5 fc0 sc0 ls10 ws0">V2X Parameters, Parameter Provisioning, and EPS Architecture for V2X</div><div class="t m0 x2 h7 yb2 ff3 fs5 fc0 sc0 ls5 ws0">One of main aspects speciﬁed for V2X communications by 3GPP is V2X parameters</div><div class="t m0 x2 h7 yb3 ff3 fs5 fc0 sc0 ls6 ws0">used for V2X communication by the UE, including parameter provisioning mechanisms.</div><div class="t m0 x2 h7 yb4 ff3 fs5 fc0 sc0 ls6 ws0">For each mode of operation for V2X communication, the V2X parameters are deﬁned</div><div class="t m0 x2 h7 yb5 ff3 fs5 fc0 sc0 ls5 ws0">in 3GPP TS 24.385 version 14.4.0 (2018).</div><div class="t m0 x2 h7 yb6 ff3 fs5 fc0 sc0 ls6 ws0">1) Main parameters for V2X communication over PC5 interface:</div><div class="t m0 x13 h7 yb7 ff3 fs5 fc0 sc0 ls5 ws0">a) A list of public land mobile networks (PLMNs) in which the UE is authorized to</div><div class="t m0 x29 h7 yb8 ff3 fs5 fc0 sc0 ls7 ws0">perform V2X communications over PC5 reference point when the UE is “served</div><div class="t m0 x29 h7 yb9 ff3 fs5 fc0 sc0 ls16 ws0">by E-UTRAN.”</div><div class="t m0 x2a h7 yba ff3 fs5 fc0 sc0 ls5 ws0">b) Radio parameters (e.g. frequency bands) used when the UE is “not served by</div><div class="t m0 x29 h7 ybb ff3 fs5 fc0 sc0 ls1d ws0">E-UTRAN” and is located in a given geographical area.</div><div class="t m0 x13 h7 ybc ff3 fs5 fc0 sc0 ls5 ws0">c) Destination address for each V2X service used to transmit V2X packets via PC5</div><div class="t m0 x29 h7 ybd ff3 fs5 fc0 sc0 ls7 ws0">interface, related to the V2X service.</div><div class="t m0 x2 h7 ybe ff3 fs5 fc0 sc0 ls6 ws0">2) Main parameters for V2X communication over LTE-Uu interface:</div><div class="t m0 x13 h7 ybf ff3 fs5 fc0 sc0 ls5 ws0">a) A list of PLMNs in which the UE is authorized to use MBMS-based V2X commu-</div><div class="t m0 x29 h7 yc0 ff3 fs5 fc0 sc0 ls7 ws0">nication.</div><div class="t m0 x2a h7 yc1 ff3 fs5 fc0 sc0 ls6 ws0">b) V2X application server address information, associated with served geographical</div><div class="t m0 x29 h7 yc2 ff3 fs5 fc0 sc0 ls5 ws0">area information and list of PLMNs that the conﬁguration applies to.</div><a class="l" rel='nofollow' onclick='return false;'><div class="d m1"></div></a><a class="l" rel='nofollow' onclick='return false;'><div class="d m1"></div></a><a class="l" rel='nofollow' onclick='return false;'><div class="d m1"></div></a><a class="l" rel='nofollow' onclick='return false;'><div class="d m1"></div></a></div><div class="pi" data-data='{"ctm":[1.961964,0.000000,0.000000,1.961964,0.000000,0.000000]}'></div></div>