Long-Term Evolution (LTE) complements the achievements of HSPA with higher peak data rates, lower latency along with an enhanced broadband example of high-demand areas. This is successfully done with the use of wider-spectrum bandwidths, OFDMA and SC-FDMA air interfaces, and advanced antenna techniques. These techniques enable high spectral efficiency along with an excellent user experience for a massive amount converged IP services. To look at full good thing about these broadband access networks and to encourage the co-existence of multiple technologies using an efficient, all-ip-packet architecture, 3GPP? implemented a different core network, the evolved packet core (EPC). EPC is planned for 3GPP Release 9 and it is suitable for use by various access networks like LTE, HSPA/HSPA+ and non-3GPP networks. The evolved packet system (EPS) comprises the EPC and a group of access systems such as the eUTRAN or UTRAN. EPS may be designed on the beginning to aid seamless mobility and QoS with minimal latency for IP services.
EVOLVING ALL-IP FLAT ARCHITECTURE
The 3GPP is beginning to change wireless networks for being flatter plus more simplified. In EPS's user plane, by way of example, there are only 2 types of nodes (base stations and gateways), while in current hierarchical networks you can find four types, including a centralized RNC. Another simplification could be the separation from the control plane, using a separate mobility-management network element. It is worth noting that similar optimizations are enabled inside the evolved HSPA network architecture, providing a likewise flattened architecture.
A key difference from current networks would be that the EPC is determined to aid packet-switched traffic only. Interfaces derive from IP protocols. Which means all services will likely be delivered through packet connections, including voice. Thus, EPS provides savings for operators by using a single-packet network for many services.
EVOLVED NODE-B (eNB)
An evident truth is that almost all of the typical protocols implemented in the current RNC are gone after the eNB. The eNB, the same as the Node B functionality within the evolved HSPA architecture, is also responsible for header compression, ciphering and reliable delivery of packets. For the control plane, functions for example admission control and radio resource management are included in the eNB. Important things about the RNC and Node B merger include reduced latency with fewer hops in the media path, and distribution with the RNC processing load into multiple eNBs.
SERVING AND PDN GATEWAYS
Between the access network and also the PDNs (e.g., the web), gateways secure the interfaces, the mobility needs and the differentiation of QoS flows. EPS defines two logical gateway entities, the S-GW and also the P-GW. The S-GW acts as a local mobility anchor, forwarding and receiving packets from the eNB in which the UE is now being served. The P-GW, consequently, interfaces together with the external PDNs, such as the Internet and IMS. Additionally it is accountable for several IP functions, for example address allocation, policy enforcement, packet classification and routing, and it provides mobility anchoring for non-3GPP access networks. In practice, both gateways can be implemented jointly physical network element, depending on deployment scenarios and vendor support.
Visit Seamless Mobility or Seamless Mobility Networks for more.