arief saferman
    • Create new note
    • Create a note from template
      • Sharing URL Link copied
      • /edit
      • View mode
        • Edit mode
        • View mode
        • Book mode
        • Slide mode
        Edit mode View mode Book mode Slide mode
      • Customize slides
      • Note Permission
      • Read
        • Only me
        • Signed-in users
        • Everyone
        Only me Signed-in users Everyone
      • Write
        • Only me
        • Signed-in users
        • Everyone
        Only me Signed-in users Everyone
      • Engagement control Commenting, Suggest edit, Emoji Reply
    • Invite by email
      Invitee

      This note has no invitees

    • Publish Note

      Share your work with the world Congratulations! 🎉 Your note is out in the world Publish Note No publishing access yet

      Your note will be visible on your profile and discoverable by anyone.
      Your note is now live.
      This note is visible on your profile and discoverable online.
      Everyone on the web can find and read all notes of this public team.

      Your account was recently created. Publishing will be available soon, allowing you to share notes on your public page and in search results.

      Your team account was recently created. Publishing will be available soon, allowing you to share notes on your public page and in search results.

      Explore these features while you wait
      Complete general settings
      Bookmark and like published notes
      Write a few more notes
      Complete general settings
      Write a few more notes
      See published notes
      Unpublish note
      Please check the box to agree to the Community Guidelines.
      View profile
    • Commenting
      Permission
      Disabled Forbidden Owners Signed-in users Everyone
    • Enable
    • Permission
      • Forbidden
      • Owners
      • Signed-in users
      • Everyone
    • Suggest edit
      Permission
      Disabled Forbidden Owners Signed-in users Everyone
    • Enable
    • Permission
      • Forbidden
      • Owners
      • Signed-in users
    • Emoji Reply
    • Enable
    • Versions and GitHub Sync
    • Note settings
    • Note Insights New
    • Engagement control
    • Make a copy
    • Transfer ownership
    • Delete this note
    • Save as template
    • Insert from template
    • Import from
      • Dropbox
      • Google Drive
      • Gist
      • Clipboard
    • Export to
      • Dropbox
      • Google Drive
      • Gist
    • Download
      • Markdown
      • HTML
      • Raw HTML
Menu Note settings Note Insights Versions and GitHub Sync Sharing URL Create Help
Create Create new note Create a note from template
Menu
Options
Engagement control Make a copy Transfer ownership Delete this note
Import from
Dropbox Google Drive Gist Clipboard
Export to
Dropbox Google Drive Gist
Download
Markdown HTML Raw HTML
Back
Sharing URL Link copied
/edit
View mode
  • Edit mode
  • View mode
  • Book mode
  • Slide mode
Edit mode View mode Book mode Slide mode
Customize slides
Note Permission
Read
Only me
  • Only me
  • Signed-in users
  • Everyone
Only me Signed-in users Everyone
Write
Only me
  • Only me
  • Signed-in users
  • Everyone
