RUMAG introduction

High level view

• RUMAG domain resides in MOAM SC. Its main
responsibility is to communicate with RRU and
manage its resource which is used for Cell
Setup.
• RUMAG has 2 communication points, one is IR
message based on TCP protocol
communicating with RRU, the other is info
model based on message queue towards
BM(data server)
 Design and framework
• RUMAG is running on one thread “controller”. It’s
separated by its design.
• IR message is received by independent thread
“Rhaps_APW_NMAPReceiver” and then delivered to
corresponding OMReactive instances registered to that
thread
• Info model message is received by “lim” thread and then
delievered by “evLimUpdate” oxf message to “controller”
thread.
• This design makes RUMAG more independent and never
block “lim” thread which is high IO consumption.
Design and framework/IRMessage
Design and framework/IMMessage
 Business logic view
• 1st step: RRU communication and
management. Pre-condition: L1L2 syn is done,
RRU detection is done, TCP service is up.
This step including CER, software negotiation,
CEC, periodic RRU delay query, calibration
indication.
Post condition: Toffset, TBdelayDL, TBdelayUL,
T2a, Ta3, N delay is updated to info model.
RU_L/RMOD_L objects is updated to ENABLED
 Business logic view(cont.)
• 2nd step: delay configuration and routingtable apply.
CellP triggers RU_L::ConfigureDevice operation to
RUMAG. RUMAG configures RRU compensation
delay. Apply routing tables created by CellP for
RU_L objects, create IQ data resource for later
usage
Post condition: TX_L/RX_L objects are created and
procedureState is updated to timingsUpdated.
RoutingTable instances are inserted to
RU_L/BBSIWTHC_L
 Business logic view(cont.)
• 3rd step: IQ data configuration and Cell
Configuration. CellP triggers
RU_L::ActivateCarriers operations to RUMAG.
RUMAG starts to configure IQ data and setup
cell, activate cell.
Post condition: RRU resource is applied to
certain cell. TX_L/RX_L’s procedure state is
updated to carrierActivated
 Miscellaneous
• Other sub-components other than device
management and resource configuration, for
example alarm handle, VSWR management.
The trigger of them is either from IR message
or info model execution request from CellP.
IRAgent is under control of CellP which is the
core of L3 software.