Overview of 3G Network Architecture

Third-generation (3G) mobile networks, standardized as IMT-2000 by the International Telecommunication Union, brought a fundamental shift from circuit-switched voice to a hybrid architecture capable of high-speed data and multimedia services. The most widely deployed 3G standard is Universal Mobile Telecommunications System (UMTS), based on Wideband Code Division Multiple Access (W-CDMA) radio access technology. The architecture is cleanly partitioned into three main segments: the User Equipment (UE), the UMTS Terrestrial Radio Access Network (UTRAN), and the Core Network (CN). The UTRAN consists of two logical components: the Node B (base station) and the Radio Network Controller (RNC). Together, these elements deliver seamless connectivity, mobility management, and quality-of-service guarantees across cellular footprints.

Understanding the roles of each component and how they communicate over standardized interfaces (Iub, Iur, Iu) is essential for network engineers, telecom students, and anyone involved in mobile system design. This article provides an authoritative, technical deep dive into the architecture, functions, and interactions of Node B, RNC, and Core Network, along with the protocols that make 3G networks reliable and scalable.

Node B: The Base Station in UTRAN

Node B is the physical radio transceiver that provides the air interface to User Equipment within a specific geographical cell. It is the UTRAN counterpart of a GSM Base Transceiver Station (BTS). Node B handles all Layer 1 (physical layer) processing, including channel coding, spreading/despreading, modulation, power control, and soft handover combining.

Key Functions of Node B

  • Radio Transmission and Reception: Node B transmits and receives W-CDMA signals on the dedicated Uu interface. It manages multiple carriers and sectors, each supporting many simultaneous users via code-division multiplexing.
  • Inner-Loop Power Control: To combat the near-far problem in CDMA systems, Node B executes fast power control at a rate of 1500 Hz, adjusting UE transmit power to maintain a target Signal-to-Interference Ratio (SIR). This is critical for capacity and battery life.
  • Soft/Softer Handover Support: Node B participates in macro diversity combining, where multiple Node Bs (or sectors) receive the same UE transmission and forward it to the RNC. Node B also performs softer handover combining for sectors under the same base station.
  • Measurement Reporting: Node B measures received signal strength, quality, and timing from UEs and reports to the RNC for handover decisions and resource allocation.
  • Lub Interface Termination: Node B connects to the RNC via the Iub interface, transporting both user-plane data (from the MAC-hs in High-Speed Downlink Packet Access, or from RLC frames) and control-plane signaling (NBAP – Node B Application Part).

Node B Hardware Architecture

A typical Node B comprises one or more Baseband Units (BBUs) that handle digital processing, and Remote Radio Units (RRUs) or integrated transceivers that convert baseband to RF. The BBU runs the physical layer algorithms, while the RRU amplifies and filters the signal. Node Bs are often deployed in configurations supporting 1, 3, or 6 sectors, with up to four carriers per sector in W-CDMA. For High-Speed Packet Access (HSPA), Node Bs include additional hardware for MAC-hs or MAC-e scheduling, which moves some intelligence from the RNC to the base station to reduce latency.

Iub Interface and Protocols

The Iub interface between Node B and RNC uses Asynchronous Transfer Mode (ATM) or IP transport. On the user plane, several DCH frames are multiplexed into AAL2 (ATM Adaptation Layer 2) or IP/UDP streams. The control plane uses NBAP (Node B Application Part) for radio link setup, deletion, reconfiguration, and measurement control. The transport network control plane handles ALCAP (Access Link Control Application Part) for AAL2 binding. In modern deployments, IP-based Iub reduces cost and complexity.

Radio Network Controller (RNC)

The RNC is the intelligent controller that manages radio resources across multiple Node Bs. It connects to the Core Network via the Iu interface and to other RNCs via the Iur interface. The RNC is responsible for connection setup, mobility management, and quality-of-service enforcement. It can be seen as the "brain" of the radio access network.

RNC Roles: Controlling, Serving, and Drift

In UMTS, an RNC can assume different roles for a given UE session:

  • Serving RNC (SRNC): The RNC that controls the UE’s connection. It manages the Iu link to the Core Network, handles handover decisions, performs outer-loop power control, and buffers data for retransmissions in RLC (Radio Link Control).
  • Drift RNC (DRNC): When a UE moves into a cell controlled by a different RNC, the Node B in that cell forwards data to the DRNC, which then sends it to the SRNC via the Iur interface. The DRNC does not hold the Iu connection for that UE.
  • Controlling RNC (CRNC): Each Node B is controlled by exactly one RNC for common channel configuration and admission control. The CRNC can be the SRNC for some UEs and the DRNC for others.

