HSPA Service Setup Failure

1.1 Fault Description

The HSPA service setup failure can be as follows: A: After a cell is set up, the HSPA cell cannot be activated. B: After the HSPA cell is activated, the HSPA service cannot be set up. The PS R99 service can be normally set up but cannot be borne on an HSPA channel. If PS services (such as the PS R99 service) cannot be set up, see Chapter 6 .

1.2 Possible Fault Causes

Possible fault causes are as follows:

The licenses for the HSPA functions are not activated. The NodeB protocol version is incorrectly configured, and does not support the HSPA services. The UE does not support the HSPA services. The IPPATH are not configured with the corresponding transmission resource on the RNC and NodeB. The maximum bit rate (MBR) has not reached the threshold for setting up the HSPA services.

1.3 Troubleshooting Method

1.3.1 HSPA Cell Activation Failure After a Cell Is Set Up
Step 1 Check whether the licenses for the HSPA functions are valid. Run the command DSP LICUSAGE to check whether the High Speed Downlink Packet Access (HSDPA) and High Speed Uplink Packet Access (HSUPA) functions are enabled. If the functions are not enabled, you must apply for licenses to activate the HSPA functions.

Step 2 Check data configuration. Run the command LST UNODEB to check whether the NodeB protocol version is configured correctly. The REL-5 version supports the HSDPA, and the REL-6 version supports both the HSDPA and the HSUPA.

Step 3 Check the occupation of the code tree in the cell. Check the occupation of code tree resources in the cell. Usually, the HSDPA service uses the last five SF16 code tree resources. If the resources are distributed to R99 users, the HSDPA service cannot be set up.

1.3.2 HSPA Service Setup Failure After the HSPA Cell Is Set Up
Step 1 Check whether the UE supports the HSPA services. The setup of the HSPA services requires the support of the UE. Send the RRC CONNECTION SETUP REQ message to check whether the UE attempting to access the network supports the HSPA functions. If the UE supports the HSDPA, the REL-5 version is displayed. If the message contains the ueCapabilityIndication IE and the value contains e-dch, the UE supports the HSUPA function, as shown in the following figure.

Step 2 Check whether the number of HSPA users is limited. The number of HSUPA users and the number of HSDPA users are independent from each other. Therefore, you need to set admission thresholds at both the cell level and the NodeB level. The maximum number of HSPA users supported by a cell is MIN (value specified in the RNC license, value set in the cell CAC algorithm). The RNC license controls the maximum number of HSPA users a single cell, which can be queried through the command DSP LICUSAGE. This number is subject to the maximum number of HSPA users that are supported. For example, the 64HSDPA Users per Cell switch is ON, indicating that the cell supports up to 64 HSDPA users.

Run the command LST UCELLCAC and set the numbers of HSUPA users and HSDPA users in the cell CAC algorithm.

Run the command LST UNODEBLGOPARA to query the maximum number of HSPA users supported by the NodeB. By default, this number is 3840. Access failure rarely occurs.

Run the command DSP UCELLCHK to query the number of HSPA users supported by the serving cell. If the result is equal or close to the number of users permitted in the license or configured in the CAC algorithm, the access fails due to the admission threshold for HSPA users. You need to re-apply for the relevant license or modify admission threshold for users.

Step 3 Check the IPPATH configurations. Check whether the IPPATH (IP) are configured on the RNC and NodeB. You must view the corresponding transmission resource mapping table. Run the command LST TRMMAP, and the following information is displayed:

Run the command LST IPPATH to check whether the IPPATH with the corresponding properties is configured. Step 4 Check whether the IPPATH are availableCheck the IP PATH state and bandwidth configuration. On the RNC, run the DSP IPPATH command through the LMT to check whether the IPPATH is available and whether the remaining bandwidth is sufficient. If the IPPATH is unavailable or the remaining bandwidth is insufficient, the IPPATH access fails.

Step 5 Check the MBR assigned by the CN. The RNC determines whether to use the HS-DSCH or E-DCH to bear the service based on the MBR assigned by the CN and the preset threshold. If the MBR assigned by the CN exceeds the threshold for setting up the HSPA service, the service can be set up on the HSDSCH/E-DCH. Otherwise, the service is borne on the E-DCH. The thresholds for the BE service and streaming service are set independently. As shown in the following figure, the MBR is assigned in the RANAP_RAB_ASSIGNMENT_REQUSET message.

You can run the command LST UFRCCHLTYPEPARA to query the threshold for setting up the HSPA service. If the uplink rate assigned by the CN is lower than the threshold for setting up the HSUPA service, you should negotiate with the operator on whether to modify the threshold to set up the HSPA service. Alternatively, you can modify the subscription information on the HLR. Check the consistency between the IMSI information and the CN-assigned information before the modification. The subscription information on the HLR may be correct, but an AT command is used to limit the rate during the dial-up. Instead of providing a solution to the problem, the

modification of the threshold for setting up the HSPA service can only ensure the settingup of the service on the HS-DSCH. The service rate for users is still under the control of the MBR. Therefore, it is necessary to modify the subscription information on the HLR or cancel the AT command for limiting the service rate.

Step 6 Check the health of a cell. Run the command DSP UCELLCHK to check the health of a cell and whether the cell is in congested state. For the specific method, see Service Setup Failure Document.