3GPP TR 36.913 V10.0.

0 (2011-03)
Technical Report

3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Requirements for further advancements for volved !niversal Terrestrial Radio Access " #!TRA$ "%T #Advanced$ "Release &'$

The present document has been developed within the 3rd Generation Partnership Project (3GPP TM) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Or ani!ational Partners and shall not be implemented. This "pecification is provided for future development wor# within 3GPP only. The Or ani!ational Partners accept no liability for any use of this "pecification. "pecifications and reports for implementation of the 3GPP TM system should be obtained via the 3GPP Or ani!ational Partners$ Publications Offices.

Release &'

3GPP TR 3()*&3 +&')')' ",'&&#'3$

%eywords
LTE, Radio

3GPP Postal address 3GPP support office address

650 Route des Lucioles - So !ia "#ti olis Val$o##e - %R"&'E Tel.( )33 * 92 9* *2 00 %a+( )33 * 93 65 *, 16

&nternet
!tt (--....3/ .o0/

Copyright Notification 'o part may be reproduced e(cept as authori!ed by written permission. The copyri ht and the fore oin restriction e(tend to reproduction in all media.
) *+,,- 3GPP Or ani!ational Partners (./&0- .T&"- 11".- 2T"&- TT.- TT1). .ll ri hts reserved. 3MT"4 is a Trade Mar# of 2T"& re istered for the benefit of its members 3GPP4 is a Trade Mar# of 2T"& re istered for the benefit of its Members and of the 3GPP Or ani!ational Partners 5T24 is a Trade Mar# of 2T"& currently bein re istered for the benefit of its Members and of the 3GPP Or ani!ational Partners G"M6 and the G"M lo o are re istered and owned by the G"M .ssociation

3GPP

Release &'

3GPP TR 3()*&3 +&')')' ",'&&#'3$

'o#te#ts
7oreword.......................................................................................................................................................8 , "cope..........................................................................................................................................................9 * /eferences..................................................................................................................................................9 3 :efinitions- symbols and abbreviations....................................................................................................9
3., :efinitions........................................................................................................................................................ 9 3.* "ymbols............................................................................................................................................................ 9 3.3 .bbreviations................................................................................................................................................... 9

8 &ntroduction................................................................................................................................................9 9 Objective....................................................................................................................................................; ; General re<uirements.................................................................................................................................= > 1apability?related re<uirements................................................................................................................=

>., Pea# :ata /ate................................................................................................................................................. = >.* 5atency............................................................................................................................................................. = >.*., 1?plane latency.............................................................................................................................................. = >.*.,., 1?plane capacity......................................................................................................................................... @ >.*.* 3?Plane latency............................................................................................................................................. @

= "ystem performance re<uirements............................................................................................................@

=., "pectrum efficiency.......................................................................................................................................... @ =.,., Pea# spectrum efficiency............................................................................................................................... @ =.,.* .vera e spectrum efficiency.......................................................................................................................... @ =.,.3 1ell ed e user throu hput............................................................................................................................ ,+ =.,.8 Ao&P capacity.............................................................................................................................................. ,, =.* Mobility.......................................................................................................................................................... ,, =.3 1overa e........................................................................................................................................................ ,, =.8 7urther 2nhanced M0M"............................................................................................................................... ,, =.9 'etwor# synchroni!ation................................................................................................................................ ,,

@ :eployment?related re<uirements...........................................................................................................,,
@., :eployment scenarios..................................................................................................................................... ,, @.* "pectrum fle(ibility........................................................................................................................................ ,* @.3 "pectrum deployment..................................................................................................................................... ,* @.8 1o?e(istence and interwor#in with le acy /.Ts........................................................................................... ,*

,+ /e<uirements for 2?3T/.' architecture and mi ration.....................................................................,3 ,, /adio /esource Mana ement re<uirements.........................................................................................,3 ,* 1omple(ity re<uirements......................................................................................................................,3 ,3 1ost?related re<uirements......................................................................................................................,3 ,8 "ervice?related re<uirements.................................................................................................................,3 Annex A (informative): System performance evaluation model ................................................................................................................14 .., "ystem performance evaluation model...............................................................................................,8 Annex B (informative): Change history......................................................................................1

3GPP

Release &'

3GPP TR 3()*&3 +&')')' ",'&&#'3$

