Main Content

winner2.layoutparset

WINNER II layout parameter configuration

Description

Download Required: To use winner2.layoutparset, first download the WINNER II Channel Model for Communications Toolbox add-on.

cfgLayout = winner2.layoutparset(msIdx,bsIdx,K,arrays) returns a structure of randomly generated WINNER II network layout parameters given mobile station (MS) indices, base station (BS) indices, BS to MS links, and antenna array configurations.

cfgLayout = winner2.layoutparset(msIdx,bsIdx,K,arrays,rmax) additionally specifies the maximum layout range used when generating MS and BS positions.

example

cfgLayout = winner2.layoutparset(msIdx,bsIdx,K,arrays,rmax,seed) additionally specifies a seed value for repeatability. To assign seed when not assigning rmax, specify rmax as [ ].

Examples

collapse all

Create a WINNER II system layout with two mobile stations (MS) connecting to the same base station (BS).

Define antenna arrays for one BS and two MS.

BSAA  = winner2.AntennaArray('UCA', 8, 0.02);  % UCA-8 array for BS
MSAA1 = winner2.AntennaArray('ULA', 2, 0.01);  % ULA-2 array for MS
MSAA2 = winner2.AntennaArray('ULA', 4, 0.005); % ULA-4 array for MS

Create system layout by using the winner2.layoutparset function.

MSIdx = [2 3]; 
BSIdx = {1}; 
K = 2; 
rndSeed = 5;
cfgLayout = winner2.layoutparset(MSIdx,BSIdx, ...
    K,[BSAA,MSAA1,MSAA2],[],rndSeed);

Visualize BS and MS positions.

BSPos  = cfgLayout.Stations(cfgLayout.Pairing(1,1)).Pos;
MS1Pos = cfgLayout.Stations(cfgLayout.Pairing(2,1)).Pos;
MS2Pos = cfgLayout.Stations(cfgLayout.Pairing(2,2)).Pos;

plot3(BSPos(1),BSPos(2),BSPos(3),'bo', ...
    MS1Pos(1),MS1Pos(2),MS1Pos(3),'rs', ...
    MS2Pos(1),MS2Pos(2),MS2Pos(3),'rd');
grid on;
xlim([0 500]);
ylim([0 500]);
zlim([0 35]);
xlabel('X-position (m)');
ylabel('Y-position (m)');
zlabel('Elevation (m)');
legend('BS','MS1','MS2','Location','northeast');

Input Arguments

collapse all

Mobile station index, specified as a row vector indicating the indices in arrays to serve as mobile stations.

Data Types: double

Base station index, specified as a column cell array, with each element representing one base station. Each cell element is an integer-valued row vector to indicate the indices in arrays to serve as different sectors of that base station.

Data Types: double

Number of links, specified as a scalar representing the number of BS-MS links to be formulated.

Data Types: double

Antenna array configurations, specified as a vector of structures defining all available arrays. All MS and BS sectors are chosen from this vector. The array of elements is typically created using the winner2.AntennaArray function.

Data Types: double

Maximum layout range, specified as a scalar representing the maximum layout range in meters used to randomly generate the MS and BS positions.

Data Types: double

Seed value used to provide repeatability, specified as an integer. When seed is not specified, the global random number generator is used. To assign seed when not assigning rmax, specify rmax as [].

Data Types: double

Output Arguments

collapse all

Configuration layout, returned as a structure containing these fields, which represent the location and orientation parameters for all simulated stations.

Active stations, returned as a row vector of structures describing the antenna arrays for active stations. Stations is created from the arrays input and adds an additional Velocity field. The row ordering specifies base station (BS) sectors first, followed by the mobile stations (MS). The BS sector and MS positions are randomly assigned. The BS sectors have no velocity. Each MS has a velocity of about 1.42 m/s with a randomly assigned direction.

Number of sectors, returned as a vector indicating the number of sectors in each BS.

BS to MS pairing, returned as a 2-by-NL matrix, where NL specifies the number of links to be modeled. See Stations for BS and MS row ordering.

Spatial scenario, returned as a 1-by-NL vector of scenario numbers. The default is 1, which specifies scenario A1.

The scenarios numbers map as {1=A1, 2=A2, 3=B1, 4=B2, 5=B3, 6=B4, 10=C1, 11=C2, 12=C3, 13=C4, 14=D1, 15=D2a}.

For more information, see WINNER II Channel Models [1], Section 2.3.

Propagation condition, returned as a 1-by-NL vector of propagation conditions (LOS = 1 and NLOS = 0) for each link. The default is 1.

Street width, returned as a 1-by-NL vector of identical values that specify the average width (in meters) of the streets. StreetWidth is used for the path loss model of the B1 and B2 scenarios. See ScenarioVector for the scenario number mapping. All elements must have the same value. StreetWidth applies only when the PathLossModelUsed field from winner2.wimparset is set to 'yes'.

Distances from BS to the last LOS point, returned as a 1-by-NL vector. Dist1 is used for the path loss model of the B1 and B2 scenarios. The default value of NaN indicates that the distance is randomly determined in path loss function. See ScenarioVector for the scenario number mapping. Dist1 applies only when the PathLossModelUsed field from winner2.wimparset is set to 'yes'.

For more information, see WINNER II Channel Models [1], Figure 4-3.

Floor numbers, returned as a 1-by-NL vector indicating the floor number where the indoor BS or MS is located. The NumFloors property is used for the path loss model of the A2 and B4 scenarios only. See ScenarioVector for the scenario number mapping. NumFloors applies only when the PathLossModelUsed field from winner2.wimparset is set to 'yes'.

Number of floors penetrated, returned as a 1-by-NL vector indicating the number of penetrated floors between BS and MS. The NumPenetratedFloors property is used for the NLOS path loss model of the A1 scenario. See ScenarioVector for the scenario number mapping. NumPenetratedFloors applies only when the PathLossModelUsed field from winner2.wimparset is set to 'yes'.

For more information, see WINNER II Channel Models [1], Table 4-4.

References

[1] Kyosti, Pekka, Juha Meinila, et al. WINNER II Channel Models. D1.1.2 V1.2. IST-4-027756 WINNER II, September 2007.

Version History

Introduced in R2017a