Pre-Match Day: 1.

Ensure Stadium cells, mobiles and sites covering entrance, road towards stadium are set to Config 4 (Event Config) in ASSET. This will ensure that all parameters are set to the correct High Capacity values. 2. Handle all discrepancies on the related cells mentioned in point 1. 3. Contact Active DAS Company to ensure that theres no alarms on the Active DAS system. 4. Investigate the alarm printout in AMOS on the sites mentioned in point 1 and ensure that no alarms are present. Escalate any problems to CNOC asap. 5. Ensure all RAX/TXB/DUW HW boards are unlocked and enabled. 6. Ensure that EUL is locked and disabled on all cells inside and around the stadium entrance. 7. Perform walk test with Active DAS Company and ensure that all RRUs are transmitting and that the coverage/quality levels are as planned. 8. Ensure that Fast Dormancy Handling feature as well as RRC Load control features loaded active and set to the correct values. Check Datasafe for any discrepancies. 9. Request RNC Planning engineers in HQ to inform if any additional precaution needs to be taken as a result of high RNC load. Match Day: Pre-Event, During Event and Post-Event: 1. Its very important to start monitoring the cells covering the stadium, entrance of the stadium and roads towards the stadium at least 2 hours before the event starts.

2. Use Google Traffic Maps http://maps.google.co.za/maps?hl=en&tab=ll to monitor the traffic

towards the stadium. This should give you an indication of the traffic movement in the area. 3. Ensure CNOC, BSS, HLS,TX Ops engineers are informed that the activity is starting by starting the Planned Work activity. 4. Investigate the alarm printout in AMOS on the sites mentioned in point 1 and ensure that no alarms are present. Escalate any problems to CNOC asap. 5. Ensure all RAX/TXB/DUW HW boards are unlocked and enabled. 6. Ensure that EUL is locked and disabled on all cells inside and around the stadium entrance. 7. Start monitoring the cells, RNC load and transmission using the following reports and/or AMOS commands on a 5min interval. a. Commands: AMOS Commands cedr Printout description Codes, Power, ul_RSSI, User_Adm usage instantaneously

cedhr pget mp load

Channel Elements usage instantaneously RNC PluginUnit load. When this value reaches 80%, please contact the RNC Planning Engineer on standby or lock the sites in the list provided.

pmx cell pmTotNoRrcUtranRejection

15 Min view of cells having RRC Utran Rejections

b. Reports: Reports Report Description Real Time Monitoring report equivalent to the cedr and cedhr commands 5 Min RNC Load report, similar to the pget mp load report

8. Follow the steps in the table below when any of the following scenarios occurs. Scenario Power > 80% utilization Action Activate Directed Retry if GSM is not congested, by changing the xx to 100 Codes > 80% utilization Activate Directed Retry if GSM is not congested, by changing the xx to 100 UL CE > 80% utilization Set UlHwAdm (iublink on rnc) to 100 DL CE > 80% utilization Set DlHwAdm (iublink on rnc) to 100 UL RSSI < - 85 dBm Disable SFxxAdmul Reason This will move traffic to GSM as the current 3G cells are not able to hold the 3G traffic This will move traffic to GSM as the current 3G cells are not able to hold the 3G traffic RNC load will increase as soon as the site goes into soft congestion. RNC load will increase as soon as the site goes into soft congestion. This will lower the UL Throughput of the users on R99 ensuring that voice and PS accessibility is protected RNC Load > 80% Please contact the RNC Planning Locking cells on the RNC will ensure

Engineer on standby or lock the sites in the list provided. pmNoRejRrcConnMpLoadC > 0 and not returning back to 0 after 15 min. Please contact the RNC Planning

that services at the stadium are maintained. It will detect the RRC admission load peak build up in a Module MP and limit the peak load to a sustainable level by early rejection of RRC Requests.

9. Its very important to keep on monitoring the cells covering the stadium, entrance of the stadium and roads towards the stadium at least 2 hours after the event ended.

10. Use Google Traffic Maps http://maps.google.co.za/maps?hl=en&tab=ll to monitor the traffic

leaving the stadium. This should give you an indication of the traffic movement in the area. 11. Ensure CNOC, BSS, HLS, TX Ops engineers are informed that the activity ended by closing the Planned Work activity. 12. Prepare Event Report using the Automated Event reporting Excel Macro available at: 13. Please add any findings, changes and anomalies found during the event.

Config 4 (Event Config) Parameter Set:

MO Class Name Fach Fach Hsdsch Hsdsch Eul IubLink IubLink PowerControl PowerControl PowerControl PowerControl PowerControl PowerControl PowerControl PowerControl

Parameter Name

MTN Event Config Value 18 15 1 4 0 (LOCKED) 98 97 100 80 100 100 70 70 40 40

Change Take Effect New connection New connection Object locked Cell Unlocked Immediate New connection New connection New connection or new radio link New connection New connection or new radio link New connection New connection or new radio link New connection or new radio link New connection or new radio link New connection or new radio link

Network Entity Utran Cell Utran Cell Utran Cell Utran Cell Utran Cell Iub Link Iub Link RNC RNC RNC RNC RNC RNC RNC RNC Downlink Power Allocation [basic] Downlink Power Allocation [basic] HSDPA Introduction [optional] HSDPA Dynamic Code Allocation [optional] Enhanced Uplink Introduction Package [optional] Admission Control [basic] Admission Control [basic] Power Control [basic] Enhanced Uplink, 2 ms TTI [optional] Enhanced Uplink Introduction Package [optional] Enhanced Uplink, 2 ms TTI [optional] Power Control [basic] Power Control [basic] Power Control [basic] Power Control [basic]

