8.5.21 Actions related to Radio Bearer mapping

25.3313GPPProtocol specificationRadio Resource Control (RRC)Release 17TS

Tools: ARFCN - Frequency Conversion for 5G NR/LTE/UMTS/GSM

When the UE receives the IEs "RB mapping info", "CCCH mapping info", "SRB1 mapping info" and/or the IE "Transport format set", when transport channels, MAC-d flows, MAC-ehs reordering queues or E-DCH MAC-d flows are added or deleted, when the UE performs a cell reselection or a state transition, or when the UE releases a RB, or when the value stored in the variable FALLBACK_R99_PRACH_ENABLED changes, the UE shall for each of the configured Radio Bearers:

1> upon moving to CELL_FACH state from URA_PCH, CELL_PCH or CELL_DCH state to initiate a cell update procedure and upon subsequent cell reselections until the first successfully completed cell update procedure, only perform the actions defined in the remainder of this subclause after reception of the CELL UPDATE CONFIRM message;

1> for FDD, select the multiplexing option according to the following:

2> if the UE is in CELL_PCH or URA_PCH state:

3> if the UE does support HS-DSCH reception in CELL_PCH and URA_PCH state and IE "HS-DSCH paging system information" is included in System Information Block type 5 or System Information Block type 5bis; or

3> if the variable HSPA_RNTI_STORED_PCH is set to TRUE:

4> if the UE does support Enhanced Uplink in CELL_FACH state and Idle mode and the IE "Common E-DCH system info" is included in System Information Block type 5 or System Information Block type 5bis and if C-RNTI, H-RNTI and primary E-RNTI are provided to the UE:

5> if the RB has a multiplexing option with transport channel type "HS-DSCH" for the DL, and the corresponding MAC-ehs reordering queue is configured, and transport channel type "E-DCH" for the UL and the corresponding common E-DCH MAC-d flow is configured:

6> select this multiplexing option;

4> else:

5> if the RB has a multiplexing option with transport channel type "HS-DSCH" for the DL, and the corresponding MAC-ehs reordering queue is configured, and transport channel type "RACH" for the UL:

6> select this multiplexing option.

2> if the UE is in CELL_FACH state:

3> if the UE does not support HS-DSCH reception in CELL_FACH state; or

3> if the IE "HS-DSCH common system information" is not included in System Information Block type 5 or System Information Block type 5bis:

4> if the RB has a multiplexing option with transport channel type "FACH" for the DL, and transport channel type "RACH" for the UL:

5> select this multiplexing option.

3> else:

4> if the UE does not support Enhanced Uplink in CELL_FACH state and Idle mode; or

4> if the IE "Common E-DCH system info" is not included in System Information Block type 5 or System Information Block type 5bis:

5> if the RB has a multiplexing option with transport channel type "HS-DSCH" for the DL, and the corresponding MAC-ehs reordering queue is configured, and transport channel type "RACH" for the UL:

6> select this multiplexing option.

4> else:

5> if either of the following conditions is met: and

6> the radio bearer is mapped to CCCH and IE "CCCH Fallback" is set to TRUE;

6> the radio bearer is mapped to DCCH and IE "DCCH Fallback" is set to TRUE.

5> if the variable FALLBACK_R99_PRACH_ENABLED is set to TRUE:

6> if the RB has a multiplexing option with transport channel type "HS-DSCH" for the DL, and the corresponding MAC-ehs reordering queue is configured, and transport channel type "RACH" for the UL:

7> select this multiplexing option.

5> else:

6> if the RB has a multiplexing option with transport channel type "HS-DSCH" for the DL, and the corresponding MAC-ehs reordering queue is configured, and transport channel type "E-DCH" for the UL and the corresponding common E-DCH MAC-d flow is configured:

6> select this multiplexing option.

2> if the UE is in CELL_DCH state:

3> if the RB has a multiplexing option with transport channel type "DCH + HS-DSCH" for the DL, and both the corresponding DCH transport channel and the corresponding MAC-d flow or MAC-ehs reordering queue are configured, and with transport channel type "E-DCH" for the UL, and the corresponding E-DCH MAC-d flow is configured:

4> select this multiplexing option; else

