7 Variables, constants and timers
36.3223GPPEvolved Universal Terrestrial Radio Access (E-UTRA)Radio Link Control (RLC) protocol specificationRelease 17TS
7.1 State variables
This clause describes the state variables used in AM and UM entities in order to specify the RLC protocol. The state variables defined in this clause are normative.
All state variables and all counters are non-negative integers.
All state variables related to AM data transfer can take values from 0 to 1023 for 10 bit SN or from 0 to 65535 for 16 bit SN. All arithmetic operations contained in the present document on state variables related to AM data transfer are affected by the AM modulus (i.e. final value = [value from arithmetic operation] modulo 1024 for 10 bit SN and 65536 for 16 bit SN).
All state variables related to UM data transfer can take values from 0 to [2[sn-FieldLength] – 1]. All arithmetic operations contained in the present document on state variables related to UM data transfer are affected by the UM modulus (i.e. final value = [value from arithmetic operation] modulo 2[sn-FieldLength]).
AMD PDUs and UMD PDUs are numbered integer sequence numbers (SN) cycling through the field: 0 to 1023 for 10 bit SN and 0 to 65535 for 16 bit SN for AMD PDU and 0 to [2[sn-FieldLength] – 1] for UMD PDU.
When performing arithmetic comparisons of state variables or SN values, a modulus base shall be used.
VT(A) and VR(R) shall be assumed as the modulus base at the transmitting side and receiving side of an AM RLC entity, respectively. This modulus base is subtracted from all the values involved, and then an absolute comparison is performed (e.g. VR(R) <= SN < VR(MR) is evaluated as [VR(R) – VR(R)] modulo 1024 <= [SN – VR(R)] modulo 1024 < [VR(MR) – VR(R)] modulo 1024).
VR(UH) – UM_Window_Size shall be assumed as the modulus base at the receiving side of an UM RLC entity. This modulus base is subtracted from all the values involved, and then an absolute comparison is performed (e.g. (VR(UH) – UM_Window_Size) <= SN < VR(UH) is evaluated as [(VR(UH) – UM_Window_Size) – (VR(UH) – UM_Window_Size)] modulo 2[sn-FieldLength] <= [SN – (VR(UH) – UM_Window_Size)] modulo 2[sn-FieldLength] < [VR(UH) – (VR(UH) – UM_Window_Size)] modulo 2[sn-FieldLength]).
The transmitting side of each AM RLC entity shall maintain the following state variables:
a) VT(A) – Acknowledgement state variable
This state variable holds the value of the SN of the next AMD PDU for which a positive acknowledgment is to be received in-sequence, and it serves as the lower edge of the transmitting window. It is initially set to 0, and is updated whenever the AM RLC entity receives a positive acknowledgment for an AMD PDU with SN = VT(A).
b) VT(MS) – Maximum send state variable
This state variable equals VT(A) + AM_Window_Size, and it serves as the higher edge of the transmitting window.
c) VT(S) – Send state variable
This state variable holds the value of the SN to be assigned for the next newly generated AMD PDU. It is initially set to 0, and is updated whenever the AM RLC entity delivers an AMD PDU with SN = VT(S).
d) POLL_SN – Poll send state variable
This state variable holds the value of VT(S)-1 upon the most recent transmission of a RLC data PDU with the poll bit set to "1". It is initially set to 0.
The transmitting side of each AM RLC entity shall maintain the following counters:
a) PDU_WITHOUT_POLL – Counter
This counter is initially set to 0. It counts the number of AMD PDUs sent since the most recent poll bit was transmitted.
b) BYTE_WITHOUT_POLL – Counter
This counter is initially set to 0. It counts the number of data bytes sent since the most recent poll bit was transmitted.
c) RETX_COUNT – Counter
This counter counts the number of retransmissions of an AMD PDU (see clause 5.2.1). There is one RETX_COUNT counter per PDU that needs to be retransmitted.
The receiving side of each AM RLC entity shall maintain the following state variables:
a) VR(R) – Receive state variable
This state variable holds the value of the SN following the last in-sequence completely received AMD PDU, and it serves as the lower edge of the receiving window. It is initially set to 0, and is updated whenever the AM RLC entity receives an AMD PDU with SN = VR(R).
b) VR(MR) – Maximum acceptable receive state variable
This state variable equals VR(R) + AM_Window_Size, and it holds the value of the SN of the first AMD PDU that is beyond the receiving window and serves as the higher edge of the receiving window.
c) VR(X) – t-Reordering state variable
This state variable holds the value of the SN following the SN of the RLC data PDU which triggered t-Reordering.
d) VR(MS) – Maximum STATUS transmit state variable
This state variable holds the highest possible value of the SN which can be indicated by "ACK_SN" when a STATUS PDU needs to be constructed. It is initially set to 0.
e) VR(H) – Highest received state variable
This state variable holds the value of the SN following the SN of the RLC data PDU with the highest SN among received RLC data PDUs. It is initially set to 0.
Each transmitting UM RLC entity shall maintain the following state variables:
a) VT(US)
This state variable holds the value of the SN to be assigned for the next newly generated UMD PDU. It is initially set to 0, and is updated whenever the UM RLC entity delivers an UMD PDU with SN = VT(US).
Each receiving UM RLC entity shall maintain the following state variables:
a) VR(UR) – UM receive state variable
This state variable holds the value of the SN of the earliest UMD PDU that is still considered for reordering. It is initially set to 0. For RLC entity configured for STCH, it is initially set to the SN of the first received UMD PDU.
b) VR(UX) – UM t-Reordering state variable
This state variable holds the value of the SN following the SN of the UMD PDU which triggered t-Reordering.
c) VR(UH) – UM highest received state variable
This state variable holds the value of the SN following the SN of the UMD PDU with the highest SN among received UMD PDUs, and it serves as the higher edge of the reordering window. It is initially set to 0. For RLC entity configured for STCH, it is initially set to the SN of the first received UMD PDU.
7.2 Constants
a) AM_Window_Size
This constant is used by both the transmitting side and the receiving side of each AM RLC entity to calculate VT(MS) from VT(A), and VR(MR) from VR(R). AM_Window_Size = 512 when a 10 bit SN is used, AM_Window_Size = 32768 when a 16 bit SN is used.
b) UM_Window_Size
This constant is used by the receiving UM RLC entity to define SNs of those UMD PDUs that can be received without causing an advancement of the receiving window. UM_Window_Size = 16 when a 5 bit SN is used, UM_Window_Size = 512 when a 10 bit SN is used and UM_Window_Size = 0 when the receiving UM RLC entity is configured for MCCH, MTCH, SC-MCCH, SC-MTCH or STCH for sidelink communication.
7.3 Timers
The following timers are configured by RRC [5]:
a) t-PollRetransmit
This timer is used by the transmitting side of an AM RLC entity in order to retransmit a poll (see sub clause 5.2.2).
b) t-Reordering
This timer is used by the receiving side of an AM RLC entity and receiving UM RLC entity in order to detect loss of RLC PDUs at lower layer (see sub clauses 5.1.2.2 and 5.1.3.2). If t-Reordering is running, t-Reordering shall not be started additionally, i.e. only one t-Reordering per RLC entity is running at a given time.
c) t-StatusProhibit
This timer is used by the receiving side of an AM RLC entity in order to prohibit transmission of a STATUS PDU (see sub clause 5.2.3).
7.4 Configurable parameters
The following parameters are configured by RRC [5]:
a) maxRetxThreshold
This parameter is used by the transmitting side of each AM RLC entity to limit the number of retransmissions of an AMD PDU (see clause 5.2.1).
b) pollPDU
This parameter is used by the transmitting side of each AM RLC entity to trigger a poll for every pollPDU PDUs (see clause 5.2.2).
c) pollByte
This parameter is used by the transmitting side of each AM RLC entity to trigger a poll for every pollByte bytes (see clause 5.2.2).
d) sn-FieldLength
This parameter gives the UM SN field size in bits (see clause 7.1).
Annex A (normative):
List of CRs Containing Early Implementable Features and Corrections
This annex lists the Change Requests (CRs) whose changes may be implemented by a UE of an earlier release than which the CR was approved in (i.e. CRs that contain on their coversheets the sentence "Implementation of this CR from Rel-N will not cause interoperability issues").
Table A-1: List of CRs Containing Early Implementable Features and Corrections
|
TDoc Number (RP-xxxxxx): CR Title |
CR Number(s) |
CR Revision Number(s) |
Earliest Implementable Release |
Additional Information |
|
RP-191382: Correction on SN size for RLC AM |
0141 |
2 |
Release 13 |
|
|
NOTE 1: In case a CR has mirror CR(s), the mirror CR(s) are not listed. NOTE 2: The Additional Information column briefly describes the content of a CR in cases where the CR title may not be descriptive enough. If the CR is descriptive enough, then the Additional Information column may be left blank. |
||||
Annex B (informative):
Change history
|
Change history |
|||||||
|---|---|---|---|---|---|---|---|
|
Date |
TSG # |
TSG Doc. |
CR |
Rev |
Cat |
Subject/Comment |
New version |
|
2007-06 |
RAN2#58bis |
R2-072715 |
First version; Endorsed as v0.1.0. |
0.1.0 |
|||
|
2007-06 |
RAN2#58bis |
R2-072910 |
Added definition for Data field element and RLC SDU segment; Removed Editor’s note on non-byte-aligned RLC SDUs; Added description for Data field for AMD PDU; Added Align Info for AMD PDU header element; Added description on extension part of AMD PDU header at concatenation; Added figure for AMD PDU; Added Segment Offset and Length Field for AMD PDU segment header element; Added Editor’s note for STATUS PDU; Added general text on parameters; Added description for Extension bit, Length Indicator, Align Info, Segment Offset and Last Segment Flag; Removed Editor’s note on Length Indicator. |
0.1.1 |
|||
|
2007-06 |
RAN2#58bis |
R2-072995 |
Moved description of Data field for AMD PDU and TMD PDU to the clause dedicated to Data field; Changed terminology for Align Info to Segmentation Info; Added Segmentation Info for UMD PDU header element; Removed figure for AMD PDU; Corrected error for AMD PDU segment header element (replaced Length Field by Last Segment Flag); Added place holders to specify the number of bits for the individual RLC header elements; Modified description for Extension bit, Segmentation Info and Last Segment Flag using tables. |
0.1.2 |
|||
|
2007-06 |
RAN2#58bis |
R2-072996 |
Bracketed terminology for Segmentation Info; Corrected clause numbering; Clarified description of Extension bit and Segment Offset. |
0.1.3 |
|||
|
2007-08 |
RAN2#59 |
R2-073554 |
Added receive operation descriptions for the case AM RLC entity receives AMD PDU segments; Modified general texts regarding retransmissions; Added a general description text for Segmentation Info; Added an Editor’s note for Segment Offset. |
0.1.4 |
|||
|
2007-08 |
RAN2#59 |
R2-073712 |
v0.1.4 was endorsed by RAN WG2 as v0.2.0. |
0.2.0 |
|||
|
2007-08 |
RAN2#59 |
R2-073844 |
Added some missing abbreviations in clause 3.2; Added description and a figure regarding RLC entity configuration in clause 4.2.1, and removed Editor’s note on this aspect; Added new sub clauses under clauses 4.2.1.1-4.2.1.3 (purely editorial modification) Added description on SN, i.e. RLC PDU based SN, and removed Editor’s note on the possibility of having the same header structure for AMD PDU and AMD PDU segment due to PDCP SN reuse; Added description of the AM receive window operation; Added description that fixed header part should be byte aligned and extension header part should be byte aligned; Modified description on extension header part (LI and E are not required for the last Data field element) and removed Editor’s note on this aspect; Added further description on Data field; LI field size is set to 11bits; Corrected editorial errors (reference number to tables) Added 3 state variables: VT(S), VR(R), VR(MR). |
0.2.1 |
|||
|
2007-08 |
RAN2#59 |
R2-073868 |
Corrected editorial errors; Added 1 constant: Rx_Wndow_Size; Added description of modulus operation on VT(S), VR(R), VT(MR). |
0.2.2 |
|||
|
2007-08 |
RAN2#59 |
R2-073881 |
Removed reference to RLC UM for VT(R) and VT(MR). |
0.2.3 |
|||
|
2007-09 |
RAN#37 |
RP-070689 |
v0.2.3 was endorsed by RAN WG2 as v1.0.0 and presented to RAN plenary for information. |
1.0.0 |
|||
|
2007-11 |
RAN2#60 |
R2-074583 |
Added description of the AM transmit window operation; Added Editor’s note that PDU loss detection should be after HARQ reordering; Added description on AM retransmission and resegmentation; Added description of the polling trigger "transmission of last data in the buffer"; Added polling trigger "poll retransmit timer" and its description; Added Editor’s note that either PDU count based or window based polling trigger should be supported; Added description of the status reporting trigger "polling from its peer AM RLC entity"; Removed old Editor’s note in the polling sub clause; Added status reporting trigger "detection of reception failure of an RLC data PDU" and its description; Added status prohibit function and its description; Added Editor’s note that at least a 1byte fixed header for the UMD PDU should be supported; Complete AMD PDU and AMD PDU segment headers captured and 3 new figures inserted for each of them; Added Editor’s note that STATUS PDU will only have 1 format; Modified description of the Data field so that it also applies to AMD PDU segment; Added description of the SN field in relation to the AMD PDU segment; Corrected description of the E field; Defined SO field length to be 15bits; Completed the description of the SO field and removed the related Editor’s note; Added description of the D/C field, RF field and P field; Added 2 state variables: VT(A) and VT(MS); Added to the description of VT(S) and VR(MR); Added 1 constant: Tx_Window_Size; Added 2 timers: T_poll_prohibit and T_status_prohibit.r |
1.0.1 |
|||
|
2007-11 |
RAN2#60 |
R2-075061 |
Cleaned up terminology related to PDUs; Editorial corrections (aligned wording, corrected Figure numbering, clarifications, etc.) Added Editor’s note that exception cases when a negatively acknowledged RLC data PDU should not be transmitted will be captured when identified; Added description that the use of status prohibit function and particular polling triggers are configurable; Modified receiver operation for RLC-AM regarding AMD PDU segments (aligned with AMD PDU); Added description that DL CCCH is handled by RLC-UM and removed corresponding Editor’s note; Added Editor’s note that wording "considered" regarding retransmission of AMD PDU / AMD PDU segment in sub clause 5.2.1 should be improved; Added to the description of SN field that it is 10bits for AMD PDU and AMD PDU segment; Removed Editor’s note regarding the need for status prohibit function; Added Editor’s note that the need for [SI] field for UMD PDU can be challenged. |
1.0.2 |
|||
|
2007-11 |
RAN2#60 |
R2-075154 |
Added an Editor’s note regarding Local NACK; Modified wording in clause 5.2.1 on the object of retransmission (RLC data PDU changed to AMD PDU / portion of AMD PDU); Clarified that STATUS PDU is triggered after the PDU containing th poll bit is "HARQ reordered", rather than just "reordered"; Removed incorrect inclusion of a T_status_prohibit and added an Editor’s which just says status prohibit function is supported. |
1.0.3 |
|||
|
2007-11 |
RAN2#60 |
R2-075198 |
Description regarding the modulus operation involving state variables was changed in order to align with TS 25.322; Figures on PDUs were slightly modified (editorial). |
1.0.4 |
|||
|
2007-11 |
RAN2#60 |
R2-075430 |
Text on receiver operation in clause 5.1.3 was revised to align the description regarding modulus operation with TS 25.322; Further cleaned up terminology related to PDUs; V1.0.4 was endorsed by RAN WG2 as v1.1.0 with the above revisions. |
1.1.0 |
|||
|
2007-11 |
RAN2#60 |
R2-075500 |
Added RLC architecture model figures (Figures 4.2.1.1.1-1, 4.2.1.2.1-1, 4.2.1.3.1-1); Added Editor’s note that the SDU discard functionality may not be specified in RLC; Added description of receive operations for RLC-UM in sub clause 5.1.2; Added to the description of receive operations for RLC-AM in sub clause 5.1.3 including: STATUS transmitting window definition, procedures for the case RLC data PDU within receiving window is received, actions at T_reordering expiry and RLC SDU reassembly; T_and in sub clause 5.1.3; Removed Editor’s note which said that PDU loss detection should be after HARQ reordering; Clarified the description of the polling trigger "transmission of last data in the buffer"; Added description of STATUS PDU construction in sub clause 5.2.3 and removed an Editor’s note in this sub clause; Modified trigger for RLC SDU discard to "indication from PDCP"; Removed Editor’s note on the type of PDUs to be specified; Removed Editor’s notes regarding STATUS PDU piggybacking; Complete UMD PDU headers captured and 2 new figures inserted for them, and removed Editor’s note on UMD PDU; Defined one STATUS PDU format with a new figure and an Editor’s note, and removed old Editor’s note in sub clause 6.2.1.6; Added description of the R1 field, CPT field, ACK_SN field, E1 field, NACK_SN field, E2 field, SOstart field and SOend field. Added 7 state variables: VR(R-SO), VR(X), VR(X-SO), VR(MS), VR(UR), VR(UMR) and VR(UX); Constants Rx_Window_Size and Tx Window size were converged into one constant "Window_Size" of which the value is defined to half the SN space, and constants "AM_Window_Size" and "UM_Window_Size" were newly defined; Added 1 timer: T_reordering. |
1.1.1 |
|||
|
2007-11 |
RAN2#60 |
R2-075501 |
Added definition for "byte segment"; Removed Editor’s note which said that the SDU discard functionality may not be specified in RLC; Added missing description for RLC-UM receive operation (the case when UMD PDU with SN that falls within the reordering window but not equal to VR(R) is received); Added missing description for RLC-AM receive operation (the case when only part of the received RLC data PDU is received in duplication); Added text related to updating state variable VR(MS); Added Editor’s note that it has to be decided whether T_reordering can be triggered by a missing RLC data PDU for which status reporting has already been triggered once; Editorial clarification / corrections were made. |
1.1.2 |
|||
|
2007-11 |
RAN2#60 |
R2-075502 |
Added text related to updating state variable VR(MS); Editorial clarification / corrections were made. |
1.1.3 |
|||
|
2007-11 |
RAN2#60 |
R2-075503 |
Modified description of VR(MS) update procedure; Modified description of VR(X) / VR(X-SO) update procedure; Editorial corrections were made. |
1.1.4 |
|||
|
2007-11 |
RAN2#60 |
R2-075504 |
Added missing description with regards to RLC-AM receive operation; Added Editor’s note on the delivery of RLC control PDUs; Editorial corrections were made. |
1.1.5 |
|||
|
2007-11 |
RAN2#60 |
R2-074589 |
v1.1.5 was endorsed by RAN WG2 as v1.2.0. |
1.2.0 |
|||
|
2007-11 |
RP-38 |
RP-070918 |
v1.2.0 was stepped to v2.0.0 and presented to RAN plenary for approval. |
2.0.0 |
|||
|
2007-12 |
RP-38 |
– |
Approved at TSG RAN-38 and placed under change control |
8.0.0 |
|||
|
2008-03 |
RP-39 |
RP-080196 |
0001 |
– |
CR0001 for TS 36.322 E-UTRA RLC: Added reference to TS 36.321; Clarified definition of "byte segment"; Renamed "Segmentation Info" to "Framing Info"; Aligned texts to refer to "upper layer" and "lower layer" instead of RRC/PDCP and MAC; Specified that BCCH and DL CCCH is handled by RLC-TM; Added support for duplicate detection by receiving RLC UM entity;; Clarified that RLC SDUs should be delivered to upper layers in sequence; Modified description so that MAC indicates "total size of RLC PDUs" together with notification of transmission opportunity instead of "TB size"; Specified that RLC SDU discard is applied for RLC-AM and RLC UM, and introduced the detailed RLC SDU discard procedure; Renamed "RLC reset" to "RLC re-establishment", and introduced the detailed RLC re-establishment procedure; Removed Editor’s note on RLC flow control (flow control will not be supported by RLC); Restructured the texts on RLC AM and RLC UM receive operations, and added/modified the detailed descriptions; Added description on prioritization of data to transmit (control > data; retransmission > new data); Removed the term STATUS transmitting window; Clarified that retransmission of negatively acknowledged data by STATUS PDU is mandatory and that retransmission of negatively acknowledged data by HARQ delivery failure is optional; Removed Editor’s note on retransmission prohibit (there will be no conditions where negatively acknowledged data shall not be retransmitted); Clarified description on polling trigger "Transmission of last data in buffer"; Added new polling triggers "Every Poll_PDU PDUs" and "Every Poll_Byte Bytes", introduced their descriptions, and added an Editor’s note that their configurability is FFS; Added description on status reporting trigger "detection of reception failure of an RLC data PDU"; Introduced description of the status prohibit function; Removed Editor’s note on the possibility to define more RLC control PDUs (no more RLC control PDUs will be defined); Clarified the "most significant bit" and "least significant bit" in an RLC PDU; Removed reference to bit numbers in RLC PDU; Modified the order of fields in the 1byte UMD PDU header; Removed Editor’s note on the order of fields in the AMD PDU / AMD PDU segment header (they are now confirmed); Modified definition of ACK_SN; Defined the special value of SOend; Added description on the UM modulus operation; Removed state variables VR(R-SO), VR(X-SO) and VR(UMR); Modified description/definition of state variables VR(MR), VR(X), VR(MS), VR(UR) and VR(UX); Introduced new state variables VR(H) and VR(UH) and their descriptions; Introduced new constants Poll_PDU and Poll_Byte and their descriptions; Clarified that only one T_reordering will be running at one time for an RLC entity; Introduced new timer T_status_prohibit and its description; Editorial corrections were made. |
8.1.0 |
|
|
2008-05 |
RP-40 |
RP-080411 |
0002 |
1 |
Clarification on STATUS PDU size for BSR |
8.2.0 |
|
|
RP-40 |
RP-080411 |
0003 |
– |
Removal of Editor’s Note on updating of VR(MS) upon expiry of T_reordering |
8.2.0 |
||
|
RP-40 |
RP-080411 |
0004 |
– |
Removal of STATUS receiving window |
8.2.0 |
||
|
RP-40 |
RP-080411 |
0005 |
– |
Duplicate detection in UM RLC |
8.2.0 |
||
|
RP-40 |
RP-080411 |
0006 |
– |
Correction to Polling Procedure |
8.2.0 |
||
|
RP-40 |
RP-080411 |
0007 |
– |
Miscellaneous corrections to TS 36.322 |
8.2.0 |
||
|
RP-40 |
RP-080411 |
0008 |
– |
Small corrections to RLC |
8.2.0 |
||
|
RP-40 |
RP-080411 |
0012 |
– |
CR to 36.322 on correction to RLC PDU reassembly |
8.2.0 |
||
|
RP-40 |
RP-080411 |
0015 |
1 |
36.322 CR on ‘RLC retransmission count and addition of Configurable Parameters’ |
8.2.0 |
||
|
RP-40 |
RP-080411 |
0017 |
– |
Service alignments with TS 36.323 (PDCP) |
8.2.0 |
||
|
RP-40 |
RP-080411 |
0018 |
– |
CR on the procedure to construct the STATUS PDU |
8.2.0 |
||
|
2008-09 |
RP-41 |
RP-080691 |
0019 |
1 |
Clarification of polling |
8.3.0 |
|
|
RP-41 |
RP-080691 |
0020 |
– |
Corrections to formatting |
8.3.0 |
||
|
RP-41 |
RP-080691 |
0021 |
2 |
The value of ACK_SN for partial STATUS PDU |
8.3.0 |
||
|
RP-41 |
RP-080691 |
0022 |
1 |
Error cases for RLC |
8.3.0 |
||
|
RP-41 |
RP-080691 |
0024 |
– |
RLC entity re-establishment |
8.3.0 |
||
|
RP-41 |
RP-080691 |
0025 |
– |
Miscellaneous corrections to RLC specification |
8.3.0 |
||
|
RP-41 |
RP-080691 |
0029 |
– |
Clarification of the reordering timer |
8.3.0 |
||
|
RP-41 |
RP-080691 |
0032 |
– |
Clarification of Triggering Conditions for Status Reports |
8.3.0 |
||
|
RP-41 |
RP-080691 |
0033 |
– |
RLC UMD PDU formats with LI |
8.3.0 |
||
|
RP-41 |
RP-080691 |
0036 |
– |
Correction on UM Receive Operation |
8.3.0 |
||
|
RP-41 |
RP-080691 |
0039 |
– |
Correction for TM RLC entity: 6.1.2.3 |
8.3.0 |
||
|
RP-41 |
RP-080691 |
0040 |
– |
Removal of MBMS channels: 6.1.2.3 |
8.3.0 |
||
|
2008-12 |
RP-42 |
RP-081019 |
0043 |
– |
Proposed CR for aligning the construction of partial Status PDUs with intended operation |
8.4.0 |
|
|
RP-42 |
RP-081019 |
0046 |
– |
Error Handling in RLC |
8.4.0 |
||
|
RP-42 |
RP-081019 |
0047 |
– |
Miscellaneous corrections to 36.322 |
8.4.0 |
||
|
RP-42 |
RP-081019 |
0048 |
– |
Correction to Segment Offset fields |
8.4.0 |
||
|
RP-42 |
RP-081019 |
0049 |
– |
Correction to the description of the delivery of RLC SDU |
8.4.0 |
||
|
RP-42 |
RP-081019 |
0050 |
– |
Minor issues on RLC |
8.4.0 |
||
|
RP-42 |
RP-081019 |
0054 |
– |
The setting of VR(X) |
8.4.0 |
||
|
RP-42 |
RP-081019 |
0055 |
– |
Adding RLC TM operation |
8.4.0 |
||
|
RP-42 |
RP-081019 |
0056 |
– |
Removing a redundant text on VT(A) setting |
8.4.0 |
||
|
RP-42 |
RP-081019 |
0057 |
– |
Counting RLC Retransmissions |
8.4.0 |
||
|
2009-03 |
RP-43 |
RP-090129 |
0058 |
– |
CR to 36.322 on RRC Parameters |
8.5.0 |
|
|
RP-43 |
RP-090129 |
0059 |
– |
Local NACKing in UE |
8.5.0 |
||
|
RP-43 |
RP-090129 |
0060 |
– |
Supporting RLC SDU larger than 2047 octets |
8.5.0 |
||
|
RP-43 |
RP-090129 |
0061 |
– |
CR on the in sequence delivery function for UM |
8.5.0 |
||
|
RP-43 |
RP-090129 |
0062 |
– |
Correction to Delivery of PDU |
8.5.0 |
||
|
RP-43 |
RP-090129 |
0063 |
1 |
Issues with SO, SOstart, and SOend fields |
8.5.0 |
||
|
RP-43 |
RP-090129 |
0064 |
– |
Miscellaneous corrections to RLC specification |
8.5.0 |
||
|
RP-43 |
RP-090129 |
0065 |
– |
Correction to status reporting triggering condition |
8.5.0 |
||
|
RP-43 |
RP-090129 |
0066 |
– |
Alignment of one condition on setting the poll bit |
8.5.0 |
||
|
RP-43 |
RP-090129 |
0067 |
1 |
Proposed CR to 36.322 on Clarification on Polling procedure |
8.5.0 |
||
|
RP-43 |
RP-090129 |
0068 |
1 |
Every Poll_PDU PDUs and Every Poll_Byte bytes triggers |
8.5.0 |
||
|
RP-43 |
RP-090129 |
0069 |
– |
UE behaviour when T_poll_retransmit expires |
8.5.0 |
||
|
RP-43 |
RP-090129 |
0076 |
– |
Definition of RETX_COUNT missing |
8.5.0 |
||
|
2009-06 |
RP-44 |
RP-090514 |
0080 |
– |
Reset of T_poll_retransmission |
8.6.0 |
|
|
RP-44 |
RP-090514 |
0081 |
– |
RLC functions |
8.6.0 |
||
|
RP-44 |
RP-090514 |
0082 |
1 |
Correction to handling of reserved field |
8.6.0 |
||
|
RP-44 |
RP-090514 |
0083 |
– |
Correction to condition for stopping t-Reordering in AM mode |
8.6.0 |
||
|
2009-09 |
RP-45 |
RP-090906 |
0084 |
– |
Possible misinterpretation on incrementing RETX_COUNT |
8.7.0 |
|
|
2009-12 |
RP-46 |
RP-091341 |
0087 |
– |
Capturing MBMS agreements in RLC |
9.0.0 |
|
|
2010-03 |
RP-47 |
RP-100305 |
0089 |
– |
Correction to RLC entity |
9.1.0 |
|
|
2010-06 |
RP-48 |
RP-100536 |
0091 |
1 |
Correction of RLC VR(H) update |
9.2.0 |
|
|
2010-09 |
RP-49 |
RP-100851 |
0092 |
1 |
Miscellaneous corrections to RLC |
9.3.0 |
|
|
2010-12 |
RP-50 |
– |
– |
– |
Upgrade to Release 10 – no technical change |
10.0.0 |
|
|
2012-09 |
RP-57 |
– |
– |
– |
Upgrade to Release 11 – no technical change |
11.0.0 |
|
|
2014-06 |
RP-64 |
RP-140892 |
0099 |
1 |
Extended RLC LI field |
12.0.0 |
|
|
2014-09 |
RP-65 |
RP-141511 |
0101 |
– |
Corrections to configuration of extended RLC LI field |
12.1.0 |
|
|
2014-12 |
RP-66 |
– |
– |
– |
MCC editorial update |
12.1.1 |
|
|
2015-03 |
RP-67 |
RP-150376 |
0105 |
1 |
RLC concatenation for extended LI field |
12.2.0 |
|
|
RP-67 |
RP-150374 |
0107 |
– |
Introduction of ProSe Direct Communication |
12.2.0 |
||
|
2015-09 |
RP-69 |
RP-151441 |
0108 |
– |
Corrections for STCH in 36.322 |
12.3.0 |
|
|
2015-12 |
RP-70 |
RP-152071 |
0114 |
– |
Introduction of extended RLC protocol formats for CA enhancement |
13.0.0 |
|
|
RP-70 |
RP-152080 |
0115 |
– |
Introduction of SC-PTM in RLC |
13.0.0 |
||
|
2016-03 |
RP-71 |
RP-160470 |
0116 |
1 |
Clarification on Polling for last data |
13.1.0 |
|
|
2016-06 |
RP-72 |
RP-161078 |
0120 |
1 |
Addition of sidelink in the overview model |
13.2.0 |
|
|
RP-72 |
RP-161081 |
0121 |
2 |
Introduction of NB-IoT |
13.2.0 |
||
|
2017-03 |
RP-75 |
RP-170655 |
0126 |
– |
F |
Correction on channel bandwidth definition for NB-IoT |
13.3.0 |
|
RP-75 |
RP-170637 |
0125 |
2 |
B |
Introducing Rel-14 NB-IoT enhancements into RLC |
14.0.0 |
|
|
2017-09 |
RP-77 |
RP-171914 |
0127 |
2 |
C |
Packet Reordering for Sidelink |
14.1.0 |
|
RP-77 |
RP-171920 |
0129 |
1 |
A |
Corrections on logical channel for Rel-13 MTC |
14.1.0 |
|
|
RP-77 |
RP-171915 |
0130 |
– |
F |
Corrections to RLC for re-establishment for NB-IoT using control plane |
14.1.0 |
|
|
2017-12 |
RP-78 |
RP-172614 |
0132 |
1 |
B |
EN-DC impacts to LTE RLC |
15.0.0 |
|
2018-04 |
Added 5G logo to the cover page |
15.0.1 |
|||||
|
2018-07 |
RP-80 |
RP-181252 |
0133 |
1 |
B |
Introduction of further NB-IoT enhancements in 36.322 |
15.1.0 |
|
RP-80 |
RP-181247 |
0138 |
1 |
B |
Introduction of Ultra Reliable Low Latency Communication for LTE |
15.1.0 |
|
|
2019-06 |
RP-84 |
RP-191382 |
0141 |
2 |
F |
Correction on SN size for RLC AM |
15.2.0 |
|
2019-09 |
RP-85 |
RP-192198 |
0142 |
– |
F |
Normative Annex of CRs Containing Early Implementable Features and Corrections |
15.3.0 |
|
2020-07 |
RP-88 |
RP-201168 |
0145 |
2 |
F |
Clarification on RLC UM SN size for NB-IoT |
15.4.0 |
|
2020-07 |
RP-88 |
Upgraded to Rel-16 |
16.0.0 |
||||
|
2022-03 |
RP-95 |
Upgraded to Rel-17, no technical change |
17.0.0 |
||||