8 RRC procedures

25.3313GPPProtocol specificationRadio Resource Control (RRC)Release 17TS

The UE shall be able to process several simultaneous RRC procedures. After the reception of a message which invoked a procedure, the UE shall be prepared to receive and act on another message which may invoke a second procedure. Whether this second invocation of a procedure (transaction) is accepted or rejected by the UE is specified in the subclauses of this clause, and in particular in subclause 8.6.3.11 (RRC transaction identifier).

On receiving a message the UE shall:

1> check that the message is addressed to the UE (e.g. by checking the IE "Initial UE identity" or the IE "U-RNTI" for messages on CCCH);

1> discard the messages addressed to other UEs.

and then the UE shall:

1> apply integrity check as appropriate;

1> proceed with error handling as specified in clause 9;

1> act upon the IE "RRC transaction identifier";

1> continue with the procedure as specified in the relevant subclause.

NOTE: Due to an error in the Release ’99 ASN.1, a Release ’99 UE is unable to determine which UE is addressed by a downlink CCCH message corresponding to a protocol version later than Release ’99. As a result, the Release ’99 UE will not be able to return a protocol error according to subclause 9.3a. Therefore, the UTRAN should only send a Release ’99 message version towards UEs that have indicated conformance to Release ’99 in the IE "Access stratum release indicator".

The RRC entity in the UE shall consider PDUs to have been transmitted when they are submitted to the lower layers. If the RRC entity in the UE submits a message for transmission using AM RLC, it shall consider the message successfully transmitted when UTRAN reception of all relevant PDUs is acknowledged by RLC. In the UE, timers are started when the PDUs are sent on the radio interface in the case of the transmission using the CCCH.