eNodeB

<h2 id="differences-between-an-evolved-node-b-and-a-node-b">Differences between an evolved Node B and a Node B</h2>
<h3>Air interface</h3>
<p>eNB uses the E-UTRA protocols <a href="/facts/OFDMA/S4DNTNUs">OFDMA</a> (downlink) and <a href="/facts/SC-FDMA/wxUCt6XX">SC-FDMA</a> (uplink) on its LTE-Uu interface. By contrast, NodeB uses the <a href="/facts/UTRA/lhy2RrMw">UTRA</a> protocols <a href="/facts/WCDMA/lhy2RrMw">WCDMA</a> or <a href="/facts/TD-SCDMA/lhy2RrMw">TD-SCDMA</a> on its <a href="/facts/Uu_interface/lhy2RrMw">Uu interface</a>.
</p>
<h3>Control functionality</h3>
<p>eNB embeds its own control functionality, rather than using a RNC (Radio Network Controller) as does a Node B.
</p>
<h3>Network interfaces</h3>
<p>eNB interfaces with the <a href="/facts/System_Architecture_Evolution/8sAINAK6">System Architecture Evolution</a> (SAE) core (also known as <a href="/facts/Evolved_Packet_Core/8sAINAK6">Evolved Packet Core</a> (EPC)) and other eNB as follows:<a class="footnote-ref" id="fnref:1" href="#fn:1"><sup>1</sup></a>
</p>
<ul><li>eNB uses the S1-AP protocol on the S1-MME interface with the <a href="/facts/Mobility_Management_Entity/8sAINAK6">Mobility Management Entity</a> (MME) for control plane traffic.</li></ul>

<h2 id="references">References</h2>

eNodeB open-in-new

eNodeB