All the industry’s talk may be about 5G, but the bulk of mobile investment will be in LTE enhancements, for years to come. The specifications for 3GPP Release 13 will be frozen shortly, and the standards body has just announced the work program for Release 14, which should be finalized in mid-2017.
Together, these two releases form ‘LTE-Advanced Pro’ and are the last two before 5G starts with Release 15 around 2018. If operators have their way, there will be far greater overlap between LTE-A Pro and 5G than there was between 3G and 4G releases – most will be developing the two technologies in parallel and using new techniques like virtualization to be able to mix and match different standards more flexibly than was possible in previous generations. That will improve the economics, avoiding yet another big bang upgrade and preserving investment in current platforms for a far longer period, while introducing 5G elements as required for specific new revenue streams such as low latency M2M services.
Vendors are already introducing elements of Release 13, and even pre-standard implementations of R14 technologies, under labels such as ‘4.5G’ (Huawei). Many R14 ingredients will be enhancements of standards in R13 or earlier, such as a next wave of specs for running LTE in unlicensed spectrum (LTE-LAA and LTE-LWA are in R13 but will be further developed in R14).
Dino Flore, the 3GPP’s RAN Group chairman, said that the list gives a “good idea on how LTE will evolve to meet various market demands”.
Many of the elements are clearly designed as bridges to 5G, optimizing current LTE networks while introducing some concepts which will be further evolved in R15 and beyond, such as virtualized RAN and advanced MIMO schemes. The tasks fall under four main headlines:
- Improvements to LTE efficiency
- RF and performance requirements
Both these are vital to optimize user experience, support new services at affordable cost, and prolong the investment in 4G.
- Offload to unlicensed – including the enhancements to LTE-LAA (Licensed Assisted Access) and LTE-LWA (LTE-WLAN Aggregation).
- Enablers of new services/verticals – perhaps the area where the original LTE releases were most lacking, but it is essential that operators can squeeze new services and revenues from their existing infrastructure in order to improve their business case as consumer revenues come under pressure. Vertical and Internet of Things services are the chief justifiers for 5G investment, but most MNOs need to pursue them long before 5G too.
According to Flore, “a few more projects” may be added in the coming months, but this list forms the bulk of the R14 work (http://www.3gpp.org/news-events/3gpp-news/1768-ran_rel14).
There are 24 work items in total under these headings. On the efficiency side, some of the technologies which wil be important to future LTE network include standardized approaches to FD-MIMO, enhanced CoMP (coordinated multipoint), enhanced VoLTE, Layer 2 latency reduction, light signalling techniques and mobility enhancements. There will also be a study on improved LTE-HSPA joint operation, reflecting the fact that, in the build-up to 5G, 3G remains a major workhorse, and itself only recently overtook 2G as the most widely installed mobile network.
For RF performance, items include more flexible LTE bandwidth, enhanced multiband operations over three bands and more, better performance at very high speed and multi-antenna verification.
As for new services and verticals, the work includes V2V (vehicle-to-vehicle) and V2X services using LTE; and enhancements to LTE Broadcast and to indoor positioning capabilities. For the Internet of Things, there will be specific improvements to LTE D2D (device-to-device) communications, and some of the characteristics of R13’s M2M standards, NB-IoT and LTE-MTC, will be adapted for an ultra-low power D2D link.
Most radically, the 3GPP wants to define a new architecture for the relay link between a wearable and its associated ‘relay device’, usually a smartphone. It will look at methods for the network to identify, address, and reach a remote UE via a relay UE, and distinguish between traffic coming from these two types, in order to treat the wearable as a separate item for billing or security. The 3GPP also wants to address end-to-end security and QoS in that relay link as well as efficient switching between D2D and conventional air interfaces, and relaying over WiFi or Bluetooth as well as LTE.
For LTE in unlicensed bands, some of the gaps which remain in R13 include better interworking between LTE and WiFi at the radio level, especially as the 802.11 networks get ever-faster. The 3GPP said future additions like 802.11y, which promises up to 20Gbps speeds in the 60 GHz band, might “require additional optimizations” such as support for 60 GHz channel measurements. Also needed are improved ways to estimate available WLAN capacity and to support Automatic Neighbor Relations in LTE-LWA; and an uplink access scheme for LTE-LAA (R13 only defined the downlink).
One of the most important elements of the R14 work is context-aware service delivery, something which is fundamental to many envisaged future mobile revenue models, but which is scarcely enabled by current network technologies. Operators can go a certain way towards understanding a user’s full context – the network knows the consumer’s location (increasingly accurately if small cells are in use) and can tie that to data stored on that person’s preferences and behavior. But the most advanced context work so far has been done by over-the-top providers, using information from users’ apps and devices and feeding it into huge artificial intelligence engines of the kind under development by Google, Facebook and others.
LTE-A Pro, 5G and related activities undertaken by ETSI’s Mobile Edge Computing initiative could all turn the MNO’s access network into a far more powerful tool to understand customers’ context in enormous detail and deliver services, QoS levels, promotions and actions accordingly. The 3GPP, in particular, says it will study how the LTE RAN can acquire service specific information, support local break-out and delivery of cached content, and tie optimization into context awareness. This, it claims, will not duplicate work being done by ETSI MEC in areas like video optimization and caching, but aims to propose an alternative approach to these tasks, with greater efficiency across different layers and networks, and less reliance on extensive DPI (deep packet inspection) on the user plane.
Context awareness will be addressed in far more depth during 5G evolution, and there is sure to be increasing cooperation and/or overlap with ETSI MEC. A white paper recently published by the UK’s main 5G R&D center, the 5G Innovation Center at the University of Surrey, proposes a ‘flat distributed cloud (FDC)’ architecture which would understand a user’s (or ‘thing’s) context and would then deliver just the right amount of capacity, latency and so on required for that particular situation. That would achieve one of the key aims of 5G – to support a user experience which is perceived to be always sufficient (as opposed to over-delivering, for a given usage, on some occasions and then disappointing on others). It will continue the LTE-A trend to push content to the edge and flatten the architecture to reduce latency – the FDC design will require just one layer in 70% of cases, and two in the rest, says the team behind it, rather than three for LTE.
The FDC approach therefore flattens the current network hierarchy even more than 4G did when compared to 3G, and proposes a “horizontally distributed cloud model that relies on new user and control plane protocols allied to the implementation of NFV and SDN, with all network nodes equipped with service compute power and storage as well as communications processing”. So far, so similar to many other 5G efforts, such as some of the European Union’s 5G-PPP initiatives. But the 5GIC insists that its approach relates general concepts to “the very specific challenges of mobile architectures”, rather than going for “blind adoption of SDN, NFV and cloud principles”.
Each node in the FDC architecture is enabled for both services and communications, with processing and storage. Clusters of dynamic, virtualized cells are linked to hardware clusters in data centers, which may be nearby or remote depending on available backhaul/fronthaul. Another technique borrowed from LTE is dual connectivity – the operator can connect to both the control plane node (mapped to a macrocell) and the user plane (the most appropriate user plane cell within a cluster of small cells with a virtualized controller). The clusters can be reorganized according to changing conditions such as load versus time, in order to optimize the network – NFV is used to reconfigure the clusters on-demand while SDN allocates resources where there are highly dynamic traffic patterns and dense environments.
The FDC is not an entirely new concept – it builds on the CUPS (Control and User Plane Separation) being developed for LTE as part of the shift towards software-defined networking (SDN). In 4G, the Serving Gateway and Packet Gateway are separated into control and user plane modes, but the 5GIC team propose end-to-end separation, with predictive signalling to reduce signal load between the cell sites and the centralized controllers.
The architecture would enable the network to access and act upon context information and, based on that, make decisions about the right levels of QoS. The user would share information with the network via a user profile, which would then provide the ‘5 Ws’ – what, when, where, who, why – to support more intelligent, personalized decisions by systems such as SON (self-optimizing network).
The FDC approach also proposes extending the current RRC (Radio Resource Protocol) into a Common Resource Connection Protocol (CRCP), allowing multiple bearer types from multiple technologies to be combined to support a single dynamic, virtual connection from a device to the FDC network. This would allow multiple radio and fixed access technologies to be treated as a single resource, mixed and matched on a per-user basis, depending on their context and usage at the time.
Another key element of FDC is a context-aware user plane protocol (UPc) that allows bearer class to be negotiated by service description and user context, not QoS class.
The paper’s authors write: “QoS controls have been seen as either too complex or insufficiently supported on an end-to-end basis to be workable … 3GPP has four generations of experience in setting QoS for mobile networks, but provision and exposure of QoS controls to the device/application has proved poor.”
Even the Differentiated Services Code Point (DSCP) from the Internet standards body, IETF, which has been more widely adopted, is usually confined to a small subset of controls. “So it is proposed here that for 5G, each communications ‘request’ is made more descriptive of the request type, content and performance required, and the network selects the best available QoS controls in the network accordingly,” the paper continues.
