Wireless Week has a very good magazine with detailed highlights of everything that happened in the recently concluded 4G World event in Chicago. The links are as follows:
Tuesday, 26 October 2010
Monday, 25 October 2010
Setting up and running networks is a complex task that requires many activities, including planning, configuration, Optimization, dimensioning, tuning, testing, recovery from failures, failure mitigation, healing and maintenance. These activities are critical to successful network operation and today they are extremely labour-intensive and hence, costly, prone to errors, and can result in customer dissatisfaction. This project focuses on ensuring that the operators’ recommendations are incorporated into the specification of the 3GPP O&M (and similar groups in other standardisation bodies) so that this critical task moves towards full automation.
The overall objective is to provide operators with the capability to purchase, deploy, operate and maintain a network consisting of Base Stations (BTS) and “Access Gateways (AGw)” from multiple vendors. The NGMN project Operational Efficiency OPE has taken the task to elaborate solutions and recommendations for pushing the operational efficiency in NGMN networks and has produced recommendations on standards and implementations. The NGMN OPE project also influenced strongly the setup of a TOP10 document reflecting main recommendations in operational area. This document (embedded below) binds these two sources which are anyhow strongly linked together into one common NGMN recommendation document.
Friday, 22 October 2010
Its long time since I blogged about TDtv. Its been quite a while since I heard about TDtv. Apparently its been superseded by IMB, aka. Integrated Mobile Broadcast.
IMB is used to stream live video and store popular content on the device for later consumption. This results in a significant offloading of data intensive traffic from existing 3G unicast networks and an improved customer experience. The multimedia client features an intuitive electronic program guide, channel grid and embedded video player for live TV viewing and video recording. All IMB applications can be quickly and cost-effectively adapted to support all major mobile operating systems and different mobile device types, including smartphones, tablets and e-readers.
IMB was defined in the 3GPP release 8 standards, and was recently endorsed by the GSMA as their preferred method for the efficient delivery of broadcast services. In June 2010, O2, Orange and Vodafone – three of the five major UK mobile operators – announced that they have teamed up for a three-month trial that will explore IMB wireless technology within a tranche of 3G TDD spectrum.
This spectrum already forms part of the 3G licenses held by many European mobile operators, but has remained largely unused because of a lack of appropriate technology. Currently, 3G TDD spectrum is available to over 150 operators across 60 countries, covering more than half a billion subscribers. IMB enables spectrally efficient delivery of broadcast services in the TDD spectrum based on techniques that are aligned with existing FDD WCDMA standards. This enables a smooth handover between IMB and existing 3G networks.
Issues that previously limited uptake of IMB, or IPWireless' tdTV system, have now all been addressed. Namely, the standard now allows for smooth handover between IMB and unicast delivery; has the potential to be integrated onto a single W-CDMA chip rather than requiring a separate chip; and has resolved interference issues with FDD W-CDMA, at least for spectrum in the 1900MHz to 1910MHz range.
IP Wireless already had a trial at Orange and T-Mobile in the UK (which have just agreed to merge), but in that pilot each 5MHz segment only gave rise to 14 TV channels per operator. The new standard could support 40 separate TV channels if two operators shared their TDD spectrum.
The GSMA announced its support and is backed up with additional support from both IPWireless and Ericsson as well as operators Orange, Softbank and Telstra.
There have been recently quite a few bad news for DVB-H and on top of that IP Wireless has announced that Samsung is going to be releasing phones with IMB support so it may be that we will see IMB sometime next year.
The GSMA paper that details IMB service scenarios and System requirements is embedded below:
Wednesday, 20 October 2010
Nokia Siemens Networks has collaborated with Qualcomm to carry out the industry’s first successful interoperability test of the new 3GPP standardized Release 8 Fast Dormancy feature. Unlike proprietary approaches to fast dormancy, the new standard allows operators to take full advantage of smart network features such as Cell_PCH without worrying that individual handset settings will ignore network controls.
The test was conducted at Nokia Siemens Networks’ Smart Lab in Dallas using Nokia Siemens Networks’ Flexi Multiradio Base Station and Radio Network Controller and Qualcomm’s QSC7230TM smartphone optimized chipset. The test showed how smartphones can act dynamically, exploiting Cell_PCH on Nokia Siemens Networks’ smart networks or adjusting to Fast Dormancy on other vendors’ traditional networks.
In fact the operators have been getting upset quite for some time because of smartphone hacks that save the UE battery life but cause network signalling congestion. See here.
To get round this problem, the UE manufacturers put a hack in the phone and what they do is that if there no data to transmit for a small amount of time, the UE sends RRC Signalling Connection Release Indication (SCRI) message. This message is supposed to be used in case when something is gone wrong in the UE and the UE wants the network to tear the connection down by sending RRC Connection Release message. Anyway, the network is forced to Release the connection.
To speed up the transitioning to CELL_PCH state in Release-8 when the UE sends SCRI message, its supposed to include the cause value as "UE Requested PS Data session end". Once the network receives this cause it should immediately move the UE to CELL_PCH state.
This is a win win situation for both the network and the UE vendors as long as a lot of UE's implement this. The good thing is that even a pre-Rel8 UE can implement this and if the network supports this feature it would work.
GSMA has created a best practices document for this feature which is embedded below.
- UMTS State Switching and Fast Dormancy Evolution - Martin Sauter
- RP-090941 - System impact of poor proprietary Fast Dormancy implementations
- RP-090942 - Clarification on Enhanced SCRI approach for fast dormancy
- RP-090960 - Configuration of Fast Dormancy
- R2-096882 - Changes to Release-8 Fast Dormancy
Tuesday, 19 October 2010
Capacity and Coverage Optimisation (CCO) was already nominally part of the Release-9 WI, but could not be completed due to amount of work related to other use cases.
Energy Savings are a very important topic, especially for operators, as solutions derived for this use case can significantly limit their expenses. According to TR 36.902 this solution should concern switching off cells or whole base stations. This may require additional standardised methods, once there is need identified for.
Basic functionality of Mobility Load Balancing (MLB) and Mobility Robustness Optimisation (MRO), also listed in TR 36.902, were defined in Rel.9. However, successful roll-out of the LTE network requires analysing possible enhancements to the Rel.9 solutions for MLB and MRO. In particular, enhancements that address inter-RAT scenarios and inter-RAT information exchange must be considered. These enhancements should be addressed in Rel.10.
There may also be other use cases for LTE for which SON functionality would bring optimisations.
Although, it is of primary interest to provide coverage to users during a roll-out, it is equally important to enhance the capacity of the network during operation. As such, both coverage and capacity are considered in the use case and supported by the SON function. The CCO SON function should be configured through appropriate objectives and targets in order to meet the operator’s requirement on coverage and capacity, and the prioritization between them.
The following use cases and scenarios are planned for Release-10:
Coverage and Capacity Optimisation (CCO)
The use case is to enable detection of following problems:
• Priority 1: coverage problems, e.g. coverage holes• Priority 2: capacity problems
Mobility Robustness Optimisation (MRO) enhancements
The use case is to enable detection and to provide tools for possible correction of following problems:
• Connection failures in inter-RAT environment:o Priority 1: at HOs from LTE to UMTS/GSMo Priority 2: at HOs from UMTS/GSM to LTE• Obtaining UE measurements in case of unsuccessful re-establishment after connectionfailure• Ping-pongs in idle mode (inter-RAT and intra-LTE environment)• Ping-pongs in active mode (inter-RAT)• HO to wrong cell (in intra-LTE environment) that does not cause connection failure (e.g. short stay problem)
Mobility Load Balancing (MLB) enhancements
The use case is to fulfil following objectives:
• Improving reliability of MLB in intra-LTE scenarios• Improving functionality of the MLB in inter-RAT scenarios (the transport method agreed for R9 should be used for R10).
For more info see 3GPP TS 32.521: Self-Organizing Networks (SON) Policy Network Resource Model (NRM) Integration Reference Point (IRP); Requirements; Release-10
There is also a Self-Organising Networks Conference that I am attending next month and I plan to give SON lots of coverage before and after the event.
If you havent read the 3G Americas whitepaper on SON, it is definitely worth a read. I have embedded it below.
Monday, 18 October 2010
Friday, 15 October 2010
I have blogged about M2M before here.
The Release 10 work item Network Improvements for Machine Type Communications – Stage 1 for NIMTC specified a number of requirements to make the network more suitable for machine type communications. Additional aspects need to be studied before proceeding with their potential inclusion in the normative work.
In the course of the Release 10 work item, it was decided to leave out MTC Device to MTC Device communications from Release 10. This because it was felt it was not possible to do it justice within the Release 10 time frame. Nevertheless, MTC Device to MTC Device communications are expected to become of major importance, especially with consumer devices communicating directly to each other. Therefore, this work item aims to study the network improvements requirements of MTC Device to MTC Device scenarios. A particular aspect of MTC Device to MTC Device scenarios is the identification and functionality needed to set up a connection towards a MTC Device. The IMS domain may provide a solution for this required functionality. In this case the impacts and requirements of MTC on IMS needs to be studied.
Additionally MTC Devices often act as a gateway for a capillary network of other MTC Devices or non-3GPP devices. These gateway MTC Devices may have specific requirements on the mobile network, which have not yet been taken into account in the Release 10 NIMTC work item. Study is needed to determine to what extent improvements are needed and can be specified by 3GPP for MTC Devices that act as a gateway for 'capillary networks' of other devices. Also alignment with what is specified by ETSI TC M2M on this aspect is needed.
Further optimisations may be possible for (groups of) MTC Devices that are co-located. An example of this could be a car with a number of different MTC Devices that always move along together. Optimisations for these kind of scenarios have been suggested, but have not yet been taken into account in the Release 10 NIMTC. Study is needed to determine to what extent network improvements can be specified for co-located MTC Devices.
Because of the different characteristics of Machine-Type Communications, the optimal network for MTC may not be the same as the optimal network for human to human communications. Optimisations of network selections and steering of roaming may be needed. Study is needed to determine to what extent improvements are needed on network selection and steering of roaming for MTC.
Many MTC applications use some kind of location tracking. E.g. the existing LCS framework could be used to provide location information for these kinds of MTC applications. Study is needed to determine to what extent improvements are needed for MTC location tracking.
MTC brings a new concept of a MTC User and MTC Server. So far little attention has been given to service requirements on the communication between the network and the MTC User/MTC Server. Also alignment with what is specified by ETSI TC M2M on that aspect is needed. Study is needed on what kind of service requirements are needed and can be specified by 3GPP.
The Objective of Study on enhancements for Machine-Type Communications item is to study additional requirements, use cases and functionality beyond that specified by the Release 10 NIMTC work item on the following aspects:
• network improvements for MTC Device to MTC Device communications via one or more PLMNs. Note: direct-mode communication between devices is out of scope.
• possible improvements for MTC Devices that act as a gateway for 'capillary networks' of other devices. Note: capillary networks themselves are out of scope of 3GPP.
• network improvements for groups of MTC Devices that are co-located with other MTC Devices
• improvements on network selection mechanisms and steering of roaming for MTC devices
• possible enhancements to IMS to support MTC
• possible improvements for location tracking of MTC Devices
• service requirements on communications between PLMN and the MTC User/MTC Server (e.g. how the MTC User can set event to be monitored with MTC Monitoring);
• possible service requirements to optimize MTC Devices
• possible New MTC Features to further improve the network for MTC
The results of the study will be recorded in a Technical Report. Work ongoing in external standard organization shall be considered (e.g. ETSI M2M, CCSA TC 10).
The European Telecommunications Standards Institute (ETSI) now has a Technical Committee exclusively focused on M2M; the Chinese Communications Standards Association (CCSA) is currently exploring the definition of M2M standards for China and the Geneva-headquartered International Telecommunications Union (ITU) is working on “mobile wireless access systems providing telecommunications for a large number of ubiquitous sensors and/or actuators scattered over wide areas in the land mobile service,” which are at the center of the M2M ecosystem.
Closer to us, the US Telecommunications Industry Association (TIA) has also launched a new engineering committee centered on Smart Device Communications (TIA TR-50). Incidentally, at Global Standards Collaboration 15 (GSC-15), which will be held on August 30- September 2, 2010 in Beijing and hosted by CCSA, the world’s leading telecommunications and radio standards organizations will meet to promote innovation and collaboration on a broad spectrum of standards topics among which M2M has been identified as a “High Interest Subject.”
Related subject on 3GPP here.
M2M workshop is happening in ETSI next week. More details here.
MTC Device: A MTC Device is a UE equipped for Machine Type Communication, which communicates through a PLMN with MTC Server(s) and/or other MTC Device(s).
Local-Access Device: A Local-Access Device is a device in MTC Capillary Network, which has no 3GPP mobile communication capability.
MTC Capillary Network: An MTC Capillary Network is a network of devices that provides local connectivity between devices within its coverage and MTC Gateway Device.
MTC Gateway Device: An MTC Gateway Device is an MTC device equipped for Machine Type Communication, which acts as a gateway for a group of co-located MTC Devices or to connect MTC Devices and/or Local-Access Devices in an MTC Capillary Network to communicate through a PLMN with MTC Server(s), and/or other MTC Device(s).
Further Interesting Reading:
Thursday, 14 October 2010
Tuesday, 12 October 2010
Monday, 11 October 2010
Friday, 8 October 2010
Continuing on yesterdays theme of Location determination. I have heard in couple of presentations that in future based on multiple RF radios that we will carry, we could be uniquely identified on the planet even though there may not be a single device identifying us uniquely.
A similar project as above but for computers is the Panopticlick project which can be found here.
A similar project as above but for computers is the Panopticlick project which can be found here.
Thursday, 7 October 2010
Some of you may have read my earlier posts on stealing spectrum via Femtocells and using Femtocells abroad illegally. This presentation tries to answer one such problem on how do you find the location where GPS cannot be used. This could also be used in case of Cognitive Radios. See my old blog entry here.
Wednesday, 6 October 2010
You can also check out the IEEE Comsoc Video tutorial "LTE Radio Access – Physical Layer", delivered by none other than Stefan Parkvall of Ericsson. The tutorial is available at: http://host.comsoc.org/freetutorial/anritsu3/anritsu3.html
Tuesday, 5 October 2010
3GPP has been working on Energy saving initiatives for Release-10 and Release-11. Here is a very quick summary of some of these items.
Telecommunication management; Study on Energy Savings Management (ESM)
Most mobile network operators aim at reducing their greenhouse emissions, by several means such as limiting their networks' energy consumption.
In new generation Radio Access Networks such as LTE, Energy Savings Management function takes place especially when mobile network operators want e.g. to reduce Tx power, switch off/on cell, etc. based on measurements made in the network having shown that there is no need to maintain active the full set of NE capabilities.
By initiating this Work Item about Energy Savings Management, 3GPP hopes to contribute to the protection of our environment and the environment of future generations.
The objective of this technical work is to study automated energy savings management features. Usage of existing IRPs is expected as much as possible, e.g. Configuration Management IRP, etc. However, this technical work may identify the need for defining a new IRP.
The following operations may be considered in this study item (but not necessarily limited to):
• Retrieval of energy consumption measurements
• Retrieval of traffic load measurements
• Adjust Network Resources capabilities
OAM aspects of Energy Saving in Radio Networks
There are strong requirements from operators on the management and monitoring of energy saving functions and the evaluation of its impact on the network and service quality. Therefore an efficient and standardized Management of Energy Saving functionality is needed. Coordination with other functionalities like load balancing and optimization functions is also required.
The objectives of this work item are:
• Define Energy Savings Management OAM requirements and solutions for the following use cases,
• eNodeB Overlaid
• Carrier restricted
• Capacity Limited Network
• Define OAM requirements and solutions for coordination of ESM with other functions like
• Self Healing
• Traditional configuration management
• Fault Management
• Select existing measurements which can be used for assessing the impact and effect of Energy Saving actions corresponding to above Energy Saving use cases.
• Define new measurements which are required for assessing the impact and effect of Energy Saving actions, including measurements of the energy consumption corresponding to above Energy Saving use cases.
Study on impacts on UE-Core Network signalling from Energy Saving
Energy Saving (ES) mechanisms are becoming an integral part of radio networks, and consequently, of mobile networks. Strong requirements from operators (for reasons of cost and environmental image) and indirectly from authorities (for the sake of meeting overall international and national targets) have been formulated. With the expected masses of mobile network radio equipment as commodities, in the form of Home NB/eNBs, this aspect becomes even more crucial.
It is necessary to ensure that ES does not lead to service degradation or inefficiencies in the network. In particular:
• the activation status of radio stations (on/off) introduces a new scale of dynamicity for the UE and network;
• mass effects in signalling potentially endanger the network stability and need to be handled properly.
It is unclear whether and how currently defined procedures are able to cope with, and eventually can be optimized for, ES conditions; thus a systematic study is needed.
The study aims, within the defined CT1 work areas, at:
• analysing UE idle mode procedures and UE-Core Network signalling resulting from frequent switch on/off of radio equipment in all 3GPP accesses, including home cell deployment and I-WLAN;
• performing a corresponding analysis for connected mode UEs;
• analysing similar impacts from activation status of non-3GPP access networks;
• documenting limitations, weaknesses and inefficiencies in these procedures, with emphasis on mass effects in the UE-Core Network signalling;
• studying potential optimizations and enhancements to these procedures;
The study shall also evaluate and give recommendations on potential enhancements to 3GPP specifications (whether and where they are seen necessary).
Study on Solutions for Energy Saving within UTRA Node B
Due to the need to reduce energy consumption within operators’ networks, and considering the large amount of UMTS network equipment deployed in the field around the world, the standardisation of methods to save energy in UMTS Node Bs is seen as an important area of study for 3GPP.There has not been a large amount of focus on energy-saving in UMTS networks so far in 3GPP, although some solutions have been agreed in Release 9. Therefore it is proposed to start an initial study phase to identify solutions and perform any initial evaluation, such that a subset of these proposals can be used as the basis for further investigation of their feasibility.
The objective is to do an initial study to identify potential solutions to enable energy saving within UMTS Node-Bs, and do light initial evaluation of the proposed solutions, with the aim that a subset of them can be taken forward for further investigation as part of a more focused study in 3GPP.
The solutions identified in this study item should consider the following aspects:
• Impacts on the time for legacy and new UEs to gain access to service from the Node B
• Impacts on legacy and new terminals (e.g. power consumption, mobility)
Some initial indication of these aspects in relation to the proposed solutions should be provided.
Study on Network Energy Saving for E-UTRAN
The power efficiency in the infrastructure and terminal should be an essential part of the cost-related requirements in LTE-A. There is a strong need to investigate possible network energy saving mechanisms to reduce CO2 emission and OPEX of operators.
Although some solutions have been proposed and part of them have been agreed in Release-9, there has not been a large amount of attention on energy saving for E-UTRAN so far. Many potential solutions are not fully shown and discussed yet. Therefore, it is proposed to start an initial study phase to identify solutions, evaluate their gains and impacts on specifications.
The following use cases will be considered in this study item:
• Intra-eNB energy saving
• Inter-eNB energy saving
• Inter-RAT energy saving
Intra-eNB energy saving, in EUTRAN network, a single cell can operate in energy saving mode when the resource utilization is sufficiently low. In this case, the reduction of energy consumption will be mainly based on traffic monitoring with regard to QoS and coverage assurance.
A lot of work on Inter-eNB energy saving has already been done for both LTE and UTRA in Rel-9. This Study Item will investigate additional aspects (if any) on top of what was already agreed for R9.
Inter-RAT energy saving, in this use case, legacy networks, i.e. GERAN and UTRAN, provide radio coverage together with E-UTRAN. For example E-UTRAN Cell A is totally covered by UTRAN Cell B. Cell B is deployed to provide basic coverage of the voice or medium/low-speed data services in the area, while Cell A enhances the capability of the area to support high-speed data services. Then the energy saving procedure can be enabled based on the interaction of E-UTRAN and UTRAN system.
The objective of this study item is to identify potential solutions for energy saving in E-UTRAN and perform initial evaluation of the proposed solutions, so that a subset of them can be used as the basis for further investigation and standardization.
Energy saving solutions identified in this study item should be justified by valid scenario(s), and based on cell/network load situation. Impacts on legacy and new terminals when introducing an energy saving solution should be carefully considered. The scope of the study item shall be as follows:
• User accessibility should be guaranteed when a cell transfers to energy saving mode
• Backward compatibility shall be ensured and the ability to provide energy saving for Rel-10 network deployment that serves a number of legacy UEs should be considered
• Solutions shall not impact the Uu physical layer
• The solutions should not impact negatively the UE power consumption
RAN2 will focus on the Intra-eNB energy saving, while RAN3 will work on Inter-RAT energy saving and potential additional Inter-eNB energy saving technology.
Study on Solutions for GSM/EDGE BTS Energy Saving
There has not been a large amount of focus on energy-saving in GSM/EDGE networks so far in 3GPP, although some solutions have been agreed in previous Releases, notably MCBTS. Therefore it is proposed to start an initial study phase to identify solutions and perform any initial evaluation, such that a subset of these proposals can be used as the basis for further investigation of their feasibility.
The objective is to study potential solutions to enable energy saving within the BTS (including MCBTS and MSR), and evaluate each proposed solutions in detail. These potential solutions shall focus on the following specific aspects
• Reduction of Power on the BCCH carrier (potentially enabling dynamic adjustment of BCCH power)
• Reduction of power on DL common control channels
• Reduction of power on DL channels in dedicated mode, DTM and packet transfer mode
• Deactivation of cells (e.g. Cell Power Down and Cell DTX like concepts as discussed in RAN)
• Deactivation of other RATs in areas with multi-RAT deployments, for example, where the mobile station could assist the network to suspend/minimise specific in-use RATs at specific times of day
• And any other radio interface impacted power reduction solutions.
The solutions identified in this study item shall also consider the following aspects:
• Impacts on the time for legacy and new mobile stations to gain access to service from the BTS
• Impacts on legacy and new mobile stations to keep the ongoing service (without increasing drop rate)
• Impacts on legacy and new mobile stations implementation and power consumption, e.g. due to reduction in DL power, cell (re-)selection performance, handover performance, etc.
• Impacts on UL/DL coverage balance, especially to CS voice
Solutions shall be considered for both BTS energy saving non-supporting and supporting mobile stations (i.e. solutions that are non-backwards compatible towards legacy mobile stations shall be out of the scope of this study).
Monday, 4 October 2010
Friday, 1 October 2010
I blogged last year about the LTE-A UE categories but then the categories were still under discussion. In the 3GPP RAN WG1#62 LTE-Advanced UE Categories were discussed based on NTT DoCoMo proposal and the data rates are as summarised in the picture above.
Note that category 8 has 1200Mbps DL and 600Mbps UL speed.
The complete report is available here.