DEV Community

VAS Experts
VAS Experts

Posted on

Telecom Core Network Software: The Key Components Every Mobile Operator Needs and Where to Start

You open a vendor list for core network software and meet a wall of acronyms: HSS, MME, PGW, PCRF, ePDG and more. Which ones do you actually have to deal with? We walk through what each part of a mobile core does, how the standard relates it to the fifth-generation core, and what to settle before you talk to a vendor. Which of these functions you run yourself depends on your operator model.

What does telecom core network software do?

In 4G, the Packet Data Network (PDN) Gateway is the point where the mobile core meets the outside network. It allocates user equipment (UE) IP addresses and takes part in policy and charging control. In the Evolved Packet Core (EPC), the Mobility Management Entity (MME) handles non-access stratum (NAS) signalling. The S6a reference point links the MME and the Home Subscriber Server (HSS) and carries subscription and authentication data.

3GPP defines SGi as the reference point between the PDN Gateway and the packet data network. That network may be an operator external public or private network or an intra-operator network.

3GPP specifies the split of the gateway functions into control plane and user plane in TS 23.214. The specification covers the control and user plane separation of the Serving Gateway and the PDN Gateway, and it lets you place the control plane and the user plane separately.

As we describe in our test lab write-up, the mobile core is an infrastructure where all components are tightly interconnected. A change to a tariff plan can affect how the network processes subscriber traffic. When you look at one function, look at its neighbours too.

Which components does a 4G mobile core need?

In the 3GPP architecture, a 4G core has these functions. The Home Subscriber Server (HSS) holds subscriber data and the Mobility Management Entity (MME) handles NAS signalling. The Serving Gateway (SGW) and PDN Gateway (PGW) are the gateways for user traffic. The Policy and Charging Rules Function (PCRF) and Policy and Charging Enforcement Function (PCEF) handle policy.

Functions of a 4G core in the 3GPP architecture

Function What it does under the 3GPP specifications Main reference points
HSS Master database for a user: it holds the subscription-related information for the network entities that handle calls and sessions S6a to the MME
MME NAS signalling, NAS signalling security and tracking area list management S6a, S11
Serving GW (SGW) Terminates the user plane interface towards the radio network; local mobility anchor for inter-eNodeB handover; routes and forwards packets S1-U, S11, S5 and S8
PDN GW (PGW) Terminates SGi towards the packet data network; allocates the UE IP address; policy and charging control features involving the PCRF and the OCS SGi, S5 and S8, Gx
PCRF Policy and charging control element; sends QoS policy and charging rules to the PCEF Gx
PCEF Service data flow detection, policy enforcement and flow based charging Gx, Gy, Gz
Online Charging System (OCS) and Offline Charging System (OFCS) The OCS performs quota management and grants authorization before a resource is used; the OFCS collects charging events and generates records for downstream billing Gy to the OCS, Gz to the OFCS

In home-routed roaming, S8 connects the SGW in the visited network with the PGW in the home network. When the SGW and the PGW are in the same network, S5 connects them: without roaming, or in roaming with local breakout, where the PGW is in the visited network.

Follow one phone as it joins the network. The MME handles NAS signalling and talks to the HSS over S6a, which carries subscription and authentication data. The data session runs through the SGW and the PGW, and the PGW allocates the IP address of the UE. For policy, the PCRF sends quality of service (QoS) rules and charging rules over Gx to the PCEF in the PGW, and the PCEF applies them.

The PGW and the SGW may be implemented in one physical node or in separate nodes. Our test lab uses classic EPC with plane separation by the Control and User Plane Separation (CUPS) model, built from the MME, the HSS, the SGW and the PGW with the PCEF. Use the table as a map of the functions in a 4G core.

What does an operator add for voice and Wi-Fi?

Voice and Wi-Fi rely on functions around the core. Voice over LTE runs on the IP Multimedia Subsystem (IMS). GSMA IR.92, the IMS Profile for Voice and SMS, defines a minimum mandatory set of 3GPP features for IMS-based telephony and for IMS-based and SGs-based SMS over LTE. Wi-Fi access relies on an evolved Packet Data Gateway (ePDG) for untrusted access or a Trusted WLAN Access Gateway (TWAG) for a trusted WLAN.

Wi-Fi has two paths. With untrusted access, the phone builds an IPsec tunnel to the ePDG, and the ePDG hands the session to the core over S2b. The SWu reference point between the phone and the ePDG supports handling of IPsec tunnels. With trusted access, the TWAG terminates S2a. It is a function of the trusted WLAN access network (TWAN). In our article, both gateways hand the subscriber over to the same core. We describe the two paths in our article on Wi-Fi access.

Who decides which path a network takes? In a non-roaming scenario, 3GPP leaves the choice to the home operator. Whether a non-3GPP IP access network is used as trusted or untrusted is not a characteristic of the access network. An operator typically makes that choice for Wi-Fi it controls. For your list, note which of the two Wi-Fi access types you plan to offer.

How do the 4G functions map to the 5G core?

