Professional Documents
Culture Documents
www.huawei.com
What Is RAN?
Background of IP RAN
IP RAN Solution
BSC
BTS RAN
NodeB/eNB RNC/MME/SGW
The radio access network (RAN), also called the backhaul network, refers to the
transmission network between the base stations (BTS/NodeB/eNodeB) and base
station controllers (BSC/RNC/MME/SGW).
As 3G and LTE
services such as
To meet the multimedia services
development of develop, the demand
Ethernet services, for high bandwidth
MSTP networks rapidly grows.
are widely Traditional SDH Because ATM
At the early deployed to bear networks cannot networks are
stage, SDH Ethernet and TDM meet the high complex in
networks are services. bandwidth deployment,
used to bear 2G requirements of 3G operation, and
pure voice services and ATM maintenance, IP
services and the networks are packet switched
TDM bandwidth therefore networks (PSNs)
usage is low. introduced. become the
mainstream bearer
networks.
What Is RAN?
Background of IP RAN
IP RAN Solution
IP Network
Because an IP An IP network
network is a provides only best-
connectionless effort packet
network, expanding an forwarding. It does not
IP network is provide OAM or QoS
convenient and mechanisms to ensure
inexpensive. link quality.
IP RAN Solution
The IP RAN solution realizes IP connectivity
between base stations and base station
controllers, applies to multiple types of
transmission media, provides OAM and QoS
mechanisms, and meets the radio backhaul
requirements.
What Is RAN?
Background of IP RAN
IP RAN Solution
If the clock and time are not synchronized between base stations, calls
may be abnormally dropped during base station handovers, resulting in
the one-way audio phenomenon. If the time and clock are not correctly
synchronized between two base stations, the call quality deteriorates.
??
Clock2
Have a date?
Clock1
Data
Video
Voice
What Is RAN?
Background of IP RAN
IP RAN Solution
RSG BSC
BTS ATN AGG
CSG
ATN
NodeB RNC
The "last mile" The access layer The aggregation layer formed The base station
meets the formed by CSGs by ASGs and RSGs uses the controllers direct
requirements for uses the ring or chain ring or chain topology and service traffic from
deploying 2G, topology and aggregates traffic from the base stations to the
3G, and LTE provides access for access layer. network aggregation
base stations at TDM, ATM, and layer.
the same site. Ethernet services.
1588v2
Key Requirements II synchronous Ethernet
Clock Synchronization 1588ACR
IP clock
Traffic classifier
Key Requirements III Traffic policy
QoS Traffic shaping
Congestion Management and Avoidance
EFM
802.1ag
Key Requirements IV BFD
Y.1731
OAM Mechanism MPLS OAM
NQA
MPLS TP OAM
Why VPN ?
The base station side does not care about the internal structure
of the network and only needs the network side to provide
transmission pipelines.
The network side wants to provide transmission pipelines to the
base station side without exposing its internal structure.
As services are diversified, the bearer network must be
compatible with multiple types of transmission media and
provides specific transport networks for specific types of
services.
Native In this solution, IP forwarding is used at the access side and efficient Native IP + L3VPN
IP+L3VPN L3VPN encapsulation is used at the aggregation side. The network has
excellent fault isolation capability and large-scale dynamic networking
capability.
RSG BSC
BTS ATN AGG M-
1
E1 ST
CSG
STM-1
ATM ATN
NodeB ATM RNC
GE
Eth.
ATN AGG RSG
NodeB/eNodeB
IP RNC/S-GW/MME
2G TDM PW 2G TDM PW
3G ATM PW 3G ATM PW
E2E L3VPN
RSG BSC
BTS ATN AGG M-
1
E1 ST
CSG
STM-1
ATM ATN
NodeB ATM RNC
GE
Eth.
ATN AGG RSG
NodeB/eNodeB
IP RNC/S-GW/MME
2G TDM PW 2G TDM PW
3G ATM PW 3G ATM PW
RSG BSC
BTS ATN AGG M -1
E1 ST
CSG
STM-1
ATM ATN
NodeB ATM RNC
GE
Eth.
ATN AGG RSG
NodeB/eNodeB
IP RNC/S-GW/MME
2G TDM PW 2G TDM PW
3G ATM PW 3G ATM PW
RSG BSC
BTS ATN AGG M-
1
E1 ST
CSG
STM-1
ATM ATN
NodeB ATM RNC
GE
Eth.
ATN AGG RSG
NodeB/eNodeB
IP RNC/S-GW/MME
2G TDM PW 2G TDM PW
Access Tunnel
3G ATM PW 3G ATM PW
Huawei's IP RAN QoS solution uses DiffServ and HQoS meet the QoS requirements of different types
of traffic by implementing traffic classification, priority mapping, and traffic scheduling. In this manner,
network service quality is ensured.
Voice service: has low requirements for bandwidth, but high requirements
for delay, jitter, and packet loss ratio.
During traffic classification, voice service packets can be mapped to EF or
AF queues.
Data service: has high requirements for bandwidth, but low requirements for
delay, jitter, and packet loss ratio.
During traffic classification, data service packets can be mapped to BE
queues.
Video service: has high requirements for bandwidth, delay, jitter, and packet
loss ratio.
During traffic classification, video service packets can be mapped to EF or
AF queues.
CS7 … CS7
…
Video CS6 … 5 5 5 5 … CS6
Video
EF … … EF
Voice AF4 … 4 4 4 4 … AF4 Voice
AF3 … AF3
…
AF2 AF2
… …
Data AF1 … AF1 Data
BE 3 3 3 3 …
BE
… …
EFM/BFD EFM/BFD
Link layer
MPLS OAM/MPLS TP OAM/BFD
PW layer
802.1ag/Y.1731/BFD
Service
layer
NQA
IP layer
There is no perfect OAM mechanism, only the most appropriate OAM mechanism. A
flexible OAM mechanism provides E2E link quality guarantee.