Documente Academic
Documente Profesional
Documente Cultură
1 (2013-09) Study on next generation Self !pti"i#ing Network $S!N% for Technical Report &TRAN and ' &TRAN; $Release ()%
3GPP TR 37.822
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 "eport 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 "eports for implementation of the 3GPP TM system should be obtained via the 3GPP Or ani!ational Partners% Publications Offices.
Release ()
&eywords
LTE, radio
'nternet
$tt#+//000.31##.or1
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.
* +,-3. 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$' 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 ()
*o&te&ts
1ontents....................................................................................................................................................3 7oreword...................................................................................................................................................8 'ntroduction...............................................................................................................................................8 - $cope......................................................................................................................................................9 + "eferences..............................................................................................................................................9 3 :efinitions and abbreviations.................................................................................................................9
3.- :efinitions..............................................................................................................................................................9 3.+ /bbreviations.........................................................................................................................................................9
3GPP
Release ()
(ore0ord
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 follows@ Aersion ).y.! where@ ) the first di it@ - presented to T$G for informationB + presented to T$G for approvalB 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. corrections. updates. etc. ! the third di it is incremented when editorial only chan es have been incorporated in the document.
2&trodu tio&
$O( enhancements may be necessary for the interoperability of the e)istin features as well as for the new features and new deployments considered in "el.-+. 'n "el.-- Mobility "obustness Optimisation (M"O) has been enhanced so that identification of the 32 type. for which a failure has occurred may be possible. Other $O( use cases may benefit from similar differentiation in handlin . /ctive antennas allow the creation of multiple vertical and hori!ontal beams ma#in the deployment dynamic. $O( may enhance networ# deployment based on active antennas. 7inally. review of $O( techniCues and verification of any enhancements with re ard to e)istin pre;"el.-+ small cells are part of the study item.
3GPP
Release ()
" o#e
The present document provides descriptions and possible solutions of use cases and analysis of these solutions. 1onsiderations with re ards to reCuested functionality in scope of other 3GPP roups if any. may be captured in this document as well.
2
; ; ;
Re3ere& es
"eferences are either specific (identified by date of publication. edition number. version number. etc.) or non;specific. 7or a specific reference. subseCuent 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. 3GPP T" +-.?,9@ FAocabulary for 3GPP $pecificationsF.
The followin documents contain provisions which. throu h reference in this te)t. constitute provisions of the present document.
D-E
3.1 4e3i&itio&s
7or the purposes of the present document. the terms and definitions iven in T" +-.?,9 D-E and the followin apply. / term defined in the present document ta#es precedence over the definition of the same term. if any. in T" +-.?,9 D-E.
3.2 %''re5iatio&s
7or the purposes of the present document. the abbreviations iven in T" +-.?,9 D-E and the followin apply. /n abbreviation defined in the present document ta#es precedence over the definition of the same abbreviation. if any. in T" +-.?,9 D-E. $O( $elf;Or ani!in (etwor#
3GPP
Release ()
b. $i nal a timer to inform the tar et that it should not hand over the 32 bac# to source within the iven time. c. $i nal a roup identity (defined at source as a bit strin ) in the Mobility $ettin 1han e procedureB later. the tar et. if it accepted the new mobility settin s. applies the new settin s to the 32s handed over successfully with the same roup identity si naled in the KO preparations. 3. $olution with pre;defined 32 roups 'n this solution. the roups are defined in the standard. The mobility settin s chan e procedure is e)tended to include ne otiation of the predefined roups. a. The e(0 e)chan e the roup ': in the handover reCuest. b. The roups are based on commonly #nown parameters. li#e 32 capabilities or release or bearer class.
3GPP
Release ()
Solutions: The problem can be solved in different ways@ -. 1larify that the ne otiation is for the least sensitive 32 (typically le acy 32s). +. 1larify that the ne otiation is for the most sensitive 32s. The clarification can be added as a specification or as an information element in the Mobility $ettin 1han e procedure. /lternatively. the problem may be considered as irrelevant. because the ambi uity was present in the procedure since the "el.?. when it was first specified. Then. the handover tri er points established via Mobility $ettin 1han e procedures should be interpreted as a recommendation that. whenever possible. the ne otiated handover tri er point shall be respected.
+) 1ell $hapin ; ; ; ; ; The solution introduces adaptive or reconfi urable antenna systems. where the main covera e of each cell is maintained unchan ed but the cell ed e can be adapted to load demand. The same P1' is used in all the cell covera e. These adjustments are considered to be on medium time scale (every -h or more seldom). The tri er for the chan e may be O/M reconfi uration (e. . based on collected &P's) or the control unit may be the base station (implementation based). Problems related to e)istin $O( features or enhancements needed@ 77$
3) 1ell splittin ; The solution adopts hi her order sectorisation (vertical. hori!ontal or a combination) to selected base stations by chan in an antenna system to include more antenna beams. each coverin a smaller area than before the chan e L however. the main covera e of the combined beams correspond to the main cell covera e before the split. 2ach of the beams broadcasts different P1'. 1ell splittin > mer in procedures is considered on a lon term time scale (every -h or more seldom L few times a day).
; ;
3GPP
Release ()
The tri er for the chan e may be O/M reconfi uration (e. . based on collected &P's) or. if the cell covera e is not affected and the split is pre;planned. the control unit is the base station (implementation based). 'ndication of the cell splittin may be needed at O/M and nei hbour e(0s. Problems related to e)istin $O( features or enhancements needed@ 77$
/ centrali!ed (in O/M) controlled solution is already possible today. since O/M is able to send any confi uration to the involved e(0s. 't is also capable of monitorin an e)tensive ran e of measurements. Therefore. the solutions for cell splittin operate on a discreet set of confi urations provided from O/M. $cenario descriptions involvin cell splittin should provide answers to the followin Cuestions@ -. $hould cell splittin occur in !ones freely defined by the e(0. or only accordin to O/M preconfi ured eo raphical informationM /nswer@ The cell splittin should occur accordin to O/M preconfi ured eo raphical information. The process of cell splittin should be carried out in a controlled and preconfi ured way. i.e. by selectin splittin confi urations that have been validated in terms of covera e at O/M level. /ccordin to networ# load and users service type and reCuirements in the considered eo raphic areas. O/M can define whether a cell splittin is necessary or not. +. $hould the "/( provide particular information to O/M in order to help confi uration of eo raphical or other information related to cell splittin M /nswer@ 'nformation such as M:T measurement data or statistics can be provided to O/M to help further optimisation of confi uration related to cell splittin . "/( can provide statistics and>or M:T data to O/M. for e)ample. O/M can consider statistics and>or confi ure M:T measurements before or after cell splittin in the concerned !ones. and the statistics and>or M:T measurements data collected from e(0s and 32s may help operators et #nowled e of the real covera e and capacity conditions under the two different antenna confi urations within the concerned eo raphical area. Operators can ma#e further optimisation on the settin of //$ antenna and eo raphical !ones. 3. $hould the cell splittin . once defined by O/M. be permanently activatedM /nswer@ The cell splittin can be activated and mer ed bac#. 'n a situation where the hot spots of traffic demand are consistently localised in space and are present for most of the time. or appear>disappear with a relatively short time period. it would be plausible to permanently adopt the cell splittin confi uration. On the other end. if the traffic hotspots are not consistently localised in space and appear in time with rather lon periods. it may be plausible to allow the mer e bac#. from the splittin confi uration to a mer ed one. 8. $hould the O/M system be able to activate>de;activate the cell splittin (cell mer in )M /nswer@ The O/M system should be able to activate>de;activate the cell splittin >mer in . which allows operators to control the cell splittin >mer in functionality at their needs. 9. $hould the e(0 be able to autonomously activate (the possibly O/M preconfi ured) cell splittin M 'f so which #ind of information is neededM <. $hould the e(0 be able to autonomously de;activate cell splittin (cell mer in )M 'f so which #ind of information is neededM /nswer9><@ The e(0 should be able to activate>de;activate the cell splittin usin splittin confi urations preconfi ured by O/M. 3nder the supervision and validation of O/M (e. . validation that the confi uration is compatible with the nei hborin e(0 status). the e(0 may be able to tri er activation>de;activation of the cell splittin when certain conditions are met. =. $hould intra;freCuency scenarios be consideredM N. $hould inter;freCuency scenarios be consideredM
3GPP
Release ()
/nswer=>N@ 0oth. intra;freCuency and inter;freCuency scenarios should be considered. which may satisfy different operators demands.
3GPP
Release ()
(.
One solution is to use proprietary methods (e. . O/M) to forward the information in the "57 report to the e(0 handlin the last servin cell. /nother solution is to forward the information in the "57 report over $- to the e(0 handlin the last servin cell. 7or this solution. there are two options. The first option is to only support sendin this to an e(0 belon in to the same MM2 pool. The second option is to support sendin this to an e(0 belon in to any MM2 pool. The latter reCuires that the T/' of the last servin 5T2 cell is #nown. 't is 77$ whether it is feasible (pendin a discussion with "/(+) to include the T/' in the "57 report from the 32.
*o& !usio&s
3GPP
Release ()
((
2013-02013-02013-02013-05 2013-05
R3-1307-2 R3-1307-3 R3-1307-6 R3-131162 R3-131092 R3-13109R3-131095 R3-131096 R3-1315-8 R3-131552 R3-131553 R3-131563
2013-05 R3<80 2013-05 R3<80 2013-05 R3<80 2013-08 R3<81 2013-08 R3<81 2013-08 R3<81 2013-08 R3<81
";e!eto& TR a1reed 7'=e ti5e 3or "7) 3or 8E t9#es added 7'=e ti5e 3or "7) 3or %%"-'ased de#!o96e&ts added T0o #ro'!e6 ases added i& >"7) 3or 8E t9#es? added @uestio&s o& er&i&1 e!! s#!itti&1 added i& t$e >"7) 3or %%"-'ased de#!o96e&ts? se tio& *a#a it9 o#ti6isatio& s e&ario added to t$e >"7) 3or %%"'ased de#!o96e&ts? se tio& % s e&ario re!ated to usi&1 o3 t$e resu!t o3 t$e RR* reesta'!is$6e&t i& t$e :R7 added to t$e >"7) 3or #re-Re!.12 s6a!! e!!s? se tio& % s e&ario re!ated to RL( re#orti&1 i& is!a&ds de#!o96e&ts added to t$e >"7) 3or #re-Re!.12 s6a!! e!!s? se tio& %dded so!utio&s 3or t$e #i&1-#o&1 #ro'!e6 %dded a&s0ers to t$e Auestio&s o& e!! s#!itti&1 T$e des ri#tio& o3 t$e %%" te $&iAues !ari3ied a&d 6o5ed to t$e i&trodu tio& to t$e !ause -.2, 'e3ore t$e Auestio&s o& t$e e!! s#!itti&1. % #ro'!e6 s e&ario o& er&i&1 o&ti&uit9 o3 a o&&e tio& i& ase o3 e!! s#!itti&1 added to !ause -.2 3hange history
0.1.0 0.1.0 0.1.0 0.1.0 0.1.0 0.1.0 0.1.0 0.2.0 0.2.0 0.2.0 0.2.0
0.1.0 0.2.0 0.2.0 0.2.0 0.2.0 0.2.0 0.2.0 0.2.0 0.3.0 0.3.0 0.3.0 0.3.0
4ate
3R
Re9 Su7ject83o""ent
!ld
New
2013-09 61 2013-09
RP-1311-7 B
3GPP