Vous êtes sur la page 1sur 3

Error! No text of specified style in document.

Error! No text of specified style in document.

R3-093082

3GPP TSG-RAN3 Meeting #66


Jeju, Korea, 09th 13th November, 2009

CR-Form-v9.6

CHANGE REQUEST
Current version:
36.902 CR 0001
rev 9.0.0
For HELP on using this form look at the pop-up text over the symbols. Comprehensive instructions on how
to use this form can be found at http://www.3gpp.org/specs/CR.htm.
Proposed change affects:

UICC apps

ME

Radio Access Network X

Title:

Finalization of Solution Description sub clause for MLB

Source to WG:
Source to TSG:

Ericsson
R3

Work item code:

SON

Category:

Date:

Release:

Core Network

27/10/09
REL-9

Use one of the following categories:


Use one of the following releases:
F (correction)
R99
(Release 1999)
A (corresponds to a correction in an earlier release)
Rel-4
(Release 4)
B (addition of feature),
Rel-5
(Release 5)
C (functional modification of feature)
Rel-6
(Release 6)
D (editorial modification)
Rel-7
(Release 7)
Detailed explanations of the above categories can
Rel-8
(Release 8)
be found in 3GPP TR 21.900.
Rel-9
(Release 9)
Rel-10 (Release 10)

Reason for change:

In order to consistently describe mobility load balancing according to the


outcome of the SON enhancements discussion, the solution description in the TR
needs to be updated.

Summary of change:

The support for Composite Available Capacity is introduced in the solution


description sub clause together with the Cell Capacity Class concept.

Consequences if
not approved:

Inconsistent TR

Clauses affected:

4.6.5

Other specs
affected:

Y N
X Other core specifications
X Test specifications
X O&M Specifications

Other comments:

3GPP

Error! No text of specified style in document.

Error! No text of specified style in document.

---------------------------------Skip unchanged text


---------------------------------4.6.5 Solution description for Intra LTE load balancing
4.6.5.1

Input data, definition of Measurements or Performance data

It is proposed that load information is used for load balancing. Besides its own load, an eNB must know the load in the
neighbouring cells to be able to decide on the appropriate candidate cell for LB action. The neighbour load can be
provided with:
Intra-LTE load balancing (information exchanged over X2):

the current radio resource usage (UL / DL GBR PRB usage, UL/DL non-GBR PRB usage, UL/DL total PRB
usage), (further refinements of non-GBR load is FFS)

the current HW load indicator (UL/DL HW load: low, mid, high, overload),

the current TNL load indicator (UL/DL TNL load: low, mid, high, overload).

a composite available capacity indicator (UL / DL) PRBs) FFS.

a cell capacity class indicator (UL / DL).

Editors notes:
- It is assumed the node indicating available capacity is ready to accept the corresponding traffic, but it is not
mandatory.
- It is also assumed that the algorithm to calculate the available capacity indicator is vendor-specific and runs in
the eNB that provides the indicator.
- Following problems are FFS:
- Is the available capacity indicator reported as an absolute value or normalised in 0-100 scale (as in Rel.8)?
- Should the available capacity indicator replace Rel.8 information (PRBs allocated) or be reported together?
- Should the available capacity indicator address both GBR and non-GBR, each separately or only one of the
two?
- Should the available capacity indicator address only radio resources, or cover also TNL and hardware
resources?

4.6.5.2

Output, influenced entities and parameter

Intra-LTE load balancing:

Handover parameters : cell-specific offset

Cell reselection parameters: Qoffsets,n, Reselection priorities

The parameters related to cell reselection are defined in [4] and those related to handover in [5]

3GPP

Error! No text of specified style in document.

4.6.5.3

Error! No text of specified style in document.

Impacted specifications and interfaces

The signalling of composite available capacity impacts the X2AP protocol and the necessary support is introduced in
the Resource Status Reporting procedures.

3GPP

Vous aimerez peut-être aussi