Wire Lab 讀書會
  • 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
    • Any changes
      Be notified of any changes
    • Mention me
      Be notified of mention me
    • Unsubscribe
    # 蔡瀚興-讀書會-21/07/17 ## 推薦連結 - [文件翻譯](https://www.cnblogs.com/soqu36/articles/12767236.html) ## <font color="FF0000">Introduction</font> 無線通信,因為數據有安全上的風險。用戶的位置和移動軌跡,會引起隱私侵權。因此提供安全特性保護用戶的隱私。 ## <font color="FF0000">Scope and Concept of LTE security</font> 1. <font color="0000ff">LTE Authentication:</font> 在UE和網絡之間執行相互的鑑權。 2. <font color="0000ff">NAS Security:</font> 在UE和MME之間執行完整性保護驗證和NAS信令的加密(加密和解密) 3. <font color="0000ff">AS Security:</font> 在UE和eNB之間執行完整性保護驗證和RRC信令消息的加密,執行用戶數據的加密。 ![](https://i.imgur.com/GEizm27.jpg) ![](https://i.imgur.com/ByIVjXa.jpg) ## <font color="FF0000">LTE authentication</font> 在移動網絡中,鑑權是判定試圖接入網絡的用戶是否是合法的簽約用戶 ### <font color="0000ff">EPS AKA (Authentication and Key Agreement)</font> 1. **HSS generates EPS authentication vectors** (RAND, AUTN, XRES, K-ASME) and sends them to MME. 2. The **MME selects one of the EPS authentication vectors** and uses it for two-way authentication, and **shares the same authentication key-KASME** with each other. ### <font color="0000ff">ASME (Access Security Management Entity)</font> 是一個**從 HSS 接收 Top-Level key 的實體**,用在 access network 中。在EPS中,**MME充當ASME的功能**,K-ASME作為一個 Top-Level key 在接入網絡中使用。MME代表HSS使用K-ASME和UE實施相互鑑權。一旦相互鑑權,UE和MME共享K-ASME作為鑑權秘鑰。 ### <font color="0000ff">**Process:**</font> 1. 當用戶請求接入LTE網絡時,在用戶和網絡之間使用EPS KAK過程來進行相互鑑權。MME使用IMSI來標識用戶,並向HSS請求鑑權向量(AV)。 2. HSS使用EPS AKA算法生成AV,AV={RAND, XRES, AUTN-HSS, K-ASME},並轉發給MME 3. 在MME存儲AV之後,從中選擇一個,使用這個AV來和UE執行相互鑑權,並轉發RAND和AUTH-HSS給UE 4. UE使用EPS AKA算法計算出RES,AUTN-UE和K-ASME 5. UE比較自己的AUTN-UE和從MME接收到的AUTH-HSS來執行網絡鑑權 6. 一旦鑑權完成,發送RES給MME,MME比較從HSS接收到的XRES和從UE接收到的RES來執行用戶鑑權 7. 如果鑑權成功,則他們就共享了相同的K-ASME(儘管K-ASME不在UE和MME之間傳送) ## <font color="FF0000">NAS Security</font> NAS security is designed to **safely transmit signaling information** between the wireless link UE and MME 1. **Perform integrity check:** Most required. *EX:integrity key (K-NASint)* 2. **Encryption of NAS signaling messages:** Optional. *EX:encryption key (K-NASenc)* ### <font color="0000ff">**Process:**</font> 1. 一旦UE和MME相互鑑權完畢並具有相同的秘鑰K-ASME,NAS安全過程開始 2. 當傳送NAS信令消息時,NAS安全秘鑰從K-ASME中衍生,用於NAS消息的安全傳送。過程包含Security Mode Command 和Security Mode Complete消息的來回,並由MME傳送Security Mode Command 消息給UE是開始。 3. MME選擇使用一個**NAS安全算法(Alg-ID)**,從K-ASME來產生K-NASinc和K-NASenc 4. MME把K-NASinc算法用於Security Mode Command消息產生**NAS-MAC(Message Authentication Code for NAS for Integrity)** 5. MME傳輸包含選擇的NAS安全算法和NAS-MAC的Security Mode Command消息給UE。因為UE並不知道選擇的加密算法,所以這個消息是完整性保護的,但是沒有加密 6. UE一旦接收到了Security Mode Command消息,使用MME選擇的NAS完整性算法來驗證完整性,並使用NAS完整性/加密算法從K-ASME中產生NAS安全秘鑰(K-NASinc,K-NASenc) 7. UE使用K-NASenc加密Security Command Complete消息,並使用K-NASinc生成消息鑑權碼NAS-MAC用於加密的消息。**現在UE可以傳輸包含NAS-MAC的加密和完整性保護的消息到MME了** 8. 一旦NAS安全建立起來,在UE和MME之間的NAS信令都是通過NAS安全秘鑰加密和完整性保護的,在無線鏈路上安全的傳輸 ## <font color="FF0000">AS Security</font> AS security is used to ensure the security of data transmission between the UE and eNB on the wireless link - **On control side:** Integrity check and encryption are performed on the RRC signaling message - **On user side:** Only encryption is performed for IP data packet ### <font color="0000ff">**Note:**</font> - Integrity protection is required, and encryption is an optional - **K-RRCint and K-RRCenc** are Used for the integrity check and encryption of **control plane data** - **K-UPenc** is used for the encryption of **user plane data** - Integrity checking and encryption are performed at the **PDCP layer** ### <font color="0000ff">**Process:**</font> 1. NAS安全建立完成之後,在UE和eNB之間AS安全建立過程開始。 2. 當傳輸RRC信令消息和IP數據包時,使用從K-eNB產生的AS安全秘鑰用於這些數據的安全傳輸。這個過程包括RRC信令消息的一個來回(Security Mode Command 和Security Mode Complete 消息),並且這個過程在eNB傳輸Security Mode Command消息給UE時開始。 3. MME從K-ASME中計算出K-eNB並傳輸給eNB,eNB使用K-eNB來執行AS安全過程。 4. eNB選擇AS安全算法(Alg-ID:算法ID)並使用這個算法ID從K-eNB中計算出完整性秘鑰(K-RRCinc)和加密秘鑰(K-RRCenc)用於RRC信令消息,計算出加密秘鑰(K-UPenc)用於用戶面 5. eNB應用K-RRCint到Security Mode Command消息產生一個消息鑑權碼(MAC-I,Message Authentication Code for Integrity)。 6. eNB開始傳輸包含選擇的AS安全算法和MAC-I的Security Mode Command消息到UE。 7. UE一旦從eNB接收到Security Mode Command消息,使用eNB選擇的AS完整性算法驗證完整性,並使用AS完整性/加密算法來計算出AS加密秘鑰(K-RRCint, K-RRCenc and K-UPenc ) 8. 接著使用RRC完整性秘鑰產生一個消息鑑權碼MAC-I給Security Mode Complete 消息,接著轉發包含MAC-I的這條消息給eNB 9. 當eNB使用AS安全秘鑰成功的驗證了接收到的Security Mode Complete 消息的完整性,AS安全建立過程完成的 10. 在AS安全建立之後,UE和eNB之間的RRC信令消息都是使用AS安全秘鑰加密的和完整性保護的,在空中鏈路上傳輸的用戶IP數據包是加密的。 ## <font color="ff0000">LTE Authentication Procedure</font> ![](https://i.imgur.com/xVi2HzP.jpg) ### 1. <font color="0000ff">**[UE -> MME] UE requests authentication to the network:**</font> UE first attach to network, sends an Attach Request message including: - **IMSI** - **KSIA-SME = 7:** indicates that the UE does not have a security key. - **UE network capability:** The security algorithm available to the UE (說明UE具備連線到何種EPS的能力及支持的NAS,AS演算法) ### 2. <font color="0000ff">**[MME -> HSS] MME requests authentication data from HSS:**</font> MME recognizes that there is no K-ASME available,sending an Authentication Information Request message to the HSS which including: - **IMSI** - **SN ID(Serving Network ID)**: Refers to the network user accesses, composed of PLMN - **n (number of AV):** the number of AV requested by the MME - **Network Type:** The type of UE access to the network (here E-UTRAN) ### 3. <font color="0000ff">**[MME <- HSS] HSS responds to requests for authentication data:**</font> 1. The HSS generates the required AV at the request of the MME, and then sends an Authentication Information Answer (AVs) message to the MME. 2. MME selects one to use in the UE's LTE authentication 3. MME allocates KSI-ASME (the index of K-ASME) instead of K-ASME to transmit to the UE for security ### 4. <font color="0000ff">**[UE <- MME] MME requests user authentication:**</font> ### 5. <font color="0000ff">**[UE -> MME] The UE responds to the authentication of the user:**</font>

    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