8.6.4 Radio bearer information elements

25.3313GPPProtocol specificationRadio Resource Control (RRC)Release 17TS

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

8.6.4.1 Signalling RB information to setup list

If the IE "Signalling RB information to setup list" is included the UE shall:

1> use the same START value to initialise the COUNT-C and COUNT-I variables for all the signalling radio bearers in the list;

1> if the IE "Signalling RB information to setup list" was included in the RADIO BEARER SETUP message:

2> if the variable LATEST_CONFIGURED_CN_DOMAIN has been initialised:

3> calculate the START value only once during this procedure according to subclause 8.5.9 for the CN domain indicated in the variable LATEST_CONFIGURED_CN_DOMAIN;

3> store the calculated START value in the variable START_VALUE_TO_TRANSMIT.

1> for each occurrence of the IE "Signalling RB information to setup":

2> use the value of the IE "RB identity" as the identity of the signalling radio bearer to setup;

2> if the signalling radio bearer identified with the IE "RB identity" does not exist in the variable ESTABLISHED_RABS:

3> create a new entry for the signalling radio bearer in the variable ESTABLISHED_RABS.

2> if the IE "Signalling RB information to setup list" was received in a message other than HANDOVER TO UTRAN COMMAND; and

2> if the variable LATEST_CONFIGURED_CN_DOMAIN has been initialised and the value "STATUS" of the variable CIPHERING_STATUS of the CN domain stored in this variable is "Started":

3> if the IE "Uplink RLC mode" or the IE "Downlink RLC mode" either in the IE "RLC info" or referenced by the RB identity in the IE "Same as RB" is set to "AM RLC" or "UM RLC":

4> initialise the 20 MSB of the hyper frame number component of COUNT-C for this signalling radio bearer with the START value in the variable START_VALUE_TO_TRANSMIT;

4> set the remaining LSB of the hyper frame number component of COUNT-C for this signalling radio bearer to zero;

4> start to perform ciphering on this signalling radio bearer, using the value of the IE "RB identity" minus one as the value of BEARER in the ciphering algorithm.

2> if the IE "Signalling RB information to setup list" was received in a message other than HANDOVER TO UTRAN COMMAND; and

2> if the variable LATEST_CONFIGURED_CN_DOMAIN has been initialised and the value "Status" of the variable "INTEGRITY_PROTECTION_INFO" of the CN domain stored in this variable is "Started":

3> initialise the 20 MSB of the hyper frame number component of COUNT-I for this signalling radio bearer with the START value in the variable START_VALUE_TO_TRANSMIT;

3> set the remaining LSB of the hyper frame number component of COUNT-I for this signalling radio bearer to zero;

3> for this signalling radio bearer, set the IE "Uplink RRC Message sequence number" in the variable INTEGRITY_PROTECTION_INFO to zero;

3> start performing integrity protection according to subclauses 8.5.10.1 and 8.5.10.2.

2> perform the actions for the IE "RLC info" as specified in subclause 8.6.4.9, applied for that signalling radio bearer;

2> perform the actions for the IE "RB mapping info" as specified in subclause 8.6.4.8, applied for that signalling radio bearer.

1> apply a default value of the IE "RB identity" equal to 1 for the first IE "Signalling RB information to setup"; and

1> increase the default value by 1 for each occurrence.

NOTE: The UTRAN should only use the default value of the IE "RB identity" within the RRC Connection Setup and Handover to UTRAN Command messages. If the default value of the IE "RB identity" is used in any other message then the UE behaviour is not specified.

8.6.4.2 RAB information for setup

If the IE "RAB information for setup" is included, the procedure is used to establish or establish/release (only if CS domain RAB mapping is reconfigured between DCH and EDCH/HSPA or IE "RAB info to replace" exists) radio bearers belonging to a radio access bearer, and the UE shall:

1> if several IEs "RAB information for setup" are included in a message other than HANDOVER TO UTRAN COMMAND and the included IEs "CN domain identity" in the IE "RAB info" does not all have the same value:

2> set the variable INVALID_CONFIGURATION to TRUE.

1> if the radio access bearer identified with the IE "RAB info" does not exist in the variable ESTABLISHED_RABS:

2> create a new entry for the radio access bearer in the variable ESTABLISHED_RABS;

2> store the content of the IE "RAB info" in the entry for the radio access bearer in the variable ESTABLISHED_RABS;

2> indicate the establishment of each radio access bearer to the upper layer entity using the IE "CN domain identity", forwarding the content of the IE "RAB identity" and the IEs NAS Synchronization Indicator as well as the following IEs if included in the IE "RAB info": "MBMS Session identity" and/ or "MBMS Service Identity";

2> if prior to this procedure there exists no transparent mode radio bearer for the CN domain included in the IE "CN domain identity" and at least one transparent mode radio bearer is included in the IE "RB information to setup"; or

2> if at least one RLC-AM or RLC-UM radio bearer is included in the IE "RB information to setup":

3> calculate the START value only once during this procedure (the same START value shall be used on all new radio bearers created for this radio access bearer) according to subclause 8.5.9 for the CN domain as indicated in the IE "CN domain identity" in the IE "RAB info" part of the IE "RAB information to setup";

NOTE: For the case of SR-VCC the START value from the mapped CS key will be incremented and compared with the START value read from the (U)SIM at connection setup. The largest value will be used for the new CS START value. For the case of rSR-VCC the START value from the mapped PS key will be incremented and compared with the START value read from the (U)SIM at connection setup. The largest value will be used for the new PS START value. This operation is provided with the existing procedure in subclause 8.5.9.

