Lte Measurement Report

This page will explain about various aspect of Measurement Process that is happe
ning in a LTE. In any technology, Measurement is done roughly at two stage. One
is measurement in Idle mode and the other one is in Connected mode. Idle mode me
asurement is mainly for Cell Selection and Reslection process and most of idle m
ode measurement criteria is determined by SIB messages, the connected mode measu
rement is mostly for Handover or CSFB and the measurement criteria is determined
by specific RRC messages dedicated for a specific UE.
This page will deal with connected mode measurement process only. Idle mode meas
urement is not the scope of this page.
In terms of RRC Message, you may say Measurement Process would be a simple one,
that is,
i) eNB sends an RRC message indicating what kind of items to be measured and
ii) UE sends an RRC message that carries the result of the measurement
You're right at the high level, but you will find it very tricky if you are aske
d to create the RRC message with all the detailed parameters (IE : Information E
lements) to trigger UE to perform the specific measurement. There are so many de
tails you need to understand.
On UE protocol stack as well, implmentating the measurement process would be one
of the most challenging item. According to my experience, it tend to take huge
time and effort to implement all sorts of measurement algorithm and take a lot o
f time for verification process as well.
Topics on this page are as follows.
LTE Measurement Report Trigger (EVENT for Measurement Report)
Measurement GAP
Layer 3 Filtering for Measurement Report
Measurement with CGI report
Example 1 > - Measuring RSRP, RSRQ for current Cell
Example 2 > - Event Based Measurement : A1, A2, A3
Example 3 > - Event Based Measurement : A5
LTE Measurement Report Trigger (EVENT for Measurement Report)

