Wire Lab 讀書會
      • 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
    • Any changes
      Be notified of any changes
    • Mention me
      Be notified of mention me
    • Unsubscribe
    # 陳毅 - 讀書會 - 21/08/28 :::info - [x] 閱讀 Netmanias-17-EMM Procedure 6. Handover without TAU - Part 2. X2 Handover ::: This document will focus on procedures for X2 handover that is performed through the x2 interface in an intra-LTE environment. So, we will assume both source and target eNBs are connected to the same MME/S-GW. ## Concept of X2 Handover ### X2 Protocol Stacks - LTE networks allow eNBs to directly exchange status information with each other via the X2 interface - Without any intervention by EPC nodes ![](https://i.imgur.com/0BOeaFa.png) 在 Control plane 上,兩個 eNB 在單一的 Stream Control Tansmission Protocol 上為多個用戶提供 X2 Application Protocol (X2AP) signaling。 在 X2AP 層上,會由 eNB UE X2AP ID 區別使用者,在 Data plane 上,兩個 eNB 之間使用 GPRS Tunneling Protocol (GTP) tunnel 連線。 ### X2AP Functions X2AP signaling information 可以被大致分為兩個類別: - 與 load/interference (Load Management function) 有關 - 與 handover (Mobility Management, Mobility Parameter Management, Mobility Robustness Optimization functions) 有關 ![](https://i.imgur.com/2Fhf6Ib.png) 與 2G/3G 想比,LTE 有著更低的細胞覆蓋率但會使用更多 base station 改善該問題。 因此,適用在 2G/3G 的管理方式已經不適用於 LTE 網路。為了解決這個問題,LTE 網路、X2AP protocol 被定義來提供 providing Self-Organizing Networks (SON) functionality,他可以允許 eNB 連結到鄰近的 eNB(s)、蒐集 status information 以及使用收集到的資料對其參數做自動優化與調整。 - Load Management enhances the interception performance among cells by exchanging load and interference information between two eNBs - eNB Configuration Update performs automatic eNB configuration - Mobility Parameters Management negotiates on handover triggering setting information among peer eNBs and uses the information for handover optimization - Mobility Robustness Optimization provides information on a handover failure event - Energy Saving help eNBs to consume less energy by exchanging information on cell activation/deactivation ### X2 Messages Relating to Mobility Management Function response message from a target eNB is required during the handover preparation procedure. - Handover Request message This message is used during the handover preparation phase. It is delivered by a source eNB to a target eNB, and includes a user’s UE context. - Handover Request Acknowledge message This message is used during the handover preparation phase. It is delivered by the target eNB to the source eNB if resource allocation is successfully completed by the target eNB - Handover Preparation Failure message This message is used during the handover preparation phase. It is delivered by the target eNB to the source eNB if resource allocation at the target eNB fails. - SN Status Transfer message This message is used during the handover execution phase. The source eNB delivers it to the target eNB to indicate from which packet it should receive or send. - UE Context Release message This message is used during the handover completion phase. The target eNB sends it to the source eNB, to request release of the UE context. - Handover Cancel message This message is used during the handover preparation phase. The source eNB sends it to the target eNB when it needs to cancel a handover in preparation. ![](https://i.imgur.com/vyVwGlL.png) ### X2 Handover Procedure at a Glance 為了方便,S-GW 與 P-GW 會標記為 **SAE-GW**,source 與 target eBNs 被標記為 **SeNB** 與 **TeNB**。 ![](https://i.imgur.com/XNhSrsk.png) #### Before X2 Handover 觀察上圖,UE 由 eNB A 服務,當 UE 偵測到 measurement event,便會發送 **Measurement Report** message 給 eNB A。 #### X2 Handover Preparation - SeNB 會選擇出 TeNB 為 Handover 的對象 - TeNB 會事先準備服務使用者所需要的資源 (e.g. C-RNTI),再發送給 SeNB #### X2 Handover Execution ![](https://i.imgur.com/nydP74F.png) #### X2 Handover Completion ![](https://i.imgur.com/6qNZJ0C.png) ### UE State and Connection Information Before and After X2 Handover The figure below illustrates the connection establishments in the user/control planes, and the UE and MME states before, during and after the X2 handover. ![](https://i.imgur.com/Xvax0Xy.png) ![](https://i.imgur.com/ZCFFm04.png) ## Procedure of X2 Handover 下圖繪製出在 X2 Handover 開始前與 X2 Handover preparation phase 時 EPS bearer 與 signaling connection 的狀態。 ![](https://i.imgur.com/IfpkVq2.png) ### Before Handover #### 1. Measurement Report 當 measurement event 被觸發,UE 會測量鄰近細胞的訊號強度並發送 **Measurement Report** message 給 Serving cell。 ### Handover Preparation #### 2. Handover Decision SeNB 會依據 Measurement Report 選擇出 TeNB,在真實的 Handover procedure 中是可以選擇多個 TeNB 的,不過在文件中一概假設僅有一個 eNB 會被選為 TeNB。 #### 3. Deriving the AS Security Base Key (KeNB*) to be Used by the Target eNB 在 handover 的過程中,Seving eNB 會被切換,因此: - RRC signaling messages and user packets still have to be delivered seamlessly and securely - Over the radio link, it is AS security keys that ensure secured delivery of such data - AS security keys are derived from $K_{eNB}$, the AS security base key. $K_{eNB}$ is derived from $K_{ASME}$ by MME after user authentication, and sent to eNB - X2 handover is performed between two eNBs without any intervention by EPC (MME), the target eNB cannot obtain $K_{eNB}$* ($K_{eNB}$ to be used by the target eNB) from MME. So, the source eNB derives it and sends to the target eNB. ![](https://i.imgur.com/XmIEqdF.png) #### 4. Requesting X2 Handover Handover Request message 包含了 UE context 的資訊。 此外,UE history 包含了在這次的 Handover 之前,UE 連線過的細胞。 ![](https://i.imgur.com/yCjtjMq.png) #### 5. Preparing X2 Handover ![](https://i.imgur.com/ZkZ92nb.png) :::info **懶人包** - 透過 $K_{eNB}$ 產生出其他 AS Security key。 - 設定 E-RAB,如果 SeNB 提供的 QoS 在 TeNB 也同樣可行,就會建立 UL S1 bearer connection。 - 基於 E-RAB QoS 資訊,TeNB 會保留 UE 在 radio link 所需的 RRC 資源,並分配 C-RNTI。 - 當 UE 執行 Handover,位於 SeNB 的下行封包需要 Forward 到 TeNB 上,為了達到這個需求,TeNB 會分配 X2 Target eNB TEID 以建立 X2 transport bearer (GTP tunnel)。 ::: #### 6. Notifying the Source eNB of Preparation Completion TeNB 會傳送在上一步提到與資源有關的資訊給 SeNB,這些資訊會包含在 **Handover Request Ack** 之中。 ![](https://i.imgur.com/egFEok5.png) #### 7. Establishing X2 Transport Bearer for DL Packets Delivery 收到 **Handover Request Ack** 後,SeNB 會知道 TeNB 已經有能力服務 UE。這時,SeNB 就會使用 X2 Target eNB TEID 並建立 X2 transport bearer,以開始傳送下行封包。 ### Handover Execution ![](https://i.imgur.com/LCBtFag.png) #### 8. Commanding a Handover Once the source eNB completes the handover preparation with the target eNB, it orders the UE to perform a handover by sending a **Handover Command** message. #### 9. Executing a Handover The UE, from the received Handover Command message, obtains C-RNTI and DRB ID to be used at the target cell, and detaches from the source eNB. Now, all packet delivery between the UE and the source eNB is stopped, and the handover interruption time period begins. #### 10. AS Security Setup The UE derives AS security keys to be used over the radio link of the target eNB. First it derives $K_{eNB}$* (AS base key for the target eNB) from the source eNB’s $K_{eNB}$, the target cell’s PCI and frequency. Next, it derives AS security keys for the target eNB ($K_{RRCint}$, $K_{RRCenc}$, $K_{UPenc}$) by using the AS security algorithms that the target eNB selected. #### 11. Notifying the No. of the Packet to Send/Receive ![](https://i.imgur.com/DRwYOCW.png) #### 12. - 14. UE’s Access to the Target eNB ![](https://i.imgur.com/PYYbbaP.png) #### 15. Secure Communication over the Radio Link All RRC signaling messages and user packets sent over the radio link between the UE and the target eNB are now securely delivered using the AS security keys. RRC signaling messages are integrity protected and encrypted while user packets are encrypted before being sent. #### 16. Resuming DL Packet Delivery to the UE ![](https://i.imgur.com/Ty1Gy43.png) ### Handover Completion ![](https://i.imgur.com/NFhnwEH.png) #### 17. Requesting the EPS Bearer (S1 Bearer) Path Switch TeNB 藉由發送 **Path Switch Request** message 通知 EPC: UE 的 Serving cell 已經改變,以更動 EPS bearer 的路徑。 #### 18. - 23. Modifying the EPS Bearer MME 會透過 **Modify Bearer Request** message 將 Target eNB 分配的 S1 Target eNB TEID 發送給 S-GW。 這樣可以通知 S-GW: DL S1 bearer 已經切換並要求它切換 bearer path,隨後,S-GW 根據要求建立 DL S1 bearer 以連線到 target eNB。 根據 UE initial attache 的 options set,部分 S-GW 需要在 EPS session 建立後且 UE 的 Serving cell 改變的情況下透過 **Modify Bearer Request** 通知 P-GW,P-GW 會根據 EPS session modification procedure 定義的方式回報給 PCRF 知道 UE 的 Serving cell 已被更動。 #### 24. Modifying the EPS Bearer Path and Sending EM Packets ![](https://i.imgur.com/hmusOBl.png) #### 25. Packet Re-odering ![](https://i.imgur.com/TbxIPJC.png) #### 26. Notifying the Modified Bearer Path ![](https://i.imgur.com/H5B2bjh.png) #### 27. Notifying to Release UE Context Target eNB 會保存 {NCC, NH} 並藉由發送 **UE Context Release** 告訴 Source eNB 可以釋放 UE context (因為 UE's bearer path 已經切換了)。 ## EPS Entity Information: Before/After X2 Handover ### Before X2 Handover UE stays in EMM-Registered and ECM/RRC-Connected state. ![](https://i.imgur.com/HXOrvIm.png) ### After X2 Handover UE still remains in EMM-Registered and ECM/RRC-Connected state. In the figure, information elements that are changed after the handover are marked in blue. ![](https://i.imgur.com/60TGPuW.png)

    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