Simulating LTE And Wi-Fi Coexistence In Unlicensed .

2y ago
25 Views
2 Downloads
2.91 MB
52 Pages
Last View : 2d ago
Last Download : 3m ago
Upload by : Axel Lin
Transcription

Simulating LTE and Wi-Fi Coexistence inUnlicensed Spectrum with ns-3Lorenza Giupponi, BiljanaBojovicTom HendersonUniversity of WashingtonAdditional contributors:Marco Miozzo, NicolaBaldoCTTCAdditional contributors:Sumit Roy, HosseinSavafi, Ben Cizdziel,Farah NadeemUniversity of WashingtonMay, 20161

Introduction The use of unlicensed spectrum for future LTE systems raisesconcerns about its impact on co-located Wi-Fi. Licensed bands are augmented by carriers located in unlicensedbands. Based on Carrier Aggregation, Secondary cells (SCell) can carry datatransmissions in unlicensed bands, with assistance from a PrimaryCell (PCell). We report here on recent extensions of the ns-3 simulator to modelsuch coexistence. ns-3 is a system simulator allowing for full-protocol stack evaluationof coexistence. ns-3 is the only freely available simulator for coexistence studiesknown to the authors.2

Critical Challenges LTE physical channels are designed on the basis of uninterrupted andsynchronous operation. LTE is designed to deal with reuse factor 1, to efficiently exploitlicensed spectrum. It relies on interference cancellation and mitigationtechniques. Existing systems in unlicensed spectrum operate in decentralized,asynchronous manner. Wi-Fi exploits interference avoidance principles Critical design issue: LTE has to coexist with other technologies, in a“fair” and “friendly” basis. 3GPP has defined fairness in technical report TR36.889 as follows:Fairness is the capability of an LAA network not to impact Wi-Fi networksactive on a carrier more than an additional Wi-Fi network operating on thesame carrier, in terms of both throughput and latency. Different regional regulatory requirements for transmission inunlicensed bands further complicate the design.3

Regulatory requirements In some markets such as Europe and Japan, a “sense andavoid” (or "listen before talk") approach is mandated beforetransmitting. Transmitters must first detect whether the channel is freebefore initiating a transmission. This requires modifications to the LTE air interface. Other markets, such as North America, Korea and China, suchrequirements do not exist. To meet ETSI’s requirements, 3GPP is producing astandardized version of LTE in unlicensed: Licensed AssistedAccess (LAA) LTE-U Forum is specifying and developing a proprietarysolution for access in unlicenced bands without Listen BeforeTalk (LBT) requirements4

LTE in unlicensed (LTE-U) LTE-U Forum is an industry consortium specifying a solutionreferred to as LTE-U This is based on LTE duty-cycling its transmission, i.e.alternating ON and OFF periods, by estimating the mostappropriate channel share that it should occupy. The most representative algorithm for LTE-U to share thechannel is Qualcomm’s CSAT. Qualcomm has provided demonstrations at MWC16, andthere are already products (e.g. Spidercloud, Samsung smallcells) with such Qualcomm chips. Verizon trials with these products have been announced.5

Licensed Assisted Access (LAA) 3GPP is standardizing a solution that can be deployed underall regulatory requirements. It is a system to be deployed as a Supplemental Downlink(SDL) in 5 GHz band. A Study Item has been recently finalized and has produced aTR 36.889, where a summary of simulation results has beenpresented and discussed. Release 14 is now focusing on eLAA, which includes UL. Other initiatives, MuLTEfire, rely on Rel. 13 and 14 to provide acomplete solution not anchored to the licensed band6

Ns-3 extensions to studycoexistence To support coexistence study evaluations, Wi-Fi Alliance fundedsimulation extensions of ns-3. The ns-3 Wi-Fi models have been developed over time byvarious authors, usually by directly referencing IEEE standards. They started with IEEE 802.11a and later many aspects of IEEE802.11b/g/p/e/n/ac have been included. We made many model enhancements to allow for Wi-Fi moduleand LTE module to inter-operate and interfere with one another. ns-3 Wi-Fi physical (PHY) model had to be updated to the multitechnology Spectrum framework in ns-3 (allowing Wi-Fi signalsto be received on LTE devices, and vice versa). This has resulted in a new SpectrumWiFiPhy class that reusesthe existing interference manager and error rate models, butallows foreign signals (like LTE) to be added to the noise on thechannel.7