3> store the calculated START value in the variable START_VALUE_TO_TRANSMIT.

1> if the radio access bearer identified with the IE "RAB identity" in the IE "RAB info" already exists in the variable ESTABLISHED_RABS:

2> if at least one RLC-AM or RLC-UM radio bearer is included in the IE "RB information to setup":

3> store the calculated START value in the variable START_VALUE_TO_TRANSMIT.

2> for each radio bearer in the variable ESTABLISHED_RABS for that radio access bearer:

3> release the PDCP and RLC entities for that radio bearer;

3> release the RAB subflow associated with the radio bearer;

3> delete the information about the radio bearer from the variable ESTABLISHED_RABS.

NOTE: When CS domain RAB mapping is reconfigured between DCH and E-DCH/HS-DSCH, UTRAN should change the radio bearer identity.

1> if the radio access bearer identified with the IE "RAB info to replace" already exists in the variable ESTABLISHED_RABS:

2> for each radio bearer in the variable ESTABLISHED_RABS for that radio access bearer:

3> release the PDCP and RLC entities for that radio bearer;

3> release the RAB subflow associated with the radio bearer;

3> delete the information about the radio bearer from the variable ESTABLISHED_RABS.

NOTE: When an SR-VCC procedure is initiated, if the received reconfiguration message attempts to configure RBs with the same RB Identity as an existing or about to be released radio bearer identity, the UE behaviour is not specified.

2> indicate to the upper layers that the radio access bearer identified by the IE "RAB info to replace" is released as part of a SR-VCC procedure.

1> for each radio bearer in the IE "RB information to setup":

2> if the radio bearer identified with the IE "RB identity" does not exist in the variable ESTABLISHED_RABS:

3> perform the actions specified in subclause 8.6.4.3;

3> store information about the new radio bearer in the entry for the radio access bearer identified by "RAB info" in the variable ESTABLISHED_RABS;

3> create a new RAB subflow for the radio access bearer;

3> number the RAB subflow in ascending order, assigning the smallest number to the RAB subflow corresponding to the first radio bearer in the list;

3> if the IE "CN domain identity" in the IE "RAB info" is set to "PS domain" and the number of RAB subflows for the radio access bearer is greater than 1:

4> set the variable INVALID_CONFIGURATION to TRUE.

2> if the radio bearer identified with the IE "RB identity" already exists in the variable ESTABLISHED_RABS:

3> set the variable INVALID_CONFIGURATION to TRUE.

1> if the IE "CS-HSPA information" is included:

2> forward the content of the IE "UL AMR rate" to upper layers;

2> use the information in the IE "Max CS delay" to determine the maximum buffering of the voice frames (see [36]).

8.6.4.2a RAB information to reconfigure

If the IE "RAB information to reconfigure" is included then the UE shall:

1> if the entry for the radio access bearer identified by the IE "CN domain identity" together with the IE "RAB Identity" in the variable ESTABLISHED_RABS already exists:

2> perform the action for the IE "NAS Synchronization Indicator", according to subclause 8.6.4.12.

1> else:

2> set the variable INVALID_CONFIGURATION to TRUE.

1> if the IE "CS-HSPA information" is included:

2> forward the content of the IE "UL AMR rate" to upper layers;

2> use the information in the IE "Max CS delay" to determine the maximum buffering of the voice frames (see [36]).

8.6.4.3 RB information to setup

If the IE "RB information to setup" is included, the UE shall apply the following actions on the radio bearer identified with the value of the IE "RB identity". The UE shall:

1> use the same START value to initialise the hyper frame number components of COUNT-C variables for all the new radio bearers to setup;

1> perform the actions for the IE "PDCP info", if present, according to subclause 8.6.4.10, applied for the radio bearer;

1> perform the actions for the IE "RLC info", according to subclause 8.6.4.9, applied for the radio bearer;

1> perform the actions for the IE "RB mapping info", according to subclause 8.6.4.8, applied for the radio bearer;

1> if the IE "Downlink RLC mode" either in the IE "RLC info" or referenced by the RB identity in the IE "Same as RB" is set to "TM RLC":

2> configure delivery of erroneous SDUs in lower layers according to indication from upper layer [5].

1> if the IE "Downlink RLC mode" either in the IE "RLC info" or referenced by the RB identity in the IE "Same as RB" is set to "UM RLC" and if the radio bearer is connected to a CS domain radio access bearer:

2> configure delivery of RLC sequence number in lower layers;

2> if the IE "RB information to setup" was received in a message other than HANDOVER TO UTRAN COMMAND:

3> if the IE "SR-VCC Info" is present and contains the IE "NONCE":

4> initialise the 20 MSB of the hyper frame number component of COUNT-C for this radio bearer (including uplink and downlink) with zero for CS domain;

3> else:

4> initialise the 20 MSB of the hyper frame number component of COUNT-C for this radio bearer (including uplink and downlink) with the latest transmitted START for CS domain;

3> set the remaining LSB of the hyper frame number component of COUNT-C for this radio bearer (including uplink and downlink) to zero;

3> start incrementing the COUNT-C values.

1> else if the IE "RB information to setup" was received in a message other than HANDOVER TO UTRAN COMMAND; and

1> if the IE "Uplink RLC mode" or the IE "Downlink RLC mode" either in the IE "RLC info" or referenced by the RB identity in the IE "Same as RB" is set to "AM RLC" or "UM RLC":

2> initialise the 20 MSB of the hyper frame number component of COUNT-C for this radio bearer with the START value in the variable START_VALUE_TO_TRANSMIT;

