Mass event handling
2
Mass Event Handling Functional description Mass event handling is based on load detection in RNC. The operation is performed by monitoring the amount of initial capacity requests in non-real time scheduling queue. For each cell the pre-determined threshold determines when the load is considered to be “high” and when it is considered to be “normal”. Only detection of the high load will trigger the following special actions for traffic handling: o Longer TVM pending time up to 8 seconds if the initial capacity request is rejected. o Temporary maximum bit rate set to minimum, typical 16 kbps, bit rate for UL DCH. o Temporarily limited maximum number of HSUPA users. Also the following special actions can be triggered for traffic handling: o E-DCH 2 ms TTI prohibition, which is triggered by the defined number of HSUPA users in the cell o CQI feedback cycle increase from 4 to 8 ms, which is triggered by the defined number of HSDPA users in the cell. o Enhanced DL power AC and HSDPA prevention, which is triggered by the defined downlink power congestion for AMR. Mass event handling is based on load detection in the RNC: o RNC defines load status based on the amount of initial capacity requests in non-real time scheduling queue: o RNC samples length of the non-real time scheduling queue of each scheduling period. o length of the non-real time scheduling queue reflects congestion in air- interface, transport or BTS: if capacity request cannot be served due to congestion, occupancy of non-real time scheduling queue starts to increase. o PRFILE parameter 002:1882 RN60_MAINT_06 is used to define the threshold for "Load_status": o If NBR of initial capacity requests higher or equal threshold set by the PRFILE, then “Load_Status” is considered to be “High” o If NBR of initial capacity requests lower threshold set by the PRFILE, then “Load_Status” is considered to be “Normal” o PRFILE parameter 002:1883 RN60_MAINT_07 is used to define the “Time-to- trigger” for changing the "Load_status": o If "Load_status" changes from “Normal” to “High”, PRFILE value is used as such
-
Upload
ashwani-agarwal -
Category
Documents
-
view
43 -
download
1
description
mass event handling
Transcript of Mass event handling
Mass Event Handling
Functional description
Mass event handling is based on load detection in RNC. The operation is performed by monitoring the amount of initial capacity requests in non-real time scheduling queue. For each cell the pre-determined threshold determines when the load is considered to be “high” and when it is considered to be “normal”. Only detection of the high load will trigger the following special actions for traffic handling:
o Longer TVM pending time up to 8 seconds if the initial capacity request is rejected.
o Temporary maximum bit rate set to minimum, typical 16 kbps, bit rate for UL DCH.
o Temporarily limited maximum number of HSUPA users.
Also the following special actions can be triggered for traffic handling:
o E-DCH 2 ms TTI prohibition, which is triggered by the defined number of HSUPA users in the cell
o CQI feedback cycle increase from 4 to 8 ms, which is triggered by the defined number of HSDPA users in the cell.
o Enhanced DL power AC and HSDPA prevention, which is triggered by the defined downlink power congestion for AMR.
Mass event handling is based on load detection in the RNC:
o RNC defines load status based on the amount of initial capacity requests in non-real time scheduling queue:
o RNC samples length of the non-real time scheduling queue of each scheduling period.
o length of the non-real time scheduling queue reflects congestion in air-interface, transport or BTS: if capacity request cannot be served due to congestion, occupancy of non-real time scheduling queue starts to increase.
o PRFILE parameter 002:1882 RN60_MAINT_06 is used to define the threshold for "Load_status":
o If NBR of initial capacity requests higher or equal threshold set by the PRFILE, then “Load_Status” is considered to be “High”
o If NBR of initial capacity requests lower threshold set by the PRFILE, then “Load_Status” is considered to be “Normal”
o PRFILE parameter 002:1883 RN60_MAINT_07 is used to define the “Time-to-trigger” for changing the "Load_status":
o If "Load_status" changes from “Normal” to “High”, PRFILE value is used as such
o If "Load_status" changes from “High” to “Normal”, PRFILE value multiplayed by 2, is used.
Mass event handling utilises load state detection with the following functions:
o Longer TVM pending time (8 secs) if initial capacity request is rejected
o Temporary maximum bit rate set to minimum bit rate for UL DCH
o Temporarily limited maximum number of HSUPA users.
Mass event handling utilises enhanced downlink power AC where AMR CS DCH speech call can be admitted if the following condidion is fulfilled, if there are simultaneous HSDPA users in the cell:
At the same time if AMR user is admitted based on the enhan
