EventHelix.

com
• telecommunication design • systems engineering • real-time and embedded systems

3GPP LTE Radio Link Control (RLC) Sub Layer
© 2009 EventHelix.com Inc. All Rights Reserved.

LTE RLC Sub Layer Functions
Acknowledged, Unacknowledged and Transparent Mode Operation Error Correction Through ARQ (AM)

EventHelix.com
• telecommunication design • systems engineering • real-time and embedded systems

• • • •

RLC

• •

Concatenation, Segmentation and Reassembly of RLC SDUs (AM and UM)

Transfer of Upper Layer PDUs

• • •

Transfer of upper layer PDUs; Error correction through ARQ (only for AM data transfer) Concatenation, segmentation and reassembly of RLC SDUs (UM and AM) Re-segmentation of RLC data PDUs (AM) Reordering of RLC data PDUs (UM and AM); Duplicate detection (UM and AM); RLC SDU discard (UM and AM) RLC re-establishment Protocol error detection and recovery
2

© 2009 EventHelix.com Inc.

RLC in the LTE Protocol Stack

EventHelix.com
• telecommunication design • systems engineering • real-time and embedded systems

MME
NAS

eNodeB
RRC PDCP

UE
NAS
RRC PDCP

RLC MAC
PHY
© 2009 EventHelix.com Inc.

RLC MAC
PHY
3

Downlink RLC Sub Layer Interfaces
Radio Bearers ROHC PDCP Security Security Security ROHC ROHC ROHC

EventHelix.com
• telecommunication design • systems engineering • real-time and embedded systems

Security

RLC

Segm. ARQ etc

...

Segm. ARQ etc Logical Channels

Segm. ARQ etc

...

Segm. ARQ etc

CCCH BCCH

PCCH

Scheduling / Priority Handling

MAC

Multiplexing UE1

Multiplexing UEn

HARQ Transport Channels

HARQ

© 2009 EventHelix.com Inc.

4

ARQ etc .. 5 .Uplink RLC Sub Layer Interfaces ROHC PDCP Security Security ROHC EventHelix.. ARQ etc CCCH Logical Channels Scheduling / Priority Handling MAC Multiplexing HARQ Transport Channels © 2009 EventHelix.com • telecommunication design • systems engineering • real-time and embedded systems Radio Bearers RLC Segm. Segm.com Inc.