3> if the RB has a multiplexing option with transport channel type "DCH + HS-DSCH" for the DL, and both the corresponding DCH transport channel and the corresponding MAC-d flow or MAC-ehs reordering queue are configured, and with transport channel type "DCH" for the UL, and the corresponding DCH transport channel is configured:

4> select this multiplexing option; else

3> if the RB has a multiplexing option with transport channel type "DCH + DSCH" for the DL:

4> the UE behaviour is unspecified; else

3> if the RB has a multiplexing option with transport channel type "HS-DSCH" for the DL, and the corresponding MAC-d flow or MAC-ehs reordering queue is configured, and with transport channel type "E-DCH" for the UL, and the corresponding E-DCH MAC-d flow is configured:

4> select this multiplexing option; else

3> if the RB has a multiplexing option with transport channel type "HS-DSCH" for the DL, and the corresponding MAC-d flow or MAC-ehs reordering queue is configured, and with transport channel type "DCH" for the UL, and the corresponding DCH transport channel is configured:

4> select this multiplexing option; else

3> if the RB has a multiplexing option with transport channel type "DSCH" for the DL:

4> the UE behaviour is unspecified; else

3> if the RB has a multiplexing option with transport channel type "DCH" for the DL, and the corresponding DCH transport channel is configured, and with transport channel type "E-DCH" for the UL, and the corresponding E-DCH MAC-d flow is configured:

4> select this multiplexing option; else

3> if the RB has a multiplexing option with transport channel type "DCH" for the DL, and the corresponding DCH transport channel is configured, and with transport channel type "DCH" for the UL, and the corresponding DCH transport channel is configured:

4> select this multiplexing option.

1> for 3.84 Mcps TDD and 7.68 Mcps TDD, select the multiplexing option according to the following:

2> if the UE is in CELL_FACH state:

3> if the RB has the multiplexing options with the transport channel types "FACH" and "DSCH" for the DL, and the corresponding FACH and DSCH transport channels are configured, and with the transport channel types "RACH" and "USCH" for the UL, and the corresponding RACH and USCH transport channels are configured:

4> if both PUSCH and PDSCH are allocated:

5> select the multiplexing option "DSCH" for DL and "USCH" for UL; else

4> if only PUSCH is allocated:

5> select the multiplexing option "FACH" for DL and "USCH" for UL; else

4> if only PDSCH is allocated:

5> select the multiplexing option "DSCH" for DL and "RACH" for UL; else

4> if neither PUSCH nor PDSCH is allocated:

5> select the multiplexing option "FACH" for DL and "RACH" for UL.

3> if the RB has a single multiplexing option with the transport channel type "FACH" for the DL and the transport channel type "RACH" for the UL:

4> select this multiplexing option; else

3> if the RB has a single multiplexing option with the transport channel type "DSCH" for the DL, and the corresponding DSCH transport channel is configured, and with the transport channel type "USCH" for the UL, and the corresponding USCH transport channel is configured:

4> select this multiplexing option; else

2> if the UE is in CELL_DCH state:

3> if the RB has a multiplexing option with transport channel type "DCH + HS-DSCH" for the DL, and both the corresponding DCH transport channel and MAC-d flow are configured, and with transport channel type "E-DCH" for the UL, and the corresponding E-DCH MAC-d flow is configured:

4> select this multiplexing option; else

3> if the RB has a multiplexing option with transport channel type "DCH + HS-DSCH" for the DL, and both the corresponding DCH transport channel and MAC-d flow are configured, and with transport channel type "DCH" for the UL, and the corresponding DCH transport channel is configured:

4> select this multiplexing option; else

3> if the RB has a multiplexing option with transport channel type "DCH + DSCH" for the DL, and both the corresponding DCH and DSCH transport channels are configured, and with transport channel type "DCH" for the UL, and the corresponding DCH transport channel is configured:

4> select this multiplexing option; else

3> if the RB has a multiplexing option with transport channel type "HS-DSCH" for the DL, and the corresponding MAC-d flow is configured, and with transport channel type "E-DCH" for the UL, and the corresponding E-DCH MAC-d flow is configured:

4> select this multiplexing option; else

3> if the RB has a multiplexing option with transport channel type "HS-DSCH" for the DL, and the corresponding MAC-d flow is configured, and with transport channel type "DCH" for the UL, and the corresponding DCH transport channel is configured:

4> select this multiplexing option; else

3> if theRB has a multiplexing option with transport channel type "DSCH" for the DL, and the corresponding DSCH transport channel is configured, and with transport channel "USCH" for the UL, and the corresponding USCH transport channel is configured:

4> select this multiplexing option.

1> for 1.28 Mcps TDD, select the multiplexing option according to the following:

2> if the UE is in CELL_PCH state:

3> if the UE does support HS-DSCH reception in CELL_PCH and URA_PCH state and IE "HS-DSCH paging system information" is included in System Information Block type 5 and the IE "Common E-DCH system info" is included in System Information Block type 5 and if C-RNTI, H-RNTI and primary E-RNTI are provided to the UE:

4> if the RB has a multiplexing option with transport channel type "HS-DSCH" for the DL and transport channel type "E-DCH" for the UL:

5> select this multiplexing option.

2> if the UE is in CELL_FACH state:

3> if the UE does not support HS-DSCH reception in CELL_FACH state and Enhanced Uplink in CELL_FACH state and Idle mode; or

3> if the IE "HS-DSCH common system information" is not included in System Information Block type 5; or

3> if the IE "Common E-DCH system info" is not included in System Information Block type 5:

4> if the RB has a multiplexing option with transport channel type "FACH" for the DL and transport channel type "RACH" for the UL:

5> select this multiplexing option; else

4> if the RB has the multiplexing options with the transport channel types "FACH" and "DSCH" for the DL, and the corresponding FACH and DSCH transport channels are configured, and with the transport channel types "RACH" and "USCH" for the UL, and the corresponding RACH and USCH transport channels are configured:

5> if both PUSCH and PDSCH are allocated:

6> select the multiplexing option "DSCH" for DL and "USCH" for UL; else

5> if only PUSCH is allocated:

6> select the multiplexing option "FACH" for DL and "USCH" for UL; else

5> if only PDSCH is allocated:

6> select the multiplexing option "DSCH" for DL and "RACH" for UL; else

5> if neither PUSCH nor PDSCH is allocated:

6> select the multiplexing option "FACH" for DL and "RACH" for UL.

4> if the RB has a single multiplexing option with the transport channel type "DSCH" for the DL, and the corresponding DSCH transport channel is configured, and with the transport channel type "USCH" for the UL, and the corresponding USCH transport channel is configured:

5> select this multiplexing option; else

3> else:

4> if the RB has a multiplexing option with transport channel type "HS-DSCH" for the DL and transport channel type "E-DCH" for the UL:

5> select this multiplexing option.

2> if the UE is in CELL_DCH state:

4> select this multiplexing option; else

3> if the RB has a multiplexing option with transport channel type "DCH + HS-DSCH" for the DL, and both the corresponding DCH transport channel and the corresponding MAC-d flow or MAC-ehs reordering queue are configured, and with transport channel type "DCH" for the UL, and the corresponding DCH transport channel is configured:

4> select this multiplexing option; else

3> if the RB has a multiplexing option with transport channel type "HS-DSCH" for the DL, and the corresponding MAC-d flow or MAC-ehs reordering queue is configured, and with transport channel type "DCH" for the UL, and the corresponding DCH transport channel is configured:

4> select this multiplexing option; else

4> select this multiplexing option.

1> configure the MAC with the appropriate transport format set (with computed transport block sizes) for the transport channel used by that RB; or

1> configure the MAC with the appropriate MAC-d flow or MAC-ehs reordering queue used by that RB;

1> in case the selected multiplexing option is a multiplexing option on E-DCH:

2> if the RLC PDU size is set to "fixed size", the set of RLC sizes that apply to the logical channel used by that RB consists of all RLC PDU sizes listed in the IE "RLC PDU size list" in the RB mapping info for E-DCH.

1> else:

2> determine the sets of RLC sizes that apply to the logical channels used by that RB, based on the IEs "RLC size list" and/or the IEs "Logical Channel List" included in the applicable "Transport format set" (either the ones received in the same message or the ones stored if none were received);

1> in case the selected multiplexing option is a multiplexing option on RACH:

2> ignore the RLC size indexes that do not correspond to any RLC size within the Transport Format Set stored for RACH.

2> if there is no remaining RLC size index corresponding to an RLC size within the Transport Format Set stored for RACH:

3> set the variable INVALID_CONFIGURATION to TRUE.

1> if RACH is the transport channel to be used on the uplink, if that RB has a multiplexing option on RACH and if it is using AM:

2> apply the largest size amongst the ones derived according to the previous bullet for the RLC size (or RLC sizes in case the RB is realised using two logical channels) for the corresponding RLC entity.

NOTE: The IE "RB mapping info" is only included in the IE "Predefined RB configurations" in system information when used for Inter-RAT handover to UTRAN and there is no AM RLC size change involved in this case.

1> if the uplink RLC PDU size is set to "flexible size" and no uplink RLC PDU size is currently set in the RLC entity:

2> if this radio bearer is a signalling radio bearer:

3> the UE behaviour is unspecified.

2> else, configure the corresponding RLC entity with the RLC length indicator size indicated in the IE "Length indicator size".

NOTE1: In uplink, if the UTRAN has configured "Flexible size" RLC PDUs and 7-bit "Length indicator size" field and "Largest UL RLC PDU size" > 126 octets, but the UTRAN has not configured "Use special value of HE field", then the UE behaviour is unspecified.

NOTE2: In uplink, if the UTRAN has configured "Flexible size" RLC PDUs and 7-bit "Length indicator size" field, but the UTRAN has also configured "Minimum UL RLC PDU" > 126 octets, then the UE behaviour is unspecified.

1> if the uplink RLC PDU size is changed from "fixed" to "flexible size" and the RLC length indicator size is 7 bits:

2> if this radio bearer is a signalling radio bearer:

3> the UE behaviour is unspecified.

2> else, configure the corresponding RLC entity with flexible RLC PDU size and the RLC length indicator size indicated in the IE "Length indicator size".

1> if that RB is using AM and the RLC size applicable to the uplink logical channel transporting data PDUs is different from the one derived from the previously stored configuration; or

1> if that RB is using AM and the RLC size applicable to the uplink logical channel transporting data PDUs changed from "flexible size" to "fixed size"; or

1> if that RB is using AM and "flexible size" RLC PDUs and the Length Indicator size applicable to the uplink logical channel transporting data PDUs is different from the one derived from the previously stored configuration; or

1> if that RB is using AM and the RLC PDU size applicable to the uplink logical channel transporting data PDUs changed from "fixed size" to "flexible size" and the indicated RLC length indicator size is 15 bits; and

1> none of the following conditions is met:

– the RLC size change is caused by a CELL UPDATE CONFIRM and the CELL UPDATE CONFIRM message includes the IE "Downlink counter synchronisation info".

– the RLC size change is caused by a reconfiguration message, and a cell update procedure occurs during the reconfiguration procedure and the CELL UPDATE CONFIRM message includes the IE "Downlink counter synchronisation info".

– the RLC size change is caused by a reconfiguration message, and a cell update procedure occurs during this reconfiguration procedure and the CELL UPDATE CONFIRM message includes the IE "RLC re-establish indicator" being set to TRUE for the corresponding radio bearer.

2> if the RLC PDU size is set to "flexible size":

3> if this radio bearer is a signalling radio bearer:

4> the UE behaviour is unspecified.

2> if the RLC size change is caused by a reconfiguration message or a CELL UPDATE CONFIRM and the IE "one sided RLC re-establishment" is included in that message and is set to TRUE; or

2> the uplink RLC size change is caused by changing the multiplexing option with transport channel type "E-DCH" to transport channel type "RACH" during cell reselection or due to a system information modification, and the UE enters or remains in CELL_FACH state, or the UE enters CELL_PCH state and the H-RNTI is stored after the state transition into CELL_PCH state, the UE shall after receiving the CELL UPDATE CONFIRM:

3> re-establish the transmitting side of the corresponding RLC entity.

2> else:

3> re-establish the corresponding RLC entity;

3> if the RLC entity for SRB2 is re-established:

4> clear all entries in the table "Processed transactions" in the variable TRANSACTIONS.

2> if the RLC PDU size is set to "fixed size":

3> configure the corresponding RLC entity with the new uplink RLC size.

2> if the RLC PDU size is set to "flexible size":

3> configure the corresponding RLC entity with the RLC length indicator size indicated in the IE "Length indicator size".