Feature Name

maxFach1Power maxFach2Power numHsPdschCodes numHsScchCodes administrativeState dlHwAdm ulHwAdm sirMax sirMaxTti2 transmissionTargetError transmissionTargetErrorTti2 ulInitSirTargetExtraHigh ulInitSirTargetHigh ulInitSirTargetLow ulInitSirTargetSrb

RbsLocalCell RbsLocalCell Rrc Rrc Rrc Rrc Rrc Rrc Rrc UtranCell UtranCell UtranCell UtranCell UtranCell UtranCell UtranCell UtranCell UtranCell UtranCell UtranCell UtranCell UtranCell UtranCell UtranCell UtranCell UtranCell UtranCell UtranCell UtranCell UtranCell

eulMaxOwnUuLoad eulMaxRotCoverage rrcLcFilterDecr rrcLcFilterDecrThresh rrcLcFilterIncr rrcLcFilterIncrThresh rrcLcFilterMax rrcLcMonitorPeriod rrcLcRrcReqMin compModeAdm dlCodeAdm eulServingCellUsersAdmTti2 interPwrMax loadSharingGsmFraction loadSharingGsmThreshold minPwrMax pwrAdm pwrOffset rrcLcEnabled sf128Adm sf16Adm sf16AdmUl sf16gAdm sf32Adm sf4AdmUl sf64AdmUl sf8Adm sf8AdmUl sf8gAdmUl treSelection

80 100 10 5 10 15 80 5 8 10 95 4 28 100 75 -30 90 5 1 (ENABLED) 128 16 50 16 24 0 100 0 0 0 4

Ongoing connection Ongoing connection Immediate Immediate Immediate Immediate Immediate Immediate Immediate New connection New connection Immediately New connection New connection New connection New connection New connection Immediately Immediate

Utran Cell Utran Cell RNC RNC RNC RNC RNC RNC RNC Utran Cell Utran Cell Utran Cell Utran Cell Utran Cell Utran Cell Utran Cell Utran Cell Utran Cell UtranCell

Enhanced Uplink Introduction Package [optional] Enhanced Uplink Introduction Package [optional] RNC RRC Load Control RNC RRC Load Control RNC RRC Load Control RNC RRC Load Control RNC RRC Load Control RNC RRC Load Control RNC RRC Load Control Admission Control [basic] Admission Control [basic] Enhanced Uplink, 2 ms TTI [optional] Downlink Power Drift Prevention [basic] Directed Retry to GSM [optional] Directed Retry to GSM [optional] Downlink Power Drift Prevention [basic] Admission Control [basic] Congestion Control [basic] RNC RRC Load Control

New connection New connection New connection New connection New connection New connection New connection New connection

Utran Cell Utran Cell Utran Cell Utran Cell Utran Cell Utran Cell Utran Cell Utran Cell Utran Cell

Admission Control [basic] Admission Control [basic] Admission Control [basic] Admission Control [basic] Admission Control [basic] Admission Control [basic] Admission Control [basic] Admission Control [basic] Soft/Softer Handover and Cell Re-selection [basic]

RRCLoadCOntrol Feature Activate the feature with the featureState parameter for RncFeature instance RrcLoadControl in RNC. > set Licensing=1,RncFeature=RrcLoadControl featureState 1 Turn on the feature per cell through attribute rrcLcEnabled in > set utrancell rrcLCEnabled 1 MO:Utrancell

It will detect the RRC admission load peak build up in a Module MP and limit the peak load to a sustainable level by early rejection of RRC Requests.

If the number of RRC Connection Requests received from UEs on cell X are less than rrcLcRrcReqMin, the filter value for the next time period is decreased with rrcLcFilterDecr, regardless of the RRR value.

If RRR > rrcLcFilterIncrThresh, the filter value for the next time period is increased with rrcLcFilterIncr. This is valid until the filter value reaches the maximum value of rrcLcFilterMax.

If RRR < rrcLcFilterDecrThresh, the filter value for the next time period is decreased with rrcLcFilterDecr. This is valid until the filter value reaches zero.

If rrLcFilterDecrThresh RRR rrcLcFilterIncrThresh , the filter value for the next time period is kept on the same level.

The Filter does not reject any RRC Connection Request with Establishment Cause equal to:

Originating Conversational Call, Terminating Conversational Call and Emergency Call.

Parameters recommended are:

Counters to monitor are: pmNoRejRrcConnRrcLc : Number of RRC Connection attempts rejected "early" in the RNC due to the feature RRLC Early Filter.

pmTotalTimeRejRrcConnRrcLc: Accumulated time per ROP period during which RNC RRC Load Control RRC Connection filter rejects is triggered.

pmNoRejRrcConnSpFlowCtrl : Number of SP RRC Connection Rejects (number of discards in the flow control between the CC SP and the Module MP) on the CC SP for this cell. pmNoRejRrcConnMpLoadC: Number of rejected RRC connections due to MP load control. Condition: Incremented by one when sending a RRC message RRC Connection Reject with rejection cause congestion, when the congestion cause has been indicated by internal load control. RNC RRC Load Control ensures that the RNC RRC request load is kept at a sustainable level, even at occasions with high number of RRC Connection Requests that can occur for example at Congested Cells at an Arena Event or to few channel elements in the cell.

The RNC RRC Load Control feature detects massive RRC Connections Requests and rejects requests, excluding voice calls, at an early stage in the RNC and saves processing resources in the RNC.