One of the most important step for Handover is Measurement Report from UE before
the handover. Network make a decision on whether it will let UE handover or not
, based on the measurement value from UE. There are many different measurement i
tems and many different ways to measure the signal quality of the current cell (
serving cell) and target cell.
Ideally a network let UE to report the signal quality (usually RSRP) of the curr
ent cell (serving cell) and target cell and set the arbitrary rule for handover.
But this can be too complicated and too much load on network since the network
may need a multiple times of consecutive measurement result in stead of using on
ly a single or a couple of measured signal quality value (Can you think of why o
nly one or a couple of signal quality measurement (RSRP) would not be a good eno
ugh for this kind of decision making ?).
As a kind of solution, 3GPP defines several set of predefined set of measurement
report mechanism to be performed by UE. These predefined measurement report typ
e is called "Event". What kind of "event" a UE has to report is specified by RRC
Connection Reconfiguration message as follows (shown in red).
+-rrcConnectionReconfiguration ::= SEQUENCE
+-rrc-TransactionIdentifier ::= INTEGER (0..3) [0]
+-criticalExtensions ::= CHOICE [c1]
+-c1 ::= CHOICE [rrcConnectionReconfiguration-r8]
+-rrcConnectionReconfiguration-r8 ::= SEQUENCE [100000]
+-measConfig ::= SEQUENCE [01010111111] OPTIONAL:Exist
| +-measObjectToRemoveList ::= SEQUENCE OF OPTIONAL:Omit
| +-measObjectToAddModList ::= SEQUENCE OF SIZE(1..maxObjectId[32]
) [1]
| | +-MeasObjectToAddMod ::= SEQUENCE
| | +-measObjectId ::= INTEGER (1..maxObjectId[32]) [1]
| | +-measObject ::= CHOICE [measObjectEUTRA]
| | +-measObjectEUTRA ::= SEQUENCE [100000]
| | +-carrierFreq ::= INTEGER (0..maxEARFCN[65535]) [6300]
| | +-allowedMeasBandwidth ::= ENUMERATED [mbw25]
| | +-presenceAntennaPort1 ::= BOOLEAN [FALSE]
| | +-neighCellConfig ::= BIT STRING SIZE(2) [01]
| | +-offsetFreq ::= ENUMERATED [dB0] OPTIONAL:Exist
| | +-cellsToRemoveList ::= SEQUENCE OF OPTIONAL:Omit
| | +-cellsToAddModList ::= SEQUENCE OF OPTIONAL:Omit
| | +-blackCellsToRemoveList ::= SEQUENCE OF OPTIONAL:Omit
| | +-blackCellsToAddModList ::= SEQUENCE OF OPTIONAL:Omit
| | +-cellForWhichToReportCGI ::= INTEGER OPTIONAL:Omit
| +-reportConfigToRemoveList ::= SEQUENCE OF OPTIONAL:Omit
| +-reportConfigToAddModList ::= SEQUENCE OF SIZE(1..maxReportConf
igId[32]) [1]
| | +-ReportConfigToAddMod ::= SEQUENCE
| | +-reportConfigId ::= INTEGER (1..maxReportConfigId[32]) [1]
| | +-reportConfig ::= CHOICE [reportConfigEUTRA]
| | +-reportConfigEUTRA ::= SEQUENCE
| | +-triggerType ::= CHOICE [event]
| | | +-event ::= SEQUENCE
| | | +-eventId ::= CHOICE [eventA3]
| | | | +-eventA3 ::= SEQUENCE
| | | | +-a3-Offset ::= INTEGER (-30..30) [0]
| | | | +-reportOnLeave ::= BOOLEAN [FALSE]
| | | +-hysteresis ::= INTEGER (0..30) [0]
| | | +-timeToTrigger ::= ENUMERATED [ms640]
| | +-triggerQuantity ::= ENUMERATED [rsrp]
| | +-reportQuantity ::= ENUMERATED [both]
| | +-maxReportCells ::= INTEGER (1..maxCellReport[8]) [1]
| | +-reportInterval ::= ENUMERATED [ms1024]
| | +-reportAmount ::= ENUMERATED [r1]
Brief description you can find from 3GPP 36.331 5.5.4 Measurement report trigger
ing is as follows. You will see pretty complicated description of the exact proc
edure of each of these events, but if you convert those descriptions into a grap
hical format it would be much easier/intuitive to understand the nature of these
events.
Event Type
Description
Event A1
Serving becomes better than threshold
Event A2
Serving becomes worse than threshold
Event A3
Neighbour becomes offset better than serving
Event A4
Neighbour becomes better than threshold
Event A5
Serving becomes worse than threshold1 and neighbour becomes better than threshol
d2
Event A6
Neighbour become offset better than S Cell (This event is introduced in Release
10 for CA)
Event B1
Inter RAT neighbour becomes better than threshold
Event B2
Serving becomes worse than threshold1 and inter RAT neighbour becomes better tha
n threshold2
Event C1
CSI-RS resource becomes better than threshold
Event C2
CSI-RS resource becomes offset better than reference CSI-RS resource
Following is an illustration showing possible conditions triggering each of the