2> set the remaining LSB of the hyper frame number component of COUNT-C for this radio bearer to zero;

2> start incrementing the COUNT-C values.

1> if the IE "RB information to setup" was received in a message other than HANDOVER TO UTRAN COMMAND; and

1> if the IE "Uplink RLC mode" and the IE "Downlink RLC mode" either in the IE "RLC info" or referenced by the RB identity in the IE "Same as RB" is set to "TM RLC":

2> if prior to this procedure there exists no transparent mode radio bearer for the CN domain included in the IE "CN domain identity" in the IE "RAB info" in the variable ESTABLISHED_RABS and at least one transparent mode radio bearer is included in the IE "RB information to setup":

3> if the IE "Status" in the variable CIPHERING_STATUS of the CN domain as indicated in the IE "CN domain identity" in the IE "RAB info" in the variable ESTABLISHED_RABS is set to "Not Started":

4> at the activation time as specified in the IE "Ciphering activation time for DPCH" if included in the IE "Ciphering mode info" in the command message or, if this IE is not included, as specified in the IE "COUNT-C activation time" included in the response message:

5> initialise the 20 most significant bits of the hyper frame number component of COUNT-C common for all transparent mode radio bearers of this CN domain with the START value in the variable START_VALUE_TO_TRANSMIT;

5> set the remaining LSB of the hyper frame number component of COUNT-C to zero;

5> do not increment the COUNT-C value common for all transparent mode radio bearers for this CN domain.

3> if the IE "Status" in the variable CIPHERING_STATUS of the CN domain as indicated in the IE "CN domain identity" in the IE "RAB info" in the variable ESTABLISHED_RABS is set to " Started":

4> at the activation time as specified in the IE "Activation Time" in the RADIO BEARER SETUP message:

5> if the IE "CN domain identity" in the "IE RAB info" is set to CS; and

5> if the IE "SR-VCC Info" is present and contains the IE "NONCE":

6> initialise the 20 most significant bits of the HFN component of COUNT-C common for all transparent mode RLC radio bearers to zero.

5> otherwise:

6> initialise the 20 most significant bits of the HFN component of COUNT-C common for all transparent mode RLC radio bearer to the value of the latest transmitted START for this CN domain.

5> while not incrementing the value of the HFN component of COUNT-C at each CFN cycle; and

5> set the remaining LSB of the HFN component of COUNT-C to zero;

5> start to perform ciphering on the radio bearer in lower layers while not incrementing the HFN.

5> initialise the 20 most significant bits of the HFN component of COUNT-C common for all transparent mode radio bearers of this CN domain with the START value in the variable START_VALUE_TO_TRANSMIT;

5> set the remaining LSB of the HFN component of COUNT-C to zero;

5> if the received message is used to perform a Timing re-initialised hard handover:

6> increment the HFN component of the COUNT-C variable by one even if the "COUNT-C activation time" is set to zero.

5> start incrementing the COUNT-C value common for all transparent mode radio bearers of this CN domain as normal, at each CFN value, i.e. the HFN component is no longer fixed in value but incremented at each CFN cycle.

2> if prior to this procedure there exists at least one transparent mode radio bearer for the CN domain included in the IE "CN domain identity" in the IE "RAB info" in the variable ESTABLISHED_RABS:

3> if the IE "Status" in the variable CIPHERING_STATUS of the CN domain as indicated in the IE "CN domain identity" in the IE "RAB info" in the variable ESTABLISHED_RABS is set to "Not Started":

4> do not increment the COUNT-C value common for all transparent mode radio bearers for this CN domain.

3> if the IE "Status" in the variable CIPHERING_STATUS of the CN domain as indicated in the IE "CN domain identity" in the IE "RAB info" in the variable ESTABLISHED_RABS is set to "Started":

4> use the COUNT-C value common for all transparent mode radio bearers of this CN domain.

1> if the IE "Status" in the variable CIPHERING_STATUS of the CN domain as indicated in the IE "CN domain identity" in the IE "RAB info" in the variable ESTABLISHED_RABS is set to "Started":

2> start to perform ciphering on the radio bearer in lower layers, using the value of the IE "RB identity" minus one as the value of BEARER in the ciphering algorithm.

NOTE: UTRAN should not use the IE "RB information to setup" to setup radio bearers with RB identity in the range 1-4.

8.6.4.4 RB information to be affected

If the IE "RB information to be affected" is included, the UE shall apply the following actions on the radio bearer identified with the value of the IE "RB identity". The UE shall:

1> perform the actions for the IE "RB mapping info", according to subclause 8.6.4.8, applied for the radio bearer.

8.6.4.4a Void

8.6.4.5 RB information to reconfigure

If the IE "RB information to reconfigure" is included, the UE shall apply the following actions on the radio bearer identified with the value of the IE "RB identity". The UE shall:

1> perform the actions for the IE "PDCP info", if present, according to subclause 8.6.4.10, applied for the radio bearer;

1> if the IE "RLC info" is present:

2> perform the actions for the IE "RLC info", according to subclause 8.6.4.9, applied for the radio bearer.

1> else:

2> continue using the current RLC configuration for the radio bearer.

1> perform the actions for the IE "RB mapping info", according to subclause 8.6.4.8, applied for the radio bearer;

1> if the IE "Downlink RLC mode" in the IE "RLC info" is set to "TM RLC":

2> configure delivery of erroneous SDUs in lower layers according to indication from upper layer [5].

1> if the IE "PDCP SN info" is included:

2> perform the actions as specified in subclause 8.6.4.11 applied for the radio bearer.

