3GPP2 LTE WorkshopSEOUL, Korea, 27th– 28th June 2005

3GPP LTE3GPP LTE StatusStatus

SourceSource 3GPP TSG RAN Chairman3GPP TSG RAN Chairman ETSI TC MSG ChairmanETSI TC MSG Chairman

2

3GPP LTE• HistoryHistory

– Workshop in Toronto on November 2nd and 3Workshop in Toronto on November 2nd and 3rdrd 2004 2004• Identification of requirementsIdentification of requirements• Several proposals for radio evolution presentedSeveral proposals for radio evolution presented

– 3GPP TSG RAN#26 in December 20043GPP TSG RAN#26 in December 2004• Approval of the lsit of requirementsApproval of the lsit of requirements• Elaboration of the first time planElaboration of the first time plan• Endorsement of the working methodsEndorsement of the working methods

– 3GPP TSG RAN#28 in March 20043GPP TSG RAN#28 in March 2004• First joint working groups meeting held in Tokyo First joint working groups meeting held in Tokyo

more than 170 delegatesmore than 170 delegates• First draft of the Technical Reports on the First draft of the Technical Reports on the

requirements elaboratedrequirements elaborated• Allowance for the starting of the work in Working Allowance for the starting of the work in Working

Groups Groups

3

3GPP LTE

• History (continued)History (continued)– TSG RAN#28 Meeting in Quebec cityTSG RAN#28 Meeting in Quebec city

• Second Joint working group meeting attended by Second Joint working group meeting attended by more than 120 delegatesmore than 120 delegates

• Completion of the Long term Evolution Completion of the Long term Evolution Requirements reportRequirements report

• Presentation of the LTE Stage 2 draft reportPresentation of the LTE Stage 2 draft report• Reports of the different joint sessions that have Reports of the different joint sessions that have

taken placetaken place– Joint RAN WG2, RAN WG3 TSG SA WG2 on the Joint RAN WG2, RAN WG3 TSG SA WG2 on the

functional split between the access and the corefunctional split between the access and the core– First discussions on Layer 1 during the two First discussions on Layer 1 during the two

meetings of TSG RAN WG1meetings of TSG RAN WG1

4

RAN#31, 8-10 March, ChinaRevised work plan Working assumption on complete concept

Channel structure MIMO scheme to be used for

evaluation Signalling procedures Mobility details

RAN#30, 30 Nov-2 Dec, MaltaRevised work planRAN Architecture including RAN migration scenariosRadio Interface Protocol ArchitectureStates and state transitionsPhysical Layer Basics

Multiple access schemeMacro-diversity or notRF ScenariosMeasurements

RAN#32, 31 May- 2 June, TBDConcept TR for approval

TR having Stage 2 level of details in order for smooth transition to Work Item phase

WIs created and their time plan agreed

RAN#29, 21-23 Sept, TallinRevised work planRAN-CN functional split agreed

RAN-CN migration scenarios included

RAN #27, 9-11 March, Tokyo•Work plan agreed•TR Structure agreed•1st list of requirements

RAN #28, 1-3 June, Quebec•Revised Work plan•Requirement TR approved

deployment scenarios includedrequirements on migration scenarios included

Mar Apr May Jun MarJul Aug Sep Oct Nov Dec Jan Feb

2005 2006

JunApr May

Work Plan for the Long term evolution for the UTRA and UTRAN

5

Long Term Evolution RequirementsLong Term Evolution Requirements• Reduced cost per bitReduced cost per bit

– Improve spectrum efficiency ( e.g. 2-4 x Rel6)Improve spectrum efficiency ( e.g. 2-4 x Rel6)– Reduce cost of backhaul (transmission in UTRAN)Reduce cost of backhaul (transmission in UTRAN)

• Increased service provisioning – more services at lower Increased service provisioning – more services at lower cost with better user experiencecost with better user experience– Focus on delivery of services utilising ”IP” Focus on delivery of services utilising ”IP” – Reduce setup time and round trip timeReduce setup time and round trip time– Increase the support of QoS for the various types of Increase the support of QoS for the various types of

services (e.g. Voice over IP)services (e.g. Voice over IP)– Increase “cell edge bitrate” whilst maintaining same site Increase “cell edge bitrate” whilst maintaining same site

locations as deployed todaylocations as deployed today– Increase peak bitrate (e.g. above 100Mbps DL and above Increase peak bitrate (e.g. above 100Mbps DL and above

50Mbps UL)50Mbps UL)– Enhance the bitrate for MBMS (e.g. 1-3 Mbps)Enhance the bitrate for MBMS (e.g. 1-3 Mbps)

6

Long Term Evolution Requirements

• Flexibility of use of existing and new frequency bandsFlexibility of use of existing and new frequency bands– Allow to deploy in wider and smaller bandwidths than 5 Allow to deploy in wider and smaller bandwidths than 5

MHz ( e.g. ranging from 1.25 to 20MHz)MHz ( e.g. ranging from 1.25 to 20MHz)– Allow variable duplex technology within bands as well Allow variable duplex technology within bands as well

as between bandsas between bands– Non-contiguous spectrum allocations to one UE should Non-contiguous spectrum allocations to one UE should

not be precludednot be precluded– Should consider FDD/TDD convergence?Should consider FDD/TDD convergence?

7

Long Term Evolution Requirements

• Architecture and mobilityArchitecture and mobility– Need to consider UTRAN Evolution and UTRA Evolution Need to consider UTRAN Evolution and UTRA Evolution

at the same time aiming at simplifying the current at the same time aiming at simplifying the current architecturearchitecture

– Shall provide open interfaces to support Multi-vendor Shall provide open interfaces to support Multi-vendor deploymentsdeployments

– Consider robustness – no single point of failureConsider robustness – no single point of failure– Support multi-RAT with resources controlled from the Support multi-RAT with resources controlled from the

networknetwork– Support of seamless mobility to legacy systems as well Support of seamless mobility to legacy systems as well

as to other emerging systems including inter RAT as to other emerging systems including inter RAT Handovers and Service based RAT SelectionHandovers and Service based RAT Selection

– Maintain appropriate level of securityMaintain appropriate level of security• Allow for reasonable terminal power consumptionAllow for reasonable terminal power consumption

8

LTE Technical consideration

• Layer 1 considerationLayer 1 consideration– Several discussion have been conducted Several discussion have been conducted

regarding OFDMregarding OFDM– Majority of the proposal are turning around the Majority of the proposal are turning around the

use of OFDM for the downlink an several use of OFDM for the downlink an several proposals for the uplink including FDM and proposals for the uplink including FDM and WCDMAWCDMA• Also some proposal for multicarrier but Also some proposal for multicarrier but

with less supportwith less support– Discussion on parameters for simulation have Discussion on parameters for simulation have

also started. Several already agreed also started. Several already agreed e.g.technics to be used – QPSK and 16QAM for e.g.technics to be used – QPSK and 16QAM for the different proposals.the different proposals.

9

LTE Technical consideration

• Radio Access Network ArchitectureRadio Access Network Architecture– Discussion have already started to review the Discussion have already started to review the

functional split between the core and the functional split between the core and the access network to fulfill the requirements and access network to fulfill the requirements and improve the current delay in the access improve the current delay in the access network.network.

– Some work has also started in 3GPP TSG SA Some work has also started in 3GPP TSG SA WG2 dealing with review of the core network WG2 dealing with review of the core network architecture. It was agreed at the last TSG SA architecture. It was agreed at the last TSG SA meeting not to link the two part meaning that a meeting not to link the two part meaning that a new LTE will be connected either to the current new LTE will be connected either to the current core or the new core network core or the new core network