Hyper Open Edge Cloud

How To Test ORS Before Sending To Client

The process of testing an ORS right before sending it to a client
  • Last Update:2025-12-31
  • Version:001
  • Language:en

Monitor Base URL Check

  • Start all services (eNB and gNB also)
  • Wait until monitor base URL is in the connection parameters
  • Click monitor base URL and check that you land on a page that asks for login and password
  • If you see 503 error after clicking monitor base URL then something is wrong:
    • The ORS might not be properly connected to internet or powered on
    • re6st might not be working properly on ORS
    • make sure service is started and has been started for at least 5 minutes
    • services might not have been instantiated incorrectly, you can try the following fix:
      • rm -rf /srv/slapgrid/slappart* /srv/slapgrid/etc/supervisord.conf.d/slappart* && reboot

Promises Check

  • Stop enb or gnb (depending on the band) and wait for 5 minutes
  • While waiting, you can check if other services are green (health, conference, mail-server and core-network), if they are not something is wrong
  • After having waited 5 minutes, check if eNB / gNB service is green 
  • If it is red, click monitor-setup-url and go to monitoring, if only check-rx-saturated is red then it is OK

Hardware and eNB / gNB Service Check

For ORS Duo:

First, cells must be tested separately, for each cell do the following:

  • Go to the eNB / gNB service (depending on the model of the cell you are testing)
  • Set "Enable Cell" to true on the cell you are testing, and "Enable Cell" to false on the other cell
  • Wait 5 minutes
  • Perform all "Hardware and eNB / gNB Service Checks" tests from below 

Then, both cells should be tested at the same time:

  • Go to the eNB / gNB service (depending on the models of the cells)
  • Set "Enable Cell" on both cells"
  • Wait 5 minutes
  • Connect a phone (no need to redo all the performance tests, just connect a phone)

For ORS Classic:

  • Perform all "Hardware and eNB / gNB Service Checks" tests from below 

For ORS Brute:

  • adjust TX Gain, RX Gain and TX Power Offset
  • Perform all "Hardware and eNB / gNB Service Checks" tests from below 

Hardware and eNB / gNB Service Checks:

  • Connect a phone to the ORS (using one of the SIM Cards you flashed)
  • If phone doesn't connect try to reboot it
  • Go to core-network service, get the iperf3 server IP and port in the connection parameters
  • Go to the eNB or gNB service (depending on which you are testing) and check the bandwidth
  • Put the phone near the ORS (in the same room)
  • Go to magic iperf3 app on the phone
  • Make sure "iperf3" is selected in the app
  • Execute the following command: "-c IP -p PORT -t20", and check speed is the following depending on the bandwidth you saw configured in the eNB or gNB service:
    • TDD 20 MHz: 12 - 17 Mbps, FDD 20 MHz: 54 - 76.5 Mbps
    • TDD 40 MHz: 30 - 40 Mbps
    • TDD 50 MHz: 35 - 48 Mbps
  • Execute the following command: "-c IP -p PORT -t20 -R", and check speed is the following depending on the bandwidth you saw configured in the eNB or gNB service:
    • TDD 20 MHz: 130 - 142 Mbps, FDD 20 MHz: 180 - 220 Mbps
    • TDD 40 MHz: 270 - 302 Mbps
    • 50 MHz: 350 - 396 Mbps
  • Execute the following command: "-c IP -p PORT -t120 -R", move away at a distance and check that the speed doesn't go too low as you move away:
    • For frequencies < 1500 speed should not change
    • For frequencies > 1500 and < 2000, speed should be divided by around 2
    • For frequencies > 2000 and < 2700, speed should be divided by around 4
    • For frequencies > 2700, speed should be divided by around 8

Some bands might have lower throughput than expected because of interference, B28 for instance will likely has interference because it is used a lot by public operators

SIM Cards Check

  • Connect a phone with all other SIM Cards to check they are flashed properly and that they have been registered properly on the panel
  • No need to do any speed test here, just connect a phone