07 RN31637EN50GLA0 RANPAR 1 HandoverControl and Mobility v1.0 RU50 NOKIA

Preview:

DESCRIPTION

07 RN31637EN50GLA0 RANPAR 1 HandoverControl and Mobility v1.0 RU50 NOKIA

Citation preview

RN31637EN50GLA0

Handover Control and Mobility

1

RN31637EN50GLA0

Handover Control and Mobility

2

RN31637EN50GLA0

Handover Control and Mobility

4

RN31637EN50GLA0

Handover Control and Mobility

5

RN31637EN50GLA0

Handover Control and Mobility

6

RN31637EN50GLA0

Handover Control and Mobility

7

RN31637EN50GLA0

Handover Control and Mobility

8

RN31637EN50GLA0

Handover Control and Mobility

9

ADJE and FMCL are new in RU50

RN31637EN50GLA0

Handover Control and Mobility

10

RN31637EN50GLA0

Handover Control and Mobility

11

Detected Set Reporting & Measurements:

optional features related to ADJD allow UE to report & handover to cells not included in the neighbor list

If feature RAN1191: “Detected Set Reporting (DSR) & Measurements” is enabled, specific counters (M1028 Autodef SHO DSR measurement) can be used to find detected set cells that are reported by the UE but that are not in the ADJS or ADJD adjacency lists and cannot therefore be targets of SHO. With that information the neighbor lists can be optimized to include such cells that would be good handover targets.

RN31637EN50GLA0

Handover Control and Mobility

12

RN31637EN50GLA0

Handover Control and Mobility

13

RN31637EN50GLA0

Handover Control and Mobility

14

RN31637EN50GLA0

Handover Control and Mobility

15

RN31637EN50GLA0

Handover Control and Mobility

16

RN31637EN50GLA0

Handover Control and Mobility

17

RN31637EN50GLA0

Handover Control and Mobility

18

RN31637EN50GLA0

Handover Control and Mobility

19

Point 1)

• Reporting range defined by offset from either

(i) best CPICH Ec/Io in the AS, or

(ii) sum of the AS measurement results

set using ActiveSetWeightingCoefficient (FMCS) (0 = use best CPICH : <>0 = use sum)

• Offset defined using AdditionWindow (FMCS)

Point 2)

Event 1A triggered when CPCIH3 Ec/Io enters UE reporting range (point 2)

Point 3)

If CPICH3 Ec/Io remains within reporting range for a time period defined by AdditionTime

(FMCS) , and the AS is not full, UE sends measurement report to RNC which adds Ncell3 to

AS if possible (point 3)

• AdditionTime defines the 'time-to-trigger' interval between the Ncell first entering the

reporting range and the UE sending the measurement report to the RNC

Point 4) If RNC is unable to add Ncell to AS, UE will wait for a period of time, defined by

AdditionReportingInterval (FMCS) (point 4) after the first measurement report, before

sending further reports periodically, with interval AdditionReportingInterval, until (a) Ncell

moves out of reporting range, or (b) RNC adds Ncell to AS.

RN31637EN50GLA0

Handover Control and Mobility

20

Point 1)

Event 1B triggered when CPICH3 EC/I0 drops out of the UE reporting range for a defined

period of time (point 1 on next slide)

Point 2)

Reporting range = Strongest CPICH in AS - DropWindow (FMCS)

Point 3)

• Time-to-trigger period set using DropTime (FMCS)

• UE sends RNC measurement report on expiry of DropTime to remove Ncell (CPICH3)

from AS.

• RNC drops the cell from the AS and UE drops the cell from the AS

RN31637EN50GLA0

Handover Control and Mobility

21

Point 1)

•UE AS full (MaxActiveSetSize = 3)

•Event 1C triggered when CPICH4 EC/IO > CPICH3 in AS by a defined margin,

ReplacementWindow (FMCS).

Point 2)

Sending of measurement report to RNC can be delayed by using 'time-to-trigger' period set by

ReplacementTime (FMCS)

Point 3)

•If 'time-to-trigger' is used difference between CPICH4 and CPICH3 must be

ReplacementWindow for the period of ReplacementTime

•If the RNC is not able to replace the Ncells, the UE continues to send measurement reports

periodically, with interval ReplacementReportingInterval, to the RNC until (a) CPICH4 falls

out of ReplacementWindow or (b) RNC replaces CPICH4 by CPICH3

RN31637EN50GLA0

Handover Control and Mobility

22

RN31637EN50GLA0

Handover Control and Mobility

23

Not hear that this option is widely used.

RN31637EN50GLA0

Handover Control and Mobility

24

RN31637EN50GLA0

Handover Control and Mobility

25

RN31637EN50GLA0

Handover Control and Mobility

26

Measurement reporting criteria are cell specific

Neighboring cells (ADJS & HOPS parameters) are defined on a controlling cell (cell from which the call has been started or best cell in case the original cell has been deleted from the AS)

During SHO the measurement reporting criteria are taken from the cell where the UE has started the connection

