srsRAN Project Logo
latest

General

  • Getting Started
  • Feature List
  • Contributions
    • FAQ
      • 1. What is a Copyright License Agreement (CLA) and why do I need one?
      • 2. How do I complete and submit the CLA?
      • 3. How will my contributions to the srsRAN Project be used?
      • 4. If I do not own the copyright in the entire work of authorship?
  • Reporting
    • Issues
    • Vulnerabilities
    • Support
  • Release Notes

User Manual

  • Installation Guide
    • Build Tools and Dependencies
    • RF-drivers
    • Clone and Build
    • PHY testvectors
    • Packages
      • Arch Linux
  • Running srsRAN Project
    • Baseline Requirements
    • System Preparation
    • Running the gNB
  • Console Reference
  • Outputs
    • Logs
    • PCAPs
      • MAC PCAPs
      • NGAP PCAPs
  • Configuration Reference
    • Format
    • Configuration Parameters
      • amf
      • rf_driver
      • cell_cfg
      • log
      • pcap
      • expert_phy
  • Troubleshooting
    • Performance Tuning
      • CPU Performance Mode
      • Performance Configuration Script
    • USRP Configuration
      • USRP Time Calibration

Developers Guide

  • srsRAN Project Software Architecture
    • High Level Architecture
      • Components and Interfaces
  • CU
    • CU-CP
    • CU-UP
  • DU
    • DU-High
      • DU Manager
        • Overview
      • F1AP-DU
        • Overview
      • Radio Link Control (RLC)
        • RLC Transparent Mode(TM)
        • RLC Unacknowledged Mode(UM)
        • RLC Acknowledged Mode (AM)
      • MAC
        • Implementation
    • DU-Low
  • Interfaces
    • E1
    • E2
    • F1
    • FAPI
    • Open FrontHaul
      • Overview
      • Implementation
    • NG
    • O1
  • ASN 1 Packing & Unpacking
  • Code Style Guide
    • Language and libraries
      • C & C++ version
      • Use of the C++ standard library
    • Mechanical source aspects
      • Source Code Formatting
      • Comments
        • File Headers
        • Class Overviews
        • Method Information
        • Member Variable Information
      • Header Guards
      • #include Style
      • Language and compiler aspects
        • Treat compiler warnings as errors
        • Code Portability
        • Avoid RTTI and Exceptions
        • Use of auto
    • Style Aspects: High Level Issues
      • Self-contained Headers
      • Using #include Sparingly
      • Using “Internal” Headers
      • Use of namespace
      • Using “early exits” and continue
      • Avoid else after a return statement
      • Use of Static Helper Functions
    • Style Aspects: Low Level Issues
      • Naming Conventions
      • Assert and expect
      • Do not use using namespace std
      • Using Range for Loops
      • Loop Structure
      • Using Pre-increment
      • Use of Anonymous Namespaces
      • Using C++ Casts
    • Recommendations
      • Function and Class Length
      • Scope
      • Logical Operators
      • Using References(&) Over Pointers(*)
      • Const Correctness
      • Avoid Complex Expressions
      • Magic numbers
      • Fixed Width Integer Types
      • Function signatures
      • Class Layout Example
    • Self Generating Documentation
      • Comment Formatting DOs and DONTs
      • Doxygen Commands
    • Commit Formatting

Knowledge Base

  • O-RAN gNB Overview
    • Introduction
    • Split 7.2x Architecture
    • srsRAN Project gNB
    • Further Reading
  • O-RAN gNB Components
    • Control Unit (CU)
    • Distributed Unit (DU)
      • DU-high
      • DU-low
  • gNB Interfaces
    • E1
    • E2
    • F1
      • F1-C
      • F1-U
    • FAPI
    • NG
      • NG-C
      • NG-U
    • O1
    • Open FrontHaul

Tutorials

  • Tutorials

Links

  • Website
  • Source code
  • Report an issue
  • Discussions Board
  • Twitter
srsRAN Project
  • »
  • DU »
  • Radio Link Control (RLC)
  • Edit on GitHub
Next Previous

Radio Link Control (RLC)¶

RLC layer connects the MAC and the F1AP/PDCP, as shown in Fig. 2, and provides that transfer services to these layers.

../../../../../_images/rlc_stack.png

Fig. 2 RLC stack¶

It does this, by providing three different modes:

  • Transparent Mode (TM)

TM is used only in control signaling (SRB0 only) and provides data transfer services without modifying the SDUs/PDUs at all.

  • Unacknowledged Mode (UM)

UM can only be used in data traffic (DRBs only) and provides data transfer services with segmentation/reassembly. It is usually used in delay-sensitive and loss-tolerant traffic, as it does not provide re-transmissions.

  • Acknowledged Mode (AM)

AM can be used in data and control traffic (mandatory for SRBs, optional for DRBs) and provides data transfer services with segmentation and ARQ procedures. This mode is usually used for traffic that is more loss-sensitive, but more delay-tolerant.


  • RLC Transparent Mode(TM)
  • RLC Unacknowledged Mode(UM)
  • RLC Acknowledged Mode (AM)
Next Previous

© Copyright 2023-2023, Software Radio Systems.. Revision 20bac3d0.

Built with Sphinx using a theme provided by Read the Docs.
Read the Docs v: latest
Versions
latest
Downloads
pdf
html
epub
On Read the Docs
Project Home
Builds