Only me Signed-in users Everyone
Engagement control Commenting, Suggest edit, Emoji Reply
  • Invite by email
    Invitee

    This note has no invitees

  • Publish Note

    Share your work with the world Congratulations! 🎉 Your note is out in the world Publish Note No publishing access yet

    Your note will be visible on your profile and discoverable by anyone.
    Your note is now live.
    This note is visible on your profile and discoverable online.
    Everyone on the web can find and read all notes of this public team.

    Your account was recently created. Publishing will be available soon, allowing you to share notes on your public page and in search results.

    Your team account was recently created. Publishing will be available soon, allowing you to share notes on your public page and in search results.

    Explore these features while you wait
    Complete general settings
    Bookmark and like published notes
    Write a few more notes
    Complete general settings
    Write a few more notes
    See published notes
    Unpublish note
    Please check the box to agree to the Community Guidelines.
    View profile
    Engagement control
    Commenting
    Permission
    Disabled Forbidden Owners Signed-in users Everyone
    Enable
    Permission
    • Forbidden
    • Owners
    • Signed-in users
    • Everyone
    Suggest edit
    Permission
    Disabled Forbidden Owners Signed-in users Everyone
    Enable
    Permission
    • Forbidden
    • Owners
    • Signed-in users
    Emoji Reply
    Enable
    Import from Dropbox Google Drive Gist Clipboard
       Owned this note    Owned this note      
    Published Linked with GitHub
    • Any changes
      Be notified of any changes
    • Mention me
      Be notified of mention me
    • Unsubscribe
    # <center><i class="fas fa-clipboard-list"></i> MAC Scheduler in LTE</center> ###### tags: `O-RAN` :::info **Goal:** Exploring MAC Scheduler in LTE and read all the paper related to it - [x] Understand MAC Scheduler in LTE - [X] Explore the MAC Scheduler Paper in IEEE - [x] Science behind in MAC Scheduler ::: :::spoiler **References** - [Web](https://yatebts.com/an-introduction-to-the-lte-mac-scheduler/#:~:text=MAC%20Scheduling%20in%20LTE&text=Sitting%20just%20above%20the%20Physical,of%20Service%20for%20UE%20connections.) - [Paper IEEE](https://remote-lib.ui.ac.id:2082/document/9271427) - [OFDM](https://blog.yate.ro/2015/05/20/ofdm-the-science-behind-lte/) ::: ## MAC Scheduler in RN-LTE Network MAC scheduler is an essetial component of the LTE radio network. They are sitting just above the Physical layer. The MAC Scheduler assigns bandwidth resources to user equipment and is responsible for deciding on how uplink and downlink channels are used by the eNodeb and the UEs of a cell. it also enforces the necessary QoS for UE connections. QoS is set of rules that come from the PCRF in the core network. These rules define priority, bit rate and latency requirements for different connections to the UE. They usually based on the types of applications using UE connection. For example, the QoS requirements for a VoLTE call are different from those for checking the e-mail. By looking this image below, MAC scheduler has control over OFDM modulation in sense of decides, according to information that is received from other LTE nework components. In this figure, the resource element (sub-carrier) is represented on the frequency axis, while the sub-frames are represented on the time axis. ![](https://i.imgur.com/DYobeWa.png) :::info **This figure shows downlonk scheduling, but the MAC Scheduler controls uplink scheduling in a similar way** ::: In order to take its resource allocation decisions, the MAC Scheduler receives information such as: * QoS data from the PCRF: minimum guaranteed bandwidth, maximum allowed bandwidth, packet loss rates, relative priority of users. * Messages from the UEs regarding the radio channel quality, the strength or weakness of the signal. * Measurements from the radio receiver regarding radio channel quality, noise and interference. * Buffer status from the upper layers about how much data is queued up waiting for transmission. ![](https://i.imgur.com/6CefeNn.png) Typically, a MAC Scheduler can be programmed to support one scheduling algorithm with many parameters. Here are some example of scheduling algorithms: * **Round Robin** - used for testing purposes and uses equal bandwidth for all UEs without accounting for channel conditions * **Proportional Fairness** - tries to balance between the QoS priorities and total throughput, usually preferred in commercial networks * **Scheduling for Delay-Limited Capacity** - guarantees that the MAC Scheduler will always prioritize applications with spesific latency requirements * **Maximum C/I** - guarantees that the MAC Scheduler will always assign resource blocks to the UE with the best channel quality One of the key features of LTE is the ability to control and prioritize bandwidth across users. It is the MAC Scheduler that gives LTE this capability. ## OFDM - The Science Behind LTE No one wants to see low quality video that they're watching on Youtube. We all want to send big chunks of data as big as and as fast as we could send, while still keeping the integrity of the data. Nevertheless, the faster we send the data, the more likely it is to experience transmission problems, especially due to interference or weak signal. OFDM is the radio science behind huge bandwidth capabilities we see in LTE. OFDM splits data into small sub-carriers, also known as data streams, on neighboring frequencies, over a single channel. It allows sending more data than through single carrier modulation techniques, and at a higher rate. OFDM also handles phenomena such as interference, noise or multipath significantly more efficiently than other modulation methods. ### How It Works The following explanation is for non-engineers and is meant to shed some light on OFDM. We'll use a theoretical example: a bandwidth of 1 MHz and round numbers, which are easier to remember and apply to real-life scenarios. Traditional single carrier modulation uses only one frequency to send the bits, as seen below. ![](https://i.imgur.com/jTPmcSl.png) In OFDM, the bandwidth of 1 MHz band is split into, say 1000 sub-carriers of 1 kHz, and each of them sends one symbol per millisecond. ![](https://i.imgur.com/oWog06a.png) Next, OFDM uses the FFT (Fast Fourier Transform) algorithm and its inverse to effectively retrieve the original data bits from the symbols and vice versa. OFDM has a special property called orthogonality, which essetially means that sub-carriers are spaced in such a way that they only partially overlap, as the peak of each sub-carrier insersects the zero crossing of the neighboring sub-carrier. This characteristic is perfectly illustrated in the image below, where you can see 5 of the 1000 1 kHz sub-carriers in the frequency domain, in a single channel. Orthogonality is what allows us to pack sub-carriers really tight, without wasted frequencies between them as in traditional cases, which require using guard bands. ![](https://i.imgur.com/poO1SoU.png) The data rate obtained using OFDM is the same as in the case of single-carrier modulation, so you might wonder why we use it so enthusiastically in LTE, which is what we'll explain below. ### Effective against multipath propagation and interference Multipath propagation occurs the moment a radio signal bounces-off obstacles that appear in its path: water sources, hills and mountains, buildings, tree etc. Multipath causes the transmitted signal to be sent on two or more paths to the receiver, making it difficult for the receiver to interpret what it receives. Only some frequencies are prone to experience multipath. In single carrier modulation systems, it has a damaging impact throughout the whole frequency and affects all of the data symbols. ![](https://i.imgur.com/lKYaij2.png) Take a look at the image below: only one carrier experiences multipath, but since all sub-carrier transport redundant copies of the sent symbols, data loss is minimal. ![](https://i.imgur.com/E7CV1vj.png) OFDM is also effective against interference because only some of the data streams will be affected by this phenomenon and data can be more easily recovered with redundant error-correction coding. ### **Spectral Eficiency** When using OFDM, LTE can tailor the modulation to make the best possible use of the available radio path to and from the UEs. Because of the OFDM carrier structure, LTE can take advantage of the changes in channel conditions and uses different modulations depending how close or far the UEs are from the transmitter. Because it uses OFMD, LTE can dynamically change the symbol alphabet, dependign on the radio conditions, for each individual sub-carrier. For example, if you're sending data close to the transmitter, LTE will apply a 64-QAM modulation scheme, that is 6 bits/symbol. In extreme cases, LTE can even use BPSK (1 bit/symbol). ### **Disadvantages** OFDM also has its downsides. It has high peak-to-average power ratio, and requires a highly linear and oversized power amplifier that usually has a low efficiency. We can see in the image below, you can see a typical OFDM peak-to-average power ratio. This occurs because because multiple sub-carriers with different phases combine constructively in the time domain. Typically, to obtain a 5 W average output power, an OFDM system requires a 100 W power amplifier, representing an increase by a factor of 20 from the actual 5 W output. Otherwise, the distortion is far too destructive to allow OFDM to function normally. ![](https://i.imgur.com/SzGPDoe.png) OFDM is also very sensitive to Doppler shift. This phenomenon occurs when the UE is moving, thus making the frequency of the signal received different from the frequency of the initially transmitted signal. Among its effects in OFDM, Doppler shift Deteriorates synchronization, data recovery, and destroys the orthogonality of sub-carriers. :::warning **Term of Abbreviations** - LTE: Long-Term Evolution * OFDM: Orthogonal Frequency Division Multiplexing * FFT: Fast Fourier Transform * MAC: Medium Access Control * PCRF: Policy and Charging Rules Function * QoS: Quality of Service * UE: User Equipment * UMTS: Universal Mobile Telecommunications System * VoLTE: Voice over LTE * RN: Radio Network :::

    Import from clipboard

    Paste your markdown or webpage here...

    Advanced permission required

    Your current role can only read. Ask the system administrator to acquire write and comment permission.

    This team is disabled

    Sorry, this team is disabled. You can't edit this note.

    This note is locked

    Sorry, only owner can edit this note.

    Reach the limit

    Sorry, you've reached the max length this note can be.
    Please reduce the content or divide it to more notes, thank you!

    Import from Gist

    Import from Snippet

    or

    Export to Snippet

    Are you sure?

    Do you really want to delete this note?
    All users will lose their connection.

    Create a note from template

    Create a note from template

    Oops...
    This template has been removed or transferred.
    Upgrade
    All
    • All
    • Team
    No template.

    Create a template

    Upgrade

    Delete template

    Do you really want to delete this template?
    Turn this template into a regular note and keep its content, versions, and comments.

    This page need refresh

    You have an incompatible client version.
    Refresh to update.
    New version available!
    See releases notes here
    Refresh to enjoy new features.
    Your user state has changed.
    Refresh to load new user state.

    Sign in

    Forgot password
    or
    Sign in via Google Sign in via Facebook Sign in via X(Twitter) Sign in via GitHub Sign in via Dropbox Sign in with Wallet
    Wallet ( )
    Connect another wallet

    New to HackMD? Sign up

    By signing in, you agree to our terms of service.

    Help

    • English
    • 中文
    • Français
    • Deutsch
    • 日本語
    • Español
    • Català
    • Ελληνικά
    • Português
    • italiano
    • Türkçe
    • Русский
    • Nederlands
    • hrvatski jezik
    • język polski
    • Українська
    • हिन्दी
    • svenska
    • Esperanto
    • dansk

    Documents

    Help & Tutorial

    How to use Book mode

    Slide Example

    API Docs

    Edit in VSCode

    Install browser extension

    Contacts

    Feedback

    Discord

    Send us email

    Resources

    Releases

    Pricing

    Blog

    Policy

    Terms

    Privacy

    Cheatsheet

    Syntax Example Reference
    # Header Header 基本排版
    - Unordered List
    • Unordered List
    1. Ordered List
    1. Ordered List
    - [ ] Todo List
    • Todo List
    > Blockquote
    Blockquote
    **Bold font** Bold font
    *Italics font* Italics font
    ~~Strikethrough~~ Strikethrough
    19^th^ 19th
    H~2~O H2O
    ++Inserted text++ Inserted text
    ==Marked text== Marked text
    [link text](https:// "title") Link
    ![image alt](https:// "title") Image
    `Code` Code 在筆記中貼入程式碼
    ```javascript
    var i = 0;
    ```
    var i = 0;
    :smile: :smile: Emoji list
    {%youtube youtube_id %} Externals
    $L^aT_eX$ LaTeX
    :::info
    This is a alert area.
    :::

    This is a alert area.

    Versions and GitHub Sync
    Get Full History Access

    • Edit version name
    • Delete

    revision author avatar     named on  

    More Less

    Note content is identical to the latest version.
    Compare
      Choose a version
      No search result
      Version not found
    Sign in to link this note to GitHub
    Learn more
    This note is not linked with GitHub
     

    Feedback

    Submission failed, please try again

    Thanks for your support.

    On a scale of 0-10, how likely is it that you would recommend HackMD to your friends, family or business associates?

    Please give us some advice and help us improve HackMD.

     

    Thanks for your feedback

    Remove version name

    Do you want to remove this version name and description?

    Transfer ownership

    Transfer to
      Warning: is a public team. If you transfer note to this team, everyone on the web can find and read this note.

        Link with GitHub

        Please authorize HackMD on GitHub
        • Please sign in to GitHub and install the HackMD app on your GitHub repo.
        • HackMD links with GitHub through a GitHub App. You can choose which repo to install our App.
        Learn more  Sign in to GitHub

        Push the note to GitHub Push to GitHub Pull a file from GitHub

          Authorize again
         

        Choose which file to push to

        Select repo
        Refresh Authorize more repos
        Select branch
        Select file
        Select branch
        Choose version(s) to push
        • Save a new version and push
        • Choose from existing versions
        Include title and tags
        Available push count

        Pull from GitHub

         
        File from GitHub
        File from HackMD

        GitHub Link Settings

        File linked

        Linked by
        File path
        Last synced branch
        Available push count

        Danger Zone

        Unlink
        You will no longer receive notification when GitHub file changes after unlink.

        Syncing

        Push failed

        Push successfully