Field Guide Change Alert

Field Guide Change Information:

Name of Change:

UTRAN number of HSDPA users increase to 64 05.0-E-001 Ericsson (UTRAN)

Affective Date of Change: Field Guide Reference #: Issuer Name: Issuer Contact #:

02/11/2011 Ericsson UTRAN Vol. II Vladimir Gusavac 425 753 0171

Change Number:

Equipment Vendor:

Description of the Change:

In the space below, describe at a high level what and why this change is necessary and how it may affect the current systems.

This approved Field Guide Alert is sent as part of the normal Field Guide Alert process to communicate a change in the National recommendation for Ericsson UTRAN configurable parameters. This Field Guide Alert supersedes FGA31 and it addresses the number of HSDPA users in the scheduler as well as the number of hs resource ids defined per TX board. On the top of number of HSDPA users change to 64 (addressed with FGA31) causing DCH resource consumption reduction this FGA is also focusing on TX board capacity allocated to HS. Basically, it will max out TX board capacity from HSDPA standpoints to improve HSDPA performance and throughput at the same no sacrificing channel element capacity for DCH. That way all available TX board resources will be fully utilized leading to more efficient way of TX board usage. Also, note there will not be change in total number of HS users per sites, but the peak of hs users per cell will be increased due to more hs resources defined. The parameters adjustment will also increase number of HS code in the pool leading to higher throughput and more HS users allocated per TTI. Each TX board has limited number of processing resource ids, which can be defined as HS, EUL or DCH

Each Resource ID can perform one of the following: 128 CEs for DCH Support EUL on 6 cell-carriers 15 codes on a single cell 20 codes dynamically shared between 2 cell-carriers 15 codes dynamically shared between 3 cell-carriers

There is also limitation in terms of the maximum number of resources for DCH and A-DCH: HS-TX15: 1 max for DCH and A-DCH HS-TX45: 3 max for DCH and A-DCH HS-TX60: 3 max for DCH and A-DCH Example: In case of 2xHS-TX60, maximum of 6 resource ids can be used for DCH and A-DCH leaving 6 resource ids for HS and EUL in total. Since one resource is used for EUL, maximum of 5 resources can be used for HS and that is something addressed here (3 resources were defined with FGA31 though). More hs resource ids will contribute to more HS codes and better HSDPA performance. Also, it increases the peak number of HS users available per cell. With introduction and big penetration of smart phones, data network usage has increased. With proposed parameters change, an objective is to reduce DCH traffic, their resource consumption and improve data customer experience. The values in braces indicate [Level, Value, Units, Class]: maxNumHsdpaUsers [NodeB, 64, Users, Global] is changed from 32 to 64 HSDPA users. The parameter defines the maximum allowed number of HSDPA users per cell. hsdpaUsersAdm [Cell, 64, Users, Global] is changed from 32 to 64 HSDPA users. The parameter defines the admission limit for the number of HSDPA users per cell. maxNumADchReservation [NodeB, (84, 125,167, 188, 250, 291, 333, 375), Integer, Local] is changed from (125, 188, 250, 312, 375) to (84, 125,167, 188, 250, 291, 333, 375). The parameter defines the maximum number of A-DCH resources that may be configured in a baseband pool. The recommended setting depends of TX board combo and number of cell carriers. numHsCodeResources [NodeB, (1,2,3), Integer, Local] is increased on some TX boards in the baseband pool. The parameter indicates how many processing resources on the TX board are loaded with HSDPA software. As mentioned, the recommended settings for the parameters maxNumADchReservation and numHsCodeResources depend of TX boards combination and number of cell carriers per site. For the sites with one TX board in the baseband pool, the recommended settings for the parameters maxNumADchReservation and numHsCodeResources are as below:

For the sites with two TX boards in the baseband pool, the recommended settings for the parameters maxNumADchReservation and numHsCodeResources are as below:

For the sites with two baseband pools, the parameters maxNumADchReservation and numHsCodeResources will be set separately for each baseband pool applying the same rules as above except the fact that in second pool the number of EUL resources will be set to 0.
How to identify which cell-carriers are in the Baseband Pool1 and in Baseband Pool2: Get printout of all TX Boards in NodeB. Several methods can be used, commands which would work are: o bo o cabx o hget slot productdata TX Select lowest slot number (it is slot=10 for 3106/3206 macros) as it is always in BB Pool1 Check which carriers are assigned to that slot TX Board (also provides RbsLocalCell correlation) hget carrier dbccDeviceRef|reservedby .slot=10

The recommended settings would help network performance: more HS users, more HS data traffic volume more HS codes and better HS performance less R99 users, less R99 data traffic volume less DL Codes & Power blocking: especially big reduction in codes blocking better Accessibility improved DL up-switch performance more efficient way of TX board usage Also, degradation in major RTB KPIs should not be observed. DL CE utilization may increase, but it will be far away from DL CE admission threshold. The following KPIs need to be closely monitored by the market once the change is made: CS & PS Call Success Rate CS & PS Retainability Rate DCH and HS traffic Number of HS rejections Presentations outlining the results are available at the following location: Result Summary number of HSDPA users increase to 64

Implementation of the Change: In the space below, describe in detail how this change is implemented for each system impacted.

The parameter maxNumHsdpaUsers is nodeB level parameter belonging to RbsLocalCell MO class. The parameter hsdpaUsersAdm is cell level parameter belonging to UtranCell MO class. The parameter maxNumADchReservation is nodeB level parameter belonging to DownlinkBaseBandPool MO class. The parameter numHsCodeResources is nodeB level parameter belonging to TxDeviceGroup MO class. No action needed by the markets, these changes will be implemented by the MPC. For any

questions regarding the timeline for specific market please contact Christopher Wyatt (cw7534@att.com). Also, here is the link to the weekly TX board report containing FGA01 audit so market can track progress.