For its policy references to the EPC policy standard TS 23.203, TS 23.503 states that the PCRF maps to the Policy Control Function (PCF) in the 5G core. It states that the PCEF maps to the combination of the Session Management Function (SMF) and the User Plane Function (UPF).

For the PGW and the MME the specifications describe interworking. These are the combined PGW-C + SMF and UPF + PGW-U functions, and the optional N26 interface between the MME and the Access and Mobility Management Function (AMF).

Policy mappings that TS 23.503 states for its references to TS 23.203

4G function 5G function or node What the specifications state
PCRF PCF TS 23.503 states: the PCRF of TS 23.203 maps to the PCF
PCEF SMF and UPF TS 23.503 states: the PCEF of TS 23.203 maps to the combination of the SMF and the UPF

In the 5G core, the PCF provides policy rules to control plane functions to enforce them. The SMF handles session management and UE IP address allocation, and the UPF is the external PDU session point of interconnect to the data network.

One more term for 5G radio. EN-DC (E-UTRA-NR Dual Connectivity) connects the phone to one eNB as master node and one en-gNB as secondary node, and the eNB is connected to the EPC via S1. The 3GPP overview page adds that the Non-Stand Alone architecture, which uses the existing LTE and EPC, is also known as EN-DC.

Where do you start when you choose core network software?

Start from what you already run and what you need: decide which functions you operate and list the interfaces they require. Then choose the generation and access types, agree how the core connects to billing and policy, and test on your own side.

  1. Decide which functions you run yourself. A Light mobile virtual network operator (MVNO) works with a host operator that retains control of the network core; a Full MVNO deploys its own core.
  2. Write a list of the functions and interfaces you need, using the 4G core functions as a template, and mark the ones you already run and the ones you plan to buy.
  3. Choose the generation and the access types: the EPC for 4G, untrusted Wi-Fi through an ePDG or trusted Wi-Fi through a TWAG, voice as defined in the GSMA profile (IMS-based), and EN-DC if you add 5G radio on top of your EPC.
  4. Agree how the core connects to billing and policy. In our test lab, the PCEF needed detailed configuration of subscriber identifier formats, quota rules and other parameters to work with the PCRF and the OCS.
  5. Test on your own side. We offer to test our software on the operator's equipment, on a virtual machine or over VPN.

This order is a suggestion from our team, and step 4 is where our lab experience comes in. In our test lab, the PCEF communicates with the PCRF and the OCS over Diameter on the Gx and Gy interfaces. If your billing and policy systems come from other vendors, put their names and interfaces on your list before the first call.

What should you check when you compare core network software vendors?

Compare vendors against your own interface list. Ask which 3GPP interfaces the software terminates and how control and user plane are separated. Ask how it connects to billing and policy systems and whether it works next to the functions you keep.

Questions to ask a core network software vendor

What to check Why it matters Question to ask
Interfaces The functions talk over named reference points: S6a, S11, S5 and S8, SGi, Gx, Gy, Gz Which of these interfaces does your software terminate?
Control and user plane The 3GPP split into control plane and user plane lets the two be placed separately Which functions are split, and how is a user plane node replaced?
Billing and policy The PCEF talks to the PCRF over Gx and to the OCS over Gy Which interfaces to the PCRF, OCS and OFCS does the software support, and in which test setups has it been run?
Functions you keep You may keep some functions where they are and replace others Can you buy one function, for example a gateway, and run it next to the others?
Testing A test on your side is the last step of the order we suggest Can we test on our own hardware, in a virtual machine or over VPN?
Wi-Fi and voice Wi-Fi access relies on the ePDG for untrusted access and the TWAG for a trusted WLAN, and the GSMA profile for voice over LTE is IMS-based Which access gateways and which IMS interfaces does your software cover?

We suggest checking these six points when you compare vendors. Add your own rows for the functions you keep, and use the list when you talk to us, too.

How do we work with operators on the mobile core?

An operator sends a request through the form on a product page. We contact the operator to specify the task, provide access to the documentation and answer questions.

We build seven products for mobile networks: Stingray PGW, Stingray ePDG, Stingray TWAG, Stingray PCRF Proxy, Stingray GTP-C Proxy, LBS and Stingray PCEF.

In our solution, the PCEF function runs as a separate module of Stingray Service Gateway. This is why we can also supply our PGW on its own: it then works with a PCEF made by other vendors. Stingray TWAG is a software gateway for mobile network operators and mobile virtual network operators. It lets them build a TWAN, a trusted Wi-Fi access network based on the 3GPP standard. Stingray GTP-C Proxy lets you combine PGWs from different vendors into shared pools.

These products are separate pieces of mobile network software; this article describes the 3GPP functions, not our product set.

Specifications used (3GPP Release 19): TS 23.002, TS 23.214 and TS 23.401.

Also used: TS 23.203, TS 23.402, TS 23.501, TS 23.503, TS 32.240 and TS 37.340.

Also used: GSMA IR.92.

Top comments (0)