2> for each AM RLC radio bearer in the CN domain as indicated in the IE "CN domain identity" in the IE "RAB info" in the variable ESTABLISHED_RABS whose RLC size is changed; and

2> for each AM RLC signalling radio bearer in the CN domain as indicated in the IE "CN domain identity" in the variable LATEST_CONFIGURED_CN_DOMAIN whose RLC size is changed:

3> if the IE "Status" in the variable CIPHERING_STATUS of this CN domain is set to "Started":

4> if the information causing the RLC re-establishment was included in system information:

5> set the HFN values for the corresponding RLC entity equal to the value of the IE "START" for this CN domain that will be included in the CELL UPDATE message following cell reselection.

NOTE: Since the UE cannot predict the START value at the time of the next CELL UPDATE transmission in the future, UTRAN should desist from changing the RLC size for a signalling radio bearer within a cell. Other than this case the change in RLC size for a signalling radio bearer is known to the UE when reading system information following cell reselection.

4> if the RLC re-establishment is caused by a CELL UPDATE CONFIRM:

5> if the whole RLC entity was re-established:

6> set the HFN values for the corresponding RLC entity in uplink and downlink equal to the value of the IE "START" included in the latest transmitted CELL UPDATE message for this CN domain.

5> if only the transmitting side of the RLC entity was re-established:

6> set the HFN value for the corresponding RLC entity in the uplink equal to the value of the IE "START" included in the latest transmitted CELL UPDATE message for this CN domain.

4> if the RLC re-establishment is caused by a reconfiguration message:

5> if the whole RLC entity was re-established:

6> set the HFN values for the corresponding RLC entity in uplink and downlink equal to the value of the IE "START" that will be included in the reconfiguration complete message for this CN domain.

5> if only the transmitting side of the RLC entity was re-established:

6> set the HFN value for the corresponding RLC entity in the direction uplink equal to the value of the IE "START" that will be included in the reconfiguration complete message for this CN domain.

NOTE1: If the UTRAN modifies the RLC size for RB2 on any reconfiguration message or Cell Update Confirm message, the UE behaviour is unspecified in this version of the specification.

NOTE2: The UE cannot rely on the configured Transport Formats to determine the RLC sizes to be used in downlink for a particular logical channel. This size can be signalled explicitly in the RLC Info IE.

1> if that RB is using AM or UM; and

1> MAC-i/is is configured and the RLC PDU size is set to "flexible size":

2> indicate the largest RLC size applicable for uplink to the corresponding RLC entity;

2> indicate the minimum RLC size applicable for the uplink to the corresponding RLC entity.

1> MAC-e/es is configured and the RLC PDU size is set to "flexible size":

2> set the variable INVALID_CONFIGURATION to TRUE.

1> if that RB is using UM and MAC-i/is is not configured:

2> indicate the largest RLC size applicable for uplink to the corresponding RLC entity.

1> configure MAC multiplexing according to the selected multiplexing option (MAC multiplexing shall only be configured for a logical channel if the transport channel it is mapped on according to the selected multiplexing option is the same as the transport channel another logical channel is mapped on according to the multiplexing option selected for it);

1> configure the MAC with the logical channel priorities according to selected multiplexing option;

1> configure the MAC with the set of applicable RLC Sizes for each of the logical channels used for that RB;

1> if there is no multiplexing option applicable for the transport channels, MAC-d flows and MAC-ehs reordering queues to be used:

2> set the variable INVALID_CONFIGURATION to TRUE.

1> if there is more than one multiplexing option applicable for the transport channels, MAC-d flows or MAC-ehs reordering queues to be used:

2> set the variable INVALID_CONFIGURATION to TRUE.

If upon cell re-selection or upon moving to CELL_FACH state from URA_PCH, CELL_PCH or CELL_DCH state to initiate cell update procedure the UE sets variable INVALID_CONFIGURATION to TRUE as a result of the actions defined in this subclause, the UE should:

1> move to idle mode;

1> release (locally) the established signalling connections (as stored in the variable ESTABLISHED_SIGNALLING_CONNECTIONS) and the established radio access bearers (as stored in the variable ESTABLISHED_RABS) and indicate this to upper layers;

1> perform other actions when entering idle mode from connected mode as specified in subclause 8.5.2.