Sie sind auf Seite 1von 70

ZTE IP RAN Introduction

ZTE University
Content

IP Basics
RAN Network Trend
ZTE IP RAN Introduction
Case Study
TCP/IP Protocol and OSI Reference Model
7 Application Layer OSI Reference Model
TCP/IP

6 Presentation Layer Application Layer


TCP/IP
5 Session Layer

4 Transport Layer Transport Layer

3 Network Layer Network Layer

2 Data Link Layer Data Link Layer

1 Physical Layer Physical Layer

 The TCP/IP protocol stack has a simple layered design and a clear relationship with the OSI reference model.
TCP/IP Protocol Stack
Provides network interfaces for application
programs.
Common protocols: HTTP, FTP, SMTP, DNS,
TFTP……
Establishes end-to-end connections.
Common protocols: TCP and UDP
Implements addressing and route selection.
Application Layer Common protocols: IP (ICMP and ARP/RARP)
Implements access based on physical medium.
Transport Layer Common protocols: Ethernet, PPP, HDLC, Frame
Relay, X.25……

Network Layer Defines interface and cables.


Binary data stream transmission

Data Link Layer

Physical Layer
TCP/IP Data Encapsulation

TELNET FTP SMTP TFTP


23 20/21 25 69

TCP/UDP
6/17
IP PACKETS

FRAMES

BITS
Application Layer Protocols
 File transfer
--> FTP and TFTP
 Mail service
Application Layer --> SMTP and POP3
 Network management
Transport Layer
--> SNMP
Network Layer  Remote login
--> Telnet
Data Link Layer
 Network service
Physical Layer
--> HTTP, DNS, and WINS
Transport Layer Protocols

 Transmission Control Protocol (TCP)


 User Datagram Protocol (UDP)

Application Layer

Transport Layer

Network Layer

Data Link Layer

Physical Layer
Format of TCP/UDP Packets
0 8 16 24 31
16-bit source port 16-bit destination port
16-bit UDP length 16-bit UDP checksum
Data

Format of UDP packets

0 8 16 24 31
16-bit source port 16-bit destination port
32-bit serial number
32-bit ACK number
URG
ACK
PSH

SYN
RST

Header length Reserved (6 bits) FIN 16-bit window size


16-bit TCP checksum 16-bit emergency pointer
Option
Data

Format of TCP packets


Port Number
 Transport layer protocols use the port number to identify and
distinguish various upper-layer application programs.
 Socket = IP + Port number
HTTP FTP Telnet SMTP DNS TFTP SNMP

20/21 23 25 53 69 161
80
Socket

TCP UDP

IP Data Packet
How to Use TCP Port Number
Host

Server
IP: 10.1.1.2
Telnet 10.1.1.2, destination port 23

1028 23 10.1.1.2

Source Destination IP address


port port
Link Establishment After Three Handshakes
Through TCP
Host Server

Sends SYN
SYN (
seq =
a)

