Long-Term Evolution (LTE) complements the prosperity of HSPA with higher peak data rates, lower latency and an enhanced broadband experience in high-demand areas. This is accomplished if you use 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 great deal of converged IP services. To take full benefit of these broadband access networks also to 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 is designed for use by various access networks for instance LTE, HSPA/HSPA+ and non-3GPP networks. The evolved packet system (EPS) comprises the EPC as well as a set of access systems for example the eUTRAN or UTRAN. EPS continues to be designed through the beginning to aid seamless mobility and QoS with minimal latency for IP services.
EVOLVING ALL-IP FLAT ARCHITECTURE
The 3GPP is evolving wireless networks to get flatter and more simplified. In EPS's user plane, as an illustration, you'll find only two types of nodes (base stations and gateways), while in current hierarchical networks you can find four types, including a centralized RNC. Another simplification will be the separation from the control plane, with 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 is the EPC is defined to aid packet-switched traffic only. Interfaces are based on IP protocols. Consequently all services is going to be delivered through packet connections, including voice. Thus, EPS provides savings for operators simply by using a single-packet network for all services.
EVOLVED NODE-B (eNB)
An obvious fact is that many from the typical protocols implemented in the present RNC are moved to the eNB. The eNB, exactly like the Node B functionality within the evolved HSPA architecture, is usually liable for header compression, ciphering and reliable delivery of packets. Around the control plane, functions for example admission control and radio resource management are also incorporated into the eNB. Benefits of the RNC and Node B merger include reduced latency with fewer hops in the news path, and distribution from the RNC processing load into multiple eNBs.
SERVING AND PDN GATEWAYS
Between access network as well as the PDNs (e.g., the world wide 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 acts as a local mobility anchor, forwarding and receiving packets to and from the eNB the place that the UE is being served. The P-GW, in return, interfaces together with the external PDNs, like the Internet and IMS. It's also in charge of several IP functions, including address allocation, policy enforcement, packet classification and routing, and it also provides mobility anchoring for non-3GPP access networks. Used, both gateways may be implemented as you physical network element, based on deployment scenarios and vendor support.
Visit Seamless Mobility or Seamless Mobility Networks for more.