equirement of eNodeBs themselves being connected to one another, along with the need to be connected to the core network elements, thus leading to a mesh structure. Hence, operators need to be very clear as to how they will achieve the required capacity in backhaul and yet be able to support such complex requirements for high capacity from LTE network deployments. This also means there needs to be sufficient investments made to realize and implement such a powerful backhaul capacity to handle the current and future LTE deployments. Environment Issues Aside from the issues discussed above, there are some challenges inherent to the technology and ecosystem that is evolving LTE development. This section addresses such issues, which are not only necessarily technology related, but also are inherent to the complexity of the technology and the environment under which such development is happening. We discuss issues relating to UE, issues with the execution of complex projects where all network elements, including UE, eNodeB, and the EPC, are evolving at the same time. Also, we highlighted the role that is played to a certain extent by standardization efforts and limitations. Some of these issues are not necessarily unique to LTE; but they need to be understood and acknowledged by the operator, if only to get a better handle on managing the challenging task of deployment under such conditions. UE Maturity During the development of any new technology or feature, there is always a lack of valid UE that could be used during network element (NE) development to validate the functionality of the NE or feature with assurance (from the eNodeB point of view). Mostly, this is due to the fact that the UE is also being developed in parallel to the eNodeB development timeline. In such scenarios, the NE development proceeds with the usage of appropriate simulation tools to simulate UE behavior. Note What is valid for the eNodeB is also valid for the LTE UE development. Hence, UE developers too should be managing the lack of an eNodeB