No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search


To have a better experience, please upgrade your IE browser.


NE20E-S2 V800R010C10SPC500 Configuration Guide - System Management 01

This is NE20E-S2 V800R010C10SPC500 Configuration Guide - System Management
Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Overview of Atom GNSS

Overview of Atom GNSS


As the commercialization of LTE-TDD and LTE-A accelerates, there is a growing need for time synchronization on base stations. Traditionally, the GNSS (GPS/GLONASS/Beidou) and PTP solutions were used on base stations to implement time synchronization.

The GNSS solution requires GNSS antenna to be deployed on each base station, leading to high TCO. The PTP solution requires 1588v2 support on network-wide devices, resulting in huge costs on network reconstruction for network carriers.

Furthermore, GNSS antenna can properly receive data from GNSS satellites only when they are placed outdoor and meet installation angle requirements. When it comes to indoor deployment, long feeders are in place to penetrate walls, and site selection requires heavy consideration due to high-demanding lightning protection. These disadvantages lead to high TCO and make GNSS antenna deployment challenging on indoor devices. Another weakness is that most indoor equipment rooms are leased, which places strict requirements for coaxial cables penetrating walls and complex application procedure. For example, taking security factors into consideration, the laws and regulations in Japan specify that radio frequency (RF) cables are not allowed to be deployed in rooms by penetrating walls.

To address the preceding challenges, the Atom GNSS timing system is introduced to NE20Es. Specifically, an Atom GNSS module which is comparable to a lightweight BITS device is inserted to an NE20E to provide GNSS access to the bearer network. Upon receipt of GNSS clock signals, the Atom GNSS module converts them into SyncE signals and then sends the SyncE signals to NE20Es. Upon receipt of GNSS time signals, the Atom GNSS module converts them into 1588v2 signals and then sends the 1588v2 signals to base stations. This mechanism greatly reduces the TCO for carriers.

Supported Interface Type

An Atom GNSS module supports only GE optical interfaces and the 1000M full duplex mode. It does not support the adaptive mode.

Supported PTP Device Type

The PTP device type supported by an Atom GNSS module can be boundary clock (BC) or telecom boundary clock(T-BC). A BC or T-BC has multiple clock interfaces. On a BC/T-BC, one interface is used to implement time synchronization with upstream devices, and other interfaces (passive interfaces excluded) are used to transmit time information to downstream devices.

Supported Delay Measurement Mechanism

By default, an Atom GNSS module supports the delay request-response mechanism, which is the PTP link delay measurement mechanism. Configuring this mechanism is not supported.

Supported Packet Encapsulation Mode

The PTP packets sent and received by an Atom GNSS module are encapsulated in Layer 2 multicast mode. Therefore, the PTP packet encapsulation type of NE20E interfaces must be configured as Layer 2 multicast for proper interconnection with an Atom GNSS module.

Updated: 2019-01-02

Document ID: EDOC1100055400

Views: 20439

Downloads: 30

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Previous Next