%o0e.o0d
This Technical /eport has been produced by the 3rd Generation Partnership Project (3GPP). The contents of the present document are subject to continuin wor# within the T"G and may chan e followin formal T"G approval. "hould the T"G modify the contents of the present document- it will be re?released by the T"G with an identifyin chan e of release date and an increase in version number as followsB Aersion (.y.! whereB ( the first di itB , presented to T"G for informationC * presented to T"G for approvalC 3 or reater indicates T"G approved document under chan e control. y the second di it is incremented for all chan es of substance- i.e. technical enhancements- correctionsupdates- etc. ! the third di it is incremented when editorial only chan es have been incorporated in the document.

3GPP

Release &'

3GPP TR 3()*&3 +&')')' ",'&&#'3$

1 Sco e
This document contains re<uirements for the further advancements for 2?3T/.D2?3T/.'.

2 Re1e0e#ces
The followin documents contain provisions which- throu h reference in this te(t- constitute provisions of the present document. /eferences are either specific (identified by date of publication- edition number- version number- etc.) or non?specific. 7or a specific reference- subse<uent revisions do not apply. 7or a non?specific reference- the latest version applies. &n the case of a reference to a 3GPP document (includin a G"M document)- a non?specific reference implicitly refers to the latest version of that document in the same Release as the present document. E,F E*F E3F E8F E9F (void) 3GPP T/ *,.@+9B GAocabulary for 3GPP "pecificationsG. 3GPP T/ *9.@,3B G/e<uirements for 2volved 3T/. (2?3T/.) and 2volved 3T/.' (2? 3T/.')G. ITU-R Circular Letter 5/LCCE/2 on IMT-Advanced 3GPP T/ *9.@,*B G7easibility study for evolved 3niversal Terrestrial /adio .ccess (3T/.) and 3niversal Terrestrial /adio .ccess 'etwor# (3T/.')G.

3 2e1i#itio#s, s34$ols a#d a$$0e5iatio#s

3.1
Aoid

2e1i#itio#s S34$ols "$$0e5iatio#s

3.2
Aoid

3.3

7or the purposes of the present document- the abbreviations defined in 3GPP T" *,.@+9 E*F and the followin applyB

* 6#t0oductio#
.t the 3GPP T"G /.' H3@ meetin - the "tudy &tem description on G7urther .dvancements for 2?3T/. (5T2? .dvanced)G was approved (/P?+=+,3>). The justification of the "tudy &tem was as followsC

3GPP

Release &'

3GPP TR 3()*&3 +&')')' ",'&&#'3$