1> if the IE "RB stop/continue" is included; and

2> if the "RB identity" has a value greater than 2; and

3> if the value of the IE "RB stop/continue" is "stop":

4> configure the RLC entity for the radio bearer to stop;

4> set the IE "RB started" in the variable ESTABLISHED_RABS to "stopped" for that radio bearer.

3> if the value of the IE "RB stop/continue" is "continue":

4> configure the RLC entity for the radio bearer to continue;

4> set the IE "RB started" in the variable ESTABLISHED_RABS to "started" for that radio bearer.

2> if the IE "RB identity" is set to a value less than or equal to 2:

3> set the variable INVALID_CONFIGURATION to TRUE.

8.6.4.6 RB information to release

If the IE "RB information to release" is included, the UE shall apply the following actions on the radio bearer identified with the value of the IE "RB identity". The UE shall:

1> if the IE "RB identity" is set to a value less than 4:

2> set the variable INVALID_CONFIGURATION to TRUE.

1> if the IE "RB identity" refers to a signalling radio bearer:

2> release the RLC entity for the signalling radio bearer;

2> delete the information about the signalling radio bearer from the variable ESTABLISHED_RABS.

1> if the IE "RB identity" refers to a radio bearer:

2> release the PDCP and RLC entities for that radio bearer;

2> indicate release of the RAB subflow associated with the radio bearer to upper layers;

2> delete the information about the radio bearer from the variable ESTABLISHED_RABS;

2> when all radio bearers belonging to the same radio access bearer have been released:

3> indicate release of the radio access bearer to upper layers providing the "CN domain identity" together with the "RAB identity" and the "MBMS Service Identity" if stored in the variable ESTABLISHED_RABS;

3> delete all information about the radio access bearer from the variable ESTABLISHED_RABS.

The UE shall:

1> determine the value for the HS_DSCH_RECEPTION variable and take the corresponding actions as described in subclause 8.5.25;

1> determine the value for the E_DCH_TRANSMISSION variable and take the corresponding actions as described in subclause 8.5.28.

8.6.4.7 RB with PDCP information

If the IE "RB with PDCP information" is included, the UE shall apply the following actions on the radio bearer identified with the value of the IE "RB identity". The UE shall:

1> for the IE "PDCP SN info":

2> perform the actions as specified in subclause 8.6.4.11.

8.6.4.8 RB mapping info

If the IE "RB mapping info" is included, the UE shall:

1> for each multiplexing option of the RB:

2> if a multiplexing option that maps a logical channel corresponding to a TM-RLC entity onto RACH, FACH, USCH, DSCH (only for TDD), HS-DSCH or E-DCH is included:

3> set the variable INVALID_CONFIGURATION to TRUE.

2> if the multiplexing option realises the radio bearer on the uplink (resp. on the downlink) using two logical channels with different values of the IE "Uplink transport channel type" (resp. of the IE "Downlink transport channel type"):

3> set the variable INVALID_CONFIGURATION to TRUE.

2> if that RB is using TM and the IE "Segmentation indication" is set to TRUE and, based on the multiplexing configuration resulting from this message, the logical channel corresponding to it is mapped onto the same transport channel as another logical channel:

3> set the variable INVALID_CONFIGURATION to TRUE.

2> if the transport channel considered in that multiplexing option is different from RACH and if that RB is using AM and the set of RLC sizes applicable to the uplink logical channel transferring data PDUs has more than one element not equal to zero:

3> set the variable INVALID_CONFIGURATION to TRUE.

2> if that RB is using UM or TM and the multiplexing option realises it using two logical channels:

3> set the variable INVALID_CONFIGURATION to TRUE.

2> for each logical channel in that multiplexing option:

3> if the value of the IE "RLC size list" is set to "Explicit list":

4> if a "Transport format set" for the transport channel this logical channel is mapped on in this multiplexing option is included in the same message, and the value (index) of any IE "RLC size index" in the IE "Explicit list" does not correspond to an "RLC size" in the IE transport format set of that transport channel given in the message; or

4> if the transport channel this logical channel is mapped on in this multiplexing option is different from RACH, and if a "Transport format set" for that transport channel is not included in the same message, and the value (index) of any IE "RLC size index" in the IE "Explicit list" does not correspond to an "RLC size" in the stored transport format set of that transport channel; or

4> if a "Transport format set" for the transport channel this logical channel is mapped on in this multiplexing option is included in the same message, and the value of any IE "Logical channel list" in the transport format set is not set to "Configured"; or

4> if a "Transport format set" for the transport channel this logical channel is mapped on in this multiplexing option is not included in the same message, and the value of any IE "Logical channel list" in the stored transport format set of that transport channel is not set to "Configured":

5> set the variable INVALID_CONFIGURATION to TRUE.

3> if the value of the IE "RLC size list" is set to "All":

4> if the transport channel this logical channel is mapped on is RACH; or

5> set the variable INVALID_CONFIGURATION to TRUE.

3> if the value of the IE "RLC size list" is set to "Configured":

4> if the transport channel this logical channel is mapped on is RACH; or

4> if a "Transport format set" for the transport channel this logical channel is mapped on in this multiplexing option is included in the same message, and for none of the RLC sizes defined for that transport channel in the "Transport format set", the "Logical Channel List" is set to "All" or given as an "Explicit List" which contains this logical channel; or

4> if a "Transport format set" for the transport channel this logical channel is mapped on in this multiplexing option is not included in the same message, and for none of the RLC sizes defined in the transport format set stored for that transport channel, the "Logical Channel List" is set to "All" or given as an "Explicit List" which contains this logical channel:

5> set the variable INVALID_CONFIGURATION to TRUE.

1> if, for the HS-DSCH transport channel, when MAC-hs is configured and as a result of the message this IE is included in, several radio bearers can be mapped onto the same MAC-d flow, and the IE "Logical Channel Identity" was not included in the RB mapping info of any of those radio bearers for a multiplexing option on that MAC-d flow or the same "Logical Channel Identity" was used more than once in the RB mapping info of those radio bearers for the multiplexing options on that MAC-d flow:

2> the UE behaviour is not specified.

1> if, for the HS-DSCH transport channel, when MAC-ehs is configured and as a result of the message this IE is included in, several radio bearers can be mapped onto the reordering queue(s), and the IE "Logical Channel Identity" was not included in the RB mapping info of any of those radio bearers for a multiplexing option on at least one reordering queue or the same "Logical Channel Identity" was used more than once in the RB mapping info of those radio bearers for the multiplexing options on any reordering queue:

2> the UE behaviour is not specified.

1> if, as a result of the message this IE is included in, several radio bearers can be mapped onto the E-DCH MAC-d flows(s), and the IE "Logical Channel Identity" was not included in the RB mapping info of any of those radio bearers for a multiplexing option on at least one E-DCH MAC-d flow or the same "Logical Channel Identity" was used more than once in the RB mapping info of those radio bearers for the multiplexing options on any MAC-d flow:

2> the UE behaviour is not specified.

1> if, for transport channels other than HS-DSCH and E-DCH, as a result of the message this IE is included in, several radio bearers can be mapped onto the same transport channel, and the IE "Logical Channel Identity" was not included in the RB mapping info of any of those radio bearers for a multiplexing option on that transport channel or the same "Logical Channel Identity" was used more than once in the RB mapping info of those radio bearers for the multiplexing options on that transport channel:

2> set the variable INVALID_CONFIGURATION to TRUE.

1> if, as a result of the message this IE is included in, there are several radio bearers configured with a multiplexing option mapped on "HS-DSCH", i.e., a downlink transport channel of type "HS-DSCH" or "DCH + HS-DSCH", and there is at least one radio bearer with a multiplexing option configured with the DL MAC header type set to "MAC-hs" and at least one radio bearer with a multiplexing option configured with the DL MAC header type set to "MAC-ehs":

2> set the variable INVALID_CONFIGURATION to TRUE.

1> if the "RB mapping info" is considered as valid according to the rules above:

2> delete all previously stored multiplexing options for that radio bearer;

2> store each new multiplexing option for that radio bearer;

2> perform the actions as specified in subclause 8.5.21;

2> determine the value for the HS_DSCH_RECEPTION variable and take the corresponding actions as described in subclause 8.5.25;

2> determine the value for the E_DCH_TRANSMISSION variable and take the corresponding actions as described in subclause 8.5.28.

1> if the IE "Uplink transport channel type" is set to the value "RACH":

2> in FDD:

3> refer the IE "RLC size index" to the RACH Transport Format Set of the first PRACH received in the IE "PRACH system information list" received in System Information Block 5, System Information Block 5bis or System Information Block 6.

2> in TDD:

3> use the first Transport Format of the PRACH of the IE "PRACH system information list" at the position equal to the value in the IE "RLC size index".

1> if the IE "Downlink transport channel type" is set to the value "HS-DSCH" or "DCH + HS-DSCH";and

1> the DL MAC header type is set to "MAC-ehs":

2> if the IE "Logical channel identity" is present:

3> configure the receiving MAC-ehs entity with the value of the IE "Logical channel identity" to be used in the "LCH-ID" field of the MAC-ehs header [15] associated with the MAC-ehs reordering queue identified by the value of the IE "DL HS-DSCH MAC-ehs Queue Id".

2> else:

3> set the variable INVALID_CONFIGURATION to TRUE.

In case IE "RLC info" includes IE "Downlink RLC mode" ("DL RLC logical channel info" is mandatory present) but IE "Number of downlink RLC logical channels" is absent in the corresponding IE "RB mapping info", the parameter values are exactly the same as for the corresponding UL logical channels. In case two multiplexing options are specified for the UL, the first options shall be used as default for the DL. As regards the IE "Channel type", the following rule should be applied to derive the DL channel type from the UL channel included in the IE:

Channel used in UL	DL channel type implied by "same as"
DCH	DCH
RACH	FACH
USCH	DSCH

If ciphering is applied, UTRAN should not map Transparent Mode RBs of different CN domains on the same transport channel and it should not map transparent mode SRBs and RBs onto the same transport channel. In such cases the UE behaviour is not specified.

For FDD the list of multiplexing options configured in the UE for each RB and SRB should comply with the following rules otherwise the UE behaviour is not specified:

– at most one multiplexing option can contain the combination "FACH" for the DL and "RACH" for the UL;

– for FDD, at most one multiplexing option can contain the combination "HS-DSCH" mapped on MAC-ehs for the DL and "RACH" for the UL;

– at most one multiplexing option can contain the combination "DCH" or "DCH + HS-DSCH" for the DL together with "DCH" for he UL;

– at most one multiplexing option can contain the combination "HS-DSCH" or "DCH + HS-DSCH" for the DL together with "DCH" for the UL;

– at most one multiplexing option can contain the combination "DCH" or "DCH + HS-DSCH" for the DL together with "E-DCH" for the UL; and

– at most one multiplexing option can contain the combination "HS-DSCH" or "DCH + HS-DSCH" for the DL together with "E-DCH" for the UL.

