Skip to main content
← All tracks

Track · 6 modules

Multi-vendor integration patterns

What neither RAN training nor ML training teaches you — the seams between vendors

For: Engineers (any background) who have seen "Nokia NRCELL ≠ Ericsson NRCellDU" and want to never write that bridge twice.

  1. 01

    MO mapping across vendors

    A practical translation table + how to keep it from drifting.

    ~18 min○ planned
  2. 02

    Counter translation and KPI normalization

    Vendor-specific counter names, why a "single KEY_KPI_MAPPING" dict rots, the DB-backed approach.

    ~22 min○ planned
  3. 03

    Alarm severity mapping (X.733 ↔ vendor)

    Critical/major/minor across NetAct, ENM, MantisBT-style — how to normalise without losing signal.

    ~15 min○ planned
  4. 04

    O-RAN R1 and the SMO interface

    NONRTRIC, A1 policies, what R1 gives you that proprietary M-plane doesn't.

    ~25 min○ planned
  5. 05

    Cell identifier resolution across vendors

    The hard part — turning Nokia's NRCELL-3 into a globally-unique cell handle.

    ~20 min○ planned
  6. 06

    Change management when vendors disagree

    Rollback strategy, two-system Q/A, the operator's "no breaking changes" floor.

    ~18 min○ planned