e.EventHelix.e.e. RRC layer or PDCP sub layer) transmitting TM RLC entity receiving TM RLC entity transmitting UM RLC entity receiving UM RLC entity • telecommunication design • systems engineering • real-time and embedded systems RLC SDUs are exchanged with upper layers SAP between upper layers AM RLC entity eNB logical channel lower layers (i.com LTE RLC Sub Layer upper layer (i. RRC layer or PDCP sub layer) © 2009 EventHelix.e.com Inc. MAC sub layer and physical layer) RLC PDUs are exchanged between peer RLC entities logical channel receiving TM RLC entity transmitting TM RLC entity receiving UM RLC entity transmitting UM RLC entity AM RLC entity UE SAP between upper layers upper layer (i. MAC sub layer and physical layer) radio interface lower layers (i. RLC SDUs are exchanged with upper layers 6 .

com RLC Modes Transparent Mode • No segmentation and reassembly of RLC SDUs • No RLC headers are added • No delivery guarantees • Suitable for carrying voice • telecommunication design • systems engineering • real-time and embedded systems Unacknowledged Mode • Segmentation and reassembly of RLC SDUs • RLC Headers are added • No delivery guarantees • Suitable for carrying streaming traffic Acknowledged Mode • Segmentation and reassembly of RLC SDUs • RLC Headers are added • Reliable in sequence delivery service • Suitable for carrying TCP traffic 7 © 2009 EventHelix.com Inc. .EventHelix.

com • telecommunication design • systems engineering • real-time and embedded systems 3GPP LTE Radio Link Control (RLC) Sub Layer UNACKNOWLEDGED MODE © 2009 EventHelix.EventHelix. 8 .com Inc.

5. Pass the RLC PDUs to MAC for transmission over the air. 4. Add RLC Header 5. . Receive from PDCP / RRC EventHelix. Segment the SDU into RLC PDUs when the MAC scheduler permits transmission. Add the SDU to the transmit buffer.Unacknowledged Mode Transmit Overview 1. Pass to MAC Sub Layer 1.com • telecommunication design • systems engineering • real-time and embedded systems 2. 3.com Inc. 9 © 2009 EventHelix. Segmentation and Concatenation 4. 2. Add the RLC header to the RLC PDU. Receive the upper layer SDU from PDCP or RRC. Add to Transmission Buffer 3.

Remove RLC Header 3.Unacknowledged Mode Receive Overview 1. Reassemble PDUs 4. Pass the assembled SDUs to the PDCP or RRC layers. 3. 2. . 4.com • telecommunication design • systems engineering • real-time and embedded systems 2. 10 © 2009 EventHelix. Receive from MAC Sub Layer EventHelix. Pass to PDCP / RRC 1.com Inc. The RLC layer removes the RLC header. The RLC layer assembles an upper layer SDUs if receipt of an RLC PDU completes the assembly of the SDU. The MAC layer passes the received RLC PDUs to the RLC layer.

and is updated whenever the UM RLC entity delivers an UMD PDU with SN = VT(US). © 2009 EventHelix.Unacknowledged Mode State Variables VT(US) Send State Variable EventHelix.com • telecommunication design • systems engineering • real-time and embedded systems • Holds the value of the SN to be assigned for the next newly generated UMD PDU. • It is initially set to 0. 11 . It is initially set to 0. 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 • Serves as the higher edge of the reordering window.com Inc. • It is initially set to 0. 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 tReordering. VR(UR) UM receive state variable • Holds the value of the SN of the earliest UMD PDU that is still considered for reordering.

12 .EventHelix.com Inc.com • telecommunication design • systems engineering • real-time and embedded systems 3GPP LTE Radio Link Control (RLC) Sub Layer ACKNOWLEDGED MODE © 2009 EventHelix.

6. Add RLC Header 4. Add to Transmission Buffer EventHelix. Keep a Copy for Retransmission 5. 5. 2.com • telecommunication design • systems engineering • real-time and embedded systems 1.Acknowledged Mode Transmit Overview 1. Pass the RLC PDUs to MAC for transmission over the air. 13 © 2009 EventHelix. Add the SDU to the transmit buffer. Make a copy of the transmit buffer for possible retransmissions. . 3. Segment the SDU into RLC PDUs when the MAC scheduler permits transmission. Segmentation and Concatenation 4. Receive from PDCP / RRC 2. 6.com Inc. Add the RLC header to the RLC PDUs. 3. Pass to MAC Sub Layer Receive the upper layer SDU from PDCP or RRC.

Pass the assembled SDUs to the PDCP or RRC layers. Reassemble PDUs 5. The MAC layer passes the received RLC PDU to the RLC layer. © 2009 EventHelix.com Inc. The RLC PDU is received correctly. 4. Receive from MAC Sub Layer EventHelix. 2. Mark for Positive Acknowledgement 4. 5. Pass to PDCP / RRC The RLC layer assembles an upper layer SDUs if receipt of an RLC PDU completes the assembly of the SDU. Remove RLC Header 3.Acknowledged Mode Receive Overview 1. 14 . 3. – Acknowledgements are sent periodically to the remote peer. 2.com • telecommunication design • systems engineering • real-time and embedded systems 1. so mark the block for positive acknowledgement. The RLC layer removes the RLC header.

.Overview 1. 3. 2. Received Positive Acknowledgement EventHelix. Remove from Retransmission Queue Free buffer released from retransmission queue 3. Access the retransmission queue and remove the buffer as it has been acknowledged.com • telecommunication design • systems engineering • real-time and embedded systems 2. A positive acknowledgement is received from the remote end.Acknowledged Mode: Received Positive Acknowledgement . 15 © 2009 EventHelix. Update the receive sequence number to allow further transmissions 1. Update the received sequence numbers to advance the sliding window.com Inc.

Retransmit the Buffer Re-segment if the MAC cannot transmit bursts with original length © 2009 EventHelix.com • telecommunication design • systems engineering • real-time and embedded systems 2. Extract the RLC PDU that needs to be retransmitted 1. Retransmit the buffer – If MAC does not support the original transmission rate. . 2. 3.com Inc.Acknowledged Mode: Received Negative Acknowledgement Overview 1. A negative acknowledgement is received from the remote end. Access the retransmission queue and extract the buffer for retransmission. re-segment the RLC block into the smaller available block size 16 3. Received a Negative Acknowledgement EventHelix.

17 . 2.Overview 1. A retransmission for a previously negatively acknowledged RLC PDU is received. © 2009 EventHelix. Reassemble all the received in sequence data and pass the reassembled SDUs to RRC/PDCP 3. Received a retransmission for a previously negatively acknowledged RLC PDU EventHelix. Assemble all the in sequence received data into SDUs – Pass the received SDUs to the RRC or PDCP layers. 2.com • telecommunication design • systems engineering • real-time and embedded systems 1.com Inc. Update the received data buffer – The received buffer may fill a hole in the previously received data. Update the receive buffer and check if the retransmission fills holes in previously received data 3.Acknowledged Mode: Received Retransmission .

com Inc. 18 .com • telecommunication design • systems engineering • real-time and embedded systems Transmit VT(A): Acknowledged State Variable VT(MS): Maximum Send State Variable VT(S): Send State Variable POLL_SN: Poll Send State Variable Receive VR(R): Receive State Variable VR(MR): Maximum Accepted Receive State Variable VR(X): Reordering State Variable PDU_WITHOUT_POLL Counter BYTE_WITHOUT_POLL Counter RETX_COUNT Counter VR(MS): Maximum STATUS Transmit State Variable VR(H): Highest Received State Variable © 2009 EventHelix.Acknowledged Mode State Variables EventHelix.

com Inc. • It is initially set to 0. and is updated whenever the AM RLC entity delivers an AMD PDU with SN = VT(S).Acknowledged Mode Transmit State Variables VT(A) Acknowledgement state variable EventHelix. It is initially set to 0. VT(S) Send state variable • This state variable holds the value of the SN to be assigned for the next newly generated AMD PDU. © 2009 EventHelix. 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. and is updated whenever a positive acknowledgment for an AMD PDU with SN = VT(A) is received VT(MS) Maximum send state variable • This state variable equals VT(A) + AM_Window_Size • It serves as the higher edge of the transmitting window.com • telecommunication design • systems engineering • real-time and embedded systems • Holds the value of the SN of the next AMD PDU for which a positive acknowledgment is to be received in-sequence • Serves as the lower edge of the transmitting window. 19 .

com Inc. 20 . Positive acknowledgements have been received for all AMD PDUs associated with a transmitted RLC SDU: Deliver the RLC SDU to the upper layers © 2009 EventHelix.com • telecommunication design • systems engineering • real-time and embedded systems The Transmit AM RLC entity maintains a transmitting window such that Transmit Serial Number (SN) falls within the Transmit window [VT(A) <= SN < VT(MS)] Deliver a new AMD PDU to lower layer. the Transmit AM RLC entity shall: AMD PDU SN= VT(S) VT(S) = VT(S) + 1 Transmit AM RLC entity receives a STATUS PDU with positive acknowledgement for a RLC data PDU VT(A) = Smallest SN awaiting acknowledgement.Acknowledged Mode Transmit Procedure EventHelix.

It is initially set to 0. and it holds the value of the SN of the first AMD PDU that is beyond the receiving window •Serves as the higher edge of the receiving window.com • telecommunication design • systems engineering • real-time and embedded systems VR(MR) Maximum acceptable receive state variable •This state variable equals VR(R) + AM_Window_Size. 21 .com Inc. 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. 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.Acknowledged Mode Receive State Variables VR(R) Receive state variable •Holds the value of the SN following the last in-sequence completely received AMD PDU •It serves as the lower edge of the receiving window. EventHelix. and is updated whenever an AMD PDU with SN = VR(R) is received. It is initially set to 0. •It is initially set to 0. © 2009 EventHelix. 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.

com • telecommunication design • systems engineering • real-time and embedded systems • This parameter is used by the transmitting side of each AM RLC entity to limit the number of retransmissions of an AMD PDU. © 2009 EventHelix. sn-FieldLength • This parameter gives the UM SN field size in bits.com Inc.RLC Configurable Parameters maxRetxThreshold pollPDU pollByte EventHelix. 22 . • This parameter is used by the transmitting side of each AM RLC entity to trigger a poll for every pollPDU PDUs. • This parameter is used by the transmitting side of each AM RLC entity to trigger a poll for every pollByte bytes.

EventHelix. © 2009 EventHelix.com RLC Priority • telecommunication design • systems engineering • real-time and embedded systems • The transmitting side of an AM RLC entity shall prioritize transmission of RLC control PDUs over RLC data PDUs. 23 . • The transmitting side of an AM RLC entity shall prioritize retransmission of RLC data PDUs over transmission of new AMD PDUs.com Inc.

24 .com • telecommunication design • systems engineering • real-time and embedded systems 3GPP LTE Radio Link Control (RLC) Sub Layer RLC PDU FORMATS © 2009 EventHelix.com Inc.EventHelix.

EventHelix.. 25 .com Inc..com TMD PDU Data . • telecommunication design • systems engineering • real-time and embedded systems Oct 1 Oct N • Transparent Mode PDUs just contain Data • No headers are included © 2009 EventHelix.

. four padding bits follow after the last LI.com UMD PDU-1 FI E Data .EventHelix. – Furthermore.. 26 . when an UMD PDU header consists of an odd number of LI(s). • An UMD PDU header needs to be extended when more than multiple Data field elements need to be sent.. – In that which case an E and a LI are present for every Data field element except the last. E SN Oct 1 Oct 2 Oct 3 Oct N UMD PDU with 5 bit Serial Number UMD PDU with 10 bit Serial Number • An UM RLC entity is configured by RRC to use either a 5 bit SN or a 10 bit SN. SN Oct 1 Oct 2 Oct N R1 R1 R1 • telecommunication design • systems engineering • real-time and embedded systems FI SN Data .. – See next two slides © 2009 EventHelix.com Inc.

5*K] Oct N FI E LI1 E LI1 E LI2 .5*K-1] Oct [2.5*K-2] Oct [2+1.EventHelix. SN LI2 (if K>=3) Oct 1 Oct 2 Oct 3 Oct 4 Oct [2. LIK Padding Data ..5*K-4] Oct [2.5*K-5] Oct [2....5*K-3] Oct [2+1.5*K-1] Oct [2+1.5+1..5+1.com Inc.5*K] Oct N E LIK-2 E LIK LIK-2 E LIK-1 LIK E LIK-1 LIK-1 LIK-1 E LIK Data .5*K-3] Oct [2.5+1.. 27 . SN LI2 Oct 1 Oct 2 Oct 3 Oct 4 Oct [2+1.5+1. © 2009 EventHelix..5+1.5*K-2] Oct [2..5+1.com UMD PDU -2 UMD PDU (5 bit SN) with Odd Number of LIs • telecommunication design • systems engineering • real-time and embedded systems UMD PDU (5 bit SN) with Even Number of LIs FI E LI1 Present if K >= 3 E LI1 E LI2 .

5*K+1] Oct N LI2 (if K>=3) LI2 © 2009 EventHelix. E LIK-2 E LIK Data .5+1..5*K-1] Oct [2..5*K-3] Oct [2.5+1...5+1.5*K] Oct [2+1. E LIK-1 LIK-1 E LIK Data .5+1.5*K-2] Oct [2+1.5*K-1] Oct [2+1..EventHelix. LIK-2 E LIK-1 LIK Padding LIK-1 R1 R1 FI SN LI1 E E SN Oct 1 Oct 2 Oct 3 Oct 4 Oct 5 Oct [2...5*K] Oct [2.com Inc.5*K-2] Oct [2. 28 .5*K+1] Oct N • telecommunication design • systems engineering • real-time and embedded systems UMD PDU (10 bit SN) with Even Number of LIs R1 E LI1 LI2 .5*K-4] Oct [2.com UMD PDU -3 UMD PDU (10 bit SN) with Odd Number of LIs R1 E LI1 Present if K >= 3 LI2 .5+1. LIK R1 R1 FI SN LI1 E E SN Oct 1 Oct 2 Oct 3 Oct 4 Oct 5 Oct [2+1..5+1.

com UMD PDU Fields . • Specifically. • The sequence number is incremented by one for every UMD PDU. © 2009 EventHelix.EventHelix. 29 . and whether the last byte of the Data field corresponds to the last byte of a RLC SDU.1 Sequence Number (SN) – 5 or 10 bit • telecommunication design • systems engineering • real-time and embedded systems • The SN field indicates the sequence number of the corresponding UMD PDU. the FI field indicates whether the first byte of the Data field corresponds to the first byte of a RLC SDU. Extension bit (E) – 1 bit • The E field indicates whether Data field follows or a set of E field and LI field follows. Framing Info (FI) – 2 bit • The FI field indicates whether a RLC SDU is segmented at the beginning and/or at the end of the Data field.com Inc.

2 Reserved 1 (R1) – 1 bit • telecommunication design • systems engineering • real-time and embedded systems • The R1 field is a reserved field for this release of the protocol. © 2009 EventHelix. 30 . and so on.com Inc. • The second LI present in the RLC data PDU header corresponds to the second Data field element present in the Data field of the RLC data PDU. Length Indicator (LI) .11 bit • The LI field indicates the length in bytes of the corresponding Data field element present in the RLC data PDU delivered/received by an UM or an AM RLC entity. • The first LI present in the RLC data PDU header corresponds to the first Data field element present in the Data field of the RLC data PDU.com UMD PDU Fields . • The value 0 is reserved.EventHelix.

– See next slide © 2009 EventHelix. AMD PDU header consists of a fixed part (fields that are present for every AMD PDU) and an extension part An AMD PDU header needs to be extended when more than multiple Data field elements need to be sent.EventHelix. 31 . – When an UMD PDU header consists of an odd number of LI(s).1 D/C RF P FI SN Data ..com Inc. – In that which case an E and a LI are present for every Data field element except the last. E SN Oct 1 Oct 2 Oct 3 Oct N • telecommunication design • systems engineering • real-time and embedded systems • • • AMD PDU consists of a Data field and an AMD PDU header.com AMD PDU . four padding bits follow after the last LI..

5+1.5*K-1] Oct [2.5*K-2] Oct [2+1... • telecommunication design • systems engineering • real-time and embedded systems Event Number of LIs D/C RF E LI1 LI2 .5+1.5*K+1] Oct N LI2 (if K>=3) LI2 32 .5*K] Oct [2.5+1.5*K] Oct [2+1.com AMD PDU .5*K-4] Oct [2.5*K+1] Oct N © 2009 EventHelix.5*K-2] Oct [2. E LIK-1 LIK-1 E LIK Data .5*K-3] Oct [2..com Inc.5*K-1] Oct [2+1.....5+1.5+1.2 Odd Number of LIs D/C RF E LI1 LI2 . LIK P FI SN LI1 E E SN Oct 1 Oct 2 Oct 3 Oct 4 Oct 5 Oct [2+1.. LIK-2 E LIK-1 LIK Padding LIK-1 P FI SN LI1 E E SN Oct 1 Oct 2 Oct 3 Oct 4 Oct 5 Oct [2. Present if K >= 3 E LIK-2 E LIK Data .5+1.EventHelix.

com Inc. Re-segmentation Flag (RF) – 1 bit • The RF field indicates whether the RLC PDU is an AMD PDU or AMD PDU segment.10 bit • The SN field indicates the sequence number of the corresponding AMD PDU. 33 . © 2009 EventHelix.com AMD PDU Specific Fields Data/Control (D/C) – 1 bit • telecommunication design • systems engineering • real-time and embedded systems • The D/C field indicates whether the RLC PDU is a RLC data PDU or RLC control PDU. Polling bit (P) – 1 bit • The P field indicates whether or not the transmitting side of an AM RLC entity requests a STATUS report from its peer AM RLC entity. Sequence Number (SN) .EventHelix. • The sequence number is incremented by one for every AMD PDU. the SN field indicates the sequence number of the original AMD PDU from which the AMD PDU segment was constructed from. • For an AMD PDU segment.

1 D/C LSF RF P FI SN SO SO Data .EventHelix.. four padding bits follow after the last LI. – In that which case an E and a LI are present for every Data field element except the last. E SN Oct Oct Oct Oct Oct • telecommunication design • systems engineering • real-time and embedded systems 1 2 3 4 5 Oct N • • • AMD PDUs can be further segmented into AMD PDU Segments AMD PDU segment header consists of a fixed part and an extension part. – When an UMD PDU header consists of an odd number of LI(s). – See next slide © 2009 EventHelix.com Inc.com AMD PDU Segment . 34 .. An AMD PDU segment header needs to be extended when more than multiple Data field elements need to be sent.

. LIK LI1 E LI2 RF P FI SN SO E SN Oct 1 Oct 2 Oct 3 Oct 4 Oct 5 Oct 6 Oct 7 Oct [4+1. LIK-2 E LIK-1 LIK Padding LIK-1 LI1 E LI2 (if K>=3) RF P FI SN SO E SN Oct 1 Oct 2 Oct 3 Oct 4 Oct 5 Oct 6 Oct 7 Oct [4.EventHelix.5*K] Oct [4+1..com AMD PDU Segment .5*K-1] Oct [4+1.5+1. 35 .....5+1.com Inc.5*K+1] Oct N • telecommunication design • systems engineering • real-time and embedded systems Even Number of LIs D/C LSF SO E LI1 LI2 ... E LIK-1 LIK-1 E LIK Data .5*K-4] Oct [4.5*K-3] Oct [4.5+1.5*K-2] Oct [4.5*K+1] Oct N © 2009 EventHelix.5+1.5*K-2] Oct [4+1.5*K-1] Oct [4. Present if K >= 3 E LIK-2 E LIK Data .5*K] Oct [4.5+1.2 Odd Number of LIs D/C LSF SO E LI1 LI2 .5+1.

AMD PDU Segment Specific Fields SO start (SOstart) . 36 . • The special SOend value "111111111111111" is used to indicate that the missing portion of the AMD PDU includes all bytes to the last byte of the AMD PDU.com • telecommunication design • systems engineering • real-time and embedded systems • The SOstart field indicates the portion of the AMD PDU with SN = NACK_SN that has been detected as lost at the receiving side of the AM RLC entity.com Inc. © 2009 EventHelix. SO end (SOend) – 15 bit • The SOend field indicates the portion of the AMD PDU with SN = NACK_SN that has been detected as lost at the receiving side of the AM RLC entity.15 bit EventHelix. • The SOend field indicates the position of the last byte of the portion of the AMD PDU in bytes within the Data field of the AMD PDU. • The SOstart field indicates the position of the first byte of the portion of the AMD PDU in bytes within the Data field of the AMD PDU. The first byte in the Data field of the original AMD PDU is referred by the SOstart field value 0.

com Inc. Consists of payload and a RLC control PDU header. Oct 1 Oct 2 Oct 3 Oct 4 Oct 5 Oct 6 Oct 7 Oct 8 Oct 9 • telecommunication design • systems engineering • real-time and embedded systems • STATUS PDU is used to send acknowledgements for received PDUs.. – When necessary one to seven padding bits are included in the end of the STATUS PDU to achieve octet alignment.EventHelix..com STATUS PDU • • D/C CPT ACK_SN ACK_SN E1 NACK_SN E1 E2 NACK_SN NACK_SN E1 E2 SOstart SOstart SOend SOend SOend NACK_SN . The payload starts from the first bit following the RLC control PDU header. © 2009 EventHelix. and it consists of: – One ACK_SN and one E1 – Zero or more sets of a NACK_SN. 37 . an E1 and an E2 – Possibly a set of a SOstart and a SOend for each NACK_SN.

All other values are reserved. • A value of 0 represents the STATUS PDU. Negative Acknowledgement SN (NACK_SN) – 10 bit • The NACK_SN field indicates the SN of the AMD PDU (or portions of it) that has been detected as lost at the receiving side of the AM RLC entity.com Inc. Control PDU Type (CPT) – 3 bit • The CPT field indicates the type of the RLC control PDU. 38 . SOstart and SOend. it interprets that all AMD PDUs up to but not including the AMD PDU with SN = ACK_SN have been received by its peer AM RLC entity. • When the transmitting side of an AM RLC entity receives a STATUS PDU.com Status PDU Fields Acknowledgement SN (ACK_SN) – 10 bit • telecommunication design • systems engineering • real-time and embedded systems • The ACK_SN field indicates the SN of the next not received RLC Data PDU which is not reported as missing in the STATUS PDU.EventHelix. • excluding those AMD PDUs indicated in the STATUS PDU with NACK_SN and portions of AMD PDUs indicated in the STATUS PDU with NACK_SN. © 2009 EventHelix.

Stage 2 Evolved Universal Terrestrial Radio Access (E-UTRA). 39 . Medium Access Control (MAC) protocol specification Evolved Universal Terrestrial Radio Access (E-UTRA).EventHelix. Overall description. Physical channels and modulation 3GPP TS 36.211 © 2009 EventHelix.300 • telecommunication design • systems engineering • real-time and embedded systems Title Evolved Universal Terrestrial Radio Access (E-UTRA) Radio Link Control (RLC) protocol specification Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN).com Inc.322 3GPP TS 36.com Explore More Specification 3GPP TS 36.321 3GPP TS 36.

Wireshark based visual protocol analysis and system design reverse engineering tool.323. SIP. ISUP.com Inc.com Thank You Links EventStudio System Designer 4.com. TCP/IP explained with sequence diagrams. call flows and object oriented design articles. 40 . © 2009 EventHelix. Real-time and Embedded System Articles Real-time and embedded systems.EventHelix. GSM.0 VisualEther Protocol Analyzer 1. H. The following links provide more information about telecom design tools and techniques: Sequence diagram based systems engineering tool.0 Telecom Call Flows TCP/IP Sequence Diagrams Description • telecommunication design • systems engineering • real-time and embedded systems Thank you for visiting EventHelix. LTE and IMS call flows.

Sign up to vote on this title
UsefulNot useful