Pages

Tuesday, 1 November 2011

RRC Signalling in Rel-10 for MDT

Last year I wrote about Minimization of Drive Testing (MDT) and mentioned about the possibility of enhancements. Now looking at the new RRC specs I can see a new message LoggedMeasurementsConfiguration has been added,
When the UE is in RRC_CONNECTED mode, this message can be sent and the UE be informed about the measurements to be performed. The message contents are as follows:

LoggedMeasurementConfiguration-r10 ::= SEQUENCE {
criticalExtensions CHOICE {
c1 CHOICE {
loggedMeasurementConfiguration-r10 LoggedMeasurementConfiguration-r10-IEs,
spare3 NULL, spare2 NULL, spare1 NULL
},
criticalExtensionsFuture SEQUENCE {}
}
}


LoggedMeasurementConfiguration-r10-IEs ::= SEQUENCE {
traceReference-r10 TraceReference-r10,
traceRecordingSessionRef-r10 OCTET STRING (SIZE (2)),
tce-Id-r10 OCTET STRING (SIZE (1)),
absoluteTimeInfo-r10 AbsoluteTimeInfo-r10,
areaConfiguration-r10 AreaConfiguration-r10 OPTIONAL, -- Need OR
loggingDuration-r10 LoggingDuration-r10,
loggingInterval-r10 LoggingInterval-r10,
nonCriticalExtension SEQUENCE {} OPTIONAL -- Need OP
}


Once the UE has done the measurements, it can inform the network in one of the following messages, RRCConnectionSetupComplete, RRCConnectionReestablishmentComplete, RRCConnectionReconfigurationComplete and UEInformationResponse that it has the required information available. This is done by including the following new Enum:

logMeasAvailable-r10 ENUMERATED {true} OPTIONAL,

Finally, the network can request the logged Measurements information in the UE Information Request Message. The new fields for that are:


UEInformationRequest-v1020-IEs ::= SEQUENCE {
logMeasReportReq-r10 ENUMERATED {true} OPTIONAL,
nonCriticalExtension SEQUENCE {} OPTIONAL
}

The UE would send the following information in the response message:


LogMeasInfo-r10 ::= SEQUENCE {
locationInfo-r10 LocationInfo-r10 OPTIONAL,
relativeTimeStamp-r10 INTEGER (0..7200),
servCellIdentity-r10 CellGlobalIdEUTRA,
measResultServCell-r10 SEQUENCE {
rsrpResult-r10 RSRP-Range,
rsrqResult-r10 RSRQ-Range
},
measResultNeighCells-r10 SEQUENCE {
measResultListEUTRA-r10 MeasResultList2EUTRA-r9 OPTIONAL,
measResultListUTRA-r10 MeasResultList2UTRA-r9 OPTIONAL,
measResultListGERAN-r10 MeasResultList2GERAN-r10 OPTIONAL,
measResultListCDMA2000-r10 MeasResultList2CDMA2000-r9 OPTIONAL
} OPTIONAL,
...
}


MeasResultList2GERAN-r10 ::= SEQUENCE (SIZE (1..maxCellListGERAN)) OF MeasResultListGERAN


LocationInfo-r10 ::= SEQUENCE {
locationCoordinates-r10 CHOICE {
ellipsoid-Point-r10 OCTET STRING,
ellipsoidPointWithAltitude-r10 OCTET STRING,
...
},
horizontalVelocity-r10 OCTET STRING OPTIONAL,
gnss-TOD-msec-r10 OCTET STRING OPTIONAL,
...
}

No comments: