3GPP System Building on Releases

LTE - THE Mobile Broadband Standard

Saw this logo in one of the 3GPP presentations. Does anyone know if this is an official logo?

Evolution of 3GPP Security

2nd Workshop by 3GPP and Broadband Forum

3GPP and Broadband Forum held another joint session recently. Here is the summary from that event (3BF-11046.zip)

All presentations and documents from that event is available to download and view here.

Three quick 3GPP Videos

Balazs Bertenyi, Dealing with the data explosion: Speaking about how 3GPP manages Releases and giving details of some of the key LTE features and some new work on the horizon.

Andrew Howell, GERAN and LTE Interworking: Andrew Howell, 3GPP GERAN Chairman, gives some background on the work of the GSM/EDGE RAN groups, including GELTE and the impact of machine type communications over legacy networks in the LTE age.


See also my earlier post on GELTE here.

Atle Monrad is Chairman of the 3GPP Core Network and Terminals group. In this short film, he explains the role of the protocol groups and gives a snap shot of the latest priorities for his group.

If you want to learn more about 3GPP, see earlier blog post here.

A Survey on 3GPP Hetrogeneous Networks

A Survey on 3GPP Hetrogeneous Networks

View more documents from Zahid Ghadialy

Available for limited time to download free from here.

Couple of presentations on GNSS and LCS

I came across couple of presentations from International Conference on Localization and GNSS, held in Tampere, Finland, June 29-30, 2011

This first presentation by Lauri Wirola of Nokia gives good summary of standardized positioning technologies in use today. It also lists the difference between control plane and user plane positioning. The 3GPP based positioning from Rel 5 to Rel 8 has been listed. Overall a very interesting presentation.

Location Standards driving the mass market LCS adoption

View more presentations from Zahid Ghadialy

The second presentation by Ignacio Fernández Hernández of the European Commission, gives an overview of the EU satnav programmes (Galileo, EGNOS) and current R&D status; Present some numbers and findings of the overall GNSS R&D panorama in EU and abroad; Present some trends and challenges in location technologies for the following years. Another interesting presentation I think.

GNSS Programmes and R&D landscape in the EU

View more presentations from Zahid Ghadialy

3GPP Standards Update for FemtoZone during MWC 2011

From the Mobile World Congress, not so long back.

3GPP Standards Update - Adrian Scrase (16/02/2011) from ETSI – World Class Standards on Vimeo.

The presentation is embedded below:

3GPP Standards Update for FemtoZone during MWC 2011

View more presentations from Zahid Ghadialy

3GPP – DVB Workshop for Next generation Mobile TV standards

TSG RAN and TSG CT hosted a joint workshop with DVB project on commonalities between DVB-NGH and eMBMS

The workshop was opened by the RAN Chairman Mr. Takehiro Nakamura on Wednesday 16th March 11:07. This is the joint session between TSG RAN, TSG CT and DVB project expert. TSG CT Chairman Mr. Hannu Hietalahti reminded that the workshop can't make any formal decisions that would be binding on either 3GPP side or DVB project side. Any agreement needs to be confirmed in DVB project and 3GPP separately. From 3GPP side this needs to be done by 3GPP TSG RAN and 3GPP TSG CT meetings during this week. The goal of the workshop is to find a common agreement how to proceed the future work on DVB-NGH and eMBMS convergence and decide the best way forward. The joint session is expected to make recommendations to TSG SA #51 based on the service requirements for DVB-NGH and the commonalities with eMBMS that can be identified. TSG SA #51 will decide the best way forward on 3GPP side.

The MBMS presentation was embedded in this post. The DVB presentation is embedded below:

Co-operation between 3GPP and the DVB Project

View more presentations from Zahid Ghadialy

The minutes of the meeting are available here: http://3gpp.org/ftp/tsg_sa/TSG_SA/TSGS_51/Docs/SP-110185.zip

All the documents from this workshop are available here: http://www.3gpp.org/ftp/workshop/2011-03-16_RAN-CT-DVB/

It was agreed that for any 3GPP work the normal 3GPP working procedures should be used. The supporting 3GPP member companies were requested to initiate Study items in the appropriate 3GPP working groups with the aim of sending them for approval during the next Plenary cycle.

It was noted that 3GPP Rel-11 stage 1 is going to be frozen in September 2011. It was seen 3GPP DVB-NGH can be a part of Rel-11 if there are interest in 3GPP community. The interesting companies are expected to contribute according to 3GPP working procedures.

UMTS-LTE in 3.5GHz

There are two new bands: 3.4-3.6 GHz and 3.6-3.8 GHz decided for Broadband Wireless Access, which are already widely available for licensing in Europe. These bands have earlier been allocated to the Fixed Service on a primary basis in Region 1. Furthermore, the 3.4-3.6 GHz band was allocated to the mobile service on a primary basis and identified for IMT at WRC 07.

These bands constitute a substantial amount of spectrum that will be available in many countries in the short term. In Europe (Region 1) both bands can be used so block sizes could be large for any duplex arrangement.

The UMTS-LTE 3500 MHz Technical Report (3GPP TR 37.801) is already available as a study of current plans in the frequency bands 3.4-3.6 GHz and 3.6-3.8 GHz for UMTS and LTE systems. Specification work is due for first publication in March 2011 (TSG#51), with a series of specifications updated or being created.

The technical report is embedded below:

3GPP TR 37.801: UMTS-LTE 3500 MHz Work Item Technical Report

View more documents from Zahid Ghadialy

3GPP Tutorials via 'The SpecTools'

Some of you may have noticed that the new and revamped 3GPP website have recently started offering 3GPP specs and features tutorials via The SpecTools. There is quite a lot of useful information and most of it is premium but a lot is free as well.

So the new starters or those wishing to refresh their knowledge feel free to check this out:

http://www.thespectool.com/3gpp/index.php

The 3GPP release 8 IMS Implementation, Deployment & Testing workshop

The 3GPP release 8 IMS Implementation, Deployment & Testing workshop took place in Sophia Antipolis on 24-25 November 2010.

The event was attended by 70 delegates actively participating to the discussions.

Presenting companies included: Tel : A1 Telekom Austria, Alcatel Lucent, Codenomicon, Conformiq, Eircom, Elvior, ETSI, France Telecom, GSMA, Huawei, Huawei, Mobitel, NTT DoCoMo, SFR, Telecom Italia, TestingTech, TU Berlin, Wind, Wipro, ZTE.

Here are the highlights from the ETSI document:

Goals and Outcome for this workshop

Share exprience from IMS implementation

Highlight areas for further specifications, for

Standards and Testing

Learn of issues and possible resolutions

Comments from The IMS Network Testing Group

Develop IMS core network test specifications based upon 3GPP, for:

• Interoperability

• conformance

• network integration

Hold interoperability events (IMS Plugtests)

Coordinate with other organisations such as OMA, MSF, GSMA

Implementations

• Beyond small islands, second wave to replace unscalable, unmaintenable early VoIP systems

• Implementation options - Hybrid CS-GW for transition from CS to LTE, which already has 2 million subscribers on IMS/CS-GW/RNC

• Auto provisioning - to simplify complexity

• IMS functions must be implemented in the core – not in any access network, such as LTE, and can be used for non-Voice as well

Implementing RCS (Rich Communication Suite)

• RCS trial feedback - Good feedback from 400 trial users on RCS but difficult to configure SBC

• RCS implementations should include aggregation with SNS (Social Network Services)– eg contact list from Facebook

• Most appreciated feature of RCS is: - cross-operator interworking and compatibility with ordinary phones, not just smartphones

Specific Issues and Resolutions

• FAX – Delay and Jitter issues - FTTH will solve long delays etc

• Emergency and Lawful Intercept with IMS -There are standards and developed solutions available but Currently still falls back to CS /TDM

• Data Provisioning speed is important, to achieve no service interruption.

• 3GPP II-NNI: Inter-IMS Network to Network Interface - Two levels: Solx (service with control function) and Coix (connection – a pipe for media).

• “PathFinder” Global ENUM – like DNS for phone number; It is a solution to number portability and can optimise routing

About Services

• Most issues are Beyond IMS - integrating OSS/BSS, existing systems, inter-vendors interfaces

• IMS and IN - Pity the Standards did not bring IN and IMS close together; Need iFC enhancements, like in IN; Need to support combining services

• OTT and SNS dominate growth - occupies the minds of commercial people, GSMA-like services have slowed down

• Service layer (Wipro) – Telcos want one SDP to serve all - include IMS and non-IMS services, human and non-humans on NAB, context based, and charge only what is ‘consumed’

Testing Methods, Tools and Test Beds

• Integrate Conformance checking with interoperability testing

• Automation of interoperability trace checking – it can reduce costs by more than 50 % compared to manual validation

• Independent Test Bed- available EPC playground for prototyping applications

• Protocol message customisation tool - allows changing the message and customise the flow

• Security testing tool - testing by ‘fuzzing’, 100% TTCN free – everything is already build in

• IMS is a multi vendor environment - Testing and validation must be an integral part of the deployment process

Memorable Quotes

“IMS is a Journey, not a destination” (ALU)

“SDP is almost anything” (Matjas Bericic, Mobitel)

“Voice as an app versus Voice as a Service” is a challenge (Manuel Vexler, Huawei)

“IMS is not a box, it is a network” (Matjas Bericic, Mobitel)

“global ENUM is DNS for phone numbers” (Adrian Dodd, GSMA)

“Kill with one SIP” (Ari Takanen, Codenomicon)

“ IOP is the red thread running through the entire ETSI standards development process “ (Milan Zoric, ETSI)

All documents from this workshop is available at: http://docbox.etsi.org/Workshop/2010/201011_IMSWORKSHOP/

Network Improvements for Machine Type Communications (NIMTC)

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.

Definitions:

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:

The M2M Switch - turning the wireless business model upside down

MARKET FOR M2M APPLICATIONS EXPLODES

Embedded Mobile M2M Modem Market on Track to More Than Triple in 2010

3GPP Green activities / Energy Saving initiatives

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-Optimization
• 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).

1200Mbps DL with LTE-Advanced

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.

Via: WirelessMoves.

3GPP and 3G Americas workshop in Latam LTE Summit

3GPP and 3G Americas held a LTE Standards workshop in advance of this years’ LTE Latin America Conference, held in Rio de Janeiro 26-28 April.

Speakers from Operators and Manufacturers’ looked at the huge potential for HSPA and LTE networks and discussed Standards and Regulatory issues that are affecting LTE Roadmaps for the Latin America Region.

Topics such as equipment availability and spectrum scarcity were high on the agenda, along with discussions on systems architecture evolution and backhaul issues.

The presentations from the workshop are available on-line HERE.

Individual presentations could be downloaded from the links below:

• Operator Presentations
  

  • VIVO - Oportunidades e Desafios Banda Larga Móvel no Brasil
    
  • CLARO - Operator Strategies for Mobile Broadband
    
  • NTT DOCOMO - RAN Migration Strategy

  
  
• Manufacturers’ Presentations
  
  • Ericsson - Perspective Setorial de HSPA Evoluido
    
  • NSN - Migrating from HSPA to HSPA+ and LTE
  
  
• 3GPP and 3G Americas Presentations
  
  • Marketplace update
    Spectrum Policy and Recommendations
    
  • 3GPP Standards Roadmap

Operator Top Ten Requirements for the networks

Operation Requirements for next generation multi-technology networks are the key topic that brought 3GPP, NGMN and TM Forum together for a workshop held March 29-30 2010 in Bonn. The two-day workshop was attended by forty industry experts who worked on use cases and requirements in three parallel work streams and provided recommendations for next steps.

At the Bonn workshop, the 3GPP Telecom Management working group - SA5 - presented background data on the SA5 work program to date, much of which meets the needs of the NGMN Top Ten Requirements:

• Quality and Quantity of Alarms
• Automatic Software Management
• Energy Saving
• LTE Automatic Neighbour Relation (ANR) and Self Organizing Networks (SON) Operation
• Performance Management in Real-time
• Substitution of Monitoring Probes by Infrastructure Inherent Trace Functionality
• eNodeB Plug & Play Self-Commissioning
• OSS Standard Itf-N
• LTE Parameter Optimization
• Automatic Inventory

The workshop conclusions acknowledged that:

• Standards specified by SA5 over the last ten years provide a widely deployed, fully re-usable and expandable solution for management of Next Generation Networks,
• NGMN Top Ten Requirements are mostly satisfied already by 3GPP SA5 specifications, the missing functionalities will be addressed in 3GPP Release 10 (due December 2010),
• The ongoing 3GPP-TMF alignment program provides an excellent opportunity to address network management of Wireless-Wireline convergence based on the 3GPP IRP framework.

At the end of this workshop, the SA5 Chairman Christian Toche said:

"This workshop has identified important requirements and allowed TMF and 3GPP to compare their solutions that can satisfy Operators requirements, of whom many are already supported in 3GPP specifications. I am confident that, as long as the representation from each group is maintained at the right level, an alignment of the 3GPP and TM Forum specifications will result from this cooperation, satisfying the requirements for use in convergent network operational environment."

Christian Toche identified that the next step includes the need for the two ongoing Network Management harmonization projects with the TM Forum - On FM and resource modelling - to be completed.

Further progress on the alignment of 3GPP and TMF specifications will be made at the follow-up workshop on May 6-7, 2010 in Montreal

3GPP documents from Bonn workshop are available at: ftp://ftp.3gpp.org/tsg_sa/WG5_TM/Ad-hoc_meetings/2010-05-Top_10/Docs/S5w100004.zip

3GPP Technology Standards Roadmap

New presentation from Stephen Hayes, Chair 3GPP-SA available on the 3GPP website. Click here.

3GPP and Broadband Forum Collaboration on Fixed Mobile Convergence Standards

Fixed/Mobile Convergence (FMC) was the key topic that brought 3GPP and the Broadband Forum together for their first joint workshop, held February 18-19 in San Francisco. The two-day workshop was attended by 120 industry experts, who reviewed over 40 contributions focused primarily on use cases and joint requirements.

The attendees, primarily 3GPP and Broadband Forum members, also included representatives from ETSI TISPAN, ATIS and other standards bodies. The diverse group came together with a shared goal; to start the process of aligning new FMC work in each organization to best address both fixed and wireless management requirements. The two days spent together allowed the group to identify the key issues at hand and the work that needs to be done. With words of appreciation and encouragement from workshop co-chairs, Stephen Hayes of 3GPP and Dave Allan of the Broadband Forum, each organization took away work items that address both near term and long term next steps for both 3GPP and the Broadband Forum.


Through liaison communications and technical contributions into each organization, joint requirements will be shared, and another workshop is envisioned for the future after a scope and gap analysis is performed by the organizations.

Workshop documents and presentations are at available…on line

Presentations & Papers from the Workshop:

• Beyond FMC Interworking UDC for FMC
• Proposed Use Case and Requirement based on Policy Control in FMC
• Proposed Architecture for Policy Control in FMC
• Seamless WLAN offload
• 3GPP EPC Overview
• Broadband Forum Status (Revised version)
• 3GPP-BBF Interworking - Mobility-Roaming-Nomadism (See Workshop docs for various revisions of this document – Last version)
• 3GPP-BBF Interworking - Authentication/Authorization/Accounting
• 3GPP-BBF Interworking Policy & QoS
• High level analysis of Interworking between fixed NW access and 3GPP domain
• ATIS’ Organizational Efforts on FMC
• ATIS Exploratory Group on Convergence (EGC) Report & Recommendations
• 3GPP-BBF Interworking - Use Cases for Public and Enterprise Wireline Interworking
• 3GPP-BBF Interworking - S9 Interface: Requirements and Protocol Selection Criteria
• 3GPP-BBF Interworking - Proposal for PCRF Based BPCF
• Media and Codec policies architecture with converged Next Generation Networks
• Focus on working procedures for the policy control aspect of FMC
• PCRF-BPCF Functional Split and Information Exchange
• View on FMC – Policy Control
• ETSI TISPANPolicy Management Overview
• 3GPP Work Item Description - Support for BBF Accesses Interworking
• WT-203 - Interworking between next Generation Fixed and 3gpp wireless access
• Fixed Mobile Interworking - QoS Control via S9
• Policy Interworking – How to setup QoS for a 3GPP UE in a BBF domain
• Fixed Mobile Interworking - Establishing the s9 Session
• Connectivity and Mobility Considerations
• Authenticaton Conundrum
• TISPAN Policy Management Overview
• 3GPP-BBF Architecture - Mobility aspects
• Change Request to 3GPP Technical Specification 22.278 - Addition of operational requirements for Fixed Mobile Convergence
• Key Workshop findings

Takehiro Nakamura on LTE Radio Aspects

In summary:

Release 8 - Minor change requests to it based on March 2009 freeze;
Release 9 - an enhanced version of Release 8 and additional features;
Release 10 (LTE-Advanced) - proposed as an IMT-Advanced and is expected to be approved by December 2010; major differences between LTE and LTE-Advanced

Via: LTE Portal