8.13 E-DCH configurations (Rel-6 or later)
34.123-33GPPPart 3: Abstract test suite (ATS)TSUser Equipment (UE) conformance specification
The purpose of this clause is to specify the general ASP sequence and to precise values only when they have something specific in the given configuration.
8.13.1 DPCH (SRB) and E-DCH (RAB) configuration
8.13.1.1 Serving E-DCH cell
1. Configure DPCH physical channel
CPHY_RL_Setup_REQ
(
cellId_1
physicalChannelIdentity,
dPCHInfo_r5OrLater
r6 (
ul_DPCH_Info6
)
)
— set up the UL-DPCH channel. When UL-DPCH is established, E-DPCH shall use the same scrambling code.
2. Configure DCH transport channels
CPHY_TrCH_Config_REQ(
cellId_1
physicalChannelIdentity,
ulconnectedTrCHList,
ulTFCS)
— set up TFS for each DCH carried by the DPCH defined in step 5 and TFCS for the CCTrCH consisting
of all DCH’s mapped on the DPCH.
3. Configure MAC entity for DCH
CMAC_Config_REQ(
physicalChannelIdentity,
ulconnectedTrCHList,
ulTFCS)
— set up TFS and TFCS for DCH’s, and map logical channel to DCH transport channel.
uE_Info
4. Configure RLC for DCCH
CRLC_Config_REQ(
rB_Identity,
rBInfo)
— set up RLC entity on top of DCCH logical channels which are mapped onto DCH
5. Configure E-DCH DL physical channel CPHY_RL_Setup_REQ
(
physicalChannelIdentity,
e_AGCHInfo
(
e_AGCHInfo
tti
e_AGCH_PowerOffset
)
)
— set up the E-AGCH identified by PhysicalChannelIdentity
— E-AGCH channel is configured only in the serving E-DCH cell
— for E-AGCH the configurable parameters are
e_AGCHInfo E_AGCH_Information
e_AGCH_PowerOffset INTEGER (0..255)
e_RNTI_Primary E_RNTI
e_RNTI_Secondary E_RNTI
— The tti value shall be the same as the associated E-DPCH
CPHY_RL_Setup_REQ
(
physicalChannelIdentity,
e_HICHInfo
(
e_HICHInfo
tti
e_HICH_PowerOffset
)
}
— set up the E-HICH identified by PhysicalChannelIdentity
— for E-HICH the configurable parameters are
e_HICHInfo E_HICH_Information
e_HICH_PowerOffset INTEGER (0..255)
— The tti value shall be the same as the associated E-DPCH
— As E-HICH is having timing dependencies with DPCH, it is configured last
CPHY_RL_Setup_REQ
(
physicalChannelIdentity,
e_RGCHInfo
(
e_RGCHInfo
tti
e_RGCH_PowerOffset
)
)
— set up the E-RGCH identified by PhysicalChannelIdentity
— for E-RGCH the configurable parameters are
e_RGCHInfo E_RGCH_Information
e_RGCH_PowerOffset INTEGER (0..255)
— The tti value shall be the same as the associated E-DPCH
6. Configure E-DCH UL physical channel
CPHY_RL_Setup_REQ
(
physicalChannelIdentity
e_DPCHInfo
(
e_DPCCH_Info
e_DPDCH_Info
scramblingCodeType
scramblingCode
tti
edch_PhysicalLayerCategory
)
)
— set up the E-DCH identified by PhysicalChannelIdentity
— for E-DPCH the configurable parameters are
e_DPCCH_Info E_DPCCH_Info
e_DPDCH_Info E_DPDCH_Info
tti E_DCH_TTI
edch_PhysicalLayerCategory INTEGER (1..16)
— The scramblingCodeType and scramblingCode shall be the same as for Ul-DPCH
7. Configure E-DCH UL transport channels
CPHY_TrCH_Config_REQ (
physicalChannelIdentity,
e_DCHMacdFlows )
— set up the E-DCH transport channel which carries one or multiple MAC_d flows, one Mac_d flow is defined as
{
tti E_DCH_TTI
harqInfo ENUMERATED { rv0 (0) }
addReconf_MAC_d_Flow E_DCH_AddReconf_MAC_d_Flow
}
— the tti parameter is the same for all Mac_d flows
— each Mac_d flow is identified by mac-d-FlowIdentity defined in the addReconf_MAC_d_Flow
— for each MAC_d flow the configurable parameters are: mac-d-FlowPowerOffset, mac-d-FlowMaxRetrans, mac-d-FlowMultiplexingList, transmissionGrantType
8. Mapping E-DCH cells in Node B
CMAC_MACe_NodeB_CellMapping_REQ
(
nodeB_Id
celllist
)
— set-up the mapping between NodeB-Id and E-DCH cells in celllist
— a E-DCH cell is mapped to only one NodeB, and the cellId allocation is unique in a test.
9. Configure MAC_e entity for E-DCH
CMAC_MACe_Config_REQ
(
nodeB_Id
ddiMappinglist
e_DCHMacdFlows
connectedToMAC_es
)
— MAC_e entity is created per Node-B
— the e_DCHMacdFlows shall be same as that used in CPHY_TrCH_Config_REQ
— the field connectedToMAC_es shall be set to TRUE in serving E-DCH cell
— the field connectedToMAC_es shall be set to FALSE in inter nodeB SHO
— ddiMappinglist is defined as
activationTime SS_ActivationTime
macHeaderManipulation MAC_HeaderManipulation
logicalChannelIdentity LogicalChannelIdentity
e_DCH_MAC_d_FlowIdentity E_DCH_MAC_d_FlowIdentity
ddi DDI
rlc_PDU_SizeList RLC_PDU_SizeList
mac_LogicalChannelPriority MAC_LogicalChannelPriority
logicalChannelType LogicalChannelType
10. Configure MAC_es entity for E-DCH
CMAC_MACes_Config_REQ
(
ddiMappinglist
macTestMode
)
— set-up the mapping between the logical channel and the Mac_d flows
— only one MAC_es entity is created
— the ddiMappinglist shall be the same as that used in CMAC_MACe_Config_REQ
11. Configure RLC entity for DTCHs which is mapped on E-DCH
CRLC_Config_REQ
(
rB_Identity,
rBInfo
)
— set up RLC entity on top of DTCH logical channel which is mapped onto MAC_d flow
8.13.1.2 SHO – addition of E-DCH RL in a serving RL cell (intra node B)
1. Configure E-DCH physical channel
— E-DPCH is not configured: the cell is under the control of the same nodeB as the initial RL.
— E-AGCH channel is not configured, it is configured only in the serving E-DCH cell
CPHY_RL_Setup_REQ
(
physicalChannelIdentity,
e_HICHInfo
(
e_HICHInfo
tti
e_HICH_PowerOffset
)
}
— set up the E-HICH identified by PhysicalChannelIdentity
— for E-HICH the configurable parameters are
e_HICHInfo E_HICH_Information
e_HICH_PowerOffset INTEGER (0..255)
— The tti value shall be the same as the associated E-DPCH in the serving E-DCH cell
CPHY_RL_Setup_REQ
(
physicalChannelIdentity,
e_RGCHInfo
(
e_RGCHInfo
tti
e_RGCH_PowerOffset
)
)
— set up the E-RGCH identified by PhysicalChannelIdentity
— for E-RGCH the configurable parameters are
e_RGCHInfo E_RGCH_Information
e_RGCH_PowerOffset INTEGER (0..255)
The tti value shall be the same as the associated E-DPCH in the serving E-DCH cell
2. Mapping E-DCH cells in Node B
CMAC_MACe_NodeB_CellMapping_REQ
{
nodeB_Id
celllist
}
— set-up the mapping between NodeB-Id and the new E-DCH cell in celllist
8.13.1.3 SHO – addition of E-DCH RL in a non-serving RL cell (inter node B)
1. Configure E-DCH DL physical channel
CPHY_RL_Setup_REQ
(
physicalChannelIdentity,
e_HICHInfo
(
e_HICHInfo
tti
e_HICH_PowerOffset
)
}
— set up the E-HICH identified by PhysicalChannelIdentity
— for E-HICH the configurable parameters are
e_HICHInfo E_HICH_Information
e_HICH_PowerOffset INTEGER (0..255)
— The tti value shall be the same as the associated E-DPCH in the serving E-DCH cell
CPHY_RL_Setup_REQ
(
physicalChannelIdentity,
e_RGCHInfo
(
e_RGCHInfo
tti
e_RGCH_PowerOffset
)
)
— set up the E-RGCH identified by PhysicalChannelIdentity
— for E-RGCH the configurable parameters are
e_RGCHInfo E_RGCH_Information
e_RGCH_PowerOffset INTEGER (0..255)
— The tti value shall be the same as the associated E-DPCH in the serving E-DCH cell
2. Configure E-DCH UL physical channel
CPHY_RL_Setup_REQ
(
physicalChannelIdentity,
e_DPCHInfo
(
e_DPCCH_Info
e_DPDCH_Info
scramblingCodeType
scramblingCode
tti
edch_PhysicalLayerCategory
)
)
— set up the E-DCH identified by PhysicalChannelIdentity, the same as in the serving E-DCh cell
— for E-DPCH the configurable parameters are
e_DPCCH_Info E_DPCCH_Info,
e_DPDCH_Info E_DPDCH_Info,
edch_PhysicalLayerCategory INTEGER (1..16)
— The scramblingCodeType and scramblingCode shall be the same as for Ul-DPCH
— The tti value shall be the same as the E-DPCH in the serving E-DCH cell
— for E-DPCH, the scramblingCodeType and scramblingCode shall be the same as for Ul_DPCH
— E-AGCH channel is not configured
3. Configure E-DCH transport channels
CPHY_TrCH_Config_REQ
(
physicalChannelIdentity,
e_DCHMacdFlows
)
— set up the E-DCH transport channel which carries the same MAC_d flows as the initial RL
4. Configure MAC_e entity for E-DCH
CMAC_MACe_Config_REQ
(
nodeB_Id
ddiMappinglist
e_DCHMacdFlows
connectedToMAC_es FALSE
)
— MAC_e entity is created per Node-B
— the e_DCHMacdFlows shall be same as that used in CPHY_TrCH_Config_REQ
— the field connectedToMAC_es shall be set to FALSE in inter nodeB SHO
— ddiMappinglist is defined like in the initial RL
5. Mapping E-DCH cells in Node B
CMAC_MACe_NodeB_CellMapping_REQ
(
nodeB_Id
celllist
)
— set-up the mapping between the new NodeB-Id and E-DCH in the new cell
8.13.2 DPCH/HS-DSCH/E-DCH setup and release order
When setting up an HSUPA RAB, the following order of channel configuration is applied:
DL-DPCH, HS-DSCH, UL-DPCH, E-DCH.
When releasing an HSUPA RAB, the following order of channel release/ modification is applied:
E-DCH, HS-DSCH, UL-DPCH, DL-DPCH.
8.13.3 Serving E-DCH cell with UL DTX Configured [Rel-7]
UL-DRX is always configured when UL-DTX is started.
1. Configure DPCH physical channel
CPHY_RL_Setup_REQ
(
cellId_1
physicalChannelIdentity,
dPCHInfo_r5OrLater
r7 (
UL_DPCH_Info_r7
{
scramblingCodeType,
scramblingCode,
dpdchPresence notPresent
},
hs_DPCCHInd,
ss_UL_DPCCH_DRX_Info
)
)
— set up the UL-DPCCH, hs-DPCCH channel. When UL-DPCCH is established, E-DPCH shall use the same scrambling code. UL DPCCH DRX parameters are provided.
2. Continue with steps 5 through 11 in clause 8.13.1.1 except for Rel-7 branches if available.
If DL_DRX is enabled IE ‘ss_DTX_Info’ shall be provided in E_AGCH/E_RGCH/HS_PDSCH configuration.
If DL_DRX is enabled IE ‘ss_DTX_Info’ shall be provided in:
– CMAC_MAChs_MACehs_TFRCconfigure_REQ when configuring HS_PDSCH.
For F-DPCH configuration ‘ss_DTX_Info’ shall be provided.
3. Configure MAC_e entity for E-DCH
CMAC_MACe_Config_REQ
(
nodeB_Id
ddiMappinglist
e_DCHMacdFlows
connectedToMAC_es
ss_DRX_MAC_Info
{
mac_InactivityThreshold,
mac_dtx_Cycle_2ms,
mac_dtx_Cycle_10ms,
timingInfo
}
)
— MAC_e entity is created per Node-B
— the e_DCHMacdFlows shall be same as that used in CPHY_TrCH_Config_REQ
— the field connectedToMAC_es shall be set to TRUE in serving E-DCH cell
— the field connectedToMAC_es shall be set to FALSE in inter nodeB SHO
— ddiMappinglist is defined as
activationTime SS_ActivationTime
macHeaderManipulation MAC_HeaderManipulation
logicalChannelIdentity LogicalChannelIdentity
e_DCH_MAC_d_FlowIdentity E_DCH_MAC_d_FlowIdentity
ddi DDI
rlc_PDU_SizeList RLC_PDU_SizeList
mac_LogicalChannelPriority MAC_LogicalChannelPriority
logicalChannelType LogicalChannelType
8.13.4 E-DCH configuration for enhanced Cell_FACH uplink (Rel-8 or later)
8.13.4.1 E-DCH configuration at cell creation
1. Configure UL DPCH physical channel
CPHY_RL_Setup_REQ (
cellId
physicalChannelIdentity,
setupMessage (
physicalChannelInfo dPCHInfo_r5 : r8: (
ul_DPCHInfo UL_DPCH_Info_r7 (
dpcch_PowerOffset
pc_Preamble
sRB_delay
powerControlAlgorithm
deltaACK — As per TS 34.108[3]
deltaNACK — As per TS 34.108[3]
ack_NACK_repetition_factor — As per TS 34.108[3]
harq_Preamble_Mode
)
modeSpecificInfo fdd : (
scramblingCodeType
scramblingCode
dpdchPresence = notPresent
)
)
)
)
— set up the UL-DPCCH without HS-DPCCH channel. When UL-DPCCH is established, E-DPCH shall use the same scrambling code.
2. Configure E-DCH DL physical channel
CPHY_RL_Setup_REQ (
cellId
physicalChannelIdentity,
setupMessage (
physicalChannelInfo e_AGCHInfo : r8 : (
e_AGCHInfo
tti
e_AGCH_PowerOffset
e_RNTI_Primary = omit
e_RNTI_Secondary = omit
initialServingGrantValue = 4 — as per TS 34.108[3]
)
)
)
— setup E-AGCH identified by PhysicalChannelIdentity
— The tti value shall be the same as the associated E-DPCH
CPHY_RL_Setup_REQ (
cellId
physicalChannelIdentity,
setupMessage (
physicalChannelInfo e_HICHInfo : (
e_HICHInfoCommonEDCH
tti
e_HICH_PowerOffset
)
)
)
— setup E-HICH identified by PhysicalChannelIdentity
— The tti value shall be the same as the associated E-DPCH
CPHY_RL_Setup_REQ (
cellId
physicalChannelIdentity,
setupMessage (
physicalChannelInfo e_RGCHInfo: (
e_RGCHInfoCommonEDCH
tti
e_RGCH_PowerOffset
)
)
)
— setup E-RGCH identified by PhysicalChannelIdentity
— The tti value shall be the same as the associated E-DPCH
3. Configure E-DCH UL physical channel
CPHY_RL_Setup_REQ (
cellId
physicalChannelIdentity
setupMessage (
physicalChannelInfo e_DPCHInfo : r8 🙁
e_DPCCH_Info
e_DPDCH_Info
scramblingCodeType
scramblingCode
tti
edch_PhysicalLayerCategory
)
)
)
— setup E-DCH identified by PhysicalChannelIdentity
4. Configure E-DCH UL transport channels
CPHY_TrCH_Config_REQ (
cellId
physicalChannelIdentity,
configMessage (
e_DCHMacd_CommonFlows
)
)
— setup the E-DCH transport channel which carries 3 common E-DCH MAC-d flows according to TS 34.108[3].
5. Mapping E-DCH cells in Node B
CMAC_MACi_NodeB_CellMapping_REQ
(
nodeB_Id
celllist
)
— setup the mapping between NodeB-Id and E-DCH cells in celllist
— a common E-DCH cell is mapped to only one NodeB
6. Configure MAC_i entity for E-DCH
CMAC_MACi_Config_REQ (
nodeB_Id
configMessage setup : commonMac_i_r8 : (
lCH_Mappinglist
e_DCHMacdFlows
)
)
— one MAC-i entity is created per Node-B
— lCH_Mappinglist includes mapping for UL CCCH and SRB1-4
— e_DCHMacdFlows shall be same as provided in e_DCHMacd_CommonFlows in CPHY_TrCH_Config_REQ
7. Configure MAC_is entity for E-DCH
7.1 Mapping for DCCH
CMAC_MACis_Config_REQ (
cellId = -1
configMessage setup : mACis_r8 : (
lCHMappinglist — DCCH mapping list
)
)
— lCHMappinglist shall be the same as DCCH list provided in CMAC_MACi_Config_REQ
7.2 Mapping for CCCH
CMAC_MACis_Config_REQ (
cellId
configMessage setup : mACis_r8 : (
lCHMappinglist — CCCH mapping list
)
)
— lCHMappinglist shall be the same as CCCH list provided in CMAC_MACi_Config_REQ
— cellId set to the cell on which E-DCH is configured (i.e. it is NOT set to -1)
8. Configure RLC entities for DCCH and CCCH mapped on E-DCH
CRLC_Config_REQ (
cellId = -1
rB_Identity,
sS_rlc_Info_r8 r8 : (
sS_ul_RLC
sS_dl_RLC_Mode
altE_bitInterpretation
useSpecialValueOfHEField
)
rB_LogCH_Mapping
)
— setup RLC entities on top of DCCH(tsc_RB1-4) and CCCH(tsc_RB0_EFUL) logical channel which is mapped onto e-MACd flow
8.13.4.2 E-DCH reconfiguration during signalling connection establishment
1. Receiving RRC Connection Request
2. Sending RRC Connection Setup
3. Reconfigure E-AGCH
3.1 Configure E-RNTI in E-AGCH
CPHY_RL_Modify_REQ (
cellId
physicalChannelIdentity,
e_AGCHInfo : r8 : (
e_AGCHInfo
tti
e_AGCH_PowerOffset
e_RNTI_Primary
e_RNTI_Secondary = omit
)
)
— E-RNTI is set to the same value as provided to UE in RRC Connection Setup
3.2 Send a grant to complete collision resolution phase
CMAC_MACi_AG_REQ (
nodeB_
cellId
grantType primary
absoluteGrantValue = 31
)
4. Receiving RRC Connection Setup Complete
8.13.4.3 E-DCH reconfiguration during radio bearer establishment
1. Sending Radio Bearer Setup
— with condition A29 (to Enhanced CELL_FACH from Enhanced CELL_FACH in PS with SRBs mapped on common E-DCH/HS-DSCH)
2. Reconfigure E-DCH UL transport channels
CPHY_TrCH_Config_REQ (
cellId
physicalChannelIdentity,
e_DCHMacd_CommonFlows
)
— reconfigure E-DCH transport channel which carries 3 common E-DCH MAC-d flows acc to TS 34.108[3].
3. Configure MAC_i entity for E-DCH
CMAC_MACi_Config_REQ (
nodeB_Id
configMessage reconfig : commonMac_i_r8 : (
lCH_Mappinglist
e_DCHMacdFlows
)
)
— lCH_Mappinglist includes mapping for UL CCCH/SRB1-4 and DTCN RB25
— e_DCHMacdFlows shall be same as that used in CPHY_TrCH_Config_REQ
4. Configure RLC entity for DTCH mapped on E-DCH
CRLC_Config_REQ (
cellId = -1
rB_Identity,
sS_rlc_Info_r8 r8 : (
sS_ul_RLC
sS_dl_RLC_Mode
)
rB_LogCH_Mapping
)
— setup RLC entity on top of DTCH(tsc_RB25) logical channel which is mapped onto e-MACd flow
5. Receiving Radio Bearer Setup Complete