Key Functions of the RNC

  • Radio Resource Management (RRM): The RNC allocates and deallocates radio bearers, manages congestion, and performs admission control, load control, and packet scheduling (for non-HSPA channels).
  • Handover Control: The RNC decides when to trigger soft, softer, or hard handovers based on UE measurement reports. It also controls the combining/splitting of data streams at the SRNC during soft handover.
  • Outer-Loop Power Control: The RNC adjusts the target SIR for each UE based on BLER (Block Error Rate) measurements. This ensures adequate quality without wasting power.
  • Security: The RNC participates in ciphering and integrity protection for the control plane, using keys provided by the Core Network.
  • Iu Interface Control: The RNC terminates the RANAP (Radio Access Network Application Part) protocol on the Iu-CS (circuit-switched) and Iu-PS (packet-switched) interfaces, managing UE registration, paging, and session setup.

RNC Protocol Stack

The RNC hosts several radio interface protocols:

  • RRC (Radio Resource Control): Handles connection establishment, measurement control, and downlink signaling. RRC states (IDLE, CELL_DCH, CELL_FACH, CELL_PCH, URA_PCH) define UE activity levels and resource usage.
  • RLC (Radio Link Control): Provides segmentation/reassembly, error correction (ARQ), and flow control. RLC operates in transparent (TM), unacknowledged (UM), or acknowledged (AM) mode depending on the service.
  • MAC (Media Access Control): Mapping logical channels to transport channels, priority handling, and scheduling. In HSPA, MAC-hs (in Node B) and MAC-e are used for high-speed data.
  • PDCP (Packet Data Convergence Protocol): Performs IP header compression and for VoLTE later, but in 3G it reduces overhead for packet data.

The Core Network

The Core Network in 3G is divided into two domains: Circuit-Switched (CS) and Packet-Switched (PS). These handle voice and data respectively, with some overlapping functions. The Core Network is responsible for routing, subscriber management, authentication, and interconnection with external networks (PSTN, Internet, other PLMNs).

Circuit-Switched Domain Components

  • Mobile Switching Center (MSC): The MSC handles voice call control, SMS, and circuit-switched data (like CS video calls). It contains the Visitor Location Register (VLR) for temporary subscriber data and location updates. The MSC connects to the RNC via Iu-CS (using RANAP) and to other MSCs via ISUP/SCCP.
  • Gateway MSC (GMSC): An MSC that serves as the entry point for calls from external networks (e.g., PSTN). GMSC queries the HLR to route calls to the current MSC/VLR.
  • Home Location Register (HLR): A central database that permanently stores subscriber information (IMSI, MSISDN, subscribed services, authentication keys). HLR supports location updates and call routing.
  • Authentication Center (AuC): Generates authentication vectors (RAND, XRES, CK, IK) for subscriber verification and cipher key derivation. AuC data is stored in HLR but the AuC is a separate logical entity.
  • Equipment Identity Register (EIR): An optional database that stores IMEI numbers for blacklisting stolen devices.

Packet-Switched Domain Components

  • Serving GPRS Support Node (SGSN): The SGSN manages packet-switched services for users within its service area. It performs mobility management (Attach, RAU), session management (PDP context activation), charging, and ciphering. It connects to the RNC via Iu-PS (RANAP over IP or ATM) and to the GGSN via Gn/Gp (GPRS Tunneling Protocol).
  • Gateway GPRS Support Node (GGSN): The GGSN acts as the gateway between the mobile network and external packet data networks (Internet, corporate LANs). It allocates IP addresses to UEs, performs IP routing, enforces QoS policies, and tunnels subscriber sessions via GTP (GPRS Tunneling Protocol). The GGSN also handles APN-based service selection.
  • Border Gateway (BG): Used for inter-PLMN GPRS roaming, connecting the home and visited networks via a Gp interface.

HLR and HSS Evolution

In pure 3G, the HLR holds both CS and PS subscriber data. As networks evolved toward IMS and SAE (System Architecture Evolution), the HLR was replaced by the Home Subscriber Server (HSS), which also supports IP Multimedia Subsystem (IMS) authentication. However, in legacy 3G networks, HLR remains central.

Interactions Between Node B, RNC, and Core Network