8.6.4.9 RLC Info

Upon reception of the IE "RLC Info", the UE shall:

1> if both the IE "Uplink RLC mode" and the IE "Downlink RLC mode" are present in the IE "RLC info":

2> configure the transmitting and receiving RLC entities in the UE for that radio bearer accordingly.

1> else, if the IE "Uplink RLC mode" is present and the IE "Downlink RLC mode" is not present in the IE "RLC info":

2> configure the transmitting RLC entity in the UE for that radio bearer accordingly and keep the configuration existing before the reception of the message for the receiving RLC entity.

1> else, if the IE "Uplink RLC mode" is not present and the IE "Downlink RLC mode" is present in the IE "RLC info":

2> configure the receiving RLC entity in the UE for that radio bearer accordingly and keep the configuration existing before the reception of the message for the transmitting RLC entity.

1> if the IE "Polling info" is present in the IE "RLC info":

2> for each present IE in the IE "Polling info":

3> configure RLC to use the corresponding function according to the value of the IE.

2> for each absent IE in the IE "Polling info":

3> configure RLC to not use the corresponding function.

1> if the IE "Polling info" is absent:

2> configure RLC to not use the polling functionality.

1> if the IE "Downlink RLC STATUS info" is present in the IE "RLC info" (this IE is present for AM RLC):

2> for each present IE in the IE "Downlink RLC STATUS info":

3> configure RLC to use the corresponding function according to value of the IE.

2> for each absent IE in the IE "Downlink RLC STATUS info":

3> configure RLC to not use the corresponding function.

1> if the IE "Transmission RLC discard" is present:

2> configure the discard procedure in RLC according to the IE "Transmission RLC discard".

1> if the IE "Transmission RLC discard" is absent (only possible for TM RLC and UM RLC):

2> do not configure SDU discard in RLC.

1> if the IE "Uplink RLC mode" is present and is set to "AM RLC":

2> if the IE "Use special value of HE field" is present:

3> configure the uplink RLC entity to use the special value of the HE field to indicate the end of an SDU.

2> if the IE "Use special value of HE field" is not present:

3> configure the uplink RLC entity to not use the special value of the HE field to indicate the end of an SDU.

1> if the IE "Uplink RLC mode" is present and is set to "UM RLC":

2> if the IE "Alternative E-bit interpretation" is present:

3> configure the uplink RLC entity to use the alternative E-bit interpretation and corresponding LI’s.

2> if the IE "Alternative E-bit interpretation" is not present:

3> configure the uplink RLC entity to use the normal E-bit interpretation and corresponding LI’s.

1> if the IE "Downlink RLC mode" is present and is set to "AM RLC":

2> if IE "DL RLC PDU size" is not present:

3> determining the downlink RLC PDU size will be handled at RLC level as described in [16], without any configuration from RRC.

NOTE: The case where this mandatory IE is not present is meant to handle the interaction with a network using an earlier release of the specification.

2> else, if the IE "DL RLC PDU size" is present, the DL RLC PDU size is set to "fixed size" and no downlink RLC PDU size is currently set in the RLC entity:

3> configure the corresponding RLC entity with the downlink RLC PDU size.

2> else, if the DL RLC PDU size is set to "flexible size" and no downlink RLC PDU size is currently set in the RLC entity:

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

4> the UE behaviour is unspecified.

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

2> else, if the DL RLC PDU size is changed to "flexible size" from "fixed size" and the indicated RLC length indicator size is 7 bits:

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

4> the UE behaviour is unspecified.

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

2> else, if the IE "DL RLC PDU size" is present, the DL RLC PDU size is set to "fixed size" and DL RLC PDU size value is different from the one currently set in the RLC entity; or

2> the DL RLC PDU size is set to "flexible size" and the indicated RLC length indicator size is different from the one currently set in the RLC entity; or

2> the DL RLC PDU size is changed to "fixed size" from "flexible size"; or

2> the DL RLC PDU size is changed to "flexible size" from "fixed size" and the indicated RLC length indicator size is 15 bits:

NOTE: The downlink RLC PDU size set in the RLC entity should be explicitly configured in this release of the specification.

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

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

5> the UE behaviour is unspecified.

3> if the IE "one sided RLC re-establishment" is set to TRUE:

4> re-establish the receiving side of the corresponding RLC entity.

3> else:

4> 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.

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

4> configure the corresponding RLC entity with the new downlink RLC PDU size.

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

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

3> if the UE supports the lossless DL RLC PDU size change and PDCP was configured for that radio bearer with the IE "Support for lossless SRNS relocation or for lossless DL RLC PDU size change" set to TRUE:

4> include the current DL PDCP receive sequence number and the radio bearer identity for that radio bearer in the variable PDCP_SN_INFO.

3> if the IE "Status" in the variable CIPHERING_STATUS of the CN domain as indicated in the IE "CN domain identity" in the IE "RAB info" for this radio bearer is set to "Started":

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

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

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

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.

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

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

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

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.

2> if the UE supports MAC-ehs:

3> configure the downlink RLC entity to use the special value of the HE field to indicate the end of an SDU.

2> else:

3> configure the downlink RLC entity to not use the special value of the HE field to indicate the end of an SDU.

1> if the IE "Downlink RLC mode" is present and is set to "UM RLC":

2> if the IE "DL UM RLC LI size" is not present:

3> configure the corresponding RLC entity with an LI size of 7 bits.

NOTE: The case where this mandatory IE is not present is meant to handle the interaction with a network using an earlier release of the specification.

2> else:

3> configure the corresponding RLC entity with the LI size indicated in the IE "DL UM RLC LI size".

2> if the IE "DL Reception Window Size" is present:

3> if the variable UE_CAPABILITY_TRANSFERRED indicates "Support of HS-PDSCH" as "Supported":

4> configure the corresponding RLC entity to support out-of-sequence reception with the receive window size indicated in the IE.

3> if the variable UE_CAPABILITY_TRANSFERRED indicates "Support of HS-PDSCH" as "Unsupported":

4> the UE behaviour is not specified.

2> else:

3> configure the corresponding RLC entity without out-of-sequence reception.

NOTE: If the "Uplink RLC mode" or the "Downlink RLC mode" of an existing radio bearer is modified by a reconfiguration message, the UE behaviour is unspecified.

2> if the IE "Alternative E-bit interpretation" is present:

3> configure the downlink RLC entity to use the alternative E-bit interpretation and corresponding LI’s.

2> if the IE "Alternative E-bit interpretation" is not present:

3> configure the downlink RLC entity to use the normal E-bit interpretation and corresponding LI’s.

8.6.4.10 PDCP Info

For ROHC, as specified in [83] and [84]:

1> the chosen MAX_CID shall be less than the value "Maximum number of ROHC context sessions" as indicated in the IE "PDCP Capability".

If IE "PDCP info" is included, the UE shall:

1> if the radio bearer is connected to a CS domain radio access bearer:

2> if the IE "PDCP info" is included in any other message than the RADIO BEARER SETUP, CELL UPDATE CONFIRM or the HANDOVER TO UTRAN COMMAND message; or

2> if the IE "PDCP PDU header" is set to the value "absent"; or

2> if the IE "Support for lossless SRNS relocation or for lossless DL RLC PDU size change" is set to TRUE; or

2> if the IE "Header compression information" is present; or

2> if the UE does not support CS voice service over HSDPA and EDCH:

3> set the variable INVALID_CONFIGURATION to TRUE.

2> else

3> include PDCP headers in both uplink and downlink PDCP PDUs.

3> configure "PDCP Unrecoverable Error Detection" in lower layer.

1> else if the radio bearer is connected to a PS domain radio access bearer:

2> if the IE "PDCP PDU header" is set to the value "absent":

3> if the IE "Support for lossless SRNS relocation or for lossless DL RLC PDU size change" is TRUE:

4> set the variable INVALID_CONFIGURATION to TRUE.

2> if the IE "PDCP PDU header" is set to the value "present":

3> include PDCP headers in both uplink and downlink PDCP PDUs;

3> if the IE "Support for lossless SRNS relocation or for lossless DL RLC PDU size change" is FALSE:

4> if the IE "Header compression information" is absent:

5> set the variable INVALID_CONFIGURATION to TRUE.

2> if the IE "Header compression information" is absent:

3> not use Header compression after the successful completion of this procedure;

3> remove any stored configuration for the IE "Header compression information".

2> if the IE "Header compression information" is present:

3> if the IE "Algorithm Type" is set to "RFC 2507":

4> if the UE capability "Maximum header compression context space", as specified in [35], is exceeded with this configuration:

5> set the variable INVALID_CONFIGURATION to TRUE.

4> if the IE "PDCP PDU header" is set to the value "absent":

5> the behaviour of the UE is unspecified.

3> if the IE "Algorithm Type" is set to "RFC 3095":

4> if the uplink RLC mode for this radio bearer is RLC-TM:

5> the behaviour of the UE is unspecified.

1> configure the PDCP entity for that radio bearer accordingly;

1> configure the RLC entity for that radio bearer according to the value of the IE "Support for lossless SRNS relocation or for lossless DL RLC PDU size change";

1> set the PROFILES parameter, used by inband ROHC profile negotiation, for this PDCP entity for both UL and DL equal to the list of ROHC profiles received in the IE "PDCP info". A UE complying to this version of the protocol shall support ROHC profiles 0x0000 (ROHC uncompressed), 0x0001 (ROHC RTP), 0x0002 (ROHC UDP) and 0x0003 (ROHC ESP) (see [52]).

1> if the IE "PDCP ROHC target mode" is received:

2> set the variable " PDCP_ROHC_TARGET_MODE " to the received value.

1> if the IE "PDCP ROHC target mode" is not received in either of the CELL UPDATE CONFIRM, the RADIO BEARER RECONFIGURATION or the RADIO BEARER SETUP message:

2> delete the variable "PDCD_ROHC_TARGET_MODE" and act according to actions specified in [36].

8.6.4.11 PDCP SN Info

If the IE "PDCP SN Info" is included, the UE shall:

1> transfer the sequence number to the PDCP entity for the radio bearer;

1> configure the RLC entity for the radio bearer to stop;

1> include the current PDCP receive sequence number and the radio bearer identity for the radio bearer in the variable PDCP_SN_INFO.

8.6.4.12 NAS Synchronisation Indicator

If the IE "NAS Synchronisation Indicator" is present in a message, the UE shall:

1> forward the content to upper layers along with the IE "CN domain identity" of the associated RAB stored in the variable ESTABLISHED_RABS at the CFN indicated in the IE "Activation time" in order to synchronise actions in NAS and AS.

8.6.4.13 PDCP context relocation info

If the IE "PDCP context relocation info" is included, the UE shall, for each radio bearer included in this IE:

1> If the IE "Downlink RFC 3095 context relocation indication" is set to TRUE:

2> perform the actions as specified in [36] for all ROHC contexts associated with that radio bearer in the downlink.

