cnsrl
  • NEW!
    NEW!  Connect Ideas Across Notes
    Save time and share insights. With Paragraph Citation, you can quote others’ work with source info built in. If someone cites your note, you’ll see a card showing where it’s used—bringing notes closer together.
    Got it
        • 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
          • Owners
          • Signed-in users
          • Everyone
          Owners Signed-in users Everyone
        • Write
          • Owners
          • Signed-in users
          • Everyone
          Owners 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
      • 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 Help
    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
    Owners
    • Owners
    • Signed-in users
    • Everyone
    Owners Signed-in users Everyone
    Write
    Owners
    • Owners
    • Signed-in users
    • Everyone
    Owners 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
    1
    • Any changes
      Be notified of any changes
    • Mention me
      Be notified of mention me
    • Unsubscribe
    --- tags: 技術文章, 5G, RAN GA: UA-79596126-4 title: (待補)5G 存取網路簡介 --- ###### 作者: 大叔 ###### 撰寫日期: 2020/10/16 {%hackmd BJrTq20hE %} # 目錄 [TOC] # 無線通訊網路 一般來說,網路可以分為行動通訊與固網通訊,行動通訊指的是透過無線電信網路上網,其經過無線存取網路 (Radio Access Network, RAN) 與核心網路 (Core Network, CN);而固網通訊指的是透過有線寬頻網路上網,會經過寬頻接取網路 (Broadband Access Network),這篇僅會介紹行動通訊的部分。 ![](https://i.imgur.com/8n210Wc.png, "Access Network") # 無線存取網路 存取網路 (Access Network) 為將用戶終端連接置網際網路的的媒介,而無線端的存取網路被稱為 RAN。 而大家所知的基地台 (BaseStation) 就是屬於 RAN 的其中一環。從 1G 開始到目前的 5G 網路,其整個通訊網路邏輯架構一直都是手機→存取網→承載網→核心網→承載網→存取網→手機,也就是編碼解碼、調變解調、加密解密。 一個基地台通常包含 BBU (Baseband Unit, 基頻模組)、RRU (Remote Radio Unit, 遠端射頻模組)、饋線、天線。在最早期的時候,基地台視一體化的,也就是說 BBU、RRU 和供電設備等都是在同一個櫃子或機房裡,接著就把 RRU 和 BBU 拆分。 ![](https://i.imgur.com/rfACjK3.png) 這樣的部屬方式由於天線與 RRU 的距離太常導致訊號損耗嚴重,饋線的成本也較高。故接下來的的部屬方式就是將 RRU 拉遠,這樣 RAN 就變成了 D-RAN (Distributed RAN)。 ![](https://i.imgur.com/Z8uBngW.png) 但是在 D-RAN 的架構下,營運商仍然需要承擔巨大的成本。為了擺放 BBU 和相關設備(電源、空調等),還是需要租賃或建設旭多室內機房,而大量的機房就等於大量的成本。再來是基頻處裡的笑路相當低落,為了在區域處於峰值負載時提供足夠的傳輸容量,需要預備高效的 BBU,但整體而言 BBU 的利用率只達到 30% 左右。這時營運商就想了一套新的架構,將所有的 BBU 集中至中央機房(Central Office, CO),這就是 C-RAN (Centralized-RAN)。 ![](https://i.imgur.com/SgcRAr6.png) 除了集中資源外,C-RAN 透過 SDN/NFV 等相關技術將在雲端架構下進行基頻處理虛擬化,不但減緩了分布式架構的挑戰,同時讓營運商在邁向雲端化行動網路上跨出第一步,並且為進展 5G 網路技術最重要的一步。 # 5G 存取網路 在 5G 網絡中,RAN 不再是由 BBU、RRU、天線等這些東西組成,而是被重構為以下 3 個功能: * CU (Centralized Unit, 集中模組): 將 BBU 的非即時部分將分割出來,負責處理非即時協議和服務。 * DU (Distribute Unit, 分布模組): BBU 的剩餘功能,負責處理物理層協議和實時服務。 * AAU (Active Antenna Unit, 主動式天線模組): BBU 部分物理層處理功能與 RRU 及天線合併成 AAU ![](https://i.imgur.com/khh1uSL.png) IMT-2020 有提到 5G 網路需求大致上可分為 3 大類,分別是大流量行動寬頻業務(Enhanced Mobile Broadband, eMMB)、超高可靠超低時延通信(Ultra-reliable and Low Latency Communications, URLLC)、大數量連接之物聯網通訊(Massive Machine Type Communications, mMTC)。由於 5G 網路的需求多樣化,需要有多樣化的部屬方式才能負荷整體網路需求。 依據 5G 提出的標準,CU、DU、AAU 可以採取分離或共構的方式,所以會出現多種網路部屬型態:

    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