Scribd Logo
Upload

Welcome to Scribd!

  • 20 views

    System Architecture Evolution Evolved Packet Core: Serving Gateway

    Uploaded by

    Bijaya Rana
    The document discusses the network interfaces used by eNBs (evolved Node Bs) in connecting to the Evolved Packet Core. Specifically, it notes that eNBs use the S1-AP protocol over the S1-MME interface to the Mobility Management Entity for control plane traffic, the GTP-U protocol over the S1-U interface to the Serving Gateway for user plane traffic, and the X2-AP protocol over the X2 interface to connect with other eNBs.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd

    System Architecture Evolution Evolved Packet Core: Serving Gateway

    Uploaded by

    Bijaya Rana
    20 views1 page
    The document discusses the network interfaces used by eNBs (evolved Node Bs) in connecting to the Evolved Packet Core. Specifically, it notes that eNBs use the S1-AP protocol over the S1-MME interface to the Mobility Management Entity for control plane traffic, the GTP-U protocol over the S1-U interface to the Serving Gateway for user plane traffic, and the X2-AP protocol over the X2 interface to connect with other eNBs.

    Original Description:

    interface

    Original Title

    Network Interfaces

    Copyright

    © © All Rights Reserved

    Available Formats

    DOCX, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    The document discusses the network interfaces used by eNBs (evolved Node Bs) in connecting to the Evolved Packet Core. Specifically, it notes that eNBs use the S1-AP protocol over the S1-MME interface to the Mobility Management Entity for control plane traffic, the GTP-U protocol over the S1-U interface to the Serving Gateway for user plane traffic, and the X2-AP protocol over the X2 interface to connect with other eNBs.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd
    Download as docx, pdf, or txt
    20 views1 page

    System Architecture Evolution Evolved Packet Core: Serving Gateway

    Uploaded by

    Bijaya Rana
    The document discusses the network interfaces used by eNBs (evolved Node Bs) in connecting to the Evolved Packet Core. Specifically, it notes that eNBs use the S1-AP protocol over the S1-MME interface to the Mobility Management Entity for control plane traffic, the GTP-U protocol over the S1-U interface to the Serving Gateway for user plane traffic, and the X2-AP protocol over the X2 interface to connect with other eNBs.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd
    Download as docx, pdf, or txt
    You are on page 1of 1

    Network Interfaces[edit]

    eNB interfaces with the System Architecture


    Evolution (SAE) core (also known as Evolved Packet
    Core (EPC)) and other eNB as follows:[1]
    eNB uses the S1-AP protocol on the S1-MME
    interface with the Mobility Management Entity (MME)
    for control plane traffic.
    eNB uses the GTP-U protocol on the S1-U interface
    with the Serving Gateway (S-GW) for user plane
    traffic.
    Collectively the S1-MME and S1-U interfaces are
    known as the S1 interface, which represents the
    interface from eNB to the EPC.
    eNB uses the X2-AP protocol on the X2 interface with
    other eNB elements.
    References[edit]
    1. Jump up^

    You might also like