14.12 Provision and reception of RRC information between network nodes
25.3313GPPProtocol specificationRadio Resource Control (RRC)Release 17TS
14.12.0 General
In certain cases, e.g., when performing handover to UTRAN or when performing SRNC relocation, RRC information may need to be transferred between UTRAN nodes, between UTRAN and another RAT, between nodes within another RAT or between the UE and another RAT.
The RRC information exchanged between network nodes or between the UE and another RAT is typically transferred by means of RRC information containers. An RRC information container is a self-contained and extensible RRC information unit that may be used to transfer a number of different RRC messages, one at a time. As stated before, RRC information containers may be used to transfer RRC messages across interfaces other than the Uu interface. The RRC messages that may be included in RRC information containers have similar characteristics as the RRC messages that are transferred across the Uu interface.
The RRC messages that are sent to/ from the UE, e.g., HANDOVER TO UTRAN COMMAND, INTER RAT HANDOVER INFO are covered by (sub)clauses 8, 9, 10, 11.0-11.4 and 12 of this specification. The following subclauses concern RRC messages exchanged between network nodes.
In future versions of this specification, it is possible to extend the RRC messages transferred across interfaces other than Uu. For these RRC messages the same extension mechanism applies as defined for RRC messages transferred across the Uu interface, as is specified in subclause 10.1, i.e., both critical and non-critical extensions may be added.
The transfer syntax for RRC information containers and RRC messages transferred between network nodes is derived from their ASN.1 definitions by use of Packed Encoding Rules, unaligned (X.691). It should be noted that the encoder adds final padding to achieve octet alignment. The resulting octet string is, carried in a container, transferred between the network nodes.
When using a separate RRC information container for each endpoint, the receiving RRC protocol entity is able to interpret the received container; this means that the receiver need not take into account information about the (network interface) message used in transferring the container.
The following encoding rules apply in addition to what has been specified in X.691 [49]:
1> When a bit string value is placed in a bit-field as specified in 15.6 to 15.11 in [11], the leading bit of the bit string value shall be placed in the leading bit of the bit-field, and the trailing bit of the bit string value shall be placed in the trailing bit of the bit-field.
NOTE: The terms "leading bit" and "trailing bit" are defined in ITU-T Rec. X.680 | ISO/IEC 8824-1. When using the "bstring" notation, the leading bit of the bit string value is on the left, and the trailing bit of the bit string value is on the right.
14.12.0a General error handling for RRC messages exchanged between network nodes
The error handling for RRC messages that are exchanged between network nodes applies the same principles as defined for other RRC messages.
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.
|
Information Element/Group Name |
Need |
Multi |
Type and reference |
Semantics description |
Version |
|---|---|---|---|---|---|
|
CHOICE case |
MP |
At least one spare choice, Criticality: Reject, is needed |
|||
|
>Handover to UTRAN |
INTER RAT HANDOVER INFO WITH INTER RAT CAPABILITIES |
||||
|
>SRNC relocation |
SRNS RELOCATION INFO |
||||
|
>RFC 3095 context info |
RFC 3095 CONTEXT INFO 14.12.4.4 |
REL-5 |
14.12.2 RRC information, target RNC to source RNC
There are 2 possible cases for RNC relocation:
1. The UE is already under control of target RNC; and
2. The SRNC Relocation with Hard Handover (UE still under control of SRNC), but UE is moving to a location controlled by the target RNC (based on measurement information).
In case 1 the relocation is transparent to the UE and there is no "reverse" direction container. The SRNC just assigns the ‘serving’ function to the target RNC, which then becomes the Serving RNC.
In case 2 the relocation is initiated by SRNC, which also provides the RRC Initialisation Information to the target RNC. Base on this information, the target RNC prepares the Hard Handover Message ( "Physical channel reconfiguration" (subclause 8.2.6), "radio bearer establishment" (subclause 8.2.1), "Radio bearer reconfiguration" (subclause 8.2.2), "Radio bearer release" (subclause 8.2.3) or "Transport channel reconfiguration" (subclause 8.2.4)).
In case 2 two possibilities are defined in order to transmit the relocation message from the target RNC to the source RNC which can be chosen by the source RNC by including or not including the IE "RB Id for handover message" in the IE "SRNS Relocation Info".
In case the IE "RB Id for handover message" has been received by the target RNC in the IE "SRNS Relocation Info", the target RNC should choose the IE "DL DCCH message" and include the DL DCCH message that should be transmitted transparently to the UE by the source RNC. In that case, the target RNC is integrity protecting the message if applicable.
If the target RNC did not receive the IE "RB Id for handover message" in the IE "SRNS Relocation Info" the target RNC should use another choice. In that case, the source RNC should integrity protect the message before transmitting it to the UE if applicable.
The source RNC then transmits the Handover Message to the UE, which then performs the handover.
In the successful case, the UE transmits an XXX COMPLETE message, using the new configuration, to the target RNC.
In case of failure, the UE transmits an XXX FAILURE, using the old configuration, to the source RNC and the RRC context remains unchanged (has to be confirmed and checked with the SRNS relocation procedure).
|
Information Element/Group name |
Need |
Multi |
Type and reference |
Semantics description |
|---|---|---|---|---|
|
CHOICE RRC message |
MP |
At least one spare choice, Criticality: Reject, is needed |
||
|
>RADIO BEARER SETUP |
RADIO BEARER SETUP 10.2.33 |
|||
|
>RADIO BEARER RECONFIGURATION |
RADIO BEARER RECONFIGURATION 10.2.27 |
|||
|
>RADIO BEARER RELEASE |
RADIO BEARER RELEASE 10.2.30 |
|||
|
>TRANSPORT CHANNEL RECONFIGURATION |
TRANSPORT CHANNEL RECONFIGURATION 10.2.50 |
|||
|
>PHYSICAL CHANNEL RECONFIGURATION |
PHYSICAL CHANNEL RECONFIGURATION 10.2.22 |
|||
|
>RRC FAILURE INFO |
RRC FAILURE INFO 10.2.41 a |
|||
|
>DL DCCH message |
OCTET STRING |
14.12.3 Void
14.12.4 RRC messages exchanged between network nodes
14.12.4.0 HANDOVER TO UTRAN COMMAND
This RRC message is sent between network nodes to transfer the actual handover command including the details of the radio configuration to be used upon handover to UTRAN as compiled by the target RNC.
Direction: target RNC source RAT
The message is exactly the same as the HANDOVER TO UTRAN COMMAND defined in subclause 10.2.16a.
14.12.4.0a INTER RAT HANDOVER INFO
This RRC message is sent between network nodes to transfer information relevant for the target RNC when preparing for handover to UTRAN.
Direction: source RAT nodetarget RAT node
The message is exactly the same as the INTER RAT HANDOVER INFO defined in subclause 10.2.16d.
14.12.4.1 INTER RAT HANDOVER INFO WITH INTER RAT CAPABILITIES
This RRC message is sent between network nodes when preparing for an inter RAT handover to UTRAN.
The radio access capabilities for the source RAT and target RAT shall always be included; the radio access capabilities for other RATs may be included if available at the source RAT.
Direction: source RATtarget RNC
|
Information Element/Group Name |
Need |
Multi |
Type and reference |
Semantics description |
Version |
|---|---|---|---|---|---|
|
UE Information elements |
|||||
|
Predefined configuration status information |
OP |
Predefined configuration status information 10.3.4.5a |
|||
|
Predefined configuration status information compressed |
OP |
Predefined configuration status information compressed 10.3.4.5b |
REL-5 |
||
|
UE security information |
OP |
UE security information 10.3.3.42b |
|||
|
UE security information2 |
OP |
UE security information2 10.3.3.42c |
REL-6 |
||
|
UE Specific Behaviour Information 1 interRAT |
OP |
UE Specific Behaviour Information 1 interRAT 10.3.3.52 |
This IE shall not be included in this version of the protocol |
||
|
UE capability container |
OP |
||||
|
>UE radio access capability |
MP |
UE radio access capability 10.3.3.42 |
|||
|
>UE radio access capability extension |
MP |
UE radio access capability extension 10.3.3.42a |
Although this IE is not always required, the need has been set to MP to align with the ASN.1 |
||
|
UE radio access capability compressed |
OP |
UE radio access capability compressed 10.3.3.42o |
REL-5 |
||
|
UE radio access capability comp 2 |
OP |
UE radio access capability comp 2 10.3.3.42oa |
REL-6 |
||
|
Other Information elements |
|||||
|
UE system specific capability |
OP |
1 to <maxSystemCapability> |
|||
|
>Inter-RAT UE radio access capability |
MP |
Inter-RAT UE radio access capability 10.3.8.7 |
|||
|
Failure cause |
OP |
Failure cause 10.3.3.13 |
Diagnostics information related to an earlier handover to UTRAN request |
||
|
Protocol error information |
CV-ProtErr |
Protocol error information 10.3.8.12 |
|||
|
UE inactivity period |
OP |
Integer (1..120) |
Provides expired time since last u-plane activity. If the integer value x is between 1 and 59, it represents the expired time x in seconds. If the integer value x is between 60 and 119, it represents the expired time (x-59) in minutes. If integer value is set to 120, no u-plane activity has been for 60 minutes or more. |
REL-9 |
|
Condition |
Explanation |
|
ProtErr |
This IE is mandatory present if the IE "Protocol error indicator" is included and has the value TRUE. Otherwise it is not needed. |
NOTE1: To facilitate that network nodes can transparently forward the RRC information received, the INTER RAT HANDOVER INFO WITH INTER RAT CAPABILITIES should include the entire INTER RAT HANDOVER INFO message. The network node, which may not be able to decode the information received, may only append some information to what was received.
NOTE2: The above table does not need to reflect the order of the information elements in the actual encoded message. The order, that is reflected in the ASN.1, should be chosen in a manner that avoids that network nodes need to perform reordering of information elements.
14.12.4.2 SRNS RELOCATION INFO
This RRC message is sent between network nodes when preparing for an SRNS relocation or a handover/cell reselection from GERAN Iu mode.
With the presence or absence of the IE "RB identity for Hard Handover message" the source RNC indicates to the target SRNC whether the source RNC expects to receive the choice "DL DCCH message" in the IE "RRC information, target RNC to source RNC" in case the SRNS relocation is of type "UE involved". Furthermore the target RNC uses this information for the calculation of the MAC-I.
Direction: source RNC/RATtarget RNC
|
Information Element/Group Name |
Need |
Multi |
Type and reference |
Semantics description |
Version |
|---|---|---|---|---|---|
|
Non RRC IEs |
|||||
|
>RB identity for Handover message |
OP |
RB identity 10.3.4.16 |
Gives the id of the radio bearer on which the source RNC will transmit the RRC message in the case the relocation is of type "UE involved". In handover from GERAN Iu mode this IE is always set to 2. |
||
|
>State of RRC |
MP |
RRC state indicator, 10.3.3.35a |
|||
|
>State of RRC procedure |
MP |
Enumerated (await no RRC message, await RB Release Complete, await RB Setup Complete, await RB Reconfiguration Complete, await Transport CH Reconfiguration Complete, await Physical CH Reconfiguration Complete, await Active Set Update Complete, await Handover Complete, send Cell Update Confirm, send URA Update Confirm, , others) |
|||
|
Ciphering related information |
|||||
|
>Ciphering status for each CN domain |
MP |
<1 to maxCNDomains> |
|||
|
>>CN domain identity |
MP |
CN domain identity 10.3.1.1 |
|||
|
>>Ciphering status |
MP |
Enumerated(Not started, Started) |
|||
|
>>START |
MP |
START 10.3.3.38 |
START value to be used in this CN domain. |
||
|
>Latest configured CN domain |
MP |
CN domain identity 10.3.1.1 |
Value contained in the variable of the same name. In case this variable is empty, the source RNC can set any CN domain identity. In that case, the Ciphering status and the Integrity protection status should be Not started and the target RNC should not initialise the variable Latest configured CN domain. |
||
|
>Calculation time for ciphering related information |
CV-Ciphering |
Time when the ciphering information of the message were calculated, relative to a cell of the target RNC. In handover and cell reselection from GERAN Iu mode this field is not present. |
|||
|
>>Cell Identity |
MP |
Cell Identity 10.3.2.2 |
Identity of one of the cells under the target RNC and included in the active set of the current call |
||
|
>>SFN |
MP |
Integer(0..4095) |
|||
|
>COUNT-C list |
OP |
1 to <maxCNdomains> |
COUNT-C values for radio bearers using transparent mode RLC |
||
|
>>CN domain identity |
MP |
CN domain identity 10.3.1.1 |
|||
|
>>COUNT-C |
MP |
Bit string(32) |
|||
|
>Ciphering info per radio bearer |
OP |
1 to <maxRB> |
For signalling radio bearers this IE is mandatory. |
||
|
>>RB identity |
MP |
RB identity 10.3.4.16 |
|||
|
>>Downlink HFN |
MP |
Bit string(20..25) |
This IE is either RLC AM HFN (20 bits) or RLC UM HFN (25 bits) |
||
|
>>Downlink SN |
CV-SRB1 |
Bit String(7) |
VT(US) of RLC UM |
||
|
>>Uplink HFN |
MP |
Bit string(20..25) |
This IE is either RLC AM HFN (20 bits) or RLC UM HFN (25 bits) |
||
|
Integrity protection related information |
|||||
|
>Integrity protection status |
MP |
Enumerated(Not started, Started) |
|||
|
>Signalling radio bearer specific integrity protection information |
CV-IP |
4 to <maxSRBsetup> |
|||
|
>>Uplink RRC HFN |
MP |
Bit string (28) |
For each SRB, in the case activation times for the next IP configuration to be applied on this SRB have already been reached this IE corresponds to the last value used. Else this value corresponds to the value the source would have initalized the HFN to at the activation time, not considering any increment of HFN due to RRC SN roll over. Increment of HFN due to RRC SN roll over is taken care of by target based on value sent by the source. |
||
|
>>Downlink RRC HFN |
MP |
Bit string (28) |
For each SRB, in the case activation times for the next IP configuration to be applied on this SRB have already been reached this IE corresponds to the last value used. Else this value corresponds to the value the source would have initalized the HFN to at the activation time, not considering any increment of HFN due to RRC SN roll over. Increment of HFN due to RRC SN roll over is taken care of by target based on value sent by the source. In particular, for SRB2, this IE should not take into account the RRC message that will trigger the relocation. NOTE: In order to have the possibility of sending downlink messages after the construction of the IE "SRNS RELOCATION INFO", the source may choose a value ahead of the last value used. |
||
|
>>Uplink RRC Message sequence number |
MP |
Integer (0.. 15) |
For each SRB, this IE corresponds to the last value received or in the case activation time was not reached for a configuration the value equals (activation time -1). |
||
|
>>Downlink RRC Message sequence number |
MP |
Integer (0.. 15) |
For each SRB, this IE corresponds to the last value used or in the case activation time was not reached for a configuration the value equals (activation time -1). In particular, for SRB2, this IE should not take into account the RRC message that will trigger the relocation. NOTE: In order to have the possibility of sending downlink messages after the construction of the IE "SRNS RELOCATION INFO", the source may choose a value ahead of the last value used for SRB3 and SRB4. |
||
|
>Implementation specific parameters |
OP |
Bit string (1..512) |
|||
|
RRC IEs |
|||||
|
UE Information elements |
|||||
|
>U-RNTI |
MP |
U-RNTI 10.3.3.47 |
G-RNTI is placed in this field when performing handover or cell reselection from GERAN Iu mode. |
||
|
>C-RNTI |
OP |
C-RNTI 10.3.3.8 |
|||
|
>UE radio access Capability |
MP |
UE radio access capability 10.3.3.42 |
|||
|
>UE radio access capability extension |
OP |
UE radio access capability extension 10.3.3.42a |
|||
|
>Last known UE position |
OP |
||||
|
>>SFN |
MP |
Integer (0..4095) |
Time when position was estimated |
||
|
>>Cell ID |
MP |
Cell identity; 10.3.2.2 |
Indicates the cell, the SFN is valid for. |
||
|
>>CHOICE Position estimate |
MP |
||||
|
>>>Ellipsoid Point |
Ellipsoid Point; 10.3.8.4a |
||||
|
>>>Ellipsoid point with uncertainty circle |
Ellipsoid point with uncertainty circle 10.3.8.4d |
||||
|
>>>Ellipsoid point with uncertainty ellipse |
Ellipsoid point with uncertainty ellipse 10.3.8.4e |
||||
|
>>>Ellipsoid point with altitude |
Ellipsoid point with altitude 10.3.8.4b |
||||
|
>>>Ellipsoid point with altitude and uncertainty ellipsoid |
Ellipsoid point with altitude and uncertainty ellipsoid 10.3.8.4c |
||||
|
>UE Specific Behaviour Information 1 idle |
OP |
UE Specific Behaviour Information idle 1 10.3.3.51 |
This IE should be included if received via the "INTER RAT HANDOVER INFO", the "RRC CONNECTION REQUEST", the IE "SRNS RELOCATION INFO" or the "Inter RAT Handover Info with Inter RAT Capabilities" |
||
|
>UE Specific Behaviour Information 1 interRAT |
OP |
UE Specific Behaviour Information 1 interRAT 10.3.3.52 |
This IE should be included if received via the "INTER RAT HANDOVER INFO", the "RRC CONNECTION REQUEST", the IE "SRNS RELOCATION INFO" or the "Inter RAT Handover Info with Inter RAT Capabilities" |
||
|
Other Information elements |
|||||
|
>UE system specific capability |
OP |
1 to <maxSystemCapability> |
|||
|
>>Inter-RAT UE radio access capability |
MP |
Inter-RAT UE radio access capability 10.3.8.7 |
|||
|
UTRAN Mobility Information elements |
|||||
|
>URA Identifier |
OP |
URA identity 10.3.2.6 |
|||
|
>T305 |
OP |
Integer (5, 10, 30, 60, 120, 360, 720, infinity) |
If UE is in CELL_FACH state, this information element shall be included. Value in minutes. Infinity means no update. |
REL-7 |
|
|
CN Information Elements |
|||||
|
>CN common GSM-MAP NAS system information |
MP |
NAS system information (GSM-MAP) 10.3.1.9 |
|||
|
>CN domain related information |
OP |
1 to <MaxCNdomains> |
CN related information to be provided for each CN domain |
||
|
>>CN domain identity |
MP |
||||
|
>>CN domain specific GSM-MAP NAS system info |
MP |
NAS system information (GSM-MAP) 10.3.1.9 |
|||
|
>>CN domain specific DRX cycle length coefficient |
MP |
CN domain specific DRX cycle length coefficient, 10.3.3.6 |
|||
|
Measurement Related Information elements |
|||||
|
>For each ongoing measurement reporting |
OP |
1 to <MaxNoOfMeas> |
The source RNC should include the measurement IEs for each measurement configured and ongoing in the UE. |
||
|
>>Measurement Identity |
MP |
Measurement identity 10.3.7.48 |
|||
|
>>Measurement Command |
MP |
Measurement command 10.3.7.46 |
This IE should have the value Setup. |
||
|
>>Measurement Type |
CV-Setup |
Measurement type 10.3.7.50 |
|||
|
>>Measurement Reporting Mode |
OP |
Measurement reporting mode 10.3.7.49 |
|||
|
>>Additional Measurements list |
OP |
Additional measurements list 10.3.7.1 |
|||
|
>>CHOICE Measurement |
CV-Setup |
||||
|
>>>Intra-frequency |
|||||
|
>>>>Intra-frequency cell info |
OP |
Intra-frequency cell info list 10.3.7.33 |
|||
|
>>>>Intra-frequency cell info on secondary UL frequency |
OP |
Intra-frequency cell info list on secondary UL frequency 10.3.7.116 |
|||
|
>>>>Intra-frequency measurement |
OP |
Intra-frequency measurement quantity 10.3.7.38 |
|||
|
>>>>Intra-frequency reporting quantity |
OP |
Intra-frequency reporting quantity 10.3.7.41 |
|||
|
>>>>Reporting cell status |
OP |
Reporting cell status 10.3.7.61 |
|||
|
>>>>Measurement validity |
OP |
Measurement validity 10.3.7.51 |
|||
|
>>>>CHOICE report criteria |
OP |
||||
|
>>>>>Intra-frequency |
Intra-frequency measurement reporting criteria 10.3.7.39 |
||||
|
>>>>>Periodical reporting |
Periodical reporting criteria 10.3.7.53 |
||||
|
>>>>>No reporting |
NULL |
||||
|
>>>Inter-frequency |
|||||
|
>>>>Inter-frequency cell info |
OP |
Inter-frequency cell info list 10.3.7.13 |
|||
|
>>>>Inter-frequency measurement |
OP |
Inter-frequency measurement quantity 10.3.7.18 |
|||
|
>>>>Inter-frequency reporting quantity |
OP |
Inter-frequency reporting quantity 10.3.7.21 |
|||
|
>>>>Reporting cell status |
OP |
Reporting cell status 10.3.7.61 |
|||
|
>>>>Measurement validity |
OP |
Measurement validity 10.3.7.51 |
|||
|
>>>>Inter-frequency set update |
OP |
Inter-frequency set update 10.3.7.22 |
|||
|
>>>>CHOICE report criteria |
MP |
||||
|
>>>>>Intra-frequency measurement reporting criteria |
Intra-frequency measurement reporting criteria 10.3.7.39 |
||||
|
>>>>>Inter-frequency |
Inter-frequency measurement reporting criteria 10.3.7.19 |
||||
|
>>>>>Periodical reporting |
Periodical reporting criteria 10.3.7.53 |
||||
|
>>>>>No reporting |
NULL |
||||
|
>>>Inter-RAT |
|||||
|
>>>>Inter-RAT cell info |
OP |
Inter-RAT cell info list 10.3.7.23 |
|||
|
>>>>Inter-RAT measurement |
OP |
Inter-RAT measurement quantity 10.3.7.29 |
|||
|
>>>>Inter-RAT reporting quantity |
OP |
Inter-RAT reporting quantity 10.3.7.32 |
|||
|
>>>>Reporting cell status |
OP |
Reporting cell status 10.3.7.61 |
|||
|
>>>>Measurement validity |
OP |
Measurement validity 10.3.7.51 |
|||
|
>>>>E-UTRA frequency list |
OP |
E-UTRA frequency list 10.3.7.6b |
REL-8 |
||
|
>>>>CHOICE report criteria |
MP |
||||
|
>>>>>Inter-RAT measurement |
Inter-RAT measurement reporting criteria 10.3.7.30 |
||||
|
>>>>>Periodical reporting |
Periodical reporting criteria 10.3.7.53 |
||||
|
>>>>>No reporting |
NULL |
||||
|
>>>Traffic Volume |
|||||
|
>>>>Traffic volume measurement |
OP |
Traffic volume measurement object 10.3.7.70 |
|||
|
>>>>Traffic volume measurement |
OP |
Traffic volume measurement quantity 10.3.7.71 |
|||
|
>>>>Traffic volume reporting quantity |
OP |
Traffic volume reporting quantity 10.3.7.74 |
|||
|
>>>>Measurement validity |
OP |
Measurement validity 10.3.7.51 |
|||
|
>>>>CHOICE report criteria |
MP |
||||
|
>>>>>Traffic volume measurement |
Traffic volume measurement reporting criteria 10.3.7.72 |
||||
|
>>>>>Periodical reporting |
Periodical reporting criteria 10.3.7.53 |
||||
|
>>>>>No reporting |
NULL |
||||
|
>>>Quality |
|||||
|
>>>>Quality measurement quantity |
OP |
Quality measurement quantity 10.3.7.59 |
|||
|
>>>>CHOICE report criteria |
MP |
||||
|
>>>>>Quality measurement |
Quality measurement reporting criteria 10.3.7.58 |
||||
|
>>>>>Periodical reporting |
Periodical reporting criteria 10.3.7.53 |
||||
|
>>>>>No reporting |
NULL |
||||
|
>>>UE internal |
|||||
|
>>>>UE internal measurement |
OP |
UE internal measurement quantity 10.3.7.79 |
|||
|
>>>>UE internal reporting quantity |
OP |
UE internal reporting quantity 10.3.7.82 |
|||
|
>>>>CHOICE report criteria |
MP |
||||
|
>>>>>UE internal measurement |
UE internal measurement reporting criteria 10.3.7.80 |
||||
|
>>>>>Periodical reporting |
Periodical reporting criteria 10.3.7.53 |
||||
|
>>>>>No reporting |
NULL |
||||
|
>>>UE positioning |
|||||
|
>>>>LCS reporting quantity |
OP |
LCS reporting quantity 10.3.7.111 |
|||
|
>>>>CHOICE report criteria |
MP |
||||
|
>>>>>LCS reporting criteria |
LCS reporting criteria 10.3.7.110 |
||||
|
>>>>>Periodical reporting |
Periodical reporting criteria 10.3.7.53 |
||||
|
>>>>>No reporting |
|||||
|
Radio Bearer Information Elements |
|||||
|
>Predefined configuration status information |
OP |
Predefined configuration status information 10.3.4.5a |
|||
|
>Signalling RB information list |
MP |
1 to <maxSRBsetup> |
For each signalling radio bearer |
||
|
>>Signalling RB information |
MP |
Signalling RB information to setup 10.3.4.24 |
|||
|
>RAB information list |
OP |
1 to <maxRABsetup> |
Information for each RAB |
||
|
>>RAB information |
MP |
RAB information to setup 10.3.4.10 |
|||
|
>PDCP ROHC target mode |
OP |
PDCP ROHC target mode 10.3.4.2a |
REL-8 |
||
|
Transport Channel Information Elements |
|||||
|
Uplink transport channels |
|||||
|
>UL Transport channel information common for all transport channels |
OP |
UL Transport channel information common for all transport channels 10.3.5.24 |
|||
|
>UL transport channel information list |
OP |
1 to <MaxTrCH> |
|||
|
>>UL transport channel information |
MP |
Added or reconfigured UL TrCH information 10.3.5.2 |
|||
|
Downlink transport channels |
|||||
|
>DL Transport channel information common for all transport channels |
OP |
DL Transport channel information common for all transport channels 10.3.5.6 |
|||
|
>DL transport channel information list |
OP |
1 to <MaxTrCH> |
|||
|
>>DL transport channel information |
MP |
Added or reconfigured DL TrCH information 10.3.5.1 |
|||
|
PhyCH information elements |
|||||
|
>TPC Combination Info list |
OP |
1 to <maxRL> |
|||
|
>>Primary CPICH info |
MP |
Primary CPICH info 10.3.6.60 |
|||
|
>>TPC combination index |
MP |
TPC combination index 10.3.6.85 |
|||
|
>TPC Combination Info list on secondary UL frequency |
OP |
1 to < maxEDCHRL> |
REL-9 |
||
|
>>Primary CPICH info |
MP |
Primary CPICH info 10.3.6.60 |
REL-9 |
||
|
>>TPC combination index |
MP |
TPC combination index 10.3.6.85 |
REL-9 |
||
|
>E-RGCH Combination Info list |
OP |
1 to <maxEDCHRL> |
REL-8 |
||
|
>>Primary CPICH info |
MP |
Primary CPICH info 10.3.6.60 |
REL-8 |
||
|
>>RG combination index |
MP |
Integer (0..5) |
REL-8 |
||
|
>E-RGCH Combination Info list on secondary UL frequency |
OP |
1 to <maxEDCHRL> |
REL-9 |
||
|
>>Primary CPICH info |
MP |
Primary CPICH info 10.3.6.60 |
REL-9 |
||
|
>>RG combination index |
MP |
Integer (0..5) |
REL-9 |
||
|
>Transmission gap pattern sequence |
OP |
1 to <maxTGPS> |
REL-5 |
||
|
>>TGPSI |
MP |
TGPSI 10.3.6.82 |
REL-5 |
||
|
>> Current TGPS Status Flag |
MP |
Enumerated(active, inactive) |
This flag indicates the current status of the Transmission Gap Pattern Sequence, whether it is active or inactive |
REL-5 |
|
|
>>TGCFN |
CV-Active |
Integer (0..255) |
Connection Frame Number of the latest past frame of the first pattern within the Transmission Gap Pattern Sequence. |
REL-5 |
|
|
>>Transmission gap pattern sequence configuration parameters |
OP |
REL-5 |
|||
|
>>>TGMP |
MP |
Enumerated(TDD measurement, FDD measurement, GSM carrier RSSI measurement, GSM Initial BSIC identification, GSM BSIC re-confirmation, Multi-carrier measurement, |
Transmission Gap pattern sequence Measurement Purpose. |
REL-5 |
|
|
E-UTRA measurements) |
REL-8 |
||||
|
>>>TGPRC |
MP |
Integer (1..511, Infinity) |
The number of remaining transmission gap patterns within the Transmission Gap Pattern Sequence. |
REL-5 |
|
|
>>>TGSN |
MP |
Integer (0..14) |
Transmission Gap Starting Slot Number The slot number of the first transmission gap slot within the TGCFN. |
REL-5 |
|
|
>>>TGL1 |
MP |
Integer(1..14) |
The length of the first Transmission Gap within the transmission gap pattern expressed in number of slots |
REL-5 |
|
|
>>>TGL2 |
MD |
Integer (1..14) |
The length of the second Transmission Gap within the transmission gap pattern. If omitted, then TGL2=TGL1. The value of TGL2 shall be ignored if TGD is set to ”undefined” |
REL-5 |
|
|
>>>TGD |
MP |
Integer(15..269, undefined) |
Transmission gap distance indicates the number of slots between starting slots of two consecutive transmission gaps within a transmission gap pattern. If there is only one transmission gap in the transmission gap pattern, this parameter shall be set to undefined. |
REL-5 |
|
|
>>>TGPL1 |
MP |
Integer (1..144) |
The duration of transmission gap pattern 1. |
REL-5 |
|
|
>>>RPP |
MP |
Enumerated (mode 0, mode 1). |
Recovery Period Power control mode during the frame after the transmission gap within the compressed frame. Indicates whether normal PC mode or compressed PC mode is applied |
REL-5 |
|
|
>>>ITP |
MP |
Enumerated (mode 0, mode 1). |
Initial Transmit Power is the uplink power control method to be used to compute the initial transmit power after the compressed mode gap. |
REL-5 |
|
|
>>>CHOICE UL/DL mode |
MP |
REL-5 |
|||
|
>>>>DL only |
Compressed mode used in DL only |
REL-5 |
|||
|
>>>>>Downlink compressed mode method |
MP |
Enumerated (SF/2, higher layer scheduling) |
Method for generating downlink compressed mode gap |
REL-5 |
|
|
>>>>UL only |
Compressed mode used in UL only |
REL-5 |
|||
|
>>>>>Uplink compressed mode method |
MP |
Enumerated (SF/2, higher layer scheduling) |
Method for generating uplink compressed mode gap |
REL-5 |
|
|
>>>>UL and DL |
Compressed mode used in UL and DL |
REL-5 |
|||
|
>>>>>Downlink compressed mode method |
MP |
Enumerated (SF/2, higher layer scheduling) |
Method for generating downlink compressed mode gap |
REL-5 |
|
|
>>>>>Uplink compressed mode method |
MP |
Enumerated (SF/2, higher layer scheduling) |
Method for generating uplink compressed mode gap |
REL-5 |
|
|
>>>Downlink frame type |
MP |
Enumerated (A, B) |
REL-5 |
||
|
>>>DeltaSIR1 |
MP |
Real(0..3 by step of 0.1) |
Delta in DL SIR target value to be set in the UE during the frame containing the start of the first transmission gap in the transmission gap pattern (without including the effect of the bit-rate increase) |
REL-5 |
|
|
>>>DeltaSIRafter1 |
MP |
Real(0..3 by step of 0.1) |
Delta in DL SIR target value to be set in the UE one frame after the frame containing the start of the first transmission gap in the transmission gap pattern. |
REL-5 |
|
|
>>>DeltaSIR2 |
OP |
Real(0..3 by step of 0.1) |
Delta in DL SIR target value to be set in the UE during the frame containing the start of the second transmission gap in the transmission gap pattern (without including the effect of the bit-rate increase) When omitted, DeltaSIR2 = DeltaSIR1. |
REL-5 |
|
|
>>>DeltaSIRafter2 |
OP |
Real(0..3 by step of 0.1) |
Delta in DL SIR target value to be set in the UE one frame after the frame containing the start of the second transmission gap in the transmission gap pattern. When omitted, DeltaSIRafter2 = DeltaSIRafter1. |
REL-5 |
|
|
>>>N Identify abort |
CV-Initial BSIC |
Integer(1..128) |
Indicates the maximum number of repeats of patterns that the UE shall use to attempt to decode the unknown BSIC of the GSM cell in the initial BSIC identification procedure |
REL-5 |
|
|
>>>T Reconfirm abort |
CV-Re-confirm BSIC |
Real(0.5..10.0 by step of 0.5) |
Indicates the maximum time allowed for the re-confirmation of the BSIC of one GSM cell in the BSIC re-confirmation procedure. The time is given in steps of 0.5 seconds. |
REL-5 |
|
|
>Scrambling Code Change List |
CH-SF/2 |
1 to <maxRL> |
REL-5 |
||
|
>>Primary CPICH info |
MP |
Primary CPICH info 10.3.6.60 |
REL-5 |
||
|
>>Scrambling code change |
MP |
Enumerated (code change, no code change) |
Indicates whether the alternative scrambling code is used for compressed mode method ‘SF/2’. |
REL-5 |
|
|
>Serving HS-DSCH cell information |
OP |
Serving HS-DSCH cell information 10.3.6.74a |
REL-12 |
||
|
>DTX-DRX Information |
OP |
DTX-DRX Information 10.3.6.34a |
REL-12 |
||
|
>Uplink secondary cell info FDD |
OP |
Uplink secondary cell info FDD 10.3.6.115 |
REL-12 |
||
|
>DCH Enhancements info FDD |
OP |
DCH Enhancements info FDD 10.3.6.149 |
REL-12 |
||
|
>Downlink information common for all radio links |
OP |
Downlink information common for all radio links 10.3.6.24 |
REL-12 |
||
|
>Downlink information per radio link list |
OP |
1 to <maxRL> |
Send downlink information for each radio link to be set-up |
REL-12 |
|
|
>>Downlink information for each radio link |
MP |
Downlink information for each radio link 10.3.6.27 |
REL-12 |
||
|
Other Information elements |
|||||
|
>Measurement report |
OP |
MEASUREMENT REPORT 10.2.19 |
The source RNC should include the Measurement report the UE sent that triggered the SRNS relocation. This information could e.g. be used by the target RNC to set initial power when establishing a DCH. |
||
|
>Failure cause |
OP |
Failure cause 10.3.3.13 |
Diagnostics information related to an earlier SRNC Relocation request (see NOTE 2 in 14.12.0a) |
||
|
>Protocol error information |
CV-ProtErr |
Protocol error information 10.3.8.12 |
|||
|
UE history information |
OP |
UE history information 10.3.8.23 |
REL-8 |
||
|
MBMS information elements |
|||||
|
MBMS joined information |
OP |
Included if the UE has joined one or more MBMS services |
REL-6 |
||
|
>P-TMSI |
OP |
P-TMSI (GSM-MAP) 10.3.1.13 |
In case the UE is in PMM-Idle |
REL-6 |
|
|
MBMS Selected Service Info |
OP |
MBMS Selected Services Info 10.3.9a.7b |
REL-6 |
|
Multi Bound |
Explanation |
|
MaxNoOfMeas |
Maximum number of active measurements, upper limit 16 |
|
Condition |
Explanation |
|
Setup |
The IE is mandatory present when the IE Measurement command has the value "Setup", otherwise the IE is not needed. |
|
Ciphering |
The IE is mandatory present when the IE Ciphering Status has the value "started" and the ciphering counters need not be reinitialised, otherwise the IE is not needed. |
|
IP |
The IE is mandatory present when the IE Integrity protection status has the value "started" and the integrity protection counters need not be reinitialised, otherwise the IE is not needed. |
|
ProtErr |
This IE is mandatory present if the IE "Protocol error indicator" is included and has the value TRUE. Otherwise it is not needed. |
|
SRB1 |
The IE is mandatory present for RB1. Otherwise it is not needed. |
|
Active |
This IE is mandatory present when the value of the IE "Current TGPS Status Flag" is "Active" and not needed otherwise. |
|
Initial BSIC |
This IE is mandatory present when the value of the IE "TGMP" is set to "GSM Initial BSIC identification" and not needed otherwise. |
|
Re-confirm BSIC |
This IE is mandatory present when the value of the IE "TGMP" is set to "GSM BSIC re-confirmation" and not needed otherwise. |
|
SF/2 |
The IE is mandatory present if the IE “Transmission Gap Pattern Sequence” is included and has the value “SF/2” as the compressed mode method, and already sent the UE the IE “Scrambling Code Change” for each RL in the active set. Otherwise the IE is not needed. |
14.12.4.3 Void
14.12.4.4 RFC 3095 CONTEXT INFO
This RRC message is sent between network nodes in SRNS relocation. It is used to transfer the compressor and decompressor context information of the ROHC protocol.
Direction: source RNC target RNC
|
Information Element/Group name |
Need |
Multi |
Type and reference |
Semantics description |
Version |
|
RFC 3095 context |
MP |
1 to <maxRBallRABs> |
REL-5 |
||
|
>RB identity |
MP |
RB identity 10.3.4.16 |
REL-5 |
||
|
>RFC 3095 context list |
MP |
1 to <maxRFC3095-CID> |
REL-5 |
||
|
>>Downlink RFC 3095 context |
OP |
REL-5 |
|||
|
>>>Downlink RFC 3095 context identity |
MP |
Integer (0..16383) |
REL-5 |
||
|
>>>DL_MODE |
MP |
Enumerated (u, o, r) |
ROHC mode in downlink before SRNS relocation. |
REL-5 |
|
|
>>>REF_IR |
MP |
Octet string (1..3000) |
The RTP IR header (see section 5.7.7 of RFC3095 for detailed format) corresponding to the oldest header in the compressor sliding window. |
REL-5 |
|
|
>>>REF_TIME |
OP |
Integer (0..4294967295) |
Arrival time (at the compressor) of REF_IR in milliseconds. See sections 4.5.4 and 6.5.1 of RFC3095. |
REL-5 |
|
|
>>>CURR_TIME |
OP |
Integer (0..4294967295) |
Current time in milliseconds. See section 6.5.1 of RFC3095. |
REL-5 |
|
|
>>>SYN_OFFSET_ID |
OP |
Integer (0..65535) |
Last synchronized offset of IP-ID. See section 4.5.5 and 6.5.1 of RFC3095 (termed "Offset_I"). It is related to the compression and decompression of IP-ID and is the synchronized offset between the IP-ID value and the SN value (in the same header) during the last SO state before the relocation procedure. |
REL-5 |
|
|
>>>SYN_SLOPE_TS |
OP |
Integer (0..4294967295) |
Last synchronized slope of TS. See sections 5.5.1.2 and 5.7 of RFC3095. In SO state, TS(n) = TS(m) + (n-m) * SYN_SLOPE_TS, where n and m are, the RTP SN of the current and the reference packet, respectively. The unit of SYN_SLOPE_TS depends on whether TS is scaled before compression or not. |
REL-5 |
|
|
>>>DYN_CHANGED |
MP |
Boolean |
Information whether dynamic fields other than RTP SN, RTP TS and IP-ID have changed in the headers that are stored in the sliding window. Set to TRUE if changed and FALSE if not changed. |
REL-5 |
|
|
>>Uplink RFC 3095 context |
OP |
REL-5 |
|||
|
>>>Uplink RFC 3095 context identity |
MP |
Integer (0..16383) |
REL-5 |
||
|
>>>UL_MODE |
MP |
Enumerated (u, o, r) |
ROHC mode in uplink |
REL-5 |
|
|
>>>REF_IR |
MP |
Octet string (1..3000) |
The RTP IR header (see section 5.7.7 of IETF RFC3095 for detailed format) corresponding to the last correctly decompressed header. |
REL-5 |
|
|
>>>REF_TIME |
OP |
Integer (0..4294967295) |
Arrival time (at the decompressor) of REF_IR in milliseconds. See sectionss 4.5.4 and 6.5.1 of RFC3095. |
REL-5 |
|
|
>>>CURR_TIME |
OP |
Integer (0..4294967295) |
Current time in milliseconds. See section 6.5.1 of RFC3095. |
REL-5 |
|
|
>>>SYN_OFFSET_ID |
OP |
Integer (0..65535) |
Last synchronized offset of IP-ID. See sectionss 4.5.5 and 6.5.1 of RFC3095 (termed"Offset_I"). It is related to the compression and decompression of IP-ID and is the synchronized offset between the IP-ID value and the SN value (in the same header) during the last SO state before the relocation procedure. |
REL-5 |
|
|
>>>SYN_SLOPE_TS |
OP |
Integer (0..4294967295) |
Last synchronized slope of TS. See sectionss 5.5.1.2 and 5.7 of RFC3095. In SO state, TS(n) = TS(m) + (n-m) * SYN_SLOPE_TS, where n and m are, the RTP SN of the current and the reference packet, respectively. The unit of SYN_SLOPE_TS depends on whether TS is scaled before compression or not. |
REL-5 |
|
|
>>>REF_SN_1 |
OP |
Integer (0..65535) |
Corresponds to the RTP Sequence Number of the predecessor of the latest RTP packet. This could be used to perform local repair of context by decompressor in U or O mode (see “ref – 1” in section5.3.2.2.5 in IETF RFC3095 for further explanation). |
REL-5 |