events A1~A6. Just suppose that you become a UE and generating measurement repor
t following along the timeline. If you don't get confused, you are high quality
UE :)
Simply put, Measurement Report is triggered by whether the measured value crosse
s (goes higher or goes lower) a certain target value. The target value can be se
t by one of two methods. One is to use threshold which is a kind of absolute val
ue and the other one is to use Offsef value which is a kind relative value with
a reference to 'something' like serving cell value. However, in reality the meas
ured value can fluctuate pretty frequently sometimes by measurement error by UE
modem and sometimes by the fluctuation of Radio channel itself. In most case, th
e network would not be interested in such a small fluctuation and does not want
to get too many measurement reports triggered by such a small fluctuation. To pr
ovent this kind of unnecessarily frequent measurement report caused by small ran
ge of fluctuation, the parameter called 'Hysterisis' is introduced. The role of
Hysterysis can be illustrated as below and hope this would make sense to you.
Measurement GAP
Before the handover, UE normally measure the cell power (signal quality) of the
target cell and report it to the network, so that network can make a decision wh
ether to allow UE to handover to the target cell or not.
It is not a big issue to measure the signal quality of the target cell if the ta
rget cell is at the same frequency as the current cell (Intrafrequency measureme
nt). But there would be an issue when the target cell is at a different frequenc
y from the current cell (Interfrequency measurement). Just in terms of logical s
ense of view, the simplest solution for Interfrequency measurement, the simplest
solution for this would be to implement two RF tranciever on UE. However, there
are some practical problems with this kind of two tranciever solution. One of t
he problems is cost issue. It would require additional cost to implement the add
itional tranciever. The other problem would be the possible interference between
the current frequency and target frequency especially when the current frequenc
y and target frequency are close to each other.
So they come out with a special techique called "Measurement GAP". This is the s
ame concept as "Compressed Mode" in UMTS. The idea of the Measurement GAP is to
create a small gap during which no transmission and reception happens. since the
re is no signal transmission and reception during the gap, UE can switch to the
target cell and perform the signal quality measurement and come back to the curr
ent cell.
To make this work seamlessly, there should be a well established agreement betwe
en UE and Network about the gap definition (e.g, Starting Position of the Gap, G
ap length, number of Gaps etc) and this agreement is established by MeasGapConfi
g IE of RRC Connection Reconfiguration message. If you see this part, RRC conten
ts is small but you need to go through several steps as follows to fully underst
and the implementation of the measurement GAP. (The spreadsheet shown at the bot
tom is here. Let me know if you find any problem with this spreadsheet).
One of the complications about the measurement GAP would be how to schedule data
transmission around the gap. Situation would be more complicated than you may t
hink because we have to think about not only the data transmission itself, but a
lso the scheduling grant and ACK/NACK transmission. One of possible scheduling e
xample around measurement gap is as follows.
Layer 3 Filtering for Measurement Report

To be honest, I've never paid attention to this parameter before, but lately I h
eard an apisode of a serious field problem (too frequent handover failure) which
was caused by a wrong implementation of this filter. It is the motivation for m
e to look into this parameter.
It is about the parameter for Layer 3 filtering for the measurement report value
which is specified in rrcConnectionReconfiguration as specified below (in blue)
) [1]
igId[32]) [1]
| | +-triggerType ::= CHOICE [event]
| | | +-event ::= SEQUENCE
| | | +-eventId ::= CHOICE [eventA3]
| | | | +-eventA3 ::= SEQUENCE
| | | | +-a3-Offset ::= INTEGER (-30..30) [0]
| | | | +-reportOnLeave ::= BOOLEAN [FALSE]
| | | +-hysteresis ::= INTEGER (0..30) [0]
| | | +-timeToTrigger ::= ENUMERATED [ms640]
| | +-reportAmount ::= ENUMERATED [r1]
| +-measIdToRemoveList ::= SEQUENCE OF OPTIONAL:Omit
| +-measIdToAddModList ::= SEQUENCE OF SIZE(1..maxMeasId[32]) [1]
OPTIONAL:Exist
| | +-MeasIdToAddMod ::= SEQUENCE
| | +-measId ::= INTEGER (1..maxMeasId[32]) [1]
| +-quantityConfig ::= SEQUENCE [1111] OPTIONAL:Exist
| | +-quantityConfigEUTRA ::= SEQUENCE [11] OPTIONAL:Exist
| | | +-filterCoefficientRSRP ::= ENUMERATED [fc0] OPTIONAL:Exist
| | | +-filterCoefficientRSRQ ::= ENUMERATED [fc0] OPTIONAL:Exist
fc0 in filterCoefficientRSRP IE means "Do not apply Layer 3 filter and report th
e raw measured data". If filterCoefficientRSRP use a value other than fc0, it m
eans "Apply Layer 3 filter with the specified the coefficient". The filter funct
ion and the meaning of each parameter is defined in 3GPP 36.331 5.5.3.2 Layer 3
filtering as follows.
Measurement with CGI report

