13.8 Parameter values for default radio configurations in CELL_FACH

25.3313GPPProtocol specificationRadio Resource Control (RRC)Release 17TS

The UE shall support the use of the default parameter values that are specified in the following. Optional IEs that are not used, are omitted. The tabular values included in this subclause, represent the actual IE values as in clause 10, and not the ASN.1 representation of these values.

The UE shall for each RB with radio bearer identity n listed in the default configuration with the Default configuration identity given in IE "Default configuration identity for CELL_FACH":

1> if a multiplexing option containing the combination "FACH" for the DL and "RACH" for the UL for a RB with radio bearer identity n is included in the default configuration:

2> if the radio bearer identity n is listed in explicit or another default configuration in the message received by the UE:

3> if there is no multiplexing option containing the combination "FACH" for the DL and "RACH" for the UL for this radio bearer identity n:

4> append the radio bearer mapping information in accordance with the default parameters for RB with radio bearer identity n to the radio bearer mapping information for RB with radio bearer identity n.

2> else

3> store the radio bearer mapping information in accordance with the default parameters for RB with radio bearer identity n and configure the transmitting and receiving RLC entities in the UE for that radio bearer according to Table 13.8.1

1> if a multiplexing option containing the combination "HS-DSCH" for the DL and "RACH" for the UL for a RB with radio bearer identity n is included in the default configuration:

2> if the radio bearer identity n is listed in explicit or another default configuration in the message received by the UE:

3> if there is no multiplexing option containing the combination "HS-DSCH" for the DL and "RACH" for the UL for this radio bearer identity n:

4> append the radio bearer mapping information in accordance with the default parameters for RB with radio bearer identity n to the radio bearer mapping information for RB with radio bearer identity n.

2> else

3> store the radio bearer mapping information in accordance with the default parameters for RB with radio bearer identity n and configure the transmitting and receiving RLC entities in the UE for that radio bearer according to Table 13.8.1

1> if a multiplexing option containing the combination "HS-DSCH" for the DL and "E-DCH" for the UL for a RB with radio bearer identity n is included in the default configuration:

2> if the radio bearer identity n is listed in explicit or another default configuration in the message received by the UE:

3> if there is no multiplexing option containing the combination "HS-DSCH" for the DL and "E-DCH" for the UL for this radio bearer identity n:

4> append the radio bearer mapping information in accordance with the default parameters for RB with radio bearer identity n to the radio bearer mapping information for RB with radio bearer identity n.

2> else

3> store the radio bearer mapping information in accordance with the default parameters for RB with radio bearer identity n and configure the transmitting and receiving RLC entities in the UE for that radio bearer according to Table 13.8.1

Table 13.8.1: Default radio configurationĀ 0 in CELL_FACH

Ref 34.108 / 25.993

Default configuration identity

0

RB INFORMATION

rb-Identity

RB1: 1, RB2: 2, RB3: 3, RB4: 4

rlc-InfoChoice

RLC info for CELL_FACH signalling

>ul-RLC-Mode

RB1: UM, RB2-RB4: AM

>>transmissionRLC-DiscardMode

RB1: N/A, RB2-RB4: NoDiscard

>>>maxDat

RB1: N/A, RB2-RB4: 40

>>transmissionWindowSize

RB1: N/A, RB2-RB4: 64

>>timerRST

RB1: N/A, RB2-RB4: 200

>>max-RST

RB1: N/A, RB2-RB4: 1

>>pollingInfo

RB1: N/A, RB2-RB4: as below

>>>TimerPoll

RB1: N/A, RB2-RB4: 1000

>>>PollSDU

RB1: N/A, RB2-RB4: 1

>>>lastTransmissionPDU-Poll

RB1: N/A, RB2-RB4: FALSE

>>>lastRetransmissionPDU-Poll

RB1: N/A, RB2-RB4: TRUE

>>>PollWindow

RB1: N/A, RB2-RB4: 99

>dl-RLC-Mode

RB1: UM, RB2-RB4: AM

>>dl-RLC-PDU-size

RB1: N/A, RB2-RB4: 128 (actual size 144 bits)

>>inSequenceDelivery

RB1: N/A, RB2-RB4: TRUE

>>receivingWindowSize

RB1: N/A, RB2-RB4: 64

>>dl-RLC-StatusInfo

RB1: N/A, RB2-RB4: as below

>>>missingPDU-Indicator

RB1: N/A, RB2-RB4: TRUE

>>dl-UM-RLC-LI-size

RB1: 7, RB2-RB4: N/A

rlc-OneSidedReEst

RB1-RB4: FALSE

rb-MappingInfo

For RACH/FACH as a mapping option

>UL-LogicalChannelMappings

>>ul-TransportChannelType

RACH

>>logicalChannelIdentity

RB1: 1, RB2: 2, RB3: 3, RB4: 4

>>rlc-SizeList

RB1-RB4: explicitList (refers to SIB5/6)

>>>rlc-SizeIndex

1 (refers to RACH TFS in SIB5/6)

>>mac-LogicalChannelPriority

RB1: 1, RB2: 2, RB3: 3, RB4: 4

>DL-logicalChannelMappingList

>>>dl-TransportChannelType

FACH

>>>logicalChannelIdentity

RB1: 1, RB2: 2, RB3: 3, RB4: 4

NOTE: In SRNC relocation, the target SRNC shall check IE "Signalling RB information" in IE "SRNS RELOCATION INFO" to find out the current RLC info and RB mapping info used by the UE.