A complete 3G call or data session flows through multiple layers. Consider a UE in CELL_DCH state performing a web browsing session:

  1. The UE is connected via a W-CDMA radio link to a Node B. Node B measures its received SIR and continuously adjusts UE power via inner-loop control.
  2. User data is sent over the air using dedicated or shared channels. Node B performs soft handover combining if the UE is in soft handover with multiple Node Bs.
  3. Node B forwards transport blocks to the SRNC over Iub. The RNC performs RLC ARQ retransmissions if needed, and reassembles PDCP PDU after header decompression.
  4. The SRNC then sends the user data over Iu-PS to the SGSN, which encapsulates it in GTP-U and sends to the GGSN.
  5. GGSN forwards IP packets to the external network. Inbound packets follow the reverse path, with the HLR consulted for mobility when the UE is idle.
  6. For voice calls, the SRNC sends speech frames (AMR) over Iu-CS to the MSC, which routes via TDM or IP to the PSTN or other MSC.
  7. Signaling (RRC, NAS messages) uses the control plane: Node B forwards NBAP/NBAP? Actually, RRC messages go over SRB (Signaling Radio Bearer) handled by RNC; NAS messages (e.g., for mobility management, call control) are transparently passed to the Core Network using RANAP.

Mobility and Handover Scenarios

3G supports several types of handovers:

  • Soft Handover: UE is connected to multiple Node Bs simultaneously. The RNC (SRNC) combines the uplink data and selects the best downlink stream. This increases reliability at cell edges.
  • Softer Handover: Same as soft but between sectors of the same Node B, handled internally.
  • Hard Handover: Used for inter-frequency or inter-system (e.g., 3G to 2G) handovers. The UE momentarily breaks the connection, retunes, and re-establishes.
  • SRNC Relocation: When the UE moves to a different RNC’s area, the SRNC relocates via the Iur interface or a direct hard handover. The Core Network updates the SGSN/MSC with the new RNC.

The RNC controls handovers using measurement reports from UE (Event 1A, 1B, 1C, etc.). Soft handover is a key feature of W-CDMA, improving capacity and reducing outage probability.

Quality of Service Framework in 3G Networks

3G defines four QoS classes (conversational, streaming, interactive, background) to support various services. The RNC and Core Network enforce QoS through:

  • Bearer negotiation: During PDP context activation, the UE requests QoS parameters (traffic class, bit rate, delay, reliability). SGSN and GGSN authorize based on subscription data.
  • Radio Bearer Setup: The RNC maps QoS to W-CDMA transport channels (DCH, DSCH, HS-DSCH, etc.) and chooses appropriate RLC mode.
  • Packet Scheduling: In HSPA, Node B’s MAC-hs scheduler dynamically allocates downlink resources, while RNC handles admission control to prevent overload.
  • Policing and Shaping: GGSN or external network elements enforce traffic contracts and shape downlink bursts.

This QoS architecture was a major advance over 2G, enabling real-time video calls and assured data rates.

Evolution: From 3G to HSPA and Beyond

To meet increasing data demand, 3GPP introduced High-Speed Packet Access (HSPA). HSPA moved scheduling to Node B (MAC-hs for downlink, MAC-e for uplink), reduced RNC involvement, and increased spectral efficiency. Key enhancements include:

  • HSDPA (Downlink): Up to 14.4 Mbps peak using adaptive modulation and coding (QPSK/16QAM), hybrid ARQ, and fast packet scheduling at Node B.
  • HSUPA (Uplink): Up to 5.76 Mbps with Node B scheduling and fast HARQ.
  • HSPA+: Introduced MIMO (Multiple Input Multiple Output), 64QAM, dual-carrier aggregation, and all-IP RAN architecture (Iub over IP), pushing peak rates to 42 Mbps and beyond. Some operators deferred HSPA+ until LTE deployment.

The RNC role evolved: in HSPA, the RNC still manages mobility, but the Node B takes on more radio scheduling tasks. Later, in LTE/SAE, the architecture flattened entirely (eNodeB replaces Node B and RNC, and the Core Network becomes an Evolved Packet Core). However, many 3G networks coexist with LTE and 5G for voice fallback (CSFB) and coverage.

Conclusion

The 3G network architecture of Node B, RNC, and Core Network provides a robust, hierarchical structure that balanced centralized control with distributed radio intelligence. Node B handles physical-layer tasks and fast power control; the RNC manages radio resources, mobility, and QoS; the Core Network routes traffic and manages subscriber data. Understanding this architecture is fundamental for telecom professionals working on network optimization, troubleshooting, or deployment of legacy systems. Although modern networks are evolving toward flat IP architectures, the principles of radio resource management, mobility, and QoS pioneered in 3G continue to inform 5G design.

For further reading, refer to the 3GPP specifications (TS 25.401, TS 23.060, TS 25.433) and standard textbooks on UMTS. A detailed overview of the Iu and Iub interfaces can be found in this ETSI technical specification for UTRAN overall description.