Amarisoft

NAS : Operator Specific PCO

The purpose of this tutorial is to show you how to send Operator specific information in PCO (Protocol Configuration Option).  Usually PCO is requested by UE and the requested information is provided by Network through NAS signaling message as below.

In case of most of PCO elements, Amarisoft core network provide the information based on PCO request from UE, but for Operator Specific PCO  the corenetwork send predefined information without request from UE.

Table of Contents

Introduction

The Protocol Configuration Options (PCO) mechanism is a fundamental aspect of modern mobile communication systems, enabling the dynamic exchange of configuration parameters between User Equipment (UE) and the core network during session establishment procedures. PCO serves as a flexible container for transporting a variety of protocol-specific options, such as IP configuration data, DNS server addresses, and operator-defined information, across the control plane of both LTE and 5G NR architectures. Architecturally, PCO is encapsulated within NAS (Non-Access Stratum) signaling messages, facilitating seamless negotiation and delivery of these options during PDN (Packet Data Network) connectivity and PDU (Protocol Data Unit) session setups. The ability to include operator-specific PCO elements—either in response to explicit UE requests or as predefined network responses—enables mobile operators to deliver tailored services, enforce network policies, and support value-added features without modifying standardized signaling flows. Understanding the end-to-end flow and configuration of PCO elements is particularly significant for network engineers and system integrators working with core network platforms such as Amarisoft, which support both LTE and NR deployments. This tutorial provides a comprehensive guide to managing and delivering operator-specific PCO information, ensuring interoperability and customization in multi-vendor, multi-technology environments.

Summary of the Tutorial

This tutorial describes how to test the transmission of Operator Specific Information in Protocol Configuration Options (PCO) using a configurable callbox environment. The main focus is on configuring the network to always include operator-specific PCO data, regardless of whether the User Equipment (UE) requests it.

This procedure validates that the network correctly includes operator-specific PCO information for the UE, regardless of explicit requests from the UE side, by utilizing the configuration parameter force=true within the operator settings.

Test Setup

Any callbox configuration that support one or more cell would be good enough for this test.

I used a UE with a callbox fitted with external antennas. The UE communicates with the callbox over the radio connection.

UE beside a callbox with antennas connected to SDR ports

Key Configuration Parameters

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

The operator array belongs to the selected pdn_list entry. Its id must be between 0xff00 and 0xffff, and value is a hexadecimal string. The force option defaults to false; I set it to true for this test.

Configuration

You can use any of LTE configuration for this tutorial (e.g, enb.default.cfg).

eNB configuration directory with enb.cfg linked to enb.default.cfg

I used mme-ims-pco-op.cfg which is copied and modified from mme-ims.cfg

MME configuration directory with mme.cfg linked to mme-ims-pco-op.cfg

Test 1 : Operator Specific Information

In this test, I will configure in such a way that eNB send Operator Specific Information on PCO regardless of whether UE request it or not.

Configuration

Add following configuration in mme-ims-pco-op.cfg  

In this tutorial, I am adding the operator specific PCO in 'internet' APN, but you can add it to any APN/PDN you want. Once you decided on which APN you want to add the operator specific PCO, add the configuration parameter operator : [  ] and specify the details in it. In this tutorial, two items are added and each item is made up of the fields : id, plmn, value and force. If you set the parameter 'force' to true, the specified PCO is transmitted regardless of whether UE request it or not.

For the first entry, I set id to 0xff00, plmn to "00101", and value to "123456". For the second entry, I set id to 0xff12, plmn to "00102", and value to "456789". Both entries use force: true.

The value field is a hexadecimal string. Here, "123456" supplies the three bytes 12 34 56, and "456789" supplies 45 67 89. You can change these strings to send your own data. Keep id within the documented range 0xff00 to 0xffff.

The internet APN uses pdn_type: "ipv4", with first_ip_addr: "192.168.3.2" and last_ip_addr: "192.168.3.254". The IPv6 sample configuration is commented out and is not used for this APN.

Internet APN operator containers with two IDs and force enabled

Perform the Test

Check the cell configuration and confirm it is configured as intended.

I used cell phy to check the radio settings. Cell 0x001 uses LTE band 7 with a 5 MHz bandwidth. The downlink ARFCN is 3350, and the uplink ARFCN is 21350.

The cell command reports PCI 1, TAC 0x0001, and PLMN 00101. Check these values against your intended cell settings before connecting the UE.

Cell console output for LTE band 7 and PLMN 00101

Power on UE and wait until it get an IP address.

The ue command in the MME console lists SUPI 001010123456789 with CN set to EPC and REG set to Y. The UE has two bearers, and its IP address list includes 192.168.3.2 and 192.168.4.2.

The address 192.168.3.2 matches first_ip_addr for the internet APN. You can check this address before looking for the operator containers in the NAS log.

MME UE list with registration confirmed and assigned IP addresses

Check in the log and confirm that the Operator specific information is configured in the PCO. You would see the operator specific data with Protocol ID and Data in PCO of Attach Accept message.

I selected Attach accept and checked its ESM message container. The message type is 0xc1, Activate default EPS bearer context request. This container includes the Extended protocol configuration options and the IPv4 address 192.168.3.2.

Protocol ID 0xff00 has Data = 00 f1 10 12 34 56. Protocol ID 0xff12 has Data = 00 f1 20 45 67 89. The final three bytes match the configured value strings "123456" and "456789", respectively.

Attach accept ESM container with operator PCO IDs and hexadecimal data