Long-Term Evolution (LTE) complements the success of HSPA with higher peak data rates, lower latency plus an enhanced broadband example of high-demand areas. This is achieved with the use of wider-spectrum bandwidths, OFDMA and SC-FDMA air interfaces, and advanced antenna techniques. These techniques enable high spectral efficiency and an excellent buyer for a wide range of converged IP services. To take full benefit of these broadband access networks and enable the co-existence of multiple technologies through an efficient, all-ip-packet architecture, 3GPP? implemented a fresh core network, the evolved packet core (EPC). EPC is planned for 3GPP Release 9 and it is meant for use by various access networks for example LTE, HSPA/HSPA+ and non-3GPP networks. The evolved packet system (EPS) comprises the EPC and also a set of access systems such as the eUTRAN or UTRAN. EPS has been designed from the ground up to support seamless mobility and QoS with minimal latency for IP services.
EVOLVING ALL-IP FLAT ARCHITECTURE
The 3GPP is evolving wireless networks for being flatter and more simplified. In EPS's user plane, for example, there are only 2 kinds of nodes (base stations and gateways), during current hierarchical networks you can find four types, including a centralized RNC. Another simplification is the separation from the control plane, with a separate mobility-management network element. It's worth noting that similar optimizations are enabled in the evolved HSPA network architecture, providing a likewise flattened architecture.
An essential difference from current networks is that the EPC is scheduled to back up packet-switched traffic only. Interfaces are based on IP protocols. This means that all services will be delivered through packet connections, including voice. Thus, EPS provides savings for operators with a single-packet network for all those services.
EVOLVED NODE-B (eNB)
A visible fact is that most with the typical protocols implemented in today's RNC are chosen the eNB. The eNB, similar to the Node B functionality in the evolved HSPA architecture, is usually to blame for header compression, ciphering and reliable delivery of packets. For the control plane, functions such as admission control and radio resource management may also be integrated into 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 your access network plus the PDNs (e.g., the web), gateways support the interfaces, the mobility needs and the differentiation of QoS flows. EPS defines two logical gateway entities, the S-GW and the P-GW. The S-GW provides a local mobility anchor, forwarding and receiving packets back and forth from the eNB the location where the UE has served. The P-GW, consequently, interfaces while using external PDNs, including the Internet and IMS. Additionally it is responsible for several IP functions, including address allocation, policy enforcement, packet classification and routing, also it provides mobility anchoring for non-3GPP access networks. Used, both gateways may be implemented as one physical network element, based on deployment scenarios and vendor support.
Visit Seamless Mobility or Seamless Mobility Networks for more.