&MT?.dvanced is enterin the phase of the process in &T3?/ addressin the development of the terrestrial radio interface recommendations. To announce this sta e of the process for &MT?.dvanced- &T3?/ has issued a 1ircular 5etter(15) to invite submission of candidate /adio &nterface Technolo ies (/&Ts) or a set of /&Ts ("/&Ts) for &MT? .dvanced. The #ey features of &MT?.dvanced delineated in the 15 areB ? ? ? ? ? ? ? ? a hi h de ree of commonality of functionality worldwide while retainin the fle(ibility to support a wide ran e of services and applications in a cost efficient mannerC compatibility of services within &MT and with fi(ed networ#sC capability of interwor#in with other radio access systemsC hi h <uality mobile servicesC user e<uipment suitable for worldwide useC user?friendly applications- services and e<uipmentC worldwide roamin capabilityC and enhanced pea# data rates to support advanced services and applications (,++ MbitDs for hi h and , GbitDs for low mobility were established as tar ets for research) .

The base line re<uirements for &MT?.dvanced will be concluded in &T3?/ IP 9: H* (June *++=) and communicated in an .ddendum to the 1ircular 5etter in the July *++= timeframe. &n the I/1+>- the followin spectrum bands were proposed as additions to the prior identified bands- and the parts of the e(istin and new bands are lobally or re ionally identified for &MT- which is the new root term to encompass both &MT?*+++ and &MT?.dvanced. ? ? ? ? 89+ MK! band 3K7 band (;@=?@;+ MK!) *.3 GK! band 1?band(38++?8*++ MK!)

&n 3GPP- 2?3T/. should be further evolved for the future releases in accordance withB ? ? 3GPP operator re<uirements for the evolution of 2?3T/. The need to meetDe(ceed the &MT?.dvanced capabilities.

1onsiderin the above- 3GPP T"G?/.' should study further advancements for 2?3T/. (5T2?.dvanced) toward meetin B ? ? /e<uirements for &MT?.dvanced and provide &T3?/ with proposals of /&Ts or "/&Ts accordin to the defined &T3?/ time schedule provided in the 1ircular 5etter and its .ddendums. 3GPP operators re<uirements for the evolution of 2?3T/.

7$8ecti5e
.) :efine a framewor# for further advancements of 2?3T/. and 2?3T/.' (to be referred to as .dvanced 2? 3T/. and .dvanced 23T/.' considerin B ? ? The time schedule of &T3?/ That the wor# on .dvanced 2?3T/. and .dvanced 2?3T/.' must not introduce any delay to the completion of the /elease = specification of 2?3T/. and 2?3T/.'

The objective of 7urther .dvancements for 2?3T/. is as followsC

3GPP

Release &'

3GPP TR 3()*&3 +&')')' ",'&&#'3$

That the eneral enhancements of specifications for /elease = 2?3T/. and 2?3T/.' are maintained and pro ressed in a focused and efficient manner.

0) :efine re<uirements for .dvanced 2?3T/. and .dvanced 2?3T/.' based on the &T3?/ re<uirements for &MT?.dvanced as well as 3GPP operators own re<uirements for advancin /elease = 2?3T/. .': 2?3T/.' considerin B ? ? ? ? 2?3T/. radio technolo y and architecture improvements "upport for all radio modes of operation &nterwor#in with le acy /.Ts (scenarios and performance re<uirements) 0ac#ward compatibility of .dvanced 2?3T/. and .dvanced 2?3T/.' with /elease = 2?3T/. and 2? 3T/.' i.e. ? ? ? ? an /elease = 2?3T/. terminal can wor# in an .dvanced 2?3T/.'an .dvanced 2?3T/. terminal can wor# in an /elease = 2?3T/.' and non?bac#ward compatible elements could be considered based on /.' decision

'ewly identified fre<uency bands and e(istin fre<uency bands- and their advanta es and limitations- in particular- the consideration of the I/1?+> conclusions- to ensure that .dvanced 2?3T/. can accommodate radio channel bandwidths commensurate with the availability in parts of the world of wideband channels in the spectrum allocations (above *+ MK!) and at the same time bein mindful on the need to accommodate those parts of the world where the spectrum allocations will not have availability of wideband channels

1) &dentify potential solutions- technolo ies for the .dvanced 2?3T/. and .dvanced 2?3T/.'. The study areas includeB ? ? ? ? ? Physical layer /adio interface layer * and //1 2?3T/.' architecture /7- includin .spects of wider channel bandwidth than *+ MK! .dvanced system concepts

:) To develop documents that will serve as a basis for the documentation to be submitted to &T3?/ to provide the 3GPP proposals for &MT?.dvancedB ,) .n G2arly ProposalG submission that would be sent to &T3?/- to be a reed at /.' H8, (@?,* "eptember *++=)- for submission to IP 9: H3 (=?,9 October *++=). *) . G1omplete Technolo yG submission that would be sent to &T3?/- to be a reed at /.' H88 (*;?*@ May *++@)- for submission to IP 9: H9 (planned for ,+?,> June *++@). 3) . G7inalG submission to incorporate updates- additional specific details or feature additions- and the re<uired self?evaluation that would be sent to &T3?/- to be a reed at /.' H89 (**?*9 "eptember *++@)- for submission to IP 9: H; (planned for ,3?*+ Oct *++@). ? 3GPP should ta#e note- that by &T3?/ convention- the formal submission deadline for &T3?/ meetin s has been established as ,;B++ hours 3T1- seven calendar days prior to the start of the meetin .

2) Ma#e recommendations for future I&s 7) 7or reference- the 1ircular 5etter as received from the &T3?/ (and future .ddendums to the same) are anne(ed to this Ior# &tem and should become an inte ral part of the I&.

3GPP

Release &'

3GPP TR 3()*&3 +&')')' ",'&&#'3$

6
The followin ? ? ?

