Remote OLT Orchestration

In today’s ecosystem, network providers have to deal with increasing bandwidth demand to be able to support high-end users’ expectations. This also includes internal requirements. They are required to add new technologies to their own infrastructure to offer the best experience, while doing everything with the same or even less cost and effort.

Bandwidth in the last mile of communications has historically been one of the challenges that operators had to deal with. Passive Optical Network (GPON) technology has been an effective approach for solving this problem.

Traditional OLT architecture

A traditional GPON network consists of:

  • Optical Line Terminal (OLT): The central office equipment that sends and receives data from the ONUs. It also manages the network and provides connectivity to the wider internet.
  • Optical Network Units (ONUs): The customer premises equipment that connects the customer’s devices (e.g., computers, routers) to the GPON network.
  • Passive Splitters

The GPON OLT system is typically installed in the Carrier’s Central Office (CO), aggregating the traffic from all the connected ONTs/ONUs. 

A traditional OLT has all of its functions in PON-specific hardware; this includes Line Cards and switches, the PON MAC layer, the PON physical layer, control software, and layer 2/3 switching. Behind an OLT, a standard network usually has an Ethernet Switch and a router.

Evolution of the OLT architecture – Remote OLT

As previously described, the OLT can be split into different components; we can divide it into two big worlds: the generic networking functions and the specific PON pieces. These pieces include Bridging, MAC Layer, and Physical Layer. An SFP transceiver with all the PON-related pieces allows for small, modular, and low-power Fiber Node solutions. The rest of the generic network functions can be performed using SDN and reusing the already existing switches.

This translates into an immediate reduction of costs when eliminating PON-specific hardware, a lower power consumption, and a footprint reduction. 

This architecture change benefits the Network providers, but now a new problem arises. These SPF transceivers need to be orchestrated. Here is where Symphonica comes into action.

Remote OLT Orchestration Using Symphonica

Symphonica is a No-Code Integration Framework to quickly and easily integrate complex network devices and virtual services. Providing a codeless integration engine where network devices and external systems on the southbound interfaces can be easily integrated, not only by using simple Webservices or Restful APIs, but also via other protocols like SNMP, LDAP, SQL, and Command-Line Interfaces like TL1, SSH, Telnet, and Netconf, among others.

Integration to all networking technologies and other applications is supported by the Symphonica Integration Engine and accomplished through point-and-click configurations and without writing a single line of code. In addition, Symphonica provides several pre-built configuration packages for previously implemented technology and use cases.

In the remote OLT orchestration scenarios, a standardized NETCONF/YANG interface is being used to configure the pluggable OLTs and the switch hardware. These are repeatable tasks that can be performed by Symphonica from a single point to the different network elements. This level of automation and abstraction from proprietary vendor methods grants the user full control of the configuration process just by pointing and clicking; no code is needed.

Symphonica simplifies and accelerates implementations, time-to-market, and the addition of new technologies.

You may also like

Cloud services

Architectural Best Practices in Cloud Services

cloud

On-Premises to Cloud

cloud journey

Empowering Insourcing and Automation: Intraway’s Role in IT Transformation