28.11.2014 Views

ts_125331v120300p

ts_125331v120300p

ts_125331v120300p

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

3GPP TS 25.331 version 12.3.0 Release 12<br />

207<br />

ETSI TS 125 331 V12.3.0 (2014-10)<br />

2> transmit a RADIO BEARER RELEASE FAILURE as response message on the DCCH using AM RLC.<br />

1> in case of reception of a TRANSPORT CHANNEL RECONFIGURATION message:<br />

2> transmit a TRANSPORT CHANNEL RECONFIGURATION FAILURE as response message on the DCCH<br />

using AM RLC.<br />

1> in case of reception of a PHYSICAL CHANNEL RECONFIGURATION message:<br />

2> transmit a PHYSICAL CHANNEL RECONFIGURATION FAILURE as response message on the DCCH<br />

using AM RLC.<br />

1> when the response message has been submitted to lower layers for transmission:<br />

2> continue with any ongoing processes and procedures as if no reconfiguration attempt had occurred.<br />

8.2.2.10 Reception of a response message by the UTRAN, failure case<br />

When the UTRAN has received:<br />

- the RADIO BEARER SETUP FAILURE message; or<br />

- the RADIO BEARER RECONFIGURATION FAILURE message; or<br />

- the RADIO BEARER RELEASE FAILURE message; or<br />

- the TRANSPORT CHANNEL RECONFIGURATION FAILURE message; or<br />

- the PHYSICAL CHANNEL RECONFIGURATION FAILURE message:<br />

the UTRAN may restore the old and delete the new configuration. Upper layers should be notified of the failure.<br />

The procedure ends on the UTRAN side.<br />

8.2.2.11 Invalid configuration<br />

If the variable INVALID_CONFIGURATION is set to TRUE the UE shall:<br />

1> keep the configuration existing before the reception of the message;<br />

1> transmit a failure response message as specified in subclause 8.2.2.9, setting the information elemen<strong>ts</strong> as<br />

specified below:<br />

2> include the IE "RRC transaction identifier"; and<br />

3> set it to the value of "RRC transaction identifier" in the entry for the received message in the table<br />

"Accepted transactions" in the variable TRANSACTIONS; and<br />

3> clear that entry.<br />

2> set the IE "failure cause" to "invalid configuration".<br />

1> set the variable INVALID_CONFIGURATION to FALSE;<br />

1> continue with any ongoing processes and procedures as if the reconfiguration message was not received.<br />

The procedure ends.<br />

8.2.2.12 Incompatible simultaneous reconfiguration<br />

If the table "Rejected transactions" in the variable TRANSACTIONS is set due to the received message and the variable<br />

PROTOCOL_ERROR_REJECT is set to FALSE, the UE shall:<br />

1> not apply the configuration contained in the received reconfiguration message;<br />

ETSI

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!