Protocols Used in OSS, NMS & EMS - Telecom Management Interfaces

Example 1: The 5G Network Surge (gNMI in Action)

During a large stadium event, hundreds of thousands of fans simultaneously use 5G to stream video. Traditional SNMP polling every 5 minutes would miss the real-time congestion.

• Protocol: gNMI streaming telemetry pushes PRB (Physical Resource Block) utilization data every 500ms.
• OSS Action: Analytics detects a sustained spike and triggers an automated scale-out of core network resources.
• Result: Fans enjoy smooth streaming, and the operator avoids SLA penalties.

Why do OSS engineers care about routing protocols? Because if the "map" breaks, customers can't reach the internet. OSS monitors these protocols to detect outages before customers complain.

CLI is like a direct conversation with the router. You type a command, the device executes it, and shows you the result. It's the "manual transmission" of network management - powerful, but requires a skilled driver.

$ ssh admin@192.168.1.100

router> enable
router# show interfaces GigabitEthernet0/1
router# configure terminal
router(config)# interface GigabitEthernet0/1
router(config-if)# description Link_to_Mumbai_PE
router(config-if)# no shutdown

router# show interfaces GigabitEthernet0/1

GigabitEthernet0/1 is up, line protocol is up
  Hardware: Gigabit Ethernet
  Description: Link_to_Mumbai_PE
  Internet address: 10.1.1.1/30
  MTU 1500 bytes, BW 1000000 Kbit/sec
  5 min input rate 12000 bits/sec

NETCONF is like filling out a standardized government form instead of writing a letter. It uses a structured format (XML) so computers can read it reliably. It also has a "draft mode" (candidate config) to test changes before applying them live.

<rpc>
  <get-config>
    <source><running/></source>
    <filter>
      <interface>GigabitEthernet0/1</interface>
    </filter>
  </get-config>
</rpc>

// edit-config → validate (optional) → commit

1. edit-config (make changes in draft)
2. validate (check for errors)
3. commit (apply to live network)

gNMI is like a live stock ticker instead of checking the price every hour. The device pushes data continuously, so the OSS sees problems instantly.

{
  "subscribe": {
    "subscription": [{
      "path": {"elem": [{"name": "interfaces"},{"name":"counters"}]},
      "sample_interval": 1000000000  // every 1 second
    }],
    "mode": "STREAM"
  }
}

{
  "update": {
    "timestamp": 1704787200000,
    "update": [{
      "path": "counters/in-octets",
      "val": {"uintVal": 987654321}
    }]
  }
}

SNMP is the traditional monitoring protocol used in telecom and enterprise networks. The OSS can poll devices for counters and status information, while devices can also send unsolicited traps or informs when important events occur.

SNMP Version: 2c
Community: public
Request ID: 12345
Variable Bindings:
  OID: ifHCInOctets.1
  OID: ifHCOutOctets.1

// Device initiates this

PDU Type: TRAP
snmpTrapOID.0 = linkDown
ifIndex.1 = 1
ifDescr.1 = "GigabitEthernet0/1"

TL1 is the language of optical transport networks (fiber). It's text-based and can send autonomous alarms. Think of it as the "Morse code" of optical networking - old but still in use.

RTRV-EQPT::SHELF-1:1234;
ENT-CRS-VT1::SRC-1-1-1-1,DST-2-2-2-2:4567;

M  1234 COMPLD
   "SHELF-1:TYPE=OPTICAL,STATUS=IS-NR"
;

// Autonomous Alarm

A  7890 REPT ALM
   "SHELF-1:CR,LOS,SA,,,";

CORBA and SOAP/XML were the "glue" that connected OSS to BSS before modern APIs. They are heavy and complex, but many telecoms still rely on them.

<soapenv:Envelope>
  <soapenv:Body>
    <getSubscriberInfoRequest>
      <msisdn>9876543210</msisdn>
    </getSubscriberInfoRequest>
  </soapenv:Body>
</soapenv:Envelope>

<soapenv:Body>
  <getSubscriberInfoResponse>
    <status>ACTIVE</status>
    <balance>250.00</balance>
  </getSubscriberInfoResponse>
</soapenv:Body>

RESTCONF is a modern, web-friendly interface for managing devices using HTTP and YANG-based data models. It is commonly used alongside NETCONF in automation-focused environments.

GET /restconf/data/interfaces/interface=Gig0/1
Host: router.example.com
Accept: application/yang-data+json

// GET Response

{"interface": {
  "name": "Gig0/1",
  "enabled": true
}}

// PATCH to update

PATCH /restconf/data/...
{"interface": {"enabled": false}}

Modern OSS platforms don't just collect data; they react instantly using event-driven systems like Apache Kafka and observability pipelines (OpenTelemetry).