16.03.2015 Views

"WINNER II Channel Models", ver 1.1, Sept

"WINNER II Channel Models", ver 1.1, Sept

"WINNER II Channel Models", ver 1.1, Sept

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

<strong>WINNER</strong> <strong>II</strong> D<strong>1.1</strong>.2 V<strong>1.1</strong><br />

Table 4-3 Far scatterer radii and attenuations for B2 and C3.<br />

Scenario FS min FS max FS loss<br />

B2 150 m 500 m 4 dB/µs<br />

C3 300 m 1500 m 2 dB/µs<br />

Step 2:<br />

For C3 create 20 delays as described for C2 model in section 4.2. step 5. For the shortest 18 delays create<br />

a typical urban C2 channel profile (powers and angles) as in section 4.2.<br />

Similarly, create 16 delays for B1 NLOS, and for the shortest 14 delays create a typical B1 NLOS<br />

channel profile as in section 4.2.<br />

The last two delays in B2 and C3 are assigned for far scatterer clusters.<br />

Step 3:<br />

Create typical urban channel powers P ’ for FS clusters substituting equation (4.5) of section 4.2 step 6<br />

−Ζn<br />

' 10<br />

with = 10 , where Ζ n ~ N(0, ζ ) is the per cluster shadowing term in [dB].<br />

P n<br />

Step 4:<br />

Next create excess delays due to far scatterer clusters as<br />

Attenuate FS clusters as FS loss, given in Table 4-3.<br />

Step 5:<br />

d<br />

BS −> FS −> MS<br />

− d<br />

LOS<br />

τ<br />

excess<br />

=<br />

(4.22)<br />

c<br />

Select directions of departure and arrival for each FS cluster according to far scatterer locations. i.e.<br />

corresponding to a single reflection from far scatterer.<br />

It is worth noticing that depending on the location of the mobile user within the cell the FS clusters may<br />

appear also at shorter delays than the maximum C2 or B1 NLOS cluster. In such cases the far scatterers<br />

do not necessarily result to increased angular or delay dispersion. Also the actual channel statistics of the<br />

bad urban users depend somewhat on the cell size.<br />

4.3 Path loss models<br />

Path loss models for the various <strong>WINNER</strong> scenarios have been developed based on results of<br />

measurements carried out within <strong>WINNER</strong>, as well as results from the open literature. These path loss<br />

models are typically of the form of (4.23), where d is the distance between the transmitter and the recei<strong>ver</strong><br />

in [m], f c is the system frequency in [GHz], the fitting parameter A includes the path-loss exponent,<br />

parameter B is the intercept, parameter C describes the path loss frequency dependence, and X is an<br />

optional, environment-specific term (e.g., wall attenuation in the A1 NLOS scenario).<br />

⎛<br />

PL = Alog ( d[ m ])<br />

+ B + C log10<br />

⎜<br />

⎝<br />

f<br />

c<br />

[ GHz]<br />

5.0<br />

⎞<br />

⎟ + X<br />

⎠<br />

10<br />

(4.23)<br />

The models can be applied in the frequency range from 2 – 6 GHz and for different antenna heights. The<br />

path-loss models have been summarized in Table 4-4, which either defines the variables of (4.23), or<br />

explicitly provides a full path loss formula. The free-space path loss, PL free , that is referred to in the table<br />

can be written as<br />

PL<br />

free<br />

= 20log10(<br />

d)<br />

+ 46.4 + 20log10(<br />

fc<br />

5.0)<br />

(4.24)<br />

The distribution of the shadow fading is log-normal, and the standard deviation for each scenario is given<br />

in the table.<br />

Frequency dependencies of <strong>WINNER</strong> path-loss models<br />

The path loss models shown in Table 4-4 are based on measured data obtained mainly at 2 and 5 GHz.<br />

These models have been extended to arbitrary frequencies in the range from 2 – 6 GHz with the aid of the<br />

path loss frequency dependencies defined below. Following various results from the open literature, as<br />

Page 43 (82)

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!