Home | Reports | Technical Documents | Tech-Blog | One-Shot Gallery | Korea ICT News | Korea Communication Market Data | List of Contributors | Become a Contributor |    
 
 
Section 5G 4G LTE C-RAN/Fronthaul Gigabit Internet IPTV/Video Streaming IoT SDN/NFV Wi-Fi KT SK Telecom LG U+ Network Protocol Samsung   Korean Vendors
 
Private 5G | Edge Netmanias Private 5G Analysis KT SK Telecom Verizon AT&T Vodafone DT Telefonica China Mobile Optage NEC Fujitsu Microsoft AWS    
    HFR Ericsson Nokia Huawei Samsung Mavenir Affirmed Metaswitch Athonet Altiostar Airspan Kyocera Apresia    
CHANNELS     HFR Private 5G Solution (my5G)       my5G Solution Components       my5G Key Features        my5G Resources          
SMEC's LTE Femto Gateway with X2 Broker - Facilitating instant mass deployment of LTE femtocells in existing LTE infrastructure
March 14, 2016 | By Y.C. Lee (www.esmec.com), Dr. Harrison Jangwoo Son (tech@netmanias.com)
Online viewer:
Comments (5)
9
박수빈 2016-03-18 15:12:40

좋은 자료 감사합니다.

 

Salvador (Sistelbanda) via LinkedIn 2016-04-04 17:27:44

I have one question, which is the difference between the X2 Broker and the standard X2-GW defined by 3GPP Rel12?

손장우 2016-04-09 17:45:10

About your question on the difference between X2 broker and X2-GW, please see "[Contribution] SMEC X2 Broker vs. X2GW" written by the white paper author.

Salvador (Sistelbanda) via LinkedIn 2016-04-18 16:39:14

I prefer the standardised X2GW. The Broker version has to be able to decode all X2 messages in order to send them to the target. New messages implies a Broker update while it is transparent for the X2GW. Also when a HeNB is disconnected, all its peers receive a notification via X2GW. The Broker don't have this functionality.

SMEC 2016-04-18 16:39:42

As you mentioned, in technical aspect "standard X2GW feature (Rel.12)" can provide more efficient way to process/transmit X2 messages between macro and home eNB. 
But in practical aspect, most of major macro vendors and HeNB vendors do not have clear roadmap of development for X2-C interface (X2GW interworking).
Furthermore, they don't have detailed migration/upgrade plan for existing, already deployed, Rel 9/10/11 macro/HeNBs in commercial networks. 
As a practical approach, we would like to suggest mobile operators deploy flexible HeNB GW which supports X2 service broker (for Rel 8~11 MeNB/HeNB) and X2GW (for Rel 12 and above) feature in a single system, to interwork with MeNB/HeNBs from multiple vendors with various release versions. 

Thank you for visiting Netmanias! Please leave your comment if you have a question or suggestion.
View All (229)
4G (1) 5G (18) Autonomous Driving (1) Backhaul (1) C-RAN/Fronthaul (13) CDN (1) CPRI (1) CoMP (1) Data Center (1) FTTH (3) Femto Gateway (1) Frequency (1) Gigabit Internet (12) Google (1) HeNB-GW (1) IPTV (10) Immersive Service (1) IoST (1) IoT (10) KT (21) Korea (4) Korea ICT Market (11) Korea ICT Service (2) LAA (1) LG U+ (15) LPWA (1) LTE (23) LTE-A (5) LTE-U (1) LWA (1) LoRa (1) MEC (1) MPTCP (2) MWC 2015 (1) Netflix (1) OTT (1) SD-WAN (2) SDN/NFV (12) SK Telecom (26) Samsung (4) Transparent Cache (1) UHD (2) Video Streaming (1) Wi-Fi (7) Wideband LTE (1) YouTube (1) vCPE (1)
Password confirmation
Please enter your registered comment password.
Password