Receives
a+1) SYN
q = b , ack = Sends SYN,
e
SYN (s
Sends SYN ACK
Establishes a session
SYN
(seq=
a+1, a
ck = b
+1)
Sliding Window
len 1024
win4096
len 1024
win4096
len 1024
win4096 Data is transmitted
len 1024
Window size needs win4096 so fast!
to be changed.
win2048
ack 4097
len 1024
win2048
len 1024
win2048

win2048
ack 6145

len 1024
win2048
len 1024
win2048
Characteristics of UDP Transmission
 It provides a protocol-based port for distinguishing
various applications running on a same computer.
 It provides a delivery service based on data
packets that is unreliable and connectionless,
which is the same as that of the IP protocol.
 UDP packets may be lost, repeated, or received
with incorrect orders.
 It works simply and the format of UDP packets is
also simple.
Network Layer Protocols

 IP (Internet Protocol)
 ICMP (Internet Control Message
Protocol)

Application Layer  ARP (Address Resolution Protocol)


 RARP (Reverse Address Resolution
Transport Layer
Protocol)
Network Layer

Data Link Layer

Physical Layer
Format of IP Packet Header

Packet Total length


Version Service type
length

Identifier Flag Fragmentation offset

Time to live Protocol Header checksum

Source IP address

Destination IP address

IP option
Introduction of IPv6
 IPv4 is a great success.
 Fast development of Internet conflicts more and
more with insufficient IPv4 addresses.
 Application of new technologies raises more nt!
ic ie
requirements on the IP protocol. uff
ins
ore
m
and
or e
e m
ar
s
s se
d re
ad
4
IPv
Characteristics of IPv6
 Fundamental improvement: almost infinite address space
 The address length increases from 32 bits to 128 bits.
 Others (more characteristics)
 Simplicity: The fixed header is simplified, which improves
processing efficiency.
 Extendibility: The flexible and extendable header is used, and the
protocol is easily extendable.
 Plug and play: The address configuration is simplified. To be
specific, automatic configuration is implemented.
 Security: The IPSec authentication and encryption at the network
layer are used, which ensures end-to-end security.
 QoS: Stream flag field is supported.
 Mobility: Mobile IPv6 is supported.
Overview of IPv6 Address
 The presentation of the IPv6 address is different from that
of the IPv4 address.
 An IPv6 address is presented in hexadecimal mode, for example,
FE08.
 An IPv6 address consists of groups of characters with four bits
each and the groups are separated by colons, for example,
2001:12FC.
 If an IPv6 address is started with 0s, the 0s can be omitted. If a
group of characters are all 0s, the group can be presented as ::, for
example,   1:2::ABCD.
 The prefix length of an IPv6 address is presented in /xx format, for
example, 1::1/64.
 The following provides different presentations of a same
IPv6 address.
 0001:0123:0000:0000:0000:ABCD:0000:0001/96
 1:123:0:0:0:ABCD:0:1/96
 1:123::ABCD:0:1/96
Content

IP Basics
RAN Network Trend
ZTE IP RAN Introduction
Case Study
Service and Technology Trends
ARPU trend of European operators

Non-voice service explosion

Radio technology acceleration

LTE
HSPA+ R8/R9
R7/R8
HSPA
R5/R6 3.9G
UMTS
R99/R4 3.75G
GSM
3.5G
3G
2G
Year
2001-2 2003-5 2006-8 2009-10 After 2010
64-144kbps 384kbps 14Mbps 40Mbps 100Mbps & higher
DL throughput
Development of Bearing Network
Performance
Bandwidth --Broader
Data ability ----Stronger
Transmission efficiency --------Higher

TCO
Networking --More flexible
Investment ----Lower
Deployment --------Faster

Evolution
Expansion & relocation --Easier
Up to date technology ----Smoother

Convenience
Operation and maintenance --Simpler
Customized service ----Richer

TDM
ATM IP
Radio Access Network Development Towards All-IP
HSS
GGSN MGCF

IP Core
IMS
MSCS MRF
MGW CSCF
IP
IP Iub
Iub SGSN
IP
IP Iu
Iu IP
IP A
A
IP
IP Iur
Iur IP
IP Gb
Gb
IP
IP Ap
Ap IP
IP RAN IP Abis
Abis
IP RAN

IP radio access network advantages

 Data processing  Convenient


 Rapid construction  Convenient O&M
performance network upgrade
 Low maintenance  Rapid new service
 High transmission  Smooth network
cost deployment
efficiency evolution
Content

IP Basics
RAN Network Trend
ZTE IP RAN Introduction
 RAN Product
 Networking
 Synchronization
 QoS
 Reliability
 Security
 OAM
Case Study
iBSC/RNC Physical Interface for IP Support

 FE/GE
 STM-1/STM-4
 E1/T1/CSTM-1

 IP over E1/T1  IP over STM-1/  10GE port


 IP over Fractional STM-4
E1/T1
 IP over CSTM-1

High capacity High throughput High integration


BTS/Node B Physical Interface for IP Support
ZTE
ZTE SDR
SDR Series,
Series, All-IP
All-IP Supported
Supported

BS8900
BS8800
BS8906
B8200

STM-1 FE GE E1/T1

G900/U900 UMTS2100

 Native IP
 IPoE1
 2G/3G co-transmission
1*FE/GE
Content

IP Basics
RAN Network Trend
ZTE IP RAN Introduction
 RAN Product
 Networking
 Synchronization
 QoS
 Reliability
 Security
 OAM
Case Study
General IP RAN Topology
All IP

FE/GE FE/GE
FE/GE

FE IP/MSTP
RNC/BSC MSCS/MGW
IP/MSTP Backbone
Hybrid Transmission FE/GE FE/GE
FE/GE
FE

E1/T1/STM-1
E1/T1/STM-1
RNC/BSC SGSN/GGSN

E1/T1/STM-1 PDH/SDH Backbone

 All IP & hybrid available for all interfaces


 2G/3G transmission sharing & differentiation
 CS/PS differentiation
IP Networking Flexibility
 IP over Ethernet
 IP over E1/CSTM-1
Hub Node B
 IP over Fractional E1 RNC

 IP hub Node B Node B


 Microwave IDU integration
MW IDU

E1

FE/GE

Adaptable for diversified interfacing requirements


L3 Switch/Router for BSC/RNC
 Broadcast separation of the BSC/RNC from the transmission network
 Independent port number of the transmission network and the
BSC/RNC enabling independent capacity expansion
 Reuse of existing GE link between the switch and the transmission
network in case of IP Abis after IP Iub
 Easy re-parenting of the BTS/Node B from one BSC/RNC to another
 Adaptable for flat architecture

L2 switch

GE
GE BSC
IP Transmission
L3 switch
GE
RNC
L2 switch

BTS/Node B
Flex A/Gb/Iu with IP Transmission

More transmission required Less transmission required

IP
High implementation cost Low implementation cost
TDM Complex networking Simple networking

CN CN CN CN CN CN

BSC/RNC BSC/RNC BSC/RNC BSC/RNC BSC/RNC BSC/RNC

IP makes it more feasible.


Content

IP Basics
RAN Network Trend
ZTE IP RAN Introduction
 RAN Product
 Networking
 Synchronization
 QoS
 Reliability
 Security
 OAM
Case Study
Clock Accuracy
 Accuracy requirement
Mode Frequency Time
Accuracy Synchronization
Requirement Requirement
GSM +/-0.05ppm N/A
WCDMA +/-0.05ppm N/A

(Source: 3GPP TS 25.104, 25.402, GSM 05.02)

 Self-oscillation accuracy of ZTE RAN equipment


Period Frequency
Accuracy
First 24 hours +/-0.01ppm
First 7 days +/-0.015ppm
First 1 month +/-0.02ppm
Synchronization Modes of ZTE IP RAN

Synchronization
Time Slot
BTS/NB

BITS clock E1/T1/STM-N E1/T1/STM-N

Line clock
BSC/RNC GPS clock

master
1588msg 1588msg
L1 recovery

slave slave
BTS/NB BTS/NB

Clock over IP (IEEE1588) Synchronous Ethernet (G.8261)


Combination of Synchronization Modes

MGW MSC server GMSC


BITS clock
GGSN SGSN
CN GPS clock E1 clock
recovery
E1 clock BTS
recovery RNC E1 without traffic

Master Master E1 clock


BSC BSC
recovery

E1 Link
BTS
Ethernet
without clock
Node B
Ethernet
Slave Slave with clock
Node B
Clock direction
GPS clock
reception
Synchronization Reference Sources
 BSC/RNC
 1 master + up to 6 slave synchronization reference sources
 2Mbps BITS
 2MHz BITS
 Line clock (E1, STM-1)
 GPS
 BTS/Node B
 1 master + up to 6 slave synchronization reference sources

2Mbps BITS

2MHz BITS

Line clock (E1, STM-1)

GPS

IP clock (IEEE1588)

Synchronous Ethernet
Master Clock Selection
 OMC configurable
 Manual switch of master
clock
 Automatic switch of master
clock
 Manual reset of master
clock
 Automatic reset of master
clock
Content

IP Basics
RAN Network Trend
ZTE IP RAN Introduction
 RAN Product
 Networking
 Synchronization
 QoS
 Reliability
 Security
 OAM
Case Study
QoS Management in IP RAN
QoS parameters Traffic data QoS configuration
from CN from/to CN at OMC

RNL QoS Differentiation

DiffServ

IP

802.1Q/P MLPPP/MCPPP

TNL FE/GE E1

BSS/RNS
Traffic data
from/to MS
Flow Classification & Mapping to TNL
Traffic
class

User Traffic From CN Basic priority Bearer Type


Plane priority C (1-15) (R99/HSPA/MBMS)
(THP)
Configurable
User at OMC
priority
(ARP) C
Control
Plane C
DSCP
Management (COS)
Plane C

 Configurable mapping according to respective parameters for 2G and 3G


DSCP & COS Application
Traffic Type DSCP COS PHB
Iub NBAP Signaling 101110 5 EF (Expedited Forwarding)
Iub Common Transport Channel 101110 5 EF (Expedited Forwarding)
RRC Connection 100100 4 AF42 (Class4, Med Drop)
R99 Conversational 100100 4 AF42 (Class4, Med Drop)
R99 Streaming 100100 4 AF42 (Class4, Med Drop)
R99 Interactive 010100 2 AF22 (Class2, Med Drop)
R99 Background 000000 0 Best effort
HSPA Conversational 100110 4 AF43 (Class4, High Drop)
HSPA Streaming 100110 4 AF43 (Class4, High Drop)
HSPA Interactive 010110 2 AF23 (Class2, High Drop)
HSPA Background 000000 0 Best effort
2G Signaling 101110 5 EF (Expedited Forwarding)
2G CS 100100 4 AF42 (Class4, Med Drop)
2G PS 010100 2 AF22 (Class2, Med Drop)
O&M 000000 0 Best effort
Clock over IP (PTP) 101110 5 EF (Expedited Forwarding)
 Configurable mapping between DSCP and COS
QoS Requirement to IP Bearer Network (SLA)

Packet
Traffic Class Delay Packet Delay Jitter Packet Loss Ratio
(One Way)
IP clock < 20 ms < 7 ms < 0.05%

Conversation < 20 ms < 7 ms < 0.05%


al

Streaming < 20 ms < 7 ms < 0.05%

Interactive < 50 ms < 10 ms < 1%

Background < 50 ms < 10 ms < 1%


CAC Rule
Traffic Reserved Bandwidth Fixed/
Adjustable
Calculated bandwidth according to
Common channel Fixed
number of PCH and FACH
Signaling radio Bit rate of SRB + transport layer
Fixed
bearer overhead
[Maximum bit rate] of RAB + Adjustable
Conversational
transport layer overhead (activity factor )
[Guaranteed bit rate] of RAB +
Streaming Fixed
transport layer overhead
Interactive/ Pseudo-GBR (configurable) + Adjustable
background transport layer overhead (priority based)
QoS Based Routing

Mixed IPoE1 & Ethernet  Real time service over E1


Without VPN
(IPoE1)
All Ethernet
 Non real time service over
Ethernet
With VPN
 Routing based on DSCP
 Call balancing between
routes
IP RAN

E1

RNC/BSC
Ethernet

Node B/BTS
Overbooking

PS

PS

Overbooking
PS Allowable
allocation
PS

Total
CS
bandwidth
CS

Higher traffic capacity, higher bandwidth efficiency


Dynamic Bandwidth Adjustment

Dynamic
Link broken adjustment

PS PS

PS PS
Poor
CS performance CS

CS CS

Real time monitoring, real time adaptation


Congestion Control
C:
C: 64kbps
64kbps B: ~384kbps

Iu

User Plane scheduling

Congestion indication
RNC
Transport bandwidth
based shaping (downlink)

Iub

Transport bandwidth
based shaping (uplink) Node B

C: 64kbps B: ~384kbps
Uu
Content

IP Basics
RAN Network Trend
ZTE IP RAN Introduction
 RAN Product
 Networking
 Synchronization
 QoS
 Reliability
 Security
 OAM
Case Study
Reliability of IP RAN
 Networking redundancy  Hardware redundancy
 2G/3G backup  Board redundancy
 Iu/A/Gb flex  Port redundancy

 Path protection
 L2 dual homing
 L3 dual homing
 Multiple path protection
 Link aggregation (IEEE
802.3ad)
RNC router1
IP1 path1 IP1'
IP3
IP2
router2
path2 IP2' PSN
ip4

path3 IP3'

router3
SGSN
2G/3G Backup
NOC A

RNC

2G
BSC
BTS/Node B 3G

3G
CN
2G

RNC
BTS/Node B
BSC
NOC B
L2 Dual Homing
IP: 10.1.1.254/24
IP: 10.1.1.1/24 MAC: 00:15:EB:00:95:DD
MAC: 00:15:EB:A1:66:0A

GIPI(M)
L2 switch

GIPI(S)
BTS/Node B L2 switch

BSC/RNC

Master-standby: Two FE/GE ports, one IP/MAC address


L3 Dual Homing
IP: 10.1.2.1/30
IP: 10.1.1.1/24 MAC: 00:15:EB:00:95:DD
MAC: 00:15:EB:A1:66:0A

GIPI

L3 switch BSC/RNC

BTS/Node B GIPI
L3 switch

IP: 10.1.1.2/24
MAC: 00:15:EB:A1:66:1A IP: 10.1.2.5/30
MAC: 00:15:EB:00:95:D0

Load sharing: Two FE/GE ports, two IP addresses


IEEE 802.3ad Link Aggregation
Link1
 Bandwidth
Link2

expansion Link3

 Link redundancy
 Load balancing Subflow1

 Static & dynamic Link A Subflow2

Subflow3

Multiple physical links into one logical link


High performance with low cost
Multiple Path Protection
 Path selection
 Static path priority for different
traffic flow
 Automatic connectivity detection
 Dynamic bandwidth measurement
 Periodical SLA monitoring
 Dual path protection RNC
 ATM over E1 & IP over Ethernet E1
 IP over E1 & IP over Ethernet
 Dual VLAN within one FE/GE port Ethernet
 Multiple path protection
 Multiple VP within one IMA group
 Multiple VP within two IMA groups
 One IMA group & dual VLAN Node B
 Multiple VLAN within one FE/GE
port

Reliable Traffic Transfer


Content

IP Basics
RAN Network Trend
ZTE IP RAN Introduction
 RAN Product
 Networking
 Synchronization
 QoS
 Reliability
 Security
 OAM
Case Study
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
VLAN Configuration Recommendation
 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
RNC

VLAN
RNC

VLAN1 …… VLANn

Node B
Node B
Content

IP Basics
RAN Network Trend
ZTE IP RAN Introduction
 RAN Product
 Networking
 Synchronization
 QoS
 Reliability
 Security
 OAM
Case Study
OAM for IP RAN
 Link connectivity
monitoring
 BFD: IP connectivity check
 IEEE 802.3ah: Ethernet
connectivity check (P2P)
 IEEE 802.1ag: Ethernet
BSC
connectivity check (E2E)
 Link performance
IP Transmission
monitoring
CN
 SLA monitoring
 Performance measurement
BTS/Node B RNC
Content

IP Basics
RAN Network Trend
ZTE IP RAN Introduction
Case Study
Revolution of XXX Mobile Network
3G OSS UMTS
2G OSSVAS Platform
Existing UMTS 2.1G
2.1G/900M
HLR TDM Network
XXX SGSN
XXX New CN
Network MSCS
Network Iub
HLR
BSC/ GSM 900/1800M
RNC
Core Network IP
VAS 2G OSS
Network
ZTE MSCS/
MGW
Abis

2G/3G OSS GSM


ZTE VASHLR
Platform
SGSN
GSM 1800M
NWM CN TDM Network 900/1800M
MSCS
Network

Difficult Expensive High Power


Evolution Transmission Consumption
Network Architecture BMI BPO
NOC #1 NOC #2
PE Router-11 PE Router-21

PE Router-12 PE Router-22

CN switch CN switch

Core 6513-11 Core 6513-12 Core 6513-21 Core 6513-22


RAN RAN

ZRNC ZRNC ZRNC ZBSC ZBSC ZBSC ZRNC ZRNC ZRNC ZBSC ZBSC ZBSC
101 102 103 11 12 13 201 202 203 21 22 23

RAN6513-11 RAN6513-12 RAN6513-21 RAN6513-22

RAN

TRAXCOMM HGC NWT WT&T

2G/3G 2G/3G 2G/3G 2G/3G 2G/3G 2G/3G 2G/3G 2G/3G


BS BS BS BS BS BS BS BS

IP network architecture with L2 service providers of XXX


L3 switch (CISCO 6513) is provided to aggregation and route.
Every road leads to Rome: reliable transmission mechanism
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

iBSC/RNC

FE Primary clock reference: IP Clock


Indoor
E1/T1 Primary clock reference: E1 / T1

Primary clock reference: GPS


Outdoor
BTS/Node B Secondary clock reference: IP Clock
Primary Clock Reference for RNC/iBSC

GPS Antenna
On rooftop

GPS Controller

Power Input GPS transmit


Antenna  GPS is set as the primary
clock resource for
RNC/iBSC in CSL Network.

RNC RNC BSC BSC  GPS receiver sub card is


#1 #2 #1 #2 integrated into clock sync
board: ICM.
Iub/Abis Link Redundancy
iBSC/RNC
Redundancy
Scheme

L3 Dual-homing
6513 6513
Hot Standby Router
Protocol (HSRP)

Automatic
re-routing
Downlink
uplink
BTS/Node B
Iu Flex Implementation
BPA CN ID NRI
PPA MSCS1 1
MSCS2 2
MSCS1 MSCS3 MSCS2 MSCS4
MSCS3 3
MSCS4 4
RNC101 SGSN1 1
SGSN2 2
BPA SGSN3 3
PPA SGSN4 4

SGSN1 SGSN3 SGSN2 SGSN4

 BPA – Base Pool Area


NOC #1 NOC #2
 PPA – Preferred Pool Area

 NRI – Network Resource Identifier


Iub/Abis L2 Network Security
Node B/BTS
FE
site

40~60 RAN 6513


sites GE
L2 Domain
Node B/BTS FE Core room 1
site
GE RAN 6513

GE

Node B/BTS GE
site FE GE
RAN 6513
40~60
L2 Domain GE
sites Core room 2
Node B/BTS FE
site RAN 6513
GE

 L2 Domain completely isolated from each other


 Each site connects one L2 Domain
 Each L2 domain connects all 4 aggregation switches
VLAN Tagging Ensuring Network Security

VLAN ID: 11 + 111 RAN 6513

VLAN ID: 12 + 112 Core room 1


Node B/BTS VLAN ID: 11 + 111
site VLAN ID: 11 + 111 RAN 6513

L2 Domain VLAN ID: 12 + 112

Node B/BTS
VLAN ID: 12 + 112 VLAN ID: 11 + 111
site +12+112
RAN 6513

VLAN ID: 11 + 111 Core room 2


+12+112

RAN 6513

 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.
IP QoS Implementation
DSCP RNC BSC

GE GE

DSCP -> COS RAN 6513 COS

GE

Ethernet
SP

FE

COS ZTE 2818S COS

FE FE

SDR 1 SDR 2 DSCP & COS


Site Networking
Site A Site B

Traffic: 10.9.11.2/24
SDR
Traffic: 10.9.11.1/24 O&M: 10.9.111.42/24
O&M 1: 10.9.11.201/24 (3G 2100M)
O&M: 10.9.111.41/24 O&M 2: 10.9.11.202/24
SDR ZXMW IDU
(3G 2100M)
ZXMW IDU ZXR10 2818S

O&M 1: 10.9.210.1/29 O&M: 10.9.111.82/24


Service O&M 2: 10.9.210.2/29
Provider ZXR10 2818S
SDR (2G
Network 900M/1800M,
O&M: 10.9.111.81/24
3G 900M)
SDR (2G 3G Traffic: 10.9.11.102/24
900M/1800M, 2G Traffic: 10.10.111.22/24
3G 900M) O&M: 10.9.111.142/24

3G Traffic: 10.9.11.101/24
2G Traffic: 10.10.111.21/24
O&M: 10.9.111.141/24
O&M 1: 10.9.11.203/24 Site C
O&M 2: 10.9.11.204/24

ZXMW IDU
Traffic: 10.9.11.3/24
SDR O&M: 10.9.111.43/24
(3G 2100M)
ZXMW IDU

O&M 1: 10.9.210.9/29
O&M 2: 10.9.210.10/29 ZXR10 2818SO&M: 10.9.111.83/24
Site D

SDR (2G
SDR 900M/1800M,
ZXMW IDU
(3G 2100M/900M) 3G 900M)
ZXMW IDU
O&M 1: 10.9.210.17/29 3G Traffic: 10.9.11.103/24
Traffic: 10.9.11.4/24 O&M 2: 10.9.210.18/29 O&M 1: 10.9.210.11/29 2G Traffic: 10.10.111.23/24
O&M: 10.9.111.44/24 O&M 2: 10.9.210.12/29 O&M: 10.9.111.143/24