IP Backhaul (IPBH) 3G-1x CDMA
Overview
Wang Yu Ying
July 31th, 2008
All Rights Reserved © Alcatel-Lucent 2006, ##### 2 | Presentation Title | Month 2006
Outline:
Introduction
IPBH Architecture Overview
IPBH Network Overview
IP Addressing for IPBH Network Elements
Data Provision
All Rights Reserved © Alcatel-Lucent 2006, ##### 3 | Presentation Title | Month 2006
Introduction
All Rights Reserved © Alcatel-Lucent 2006, ##### 4 | Presentation Title | Month 2006
Introduction:
CDMA IP Backhaul uses Internet Protocol as a standardized network layer for transferring signaling and bearer traffic between network elements (e.g. Base Transceiver Station (BTS), DCS and ECPC).
Solution achieves better bandwidth utilization between the cells and MSC enabling fewer leased facilities for a given level of traffic.
The solution includes the following components :
– 3G-1X Base Stations
– IP Transport (Edge Routers, L2 Switches or MLS)
– MSC Equipment
All Rights Reserved © Alcatel-Lucent 2006, ##### 5 | Presentation Title | Month 2006
Configuration Requirements
Supported on all Modcell types (1 through 4) with Universal Radio
Controller (URC)
– Modcell 1.0/2.0/3.0 requires upgrade of all CDMA Radio Complex
(CRC) to URCm
IP Backhaul Cell is either all IP or Frame Relay (FR)
– Cannot mix IP and FR on the same cell
Supported only on FMM platform for the RCS-AP
Supports a mix of IP and FR BTSs on one RCS-AP
5E BHS requires PSU2e with Core700 SMP
Soft-handoff universe can support mix of IP and FR BTSs
Does not alter ATM soft-handoff network (intra or inter-MSC)
– IP soft-handoff in the future
All Rights Reserved © Alcatel-Lucent 2006, ##### 6 | Presentation Title | Month 2006
Benefits of converting from FR to IPBH
leverages IP as standardized network layer for signaling and bearer transport for BTS to MSC.
Evolution path to All-IP-Network.
Provides increased and improved capacity on the 5ESS DCS and T1 carriers.
Separate voice and data packets
Frees up trunk resources
All Rights Reserved © Alcatel-Lucent 2006, ##### 7 | Presentation Title | Month 2006
IPBH Architecture Overview
All Rights Reserved © Alcatel-Lucent 2006, ##### 8 | Presentation Title | Month 2006
TDM
Grooming
Backhaul
Transport
Network
5ESS DCS
P
H
A
F
R
P
H
F
R
P
H
F
R
P
H
F
R
P
H
DF2
D
F
I
D
F
I
TSI
OIU
OCx/DS3
or STMx
RCS
AP
MSC AP
Complex
PPs and SLs
Signaling
Links (SLs)
on DS0s
over T1/E1
PPs on
STS1s
PPs+SLs
on
T1s/E1s
PSU
Signaling links delivered to ECPC directly from DACS or via 5ESS
nail-up
5ESS interfaces carry PPs only or
optionally PPs with SLs
PPs delivered to FRPH via
TMS/TSI and DF2
SLs delivered to ECPC via nailup connection to
T1/E1
RCS
AP
RCS
AP
ATM
Network
Current Backhaul via Frame Relay
All Rights Reserved © Alcatel-Lucent 2006, ##### 9 | Presentation Title | Month 2006
IP Backhaul Architecture
Ethernet
Backhaul
Transport
Network
Up to OC - 12
Traffic and
Signaling
RCS AP
5ESS DCS
P H A
F R P H
F R P H
F R P H
F R P H
F R P H
F R P H
F R P H
F R P H
B H S P H
DF2
D F I
D F I
TSI
DNU - S
PSU
OC-3
100BaseT Ethernet
OIU
PSTN
Edge Routers
FMM LAN
FMM AP
Complex
Control signaling delivered to FMM LAN directly from backhaul router (No DS0 grooming)
100BaseT Ethernet (or GigE in Future)
DNU-Ss/DLTUs can be retired from backhaul
usage
Recovered fabric capacity
Traffic delivered directly to specific BHS (voice or data)
All Rights Reserved © Alcatel-Lucent 2006, ##### 10 | Presentation Title | Month 2006
Architecture Overview
All traffic and signaling between BTSs and the MSC is carried over the IP network layer (IP Version 4 only). The network interfaces at the BTSs are un-channelized DS1s.
At the BTS traffic on any carrier can be switched to/from any DS1 in the same BTS frame so DS1s can be optimally utilized. Bandwidth is added to a BTS frame in DS1 increments as needed to support capacity growth regardless of carrier configuration and carrier load.
Traffic and signaling are mixed over the DS1s and separated at the IP switching layer.
On the network side the DS1s terminate on commercial IP aggregation routers. Connections to elements at the MSC are all IP over Ethernet, rather than fractional DS1 TDM channels.
All Rights Reserved © Alcatel-Lucent 2006, ##### 11 | Presentation Title | Month 2006
Architecture Overview(con’t)
Provisioned data determines which PSU and/or RNC will serve the traffic from a given BTS. A different PSU can be provisioned per carrier.
BTSs can be provisioned such that voice is served on a PSU (or PSUs) while packet data is served on an RNC (or RNCs). This enables packet data to be truly offloaded from PSUs and the inter-PSU soft handoff network.
IP backhaul is supported on all Modcell types with Universal Radio Controllers (URCm, URC-1 and URC-2). It is not supported on Modcells with CRCs.
IP backhaul is supported on RCSs hosted on FMM-APs. It is not supported on RCSs hosted on GNP-APs.
All Rights Reserved © Alcatel-Lucent 2006, ##### 12 | Presentation Title | Month 2006
Differences Between FRPP and IP Backhaul
FR Packet Pipe IP Backhaul
Trunk Group, Trunk Group
Member provisioning
Automatic backhaul association
Data Link provisioning TCP/IP connection for data link
DACS for DS0 Grooming IP Edge router
FRPH/DFI in 5E PSU BHS
E1 termination at 5E Ethernet termination at 5E
E1 termination at AP Ethernet termination at AP
All Rights Reserved © Alcatel-Lucent 2006, ##### 13 | Presentation Title | Month 2006
IPBH Network Overview
All Rights Reserved © Alcatel-Lucent 2006, ##### 14 | Presentation Title | Month 2006
URC 1
BTS 1
BHS 1
PSU 1
BHS 2
BHS 3
Traffic subnets per MLS
MLGs
B2
B1
Control subnet
UDPmux UDP IP
ML-PPP NxE1
URC 1
BTS n
URC 2
ER-2
ER-1 MLS-1
MLS-2
MSC NxE1 Ethernet Flexible L1/L2
L2-A
L2-B
RCS 1
RCS 2
RCS x
BHS 4
…
PS (SM)
Control TCP IP
ML-PPP NxE1
UDPmux UDP IP
Ethernet
Control TCP IP
Ethernet
Multi-Layer Switches
…
Edge Routers
MMC
Tr1
Tr2
BTS subnets per ER
Router NMS
IP Backhaul Network Topology
VRRP
All Rights Reserved © Alcatel-Lucent 2006, ##### 15 | Presentation Title | Month 2006
Important Terms
MLG
BHM
BHA
BHS
BHCS(BSSA)
All Rights Reserved © Alcatel-Lucent 2006, ##### 16 | Presentation Title | Month 2006
MLG
MLG (Multi Link Group) and MultiLink-PPP (ML-PPP)
– A group of DS1 between Base Station(s) & Edge Router
– Running ML-PPP protocol to split and recombine sequencing
datagrams across E1s, like SS7 signaling load-sharing
Router D
A C S URC
URC BTS
URC
OC-3, OC-12
All Rights Reserved © Alcatel-Lucent 2006, ##### 17 | Presentation Title | Month 2006
BHM
BHM (Backhaul Manager)
– The BHM is in the ECPC FMM complex to manage the BHS to BTS
associations required for user traffic.
– The role of the BHM is to provide to each RCS/BTS all the
information that is needs to create user traffic associations
between the BTS and their assigned BHSs
– The BHM combines the provisioned information for the BTS with
information about the BHSs that it pulls from DCSs to produce the
information that it sends to each RCS/BTS.
– The BHM runs on the FMM B-servers
– The BHM communicates with a DCS over the existing ECPC-DCS
communications infrastructure
All Rights Reserved © Alcatel-Lucent 2006, ##### 18 | Presentation Title | Month 2006
BHM Primary Interfaces
BHM
RCS-1
RCS-2
RCS-3
RCS-x
RNC
BHS-2
BHS-1
BHS-3
5ESS
PSU2e BHS-1
BHS-2
BHS-3
BHS-4
RC/V
BHS Configuration & Status
RC/V Configuration
& Updates
RCS (Carrier/SOC/BHS)
SDP ROP
All Rights Reserved © Alcatel-Lucent 2006, ##### 19 | Presentation Title | Month 2006
BHA
The backhaul server association (BHA) is a UDPMux session between a BTS and a BHS. This association is identified by the BTS IP address, the BHS IP address, and the UDP port number.
A BHA is simply the linking or association of a BTS and BPH to form logical, semi-permanent path for carrying user traffic between BTS and BPH.
All Rights Reserved © Alcatel-Lucent 2006, ##### 20 | Presentation Title | Month 2006
Backhaul Server Association (BHA)
URC1
IP addr 1
IP addr 2
URC2
BTS 1
MLG1
MLG2
URC1
IP addr 3
BTS 2
MLG1
BPH 1
IP addr 4
PSU 1
BPH 2
IP addr 5
BPH 3
IP addr 6
UDPa
UDPb
UDPz
UDPg
UDPc
UDPa
UDPb
UDPa
UDPf
UDPd
UDPy
UDPz
A BHA is simply the linking or
association of a BTS and BPH
to form logical, semi-
permanent path for carrying user traffic between BTS and
BPH.
BHA are set up by a BTS based on ECP provisioning: carrier/Service Option Class(SOC)-to-BPH (SOC is voice, data, or both)
BHA is identified by MLG and BHS IP addresses and UDP ports
BHA are not maintained as trunks, i.e maintenance is not like PP maintenance
PHE3 can terminate up to 256 BHA from multiple BTS and MLGs
BHA can handle up to 240 call legs
DCS provides commands to dump BHA information on a BPH/PHGRP
Heart-beat messages (XID bounce) are used to verify health of a BHA
All Rights Reserved © Alcatel-Lucent 2006, ##### 21 | Presentation Title | Month 2006
BHS
Backhaul Server Group (BHS) resides in PHU2e
– The thing at the MSC that terminates an IP connection from a BTS
– BPH on PSU
– BHS is a PHGRP that handles IP backhaul traffic (FPS calls it BPH)
All Rights Reserved © Alcatel-Lucent 2006, ##### 22 | Presentation Title | Month 2006
IP Backhaul Architecture – FPS DCS BPH
L2/MLS-1
L2/MLS-2
BHSs
Multi-Layer Switches
• IP backhaul will only be supported on SM2K with Core700 and PSU2e.
• IP backhaul traffic is terminated on BPH:
• PHE3 with 100 BaseT on PSU2e (TN113 with Ethernet paddle board)
• Future: PHE4 in future with GigE on iPS
• BPH must be equipped in duplex configuration
•The BPH pair share a “floating” IP address
•Each BPH has its own IP address
• A PHGRP (i.e., BHS) identifies a BPH pair.
• PHE3 can handle up to 2,000 EVRC call legs
• PHE4 is expected to handle up to 30,000 EVRC calls
Backhaul Server (BHS)
A PHGRP that handles IP
backhaul traffic (FPS calls
it BPH)
UDPmux UDP IP
Ethernet
PSU 1
BHS 1 BHS 1
BHS 1
BHS 1
BHS 1
BHS 2
BHS 3
BHS 4
All Rights Reserved © Alcatel-Lucent 2006, ##### 23 | Presentation Title | Month 2006
BHCS(BSSA)
BHCS(IP Backhaul Connection Server), it is called BSSA (Backhaul Server Security Agent) after R28
– the primary role of the BHCS is to send URCs the addresses of the BTS’s
primary and alternate RCSs.
Why do we need a BHCS?
– Introducing IP addressing allows us to be more flexible with our
configuration
– This means the BTS no longer has a nailed up path directly to its
RCS
– Somehow the BTS needs to determine the AP that it needs to be
communicating with
– Did not want to provision the information directly into the BTS, or
into the supporting IP Network since the information is already in
the MSC
All Rights Reserved © Alcatel-Lucent 2006, ##### 24 | Presentation Title | Month 2006
Basic BHCS Scenario
Once a BTS boots it will perform the following
– The BTS receives the BHCS IP addresses (LAN0 and LAN1) from the
Edge Router via the IPCP protocol during the PPP setup
The BTS will perform the following per MLG
– The BTS sends a request to the BHCS using the Simple Base Station
Startup Protocol (SBSP). In the request the BTS sends its Backplane
Serial Number.
– The BHCS receives the number and authenticates the BTS. The
authentication requires
• The BPSN can be found in the MSC database
• The BTS is properly configured to use IP Backhaul
All Rights Reserved © Alcatel-Lucent 2006, ##### 25 | Presentation Title | Month 2006
Basic BHCS Scenario (cont’d)
Once authenticated, the BHCS uses the BPSN to perform a lookup into the database to identify the Primary and Alternate RCS-APs
The BHCS will then use the RCS-AP numbers and the Network Address to calculate the IP Addresses which need to be returned to the BTS
The BHCS will then return the following
– IP Address and Port Number of Primary FMM-AP LAN interface 0
– IP Address and Port Number of Primary FMM-AP LAN interface 1
– IP Address and Port Number of Secondary FMM-AP LAN int 0
– IP Address and Port Number of Secondary FMM-AP LAN int 1
If the BHCS cannot authenticate the BTS, the BHCS will NOT send a response back to the BTS
All Rights Reserved © Alcatel-Lucent 2006, ##### 26 | Presentation Title | Month 2006
BTS Router MSC Component
Establish PPP/MLPPP
Provide MLG and BHCS IP to BTS via IPCP
Queries BHCS for AP IP
for its RCS process
RCS AP 5E or RNC BHCS
RCS provides
configuration to BTS Including IP of 5E or RNC BHS
Part of stable clear
Establishes UDPBHA
sockets with 5E or RNC BHS
for bearer channel
TCP
TCP
Establishes signaling
link socket with the AP
TCP
UDP
BTS
Finishes initialization To OAM Ready
BTS
Call Processing Ready
BTS Initialization
All Rights Reserved © Alcatel-Lucent 2006, ##### 27 | Presentation Title | Month 2006
j,x
k,y
j,x
k,y
j,x
k,y
c, j,x
c, k,y
a,x
b,y
a,x
b,y
a,x
b,y
a,x
b,y
x
y
x
y
L
2
1
L
2
0
L
2
1
L
2
0
L
2
1
L
2
0 c, j
c ,a
c, k
c, b
MLS 0
MLS 1
Base FMM-AP
Frame
AP
AP
AP
AP
AP
AP
AP
AP
AP
AP
BHCS
BHCS Network Access
=> Must have access
from each MLS
to every AP frame
=> Must maintain access when
- one MLS fails
- one L2 fails
- one AP port fails
Note:
All URCs must
communicate
with the single
lead BHCS to
begin URC –
MSC link
initialization
BHCS can float
to any AP in
any frame
All Rights Reserved © Alcatel-Lucent 2006, ##### 28 | Presentation Title | Month 2006
URC 1
BTS n
URC 2
URC 1
BTS 1
BHS 1
BHS 2
BHS 3
MLG-1
Control subnets
UDPmux UDP IP
ML-PPP NxT1
ER-
ER- MLS-0
MLS-1
MSC NxT1 Ethernet Flexible L1/L2
L2-0
L2-1
RCSAP
RCSAP
RCSAP
BHS 4
…
PSUs/RNCs
Control TCP IP
ML-PPP NxT1
UDPmux UDP IP
Ethernet
Control TCP IP
Ethernet Multi-Layer Switches
…
Edge Routers
Growth Frame FMM APs
Router NMS
Traffic subnets
MLG-1
MLG-1
MLG-2
IP Backhaul Mode
All Rights Reserved © Alcatel-Lucent 2006, ##### 29 | Presentation Title | Month 2006
L3
RCS-AP Connectivity - L3/L2 Adjacent to MSC
L2
L2-0
L2-1
RCS-AP
Frame 3
L2-0
L2-1
RCS-AP
Frame 7 L2-0
L2-1
Base
Frame
ERs ERs ERs
Secondary route to control subnet 0
Frame gateways within control subnet 0
Frame gateways within control subnet 1
L3
Primary route to control subnet 0
Per-frame gateways keep backhaul packets off inter-frame links
RCS-AP 1
RCS-AP 2
RCS-AP 24
…
L3
Fr-3
Fr-7 Ctl-0
…
…
…
Ctl-1 …
…
…
Fr-7
Fr-3
Router 1
Router 2 Frame subnets
not visible to ERs
All Rights Reserved © Alcatel-Lucent 2006, ##### 30 | Presentation Title | Month 2006
BHS Connectivity - L3/L2 Adjacent to MSC
L3 L2
TGW-2
ERs ERs ERs
1+1 Pair
BHS-A
BHS-B
TGW-1 L2
L2
L3
L3
Router 1
Router 2
MLS 1
MLS 2
All uplink routes are equal
Primary route to ER X
Secondary route to ER X
If BHS-A uses TGW-1 and BHS-B uses TGW-2, then no need for VRRP
Could be one or more traffic subnets (but not clear why more than one is useful)
VLAN tagged if more than one traffic subnet and/or shared interface
All Rights Reserved © Alcatel-Lucent 2006, ##### 31 | Presentation Title | Month 2006
BPH Architecture – Traffic Frames
Host
Internal IP Addr
BHS Service
External IP Addr
Physical
External IP Addr
PHE3 (Serving BPH)
Host
Internal IP Addr
Physical
External IP Addr
PHE3 (Non-serving BPH)
PB
MA
X
PB
MA
X
Eth
ern
et
Pad
dle
board
Eth
ern
et
Pad
dle
board
AP
AP
BHA - UDPMux
traffic between the
BHS IP address on
the Serving BPH
and the MLGs
Traffic frames
between BPH and
Frame Selectors in
PHVs
CID-DLCI Map
control between
Frame Selectors in
PHV/DPH and BPH
Serving BPH
update of
dynamic data in
non-serving BPH
CID Map Shadow
CID Map Shadow
NP
NP
All Rights Reserved © Alcatel-Lucent 2006, ##### 32 | Presentation Title | Month 2006
ER-1
ER-2 SW-2
SW-1
BTS PSU 2
BHS 3
MLG
MSC
L2-A
L2-B
RCS-AP 1
RCS-AP 2
BHS 1
PSU 1
SHO
PS
MSC Switches
Edge Routers
Growth Frame
FMM-APs in MMC
BHS 1
Control
RCS
Carrier 1
Voice
Carrier 2
Voice
Carrier 2
Data
Carrier 2
Voice
Carrier 1
Voice
Carrier 2
Data
Control Voice Data
IP Backhaul Service Frame
All Rights Reserved © Alcatel-Lucent 2006, ##### 33 | Presentation Title | Month 2006
IP Addressing for IPBH Network
Elements
All Rights Reserved © Alcatel-Lucent 2006, ##### 34 | Presentation Title | Month 2006
IP Backhaul Network Addressing
Three addresses are provisioned at the MSC that define the control subnets: the network ID of the control subnets and the address of a gateway router for each subnet.
Only one network ID is required because the two subnets are contiguous.
The control subnets can be located anywhere in the IP address range.
In practice, the control subnets cannot overlap with any BTS or traffic (BHS) subnets, and they cannot overlap with the AP subnets used for internal communications
All Rights Reserved © Alcatel-Lucent 2006, ##### 35 | Presentation Title | Month 2006
Network Elements IP Connectivity
FMM APs (Cajun Switches) to MLS Switches
– Layer 3 connections terminate at the MLSes
5ESS and BHS to MLS Switches
– Layer 2 connections terminate at the MLSes. The HSRP / VRRP runs
at the MLS switches to terminate these L2 connections
MLS to Edge Routers Connections
– Layer 3 Point-to-Point links between the MLSes and the Edge
Routers (ERs)
All Rights Reserved © Alcatel-Lucent 2006, ##### 36 | Presentation Title | Month 2006
RCS-AP IP Addressing
The ECPC-AP LAN is dual star cross-connected only in the base frame
– Each AP has an interface to each “half” of the ECPC LAN
– Up to 24 APs per growth frame including the Satellites APs
– FMM-AP supports both IPBH and FR simultaneously
L2-0
L2-1
Base
Frame
L2-0
L2-1
Growth
Frame 3
L2-0
L2-1
Growth
Frame N
No AP address Change for existing FR APF IPBH FMM-AP Assign New Addresses
L2-0
L2-1
Growth
Frame 1 AP 1
AP 2
AP 24
…
…
LAG
L2-0
L2-1
Growth
Frame 1 AP 1
AP 2
AP 24
…
…
MLS-01
MLS-02
All Rights Reserved © Alcatel-Lucent 2006, ##### 37 | Presentation Title | Month 2006
RCS-AP IP Addressing
Each RCS-AP requires two IP addresses for backhaul, one for each of its Ethernet interfaces.
The provisioned network ID and the AP’s logical number determine the two addresses used by an AP.
The backhaul IP address of an RCS-AP interface is static and is not moved between interfaces to accomplish fault tolerant networking. Therefore, each RCS-AP is known to BTSs by both of its IP addresses.
All Rights Reserved © Alcatel-Lucent 2006, ##### 38 | Presentation Title | Month 2006
RCS-AP IP Addressing
/21 bit Network Prefix (Provisioned on ECP form) defines the block of 2048 addresses from which all RCS-AP IP Addresses and the Gateway Addresses are automatically derived
– 2048 IP Address block is subdivided into 2 adjacent subnets of 1024
Addresses each for each ½ of the AP LAN
• RCS-AP LAN 0 – 1024 Addresses (/22)
• RCS-AP LAN 1 – 1024 Addresses (/22)
– Each 1024 block (/22) is further divided into blocks of 32 IP
Addresses (/27) for each Frame
• AP Frame LAN 0 - /27 per Frame
• AP Frame LAN 1 - /27 per Frame
All Rights Reserved © Alcatel-Lucent 2006, ##### 39 | Presentation Title | Month 2006
RCS-AP IP Addressing
Each AP derives a backhaul address for each of its interfaces based on
– Network Prefix (LAN 0 or 1), Frame # (1-28), Drawer # (1-8), Slot #
(1-3)
Frame offset 0 and host ID 1 is used by the BHCS
Network Prefix
Fr 0 Fr 1 Fr 2 Fr 3 … Fr 28 … 31
Fr 0 Fr 1 Fr 2 Fr 3 … Fr 28 … 31
1024 LAN-0
1024 LAN-1
32 addresses per frame
2048
All Rights Reserved © Alcatel-Lucent 2006, ##### 40 | Presentation Title | Month 2006
BHCS IP Addressing
The Backhaul Connection Server (BHCS) IP address will be calculated form the Control Network ID. The BHCS Host Id will be 1, and its default gateway will be host Id 30, in each of the 2 Lans.
The IP address for the BHCS will move to whichever AP is hosting the active process.
All RCS-APs that support IPBH has an active CCMip that is capable of hosting BHCS. Currently there is one active BHCS in the MSC
All Rights Reserved © Alcatel-Lucent 2006, ##### 41 | Presentation Title | Month 2006
RCS-AP IP Addressing – An Example
Network Type LAN-0 LAN-1
Network Address 172.17.0.0 /27 172.17.4.0 /27
BHCS 172.17.0.1 172.17.4.1
Unused 172.17.0.2 172.17.4.2
Unused 172.17.0.3 172.17.4.3
Unused 172.17.0.4 172.17.4.4
Unused 172.17.0.5 172.17.4.5
Unused 172.17.0.6 172.17.4.6
Unused 172.17.0.7 172.17.4.7
Unused 172.17.0.8 172.17.4.8
Unused 172.17.0.9 172.17.4.9
Unused 172.17.0.10 172.17.4.10
Unused 172.17.0.11 172.17.4.11
Unused 172.17.0.12 172.17.4.12
Unused 172.17.0.13 172.17.4.13
Unused 172.17.0.14 172.17.4.14
Unused 172.17.0.15 172.17.4.15
Unused 172.17.0.16 172.17.4.16
Unused 172.17.0.17 172.17.4.17
Unused 172.17.0.18 172.17.4.18
Unused 172.17.0.19 172.17.4.19
Unused 172.17.0.20 172.17.4.20
Unused 172.17.0.21 172.17.4.21
Unused 172.17.0.22 172.17.4.22
Unused 172.17.0.23 172.17.4.23
Unused 172.17.0.24 172.17.4.24
Unused 172.17.0.25 172.17.4.25
Unused 172.17.0.26 172.17.4.26
Unused 172.17.0.27 172.17.4.27
Unused 172.17.0.28 172.17.4.28
Unused 172.17.0.29 172.17.4.29
Default Gateway 172.17.0.30 172.17.4.30
Broadcast 172.17.0.31 172.17.4.31
BHCS
Network Address – 172.17.0.0 /21
RCS AP LAN 0 – 172.17.0.0 /22
RCS AP LAN 1 – 172.17.4.0 /22
BHCS LAN 0 – 172.17.0.0 /27
BHCS LAN 1 – 172.17.4.0 /27
AP Frame 1 LAN 0 – 172.17.0.32
/27
AP Frame 1 LAN 1 – 172.17.4.32
/27
All Rights Reserved © Alcatel-Lucent 2006, ##### 42 | Presentation Title | Month 2006
RCS-AP IP Addressing – An Example Frame No -->
Network Type LAN-0 LAN-1 LAN-0 LAN-1 LAN-0 LAN-1
Network Address 172.17.0.32 /27 172.17.4.32/27 172.17.0.64 /27 172.17.4.64 /27 172.17.0.96 /27 172.17.4.96 /27
DRW-1, slot-3 172.17.0.33 172.17.4.33 172.17.0.65 172.17.4.65 172.17.0.97 172.17.4.97
DRW-1, slot-4 172.17.0.34 172.17.4.34 172.17.0.66 172.17.4.66 172.17.0.98 172.17.4.98
DRW-1, Slot-5 172.17.0.35 172.17.4.35 172.17.0.67 172.17.4.67 172.17.0.99 172.17.4.99
DRW-2, slot-3 172.17.0.36 172.17.4.36 172.17.0.68 172.17.4.68 172.17.0.100 172.17.4.100
DRW-2, slot-4 172.17.0.37 172.17.4.37 172.17.0.69 172.17.4.69 172.17.0.101 172.17.4.101
DRW-2, Slot-5 172.17.0.38 172.17.4.38 172.17.0.70 172.17.4.70 172.17.0.102 172.17.4.102
DRW-3, slot-3 172.17.0.39 172.17.4.39 172.17.0.71 172.17.4.71 172.17.0.103 172.17.4.103
DRW-3, slot-4 172.17.0.40 172.17.4.40 172.17.0.72 172.17.4.72 172.17.0.104 172.17.4.104
DRW-3, Slot-5 172.17.0.41 172.17.4.41 172.17.0.73 172.17.4.73 172.17.0.105 172.17.4.105
DRW-4, slot-3 172.17.0.42 172.17.4.42 172.17.0.74 172.17.4.74 172.17.0.106 172.17.4.106
DRW-4, slot-4 172.17.0.43 172.17.4.43 172.17.0.75 172.17.4.75 172.17.0.107 172.17.4.107
DRW-4, Slot-5 172.17.0.44 172.17.4.44 172.17.0.76 172.17.4.76 172.17.0.108 172.17.4.108
DRW-5, slot-3 172.17.0.45 172.17.4.45 172.17.0.77 172.17.4.77 172.17.0.109 172.17.4.109
DRW-5, slot-4 172.17.0.46 172.17.4.46 172.17.0.78 172.17.4.78 172.17.0.110 172.17.4.110
DRW-5, Slot-5 172.17.0.47 172.17.4.47 172.17.0.79 172.17.4.79 172.17.0.111 172.17.4.111
DRW-6, slot-3 172.17.0.48 172.17.4.48 172.17.0.80 172.17.4.80 172.17.0.112 172.17.4.112
DRW-6, slot-4 172.17.0.49 172.17.4.49 172.17.0.81 172.17.4.81 172.17.0.113 172.17.4.113
DRW-6, Slot-5 172.17.0.50 172.17.4.50 172.17.0.82 172.17.4.82 172.17.0.114 172.17.4.114
DRW-7, slot-3 172.17.0.51 172.17.4.51 172.17.0.83 172.17.4.83 172.17.0.115 172.17.4.115
DRW-7, slot-4 172.17.0.52 172.17.4.52 172.17.0.84 172.17.4.84 172.17.0.116 172.17.4.116
DRW-7, Slot-5 172.17.0.53 172.17.4.53 172.17.0.85 172.17.4.85 172.17.0.117 172.17.4.117
DRW-8, slot-3 172.17.0.54 172.17.4.54 172.17.0.86 172.17.4.86 172.17.0.118 172.17.4.118
DRW-8, slot-4 172.17.0.55 172.17.4.55 172.17.0.87 172.17.4.87 172.17.0.119 172.17.4.119
DRW-8, Slot-5 172.17.0.56 172.17.4.56 172.17.0.88 172.17.4.88 172.17.0.120 172.17.4.120
Unused 172.17.0.57 172.17.4.57 172.17.0.89 172.17.4.89 172.17.0.121 172.17.4.121
Unused 172.17.0.58 172.17.4.58 172.17.0.90 172.17.4.90 172.17.0.122 172.17.4.122
Unused 172.17.0.59 172.17.4.59 172.17.0.91 172.17.4.91 172.17.0.123 172.17.4.123
Unused 172.17.0.60 172.17.4.60 172.17.0.92 172.17.4.92 172.17.0.124 172.17.4.124
Unused 172.17.0.61 172.17.4.61 172.17.0.93 172.17.4.93 172.17.0.125 172.17.4.125
Default Gateway 172.17.0.62 172.17.4.62 172.17.0.94 172.17.4.94 172.17.0.126 172.17.4.126
Broadcast 172.17.0.63 172.17.4.63 172.17.0.95 172.17.4.95 172.17.0.127 172.17.4.127
Frame-3Frame-1 Frame-2
All Rights Reserved © Alcatel-Lucent 2006, ##### 43 | Presentation Title | Month 2006
5ESS BHS IP Addressing
A BHS is a 1+1 pair of BPHs (PSU). Each BPH (1+1) pair consists of a serving and non-serving BPH
Each BPH has one 100 Mbps Ethernet link (Copper) that connects to IP Backhaul Ethernet Switch.
There are 3 IP Addresses per BPH pair – One Virtual and Two interfaces addresses for each BPH
The Virtual (Service Address) is always associated with the active BPH
– The active BPH does a gratuitous ARP to take over the Virtual IP
Address
Each BPH has one default gateway that is used for all the BTS-bound packets
All Rights Reserved © Alcatel-Lucent 2006, ##### 44 | Presentation Title | Month 2006
5ESS BHS IP Addressing
Each SM has 2 PSU2e’s (0 and 1) that each supports up to 10 pair of BHS
/26 subnet mask is recommended for each SM that supports 2 PSU2e’s with 10 BHS in PSU2e 0 and 9 BHS in PSU2e 1
The default gateway will be assigned the (Broadcast –1) and the IP Backhaul Edge Routers interface address will be assigned as (Broadcast – 2) and (Broadcast –3) respectively
All Rights Reserved © Alcatel-Lucent 2006, ##### 45 | Presentation Title | Month 2006
BTS IP Addressing
A Multi-link Group (MLG) resides between a OneBTS and the IP Backhaul Edge Router
For each URC in BTS, there will be an MLG configured on the Edge Router
An IP address is required for both sides of an MLG that is one IP address at the URC and the other on the Edge Router
During the PPP/MLPP signaling phase, the router provides itself an IP address and the static IP address to the OneBTS
All Rights Reserved © Alcatel-Lucent 2006, ##### 46 | Presentation Title | Month 2006
BTS IP Addressing
The router and the OneBTS IP address of an MLG needs to be within the same 256 address range due to gateway provisioning on the OneBTS
There are two ways to define BTS IP Addresses in the IP Backhaul Edge Router
– Static IP Address Assignment
– Dynamic IP Address Assignment
Cisco 10K Routers require /30 subnet for each URC
Juniper M40e Routers can be configured with a host address on the router and the BTS. But both routers and the BTS IP address must be in 256 address range. No requirement of /30 subnet for each URC
All Rights Reserved © Alcatel-Lucent 2006, ##### 47 | Presentation Title | Month 2006
Other IPBH IP Addressing
Management IP Addresses
– Edge Routers (Juniper M40e and Cisco 10K)
– Multi-Layer Switches (Riverstone 8860, Cisco 6509)
Routers Redundancy IP Addressing
– Redundancy Network 1 to 4 – For MLS to ER Connectivity
– Redundancy Network 5 – For MLS to MLS Connectivity
– /30 subnet required for each Redundancy Network
Loopback IP Addresses
– Edge Routers (ERs)
– Multi-Layer Switches (MLSes)
All Rights Reserved © Alcatel-Lucent 2006, ##### 48 | Presentation Title | Month 2006
VLAN Assignment
RCS-AP Frame
– No VLAN assignment needed for RCS-AP frame
5ESS BHS
– One VLAN for each
Management VLAN
– One VLAN for Edge Routers and MLS OAM connectivity
All Rights Reserved © Alcatel-Lucent 2006, ##### 49 | Presentation Title | Month 2006
IP Addressing – In Summary
/21 subnet for RCS-AP Frames
– Supports 28 AP frames. Each frame requires /27 subnet in LAN 0 and
/27 subnet in LAN 1
/26 subnet per SM
– Supports 2 PSU2e’s with 10 BHS in PSU2e 0 and 9 BHS in PSU2e 1.
Each pair of BHS requires 3 IP Addresses
/27 subnet for each BTS
– Divided into /30 for each URC. The /27 subnet can support up to 8
URCs or MLGs
All Rights Reserved © Alcatel-Lucent 2006, ##### 50 | Presentation Title | Month 2006
Data Provisioning
All Rights Reserved © Alcatel-Lucent 2006, ##### 51 | Presentation Title | Month 2006
SCM05-654_IPBH FEATURE ACTIVATION FOR INTEGRATED RCS-AP.pdf
SCM04_10_chap4_option2_BTS.doc
IPBH BHS Provisioning
All Rights Reserved © Alcatel-Lucent 2006, ##### 52 | Presentation Title | Month 2006
IPBH Acronyms
ARP – Address Resolution Protocol
BHA – Backhaul Server Association
BHM – Backhaul Manager (in ECP)
BHS – Backhaul Server
BPH – Backhaul Protocol Handler
BTS – Base Transceiver Station
CRC – CDMA Radio Controller (Modcell 1, 2, &3 interface/controller)
DACS – Digital Access and Cross Connect Systems
DCS – Digital Cellular Switch
DFI – Digital Facility Interface
DLCI – Data Link Connection Identifier
DLTU – Digital Line Trunk Unit
ECPC – Executive Cellular Processor Complex
ER – Edge Router
EVRC – Enhanced Variable Rate Codec
HSRP – Hot Standby Router Protocol
MLG – Multi-Link Group
ML-PPP – Multi-link Point-to-Point Protocol
MLS – Multi-Layer Switch
MSC- Mobile Switching Center
NMS – Network Management System
OPEX – Operations Expenses PCF
– Packet Control Function PCM –
Pulse Code Modulation PHGRP –
Protocol Handler Group PP – Packet
Pipe PPP – Point-to-
Point Protocol PSU – Packet Switch
Unit RCS – Radio Cluster
Server RSTP – Rapid Spanning
Tree Protocol RNC – Radio Network
Controller SBSP – Simple
BaseStation Startup Protocol