1 ZTE IP RAN Introduction ZTE IP RAN Introduction Name: E-mail: UMTS Product Planning & System Dept. ZTE Product R&D System Name: E-mail: UMTS Product Planning & System Dept. ZTE Product R&D System Requirement Analysis ZTE IP RAN Solution Case Study Requirement Analysis ZTE IP RAN Solution Case Study
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
1
ZTE IP RAN IntroductionZTE IP RAN Introduction
Name:
E-mail:UMTS Product Planning & System Dept.ZTE Product R&D System
Name:
E-mail:UMTS Product Planning & System Dept.ZTE Product R&D System
Requirement Analysis
ZTE IP RAN Solution
Case Study
Requirement Analysis
ZTE IP RAN Solution
Case Study
2
3
GSMGSMUMTS
R99/R4
UMTSR99/R4
HSPAR5/R6
HSPAR5/R6
HSPA+R7/R8
HSPA+R7/R8
LTER8/R9
LTER8/R9
Year
DL throughput
2001-2 2003-5 2006-8 2009-10 After 2010
64-144kbps 384kbps 14Mbps 40Mbps 100Mbps & higher
Service and Technology Trends
Non-voice service explosion
Radio technology acceleration
2G2G
3G3G
3.5G3.5G3.75G3.75G
3.9G3.9G
ARPU trend of European operatorsARPU trend of European operators
Master-standby: Two FE/GE ports, one IP/MAC address
BTS/Node B
BSC/RNC
GIPI(S)
IP: 10.1.1.1/24MAC: 00:15:EB:A1:66:0A
IP: 10.1.1.254/24MAC: 00:15:EB:00:95:DD
L2 switch
L2 switchGIPI(M)
19
37
L3 Dual Homing
BTS/Node B
BSC/RNC
GIPI
IP: 10.1.1.1/24MAC: 00:15:EB:A1:66:0A
IP: 10.1.2.1/30MAC: 00:15:EB:00:95:DD
L3 switch
L3 switch
GIPI
IP: 10.1.2.5/30MAC: 00:15:EB:00:95:D0
Load sharing: Two FE/GE ports, two IP addresses
IP: 10.1.1.2/24MAC: 00:15:EB:A1:66:1A
38
ZTE IP RAN SolutionZTE IP RAN Solution
RAN Product
Networking
Synchronization
QoS
Reliability
Security
OAM
RAN Product
Networking
Synchronization
QoS
Reliability
Security
OAM
20
39
Security for IP RAN
Security threat Unauthorized access Loss or corruption of information Broadcast storm
Security operation Access control list (ACL) for protection of network elements IPSec in case public transmission network is used for Iub/Abis VLAN tagging for network separation and broadcast suppression
40
BTS/Node B side: Lower number of BS sites in one VLAN means
higher security.
BSC/RNC side: L3 switch, instead of BSC/RNC, used for VLAN tagging
Redundancy: Multiple VLAN with different routes
VLAN Configuration Recommendation
Node BNode B
VLAN RNCRNC
Node BNode B
VLANnVLAN1
RNCRNC
……
21
41
ZTE IP RAN SolutionZTE IP RAN Solution
RAN Product
Networking
Synchronization
QoS
Reliability
Security
OAM
RAN Product
Networking
Synchronization
QoS
Reliability
Security
OAM
42
OAM for IP RAN
Link monitoring IEEE 802.3ah: Ethernet link check (P2P) IEEE 802.1ag: Ethernet link check (E2E) BFD: IP connectivity check
SLA monitoring Performance management
Ethernet performance management IP performance management
IP TransmissionIP Transmission
BTS/Node B
BSC
CN
RNC
22
43
Bidirectional Forwarding Detection
BTS/Node BBTS/Node B BSC/RNCBSC/RNC
Static route based BFDStatic route based BFD
Explicit BFDExplicit BFD
44
SLA Monitoring
IP SLA monitoring functionality Network availability monitoring IP SLA based CAC Troubleshooting
IP SLA monitoring method Continuous UDP echo Continuous ICMP echo
IP SLA monitoring initiation Instant test Performance test
CNCN
BTS/Node BBTS/Node B RNCRNC
BSCBSC UDP echoICMP echo
Depends on the subscribed bandwidth
e.g. 100Mbps
Execute the above procedure with configured frequency and packet size, calculate the data rate of received packets. Then change the frequency and packet size to get the maximum bandwidth.
Available bandwidth
Less than 0.05%Repeat the above procedure periodically, count the number of sent packets and received packets, then get the packet loss ratio.
Packet loss ratio
Less than 7msRepeat the above procedure periodically, and then get the delay jitter.Delay jitter
Less than 20ms1.RNC sends UDP packets with sequence number and timestamp to Node B.2.Node B loops back the UDP packets.3.RNC receives the looped UDP packets and calculates the round trip delay.
Delay
Expected resultTest ProcedureTest Item
23
Requirement Analysis
ZTE IP RAN Solution
Case Study
Requirement Analysis
ZTE IP RAN Solution
Case Study
46
46
BSC/RNC
Core NetworkCore Network
ZTE MSCS/MGW
HLR
ZTE VAS PlatformZTE VAS Platform
Existing VAS PlatformExisting VAS Platform
CSL NewNetwork
2G/3G OSS GSM 900/1800M
UMTS 2.1G/900M
GSM 900/1800M
GSM 1800M
UMTS 2.1G
CSLNetwork
NWMNetwork
2G OSSVAS
SGSN
MSCS
HLR
3G OSS2G OSS
CNTDM Network
SGSN
MSCS
HLR
TDM NetworkCN
Iub
Abis
IPNetwork
High Power Consumption
Difficult Evolution
Expensive Transmission
Revolution of CSL Mobile Network
24
4747
RAN Synchronization Solution
Primary clock reference: GPS
Secondary clock reference for RNC: via fiber from MGW
Secondary clock reference for iBSC: via E1 from MSCs
Indoor
Primary clock reference: IP Clock
Primary clock reference: E1 / T1
Outdoor
Primary clock reference: GPS
Secondary clock reference: IP Clock
FE
E1/T1
BTS/Node B
iBSC/RNC
48
GPS ControllerGPS Controller
RNC #1
RNC #2
BSC #1
BSC #2
GPS transmit Antenna
GPS Antenna
On rooftop
Power Input
Primary Clock Reference for RNC/iBSC
GPS is set as the primary clock resource for RNC/iBSC in CSL Network.
GPS receiver sub card is integrated into clock sync board: ICM.
25
49
Network Architecture
IP network architecture with L2 service providers of CSL
L3 switch (CISCO 6513) is provided to aggregation and route.
Every road leads to Rome: reliable transmission mechanism
5050
Downlink
uplink
Iub/Abis Link Redundancy
RedundancyScheme
L3 Dual-homing
Hot Standby Router Protocol (HSRP)
Automatic re-routing
Automatic re-routing
iBSC/RNC
65136513
BTS/Node B
26
51
Iub/Abis L2 Network Security
L2 Domain
L2 Domain
Node B/BTSsite
Node B/BTSsite
RAN 6513
RAN 6513
Core room BMI
RAN 6513
RAN 6513
Core room BPO
FE
FE
GE
GE
GE
GENode B/BTS
site
Node B/BTSsite
GE
GE
GE
FE
FE
40~60sites
40~60sites
L2 Domain completely isolated from each other
Each site connects one L2 Domain
Each L2 domain connects all 4 aggregation switches
52
VLAN Tagging Ensuring Network Security
L2 Domain
Node B/BTSsite
Node B/BTSsite
RAN 6513
RAN 6513
Core room BMI
RAN 6513
RAN 6513
Core room BPO
VLAN ID: 11 + 111
VLAN ID: 12 + 112
VLAN ID: 12 + 112
VLAN ID: 11 + 111
VLAN ID: 11 + 111+12+112
VLAN ID: 11 + 111
VLAN ID: 12 + 112
VLAN ID: 11 + 111+12+112
VLAN tagging is applied in Iub Ethernet transport; all Iub packets contain VLAN tagging.
Due to VLAN applied, not only L2 loop is avoided, but also traffic can be distributed to multiple GE links to achieve load balancing.