Model enhancements in Wi-Fi Wi-Fi Clear Channel Access was enhanced to sense for non-WiFi signals and to support CCA-ED (-62 dBm) and CCA-PD (-82dBm) thresholds. Wi-Fi preamble detection (PD) based on AWGN channel model,and also TGn fading Channel Model D Wi-Fi RSS-based AP selection and roaming Wi-Fi MIMO approximations to support 2x2 DL, 1x2 DL onAWGN and TGn Model D8

Model enhancements in LTE LTE interference model relies on the simplifying assumptionthat all interfering signals are LTE and are synchronized atsubframe level. LTE inteference model has been enhanced to handleinteference by signals of any type. This relies on ns-3 Spectrum framework. The reception of LTE signals is evaluated by chunks, whereeach chunk is identified by a constant power spectral density.9

Simulation scenarios An initial test scenario, useful for testing basic model operation ina small scale setting, grew into TR36.889-like indoor and outdoorscenarios In the initial test scenario depicted below, D1 and d2 can varyand operator A and B can be either LTE or Wi-Fi10

Indoor 3GPP scenarioUnlicensed channel modelNetwork LayoutSystem bandwidthCarrier frequencyNumber of carriersTotal Base Station (BS) transmissionpowerTotal User equipment (UE)transmission powerDistance dependent path loss,shadowing and fadingAntenna patternAntenna heightUE antenna heightAntenna gainUE antenna gainNumber of UEsUE DroppingTraffic ModelUE noise figureCell selectionNetwork synchronization3GPP TR 36.889Indoor scenario20 MHz5 GHz1, 4 (to be shared between twooperators)1 for evaluations with DL UL Wi-Ficoexisting with DL-only LAA18/24 dBm18 dBm for unlicensed spectrumITU InH2D Omni-directional6m1.5 m5 dBi0 dBi10 UEs per unlicensed band carrier peroperator for DL-only10 UEs per unlicensed band carrier peroperator for DL-only for four unlicensedcarriers.20 UEs per unlicensed band carrier peroperator for DL UL for singleunlicensed carrier.20 UEs per unlicensed band carrier peroperator for DL UL Wi-Fi coexistingwith DL-only LAAAll UEs should be randomly droppedand be within coverage of the small cellin the unlicensed band.FTP Model 1 and 3 based on TR36.814 FTP model file size: 0.5 Mbytes.Optional: VoIP model based onTR36.8899 dBFor LAA UEs, cell selection is based onRSRP (Reference Signal ReceivedPower.For Wi-Fi stations (STAs), cellselection is based on RSS (Receivedsignal power strength) of WiFi AccessPoints (APs). RSS threshold is -82 dBm.For the same operator, the network canbe synchronized. Small cells of differentoperators are not synchronized.ns-3 implementationIndoor scenario20 MHz5 GHz (channel 36, tunable)1 for evaluations with DL UL Wi-Ficoexisting with DL-only LAA18/24 dBmSimulations herein consider 18 dBm18 dBm802.11ax indoor model2D Omni-directional6 m (LAA, not modelled for Wi-Fi)1.5 m (LAA, not modelled for Wi-Fi)5 dBi0 dBiSupports all the configurations in TR36.889. Simulations herein consider thecase of 20 UEs per unlicensed bandcarrier per operator for DL LAAcoexistence evaluations for singleunlicensed carrier.Randomly dropped and within small cellcoverage.FTP Model 1 as in TR36.814.FTP model file size: 0.5 MbytesVoice model: DL onlyFigure source: 3GPP TR 36.889 V13.0.0(2015-05)9 dBRSRP for LAA UEs and RSS for Wi-FiSTAsSmall cells are synchronized, differentoperators are not synchronized.11

Outdoor 3GPP scenarioOutdoor layout: hexagonal macrocell layout. 7 macro sites and 3 cells per site. 1Cluster per cell. 4 small cells per operator per cluster, uniformly dropped. ITU UMichannel model.Distance between cluster andmacro nodeDmaR1Macro NodeR2cro-clusterCluster 1R1: radius of small cell dropping within a cluster;R2: radius of UE dropping within a clusterFigure source: 3GPP TR 36.889 V13.0.0 (2015-05)12

Traffic Models The overall offered load is to be the same for both coexisting networks. TR36.889 calls for several traffic models. We have implemented the FTP Model 1. It simulates file transfers arriving according to a Poisson processwith arrival rate lambda across the entire operator network. The recommended range for lambda is between from 0.5 to 2.5.The file size is 2 Mbytes with 0.5 Mbytes optional in TR 36.814,but TR 36.889 requests the 0.5 Mbytes size. We provide a constant bit rate UDP flow option, with varying bit ratesup to saturation. We also support a Voice application based on TR36.889 100% downlink activity Voice replaces rather than adds to a UE FTP flow Voice added on only the operator B network 50% DL and 50% UL traffic (talk spurts of 5 sec)13

Performance metrics Performance metrics are described in TR 36.889. The main performance metrics are ‘user perceivedthroughput’ and ‘latency’, plotted as CDFs, for a givenscenario. In ns-3, we are calculating these by using the built-inFlowMonitor tool that tracks per-flow statistics includingthroughput and latency, and we then post-processthese results to obtain CDFs. In case of voice, Packets are marked for ExpeditedForwarding and handled by AC VO category. Latency threshold of 50 ms, and voice outage declared basedon 98% packets arriving within latency bound. Per-packet latency CDF plots14

Performance metrics Throughput and latency statistics tell how well thenetwork performs to users, but do an inadequate job ofexplaining why. We heavily instrumented the simulator to log andclassify: All PHY layer transmissionsBackoff valuesEvolution of contention windowsHARQ feedback logsWi-Fi retransmissionsTCP retransmission events15

Wi-Fi model 20 MHz 802.11n tuned to channel 36 (5.18 GHz) AWGN-based or TGn channel model D error models. Energy detection (ED)-based CCA for detection of other RAT,Preamble detection (PD)-based CCA for Wi-Fi frame detection atthe threshold of signal detection, around -88 dBm (i.e. moresensitive than the -82 dBm threshold). WiFi’s CCA ED (to LAA signals) defaults to -62 dBm. The current model is limited to 802.11n 2x2 MIMO (supported by aMIMO abstraction model) and an MCS 15 maximum rate, ratherthan 802.11ac. We do not support transmission beamforming (TxBF). An adaptive but idealized, feedback-based Wi-Fi rate control isused; rate control adjustments are made immediately uponfeedback from the peer and not due to a probing algorithm suchas Minstrel.16

Block diagram of coexistencesimulatorHigher layersEnhanced ns-3LTE NetDeviceHigher layersAP StationManagerLTE RLCLTE MACInterference/error modelscollision detectionvia Hybrid ARQ (HARQ)LBTChannelAccessLTE PHYrequest/ ManagerPHY signals(LTE and Wi-Fi)Enhanced ns-3Wi-Fi stransmissionsInterference/error modelsPHY signals(LTE and Wi-Fi)ns-3 MultiModel Spectrum ChannelKey:Existing ns-3 modelNew model developedIEEE 802.11ax indoor propagation loss model17

LAA Functional block diagramWi-Fi Measurement ConfigurationL3/RRMLAA Co-existenceManagerWi-Fi MeasurementsEDBuffer StatusL2Unlicensed ChannelMACCCA StartPHYCCA SuccessLTE DevicePHYWi-Fi DeviceLAA Device18

LAA model LAA uses an exponential backoff according to the Category 4design The update of the contention window is implemented following aHARQ feedback based approach, as suggested in [R1-156332]. LAA Energy Detection threshold (ED) is separately tunable (-72dBm default, based on latest agreements). LAA model defaults to a fixed defer time of 43 us. LAA CCA slot time 9 us. CWmin 15, CWmax 63 (based on latest agreements,configurable upward to 1023). LAA model defaults to 8 ms TXOP, based on latest agreements. Itis configurable upward to 20 ms. Data transfer starts at subframe boundary. We implementreservation signals to occupy the channel and force other nodes todefer, while we are not occupying the channel with data.19

Wi-Fi CCA Wi-Fi implements a Distributed Coordination Function (DCF) orEnhanced Distributed Coordination Access (EDCA) Resolves contention among competing nodes by implementing arandom backoff with exponentially increasing maximum contentionwindow.20

3GPP LBT procedure Different LBT categories have been evaluated, and finally the mostsimilar to Wi-Fi was selected. In LBT, nodes wishing to transmit must observe a clear channel during43 us deferral period. After this the node can transmit immediately if the channel was idle. If the medium was busy, an extended CCA is performed till channel isdeemed idle. The channel is observed during a random number N multiplied by theCCA slot duration of 9 us. N is the number of clear slots that need to be observed beforetransmitting N is randomly selected between 1 and q. q is the upper bound of the contention window, which varies between15 and 63 The contention window size (CWS) is increased upon collisiondetection and reset upon absence of collision21

3GPP LBT procedureFigure source: 3GPP TR 36.889 V13.0.0(2015-05)22

Contention Window Size update ruleCWS adjustment based on HARQ-ACKs Based on R1-156332 The CWS is increased if at least Z % of the HARQ-ACKfeedback values for a reference subframe set are NACK.Otherwise, the CWS is reset to the minimum value (i.e., 15). Reference subframe set (to be down selected) Alt. 1: the latest DL subframe for which HARQ-ACKfeedback is available Alt. 2: the first DL subframe of the latest DL data burstfor which HARQ-ACK feedback is available. Alt. 3: all subframes of the latest DL data burst for whichHARQ-ACK feedback is available. Z value: Select one out of {10%, 50%, 75%, 80%, 100%}. Z is configurable, and according to latest agreements is setto 80% by default.23

HARQ based rule concerns In Wi-Fi each tx burst is a point-to-point transmission, so there is only oneACK/NACK for each tx burst.In LAA each tx burst is a point-to-multipoint transmission, so the way ofcombining the multiple feedbacks received from the different UEs can impactthe update of the CW, and ultimately the channel occupancy.The scheduler has an impact.In Wi-Fi the feedback is sent after 16 μs, while in LAA it is sent 7 ms after thetransmission. So update is delayed.HARQ does not necessarily reflect collisions! It is hard to say if we are reallydetecting collisions through NACKsThe standard LTE transmissions are designed to maintain the BLER to 10%,so there may easily be NACKs without collision (easily solved by HARQ).Alternative 2, down-selected in November 2015 3GPP meeting makes that if acollision is detected in a subframe different than the first one, may be ignored24

DRS and system information model DRS signals have to be sent during the so called DMTC window (6msec between SF0 and SF5). This occurs with a configurableperiodicity T 40/80/160 msec. If data is scheduled during DMTC window, DRS is embedded indata transmission. Otherwise it is sent alone, without data. DRS transmission without data is subject to LBT. It should besubject to a priority LBT with a fixed defer period of only 25 us, butwe consider a normal LBT, as for data. When DRS is sent without data, we model it with 14 symbols (1msec). In addition, PSS/SSS are sent in every subframe 0 and 5 that datais scheduled, and CRC is scheduled in every subframe that data isscheduled. System information is channeled through primary cell.25

Upper layers model We evaluate performances of the above mentioned trafficmodels over both UDP and TCP transport protocols. For TCP, we default to TCP NewReno. Ns-3 offers multiple options. As for the LAA link layer, we consider UDP over RLC-UM andTCP over both RLC-AM and RLC-UM.26

MAC-PHY DL/UL timings The scheduler/MAC works 2 subframes in advance wrt when the dataactually occupies the channel. In UL we use synchronous HARQ, and in DL asynchronous HARQ,according to standard. UE MAC responds in UL SF #n 4 to events of eNB MAC happenedin DL SF #n eNB MAC responds in DL SF #n 4 to events of UE MAC happenedin UL SF #n27

Implementation Partial subframes are not supported Differently from some studies in 3GPP (e.g. QCOM, BCOM), where thelength of reservation is a random variable uniformly distributed between 0and 0.5 ms, here it is distributed between 0 and 1 ms. Channel access request deferred until data is already scheduled andready for imminent transmission on next subframe.28

FTP over UDP and RLC-UM fordifferent λStep 1Wi-FiThroughputStep 2LAAλ 0,5Step 1Wi-FiLatencyStep 2LAAλ 0,529

FTP over UDP and RLC-UM fordifferent λStep 1Wi-FiStep 2LAAThroughputStep 1Wi-FiLatencyStep 2LAA30

FTP over UDP and RLC-UM fordifferent λStep 1Wi-FiStep 2LAAλ 2,5ThroughputStep 1Wi-FiLatencyStep 2LAAλ 2,531

FTP over UDP and RLC-UM fordifferent λStep 1Wi-FiStep 2LAAThroughputλ 3,5Step 1Wi-FiLatencyStep 2LAAλ 3,532

Impact of LAA EDThr-62 dBm-82 dBm33

Impact of CTS2selfThroughputwithoutLatencywith34

Impact of DRS periodicityThroughputLatencyT 40 msT 80 msT 160 msMay occupy more airtime that Wi-Fi beacons (0.14 ms every 100 ms) 35

Impact of Z in CWS updateThroughputLatencyZ 80%Z 10%36

Impact of maximum CWSThroughputLatencyCWMmax 63CWMmax 102337

Impact of TxOP lengthThroughputLatencyTxOP 4 msTxOP 8 ms38

FTP over TCP and RLC-AM fordifferent λStep 1Wi-FiThroughputStep 2LAAλ 0,5Step 2LAAStep 1Wi-FiLatencyλ 0,539

FTP over TCP and RLC-AM fordifferent λStep 1Wi-FiStep 2LAAThroughputλ 1,5Step 1Wi-FiLatencyStep 2LAAλ 1,540

FTP over TCP and RLC-AM fordifferent λStep 1Wi-FiStep 2LAAThroughputλ 2,5Step 1Wi-FiLatencyStep 2LAAλ 2,541

FTP over TCP and RLC-AM fordifferent λStep 1Wi-FiStep 2LAAThroughputλ 3,5Step 1Wi-FiLatencyStep 2LAAλ 3,542

LAA throughput is low-- issomething wrong? 3GPP FTP model consists of: File transfers sent at random times according to a Poisson process controlled by parameterLambdaFile size 0.5MB, Lambda between 0.5 and 2.5; a Lambda of 2.5 means about one file transferevery 400ms TCP transfers of 0.5 MB with TCP segment size of 536 bytes led toabout 22 RTTs required over our LAA implementation We therefore configured a default segment size of 1440 bytes and an initial congestion windowsize of 10 segments, but still many round trip times are required to complete the transfer. Each RTT is variable but on the order of 10-30ms: LTE protocol stackintroduces very high latencies. This is due by LTE standard times, plus delays and timers introduced by RLC-AM.Those delays introduced by RLC-AM may be optimized searching for tradeoffs,but this would not increase Wi-Fi performance anyway.The delay are accentuated by the fact that there is not traffic in UL direction, sowe need to send Buffer Status Report (BSR) every time we need to send UL TCPACKs Overall throughput is then bounded by about 10-20 Mb/s since ittakes 400-500ms to complete the transfer43

If LAA throughput is so low,why is Wi-Fi impacted? The throughput degradation is due to the additional contention thatLAA LBT causes because it occupies the channel much more thanthe corresponding Wi-Fi network. LAA LBT takes the channel during more time because itintroduces retransmissions from RLC layer, as well as someoverhead again from RLC layer, if RLC-AM is considered(STATUS PDU). Resources may happen to be used more inefficiently than in Wi-Fi.Small amounts of data and/or control are scheduled inefficiently,since the SF is the minimum granularity for resource allocation. In these cases Wi-Fi occupies the channel only for tens ofmicroseconds.44

RLC-AM vs. RLC-UMThroughputLatencyλ 2,5, RLC-UMλ 2,5, RLC-AMλ 2,545

UDP 400 KbpsStep 2LAAStep 1Wi-FiThroughputStep 1Wi-FiLatencyStep 2LAA46

UDP 400 Kbps This traffic model allows to observe the effect of thetransmis

synchronous operation. LTE is designed to deal with reuse factor 1, to efficiently exploit licensed spectrum. It relies on interference cancellation and mitigation techniques. Existing systems in unlicensed spectrum operate in decen

Related Documents:

Apr 05, 2017 · Cisco 4G LTE and Cisco 4G LTE-Advanced Network Interface Module Installation Guide Table 1 Cisco 4G LTE NIM and Cisco 4G LTE-Advanced NIM SKUs Cisco 4G LTE NIM and Cisco 4G LTE-Advanced NIM SKUs Description Mode Operating Region Band NIM-4G-LTE-LA Cisco 4G LTE NIM module (LTE 2.5) for LATAM/APAC carriers. This SKU is File Size: 2MBPage Count: 18Explore furtherCisco 4G LTE Software Configuration Guide - GfK Etilizecontent.etilize.comSolved: 4G LTE Configuration - Cisco Communitycommunity.cisco.comCisco 4G LTE Software Configuration Guide - Ciscowww.cisco.comCisco 4G LTE-Advanced Configurationwww.cisco.com4G LTE Configuration - Cisco Communitycommunity.cisco.comRecommended to you b

Samsung Galaxy S4 Active with LTE Samsung Galaxy Note LTE / Note II LTE / Note 3 LTE Samsung Galaxy ACE 3 LTE Samsung Galaxy Note 10.1 LTE / Note 8.0 with LTE Samsung Galaxy Mega 6.3 with LTE . 5 Samsung Galaxy Tab 3 10.1 LTE / Tab 3 7.0 LTE Sony Xperia V / Z / SP / Z Ultra / Z1

Cisco 819 Series 4G LTE ISRs, Cisco C880 Series 4G LTE ISRs, and Cisco C890 Series 4G LTE ISRs also support integrated 4G LTE wireless WAN. Cisco 4G LTE EHWICs and Cisco 800 Series 4G LTE ISRs support the following 4G/3G modes: † 4G LTE—4G LTE mobile specificati

TD-HSDPA/HSUPA: 2.8Mbps DL, 2.2Mbps UL EDGE: Multi Slot Class 12 236.8 kbps DL & UL GPRS: Multi Slot Class 10 85.6 kbps DL & UL Frequency Bands: LTE Band B1 (2100MHz) LTE Band B2 (1900MHz) LTE Band B3 (1800MHz) LTE Band B4 - AWS (1700MHz), LTE Band B5 (850MHz), LTE Band B7 (2600MHz) LTE Band B8 (900MHz) LTE Band B12 (700MHz) LTE

ETSI is the copyright holder of LTE, LTE-Advanced and LTE Advanced Pro and 5G Logos. LTE is a trade mark of ETSI. Grandmetric is authorized to use the LTE, LTE-Advanced, LTE-Advanced Pro and 5G logos and the acronym LTE. All information that will be discussed is provided "as is" and Grandmetric gives no guarantee or warranty that the information

Cisco Fourth-Generation LTE Network Interface Module Installation Guide Hardware Overview Hardware Overview Cisco 4G-LTE NIM addresses the modular 4G-LTE cellu lar connectivity on the Cisco 4000 Series ISRs. Cisco 4G-LTE-NIM is feature-compatible with Cisco EHWIC-4G-LTE. Table 1 describes the Cisco 4G LTE

LTE Specifications Frequency Band LTE-FDD Band 2: UL 1850MHz - 1910MHz 1930MHz - 1990MHz DL LTE-FDD Band 3: 1710MHz - 1785MHz 1805MHz - 1880MH LTE-FDD Band 7: 2500MHz - 2570MHz 2620MHz - 2690MHz LTE-FDD Band 28B: 718MHz - 748MHz 773MHz - 803MHz LTE-TDD Band 42: 3400MHz - 3600MHz Non 3GPP-band TDD 1785MHz - 1805MHz 1900MHz .

LTE and LTE-Advanced FDD/TDD X-Series Measurement App, Multi-Touch N9080C and N9082C Technical Overview - Perform LTE and LTE-Advanced FDD and TDD base station (eNB) and user equipment (UE) transmitter tests - Accelerate measurements with one-button RF conformance tests as defined by 3GPP TS 36.141 and 36.521 specification