Hyper Open Edge Cloud


Is it necessary to deploy additional Wireless Network Management Or Gateways
  • Last Update:2024-02-20
  • Version:001
  • Language:en

Q: Whether It Is Necessary To Deploy Additional Wireless Network Management Or Gateways ?

A: Checkout Network Architecture Of ORS.

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.