Académique Documents
Professionnel Documents
Culture Documents
System Description
SNMTC-v3-0312
This manual should be read and used as a guideline for properly installing and/or operating the
product. Owing to product variations across the range, any illustrations and photographs used in
this manual may not be a wholly accurate depiction of the actual products you are using.
This manual may be changed for system improvement, standardization and other technical
reasons without prior notice.
Samsung Networks documentation is available at http://www.samsungdocs.com
Contents
Preface v
Conventions in this Document ......................................................................................................... v
New and Changed Information ....................................................................................................... vi
Revision History ............................................................................................................................... vi
Organization of This Document ...................................................................................................... vi
Equipment Markings ...................................................................................................................... vii
Chapter 1 Samsung LTE System Overview 1
Introduction to Samsung LTE System ............................................................................................... 1
Samsung LTE Network Configuration ............................................................................................... 5
Protocol Stack between NEs ............................................................................................................ 8
Chapter 2 SOT50 Overview 12
Introduction to SOT50 .................................................................................................................... 12
Key Features ................................................................................................................................... 13
Physical Layer Processing .......................................................................................................... 13
Call Processing Function ............................................................................................................ 17
IP Processing .............................................................................................................................. 19
SON Function ............................................................................................................................. 19
Easy Operation and Maintenance ............................................................................................. 21
Specification ................................................................................................................................... 24
Chapter 3 SOT50 Structure 26
Hardware Structure ........................................................................................................................ 26
L7UA .......................................................................................................................................... 26
PA and Filter .............................................................................................................................. 28
Antenna ..................................................................................................................................... 28
External Interface ...................................................................................................................... 28
Software Structure ......................................................................................................................... 32
Basic Software Structure............................................................................................................ 32
CPS Block.................................................................................................................................... 35
OAM Blocks ................................................................................................................................ 38
Chapter 4 Message Flow 42
Data Traffic Flow ............................................................................................................................ 42
Network Sync Flow ......................................................................................................................... 43
Alarm Signal Flow ........................................................................................................................... 44
Loading Flow .................................................................................................................................. 45
Operation and Maintenance Message Flow .................................................................................. 46
Web-EMT ................................................................................................................................... 47
CLI .............................................................................................................................................. 47
Appendix Acronyms 49
This description describes the characteristics, features and structure of the SOT50.
Symbols
Symbol Description
Indicates a task.
Indicates a shortcut or an alternative method.
Provides additional information.
Menu Commands
menu | command
This indicates that you must select a command on a menu, where menu is the
name of the menu, and command is the name of the command on that menu.
Revision History
The following table lists all versions of this document.
Document Product/Software Document Publication Date Remarks
Number Version Version
2600-00I2D3GA2 SOT50 1.0 2 September 2015 -
2600-00I2D3GA2 SOT50 2.0 4 November 2015 -
2600-00I2D3GA2 SOT50 3.0 3 February 2016 -
Equipment Markings
This marking on the product, accessories or literature indicates that the
product and its electronic accessories (e.g. charger, headset, USB cable)
should not be disposed of with other household waste at the end of their
working life. To prevent possible harm to the environment or human health
from uncontrolled waste disposal, please separate these items from other
types of waste and recycle them responsibly to promote the sustainable
reuse of material resources.
For more information on safe disposal and recycling, visit our website
www.samsung.com/in or contact our Helpline numbers-18002668282,
180030008282.
Samsung LTE system is based on the Rel-8 and Rel-9 standards of the LTE 3rd
Generation Partnership Project (3GPP).
Samsung LTE system consists of evolved UTRAN Node B (eNB), Evolved Packet
Core (EPC) and LTE System Manager (LSM).
The eNB exists between EPC and User Equipment (UE). It establishes wireless
connections with UE and processes packet calls according to LTE air interface
standard. The eNB manages UE in connected mode at the Access Stratum (AS)
level. The EPC is the system, which is located between eNB and Packet Data
Network (PDN) to perform various control functions. The EPC consists of
Mobility Management Entity (MME), Serving Gateway (S-GW), and PDN
Gateway (P-GW). The MME manages UE in idle mode at the Non-Access Stratum
(NAS) level. Also S-GW and P-GW manages user data at the NAS level and
interworks with other networks.
The LSM provides man-machine interface; manages the software, configuration,
performance, and failures. Also, it acts as a Self-Organizing Network (SON)
server.
The following figure shows the functional distinctions between eNB of E-UTRAN,
MME, S-GW, and P-GW according to the 3GPP standard. The eNB has a layer
structure and EPC has no layer.
eNB
Inter Cell RRM
RB Control
Connection Mobility Cont.
Radio Admission Control
MME
eNB Measurement
Configuration & Provision NAS Security
PDCP
RLC S-GW P-GW
S1
MAC UE IP address allocation
Mobility Anchoring
PHY Packet Filtering
E-UTRAN EPC
eNB
The eNB is a logical network component of Evolved UTRAN (E-UTRAN), which
is located on access side in the LTE system.
The eNBs can be interconnected with each other by X2 interface. The eNBs are
connected by S1 interface to the Evolved Packet Core (EPC).
The wireless protocol layer of eNB is divided into layer 2 and layer 3. The layer 2
is subdivided into Media Access Control (MAC) layer, Radio Link Control (RLC)
layer, and PDCP layer, each of which performs independent functions. Also,
layer3 has Radio Resource Control (RRC) layer.
The MAC layer distributes air resources to each bearer according to its priority.
Also, it performs multiplexing function and HARQ function for the data, which is
received from the multiple upper logical channels.
The RLC layer performs the following functions:
Segments and reassembles the data, which is received from PDCP layer under
the size specified by MAC layer
Requests retransmission to recover if data transmission fails in the lower layer
(ARQ)
Reorders the data recovered by performing HARQ in MAC layer (re-ordering)
The PDCP layer performs the following functions:
MME
The MME interworks with E-UTRAN (eNB) to process the Stream Control
Transmission Protocol (SCTP)-based S1 Application Protocol (S1-AP) signalling
messages for controlling call connections between MME and eNB. Also, MME
process the SCTP-based NAS signalling messages for controlling mobility
connection and call connection between UE and EPC.
The MME is responsible for collecting/modifying the user information and
authenticating the user by interworking with HSS. It is also responsible for
requesting the allocation/release/change of the bearer path for data routing and
retransmission with GTP-C protocol by interworking with S-GW.
The MME interworks with 2G and 3G systems, Mobile Switching Center (MSC),
and Serving GPRS Support Node (SGSN) for providing mobility and Handover
(HO), Circuit Service (CS) fallback, and Short Message Service (SMS).
The MME is responsible for inter-eNB mobility, idle mode UE reachability,
Tracking Area (TA) list management, choosing P-GW/S-GW, authentication, and
bearer management.
The MME supports mobility during inter-eNB handover and the inter-MME
handover. It also supports SGSN selection function upon handover to 2G or 3G
3GPP network.
S-GW
The S-GW acts as the mobility anchor during inter-eNB handover and inter-3GPP
handover, and routes and forwards user data packets. The S-GW allows the
operator to apply application-specific charging policies to UE, PDN or QCI and
manages the packet transmission layers for uplink/downlink data.
The S-GW also supports GPRS Tunnelling Protocol (GTP) and Proxy Mobile IP
(PMIP) by interworking with MME, P-GW, and SGSN.
PDN
Gy
EPC OCS
Gz Gx
PCRF
OFCS Sp
P-GW S10
Gz
EMS
S-GW MME
CSM
S1-U S1-MME
SNMP/FTP/UDP X2-C
EMS
X2-U
LSM
eNB
RMI Uu
MSS
UE UE
eNB
The eNB is located between UE and EPC. It processes packet calls by connecting
to UE wirelessly according to the LTE air standard. The eNB is responsible for
transmission and receipt of wireless signals, modulation and demodulation of
packet traffic signals, packet scheduling for efficient utilization of wireless
resources, Hybrid Automatic Repeat Request (HARQ)/ARQ processing, Packet
Data Convergence Protocol (PDCP) for packet header compression, and wireless
resources control.
In addition, eNB performs handover by interworking with the EPC.
EPC
The EPC is a system, which is located between the eNB and PDN. The
subcomponents of the EPC are the MME, S-GW and P-GW.
MME: Processes control messages using the NAS signaling protocol with the
eNB and performs control plane functions such as UE mobility management,
tracking area list management, and bearer and session management.
S-GW: Acts as the anchor for the user plane between the 2G/3G access system
and the LTE system and manages and changes the packet transmission layer
for downlink/uplink data.
P-GW: Allocates an IP address to UE, acts as the anchor for mobility between
the LTE and non-3GPP access systems, and manages/changes charging and
the transmission rate according to the service level.
NAS NAS
Relay
RRC RRC S1-AP S1-AP
RLC RLC IP IP
MAC MAC L2 L2
L1 L1 L1 L1
GTP-U GTP-U
UDP UDP
IP IP
L2 L2
L1 L1
S1-AP S1-AP
SCTP SCTP
IP IP
L2 L2
L1 L1
S1-MME
eNB MME
GTP-U GTP-U
UDP UDP
IP IP
L2 L2
L1 L1
eNB eNB
X2
X2-AP X2-AP
SCTP SCTP
IP IP
L2 L2
L1 L1
eNB eNB
X2
IP IP
L2 L2
L1 L1
Introduction to SOT50
The SOT50 is located between UE and EPC. It interfaces wirelessly in accordance
with the LTE air standard and provides subscribers with wireless communications
service. The SOT50 transmits and receives wireless signals to and from UE and
processes the modulation and demodulation of traffic signals. In addition, it
allocates packet scheduling and wireless bandwidth, and performs handover by
interfacing with the EPC.
The SOT50 is an all-in-one unit. If a fault occurs, the unit must be replaced.
Key Features
The key functions of the SOT50 (hereinafter eNB) are as follows:
Physical Layer Processing
Call Processing Function
IP Processing
SON Function
Easy Operation and Maintenance
For availability and provision schedule of the features and functions described in
the system manual, please refer to separate documentations.
OFDMA/SC-FDMA Scheme
The eNB performs the downlink OFDMA/uplink SC-FDMA channel processing
that supports the LTE standard physical layer. The downlink OFDMA scheme
allows the system to transmit data to multiple users simultaneously using the
subcarrier allocated to each user. Depending on the channel status and the
transmission rate requested by the user, the downlink OFDM can allocate one or
more subcarriers to a specific subscriber to transmit data.
In addition, when all sub-carriers are divided for multiple users, the eNB can select
and assign to each subscriber a sub-carrier with the most appropriate features using
the OFDMA scheme, thus to distribute resources efficiently and increase data
throughput.
Channel Encoding/Decoding
The eNB is responsible for channel encoding/decoding to correct the channel
errors that occurred on a wireless channel. In LTE, the turbo coding and the 1/3
tail-biting convolutional coding are used. Turbo coding is mainly used for
transmission of large data packets on downlink and uplink, while convolutional
coding is used for control information transmission and broadcast channel for
downlink and uplink.
Modulation/Demodulation
For the data received over the downlink from the upper layer, the eNB processes it
through the baseband of the physical layer and then transmits it via a wireless
channel. At this time, to transmit a baseband signal as far as it can go via the
wireless channel, the system modulates and transmits it on a specific high
frequency bandwidth.
For the data received over the uplink from UE through a wireless channel, the eNB
demodulates and changes it to the baseband signal to perform decoding.
Link Adaptation
The wireless channel environment can become faster or slower, better or worse
depending on various factors. The system is capable of increasing the transmission
rate or maximizing the total cell throughput in response to the changes in the
channel environment, and this is called link adaptation.
In particular, the Modulation and Coding Scheme (MCS) is used for changing the
modulation method and channel coding rate according to the channel status. If the
channel environment is good, the MCS increases the number of transmission bits
per symbol using a high-order modulation, such as 64 QAM. If the channel
environment is bad, it uses a low-order modulation, such as QPSK and a low
coding rate to minimize channel errors.
In addition, in the environment where MIMO mode can be used, the eNB operates
in MIMO mode to increase the peak data rate of subscribers and can greatly
increase the cell throughput.
If the channel information obtained is incorrect or modulation method of higher
order or higher coding rate than the given channel environment is used, errors may
occur.
In such cases, the errors can be corrected by the HARD function.
H-ARQ
The H-ARQ is a retransmission method in the physical layer, which uses the stop-
and-wait protocol. The eNB provides the H-ARQ function to retransmit or
combine frames in the physical layer so that the effects of wireless channel
environment changes or interference signal level changes can be minimized, which
results in throughput improvement.
The LTE uses the Incremental Redundancy (IR)-based H-ARQ method and
regards the Chase Combining (CC) method as a special case of the IR method.
The eNB uses the asynchronous method for downlink and the synchronous method
for uplink.
Power Control
When transmitting a specific data rate, too high a power level may result in
unnecessary interferences and too low a power level may result in an increased
error rate, causing retransmission or delay. Unlike in other schemes such as
CDMA, the power control is relatively less important in LTE. Nevertheless,
adequate power control can improve performance of the LTE system.
Therefore, UE should use adequate power levels for data transmission in order not
to interfere with nearby cells. Likewise, the power level for each UE could be
controlled for reducing the inter-cell interference level.
In the LTE downlink, the eNB can reduce inter-cell interference by transmitting
data at adequate power levels according to the location of UE and the MCS, which
results in improvement of the entire cell throughput.
MIMO
The eNB can support the MIMO by using multiple antennas. For this purpose, the
channel card of the eNB has the baseband part to process the MIMO, and
individual RF paths can be processed separately. The eNB supports various types
of the MIMO to provide the high-performance data service.
The eNB uses multiple antennas to support the MIMO. MIMO has the following
schemes.
Direction Item Description
Downlink Space Frequency Block This scheme implements the space-time block coding (STBC) on
Coding (SFBC) frequency instead of on time for increased reliability of the link. The
Alamouti codes are used.
Handover
The eNB supports intra-frequency or inter-frequency handover between intra-eNB
cells, X2 handover between eNBs, and S1 handover between eNBs. It also
processes signaling and bearer for handover. At intra-eNB handover, handover-
related messages are transmitted via internal eNB interfaces; at X2 handover, via
the X2 interface; at S1 handover, via the S1 interface.
To minimize user traffic loss during X2 and S1 handovers, the eNB performs the
data forwarding function. The source eNB provides two forwarding methods to the
target eNB: direct forwarding via the X2 interface and indirect forwarding via the
S1 interface.
The eNB allows the UE to receive traffic without loss through the data forwarding
method at handover.
RLC ARQ
The eNB performs the ARQ function for the RLC Acknowledged Mode (AM)
only.
When receiving and transmitting packet data, the RLC transmits the SDU by
dividing it into units of RLC PDU at the transmitting side and the packet is
retransmitted (forwarded) according to the ARQ feedback information received
from the receiving side for increased reliability of the data communication.
QoS Support
The eNB receives the QoS Class Identifier (QCI) in which the QoS characteristics
of the bearer are defined and the GBR, the MBR, and the Aggregated Maximum
Bit Rate (UE-AMBR) from the EPC. It provides the QoS for the wireless section
between the UE and the eNB and the backhaul section between the eNB and the S-
GW.
Via the air interface, it performs retransmission to satisfy the rate control
according to the GBR/MBR/UE-AMBR values, priority of bearer defined in the
QCI, and scheduling considering packet delay budget, and the Packet Loss Error
Rate (PLER).
Via the backhaul interface, it performs QCI-based packet classification, QCI to
DSCP mapping, and marking for the QoS. It provides queuing depending on
mapping results, and each queue transmits packets to the EPC according to a strict
priority, and so on.
In the Element Management System (EMS), in addition to the QCI predefined in
the specifications, operator-specific QCI and QCI-to-DSCP mapping can be set.
IP Processing
IP QoS
The eNB can provide the backhaul QoS when communicating with the EPC by
supporting Differentiated Services (DiffServ).
The eNB supports eight DiffServ classes and mapping between the services classes
of the user traffic received from the UE and DiffServ service classes. In addition,
the eNB supports mapping between the Differentiated Services Code Points
(DSCP) and the 802.3 Ethernet MAC service classes.
IP Routing
Because the eNB provides multiple Ethernet interfaces, it stores in the routing
table the information on which Ethernet interface the IP packets will be routed to.
The routing table of the eNB is configured by the operator. The method for
configuring the routing table is similar to the standard router configuration method.
The eNB supports static routing setup, but it does not support dynamic routing
protocols, such as Open Shortest Path First (OSPF)/Border Gateway Protocol
(BGP).
IP Multicast Routing
The eNB provides multiple Ethernet interfaces and it stores information on which
Ethernet interface IP packets will be routed to in the routing table.
The routing table of eNB is configured by the operator in the similar way to the
router standard configuration. IP multicast is based on PIM and IGMPv2 SSM.
Ethernet/VLAN Interface
The eNB provides an Ethernet interface. For the Ethernet interface, it supports the
static link grouping, Virtual Local Area Network (VLAN) function, and Ethernet
Class of Service (CoS) function in accordance with IEEE 802.3ad. The MAC
bridge function defined in IEEE 802.1D is not supported.
The eNB allows multiple VLAN IDs to be set for an Ethernet interface. To support
Ethernet CoS, it maps the DSCP value of the IP header to the CoS value of the
Ethernet header on the Tx packet.
SON Function
The SON function supports the self-configuration, self-establishment and self-
optimization function.
Self-Optimization
PCI Auto-configuration
Samsung PCI optimization provides functions such as auto PCI configuration for
initial PCI allocation during network installation, PCI collision, confusion
detection and auto PCI optimization for PCI reallocation.
Automatic Neighbor Relation (ANR)
Samsung ANR configures and manages the intra-LTE NRT to guarantee stable UE
mobility in the LTE system. Samsung ANR fully meets the requirements of the
3GPP LTE standard. At the self-configuration phase, it provides the initial NRT
auto-configuration function based on the location information of active cells
during the eNB or cell growing procedure. At the self-optimization phase, it
provides automatic NR addition and X2 interface establishment function triggered
by UE mobility or periodical operation, and periodical NRT management function.
Mobility Robustness Optimization (MRO)
Samsung MRO optimizes the HO performance automatically during system
operation, in order to satisfy KPI for HO success rate and to reduce Ping-Pong HO
to the extent of satisfying KPI. Samsung MRO is triggered at regular intervals, and
controls HO parameters based on the HO statistics collected during the interval.
The HO-related statistics used by Samsung MRO include all the HO-related
problems specified in 3GPP standard (Too-late HO/Too-early HO/HO to Wrong
Cell). RLF indication messages and handover report messages delivered through
X2 interface are used to collect statistics on the above problems.
Samsung MRO controls CIO, the HO parameter that changes HO time at the cell’s
level, in order to satisfy KPI on HO success rate and to reduce Ping-Pong HO; if
KPI is not satisfied, the function controls the CIO value based on the tendency of
the HO-related problems. It also monitors if the HO or call drop rate performance
sharply slows down for a certain period of time after changing the CIO value. If so,
it performs fallback action to return to the previous CIO value, maintaining
stability of HO performance.
Random Access Channel (RACH) Optimization
During self-configuration phase, EMS supports RSI (root sequence index) auto-
configuration using location information. Subsequently, during the operational
phase, each eNB collects the information pertaining to any RSI conflicts and
informs EMS about conflict information for reconfiguring. For RACH
optimization, eNB collects the statistics of the dedicated preamble allocation
attempt/success and optimizes the number of dedicated preambles. eNB also
collects the statistics of the preamble transmission during RA and optimizes the
PRACH Configuration Index and Preamble Initial Received Target Power.
Mobility Load Balancing (MLB)
The MLB function monitors the cell’s load. If the load status satisfies the MLB
execution condition specified by the operator, this function moves a part of the
traffic to a neighbor cell through network-initiated HO. The MLB execution
condition is divided into the load equalization condition among multiple carriers,
and the overload condition of a cell.
Call Trace
The eNB supports the call trace function for a specific UE.
The operator can enable trace for a specific UE through the MME. The trace
execution results such as signaling messages are transmitted to the LSM.
IEEE 802.3ah
The eNB provides the IEEE 802.3ah Ethernet OAM function for the backhaul
interface. Although the IEEE 802.3ah OAM is for the physical layer, it is located
on the MAC layer to support the entire IEEE 802.3 PHY; the 802.3ah OAM frame
is created and processed according to the functions defined in the standards.
The Ethernet OAM functions include the discovery function where the both ends
of a link discover each other to monitor the connectivity continuously and deliver
the key link events such as dying gasp; the remote loopback function; the link
monitoring function to monitor the error packets and deliver an event notification
in case of abnormal threshold; and the variable retrieval function for the 802.3ah
standard MIB.
The eNB supports the response to the 802.3ah OAM function triggered by an
external active mode entity, loopback mode operation, and the 802.3ah Ethernet
OAM passive mode such as transmission of event notification.
Specification
Key Specifications
The key specifications of the SOT50 are as follows:
Item Specification
Air Specification LTE TDD
Operating Frequency 2.3 GHz Single band (B40) (2,300~2,400 MHz)
Channel Bandwidth 20 MHz
RF Chain 2Tx/2Rx
Output Power 5 W/path
Capacity 1 Carrier/Omni
Backhaul Optic GE 1 port
Daisy chain Optic GE 1 port
Clock solution GPS, IEEE1588v2
Holdover 8 h for GPS
Cooling Convection cooling
Input Power
The following table shows the power specifications for the LTE eNB. The LTE
eNB complies with EN60950 safety standard for electrical equipment. If the
operator wants AC power for the system input voltage, it can be supplied using an
additional external rectifier (installed by the provider).
Item Specification
Input Power 230 V AC (nominal voltage)
GPSR Specifications
The following table shows the GPS Receiver (GPSR) specifications of the SOT50.
Item Specification
Received Signal from GPS GPS L1 Signal
Frequency Accuracy (ppm) 0.05
Phase Accuracy 1 us (lock state)
8 us (holdover state)
IEEE1588v2 Specifications
The IEEE1588v2 specifications for the SOT50 are as follows:
Item Specification
Standard IEEE 1588v2
Frequency Accuracy (ppm) 0.05
Phase Accuracy 10 us
FPP > 1 % for 4 us (packet delay window)/60 s (time
window)
Maximum one way delay < 250 ms
Maximum PDV < 300 us
No asymmetry
No reroute
Ambient Conditions
The following table shows the ambient conditions and related specifications of the
SOT50:
Category Specifications
Operating temperature (°C) -30~55
Operating Humidity (%) 5~100
3
Condensing, not to exceed 30 g/m absolute humidity
Earthquake Telcordia GR-63-CORE: Earthquake Zone4
Vibration Telcordia GR-63-CORE
Office Vibration
Transportation Vibration
EMC EN 301 489-1, EN 301 489-23
Hardware Structure
The SOT50 consists of the LTE 7 baseband and transceiver Unified Board
Assembly (L7UA), which is a digital processing board, AC/DC, UCCM, AMP and
a Filter block.
The internal configuration of the SOT50 is shown below.
BH_OPT
L7UA
EXT_OPT
- Main Processing Filter ANT_0
AC PWR - Clock generation & Distribution
RRH_OPT - Network Interface
- Transceiver function GPS
SYNC - Subscriber Channel processing
- DAC/ADC Function ANT_1
LED - Reset Filter
DBG
L7UA
The major functions of the L7UA are as follows:
Main Control Functions
Clock Generation and Distribution Function
Network Interface Function
Subscriber Channel Processing Function
RU Interface
DAC/ADC
In the downlink path, a baseband signal is converted into an analog signal through
the Digital-to-Analog Converter (DAC). The frequency of those analog signals is
up converted through the modulator, and then the signals are amplified into high-
power RF signals through the power amplifier.
In the uplink path, a signal low noise amplified is down converted in frequency
through the demodulator. These down-converted frequency signals are converted
into baseband signals through the Analog-to-Digital Converter (ADC). The
converted baseband signal is transmitted to the modem.
Reset
Operator can do remote reset of the SOT50 via LSM. The L7UA receives Reset
order from LSM, the power is initialized.
PA and Filter
In downlink path, RF signal amplified by PA is transmitted to the antenna after
meeting the specified spectrum mask through filter. In uplink path, RF signal
received through filter is transmitted to the L7UA.
PA
100 MHz BW Operating Frequency
Supports 20 MHz 1 Carrier Omni 2Tx2Rx
Maximum Output 5 + 5 W (based on external antenna of enclosure)
Filter
Suppresses the radiation of unnecessary frequencies outside the bandwidth
Supports 2Tx2Rx RF path
Antenna
According to RF environment, Integrated Antenna type or External Antenna type
can be installed. The antenna of the SOT50 supports 2T2R as integrated type.
The electrical specifications of the SOT50 are as follows:
Item Specifications
Frequency Range (MHz) 2300~2400
3 dB Horizontal 65˚ ± 5˚
Beam-Width Vertical 30.0˚ ± 3˚
Gain (dBi) ≥ 10
Front-to-Back Ratio (dB) ≥ 25
Polarization Type Dual, Slant ± 45˚
Input Maximum CW Power (W) 50
Impedance (Ω) 50
Return Loss (dB) ≤ -14.0
Isolation between Ports (dB) ≥ 25
External Interface
The external interface of the SOT50 is as follows:
GPS
AC_PWR
ANT_1 ANT_0
GPS
AC_PWR
LED
Status Description
Red on Board initialization
Critical alarm or backhaul link down detected
Amber Blinking (Fast) Software download state (blinking period: 200
ms)
Amber Blinking (Slow) System registration state (blinking period: 1000
ms)
Amber on Booting completion
Green On Software activation sate
Green blinking Normal operation
Red blinking (Fast) Firmware fusing state (blinking period: 200 ms)
Red blinking (Slow) Major/minor alarm is detected.
LED off No power supply
Connector
Interface Name Interface Type Description
AC_PWR Jonhon 3 pin AC bayonet type connector Power
RRH_OPT SFP LC type, Jonhon screw type PDLC Reserved
(CPRI interface port)
Software Structure
Basic Software Structure
The software of the eNB is divided into three parts: Kernel Space (OS/DD),
Forwarding Space (NPC, NP) and User Space (MW, IPRS, CPS, OAM) which are
described below.
User Space
MW
DHCP
MDS THS HAS DUS MFS ENS
OS DD NPC NP
Hardware
RFS: Stores and manages the binary files, libraries, and configuration files
necessary for running and operating the software in accordance with the File-
system Hierarchy Standard 2.2 (FHS).
Utility: Provides the functions for managing the complex programmable logic
device (CPLD), LED, watchdog, and environment and inventory information,
measuring and viewing the CPU load, and storing and managing fault
information when a processor goes down.
MAC filtering
IP Packet forwarding
IP fragmentation and reassembly
Link aggregation
VLAN termination
ACL (Access Control List)
Middleware (MW)
The MW ensures seamless communication between OS and applications on
various hardware environments. It provides a Message Delivery Service (MDS)
between applications, Debugging Utility Service (DUS), Event Notification
Service (ENS), High Availability Service (HAS) for redundancy management and
data backup, Task Handling Service (THS), Miscellaneous Function Service
(MFS).
MDS: Provides all services related to message transmitting and receiving.
DUS: Provides the function for transmitting debugging information and
command between the applications and the operator.
ENS: Adds and manages various events such as timers, and provides the
function for transmitting an event message to the destination at the time when
it is needed.
HAS: Provides the data synchronization function and the redundancy state
management function.
THS: Provides the task creation/termination function, the task control function,
and the function for providing task information, and so on.
MFS: The MFL is responsible for all hardware-dependent functions, such as
accessing physical addresses of hardware devices.
IPSS: Software that performs the security function for the IP layer. It is
responsible for filtering based on the IP address, TCP/UDP port number and
protocol type.
DHCP: Software block that performs the automatic IP address allocation
function. It is responsible for obtaining an IP address automatically by
communicating with the DHCP server.
In the following sections, the Master OAM Board and Call Processing Board,
where the software runs on, indicate the UAMA/LMA3 and L9CA of CDU each.
CPS Block
The Call Processing Software (CPS) block performs the resource management of
the LTE eNB and the call processing function in the eNB defined in the 3GPP and
performs the interface function with the EPC, UE, and neighbor eNBs. The CPS
consists of the eNB control processing subsystem (ECS) which is responsible for
network access and call control functions, and the eNB data processing subsystem
(EDS) which is responsible for user traffic handling.
In addition, depending on the eNB functions defined in 3GPP, the ECS consists of
SCTB, ECMB, ECCB, SCTB, CSAB, TrM, and EMCB; and the EDS consists of
GTPB, PDCB, RLCB and MACB.
In sequence delivery
Duplicate detection
RLC SDU discard
RLC re-establishment
Protocol error detection and recovery
OAM Blocks
The Operation Administration and Maintenance (OAM) is responsible for
operation and maintenance in the eNB.
The OAM is configured with OSAB, PM, FM, CM, SNMP, SwM, TM, Web-EMT
and CLI.
The major functions of the OAM are as follows:
Receiving Path
The RF signal received by the antenna passes through the L7FU’s filter and its low
noise is amplified by the LNA. This signal is converted to the data signal of
baseband after the RF down-conversion in the transceiver of the L7UA. The data
which passed through the SC-FDMA signaling process in the modem is converted
to the Gigabit Ethernet frame and transmitted to the EPC through GE.
EPC
UP Power Tx
Main D/A
IP GE Conversion Amp Filter
Processor TDD
Network & SW
Down Rx
Modem A/D LNA
Conversion Filter
CPU
IEEE1588 Ethernet Ethernet
Master (Server) PHY Switch
The SOT50 does not support receiving synchronization signal from GPS and IEEE
1588 Master simultaneously.
LSM
A: Reset
B: Alarm
B A
L7UA Filter
Loading Flow
Loading is the procedure through which the processor of the system can download
from the LSM the software executables, data, and other elements required to
perform its functions.
Loading the system is performed during the system initialization procedure.
Loading is also is carried out when the operator of an upper management system
restarts a board.
At the first system initialization, the system is loaded through the LSM. As the
loading information is stored in the internal storage, no unnecessary loading is
carried out afterward. After the first system initialization, it compares the software
files and versions of LSM and downloads changed software files.
The loading information contains the software image and default configuration
information file, and so on.
L7UA
LSM
L7UA
Other Blocks
SNMP message
HTTP message
(command/response)
Statistical Data
Web-EMT
The Web-EMT is a kind of GUI-based console terminal. It is the tool that monitors
the status of devices and performs operation and maintenance tasks by connecting
directly to the eNB. The operator can run the Web-EMT using Internet Explorer,
without installing separate software. The GUI is provided using the HTTPs
protocol internally.
Web-EMT
HTTP message
L7UA
HTTP Server
OAM
command/
response
Other Block
Through the Web-EMT, the operator can reset or restart the eNB or its internal
boards, view and change the configuration and operation parameter values,
monitor the system status and faults, carry out diagnostic functions, and so on. But
the resource grow and degrow functions and changing the operation information
related to neighbor list are available from the LSM only, which manages the entire
networks and the loading images.
CLI
The CLI is the method used for operation or maintenance of the eNB. Operator can
perform the text-based operation and maintenance via CLI after login to eNB via
telnet in PC.
The functions of the CLI are as follows:
Loading
The CLI can reset or restart board of the eNB.
Configuration Management
The CLI provides the function that executes the Man-to-Machine Command
(MMC) that allows viewing and changing the configuration information for eNB.
Status Management
The CLI provides the function that manages the status for the processors and
various devices of the eNB.
Fault Management
The CLI checks whether there are any faults with the processors and various
devices of the eNB and provides the operator with the location and log of each
fault. Since the CLI can display both of the hardware and software faults, the
operator can know all faults that occur in the eNB.