Definition
Network Element (Network Element) is a functional entity in the mobile communication network, implementing core functions such as access, mobility, sessions, and user plane. The 4G EPC (Evolved Packet Core) uses a traditional network element architecture, with main elements including MME, SGW, PGW, HSS, etc.; the 5G 5GC (5G Core Network) uses a service-based architecture (SBA), where network elements are split into AMF, SMF, UPF, AUSF, etc., interacting through service-based interfaces (e.g., HTTP/2), supporting flexible deployment and expansion.
Main 4G EPC Network Elements
- MME (Mobility Management Entity): mobility management, location updates, paging, session management, authentication, handover signaling processing
- SGW (Serving Gateway): user plane anchor, data forwarding during eNB handover, S5/S8 interface with PGW
- PGW (PDN Gateway): IP address allocation, QoS, charging, internet/private network exit, private network access anchor
- HSS (Home Subscriber Server): User subscription data, authentication vectors, location information
Main network elements of 5G 5GC
AMF (Access and Mobility Management), SMF (Session Management), UPF (User Plane Function), AUSF (Authentication), UDM (User Data Management), PCF (Policy Control), etc. Control plane and user plane separation (CUPS), UPF can be distributed and deployed near base stations to reduce latency. When IoT devices connect, PGW/UPF assigns IPs and establishes bearers/PDU sessions, and data is forwarded to the internet or enterprise private networks via user plane network elements.
Typical Use Cases
Network elements constitute the core of cellular networks. After IoT devices connect through base stations (eNB/gNB), they communicate with the cloud via SGW/PGW or UPF. SimtoLink's IoT SIM cards are authenticated and managed for mobility by MME/AMF in the operator network, with IP allocation and data forwarding handled by PGW/UPF; in private network scenarios, PGW/UPF routes traffic to the enterprise-side gateway.
When SimtoLink's IoT SIM cards access the operator network, data flows through network elements like MME/AMF, SGW/PGW, or UPF. When SimtoLink configures APN, private networks, or fixed IPs for customers, it actually interacts with operator PGW/UPF and other element policies. Understanding the functions of network elements helps customers troubleshoot connection failures, IP allocation, QoS, and other issues. SimtoLink technical support can assist customers in analyzing signaling and network element configurations.
The Control-Plane Anchor and the User-Plane Exit Are Separate
A network element is not the product name of a cabinet. It is a function that has to be deployed separately from the others. In 4G the MME handles signaling only: attach, authentication, tracking-area update, paging, and bearer-setup requests. The user’s IP packets do not pass through it. The SGW is the user-plane anchor inside an area. When the device hands over between base stations, data is forwarded from there. The PGW is the exit toward the internet or the enterprise private network. It assigns addresses, enforces policy, and marks charging. The HSS stores the subscription and does not forward service packets. 5G splits these functions more finely. The AMF takes mobility, the SMF manages the session, the UPF forwards the user plane, the AUSF and UDM handle authentication and subscription, and the PCF issues policy. The control plane can stay centralized. The user plane can move down into a room closer to the base station.
So “the core network has a problem” has to land on one function. If paging was never sent, look at the MME or AMF and the location it stored. If address assignment fails or the private-network route is wrong, look at the PGW, SMF, or UPF. If an authentication vector cannot be fetched, look at the HSS or UDM. A clean base-station log does not prove that the exit element is healthy.
Pick the Element from the Symptom
These distinctions apply when the device can already see a cell and the problem starts after attach. With no signal, do not start at the PGW. If attach is rejected for a cause tied to authentication or subscription, ask which HSS or UDM holds the user data and whether the SIM’s IMSI belongs to this network. If the device can attach, receives an address, and still cannot reach the enterprise intranet, look at the APN route, the tunnel endpoint, and the address pool on the PGW or UPF. Do not scan base stations again. If downlink suddenly cannot be reached and uplink reports still go out, look at whether the location and the reachability timer in the MME or AMF are still there.
After 5G separates control plane and user plane, there can be several UPFs. The SMF chooses which UPF anchors the session. If the enterprise private line lands on only one UPF and the device is assigned another, the public internet works and the private network does not. After a handover or roaming, the anchor can change. The old tunnel does not follow the device by itself. When checking a session, look at the anchor identity as well as the cell the device is on now.
Recording an APN Routing Failure as Poor Coverage
The most common mix-up is a device that shows registered while the service does not work, and the site responds by adjusting the antenna. Registration complete means at least the AMF or MME has accepted this signaling. A service that does not work more often sits in the session and the exit. Another error is to map 4G and 5G element names one for one. The MME is not a simple merger of AMF and SMF. Address assignment and policy from the PGW belong in 5G to the SMF, UPF, and PCF. The wrong interface returns a log that says “nothing abnormal.” A capture point chosen on the user plane at the base station never sees the address and DSCP after the PGW rewrites them, so it looks as if the network applied no policy.
With several SIMs and several APNs, different APNs on the same SIM can terminate on different PGWs. A management APN that can reach the internet does not prove a service APN that points at the enterprise firewall. Record the reject cause, the assigned address, the anchor name, and the exit route separately. When the cause points at subscription or an unknown APN, measuring RSRP again has no diagnostic value.
The management access point and the service access point of the same device can terminate on different exit elements. A management path that can open a web page only shows that address translation on that exit is working. It does not prove that the tunnel and the route of the service path are working. If the user-plane anchor does not follow the session after a handover, packets on the old tunnel are sent to a base station the device has already left. The log needs both the anchor name and the current cell. When the two do not match, checking the antenna further is pointless. A five-tuple or authentication failure should go back to the element that holds the user data, not to a service-packet capture on the exit element. What the exit captures is traffic that has already passed authentication. It does not show a subscription reject.