1> If the IE "Uplink RFC 3095 context relocation indication" is set to TRUE:

2> perform the actions as specified in [36] for all ROHC contexts associated with that radio bearer in the uplink.

8.6.4.14 RLC Info MBMS

Upon reception of the IE "RLC Info MBMS", the UE shall:

1> configure the receiving RLC entity in the UE for that radio bearer accordingly;

1> configure the corresponding RLC entity with the LI size indicated in the IE "DL UM RLC LI size".

1> if the IE "DL Duplication Avoidance and Reordering info" is present:

2> configure the corresponding RLC entity to use the UM duplication avoidance and reordering functionality.

1> if the IE "DL Out of sequence delivery info" is present:

2> configure the corresponding RLC entity to use the UM out of sequence delivery functionality.

8.6.4.15 RAB information for MBMS ptp bearer

If the IE "RAB information for MBMS ptp bearer" is included then the UE shall:

1> if an entry for the radio access bearer identified by the IE "RB Identity" already exists in the variable ESTABLISHED_RABS and a value of the IE "MBMS Service Identity" is stored in this entry of the variable ESTABLISHED_RABS:

2> notify upper layers that the radio access bearer characterised by the parameters currently stored in this entry of the variable ESTABLISHED_RABS is released;

2> reuse this entry of the variable ESTABLISHED_RABS and update it with the received value of IE "MBMS Service Identity" and, if included, with the received value of IE "MBMS Session Identity";

2> notify upper layers that the radio access bearer characterised by the updated parameters in this entry is established.

1> else:

2> set the variable INVALID_CONFIGURATION to TRUE.

8.6.4.16 Retrievable configuration info

If the IE "Retrievable configuration info" is included in the reconfiguration message:

1> perform the actions below, and then act upon all other received information elements as specified in subclause 8.6.

If the IE "Retrievable configuration to be invoked" is included in the reconfiguration message:

1> consider the IE "Retrievable configuration to be invoked" as the invoked id;

1> act as if all parameters stored in the variable RETRIEVABLE_CONFIGURATION for the invoked id had been received in the reconfiguration message;

1> if any of the parameters stored in the variable RETRIEVABLE_CONFIGURATION for the invoked id are also included in the reconfiguration message or if the parameter has not been assigned a value in the variable RETRIEVABLE_CONFIGURATION:

2> act upon the values received in the reconfiguration message for those parameters in the variable RETRIEVABLE_CONFIGURATION.

If the IE "Retrievable configuration to be stored" is included in the reconfiguration message:

1> consider the IE "Retrievable configuration to be stored" as the stored id;

1> after the IE "Retrievable configuration to be invoked", if included, has been acted upon above:

2> store the values of the parameters of the resulting configuration with the stored id in the variable RETRIEVABLE_CONFIGURATION, replacing or clearing any previously stored information in this entry.

If the IE "Retrievable configuration to be removed" is included in the reconfiguration message:

1> remove the retrievable configurations identified by the IE "Retrievable configuration identity".

If the IE "Retrievable configuration to be invoked" is included in the reconfiguration message and a retrievable configuration with the received identity is not stored in the variable RETRIEVABLE_CONFIGURATION:

1> set the variable INVALID_CONFIGURATION to TRUE.

If other IEs than the IE "Preconfigured retrievable configuration" are also included in the message, the UE shall first act on those IEs, and then act on the IE "Preconfigured retrievable configuration". For each occurrence of the IE "Preconfigured retrievable configuration":

1> consider the IE "Retrievable configuration identity" as the stored id;

1> store all values of the parameters in IE "Retrievable configuration" with the stored id in the variable RETRIEVABLE_CONFIGURATION;

1> if the same retrievable configuration identity has already been stored in the variable RETRIEVABLE_CONFIGURATION:

2> if any of the parameters stored in the variable RETRIEVABLE_CONFIGURATION for the IE "Retrievable configuration identity" are also included in IE "Retrievable configuration" in the reconfiguration message, or if the parameter has not been assigned a value in the variable RETRIEVABLE_CONFIGURATION:

3> overwrite the stored values with the values received in IE "Retrievable configuration"and store the new values in the variable RETRIEVABLE_CONFIGURATION.

8.6.4.17 Other state configuration info

If the IE "Other state configuration info" is included in the reconfiguration message, the UE shall:

1> if the IE "Other state configuration to be stored" is present, then for each configuration:

2> set the variable INVALID_CONFIGURATION to TRUE if any of the following conditions are met

3> there is already one stored configuration with the same value in IE "Source RRC State Indicator";

3> if the IE "Source RRC state Indicator" is "CELL_DCH", and the IE "Target RRC State Indicator" is other than "CELL_FACH", "CELL_PCH" or "URA_PCH";

3> if the IE "Source RRC state Indicator" is "CELL_FACH", and the IE "Target RRC State Indicator" is other than "CELL_PCH" or "URA_PCH";

3> if the RRC configuration in the IE "configuration" is not valid for the target state indicated by IE "Target RRC State Indicator".

2> if variable OTHER_STATE_CONFIGURATION already contains a configuration with the same "Other state configuration identity":

3> overwrite the stored values with the values received in the reconfiguration message and store the new values in the UE variable OTHER_STATE_CONFIGURATION.

2> else:

3> store all values of applicable parameters with the associated identity in the variable OTHER_STATE_CONFIGURATION.

1> if the IE "Other state configuration to be removed" is present:

2> for each each occurance of the IE "Other state configuration identity":

3> remove the corresponding other state configuration in the variable OTHER_STATE_CONFIGURATION.