Long-Term Evolution (LTE) complements the prosperity of HSPA with higher peak data rates, lower latency and an enhanced broadband experience of high-demand areas. It's done this way with the use of wider-spectrum bandwidths, OFDMA and SC-FDMA air interfaces, and advanced antenna techniques. These techniques enable high spectral efficiency as well as an excellent buyer to get a wide range of converged IP services. To look at full benefit of these broadband access networks as well as enable the co-existence of multiple technologies by using an efficient, all-ip-packet architecture, 3GPP? implemented a new core network, the evolved packet core (EPC). EPC is planned for 3GPP Release 9 and is intended for use by various access networks for instance LTE, HSPA/HSPA+ and non-3GPP networks. The evolved packet system (EPS) comprises the EPC and a list of access systems for example the eUTRAN or UTRAN. EPS may be designed through the start to support seamless mobility and QoS with minimal latency for IP services.
EVOLVING ALL-IP FLAT ARCHITECTURE
The 3GPP is beginning to change wireless networks being flatter plus much more simplified. In EPS's user plane, by way of example, you will find only home equity loans nodes (base stations and gateways), when it is in current hierarchical networks you will find four types, including a centralized RNC. Another simplification will be the separation from the control plane, using a separate mobility-management network element. It truly is worth noting that similar optimizations are enabled inside evolved HSPA network architecture, providing a likewise flattened architecture.
An important difference from current networks could be that the EPC is defined to guide packet-switched traffic only. Interfaces are based on IP protocols. Which means that all services is going to be delivered through packet connections, including voice. Thus, EPS provides savings for operators simply using a single-packet network for everyone services.
EVOLVED NODE-B (eNB)
A noticeable truth is that many from the typical protocols implemented in the present RNC are transferred to the eNB. The eNB, the same as the Node B functionality from the evolved HSPA architecture, is also responsible for header compression, ciphering and reliable delivery of packets. On the control plane, functions for instance admission control and radio resource management are also included in the eNB. Important things about the RNC and Node B merger include reduced latency with fewer hops on tv path, and distribution of the RNC processing load into multiple eNBs.
SERVING AND PDN GATEWAYS
Involving the access network along with the PDNs (e.g., the online world), gateways keep 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 where the UE is being served. The P-GW, therefore, interfaces with the external PDNs, such as Internet and IMS. It's also responsible for several IP functions, for instance address allocation, policy enforcement, packet classification and routing, and yes it provides mobility anchoring for non-3GPP access networks. In practice, both gateways is usually implemented as one physical network element, based on deployment scenarios and vendor support.
Visit Seamless Mobility or Seamless Mobility Networks for more.