Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
Xia Cuichun
2006/9/18
Revision History
Date 2006-9-15 2006-10-14 2006-11-10 2006-12-19 Revision Version V1.0 V1.1 V1.2 V1.3 Description Create the document. Add the contents about signaling flows. Add descriptions about the problems found during the test. Delete the unnecessary information. Author Xia Cuichun Xia Cuichun and Ge Liang Xia Cuichun Ge Yougong
Contents
1 Basic Signaling Flows.............................................................................................................5 1.1 1.2 1.3 1.4 1.5 2 Signaling Flow when the UE Reports the HSUPA Capability .........................................5 HSUPA Cell Setup Signaling Flow..................................................................................7 Signaling Flow for Service Setup over the HSUPA Channel...........................................8 Soft (Softer) Handover Signaling Flow..........................................................................12 Hard Handover Signaling Flow (E2E/E2D)....................................................................17
2012-1-13
Page 3 of 21
Figures
Figure 1.1The RRC CONNECTION REQUEST message..............................................................5 Figure 1.2The RRC CONNECT SETUP CMP message.................................................................6 Figure 1.3HSUPA cell setup signaling flow..................................................................................7 Figure 1.4Major IEs in the NBAP_PSCH_RECFG_REQ message...............................................8 Figure 1.5IEs in the RL_RECFG_READY message......................................................................9 Figure 1.6E-RNTI in the RB_SETUP message............................................................................10 Figure 1.7MAC-d flow information in the RB_SETUP message...............................................10 Figure 1.8E-DCH information in the RB_SETUP message........................................................11 Figure 1.9HSUPA soft handover signaling flow.........................................................................13 Figure 1.10RG_Combination_Index in the soft handover process .........................................14 Figure 1.11RLS information returned in the NBAP_RL_RECFIG_READY message upon service setup over the HSUPA channel .....................................................................................15 Figure 1.12RLS information when an E-DCH radio link is added.............................................15 Figure 1.13Serving cell update (physical channel reconfiguration) ........................................16
2012-1-13
Page 4 of 21
2012-1-13
Page 5 of 21
The E-DCH physical layer category information is contained in the UE_CAPABILITY_CONTAINER. The UU_UE_CAP_CONTAINER_R6_STRU generally consists of two parts:
The other is INTER_RAT_UE_RADIO_ACCESS_CAP. Where, the UeRadioAccessCapV690ext will report whether the UE supports the E-DCH. If yes, the value of E-DCH category will be reported. Because these values are stored in the container, they cannot be directly viewed in the message.
2012-1-13
Page 6 of 21
2012-1-13
Page 7 of 21
1.3 Signaling Flow for Service Setup over the HSUPA Channel
Generally, the NodeB returns the control information related to the E-DCH to the RNC through the RL_RECFG_READY message. Such information includes the Primary ERNTI used by the E-AGCH, Secondary E-RNTI, the channelisation code, the ERGCH/E-HICH signature sequence, and the initial serving grant value.
2012-1-13
Page 8 of 21
Note: If the RRC is set up on the CCH, NodeB will return the above information in the RL_SETUP_RESPONSE message.
The RNC informs the UE of the (Primary) E-RNTI newly assigned by the NodeB through the RB_SETUP message, as shown in 1.3.
2012-1-13
Page 9 of 21
2012-1-13
Page 10 of 21
In 1.3, the type of transmission channel added is E-DCH and the TTI is 10ms. The RVTABLE is used for the HARQ retransmission. The PO of the MAC-d flow is 0dB. The HARQ can be transmitted for up to eight times. As only one MAC-d flow is configured, MAC-d flow multiplexing is not involved.
The following lists explanations of some parameters in Figure 8: 1) 2) 3) 4) E-DPCCH-DPCCH power offset: The value is 5 (15/15), indicating that the transmit power of the E-DPCCH is the same as that of the DPCCH. Happybit delay timer: The value is 20ms. A smaller value means it is easier to trigger Unhappy. E-TFCI: The value is Table 1, which is generally used when the RLC PDU is set to 336bit. Reference E-TFCI and PO: There is only one group of reference E-TFCI and PO here. The settings of these values are very important.
2012-1-13
Page 11 of 21
5) 6) 7) 8) 9)
Maximum number of channelisation codes supported: The value is 7 here, representing two SF4 codes. pl-NonMax (Puncturing Limit): The value is 11 here, representing 0.44. At this puncturing limit, the maximum rate of the uplink MAC layer can reach 1.44Mbps. periodicityOfSchedInfo (Period for sending Scheduling Information): The value is 50ms when there is no grant and 100ms when there is grant. The PO is 6dB. RG threeIndexStep Threshold: The value is 20. TwoIndexStep Threshold: The value is 25. The initial grant value is calculated by the NodeB according to the user GBR attributes.
Meanwhile, most of the above information will also be sent to the NodeB through the RL_RECFG_PREP message.
2012-1-13
Page 12 of 21
2012-1-13
Page 13 of 21
RG_Combination_Index indicates that the UE combines the E-RGCHs of all the cells belonging to the same serving RLS. The flow is described as follows: The UE originates the service in the serving cell. The NodeB returns the RLS information of the E-DCH radio link that is set up in the RL_RECFG_READY message. When a new link is added, NodeB also returns the RLS information of the new E-DCH radio link. Based on such information, the RNC indicates the RG_Combination_Index in the RRC_ACTIVE_SET_UPDATE message. According to this index, the UE combines the RG information of the cells that belong to this serving RLS.
2012-1-13
Page 14 of 21
Figure 1.11 RLS information returned in the NBAP_RL_RECFIG_READY message upon service setup over the HSUPA channel
2012-1-13
Page 15 of 21
In 1.4, the RNC uses the PCH reconfiguration command to change the 230 cell into the E-DCH non-serving cell and meanwhile indicates that the 233 cell has been changed into an E-DCH serving cell.
2012-1-13
Page 16 of 21
Note: For Huawei products, the condition for triggering the HS-DSCH serving cell update and E-DCH serving cell update is that the UE reports the 1D event. As the DCH is still used at the downlink direction during the test, the HS-DSCH serving cell attribute of both the source cell and the target cell is FALSE. In the future, using HSDPA and HSUPA jointly to carry services will become a mainstream application. In this case, the HS-DSCH and E-DCH serving cell attributes will be updated at the same time.
The following explains the relationship between an HSUPA cell and a non-HSUPA cell in the soft handover process:
When the new target cell does not support the HSUPA or supports HSUPA but the admission fails, the target cell will be added to the active set. After the successful addition, the RNC will reconfigure the E-DCH radio link of the source cell as a DCH.
If the non-HSUPA cells in the active set are removed (that is, all cells in the active set supports the HSUPA), an attempt will be made to reconfigure the DCH radio link over the E-DCH.
2012-1-13
Page 17 of 21
The contents of the RRC_PH_CH_RECFG message are similar to that in the previous section, except that this message has the extra information related to the compressed mode. When the UE reports the RRC_PH_CH_RECFG_CMP message on the new cell, the hard handover flow is ended. This flow is an E2E hard handover flow. That is, the service stays on the E-DCH before and after the hard handover. The following explains the E2D hard handover flow.
2012-1-13
Page 18 of 21
The channel type is back to the DCH and the compressed mode is stopped.
2012-1-13
Page 19 of 21
In the RB MAPPING, the UE uplink channel is back to the DCH and meanwhile the EDCH information has been deleted.
2012-1-13
Page 20 of 21
Table 13.1 FDD E-DCH physical layer categories E-DCH category Maximum number of EDCH codes transmitted Minimum spreadin g factor Support for 10 and 2 ms TTI EDCH Maximum number of bits of an E-DCH transport block transmitted within a 10 ms EDCH TTI 7110 14484 14484 20000 20000 20000 Maximum number of bits of an E-DCH transport block transmitted within a 2 ms E-DCH TTI
1 2 2 2 2 4
10 ms TTI only 10 ms and 2 ms TTI 10 ms TTI only 10 ms and 2 ms TTI 10 ms TTI only 10 ms and 2 ms TTI
NOTE: When four codes are transmitted in parallel, two codes shall be transmitted with SF2 and two with SF4.
Note: The E-DCH capability of Qualcomm 7200 is Category 5, that is, the UE supports 2*SF2 and 10ms TTI.
2012-1-13
Page 21 of 21