10.3.4 Radio Bearer Information elements
25.3313GPPProtocol specificationRadio Resource Control (RRC)Release 17TS
10.3.4.oa Common RB mapping info
NOTE: For FDD and 1.28 Mcps TDD only.
A multiplexing option between a logical channel and a MAC-ehs queue.
|
Information Element/Group name |
Need |
Multi |
Type and reference |
Semantics description |
Version |
|
Logical channel identity |
MP |
Integer(1..15) |
Note |
REL-7 |
|
|
MAC-ehs queue identity |
MP |
MAC-ehs Queue Id 10.3.5.7f |
REL-7 |
NOTE: the IE "Logical channel identity" conveys the value to be used in the "LCH-ID" field of the MAC-ehs header [15] associated with the MAC-ehs reordering queue identified by the IE "MAC-ehs queue identity".
10.3.4.0 Default configuration identity
This information element identifies a default radio parameter configuration. The corresponding default configurations are specified in subclause 13.7.
|
Information Element/Group name |
Need |
Multi |
Type and reference |
Semantics description |
Version |
|
Default configuration identity |
MP |
Integer (0..10, |
See NOTE 1 |
||
|
11, |
REL-4 |
||||
|
13, |
Default configuration ID 2 is not used. |
REL-5 |
|||
|
12, 14, 15, 16 |
REL-6 |
||||
|
17, |
Used only in RRC Connection Setup message. |
REL-6 |
|||
|
18..22, |
See NOTE 1 |
REL-6 |
|||
|
23, |
Default configuration 23 shall not be used in this version of the specification. |
REL-9 |
|||
|
24, |
REL-10 |
||||
|
25..31) |
Reserved for future extension |
REL-10 |
|||
|
NOTE 1: For TDD, default configuration identities 0, 1, 5, 6, 7 and 22 are only valid from REL-10. |
|||||
10.3.4.0a Default configuration for CELL_FACH
This information element identifies a default radio parameter configuration for CELL_FACH. The corresponding default configurations are specified in subclause 13.8.
|
Information Element/Group name |
Need |
Multi |
Type and reference |
Semantics description |
Version |
|
Default configuration mode |
MP |
Enumerated (FDD, TDD) |
Indicates whether the FDD or TDD version of the default configuration shall be used |
REL-8 |
|
|
Default configuration identity for CELL_FACH |
MP |
Integer (0, |
REL-8 |
||
|
1..15) |
Reserved for future extension |
REL-8 |
10.3.4.1 Downlink RLC STATUS info
|
Information Element/Group name |
Need |
Multi |
Type and reference |
Semantics description |
Version |
|---|---|---|---|---|---|
|
Timer_Status_Prohibit |
OP |
Integer(10..550 by step of 10, 550..1000 by step of 50) |
Minimum time in ms between STATUS reports |
||
|
Missing PDU Indicator |
MP |
Boolean |
Value TRUE indicates that UE should send a STATUS report for each missing PDU that is detected |
||
|
Timer_STATUS_periodic |
OP |
Integer(100,200, 300, 400, 500, 750, 1000, 2000) |
Time in milliseconds |
||
|
Timer_Reordering |
CV-Multiflow |
Integer(50,100,150,200,400,600,800,1000) |
Time in milliseconds for which a UE should wait upon encountering a gap in the RLC sequence numbers. NOTE1. |
REL-11 |
|
|
NOTE1: If this IE is included for SRB0 or SRB1, then the UE behaviour is unspecified. |
|||||
|
Condition |
Explanation |
|
Multiflow |
The IE is optional when the Multiflow operation is configured, otherwise it is not needed. |
10.3.4.1a PDCP context relocation info
This information element indicates that the header compression context relocation is to be performed during SRNS relocation for the given radio bearer.
|
Information Element/Group name |
Need |
Multi |
Type and reference |
Semantics description |
Version |
|
RB identity |
MP |
RB identity 10.3.4.16 |
REL-5 |
||
|
Downlink RFC 3095 context relocation indication |
MP |
Boolean |
TRUE means RFC 3095 context relocation is performed in downlink |
REL-5 |
|
|
Uplink RFC 3095 context relocation indication |
MP |
Boolean |
TRUE means RFC 3095 context relocation is performed in uplink |
REL-5 |
10.3.4.2 PDCP info
The purpose of the PDCP info IE is to indicate which algorithms shall be established and to configure the parameters of each of the algorithms.
|
Information Element/Group name |
Need |
Multi |
Type and reference |
Semantics description |
Version |
|---|---|---|---|---|---|
|
Support for lossless SRNS relocation or for lossless DL RLC PDU size change |
CV-LosslessCriteria |
Boolean |
TRUE means support |
||
|
Max PDCP SN window size |
CV-Lossless |
Enumerated(sn255, sn65535) |
Maximum PDCP sequence number window size. The handling of sequence number when the Max PDCP SN window size is 255 is specified in [23]. |
||
|
PDCP PDU header |
MP |
Enumerated (present, absent) |
Whether a PDCP PDU header is existent or not. |
||
|
Header compression information |
OP |
1 to <maxPDCPAlgoType> |
|||
|
>CHOICE algorithm type |
MP |
Note 1 |
|||
|
>>RFC 2507 |
Header compression according to IETF standard RFC 2507 |
||||
|
>>>F_MAX_PERIOD |
MD |
Integer (1..65535) |
Largest number of compressed non-TCP headers that may be sent without sending a full header. Default value is 256. |
||
|
>>>F_MAX_TIME |
MD |
Integer (1..255) |
Compressed headers may not be sent more than F_MAX_TIME seconds after sending last full header. Default value is 5. |
||
|
>>>MAX_HEADER |
MD |
Integer (60..65535) |
The largest header size in octets that may be compressed. Default value is 168. |
||
|
>>>TCP_SPACE |
MD |
Integer (3..255) |
Maximum CID value for TCP connections. Default value is 15. |
||
|
>>>NON_TCP_SPACE |
MD |
Integer (3..65535) |
Maximum CID value for non-TCP connections. Default value is 15. |
||
|
>>>EXPECT_REORDERING |
MD |
Enumerated (reordering not expected, reordering expected) |
Whether the algorithm shall reorder PDCP SDUs or not. Default value is "reordering not expected". |
||
|
>>RFC 3095 |
Header compression according to IETF ROHC standard [83], [84]. |
REL-4 |
|||
|
>>>Profiles |
MP |
1 to <maxROHC- Profiles> |
Profiles supported by both compressor and decompressor in both UE and UTRAN. Profile 0 shall always be supported. |
REL-4 |
|
|
>>>>Profile instance |
MP |
Integer(1.. 3) |
1 = 0x0001, 2 = 0x0002, 3 = 0x0003 (see [52]) |
REL-4 |
|
|
>>>Uplink |
OP |
Indicates the necessary information elements for Uplink. |
REL-4 |
||
|
>>>>Max_CID |
MD |
Integer (1.. 16383) |
Highest context ID number to be used by the UE compressor. Default value is 15. |
REL-4 |
|
|
>>>Downlink |
OP |
Indicates the necessary information elements for Downlink. |
REL-4 |
||
|
>>>>Max_CID |
MD |
Integer (1.. 16383) |
Highest context ID number to be used by the UE decompressor. Default value is 15. |
REL-4 |
|
|
>>>>Reverse_Decompression_Depth |
MD |
Integer (0..65535) |
Determines whether reverse decompression should be used or not and the maximum number of packets that can be reverse decompressed by the UE decompressor. Default value is 0 (reverse decompression shall not be used). |
REL-4 |
|
|
Note 1: If several occurrences of the same algorithm type are included in the same IE “header compression information”, the UE behaviour is unspecified. |
|||||
|
Condition |
Explanation |
|
LosslessCriteria |
This IE is mandatory present if the IE "RLC mode" is "Acknowledged", the IE "In-sequence delivery " is TRUE and the IE "SDU Discard Mode" is "No discard" and not needed otherwise. |
|
Lossless |
This IE is mandatory present if the IE "Support for lossless SRNS relocation or for lossless RLC PDU size change" Is TRUE, otherwise it is not needed. |
10.3.4.2a PDCP ROHC target mode
|
Information Element/Group name |
Need |
Multi |
Type and Reference |
Semantics description |
Version |
|
Target Mode |
MP |
Enumerated (O-mode, R-mode) |
The UE shall only transit to the signalled mode for operation of ROHC as decribed in [36]. |
REL-5 |
10.3.4.3 PDCP SN info
|
Information Element/Group name |
Need |
Multi |
Type and Reference |
Semantics description |
|
Receive PDCP sequence number |
MP |
Integer(0..65535) |
The PDCP sequence number, which the sender of the message is expecting next to be received. |
10.3.4.4 Polling info
|
Information Element/Group name |
Need |
Multi |
Type and reference |
Semantics description |
|
Timer_poll_prohibit |
OP |
Integer(10..550 by step of 10, 600..1000 by step of 50) |
Minimum time between polls in ms |
|
|
Timer_poll |
OP |
Integer(10..550 by step of 10, 600..1000 by step of 50) |
Time in ms. |
|
|
Poll_PDU |
OP |
Integer(1,2,4,8,16,32,64,128) |
Number of PDUs, interval between pollings |
|
|
Poll_SDU |
OP |
Integer(1,4,16,64) |
Number of SDUs, interval between pollings |
|
|
Last transmission PDU poll |
MP |
Boolean |
TRUE indicates that poll is made at last PDU in transmission buffer |
|
|
Last retransmission PDU poll |
MP |
Boolean |
TRUE indicates that poll is made at last PDU in retransmission buffer |
|
|
Poll_Window |
OP |
Integer(50,60,70,80,85,90,95,99) |
Percentage of transmission window, threshold for polling |
|
|
Timer_poll_periodic |
OP |
Integer(100,200, 300, 400, 500, 750, 1000, 2000) |
Time in milliseconds Timer for periodic polling. |
10.3.4.5 Predefined configuration identity
This information element identifies a pre- defined radio parameter configuration.
|
Information Element/Group name |
Need |
Multi |
Type and reference |
Semantics description |
|
Predefined radio configuration identity |
MP |
Integer (0..15) |
10.3.4.5a Predefined configuration status information
Another system may provide the UE with one or more predefined UTRAN configurations, comprising of radio bearer, transport channel and physical channel parameters. If requested, the UE shall indicate the configurations it has stored. The predefined configuration status information should include the following RRC information.
|
Information Element/Group name |
Need |
Multi |
Type and reference |
Semantics description |
|---|---|---|---|---|
|
RB information elements |
||||
|
Predefined configurations |
maxPredefConfigCount |
The list is in order of preconfiguration identity |
||
|
>Predefined configuration value tag |
OP |
Predefined configuration value tag 10.3.4.6 |
The UE shall include the value tag if it has stored the concerned configuration |
|
Multi Bound |
Explanation |
|
MaxPredefConfigCount |
Maximum number of predefined configurations |
10.3.4.5b Predefined configuration status information compressed
Another system may provide the UE with one or more predefined UTRAN configurations, comprising of radio bearer, transport channel and physical channel parameters. If requested, the UE shall indicate the configurations it has stored. The compressed predefined configuration status information should include the following RRC information.
|
Information Element/Group name |
Need |
Multi |
Type and reference |
Semantics description |
Version |
|---|---|---|---|---|---|
|
Sets with different value tags |
MP |
REL-5 |
|||
|
>Pre-defined configuration set with different value tags |
MP |
1..2 |
REL-5 |
||
|
>>Start position |
MD |
INTEGER (0..10) |
Default value is 0, corresponding with the first pre- defined configuration. The pre-defined configuration where the consecutive sequence of pre-defined configurations begins. |
REL-5 |
|
|
>>Pre-defined configuration value tag list |
MP |
6..<maxPredefConfig> |
Pre-defined configuration value tag 10.3.4.6 |
Value Tags for each pre-defined configuration starting from the lowest. |
REL-5 |
|
Other Entries |
OP |
REL-5 |
|||
|
>Pre-defined configuration list with variable size |
MP |
1..<maxPredefConfig> |
List of other pre-defined configurations not included within the Sets with different value tags, in consecutive order starting with the lowest. If there are stored pre-defined configurations positioned after a pre-defined configuration that is not stored, the UE shall indicate the not-stored pre-defined configuration by explicitly indicating it to be absent. If there are no stored pre-defined configurations positioned after a pre-defined configuration that is not stored, then the UE may totally omit these pre-defined configurations from the IE, i.e. reduce the size of the list to correspond to the last position that contained a stored pre-defined configuration. |
REL-5 |
|
|
>>Predefined configuration value tag |
OP |
Predefined configuration value tag 10.3.4.6 |
The UE shall include the value tag if it has stored the concerned configuration |
REL-5 |
10.3.4.6 Predefined configuration value tag
This information element is used to identify different versions of a radio bearer configuration as may be used within one PLMN e.g. to support different UTRAN implementations.
|
Information Element/Group name |
Need |
Multi |
Type and Reference |
Semantics description |
|
Predefined configuration value tag |
MP |
Integer(0..15) |
10.3.4.7 Predefined RB configuration
This information element concerns a pre- defined configuration of radio bearer parameters
|
Information Element/Group name |
Need |
Multi |
Type and Reference |
Semantics description |
|
UE information elements |
||||
|
Re-establishment timer |
MP |
Re-establishment timer 10.3.3.30 |
Only one RAB supported |
|
|
Signalling radio bearer information |
||||
|
Signalling RB information to setup List |
MP |
1 to <maxSRBsetup> |
For each signalling radio bearer |
|
|
>Signalling RB information to setup |
MP |
Signalling RB information to setup 10.3.4.24 |
||
|
RB information |
Only one RAB supported |
|||
|
RB information to setup list |
MP |
1 to <maxRBperRAB> |
||
|
>RB information to setup |
MP |
RB information to setup 10.3.4.20 |
10.3.4.8 RAB info
This IE contains information used to uniquely identify a radio access bearer.
|
Information Element/Group name |
Need |
Multi |
Type and reference |
Semantics description |
Version |
|
RAB identity |
MP |
RAB identity 10.3.1.14 |
|||
|
MBMS Service Identity |
CV-Message |
MBMS service ID 10.3.9a.8a |
Included when establishing a RB for a MBMS service of the broadcast type; NOTE 1 |
REL-6 |
|
|
MBMS Session identity |
CV-Message |
MBMS Session identity 10.3.9a.9 |
REL-6 |
||
|
CN domain identity |
MP |
CN domain identity 10.3.1.1 |
|||
|
NAS Synchronization Indicator |
OP |
NAS Synchronization indicator 10.3.4.12 |
|||
|
Re-establishment timer |
MP |
Re-establishment timer 10.3.3.30 |
|||
|
NOTE 1: Only the "MBMS Service ID" part of the MBMS service identity is signalled in this IE. The UE should consider that the "PLMN identity" part of the MBMS service identity equals the PLMN identity of an MBMS service with the same "MBMS Service ID" stored in the variable ACTIVATED_MBMS_SERVICES. If there is no such MBMS service or more than one such MBMS service, the UE behaviour is unspecified. |
|||||
|
Condition |
Explanation |
|
Message |
This IE is optionally present in the RADIO BEARER SETUP and the SRNS RELOCATION INFO messages and not needed otherwise. |
10.3.4.9 RAB info Post
This IE contains information used to uniquely identify a radio access bearer.
|
Information Element/Group name |
Need |
Multi |
Type and reference |
Semantics description |
|
RAB identity |
MP |
RAB identity 10.3.1.14 |
||
|
CN domain identity |
MP |
CN domain identity 10.3.1.1 |
||
|
NAS Synchronization Indicator |
OP |
NAS Synchronization indicator 10.3.4.12 |
10.3.4.9a RAB information for MBMS ptp bearers
|
Information Element/Group name |
Need |
Multi |
Type and reference |
Semantics description |
Version |
|---|---|---|---|---|---|
|
RB identity |
MP |
RB identity 10.3.4.16 |
REL-7 |
||
|
MBMS Service Identity |
MP |
MBMS Service ID 10.3.9a.8a |
Indicates that this radio bearer is used for a different MBMS service. |
REL-7 |
|
|
MBMS Session Identity |
OP |
MBMS Session identity 10.3.9a.9 |
Indicates that this radio bearer is used for a different session of the MBMS service. |
REL-7 |
10.3.4.10 RAB information for setup
|
Information Element/Group name |
Need |
Multi |
Type and reference |
Semantics description |
Version |
|
RAB info |
MP |
RAB info 10.3.4.8 |
|||
|
CS-HSPA information |
CV-CS |
REL-8 |
|||
|
>UL AMR rate |
MD |
Enumerated (t0, t1, t2, t3, t4, t5, t6, t7, t8) |
Indicates the bit rate as defined in [62] and [63]. In case NAS Synchronization Indicator indicates AMR, default value is “t7”. In case NAS Synchronization Indicator indicates AMR-WB, default value is “t8“. 7 spare values are needed. |
REL-8 |
|
|
>Max CS delay |
MP |
Integer (20..200 by step of 10) |
Indicates the maximum possible delay for CS voice frames Unit is ms |
REL-8 |
|
|
RAB info to replace |
CV-SRVCC |
RAB info to replace 10.3.4.11a |
REL-8 |
||
|
RB information to setup list |
MP |
1 to <maxRBperRAB> |
|||
|
>RB information to setup |
MP |
RB information to setup 10.3.4.20 |
|
Condition |
Explanation |
|
CS |
This IE is mandatory if the IE “CN domain identity” has the value “CS domain” and the RAB is mapped on HS-DSCH/E-DCH. It is not needed otherwise. |
|
SRVCC |
This IE is mandatory if the RAB is established as part of an SR-VCC procedure and the message is not HANDOVER TO UTRAN COMMAND message and not needed otherwise. |
10.3.4.11 RAB information to reconfigure
|
Information Element/Group name |
Need |
Multi |
Type and reference |
Semantics description |
Version |
|---|---|---|---|---|---|
|
RAB identity |
MP |
RAB Identity 10.3.1.14 |
|||
|
CN domain identity |
MP |
CN domain identity 10.3.1.1 |
|||
|
NAS synchronization indicator |
MP |
NAS Synchronization info 10.3.4.12 |
Note 1 |
||
|
CS-HSPA information |
CV-CS |
REL-8 |
|||
|
>UL AMR rate |
MD |
Enumerated(t0, t1, t2, t3, t4, t5, t6, t7, t8) |
Indicates the bit rate as defined in [62] and [63]. In case NAS Synchronization Indicator indicates AMR, default value is “t7”. In case NAS Synchronization Indicator indicates AMR-WB, default value is “t8“. 7 spare values are needed. |
REL-8 |
|
|
>Max CS delay |
MP |
Integer(20..200 by step of 10) |
Indicates the maximum possible delay for CS voice frames Unit is ms |
REL-8 |
|
Condition |
Explanation |
|
CS |
This IE is mandatory if the IE “CN domain identity” has the value “CS domain” and the RAB is mapped on HS-DSCH/E-DCH. It is not needed otherwise. |
NOTE 1: This IE is only relevant for the CS domain.
10.3.4.11a RAB info to replace
This IE contains information to identify a radio access bearer to be replaced with a new radio access bearer as part of SR-VCC procedures. This IE is not included in case SR-VCC from LTE to UMTS.
|
Information Element/Group name |
Need |
Multi |
Type and reference |
Semantics description |
Version |
|
RAB identity |
MP |
RAB identity 10.3.1.14 |
REL-8 |
||
|
CN domain identity |
MP |
CN domain identity 10.3.1.1 |
REL-8 |
10.3.4.12 NAS Synchronization indicator
A container for non-access stratum information to be transferred transparently through UTRAN.
|
Information Element/Group name |
Need |
Multi |
Type and reference |
Semantics description |
|
NAS Synchronization indicator |
MP |
Bit string(4) |
The first/leftmost bit of the bit string contains the most significant bit of the NAS Synchronization indicator. |
10.3.4.13 RB activation time info
This IE contains the time, in terms of RLC sequence numbers, when a certain configuration shall be activated, for a number of radio bearers.
|
Information Element/Group name |
Need |
Multi |
Type and reference |
Semantics description |
|
Radio bearer activation time |
MP |
1 to <maxRB> |
||
|
>RB identity |
MP |
RB identity 10.3.4.16 |
||
|
>RLC sequence number |
MP |
Integer (0.. 4095) |
RLC SN [16] . |
10.3.4.14 RB COUNT-C MSB information
The MSB of the COUNT-C values of the radio bearer.
|
Information Element/Group name |
Needed |
Multi |
Type and reference |
Semantics description |
|
RB identity |
MP |
RB identity 10.3.4.16 |
||
|
COUNT-C-MSB-uplink |
MP |
Integer (0.. 2^25-1) |
25 MSBs from COUNT-C associated to this RB |
|
|
COUNT-C-MSB-downlink |
MP |
Integer (0.. 2^25-1) |
25 MSBs from COUNT-C associated to this RB |
10.3.4.15 RB COUNT-C information
The COUNT-C values of the radio bearer.
|
Information Element/Group name |
Needed |
Multi |
Type and reference |
Semantics description |
|
RB identity |
MP |
RB identity 10.3.4.16 |
||
|
COUNT-C-uplink |
MP |
Integer (0.. 2^32-1) |
||
|
COUNT-C-downlink |
MP |
Integer (0.. 2^32-1) |
10.3.4.16 RB identity
An identification number for the radio bearer affected by a certain message.
|
Information Element/Group name |
Need |
Multi |
Type and reference |
Semantics description |
|
RB identity |
MP |
Integer(1..32) |
Values 1-4 shall only be used for signalling radio bearers. The IE value minus one shall be used as BEARER in the ciphering algorithm. |
10.3.4.17 RB information to be affected
|
Information Element/Group name |
Need |
Multi |
Type and reference |
Semantics description |
|
RB identity |
MP |
RB identity 10.3.4.16 |
||
|
RB mapping info |
MP |
RB mapping info 10.3.4.21 |
10.3.4.18 RB information to reconfigure
|
Information Element/Group name |
Need |
Multi |
Type and reference |
Semantics description |
|
RB identity |
MP |
RB identity 10.3.4.16 |
||
|
PDCP info |
OP |
PDCP info 10.3.4.2 |
||
|
PDCP SN info |
OP |
PDCP SN info 10.3.4.3 |
PDCP sequence number info from the network. Present only in case of lossless SRNS relocation. |
|
|
RLC info |
OP |
RLC info 10.3.4.23 |
||
|
RB mapping info |
OP |
RB mapping info 10.3.4.21 |
||
|
RB stop/continue |
OP |
Enumerated(stop, continue) |
10.3.4.19 RB information to release
|
Information Element/Group name |
Need |
Multi |
Type and reference |
Semantics description |
|
RB identity |
MP |
RB identity 10.3.4.16 |
10.3.4.20 RB information to setup
|
Information Element/Group name |
Need |
Multi |
Type and reference |
Semantics description |
|---|---|---|---|---|
|
RB identity |
MP |
RB identity 10.3.4.16 |
||
|
PDCP info |
OP |
PDCP info 10.3.4.2 |
||
|
CHOICE RLC info type |
MP |
|||
|
>RLC info |
RLC info 10.3.4.23 |
|||
|
>Same as RB |
RB identity 10.3.4.16 |
Identity of RB with exactly the same RLC info IE values |
||
|
RB mapping info |
MP |
RB mapping info 10.3.4.21 |
NOTE: This information element is included within IE "Predefined RB configuration".
10.3.4.21 RB mapping info
A multiplexing option for each possible transport channel MAC-d flow or E-DCH MAC-d flow this RB can be multiplexed on.
|
Information Element/Group name |
Need |
Multi |
Type and reference |
Semantics description |
Version |
|
|---|---|---|---|---|---|---|
|
Information for each multiplexing option |
MP |
1 to <maxRBMuxOptions> |
||||
|
>RLC logical channel mapping indicator |
CV-UL-RLCLogicalChannels |
Boolean |
TRUE indicates that the first logical channel shall be used for data PDUs and the second logical channel shall be used for control PDUs. FALSE indicates that control and data PDUs can be sent on either of the two logical channels. This parameter is not used in this release and shall be set to TRUE. |
|||
|
>Number of uplink RLC logical channels |
CV-UL-RLC info |
1 to MaxLoCHperRLC |
1 or 2 logical channels per RLC entity or radio bearer RLC [16] |
|||
|
>>CHOICE Uplink transport channel type |
REL-6 |
|||||
|
>>>DCH, RACH, USCH |
REL-6 |
|||||
|
>>>>Uplink transport channel type |
MP |
Enumerated(DCH,RACH,USCH |
USCH is TDD only |
|||
|
>>>>ULTransport channel identity |
CV-UL-DCH/USCH |
Transport channel identity 10.3.5.18 |
This is the ID of a DCH or USCH (TDD only) that this RB could be mapped onto. |
|||
|
>>>>Logical channel identity |
OP |
Integer(1..15) |
This parameter is used to distinguish logical channels multiplexed by MAC on a transport channel. |
|||
|
>>>>CHOICE RLC size list |
MP |
The RLC sizes that are allowed for this logical channel. |
||||
|
>>>>>All |
Null |
All RLC sizes listed in the Transport Format Set. 10.3.5.23 |
||||
|
>>>>>Configured |
Null |
The RLC sizes configured for this logical channel in the Transport Format Set. 10.3.5.23 if present in this message or in the previously stored configuration otherwise |
||||
|
>>>>>Explicit List |
1 to <maxTF> |
Lists the RLC sizes that are valid for the logical channel. |
||||
|
>>>>>>RLC size index |
MP |
Integer(1..maxTF) |
The integer number is a reference to the RLC size which arrived at that position in the Transport Format Set 10.3.5.23 |
|||
|
>>>E-DCH |
Note 4 |
REL-6 |
||||
|
>>>>Logical channel identity |
MP |
Integer(1..15) |
This parameter is used to distinguish logical channels multiplexed by MAC on a transport channel |
REL-6 |
||
|
>>>>E-DCH MAC-d flow identity |
MP |
E-DCH MAC-d flow identity 10.3.5.7e |
REL-6 |
|||
|
>>>>CHOICE RLC PDU size |
MP |
REL-8 |
||||
|
>>>>>Fixed size |
REL-8 |
|||||
|
>>>>>>DDI |
MP |
Integer (0..62) |
If more than 1 UL RLC PDU size is configured for this RB, the different sizes will use subsequent DDI values starting from this DDI value. Value “0x3F” is reserved Note 6 |
REL-6 |
||
|
>>>>>>RLC PDU size list |
MP |
1 to <maxRLCPDUsizePerLogChan> |
REL-6 |
|||
|
>>>>>>>RLC PDU size |
MP |
Integer(16..5000 by step of 8) |
Unit is bits |
REL-6 |
||
|
>>>>>Flexible size |
REL-8 |
|||||
|
>>>>>>Length indicator size |
CV-UL-RLC AM mode |
Enumerated (7-bit, 15-bit) |
REL-8 |
|||
|
>>>>>>Minimum UL RLC PDU size |
MP |
Integer (16..12040 by step of 8) |
Unit is bits |
REL-8 |
||
|
>>>>>>Largest UL RLC PDU size |
MP |
Integer (16..12040 by step of 8) |
Unit is bits |
REL-8 |
||
|
>>>>Include in Scheduling Info |
MP |
Boolean |
Indicates whether or not this logical channel is to be considered when performing scheduling info reporting, as per [15] |
REL-6 |
||
|
>>MAC logical channel priority |
MP |
Integer(1..8) |
This is priority between a user’s different RBs (or logical channels). [15] |
|||
|
>Downlink RLC logical channel info |
CV-DL-RLC info |
|||||
|
>>Number of downlink RLC logical channels |
MD |
1 to MaxLoCHperRLC |
1 or 2 logical channels per RLC entity or radio bearer RLC [16] Default value is that parameter values for DL are exactly the same as for corresponding UL logical channel. In case two multiplexing options are specified for the UL, the first options shall be used as default for the DL. As regards to the IE "Channel type", rule is specified in 8.6.4.8. |
|||
|
>>>Downlink transport channel type |
MP |
Enumerated(DCH,FACH,DSCH,DCH+DSCH |
Note 3 |
|||
|
, HS-DSCH, DCH + HS-DSCH) |
Note 4 |
REL-5 |
||||
|
>>>DL DCH Transport channel identity |
CV-DL-DCH |
Transport channel identity 10.3.5.18 |
||||
|
>>>DL DSCH Transport channel identity |
CV-DL-DSCH |
Transport channel identity 10.3.5.18 |
||||
|
>>>CHOICE DL MAC header type |
CV-DL-HS-DSCH |
Depending on the MAC-hs/ehs type of header selected for HS-DSCH |
REL-7 |
|||
|
>>>>MAC-hs |
REL-7 |
|||||
|
>>>>>DL HS-DSCH MAC-d flow identity |
MP |
MAC-d flow identity 10.3.5.7c |
REL-5 |
|||
|
>>>>MAC-ehs |
REL-7 |
|||||
|
>>>>>DL HS-DSCH MAC-ehs Queue Id |
MP |
MAC-ehs Queue Id 10.3.5.7f |
Note 5 |
REL-7 |
||
|
>>>Logical channel identity |
OP |
Integer(1..15) |
16 is reserved Note 5 |
|||
|
Note 3: The IE "Downlink transport channel type" values " DSCH” and “DCH+DSCH " should not be used for FDD. If received the UE behaviour is unspecified. |
||||||
|
Note 4: If included in System Information Block Type 16, the values ‘HS-DSCH’ and ‘DCH + HS-DSCH’ do not apply for the IE "Downlink transport channel type". Furthermore, if included in System Information Block Type 16, the value "E-DCH” for the IE "Uplink transport channel type" does not apply. |
||||||
|
Note 5: If the IE "Downlink transport channel type" is "HS-DSCH" or "DCH + HS-DSCH" and the DL MAC header type is "MAC-ehs", the IE "Logical channel identity" conveys the value to be used in the "LCH-ID" field of the MAC-ehs header [15], associating the logical channel with the MAC-ehs reordering queue identified by the IE "DL HS-DSCH MAC-ehs Queue Id". |
||||||
|
Note 6: If the radio bearer has a multiplexing option configured with the UL MAC header type of "MAC-i/is" then this value is ignored. |
||||||
|
Condition |
Explanation |
|
UL-RLC info |
If "CHOICE Uplink RLC mode" in the IE "RLC info" that applies for that RB (i.e. either the one stored or received in the same message for the RB for which the "RB mapping info" was received, or the one stored or received in the same message for the RB pointed at in the IE "Same as RB" in the IE "RB information to setup" stored or received in the same message) is present this IE is mandatory present. Otherwise the IE is not needed. |
|
DL-RLC info |
If "CHOICE Downlink RLC mode" in the IE "RLC info" that applies for that RB (i.e. either the one stored or received in the same message for the RB for which the "RB mapping info" was received, or the one stored or received in the same message for the RB pointed at in the IE "Same as RB" in the IE "RB information to setup" stored or received in the same message) is present this IE is mandatory present. Otherwise the IE is not needed. |
|
UL-RLCLogicalChannels |
If "Number of uplink RLC logical channels" in IE "RB mapping info" is 2, then this IE is mandatory present. Otherwise this IE is not needed. |
|
UL-DCH/USCH |
If IE "Uplink transport channel type" is equal to "DCH" or "USCH" (TDD only) this IE is mandatory present. Otherwise the IE is not needed. |
|
DL-DCH |
If IE "Downlink transport channel type" is equal to "DCH", "DCH+DSCH" or “DCH + HS-DSCH” this IE is mandatory present. Otherwise the IE is not needed. |
|
DL-DSCH |
If IE "Downlink transport channel type" is equal to "DSCH" or "DCH+DSCH" this IE is mandatory present. Otherwise the IE is not needed. |
|
DL-HS-DSCH |
If IE "Downlink transport channel type" is equal to "HS-DSCH" or “DCH + HS-DSCH” this IE is mandatory present. Otherwise the IE is not needed. |
|
UL-RLC AM mode |
If "CHOICE Uplink RLC mode" in the IE "RLC info" that applies for that RB (i.e. either the one stored or received in the same message for the RB for which the "RB mapping info" was received, or the one stored or received in the same message for the RB pointed at in the IE "Same as RB" in the IE "RB information to setup" stored or received in the same message) is “AM RLC “ this IE is mandatory present. Otherwise the IE is not needed. |
10.3.4.22 RB with PDCP information
|
Information Element/Group name |
Need |
Multi |
Type and reference |
Semantics description |
Version |
|
RB identity |
MP |
RB identity 10.3.4.16 |
|||
|
PDCP SN info |
MP |
PDCP SN info 10.3.4.3 |
PDCP sequence number info from the sender of the message for lossless SRNS relocation. |
||
|
PDCP sequence number info from the sender of the message for lossless SRNS relocation or for lossless DL RLC PDU size change. |
REL-5 |
10.3.4.23 RLC info
|
Information Element/Group name |
Need |
Multi |
Type and reference |
Semantics description |
Version |
|---|---|---|---|---|---|
|
CHOICE Uplink RLC mode |
OP |
Indicates if Acknowledged, Unacknowledged or Transparent mode RLC shall be used. |
|||
|
>AM RLC |
|||||
|
>>Transmission RLC discard |
MP |
Transmission RLC discard 10.3.4.25 |
|||
|
>>Transmission window size |
MP |
Integer(1,8,16,32,64,128,256,512,768,1024,1536,2047,2560,3072,3584,4095) |
Maximum number of RLC PUs sent without getting them acknowledged. This parameter is needed if acknowledged mode is used. UE shall also assume that the UTRAN receiver window is equal to this value. |
||
|
>>Timer_RST |
MP |
Integer(50, 100, 150, 200, 250, 300, 350, 400, 450, 500, 550, 600, 700, 800, 900, 1000) |
Elapsed time in milliseconds. It is used to trigger the retransmission of RESET PDU. |
||
|
>>Max_RST |
MP |
Integer(1, 4, 6, 8, 12 16, 24, 32) |
Defined in [16]. If other values than 1 are used for SRB2 the UE behaviour is unspecified. |
||
|
>>Polling info |
OP |
Polling info 10.3.4.4 |
|||
|
>UM RLC |
|||||
|
>>Transmission RLC discard |
CV-CS-HSPA |
Transmission RLC discard 10.3.4.25 |
NOTE 3 |
||
|
>TM RLC |
|||||
|
>>Transmission RLC discard |
OP |
Transmission RLC discard 10.3.4.25 |
|||
|
>>Segmentation indication |
MP |
Boolean |
TRUE indicates that segmentation is performed. |
||
|
CHOICE Downlink RLC mode |
OP |
Indicates if Acknowledged, Unacknowledged or Transparent mode RLC shall be used |
|||
|
>AM RLC |
|||||
|
>>CHOICE DL RLC PDU size |
MP |
REL-7 |
|||
|
>>>Fixed size |
REL-7 |
||||
|
>>>>DL RLC PDU size |
MP |
Integer(16..5000 by step of 8) |
Unit is bits |
REL-5 |
|
|
>>>Flexible size |
NOTE 1 |
REL-7 |
|||
|
>>>>Length indicator size |
MP |
Enumerated (7-bit, 15-bit) |
REL-7 |
||
|
>>In-sequence delivery |
MP |
Boolean |
TRUE indicates that RLC shall preserve the order of higher layer PDUs when these are delivered. FALSE indicates that receiving RLC entity could allow SDUs to be delivered to the higher layer in different order than submitted to RLC sublayer at the transmitting side. |
||
|
>>Receiving window size |
MP |
Integer(1,8,16,32,64,128,256,512,768,1024,1536,2047,2560,3072,3584,4095) |
Maximum number of RLC PUs allowed to be received. This parameter is needed if acknowledged mode is used. UE shall also assume that the UTRAN transmitter window is equal to this value |
||
|
>>Downlink RLC status Info |
MP |
Downlink RLC status info 10.3.4.1 |
|||
|
>UM RLC |
|||||
|
>>DL UM RLC LI size |
MP |
Integer(7, 15) |
Size in bits to use for the downlink RLC UM LI. |
REL-5 |
|
|
>>DL Reception Window Size |
CV-Not-SIB16o |
Integer(32, 48, 64, 80, 96, 112) |
REL-6 |
||
|
>TM RLC |
|||||
|
>>Segmentation indication |
MP |
Boolean |
TRUE indicates that segmentation is performed. |
||
|
One sided RLC re-establishment |
MP |
Boolean |
TRUE indicates that only one side of the AM RLC entity is re-established. |
REL-5 |
|
|
Alternative E-bit interpretation |
CV-Not-SIB16o |
Enumerated (TRUE) |
The absence of this IE implies: "normal E-bit interpretation". |
REL-6 |
|
|
Use special value of HE field |
CV-Not-SIB16o |
Enumerated (TRUE) |
The absence of this IE implies: “do not use special value of the HE field in the uplink RLC entity”. |
REL-7 |
|
|
NOTE 1: If included in SIB type 16, the "Flexible size" does not apply for downlink RLC PDU size (AM RLC). |
|||||
|
NOTE 2: Void. |
|||||
|
NOTE 3: If this IE is absent and the radio bearer is connected to a CS domain radio access bearer, the UE behaviour is unspecified. |
|||||
|
Condition |
Explanation |
|
Not-SIB16o |
If included in System Information Block Type 16, this IE is not needed. Otherwise the IE is optional |
|
CS-HSPA |
This IE is mandatory present If the radio bearer is connected to a CS domain radio access bearer, Otherwise the IE is optional. |
NOTE: This information element is included within IE "Predefined RB configuration".
10.3.4.23a RLC info MBMS
The IE RLC info MBMS is used for point-to-multipoint radio bearers, featuring only the downlink RLC UMD.
|
Information Element/Group name |
Need |
Multi |
Type and reference |
Semantics description |
Version |
|---|---|---|---|---|---|
|
DL UM RLC LI size |
MP |
Integer (7, 15) |
Size in bits to use for the downlink RLC UM LI. |
REL-6 |
|
|
DL Duplication Avoidance and Reordering info |
CV-MTCH |
UM Duplication Avoidance and Reordering info 10.3.4.26 |
REL-6 |
||
|
DL Out of sequence delivery info |
CV-MCCH |
UM Out of sequence delivery info 10.3.4.27 |
REL-6 |
|
Condition |
Explanation |
|
MTCH |
If the IE concerns MTCH (see Note 1), this IE is optional. Otherwise the IE is not needed. |
|
MCCH |
If the IE concerns MCCH, this IE is optional. Otherwise the IE is not needed. |
NOTE 1: The UE behaviour is unspecified if this IE is received with regard to an MTCH configured for MBSFN operation. A network should not send this IE with regard to an MTCH configured for MBSFN operation.
10.3.4.24 Signalling RB information to setup
|
Information Element/Group name |
Need |
Multi |
Type and reference |
Semantics description |
|
RB identity |
MD |
RB identity 10.3.4.16 |
Default value is specified in subclause 8.6.4.1 |
|
|
CHOICE RLC info type |
MP |
|||
|
>RLC info |
RLC info 10.3.4.23 |
|||
|
>Same as RB |
RB identity 10.3.4.16 |
Identity of RB with exactly the same RLC info IE values |
||
|
RB mapping info |
MP |
RB mapping info 10.3.4.21 |
NOTE: This information element is included within IE "Predefined RB configuration".
10.3.4.24a SR-VCC Info
This IE contains information that allows the calculation of the CK and IK for the CS domain, due to a SR-VCC procedure.
|
Information Element/Group name |
Need |
Multi |
Type and reference |
Semantics description |
Version |
|
NONCE |
OP |
Bit string (128) |
REL-8 |
10.3.4.25 Transmission RLC Discard
|
Information Element/Group name |
Need |
Multi |
Type and reference |
Semantics description |
|---|---|---|---|---|
|
CHOICE SDU Discard Mode |
MP |
Different modes for discharge the RLC buffer on the transmitter side; "Timer based with explicit signalling", "Timer based without explicit signalling", "Discard after Max_DAT retransmissions" or "No_discard". For unacknowledged mode and transparent mode, only Timer based without explicit signalling is applicable. If "No_discard" is used, reset procedure shall be done after Max_DAT retransmissions |
||
|
>Timer based explicit |
||||
|
>>Timer_MRW |
MP |
Integer(50,60, 70, 80, 90, 100, 120, 140, 160, 180, 200, 300, 400, 500, 700, 900) |
Elapsed time in milliseconds. It is used to trigger the retransmission of a STATUS PDU containing an MRW SUFI field |
|
|
>>Timer_discard |
MP |
Integer(100, 250, 500, 750, 1000, 1250, 1500, 1750, 2000, 2500, 3000, 3500, 4000, 4500, 5000, 7500) |
Elapsed time in milliseconds before a SDU is discarded. |
|
|
>>MaxMRW |
MP |
Integer(1, 4, 6, 8, 12 16, 24, 32) |
Defined in [16] |
|
|
>Timer based no explicit |
||||
|
>>Timer_discard |
MP |
Integer(10,20,30,40,50,60,70,80,90,100) |
Elapsed time in milliseconds before a SDU is discarded. |
|
|
>Max DAT retransmissions |
||||
|
>>Max_DAT |
MP |
Integer(1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 15, 20, 25, 30, 35, 40) |
Defined in [16] |
|
|
>>Timer_MRW |
MP |
Integer(50, 60, 70, 80, 90, 100, 120, 140, 160, 180, 200, 300, 400, 500, 700, 900) |
Elapsed time in milliseconds. It is used to trigger the retransmission of a STATUS PDU containing an MRW SUFI field |
|
|
>>MaxMRW |
MP |
Integer(1, 4, 6, 8, 12 16, 24, 32) |
Defined in [16] |
|
|
>No discard |
||||
|
>>Max_DAT |
MP |
Integer(1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 15, 20, 25, 30, 35, 40) |
Defined in [16] |
|
CHOICE SDU Discard Mode |
Condition under which the given SDU Discard Mode is chosen |
|
Timer based explicit |
If the modes for discharge of the RLC buffer on the transmitter side is "Timer based with explicit signalling" |
|
Timer based no explicit |
If the modes for discharge of the RLC buffer on the transmitter side is "Timer based without explicit signalling" For unacknowledged mode, only Timer based without explicit signalling is applicable. |
|
Max DAT retransmissions |
If the modes for discharge of the RLC buffer on the transmitter side is "Discard after Max_DAT retransmissions" |
|
No discard |
If the modes for discharge the of RLC buffer on the transmitter side is "Reset procedure shall be done after Max_DAT retransmissions" |
10.3.4.26 UM Duplication Avoidance and Reordering info
|
Information Element/Group name |
Need |
Multi |
Type and reference |
Semantics description |
Version |
|---|---|---|---|---|---|
|
Timer_DAR |
MP |
Integer(40, 80, 120, 160, 240, 320, 480, 640, 960, 1280, 1920, 2560, 3840, 5120) |
Timer (in milliseconds) when PDUs are released to the upper layers even though there are outstanding PDUs with lower RLC SN values. |
REL-6 |
|
|
Window size DAR |
MP |
Integer(4, 8, 16, 32, 40, 48, 56, 64) |
REL-6 |
10.3.4.27 UM Out of sequence delivery info
|
Information Element/Group name |
Need |
Multi |
Type and reference |
Semantics description |
Version |
|---|---|---|---|---|---|
|
Timer_OSD |
CV- notMCCH |
Integer (40, 80, 120, 160, 240, 320, 480, 640, 960, 1280, 1920, 2560, 3840, 5120) |
REL-6 |
||
|
Window size OSD |
MP |
Integer(8, 16, 32,40, 48, 56, 64) |
REL-6 |
NOTE: This timer used to flush the buffer is configured at RRC level and indicated via a local primitive.
|
Condition |
Explanation |
|
notMCCH |
If this concerns a logical channel other than MCCH then this IE is mandatory otherwise it is not needed. In the latter case Timer_OSD takes the value of the IE Modification Period as indicated within the IE MCCH configuration information |