Amarisoft

NR SA Out of Coverage (OOC)

This tutorial is about Out of Coverage test. It would shows how you can put UE in out of test condition and check if UE gets recovered from the OOC states. In terms of user level operation, OOC is a very simple feature that would not attract much attention. But handling OOC is pretty important in terms of UE implementation. Usually UE manufacturer perform quite long list of test for OOC.

NOTE : If these step repeats blindly when the suitable cells are not available, the battery would run out quickly. So the strategy to perform this process is very important on UE modem development. One of the most common trick to reduce the battery consuption is the increase the time interval at Step 4 every time UE fails to find suitable cell when it wake up. However, if you set too long time interval (backoff time), the time for UE to recover from OOC when the UE enters into the area with normal coverage. So well-define optimization is required and these optimization is up to UE implementation (not defined by 3GPP).

Table of Contents

Introduction

Out of Coverage (OOC) scenarios are a critical facet of wireless communication technology, particularly in the context of User Equipment (UE) behavior and resilience in mobile networks. In modern cellular architectures, such as LTE and 5G NR, UEs are designed to maintain robust connectivity by continuously monitoring signal strength, performing cell reselection, and ensuring seamless transitions between coverage areas. However, when a UE is unable to detect any suitable serving cell—due to geographical, environmental, or network-side factors—it enters an OOC state. The management of this state is essential for both user experience and device longevity, as improper handling can lead to excessive battery drain and delays in service recovery. While OOC handling is largely transparent to end users, it involves sophisticated algorithms and state machines within the UE modem, balancing the need for prompt recovery with efficient power consumption. The strategy for periodic wake-up, measurement procedures, and back-off interval adjustments is typically vendor-specific, as 3GPP standards provide only broad guidelines, leaving optimization to individual manufacturers. This tutorial provides a comprehensive guide to OOC testing, demonstrating how to simulate OOC conditions, monitor UE behavior, and validate recovery mechanisms, which are vital for ensuring device robustness and compliance with operator requirements.

Summary of the Tutorial

This tutorial outlines the procedures for performing a low-layer Out of Coverage (OOC) test on a 5G standalone (NR SA) system using Amarisoft equipment.

This procedure allows for systematic verification of idle mode Out of Coverage detection and recovery mechanisms in the UE under controlled cell power conditions. All steps preserve the integrity of the UE’s idle/attach state transitions and signal monitoring.

Test Setup

Test setup for this tutorial is as shown below.  This is just for low layer testing, you may not need any complicated IP layer setup.

TestSetup Callbox UE 1sdr 01

Key Configuration Parameters

Followings are important configuration parameters for this tutorial. You may click on the items for the descriptions from Amarisoft documents.

Configuration

I have used gnb-sa.cfg which is installed by default without any modification.

NR SA OOC Config 01

I am using the default mme (mme-ims.cfg), ims config as shown below.

NR BWP Test1 Configuration 02

Perform the Test

Power on UE and let it attach. You may wait until it gets into idle because OOC (Out Of Coverage) is mainly for idle mode test. If the cell goes out of coverage during the connected mode, call drop would happen.

NR SA OOC Run 01

Make it sure that UE is in idle mode and it indicates a relatively strong signal strength before the OOC test. If you are not using a phone that can display signal strength, you may use AT command to check the signal strength.

NR SA OOC Run 02

Check on the current cell power using tx_gain command. And then decrease the cell gain step by step until UE gets into Out Of Coverage states.

NR SA OOC Run 03

NOTE : How much power I need to decrease to put UE into OOC (Out of Coverage) state ?  The answer is 'it depends on UE implementation'. Do some experiements with your own DUT to find the right value.

If UE gets into OOC (Out Of Coverage) states, the signal indicator on the display would show 'No Signal' icon.

NR SA OOC Run 04

Stay in Out of Coverage for some time.  And then increase the cell power to normal

NR SA OOC Run 05

Wait until UE reattach to the cell.  How long you have to wait until UE reattach varies depending on how long the UE was in Out of Coverage status and UE implementation of Out of Coverage recovery algorithm.

NR SA OOC Run 06

Once the connection is recovered to In Service, you can confirm it with signal strength indicator on display.

NR SA OOC Run 07