There is a special type of Measurement Report. Normally Measurement Control/Repo
rt is for detecting the signal strength of the target cell, but CGI report is no
t for measuring the signal strength. It is to detect the Cell ID. It is not a si
mple cell ID, it is to measure CGI (Cell Global Identity) which uniquely identif
ies a cell in the whole world.
For a ordinary measurement report, UE only have to switch its tuner to target ce
ll and measure the signal strength and it does not have to decode any MIB, SIB o
f the target cell. It would take very short time to measure the signal strength.
But it is different story in case of CGI. CGI is made up of PLMN + LAC + Cell I
D. It means UE has to decode MIB/SIBs of the target cell.
Decoding MIB/SIB is not a big issue if it is in idle mode, but the problem is th
at measurement control/report should happen in Connected Mode. Measurement GAP i
n LTE would not give enough time for UE to decode MIB/SIBs of the target cell.
Then how can we give UE enough time to measure MIB/SIBs of target cell in connec
ted mode. You can use DRX for this. Using DRX, you can give UE time long enough
to measure MIB/SIBs of target cell.
One think you have to be careful about DRX is that you have to make it sure that
network should not send any data or UL Grant during the drx cycle. In case of m
easurement gap, measurement gap has high priority than data transmission/recepti
on, but in DRX data transmission or handling UL grant has higher priority than D
RX. It means if UE has any DL data or UL Grant during onTime of DRX cycle it doe
s not goes into OFF period for a certain duration. If network keep sending data
or UL grant during the DRX cycle (see DRX page for details), UE can never gets i
nto OFF period meaning it cannot have time to switch to target cell for CGI dete
ction. In this case, UE would still send Measurement Report but cgi-info field w
ould be missing in the report.
Following is one example of RRC Connection Reconfiguration for CGI Report measur
ement control. See if my description above is properly reflecting the real messa
ge. For the details of this message, refer to following tables from 36.521-1.
Table 8.3.3.2.3.3-7: RRCConnectionReconfiguration (step 5, Table 8.3.3.2.3.2-2)
Table 8.3.3.2.3.3-8 MeasConfig (step 5, Table 8.3.3.2.3.2-2)
Table 8.3.3.2.3.3-9: MeasObjectUTRA-CGI (step 5, Table 8.3.3.2.3.2-2)
Table 8.3.3.2.3.3-10: ReportConfigUTRA-CGI (step 5, Table 8.3.3.2.3.2-2)
Table 8.3.3.2.3.3-11: RadioResourceConfigDedicated-DRX (step 5, Table 8.3.3.2.3.
2-2)
Following is one example of Measurement Report that UE reported.
Example 1 > - Measuring RSRP, RSRQ for current Cell

