Hyper Open Edge Cloud


Explain the network architecture of ORS
  • Last Update:2024-02-20
  • Version:001
  • Language:en

Q: Please explain the network architecture of the ORS and whether it is necessary to deploy additional wireless network management and gateways.

A: The general architecture is described here

This architecture has 3 components:

  • the master which runs the OSS/BSS/NMS master and the core network;
  • the node which runs the OSS/BSS/NMS node and eNodeB/gNodeN;
  • the leaf which runs RU/RRH.

Everything in this architecture is open source except Amarisoft stack which is proprietary (possibly licensed source under specific conditions).

This architecture translates in different topologies depending on the use case:

  • master + node + leaf running on the same hardware ("all-in-one")
  • master on one hardware, node + leaf on another hardware  (typical of coverage extension)
  • master on one hardware, node + leaf + local epc/5gc on another hardware (typical of private networks)
  • master, node and leaf on three different hardware (typical of public networks)

The picture below illustrates two examples of topologies.

The upper part of the diagram illustrates typical deployment of public 4G/5G network based on a "BBU hotel" topology. This is the most cost efficient approach to deploy a 4G/5G vRAN network with macro-cells. All servers are running Amarisoft eNb/gNb and SlapOS are located in one building. They are connected through optical fiber to RRH/RU with distances of up to 100 km (less in practice due to transceiver constraints). Connectivity can be based on CPRI or eCPRI, with or without a fronthaul switch or a mux/demux in between. Further detail can be provided in a separate dicussion. 

The lower part of the diagram shows the ORS "all-in-one" device and is typical of 4G/5G private networks or coverage extension applications. The key idea is to keep things as simple as possible with "plug-and-play" operation. ORS connects using a single RJ45 cable by Ethernet (PoE) to any router or Internet gateway which provides TCP/IP connectivity. It runs SlapOS node software which provides network configuration, automation, monitoring and management. SlapOS automated deployment and operarion of Amarisoft eNb/gNb and local core network. SlapOS can also be used to deploy local edge services: CDN, virtual PLC, etc. In particular, SlapOS is used to deploy a local epc/5gc which ensures low latency for Industry 4.0 application and continuous operation even in case of downtime of the TCP/IP connectivity. It can also connect, at the same time, to a remote epc/5gc in order to integrate with another public or private network.

The picture below shows the panel interface to manage ORS basic parameters: