...
"CellReports" table containing the following fields:
Timestamp
- PLMN (tag)
- KPMNodeID (tag) - The KPM Node identification in string form to accomodate the many binary variants (maybe an hex dump?)
- S-NSSAI (tag?) - useful to identify slices?
NRCellIdentity (tag?)
Any of the fields defined for cell reports in TS 28.552, for example the following are provided by RIC Test scenario generator:DRB.UEThpDl - Average DL throughput in Kb/s
RRU.PrbUsedDl / RRU.PrbAvailDl
RRU.PrbUsedUl / RRU.PrbAvailUl
QosFlow.PdcpPduVolumeUl -UL PDCP PDU Data Volume (amount of kilobytes in the reporting period)
QosFlow.PdcpPduVolumeDLPdcpPduVolumeDl - DL PDCP PDU Data Volume (amending inconsistency in the case of the final "L" in TS 28.552)
And proprietary extensions:Viavi.Geo.x - Non standard / Viavi proprietary extension / External enrichment
Viavi.Geo.y
- Viavi.Geo.z
"UeReports" measurement table containing the following fields:
Timestamp
UE.Id - String representation to accomodate the many forms.
Note: A "UE id resolution" xApp may be needed to match the same UE on different measurements and possibly producing unique ids for this fieldSlice.Id
DRB.UEThpDl - TS 28.552 Average DL UE throughput
RRU.PrbUsedDl - TS 28.552 DL PRB used for data traffic
Viavi.Geo.x”, .y, .z... Viavi proprietary extensions
RF.serving.Id - May be just the PCI or resolved into NRCellIdentity
RF.serving.RSRP (Loosely based on LTE specs)
RF.serving.RSRQ
RF.serving.RSSINR
RF.nb1.CellId - 1st neighbour id
RF.nb1.RSRP, etc. 1st neighbour signal levels
RF.nb2.CellId - 2nd neighbour id
RF.nb2.RSRP, etc. 2nd neighbour signal levels
- "cellMeasReport" cell load measurement table has the following fields:
- Timestamp
- DLOccupyPRBNum – 3GPP supported
- CellDLMACRate – proprietary
- ULSINR – proprietary
- MCS – proprietary
- PDCPOccupBuffer – proprietary
- PDCPUnusedBuffer – proprietary
- DLPacketDiscardNum – proprietary
- DLPacketSDUNum – 3GPP supported
- DLPacketLossNum – 3GPP supported
- DLMACRate – proprietary
...