Following is an example for RRC Connection Reconfiguration (Measurement) for the
current cell (Serving Cell). You would notice that we don't need to configure a
nything about MeasurementGap since UE does not have to jump to other frequencies
for the measurement.
+-c1 ::= CHOICE [rrcConnectionReconfiguration]
+-rrcConnectionReconfiguration ::= SEQUENCE
+-rrc-TransactionIdentifier ::= INTEGER (0..3) [0]
+-c1 ::= CHOICE [rrcConnectionReconfiguration-r8]
) [1] OPTIONAL:Exist
| | +-measObjectEUTRA ::= SEQUENCE [001000]
| | +-carrierFreq ::= INTEGER (0..maxEARFCN[65535]) [2175]
| | +-allowedMeasBandwidth ::= ENUMERATED [mbw50]
| | +-presenceAntennaPort1 ::= BOOLEAN [FALSE]
| | +-neighCellConfig ::= BIT STRING SIZE(2) [00]
| | +-offsetFreq ::= ENUMERATED OPTIONAL:Omit
| | +-cellsToRemoveList ::= SEQUENCE OF OPTIONAL:Omit
| | +-cellsToAddModList ::= SEQUENCE OF SIZE(1..maxCellMeas[
32]) [1] OPTIONAL:Exist
| | | +-CellsToAddMod ::= SEQUENCE
| | | +-cellIndex ::= INTEGER (1..maxCellMeas[32]) [1]
| | | +-physCellId ::= INTEGER (0..503) [0]
| | | +-cellIndividualOffset ::= ENUMERATED [dB-24]
| | +-blackCellsToRemoveList ::= SEQUENCE OF OPTIONAL:Omit
| | +-blackCellsToAddModList ::= SEQUENCE OF OPTIONAL:Omit
| | +-cellForWhichToReportCGI ::= INTEGER OPTIONAL:Omit
igId[32]) [1] OPTIONAL:Exist
| | +-triggerType ::= CHOICE [periodical]
| | | +-periodical ::= SEQUENCE
| | | +-purpose ::= ENUMERATED [reportStrongestCells]
| | +-reportAmount ::= ENUMERATED [infinity]
| +-measIdToRemoveList ::= SEQUENCE OF OPTIONAL:Omit
| +-measIdToAddModList ::= SEQUENCE OF SIZE(1..maxMeasId[32]) [1]
OPTIONAL:Exist
| | +-MeasIdToAddMod ::= SEQUENCE
| | +-measId ::= INTEGER (1..maxMeasId[32]) [1]
| +-quantityConfig ::= SEQUENCE [1000] OPTIONAL:Exist
| | +-quantityConfigEUTRA ::= SEQUENCE [11] OPTIONAL:Exist
| | | +-filterCoefficientRSRP ::= ENUMERATED [fc4] OPTIONAL:Exist
| | | +-filterCoefficientRSRQ ::= ENUMERATED [fc4] OPTIONAL:Exist
| | +-quantityConfigUTRA ::= SEQUENCE OPTIONAL:Omit
| | +-quantityConfigGERAN ::= SEQUENCE OPTIONAL:Omit
| | +-quantityConfigCDMA2000 ::= SEQUENCE OPTIONAL:Omit
| +-measGapConfig ::= CHOICE OPTIONAL:Omit
| +-s-Measure ::= INTEGER OPTIONAL:Omit
| +-preRegistrationInfoHRPD ::= SEQUENCE OPTIONAL:Omit
| +-speedStatePars ::= CHOICE OPTIONAL:Omit
+-mobilityControlInfo ::= SEQUENCE OPTIONAL:Omit
+-dedicatedInfoNASList ::= SEQUENCE OF OPTIONAL:Omit
+-radioResourceConfigDedicated ::= SEQUENCE OPTIONAL:Omit
+-securityConfigHO ::= SEQUENCE OPTIONAL:Omit
+-nonCriticalExtension ::= SEQUENCE OPTIONAL:Omit
An example of Measurement Report for the measurement configuration specified abo
ve is as follows.
+-c1 ::= CHOICE [measurementReport]
+-measurementReport ::= SEQUENCE
+-c1 ::= CHOICE [measurementReport-r8]
+-measurementReport-r8 ::= SEQUENCE [0]
+-measResults ::= SEQUENCE [0]
| +-measId ::= INTEGER (1..maxMeasId[32]) [1]
| +-measResultServCell ::= SEQUENCE
| | +-rsrpResult ::= INTEGER (0..97) [52]
| | +-rsrqResult ::= INTEGER (0..34) [18]
| +-measResultNeighCells ::= CHOICE OPTIONAL:Omit
+-nonCriticalExtension ::= SEQUENCE OPTIONAL:Omit
Example 2 > - Event Based Measurement : A1, A2, A3

Following is an example log captured in live network with Azenqos tool . In this
example, network configures various measurement objects simultaneously with mul
tiple different events. You wouldn't see the event based measurement report in t
his example (since UE didn't meet the condition for those events), but you will
see the good examples how multiple different events are defined in a single rrc
message and how UE report those multiple measurement. Usually measurements confi
guration in live network is much more complicated than those settings in the tes
t equipment. So this can be a very practical examples for you.
DL-DCCH-Message ::= {
message: c1: rrcConnectionReconfiguration: RRCConnectionReconfiguration ::=
{
rrc-TransactionIdentifier: 3
criticalExtensions: c1: rrcConnectionReconfiguration-r8:
RRCConnectionReconfiguration-r8-IEs ::= {
measConfig: MeasConfig ::= {
measObjectToAddModList: MeasObjectToAddModList ::= {
MeasObjectToAddMod ::= {
measObjectId: 1
measObject: measObjectEUTRA: MeasObjectEUTRA ::= {
carrierFreq: 1300
allowedMeasBandwidth: 3 (mbw50)
presenceAntennaPort1: FALSE
neighCellConfig: '01'
offsetFreq: 15 (dB0)
cellsToAddModList: CellsToAddModList ::= {
CellsToAddMod ::= {
cellIndex: 1
physCellId: 290
cellIndividualOffset: 15 (dB0)
}
}
}
}
}
reportConfigToAddModList: ReportConfigToAddModList ::= {
ReportConfigToAddMod ::= {
reportConfigId: 1
reportConfig: reportConfigEUTRA: ReportConfigEUTRA ::= {
triggerType: event: event ::= {
eventId: eventA3: eventA3 ::= {
a3-Offset: 2
reportOnLeave: FALSE
}
hysteresis: 2
timeToTrigger: 8 (ms320)
}
triggerQuantity: 0 (rsrp)
reportQuantity: 0 (sameAsTriggerQuantity)
maxReportCells: 4
reportInterval: 1 (ms240)
reportAmount: 7 (infinity)
reportconfigeutra-ext1: reportconfigeutra-ext1 ::= {
reportAddNeighMeas-r10: 0 (setup)
}
}
}
reportConfigId: 2
a3-Offset: -20
reportOnLeave: TRUE
}
hysteresis: 4
}
reportQuantity: 1 (both)
maxReportCells: 8
}
}
}
reportConfigId: 3
a1-Threshold: threshold-RSRP: 37
}
hysteresis: 2
}
maxReportCells: 1
reportAmount: 0 (r1)
}
}
reportConfigId: 4
}
hysteresis: 2
}
maxReportCells: 1
}
}
reportConfigId: 5
}
hysteresis: 2
}
maxReportCells: 1
}
}
reportConfigId: 6
}
hysteresis: 2
}
maxReportCells: 1
}
}
}
measIdToAddModList: MeasIdToAddModList ::= {
MeasIdToAddMod ::= {
measId: 1
measObjectId: 1
reportConfigId: 1
}
measId: 2
measObjectId: 1
reportConfigId: 2
}
measId: 3
measObjectId: 1
reportConfigId: 3
}
measId: 4
measObjectId: 1
reportConfigId: 4
}
measId: 5
measObjectId: 1
reportConfigId: 5
}
measId: 6
measObjectId: 1
reportConfigId: 6
}
}
quantityConfig: QuantityConfig ::= {
quantityConfigEUTRA: QuantityConfigEUTRA ::= {
filterCoefficientRSRP: 6 (fc6)
filterCoefficientRSRQ: 6 (fc6)
}
}
s-Measure: 0
speedStatePars: release: <present>
}
}
}
}
Now UE reports multiple measurement reports for each measurement ID.

UL-DCCH-Message ::= {
message: c1: measurementReport: MeasurementReport ::= {
criticalExtensions: c1: measurementReport-r8: MeasurementReport-r8-IEs :
:= {
measResults: MeasResults ::= {
measId: 2
measResultPCell: measResultPCell ::= {
rsrpResult: 21
rsrqResult: 10
}
measResultNeighCells: measResultListEUTRA: MeasResultListEUTRA :
:= {
MeasResultEUTRA ::= {
physCellId: 284
measResult: measResult ::= {
rsrpResult: 20
rsrqResult: 17
}
}
}
measresults-ext0: measresults-ext0 ::= {
}
measResultServFreqList-r10: MeasResultServFreqList-r10 ::= {
MeasResultServFreq-r10 ::= {
servFreqId-r10: 1
measResultSCell-r10: measResultSCell-r10 ::= {
rsrpResultSCell-r10: 29
rsrqResultSCell-r10: 23
}
}
}
}
}
}
}
}
:= {
measId: 4
rsrpResult: 21
rsrqResult: 10
}
}
servFreqId-r10: 1
}
}
}
}
}
}
}
}
:= {
measId: 6
rsrpResult: 21
rsrqResult: 10
}
}
servFreqId-r10: 1
}
}
}
}
}
}
}
}
Example 3 > - Event Based Measurement : A5