Ge#e0al 0e9ui0e4e#ts
eneral re<uirements are valid for .dvanced 2?3T/. and .dvanced 2?3T/.' .dvanced 2?3T/. and .dvanced 2?3T/.' shall be an evolution of /elease = 2?3T/. and 2?3T/.' .ll relevant re<uirement in E3F are valid also for .dvanced 2?3T/. and .dvanced 2?3T/.' .dvanced 2?3T/. and .dvanced 2?3T/.' shall meet or e(ceed &MT?.dvanced re<uirements within the &T3?/ time plan

The e(pectancy is that .dvanced 2?3T/. should provide substantially hi her performance compared to what is e(pected to be the &MT?.dvanced re<uirements in &T3?/. The values provided in clauses > and = have been e(pressed as preferred performance of .dvanced 2?3T/.. These values are reco nised as bein very ambitious- especially in li ht of the &T3?/ time plan- and the performance evaluation results enerated for 5T2 /=- but are adopted as lon term tar et for .dvanced 2?3T/.G

,
,.1

'a a$ilit3-0elated 0e9ui0e4e#ts

Pea: 2ata Rate

The pea# data rate is the ma(imum data rate to be supported from a system re<uirement viewpoint (i.e. not from radio performance re<uirement viewpoint) re ardless of radio interface parameters such as the transmission bandwidth and antenna confi uration. .dvanced 2?3T/. should support si nificantly increased instantaneous pea# data rates. .t a minimum- .dvanced 2?3T/. should support the #ey feature of &MT?.dvanced which is stated in the 1ircular 5etter from the &T3?/ as Genhanced pea# data rates to support advanced services and applications (,++ MbitDs for hi h and , GbitDs for low mobility were established as tar ets for research)G The system should tar et a downlin# pea# data rate of , Gbps and an uplin# pea# data rate of 9++ Mbps.

,.2
,.2.1

Late#c3
'- la#e late#c3

The overall 1?Plane latency shall be si nificantly decreased compared to 2P" /el?=. The 1?Plane latency ta#es into account /.' and 1' latencies (e(cludin the transfer latency on the ", interface) in unloaded conditions. The tar et for transition time from &dle mode (with &P address allocated) to 1onnected mode is less than 9+ ms includin the establishment of the user plane (e(cludin the ", transfer delay). The tar et for the transition from a Gdormant stateG in 1onnected Mode (i.e. :/L substate in 1onnected Mode in 2?3T/.') is less than ,+ ms (e(cludin the :/L delay).

3GPP

Release &'

3GPP TR 3()*&3 +&')')' ",'&&#'3$

Less t!a# 10 4s "cti5e (i#-s3#c) "cti5e ; <do04a#t= (u#-s3#c)

Less t!a# 50 4s 'a4 ed-state

1i2ure /)&3 Requirements for state transitions

,.2.1.1

'- la#e ca acit3

The system should be able to support at least 3++ active users without :/L in a 9 MK! bandwidth. The same number of //1 connections with :/L as in /elease = 2?3T/. and 2?3T/.' (,;#) is e(pected.

,.2.2

>-Pla#e late#c3

.dvanced 2?3T/. and .dvanced 2?3T/.' should allow for reduced 3?plane latency compared to /elease = 2? 3T/. and 2?3T/.'- specifically in situations whereB ? ? The 32 does not have a valid schedulin assi nment The 32 needs to synchronise and obtain a schedulin assi nment

The 3?Plane latency is defined as the minimum achievable user plane latency with the system confi urations optimi!ed for latency

?
?.1

S3ste4 e01o04a#ce 0e9ui0e4e#ts

S ect0u4 e11icie#c3

&n this section- the tar et for pea# spectrum efficiency- the avera e spectrum efficiency- and cell ed e spectrum efficiency are defined. The tar et for avera e spectrum efficiency and the cell ed e user throu hput efficiency should be iven a hi her priority than the tar et for pea# spectrum efficiency and Ao&P capacity. The tar et for avera e spectrum efficiency and the cell ed e spectrum efficiency should be achieved simultaneously.

?.1.1

Pea: s ect0u4 e11icie#c3

The pea# spectrum efficiency is the hi hest data rate normalised by overall cell bandwidth assumin error?free conditions- when all available radio resources for the correspondin lin# direction are assi ned to a sin le 32. The system tar et to support downlin# pea# spectrum efficiency of 3+ bpsDK! and uplin# pea# spectrum efficiency of ,9 bpsDK!. .ssumption of antenna confi uration is =(= or less for :5 and 8(8 or less for 35

?.1.2

"5e0a/e s ect0u4 e11icie#c3

.vera e spectrum efficiency is defined as the a re ate throu hput of all users (the number of correctly received bits over a certain period of time) normali!ed by the overall cell bandwidth divided by the number of cells. The avera e spectrum efficiency is measured in bDsDK!Dcell.

3GPP

Release &'

&'

3GPP TR 3()*&3 +&')')' ",'&&#'3$

.dvanced 2?3T/. should tar et the avera e spectrum efficiency to be as hi h as possible- iven a reasonable system comple(ity. The e(pectation at the end of the study item is that the values of all the tar ets (of the different confi urations) will be made available- but currently the evaluation for the blan#ed out bo(es in the table below- are a lower priority.

.dvanced 2?3T/. should tar et the avera e spectrum efficiencies in different environments below. Ta4le 0)& Tar2ets for avera2e spectrum efficienc5 /adio env. .nt. 1onfi 35 ,(* *(8 :5 *(* 8(* 8(8 1ase , EbpsDK!DcellF ,.* *.+ *.8 *.; 3.> Micro &ndoor /uralD Ki h speed

'OT2B There is a need to define all the cases in the tables. 1ase , is defined in .nne( .. 1ase , is included to permit 3GPP to compare .dvanced 2?3T/. to /elease = 2?3T/.. 3GPP should consider that the other environments would be based on the &T3?/ environments (these are currently desi nated as Ki h "peed- 0ase 1overa e 3rbanMicrocellular- M &ndoor). These environments are defined in /ecommendationD/eports E&MT.T21KF and E&MT.2A.5F which are e(pected to be concluded in &T3?/ IP 9: in early July *++=. "uch definitions would ensure consistency with developin submissions to &T3?/ for &MT?.dvanced and for consistency with performin simulations- etc. Thus 3GPP would have 9 environments 1ase , plus the 8 &T3?/ environments.

?.1.3

'ell ed/e use0 t!0ou/! ut

The cell ed e user throu hput is defined as the 9N point of 1:7 of the user throu hput normali!ed with the overall cell bandwidth. .dvanced 2?3T/. should tar et the cell ed e user throu hput to be as hi h as possible- iven a reasonable system comple(ity. . more homo eneous distribution of the user e(perience over the covera e area is hi hly desirable and therefore a special focus should be put on improvin the cell ed e performance. The e(pectation at the end of the study item is that the values of all the tar ets (of the different confi urations) will be made available- but currently the evaluation for the blan#ed out bo(es in the table below- are a lower priority. .dvanced 2?3T/. should tar et the cell ed e user throu hput below in different environments Ta4le 0), Tar2ets for cell ed2e throu2hput /adio env. 1ase , Micro EbpsDK!DcellDuserOF &ndoor /uralD Ki h speed

.nt. 1onfi 35 ,(* +.+8 *(8 +.+> :5 *(* +.+> 8(* +.+@ 8(8 +.,* O ,+ users uniform?randomly dropped in the cell

3GPP

Release &'

&&

3GPP TR 3()*&3 +&')')' ",'&&#'3$

'OT2B There is a need to define all the cases in the tables. 1ase , is defined in .nne( .. 1ase , is included to permit 3GPP to compare .dvanced 2?3T/. to /elease = 2?3T/.. 3GPP should consider that the other environments would be based on the &T3?/ environments (these are currently desi nated as Ki h "peed0ase 1overa e 3rban- Microcellular- M &ndoor). These environments are defined in /ecommendationD/eports E&MT.T21KF and E&MT.2A.5F which are e(pected to be concluded in &T3?/ IP 9: in early July *++=. "uch definitions would ensure consistency with developin submissions to &T3?/ for &MT?.dvanced and for consistency with performin simulations- etc. Thus 3GPP would have 9 environments 1ase , plus the 8 &T3?/ environments.

?.1.*

Vo6P ca acit3

Ao&P capacity should be improved relative to that shown in the evaluation for 2?3T/. and 2?3T/.' in E9F for all antenna confi urations.

?.2

@o$ilit3

The system shall support mobility across the cellular networ# for various mobile speeds up to 39+#mDh (or perhaps even up to 9++#mDh dependin on the fre<uency band). "ystem performance shall be enhanced for + to ,+#mDh and preferably enhanced but at least no worse than 2?3T/. and 2?3T/.' for hi her speeds

?.3

'o5e0a/e

/e<uirements for 1overa e in /elease = 2?3T/. and 2?3T/.' E3F are applicable for .dvanced 2?3T/. and .dvanced 2?3T/.'.

?.*

%u0t!e0 E#!a#ced @A@S

The tar ets for M0M" in .dvanced 2?3T/. and .dvanced 2?3T/.' should be better than those studied in /elease = 2?3T/. and 2?3T/.' E3F. "pecifically- the tar et spectrum efficiency for M0M" in .dvanced 2?3T/. should be better than that in /elease = 2?3T/..

?.5

&et.o0: s3#c!0o#iBatio#

/e<uirements for 'etwor# synchroni!ation in /elease = 2?3T/. and 2?3T/.' E3F are applicable for .dvanced 2? 3T/. and .dvanced 2?3T/.'.

9
9.1

2e lo34e#t-0elated 0e9ui0e4e#ts
2e lo34e#t sce#a0ios

.dvanced 2?3T/. and .dvanced 2?3T/.' will be deployed as an evolution of /elease = 2?3T/. and 2?3T/.' and on new bands. .dvanced 2?3T/. and .dvanced 2?3T/.' shall be bac#wards compatible with /elease = 2? 3T/. and 2?3T/.' in the sense that ? ? a /elease = 2?3T/. terminal can wor# in an .dvanced 2?3T/.'an .dvanced 2?3T/. terminal can wor# in an /elease = 2?3T/.'

Kowever- non?bac#ward compatible element mi ht be considered if si nificant ain or benefit can be achieved. &t should be e(pected to have increased deployment of indoor e'0 and K'0 in .dvanced 2?3T/.'. &n addition to the deployment scenario in /elease = 2?3T/. and 2?3T/.'- the system shall be considered in indoor scenario.

3GPP

Release &'

&,

3GPP TR 3()*&3 +&')')' ",'&&#'3$

9.2
? ? ? ? ? ?

S ect0u4 1le+i$ilit3
89+P8>+ MK! band;@=P=;* MK! band>@+P=;* MK! band*.3P*.8 GK! band3.8P8.* GK! band- and 8.8?8.@@ GK! band.

The initial identified bands in addition to the already allocated bands in 2?3/. are followsB

.dvanced 2?3T/. shall operate in spectrum allocations of different si!es includin wider spectrum allocations than those of /elease = 2?3T/. to achieve hi her performance and the tar et pea# data rate- e. . up to ,++ MK!. Main focus for wider bandwidth solution than *+MK! should be on consecutive spectrum- but . re ation of the spectrum for .dvanced 2?3T/. should be supported considerin reasonable 32 comple(ity 7:: and T:: should be supported for e(istin paired and unpaired band- respectively 7or new identified band- duple( mode should be studied considerin - e. . delay- spectrum efficiency- operation- 0" and 32 comple(ity and overall co?e(istence aspects especially on adjacent channels

9.3

S ect0u4 de lo34e#t

.dvanced 2?3T/. is re<uired to cope with followin scenariosB a) 1o?e(istence in the same eo raphical area and co?location with G2/.'D3T/.D2?3T/. on adjacent channels. b) 1o?e(istence in the same eo raphical area and co?location between operators on adjacent channels. c) 1o?e(istence on overlappin andDor adjacent spectrum at country borders. d) .dvanced 2?3T/. shall be possible to operate standalone- i.e. there is no need for any other carrier to be available. e) .ll fre<uency bands should be allowed followin release independent fre<uency band principles f) Operation of /elease = 2?3T/. and .dvanced 2?3T/. in the same spectrum

9.*
? ?

'o-e+iste#ce a#d i#te0.o0:i#/ .it! le/ac3 R"Ts

Kandovers with le acy /.Ts 'etwor# sharin

7ollowin features already supported in previous releases are a pre?re<uisite for bein supported by .dvanced 2? 3T/.'B

The same inter?/.T interwor#in capabilities with at least same performance as in /elease = 2?3T/.' shall be supported. &ntra?/.T handover performance shall be same or better than /elease = 2?3T/.'. KO re<uirements for /elease = 2?3T/.' Q .dvanced 2?3T/.' shall be same as intra?.dvanced 2?3T/.' KO performance.

3GPP

Release &'

&3

3GPP TR 3()*&3 +&')')' ",'&&#'3$

10

Re9ui0e4e#ts 1o0 E->TR"& a0c!itectu0e a#d 4i/0atio#

.dvanced 2?3T/.' architecture should be based on /elease = 2?3T/.' architecture. 'ew architecture should be considered in .dvanced 2?3T/.' if si nificant benefit can be e(pected.

11

Radio Resou0ce @a#a/e4e#t 0e9ui0e4e#ts

/adio resource mana ement re<uirements of /elease = 2?3T/. and 2?3T/.' E3F are applicable for .dvanced 2? 3T/. and .dvanced 2?3T/.'.

12

'o4 le+it3 0e9ui0e4e#ts

1omple(ity re<uirements of /elease = 2?3T/. and 2?3T/.' E3F are applicable for .dvanced 2?3T/. and .dvanced 2?3T/.'.

13
? ? ? ? ?

'ost-0elated 0e9ui0e4e#ts
5ow cost of the infrastructure deployment and terminal for .dvanced 2?3T/. and .dvanced 2?3T/.' shall be an essential element Power efficiency in the infrastructure and terminal shall be an essential element 0ac#haulin shall minimi!e cost per bit .dvanced 2?3T/. and .dvanced 2?3T/.' should allow bac#haul usin 5T2 spectrum 7urther enhancements of "O' and self confi uration shall be an essential element- e. .B ? ? "pecial care with respect to "O' shall be ta#en for special deployment scenarios li#e networ# sharin "pecial care with respect to "O' shall be ta#en for mass deployment scenarios li#e in the case of home e'0s- i.e. for &n and Outbound Mobility for home e'ode 0 and problems caused by incorrect behaviour of home e'0s. .voidin need for drive tests &mpact to 32 comple(ity and power consumption needs to be ta#en into account

? ? ? ?

Operation and maintenance tas#s shall be minimi!ed to the ma(imum possible e(tent. Ihere needed it should be based on open interfaces e'ode 0 implementation cost efficiency and fle(ibility for multi?vendor deployments should be considered- such as /7 re<uirements in specific scenarios or base station modularity aspects with e. . remote radio units and open interfaces .ll the interfaces specified shall be open for multi?vendor e<uipment interoperability.

1*

Se05ice-0elated 0e9ui0e4e#ts

"ervice related re<uirements of /elease = 2?3T/. and 2?3T/.' E3F are applicable for .dvanced 2?3T/. and .dvanced 2?3T/.'.

3GPP

Release &'

&-

3GPP TR 3()*&3 +&')')' ",'&&#'3$

"##e+ " (i#1o04ati5e)( S3ste4 e01o04a#ce e5aluatio# 4odel ".1 S3ste4 e01o04a#ce e5aluatio# 4odel

One of the system performance evaluation models in .dvanced 2?3T/. (1ase ,) is the same as the model used for 2? 3T/.. The carrier fre<uency (17)- &nter?site distance (&":)- operatin bandwidth (0I)- penetration loss (P5oss) and 32 speed are iven in Table ..,?,. Ta4le A)&#& 6 3GPP 7ase & model Simulation Cases , C! ('()) *.+ "S# (meters) 9++ B$ (*()) ,+ %&oss (dB) *+ Speed (+m,h) 3

3GPP

Release &'

&.

3GPP TR 3()*&3 +&')')' ",'&&#'3$

"##e+ A (i#1o04ati5e)( '!a#/e !isto03

Ta4le A)&3 8raft 9istor5
7han2e histor5
8ate TSG : TSG 8oc) Su4ject;7omment <ld New

200?-05 R"&C*0 200?-06 2009-06 2009-12 RP-*6 2011-03 RP-51

RP-0?0**5

Su$4itted 1o0 a 0o5al at TSG R"& C*0 Re o0t a 0o5ed at TSG-R"& a#d laced u#de0 c!a#/e co#t0ol @i#o0 edito0ial co00ectio# to title, :e3.o0ds, lo/o, la3out > /0ade to t!e Release 9 - #o tec!#ical c!a#/e > /0ade to t!e Release 10 - #o tec!#ical c!a#/e

1.0.0 ?.0.0 ?.0.1 9.0.0

1.0.0 ?.0.0 ?.0.1 9.0.0 10.0.0

3GPP