ts_125331v120300p

3GPP TS 25.331 version 12.3.0 Release 12
2125
ETSI TS 125 331 V12.3.0 (2014-10)
Although the same principles apply for network nodes receiving unknown, unforeseen and erroneous RRC messages
received in RRC information containers, the notification of the error should be done in a different manner, as specified
in the following:
The network node receiving an invalid RRC message from another network node should:
1> if the received RRC message was unknown, unforeseen or erroneous:
2> prepare an RRC FAILURE INFO message, including the IE "Failure cause" set to "Protocol error" and the IE
"Protocol error information" including an IE "Protocol error cause" which should be set as follows:
3> to "ASN.1 violation or encoding error" upon receiving an RRC message for which the encoded message
does not result in any valid abstract syntax value;
3> to "Message type non-existent or not implemented" upon receiving an unknown RRC message type;
3> to "Message extension not comprehended" upon receiving an RRC message including an undefined
critical message extension;
3> to "Information element value not comprehended" upon receiving an RRC message including an
mandatory IE for which no default value is defined and for which either the value is set to spare or for
which the encoded IE does not result in a valid transfer syntax. The same applies for conditional IEs, for
which the conditions for presence are met, the IE is present but has a value set to spare or for which the
encoded IE does not result in a valid transfer syntax;
3> to "Information element missing" upon receiving an RRC information container with an absent
conditional IE for which the conditions for presence are met.
1> if there was another failure to perform the operation requested by the received RRC message:
2> prepare an RRC FAILURE INFO message, including the IE "Failure cause" set to a value that reflects the
failure cause.
1> send the RRC FAILURE INFO message to the network node from which the invalid RRC protocol information
was received.
NOTE 1: The appropriate (failure) messages used across the network interfaces may not support the inclusion of a
RRC information container. In this case, the information contained in the RRC FAILURE INFO message
may need to be transferred otherwise e.g. by mapping to a cause value (e.g. a cause value in the RR-
HANDOVER FAILURE message when there is a error associated with the RRC-HANDOVER TO
UTRAN COMMAND message).
NOTE 2 In case the RRC procedure used to perform SRNS relocation fails e.g. due to non comprehension, the
source RNC may notify the target RNC by including the diagnostics information (IEs "Protocol error"
and "Protocol error information") in the "RRC message "SRNS Relocation" Info sent in the RRC
information container" used for a subsequent relocation request.
14.12.1 RRC Information to target RNC
The RRC information container "RRC Information to target RNC" may either be sent from source RNC or from another
RAT. In case of handover to UTRAN, this information originates from another RAT, while in case of SRNC relocation
the RRC information originates from the source RNC. In case of handover to UTRAN, the RRC information transferred
may provide UTRAN specific information, as defined in the INTER RAT HANDOVER INFO WITH INTER RAT
CAPABILITIES message, that the target RNC needs when preparing the handover command message. In case of
SRNC relocation and handover/cell reselection from GERAN Iu mode, the RRC information transferred specifies the
configuration of RRC and the lower layers it controls, e.g., including the radio bearer and transport channel
configuration. It is used by the target RNC to initialise RRC and the lower layer protocols to facilitate SRNC relocation
and handover/cell reselection from GERAN Iu mode in a manner transparent to the UE.
RFC 3095 CONTEXT INFO is used to transfer the compressor and decompressor context information of the ROHC
[83], [84] protocol from source RNC to target RNC.
ETSI