Following is an example log captured in live network with Azenqos tool . In this
example, network configures various measurement objects simultaneously with mul
tiple different events. You wouldn't see the event based measurement report in t
his example (since UE didn't meet the condition for those events), but you will
see the good examples how multiple different events are defined in a single rrc
message and how UE report those multiple measurement. Usually measurements confi
guration in live network is much more complicated than those settings in the tes
t equipment. So this can be a very practical examples for you.
DL-DCCH-Message ::= {
message: c1: rrcConnectionReconfiguration: RRCConnectionReconfiguration ::=
{
rrc-TransactionIdentifier: 0
criticalExtensions: c1: rrcConnectionReconfiguration-r8:
RRCConnectionReconfiguration-r8-IEs ::= {
measConfig: MeasConfig ::= {
measObjectToAddModList: MeasObjectToAddModList ::= {
measObjectId: 2
carrierFreq: 251
measobjecteutra-ext0: measobjecteutra-ext0 ::= {
measCycleSCell-r10: 2 (sf320)
}
}
}
measObjectId: 3
carrierFreq: 1275
}
}
}
reportConfigToAddModList: ReportConfigToAddModList ::= {
reportConfigId: 7
a5-Threshold1: threshold-RSRP: 31
a5-Threshold2: threshold-RSRP: 37
}
hysteresis: 2
}
maxReportCells: 4
}
}
}
reportConfigId: 8
a3-Offset: 2
reportOnLeave: FALSE
}
hysteresis: 2
}
maxReportCells: 4
}
}
}
}
measIdToAddModList: MeasIdToAddModList ::= {
measId: 7
measObjectId: 2
reportConfigId: 7
}
measId: 8
measObjectId: 3
reportConfigId: 8
}
}
measGapConfig: setup: setup ::= {
gapOffset: gp0: 32
}
}
}
}
}
Followings are the measurement report from UE based on the configuration shown a
bove. Here again, there is no report about Event 5 or 3 configured above sinec U
E didn't hit the condition for those events in this test.
:= {
measId: 2
rsrpResult: 19
rsrqResult: 6
}
measResultNeighCells: measResultListEUTRA: MeasResultListEUTRA :
:= {
physCellId: 284
rsrpResult: 20
rsrqResult: 17
}
}
physCellId: 288
rsrpResult: 17
rsrqResult: 8
}
}
}
}
servFreqId-r10: 1
}
measResultBestNeighCell-r10: measResultBestNeighCell
-r10 ::= {
physCellId-r10: 284
rsrpResultNCell-r10: 26
rsrqResultNCell-r10: 19
}
}
}
}
}
}
}
}

Lte Measurement Report

Загружено:

Сведения о документе

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Lte Measurement Report

Загружено:

Авторское право:

Доступные форматы

This page will explain about various aspect of Measurement Process that is happe

LTE Measurement Report Trigger (EVENT for Measurement Report)

Following is an illustration showing possible conditions triggering each of the

Layer 3 Filtering for Measurement Report

Measurement with CGI report

Following is one example of Measurement Report that UE reported.

Example 1 > - Measuring RSRP, RSRQ for current Cell

Example 2 > - Event Based Measurement : A1, A2, A3

Now UE reports multiple measurement reports for each measurement ID.

Example 3 > - Event Based Measurement : A5

Вам также может понравиться