The measurement reporting criteria are updated only when the original cell leaves the Active Set (NSN Implementation), according to the strongest cell in the Active Set, by sending the MEASUREMENT CONTROL message, transmitted on the DL DCCH. Standard would allow to update reporting criteria, according the current best server.

When the UE receives a MEASUREMENT CONTROL message, the UE shall stop monitoring & measurement reporting and shall replace the measurement reporting criteria with the new information received in the MEASUREMENT CONTROL message.

RN31637EN50GLA0

Handover Control and Mobility

27

RN31637EN50GLA0

Handover Control and Mobility

28

RN31637EN50GLA0

Handover Control and Mobility

29

RN31637EN50GLA0

Handover Control and Mobility

30

RN31637EN50GLA0

Handover Control and Mobility

31

RN31637EN50GLA0

Handover Control and Mobility

32

RN31637EN50GLA0

Handover Control and Mobility

33

RN31637EN50GLA0

Handover Control and Mobility

34

RN31637EN50GLA0

Handover Control and Mobility

35

RN31637EN50GLA0

Handover Control and Mobility

36

RN31637EN50GLA0

Handover Control and Mobility

37

RN31637EN50GLA0

Handover Control and Mobility

38

RN31637EN50GLA0

Handover Control and Mobility

39

RN31637EN50GLA0

Handover Control and Mobility

40

RN31637EN50GLA0

Handover Control and Mobility

41

RN31637EN50GLA0

Handover Control and Mobility

42

RN31637EN50GLA0

Handover Control and Mobility

43

RN31637EN50GLA0

Handover Control and Mobility

44

RN31637EN50GLA0

Handover Control and Mobility

45

RN31637EN50GLA0

Handover Control and Mobility

46

RN31637EN50GLA0

Handover Control and Mobility

47

RN31637EN50GLA0

Handover Control and Mobility

48

RNC starts IF/IS measurements based on UL outer-loop power control reports

Enable reports from Outer-loop Power Control Controller to trigger IF/IS HO, RNC: EnableULQualDetRep/default 0=no, 1=yes

Time duration for which BER/BLER target has not been reached, despite SIR target at maximum level, RNC: ULQualDetRepThreshold; 0.5..5, step 0.5s; default: 0.5 s

Periodic report, every RNC: ULQualDetRepThreshold seconds, while BLER/BLER target is not reached

In addition, the UL data rate allocated to the user must not exceed WCEL: HHoMaxAllowedBitrateUL (default value: 32 kbits/s)

RN31637EN50GLA0

Handover Control and Mobility

49

RN31637EN50GLA0

Handover Control and Mobility

50

RN31637EN50GLA0

Handover Control and Mobility

51

RN31637EN50GLA0

Handover Control and Mobility

52

RN31637EN50GLA0

Handover Control and Mobility

53

RN31637EN50GLA0

Handover Control and Mobility

54

RN31637EN50GLA0

Handover Control and Mobility

55

RN31637EN50GLA0

Handover Control and Mobility

56

RN31637EN50GLA0

Handover Control and Mobility

57

RN31637EN50GLA0

Handover Control and Mobility

58

RN31637EN50GLA0

Handover Control and Mobility

59

RN31637EN50GLA0

Handover Control and Mobility

60

RN31637EN50GLA0

Handover Control and Mobility

61

RN31637EN50GLA0

Handover Control and Mobility

62

RN31637EN50GLA0

Handover Control and Mobility

63

RN31637EN50GLA0

Handover Control and Mobility

64

RNC uses RRC: Physical channel reconfiguration to execute HO

RN31637EN50GLA0

Handover Control and Mobility

65

RN31637EN50GLA0

Handover Control and Mobility

66

RN31637EN50GLA0

Handover Control and Mobility

67

RN31637EN50GLA0

Handover Control and Mobility

68

RN31637EN50GLA0

Handover Control and Mobility

69

RN31637EN50GLA0

Handover Control and Mobility

70

RN31637EN50GLA0

Handover Control and Mobility

71

To enable “Forced Handover for AMR Voice Call settings must be:

GSMcauseTxPwrUL = true

GsmUETxPwrThrAMR = -60 dB

RN31637EN50GLA0

Handover Control and Mobility

72

RN31637EN50GLA0

Handover Control and Mobility

73

RN31637EN50GLA0

Handover Control and Mobility

74

RN31637EN50GLA0

Handover Control and Mobility

75

RN31637EN50GLA0

Handover Control and Mobility

76

RN31637EN50GLA0

Handover Control and Mobility

77

RN31637EN50GLA0

Handover Control and Mobility

78

RN31637EN50GLA0

Handover Control and Mobility

79

RN31637EN50GLA0

Handover Control and Mobility

80

RN31637EN50GLA0

Handover Control and Mobility

81

RN31637EN50GLA0

Handover Control and Mobility

82

RN31637EN50GLA0

Handover Control and Mobility

83

RN31637EN50GLA0

