F5/unison
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

documented lte-rrc test suite

Browse Source
This commit is contained in:
Nicola Baldo
2012-12-14 14:52:40 +01:00
parent 9b5ceb07af
commit 15057b0a4e
2 changed files with 124 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

79
src/lte/doc/source/lte-testing.rst
View File

@@ -504,6 +504,85 @@ transmitted by the RLC instance, both the size and the content of the
PDU are verified to check for an exact match with the test vector.
RRC
---
The test suite ``lte-rrc`` tests the correct functionality of the following aspects:
#. MAC Random Access
#. RRC System Information Acquisition
#. RRC Connection Establishment
#. RRC Reconfiguration
The test suite considers a type of scenario with a single eNB and multiple UEs that are instructed to connect to the eNB. Each test case implement an instance of this scenario with specific values of the following parameters:
- number of UEs
- number of Data Radio Bearers to be activated for each UE
- time :math:`t^c_0` at which the first UE is instructed to start connecting to the eNB
- time interval :math:`d^i` between the start of connection of UE :math:`n` and UE :math:`n+1`; the time at which user :math:`n` connects is thus determined as :math:`t^c_n = `t^c_0 + n d^i` sdf
- a boolean flag indicating whether the ideal or the real RRC protocol model is used
Each test cases passes if a number of test conditions are positively evaluated for each UE after a delay :math:`d^e` from the time it started connecting to the eNB. The delay :math:`d^e` is determined as
.. math::
d^e = d^{si} + d^{ra} + d^{ce} + d^{cr}
where:
- :math:`d^{si}` is the max delay necessary for the acquisition of System Information. We set it to 90ms accounting for 10ms for the MIB acquisition and 80ms for the subsequent SIB2 acquisition
- :math:`d^{ra}` is the delay for the MAC Random Access (RA)
procedure. This depends on preamble collisions as well as on the
availability of resources for the UL grant allocation. The total amount of
necessary RA attempts depends on preamble collisions and failures
to allocate the UL grant because of lack of resources. The number
of collisions depends on the number of UEs that try to access
simultaneously; we estimated that for a :math:`0.99` RA success
probability, 5 attempts are sufficient for up to 20 UEs, and 10
attempts for up to 50 UEs. For the UL
grant, considered the system bandwidth and the
default MCS used for the UL grant (MCS 0), at most 4 UL grants can
be assigned in a TTI; so for :math:`n` UEs trying to
do RA simultaneously the max number of attempts due to the UL grant
issue is :math:`\lceil n/4 \rceil`. The time for
a RA attempt is determined by 3ms + the value of
LteEnbMac::RaResponseWindowSize, which defaults to 3ms, plus 1ms
for the scheduling of the new transmission.
- :math:`d^{ce}` is the delay required for the transmission of RRC CONNECTION
SETUP + RRC CONNECTION SETUP COMPLETED. We consider a round trip
delay of 10ms plus :math:`\lceil 2n/4 \rceil` considering that 2
RRC packets have to be transmitted and that at most 4 such packets
can be transmitted per TTI.
- :math:`d^{cr}` is the delay required for eventually needed RRC
CONNECTION RECONFIGURATION transactions. The number of transactions needed is
1 for each bearer activation plus a variable number for SRS
reconfiguration that depends on:math:`n`:
+ 0 for :math:`n \le 2`
+ 1 for :math:`n \le 5`
+ 2 for :math:`n \le 10`
+ 3 for :math:`n \gt 10`
Similarly to what done for :math:`d^{ce}`, for each transaction we consider a round trip
delay of 10ms plus :math:`\lceil 2n/4 \rceil`.
delay of 20ms.
The conditions that are evaluated for a test case to pass are, for
each UE:
- the eNB has the context of the UE (identified by the RNTI value
retrieved from the UE RRC)
- the RRC state of the UE at the eNB is CONNECTED_NORMALLY
- the RRC state at the UE is CONNECTED_NORMALLY
- the UE is configured with the CellId, DlBandwidth, UlBandwidth,
DlEarfcn and UlEarfcn of the eNB
- the IMSI of the UE stored at the eNB is correct
- the number of active Data Radio Bearers is the expected one, both
at the eNB and at the UE
- for each Data Radio Bearer, the following identifiers match between
the UE and the eNB: EPS bearer id, DRB id, LCID

47
src/lte/test/test-lte-rrc.cc
View File

@@ -23,7 +23,7 @@
#include <ns3/network-module.h>
#include <ns3/mobility-module.h>
#include <ns3/lte-module.h>
#include <cmath>
NS_LOG_COMPONENT_DEFINE ("LteRrcTest");
@@ -89,11 +89,51 @@ LteRrcConnectionEstablishmentTestCase::LteRrcConnectionEstablishmentTestCase (ui
m_nBearers (nBearers),
m_tConnBase (tConnBase),
m_tConnIncrPerUe (tConnIncrPerUe),
m_delayConnEnd (140+nUes*8/4), // includes: time to receive system information, time for Random Access (RACH preamble, RAR response), time to send and receive RRC connection request+setup+completed. Value should be slightly higher than T300 in TS 36.331
m_delayDiscStart (delayDiscStart),
m_delayDiscEnd (10),
m_useIdealRrc (useIdealRrc)
{
// see the description of d^e in the LTE testing docs
double dsi = 90;
double nRaAttempts = 0;
if (nUes <= 20)
{
nRaAttempts += 5;
}
else
{
NS_ASSERT (nUes <= 50);
nRaAttempts += 10;
}
nRaAttempts += std::ceil (nUes/4.0);
double dra = nRaAttempts * 7;
double dce = 10.0 + (2.0*nUes)/4.0;
double nCrs;
if (nUes <= 2)
{
nCrs = 0;
}
else if (nUes <= 5)
{
nCrs = 1;
}
else if (nUes <= 10)
{
nCrs = 2;
}
else if (nUes <= 20)
{
nCrs = 3;
}
else
{
nCrs = 4;
}
double dcr = (10.0 + (2.0*nUes)/4.0)*(m_nBearers + nCrs);
m_delayConnEnd = round (dsi + dra + dce + dcr);
NS_LOG_LOGIC (this << GetName () << " dsi=" << dsi << " dra=" << dra << " dce=" << dce << " dcr=" <<dcr << " m_delayConnEnd=" << m_delayConnEnd);
}
void
@@ -253,6 +293,9 @@ LteRrcTestSuite::LteRrcTestSuite ()
: TestSuite ("lte-rrc", SYSTEM)
{
NS_LOG_FUNCTION (this);
AddTestCase (new LteRrcConnectionEstablishmentTestCase ( 50, 0, 0, 0, 1, 0));
for (uint32_t useIdealRrc = 0; useIdealRrc <= 1; ++useIdealRrc)
{
// <----- all times in ms ----------------->