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.

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.

Recent findings suggest that 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.

Functions of a 4G core in the 3GPP architecture.

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.

According to recent reports, 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.

According to recent reports, 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.

Sources indicate that 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 initiative to offer.

In a recent development, 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).

In a recent development, 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.

In a recent development, 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.

It has been revealed that 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.

Industry observers note that 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.

In a recent development, 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.

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.

According to recent reports, 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.

Industry observers note that 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.

It has been revealed that 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.

β†’ Read original article