Handover Control and Mobility

84

RN31637EN50GLA0

Handover Control and Mobility

85

RN31637EN50GLA0

Handover Control and Mobility

86

RN31637EN50GLA0

Handover Control and Mobility

87

RN31637EN50GLA0

Handover Control and Mobility

88

RN31637EN50GLA0

Handover Control and Mobility

89

RN31637EN50GLA0

Handover Control and Mobility

90

RN31637EN50GLA0

Handover Control and Mobility

91

Processing of measurement results indicated load:

1) Measurement Phase: Sliding windows (see AveragingWindows for

ON) to average load measurements.

2) Load based HO state “ON”: LHO state “ON” indication shall be

broadcasted if Load rises above the threshold.

3) Hysteresis Time: Load based HO are started if load rises above a

given threshold and stays there for the Hysteresis time.

4) Load based HO phase: Activation of new Load based HOs is

stopped if load measurements averaged via Sliding windows (see

Averaging Windows for OFF) fall below threshold; Note: Averaging

windows for starting Load based Handover state are longer than for

stopping

5) Load based HO state “OFF”: LHO state “OFF” indication shall be

broadcasted after Timer (see Delay OFF) exceeded and averaged

load measurements have been continuously below threshold.

RN31637EN50GLA0

Handover Control and Mobility

92

RN31637EN50GLA0

Handover Control and Mobility

93

RN31637EN50GLA0

Handover Control and Mobility

94

RN31637EN50GLA0

Handover Control and Mobility

95

RN31637EN50GLA0

Handover Control and Mobility

96

RN31637EN50GLA0

Handover Control and Mobility

97

RN31637EN50GLA0

Handover Control and Mobility

98

RN31637EN50GLA0

Handover Control and Mobility

99

RN31637EN50GLA0

Handover Control and Mobility

100

RN31637EN50GLA0

Handover Control and Mobility

101

RN31637EN50GLA0

Handover Control and Mobility

102

RN31637EN50GLA0

Handover Control and Mobility

103

RN31637EN50GLA0

Handover Control and Mobility

104

RN31637EN50GLA0

Handover Control and Mobility

105

RN31637EN50GLA0

Handover Control and Mobility

106

RN31637EN50GLA0

Handover Control and Mobility

107

RN31637EN50GLA0

Handover Control and Mobility

108

RN31637EN50GLA0

Handover Control and Mobility

109

RN31637EN50GLA0

Handover Control and Mobility

110

Multi-Band Load Balancing MBLB

allows Target cell selection depending on: UE capability & service, freq. band, target/source

cell load, UE distance from source/target cells.

It extends existing scenarios, e.g.:

HSPA capable UE with CS RAB in HSDPA cell can be moved to DCH cell

Target & source cell loads can be checked prior HSDPA inactivity triggered HO

Load based HO can be triggered by HSPA traffic overload

Load sharing/balancing between HSPA cells/bands is provided

RN31637EN50GLA0

Handover Control and Mobility

111

RN31637EN50GLA0

Handover Control and Mobility

112

RN31637EN50GLA0

Handover Control and Mobility

113

RN31637EN50GLA0

Handover Control and Mobility

114

RN31637EN50GLA0

Handover Control and Mobility

115

MBLB selects the most suitable layer for UE using preference score

Preferred Layer: based upon UE capability and service type. Preferred layers for different UE capability and service combinations can be specified, e.g. HSDPA capable UE with NRT service

Preferred Band: increased weight can be allocated to specific operating bands and the operating band capability of the UE is taken into account

Reported RSCP: Lower operating bands are preferred for low reported RSCP, whereas upper operating bands are preferred for high reported RSCP (lower operating bands provide coverage, while upper operating bands provide capacity)

Load: load balancing and HSPA load state are taken into account

RN31637EN50GLA0

Handover Control and Mobility

116

RN31637EN50GLA0

Handover Control and Mobility

117

RN31637EN50GLA0

Handover Control and Mobility

118

RN31637EN50GLA0

Handover Control and Mobility

119

The table illustrates how RNC decide, which cells have higher HSDPA load and when cells are considered overloaded.

The MBLB 'HSDPA load level' metrics are:

- 'HSDPA power per user' (that is similar to "HSDPA Layering/RAN1011" metric used to balancing the load)

- indication of still available/left HSDPA power. This is important to properly interpret load of two cells having same used HSDPA power per user

(cell having power available is less loaded then the one w/out HSDPA power left)

The table with 'HSDPA load levels' on the slide explaining Load Weight is included to let the trainee to get idea about power thresholds for each HSPDA load level,

and to indicate how RNC interprets HSPA overload due to HSDPA load level (there are also other metrics for HSPA overload / BB resources, UL used power and UE throughput etc) and what it does if cell is not enabled for HSDPA.

RN31637EN50GLA0

Handover Control and Mobility

120

RN31637EN50GLA0

Handover Control and Mobility

121

RN31637EN50GLA0

Handover Control and Mobility

122

Recommended