ts_125331v120300p

3GPP TS 25.331 version 12.3.0 Release 12
204
ETSI TS 125 331 V12.3.0 (2014-10)
2> on the transmitting side of an RLC entity apply the new ciphering configuration in downlink immediately.
1> for radio bearers using RLC-TM:
2> begin incrementing the COUNT-C at the CFN only as indicated in:
3> the IE "Ciphering activation time for DPCH" in the IE "Ciphering mode info", if included in the message
that triggered the radio bearer control procedure; or
3> the IE "COUNT-C activation time", if included in the response message for this procedure.
1> and the procedure ends on the UTRAN side.
8.2.2.5a
Rejection by the UE
If the UTRAN establishes one or more p-t-p radio bearer(s) for the transmission of a session of an MBMS service,
identified by the IE "MBMS Session identity", for which upper layers indicate that it has already been received
correctly, the UE shall:
1> transmit a failure response as specified in subclause 8.2.2.9, setting the information elements as specified below:
2> include the IE "RRC transaction identifier";
2> set it to the value of "RRC transaction identifier" in the entry for the received message in the table "Accepted
transactions" in the variable TRANSACTIONS;
2> clear that entry; and
2> set the IE "failure cause" to "MBMS session already received correctly".
1> set the variable UNSUPPORTED_CONFIGURATION to FALSE;
1> continue with any ongoing processes and procedures as if the reconfiguration message was not received.
1> the procedure ends.
If the UTRAN establishes one or more p-t-p radio bearer(s) for the transmission of a session of an MBMS service,
which will inhibit reception of one or more MBMS services which according to upper layers are of higher priority, the
UE may:
1> transmit a failure response as specified in subclause 8.2.2.9, setting the information elements as specified below:
2> include the IE "RRC transaction identifier";
2> set it to the value of "RRC transaction identifier" in the entry for the received message in the table "Accepted
transactions" in the variable TRANSACTIONS;
2> clear that entry; and
2> set the IE "failure cause" to "Lower priority MBMS service".
1> set the variable UNSUPPORTED_CONFIGURATION to FALSE;
1> continue with any ongoing processes and procedures as if the reconfiguration message was not received.
1> the procedure ends.
8.2.2.6 Unsupported configuration in the UE
If the UTRAN instructs the UE to use a configuration, which it does not support and/or if the received message causes
the variable UNSUPPORTED_CONFIGURATION to be set to TRUE, the UE shall:
1> transmit a failure response as specified in subclause 8.2.2.9, setting the information elements as specified below:
2> include the IE "RRC transaction identifier"; and
ETSI