01 IP TX Design For GUL V2.6 - 20150602

Security Level: public
IP TX Design for GUL

V2.6 VF & Huawei
2nd Jun 2015 www.huawei.com
HUAWEI TECHNOLOGIES CO., LTD.

Content
 BSC/RNC Tx Design
 IuB over IP
 IuB/Abis over IP
 LTE Tx Design
 Test Case
 3G IPSec Migration
 3G-4G Co-MPT
 E1 for 2G/3G
 Q&A
 BSC/RNC Tx Design
Redundancy Design
 The purpose of the protection is primarily to provide
redundancy, not load sharing.
 GOUc work as active and standby;
 The ports will be active and active;
 The Higher and Lower Route will be enabled on the route

as well as BSC/RNC two ports;
 Two Device IP address will be assigned for two group

NodeBs
 Control Plane and User Plane will share the same IP

address
Agreed this solution on 25th, Jun, 2012
HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 3

 BSC/RNC Tx Design (Phase I)
Phase I
 BSC/RNC ports will work as Active and Active, for Tellabs Route doesn’t support VRRP/HSRP;
 4 DEVIPs will be used for DL traffic monitoring since RAN Sharing will be enabled;
MTX
VLANID: zz1
ETH IP2:
PE1:xx.xx.xx.xx/27
zz.zz.zz.2/30 ETH IP1:
GOUc zz.zz.zz.1/30
0/22/0
DEVIP1 &3 BEP/BT NodeB/BTS
VF: Y.Y.Y.1/32
O2: Y.Y.Y.3/32 Sec GW Tellabs
GOUc
0/23/0 ETH IP5:
PE2: xx.xx.xx.xx/27 zz.zz.zz.5/30
DEVIP2 &4
VF: Y.Y.Y.2/32
O2: Y.Y.Y.4/32 ETH IP6: VLANID: zz5
zz.zz.zz.6/30
VF Huawei BSC/RNC

 BSC/RNC Tx Design (Phase II)
Phase II
 CPN will be connected with RNC directly, and also HSRP will be enabled, only 2 DEVIPs are
required ;
MTX
PE1:xx.xx.xx.xx/27
xx.xx.xx.xx/27
GOUc
0/22/1
DEVIP1 BEP/BT NodeB/BTS
VLANID: xx.xx.xx.xx/27 HSRP
VF: Y.Y.Y.1/32 xxx Sec GW Tellabs
GOUc
0/23/1
PE2: xx.xx.xx.xx/27
DEVIP2
O2: Y.Y.Y.2/32
VF Huawei BSC/RNC

 G/U/L IP Co- TX Design
Agreed Assumption
 G/U will share the Tx, and only 100Mbps is available;
 LTE will connect with Tx equipment, with 1GE available;
 1 FE/GE connection per BBU;
 IP Sec will not be available before Jan, 2013;

 Tx Connections (1 FE/GE per BBU)
308_261 & 314_261

LRFU800M
LRFU800M
LRFU800M
WRFUe2.1G
WRFUe2.1G
WRFUe2.1G
LRFU800M
LRFU800M
LRFU800M
2100M
UCIU UCIU
GTMUb GTMUb
WBBPf WBBPf
2G/3G over FE
WBBPf UMPTa1 WBBPf UMPTa1
2G/3G over FE
2100M
Tellabs
MRFU900M
MRFU900M
MRFU900M
MRFU1800M
MRFU1800M
MRFU1800M
MRFU900M
MRFU900M
MRFU900M
MRFU1800M
MRFU1800M
MRFU1800M
2100M
LBBPd LBBPd
LBBPd UMPTa2 LBBPd UMPTa2
4G over GE 4G over GE
BTS3900L BTS3900L

 Tx Connections (1 FE/GE per BBU)
306_560 & 306_261
BTS3900AL
BTS3900AL UCIU
GTMUb
GTMUb WBBPf
WBBPf WBBPf UMPTa1
2G/3G over FE
WBBPf UMPTa1
2100M
LBBPd
2G/3G over FE LBBPd UMPTa2
4G over GE
2100M
LRFU800M
LRFU800M
LRFU800M
MRFU900M
MRFU900M
MRFU900M
WRFUe2.1G
WRFUe2.1G
WRFUe2.1G
MRFU900M
MRFU900M
MRFU900M
WRFUe2.1G
WRFUe2.1G
WRFUe2.1G
MRFU1800M
MRFU1800M
MRFU1800M
2100M

 IuB over IP
Design for IuB over IP(in SRAN)

 Service and OAM are separated, the subnets are /30 and /29, respectively
 Service and OAM go through different VLAN;
 NodeB OAM IP: IP10, M2000 IP: IP 30

 NodeB Service IP: IP13, RNC IP: IP20
3G OAM Channel IP10 < -- IP12-- > IP30
3G Service Channel IP13 < -- IP14-- > IP20
It will be discarded and updated to Co-MPT, matching to new VOD
2G/3G BSC
GTMU
IP30: xx.17.29.146/27
Tellabs
WMPT IP12: xx.51.25.1/29

M2000
CPN
IP10: xx.51.25.3/29 IP11: xx.51.25.2/29
L2 network
IP13: xx.17.73.2/30
IP Backbone
IP14: xx.17.73.1/30 CPN
4G IP20: xx.17.64.1/32
Tellabs
RNC
UMPT

G/U Co-TX
 Add new IP address: IP 15, IP 16, IP17, IP18, IP21, IP22
 IP 10 change from /29 to /32; IP11 and IP12 change from /29 to /30;
 NodeB OAM IP: IP10, M2000 IP: IP30
 NodeB Service IP: IP15, RNC IP: IP20(VF) and IP22(O2)
 GSM Service & OAM IP: IP16, BSC IP: IP21;
 UMTS IP Sec Tunnel will set between UMPT(IP13) to SecGW-1(IP41), UMPT(IP11) to SecGW-1(IP42) . UMTP(IP17) to SecGW-2(IP40) will be set for GSM;
 PKI server should be the same for GSM and UMTS sites;
 Only DL(not UL) for different operators will be monitored. IP20<->IP15(bear CP of VF&O2 and UP of VF) IP22<-> IP15 (bear UP of O2)
Notes/Advantage
 GSM use dedicated VLAN ID, UMTS OAM and Service are separated by VLAN ID; 3G OAM Channel IP10 < -- IP12-- > IP30
3G Service Channel IP15 < -- IP14-- > IP20/IP22
 Smoothly upgrade from the existing IuB over IP Design to G/U Co-TX design; 2G Service&OAM Channel IP16 < -- IP18- > IP21
 Remote commissioning is difficult IP Sec
 Morecost/ resource/less technical skills required during migration;
SecGW-2
IP21: xx.xx.xx.x/32
IP40: xx.xx.xx.x/32
2G/3G UCIU BSC
GTMU
IP30: xx.17.29.146/27
IP16: YY.YY.Y.Y/32 Tellabs
WMPT-> UMPTa1 IP12: xx.51.25.1/30

IP11: xx.51.25.2/30 M2000
CPN
IP10: xx.51.25.5/32 L2 network IP42: xx.xx.xx.x/32
IP13: xx.17.73.2/30
IP15: xx.xx.xx.x/32 IP14: xx.17.73.1/30 SecGW-1
IP17: zz.zz.zz.z/30 IP Backbone
IP18: zz.zz.zz.z/30 CPN IP41: xx.xx.xx.x/32
4G IP20: xx.17.64.1/32
Tellabs
RNC IP22: xx.xx.xx.x/32
It will be discarded and updated to Co-MPT,

UMPTa2 matching to new VOD

 QoS Profile-Abis over IP
System Interf Service Type Huawei Vodafone Proposed QoS Class Mapping
ace Default
PHB DSCP DSCP PHB MPLS EXP BEP2.0 BEP 1.0 BT p-
bit
2G Abis CS speech service EF 46 46 EF 5 (SP) EF RT/EF 5

(SP2) (SP2)
Extended Signalling (ESL) CS6 48 40 AF31 3 (WFQ) AF31 AF31 3
(WFQ2=2 (WFQ)
Radio Signalling Link CS6 48 40 0)
(RSL)
Operations and Maintenance CS6 48 28 AF32 3 IC AF32 AF32 1
(OML) 1 OOC (WFQ2=2 (WFQ)
(WFQ) 0)
CS data service AF41 34 10 AF11 3 IC AF11 BE 1

1 OOC (WFQ4=4 (WRQ5=5)
PS high-priority data AF41 34 10 (WFQ) 5)
service (not used)
PS low-priority data AF31 26 10
service (1)
Extended Maintenance Link AF21 18 0 BE 0 (WFQ) BE 0
(EML) (WRQ5=5
)
Page 11
HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential
 QoS Profile-IuB over IP
System Interface Service Type Huawei Vodafone Proposed QoS Class Mapping
Default
PHB DSCP DSCP PHB MPLS EXP BEP 2.0 BEP 1.0 BT p-
bit
3G IuB AMR speech service voice EF 46 46 EF 5 (SP) EF (SP2) RT/EF 5
CS Video service voice EF 46 46 (SP2)
HSDPA speech service (plan AF41 34 46
to use)
HSUPA speech service (plan AF41 34 46
to use)
R99 CS session service: AF41 34 46
voice over R99 (not
currently used)
R99 PS session service (not AF41 34 46
currently used)
HSDPA session service (not AF41 34 46
currently used)
HSUPA session service (not AF41 34 46
currently used)
R99 CS stream service (not AF41 34 34 AF41 4 (WFQ) AF41 (SP3) AF41 4
currently used) (WFQ)
R99 PS stream service (not AF41 34 34
currently used)
HSDPA stream service (not AF41 34 34
currently used)
HSUPA stream service (not AF41 34 34
currently used)
NCP & CCP CS6 48 40 AF31 3 (WFQ) AF31 AF31 3
Common channel service EF 46 40 (WFQ2=20) (WFQ)
active

 QoS Profile-IuB over IP
System Interface Service Type Huawei Vodafone Proposed QoS Class Mapping
3G IuB Default
PHB DSCP DSCP PHB MPLS EXP BEP BEP BT p-
2.0 1.0 bit
IMS signalling (IMS EF 46 36 AF31 3 (WFQ) AF31 AF31 3

SRB) (WFQ2= (WFQ
Signalling (SRB) EF 46 36 20) )
HSDPA signalling (SRB) EF 46 36
HSDPA IMS signalling EF 46 36
(IMS SRB)
HSUPA signalling (SRB) EF 46 36
HSUPA IMS signalling EF 46 36
(IMS SRB)
R99 PS high-priority AF21 18 26 AF31 3 (WFQ) AF31 AF31 3
interactive service (WFQ2= (WFQ
HSDPA high-priority AF11 10 26 20) )
interactive service
HSUPA high-priority AF11 10 26
interactive service
OAM OM High Priority EF/4 46/3 28 AF32 3 IC AF32 AF32 1
1 4 1 OOC (WFQ2= (WFQ
(WFQ) 20) )
OM Low Priority AF31 26 0 BE 0 (WFQ) BE BE 0
(WRQ5= (WRQ
5) 5=5)

 LTE Tx Design
Content
 IP&VLAN
 QoS
 IPSec & PKI servers
 Remote Commissioning Solution
 OAM &Synchronization
 Bandwidth Calculate
 eRAN Sharing
 S1-flex
 SCTP Mult-homing
 Naming Rules
 Cooperation with a Third Part Equipment

 IP&VLAN
LTE TX Principle
 One IPSec tunnel for VDF OAM&S1, One IPSec tunnel for VDF X2, One IPSec tunnel for O2 S1&X2
 CP and UP IP address will be separated for S1 interface with different internal IP addresses
LTE IP address
 OAM internal IP: IP10.  external IP for VDF OAM&S1: IP1  Gateway IP address for VDF OAM&S1: IP2
 VDF S1 CP internal IP: IP11  external IP for VDF X2: IP3  Gateway IP address for VDF X2: IP4
 VDF S1 UP internal IP: IP12  external IP for O2 S1&X2: IP5  Gateway IP address for O2 S1&X2: IP6
 VDF X2 CP&UP internal IP:IP13
 O2 S1 CP internal IP: IP14  IPSec tunnel for VDF OAM&S1: IP1 <--> IP43  VLANID for VDF OAM&S1: VLAN 2
 O2 S1 UP internal IP: IP15  IPSec tunnel for VDF X2: IP3 <--> IP44  VLANID for VDF X2: VLAN 4
 O2 X2 CP&UP internal IP:IP16  IPSec tunnel for O2 S1&X2: IP5 <--> IP60  VLANID for O2 S1&X2: VLAN 6
4G
IP10: xx.51.25.5/32 UMPTa2 IP2: xx.51.25.1/30

IP1: xx.51.25.2/30 VLAN2 IP Backbone M2000
CPN IP43: xx.xx.xx.x
IP11: xx.xx.xx.x/32 L2 network
IP12: xx.xx.xx.x/32 IP3: xx.17.73.2/30
IP4: xx.17.73.1/30 VDF SecGW
IP13: xx.xx.xx.x/32 VLAN4
IP14: xx.xx.xx.x/32 CPN
IP5: zz.zz.zz.2/30 IP44: xx.xx.xx.x
IP15: xx.xx.xx.x/32 IP6: zz.zz.zz.1/30
VLAN6 route VDF EPC
IP16: xx.xx.xx.x/32
IP60: xx.xx.xx.x
IP Backbone
PS: At the beginning, VDF OAM&S1&X2 will go to the same SecGW, but in the future, X2 will go CPN
to a different SecGW. This is the reason why X2 use a separate IPSec tunnel O2 SecGW O2 EPC

 IP&VLAN
IP Assignment Suggestion
Although the S1-CP, S1-UP, OAM and X2 IP address is host IP address, to simple the configuration as
well as routing, here is the suggestion:
 1. The S1 IP address and X2 IP address of all the eNodeB are recommended assigned as two different
big network segment. S1-C and S1-U can be in the same network segment or different network segment;
 2. The X2 IP address of all the eNodeB can be aggregated into one network segment
VF agree the suggestion. The following is the example of IP assignment from VF;
One example on the live network: S1 CP is x.x.a.b, S1 UP is x.x.(a+4).b, OAM is x.x.(a+8).b

 QoS
QoS Recommendation for eRAN3.0(responding to SRAN7.0 recommendation)
 The high QoS service get the high priority
 Divide the OM traffic into OM-H and OM-L
Service Type DSCP DSCP VLAN Pri
QCI1 0x2E 46 5
QCI2 0x1A 26 3
QCI3 0x22 34 4
QCI4 0x1A 26 3
Userdata QCI5 0x2E 46 5
QCI6 0x12 18 2
QCI7 0x12 18 2
QCI8 0x0A 10 1
QCI9 0 0 0
SCTP 0x30 48 6
MML 0x2E 46 5
OM
FTP 0x12 18 2
synchronization 1588V2 0x2E 46 5
IKE 0x30 48 6
Ping request 0x3F 63 7
Ping respond 0 0 0
ARP Without DSCP 5
The way of change the QoS configuration

 Single VLAN+ DSCPMAP
 Use the new MML command DSCPMAP to set the mapping between all the DSCP values and P-bit

 QoS
The way of change the QoS configuration
 Single VLAN+ DSCPMAP
 Use the new MML command DSCPMAP to set the mapping between all the DSCP values and P-bit
System Service Vf DSCP PHB VF Forwarding Class MPLS EXP BEP 2.0 BEP 1.0 BT p-bit
6
48 CS6 CS6 (SP1)
N/A IP-network control (BEP 1.0, MSP) Network Control (WFQ 1%) Control, CS7 (SP1) N/A
2G/3G/4G Sync (PTP) 56 CS7 CS7(SP1)
2G/3G/4G Huawei Ping Request (ICMP) 63
2G/3G CS Voice 46
2G CS Data (WAP) 46
EF 5 EF (SP2)
4G QCI1: Conversational Voice 46 Conversational 6
(SP 80%) RT/EF (SP2)
3G Signalling (CCH, SRB, NBAP) 46 EF (SP1)
2G RAN control plane (RSL, ESL) 40 CS5
4G QCI3: Real Time Gaming 36 AF42
AF41 (SP3)
4G QCI2: Conversational Video (Live streaming) 38 AF43
4G QCI4: Non-Conversational video (buffered streaming) 34
3G R99 Streaming, Interactive and Background 34 AF41
3G HSPA Streaming 34
2G PS Data 34
2G/3G/4G O&M high priority (configuration, SNMP traps) 32 4 5
CS4 Streaming AF31 (WFQ3=20) pG, AF41 (WFQ)
3G/4G OAM Undifferentiated 32 (WFQ 8%) AF (SP2)
3G RAN Control Plane (NCP, CCP) 26
4G RAN control plane 26
AF31
2G/3G/4G RAN Transport protocols (BFD, NTP, etc.)[IKE Huawei] 26
4G QCI5: IMS Signalling (SIP packets) 26
3G HSPA Interactive 20 AF22 7 4
HSPA Interactive AF21 (WFQ2=20) G+E, AF31 (WFQ)
3G HSPA Background 22 AF23 (WFQ 5%) AF (SP2)
4G QCI6: Video (buffered streaming). 28 AF32
3
4G QCI7. UM traffic 18 AF21 Interactive AF11 (WFQ1=45) G+E, AF32 (WFQ)
(WFQ 5%)
4G QCI8. TCP-Based 10 AF11
0
4G QCI9. TCP-Based 0
BE (SP3)
2G/3G/4G O&M low priority (O&M Bulk: charging, FTP) 0 0
BE Background BE (WRQ0=5) BE (WRQ)
2G/3G/4G ICMP 0 (WFQ 1%)
2G/3G/4G IKE (Ericsson) 0

 IP Sec & PKI servers
IPSec
 Three IPSec tunnels will be established between eNodeB and SecGW, one for VF OAM&S1, one for VF X2, one for O2 S1&X2
 All the IPSec tunnels must be use the same certification;
 A pair of IP addresses per tunnel, which require both eNodeB and the SecGW provide three IPs for three IPSec tunnels
 ACL rule;
Certification
 Root Certification/Trust Certification is the same;
 Device Certification/Equipment Certification/Node Certification are the same;
4G
UMPTa2
IP1: xx.51.25.2/30 IP2: xx.51.25.1/30 IP Backbone M2000
CPN IP43: xx.xx.xx.x
L2 network
IP3: xx.17.73.2/30
CPN
IP6: zz.zz.zz.1/30
route VF EPC
IP60: xx.xx.xx.x
IP Backbone
CPN
O2 SecGW O2 EPC

 IP Sec & PKI servers
Certification deployment
 VF Root Cert., O2 Device Cert. and O2 Root Cert. will be pre-build in the O2 SecGW;
 O2 Root Cert. on Huawei MBTS will be downloaded from M2000;
 Anthentication between Huawei MBTS and VF SecGW is using VF Certifications;
 Authentication between Huawei MBTS and O2 SecGW is crossed.: MBTS send VF Device Cert., it will be checked by O2 SecGW
using VF root Cert; In the other direction, O2 SecGW send O2 Device Cert to MBTS, it will be checked via O2 Root Cert.
2 Huawei root certification

CMPV
tio n with vice VDF root certification
a de
rrtific awei
ly V DF ce ioning(hu PKI (VF)
Huawei root certification App ss
comi rtification
)
when ce
Huawei device certificton VDF device certificate
VDF device certificate VDF root certificate
VDF root certificate

O2 root certificate VF Core Network
MME/SGW/M2000
)
Cert.
2
F CMPV VDF SecGW
c (V D o n with e
IPse ertifi
cati
F dev
ic
th e VDF c ioning(VD
te is s
Upda ter comm tification)
af cer
Send V O2 SecGW
D
Reply F device Ce
O 2 de r
MBTS vice C t. O2 Core Network
ert.
O2 device certificate
O2 MME/SGW
O2 root certificate
IPsec cross VF root certificate
authentication PKI (O2)

 Remote Commissioning Solution -- part1
Huawei Solution
 eNodeB powers on (now eNodeB just has Huawei root certification and Huawei device certification which were preinstalled when
eNodeB was manufactured)
 DHCP process between eNodeB and M2000 (M2000 acts as the DHCP server) and eNodeB gets the IP/VLAN/route/SecGW/CA
information from DHCP server which is carried in DHCP message
 eNodeB applies the VDF certification with CMPV2 using Huawei device certification (until now eNodeB gets the VDF root certification
and VDF device certification)
 eNodeB establishes the IPSec with VDF SecGW using VDF certification
 OMCH for PNP is established
 Download the configuration/software from M2000
 eNodeB restarts and establishes the IPSec tunnel successfully with VDF SecGW using VDF certification
 eNodeB downloads the O2 root certification from M2000(until now eNodeB gets O2 root certification)
 eNodeB establishes the IPSec tunnel successfully with O2 SecGW using VDF certification
Requirement for the transmission network

 SecGW should allow the plaintext DHCP message to pass when commissioning
 CA can access without IPSec when commissioning

Certification Deployment
 Root certification means the certification that is issued by the CA for itself. The subject type in the certification is CA.
 Device Certification means the certification that is issued by the CA for other entities. The subject type in the certification is End Entity.
 eNodeB just can use VDF device certification for IPSec negotiation
PV2 Huawei root certification

with CM e VDF root certification
Huawei root certification ation devic
F cerrtific (huawei
Huawei device certificton VD ning PKI (VF)
Apply comissio cation)
i
VDF device certificate when certif
VDF root certificate VDF device certificate
VDF root certificate
O2 root certificate
VF Core Network
MME/SGW/M2000
)
V D FCert. with CM
PV2 VDF SecGW
(
IPsec DF certificati(VDF device
o n
V ing
te the ission
Upda ter comm tification)
af cer
Send V O2 SecGW
D
Reply F device Ce
O 2 de r
MBTS vice C t. O2 Core Network
ert.
O2 device certificate
O2 MME/SGW
O2 root certificate
IPsec cross VF root certificate
authentication PKI (O2)

VLAN Solution
 There is no VLAN information on the eNodeB before the DHCP process so eNodeB need the VLAN information
to make sure the DHCP message can go through the L2 network. 3 solution are suggested.
VLAN learning - Solution1

 M2000 sends the TCP handshake message to the eNodeB and SecGW initialize the IKE negotiation
 Requirement for network: 1) Before the IPSec tunnel establishment, SecGW can initialize the IKE negotiation
after receiving downlink data
Initiating the IKE
negotiation when receiving
the TCP SYNC
External FireWall M2000

DHCP Server (Internal DHCP
Server)
MBTS C
SeGW SYN
TC P
GW
broadcast ARP REQ IKE MME
with VLAN
External Internal
network network
SGW
HUAWEI Install
ARP Request with VLANID X IKE TCP SYNC
1. VLAN VLAN learning by ARP Requests

LEARNING ARP Request with VLANID X IKE TCP SYNC
DHCP discover with VLANID X

VLAN learning -- Solution2

 eNodeB sends DHCP message without VLAN, And the L2 access equipment add the VLAN tag
 Requirement for network: 1) L2 Access equipment add VLAN tag for eNodeB.
Configure port defaut VLAN as DHCP Server

the VLAN of the first DHCP M2000
FireWall
(Internal DHCP
Server)
MBTS SeGW C
SYN
LSW TC P
External
network X
Internal MME
HUAWEI Install network
1. VLAN SGW
VLAN learning by ARP Requests Configure Loaded
LEARNING
DHCP discover without VLAN DHCP discover with VLAN X

2. First try
witout VLAN DHCP Offer with VLANID X
DHCP Offer without VLAN

VLAN learning -- Solution3

 IP SLA monitor: VLAN monitor router sends the ICMP message to eNodeB periodic
 Requirement for network: 1) support IP SLA monitor;
External
DHCP Server
VLAN1
M2000
FireWall (Internal DHCP
GW1 VLAN Server)
monitor
SYNC
Unused IP1
Router SeGW TC P
GW2 X Internal
network
GW3
External MME
VLAN2 Unused IP2 network
SGW
VLAN3
broadcast ARP REQ with VLAN
Unicast ICMP ping
HUAWEI Install
ARP Req with VLAN X ICMP ping
1. VLAN
LEARNING ARP Req with VLAN X ICMP ping
DHCP discover with VLAN X

 OAM & Synchronization
OAM
 OAM traffic will be encrypt with IPSec tunnel
 Divide the OM traffic into OM-H and OM-L
Synchronization
 Supporting: eNodeB Support many types of synchronization, which is list below
 Requirement: Frequency accuracy should better than  0.05 ppm
 Decision: Synchronous Ethernet will be used and all the transmission equipment must support synchronous Ethernet
Notes1 : If 1588V2 selected to support phase synchronization, all the transmission equipment must support 1588V2 also;
Notes 2: If VF select 1588V2 for phase synchronization, the synchronization message cannot be encrypted.

 Bandwidth Calculate
Bandwidth calculate -- the maximal bandwidth for transmission
Suppose that the peak throughput is 116Mps and other parameters is following:
 ER: (700+12+8+70+4+18+20) /700= 1.19

 S1 user plane: 116*1.19*1( throughput*ER*Peak to Ave Ratio)= 138.04
 S1 control plane: 138.04*2%= 2.7608(supposed the bandwidth that S1 control plane needed is 2% of the S1 user
plane according to Huawei engineer experience)
 Total for S1: 138.04+2.7608= 140.8008

 Total for X2: 140.8008*3%= 4.224024 2.7608 (suppose the bandwidth that X2 needed is 3% of the S1 user plane
according to Huawei engineer experience)
 Total for S1&X2:140.8008+4.224024= 145.024
 Considering the OAM & synchronization, total requirement is 150M
Notes: use the average throughput to calculate the average transmission bandwidth and mind that the Peak to Ave Ratio is different
from this example

 eRAN Sharing
eRAN Sharing Topology
NE or Interface eNodeB CN OSS NMS S1 If-N

Sharing/Independence Sharing Sharing or Sharing Independence Sharing or Independence
Independence Independence

 S1-Flex
S1-Flex
 S1-flex on an LTE/SAE network is a feature that enables one eNodeB to set up S1-MME connections
to multiple MMEs, which form a resource pool known as an MME pool. When a UE attaches to the
network through an eNodeB, the eNodeB selects the serving MME of the UE and sets up a dedicated
S1 connection.
 VF use S1-flex for LTE

 S1-Flex
Network
 In order for all the MMEs in the MME pool to serve the MME pool area, each MME in the MME pool
must be connected to all the eNodeBs in the MME pool area. In this way, each eNodeB is connected to
all the MMEs in the MME pool.
 The physical link may require only one Ethernet cable, but the eNodeB must connect to several MMEs
in terms of logical links.
 In Beacon project, 2 MME in VF, 6 MME in TF for LTE.

 S1-Flex
Configuration
 The eNodeB must negotiate with multiple MMEs over parameters. The negotiated parameters include
MNC, MCC, and TAC,IP address of MME, port for SCTPLINK.
 The eNodeB should correctly configure the IPRT to each MME in the MME pool.
 Add the MME information with command ADD MME

ADD MME: MMEID=0, FIRSTSIGIP="1.1.1.1", LOCPORT=36412, DESCRIPTION="mme1";
ADD MME: MMEID=1, FIRSTSIGIP=“2.2.2.2", LOCPORT=36412, DESCRIPTION="mme2";
 Add S1 signal IP address

ADD S1SIGIP: SN=7, S1SIGIPID="1", LOCIP="3.3.3.3", LOCPORT=36412;

 S1-Flex
Definition of NNSF (3GPP TS23.236)
 NAS Node Selection Function (NNSF): This function allocates a suitable EPC node to provide services
for a UE and routes the following data of the UE to the node.

 S1-Flex
NNSF (3GPP TS23.236)
 In S1-flex, the eNodeB must implement the NNSU function using the following techniques:
 1. MME pool selection: eNodeBs in overlaps between MME pool areas select one MME pool based on
the topology.
 2. MME selection within the MME pool is based on the load configurations of MMEs, balancing the load
among the MMEs and effectively using the processing capabilities.
 3. Load rebalancing among MMEs: Load rebalancing is achieved among MMEs by transferring the UE
contexts registered with one MME to other MMEs in the same MME pool.
 4. MME overload processing: When an MME is overloaded, it sends the Overload Start message to the
eNodeB, instructing the eNodeB to take measures, for example, rejecting non-emergency calls initiated
by UEs or rejecting signaling initiated by UEs.

 SCTP Multi-homing
SCTP Multi-homing
 O2 will use this feature, but VF does not;
 With this feature, there are two SCTP links between one eNodeB and one MME, one is primary, one is backup. Once
detecting the primary path disconnected, eNodeB would switch to backup path if the status of backup path is OK. If the
primary one recovers then eNodeB can switch back
 Heartbeat detection provided by SCTP is used to check the connectivity of the path when the link is idle; When the link
is busy, that is, carrying services, the number of consecutive packet retransmissions is used to check the connectivity of
the path.
 eNodeB can use one S1 signal IP address to establish two SCTP links with two MME IP addresses so O2 can use one
S1-C IP address and two MME IP addresses for SCTP multi-homing ;
First IP address
First IP address
Second IP address
eNodeB MME
 Naming Rules
1. Customer requirement
2. Restriction in Huawei system Huawei recommends Naming Rules:
3. Unique on the network. 1. eNodeB: location name+eNodeB type
2. CELL : eNodeB name+CellID
4. Easy to use and understand
eNodeB Name eNodeB ID eNodeB Cell Name Cell ID

Aleksandrow_DBS3900_1_Cell1 1
Aleksandrow_DBS3900_1 1
Aleksandrow_DBS3900_1_Cell2 2
Aleksandrow_DBS3900_2 2
Beacon Project Naming Rules

1. eNodeB: V + [JVCO ID]+ H+ [VF ID]
2. Cell ID=1,2,3,4,5,6 for VF, 7,8,9 for TF

Cooperation with the EPC/SecGW/transmission network

 EPC: MME&SGW IP, SCTP port, relative parameters abut SCTP, such as RTO min/max/initial value and so on
 SecGW
Description Huawei support
Phase 1 (IKE Policy)
IKE Version IKEv2/IKEv1
ISAKMP lifeteime 60 to 604800 sec
Encryption DES, 3DES, AES128, AES192, AES2
Hash-Algorithm MD5, SHA1, AES_XCBC_96(all the authentication algorithm,not just Hash)
Authentication RSA 2048 bits,1024bits
Key Exchange DH 14 (2048 bits), DH 15(3072 bits),DH 2(1024 bits),DH 1(728 bits)
Phase 2 (IPsec Parameters)
SA Lifetime 30 to 604800 seconds
Volume Limit 0,1843200~4294967295KB
encapsulation mode tunnel, transport
protocol ESP,AH,AH_ESP
Encryption DES, 3DES, AES128, AES192, AES256
MD5, SHA1, AES-XCBC-MAC-96, SHA256(all the authentication algorithm,not just
Hash Algorithm
Hash)
IPSec PFS PRF_GROUP1,PRF_GROUP2
Notes
 During Remote Commissioning, the PFS must be disable
 During Remote Commissioning, the IDTYPE must be FQDN

Cooperation with the EPC/SecGW/transmission network
 Transmission network: MTU, bandwidth/duplex, it’s 1 Gbps, and FULL,
MTU: 1500
 The QoS requirement for transmission network is following. Huawei recommend the best QoS
Type Delay Jitter Packet Error Loss Rate
S1 interface Best 5ms 2ms 0.0001%
Recommended 10ms 4ms 0.001%
Tolerable 20ms 8ms 0.5%
X2 interface Best 10ms 4ms 0.0001%
Recommended 20ms 7ms 0.001%
Tolerable 40ms 10ms 0.5%

 Test Case & 3G IPSec Migration
Test Case
 Basic part
 Customized part for two PKI solution
3G IPSec Migration
 Design change
Current BSC/RNC IP connectivity redundancy design with Tellabs is load sharing (GOUc board: Active and Standby, Ports:
Active and Active), when migrated to CPN, it will use VRRP(GOUc board: Active and Standby, Ports: Active and Standby)
 Configuration change
IP/QoS/route/IPSec

 2G-3G-4G Co-MPT
Design of purpose
 2G-3G-4G Co-MPT is not designed yet in VF UK. 3G-4G Co-MPT is used for Lampsite non-RAN Sharing (on 2nd Feb,15)
 2G/3G co-MPT, 2G/4G Co-MPT, 3G/4G Co-MPT is designed for Beacon version 2(matching to new VOD)
 Overview is list below
GBTS NE: BTS3900 GSM NodeB NE： BTS3900 WCDMA eNodeB NE：BTS3900 LTE
RAT-G
RAT-U
RAT-L
COMM GSM COMM
COMM
GTMU UMPT/ LMTP

UMPT/ WMTP
Co-MPT NE: BTS3900
RAT-L
RAT-G
RAT-U
RAT：Radio Access Technology

COMM
MPT：Main Processing & Transmission
UMPT
Unit
 NE:：Network Element
Design Test & Verification Reconstruction Implementation Acceptance
• Co-MPT function test

• Voice/Data/SMS service test after Co- • Reconstruction scheme
• Network design MPT reconstruction design • Basic acceptance
• Co-MPT function verification • Reconstruction preparation • Optional acceptance
• Script generation • Voice/Data/SMS service verification • Reconstruction
after Co-MPT reconstruction implementation

 3G-4G Co-MPT (LampSite)
3G/4G IP address
 VDF S1 CP internal IP: IP11  external IP for VDF OAM&S1: IP1  Gateway IP address for VDF OAM&S1: IP2
 VDF S1 UP internal IP: IP12  external IP for VDF X2: IP3  Gateway IP address for VDF X2: IP4 4G
 IPSec tunnel for VDF OAM&S1: IP1 <--> IP43  VLANID for VDF OAM&S1: VLAN 2
 IPSec tunnel for VDF X2: IP3 <--> IP44  VLANID for VDF X2: VLAN 4
 3G/4G OAM internal IP: IP 10
VF/O2 internal 3G service IP: IP17 External IP for VF/O2 3G Service: IP7 Gateway IP address for VF/O2 3G service: IP8
  
 VLANID for VF 3G service: VLAN8

3G
RNC
3G/4G
IP7: xx.xx.xx.2/30 IP8: xx.xx.xx.1/30 CPN

VLAN8
UBBPd6(L)
UMPTb1
UBBPd6(U) IP1: xx.51.25.2/30 IP2: xx.51.25.1/30 IP Backbone M2000
VLAN2 CPN IP43: xx.xx.xx.x
IP10: xx.51.25.5/32 L2 network
IP11: xx.xx.xx.x/32 IP3: xx.17.73.2/30
IP12: xx.xx.xx.x/32
VLAN4
IP44: xx.xx.xx.x
route
IP17: xx.xx.xx.x/32 VDF EPC
Notes
 Once IP Sec is ready for 3G, IP7 can be used to setup the IP Sec between IP7 to SecGW

 2G/3G Co-MPT (Beacon V2)
2G/3G IP address
 VDF 3G Service internal IP: IP17  external IP for VDF OAM&Service: IP7  Gateway IP address for OAM&Service: IP8
 VLANID for VDF OAM&Service: VLAN 8 3G
 2G/3G OAM internal IP: IP10
VF/O2 internal 2G service IP: IP18


2G
U2000 2G/3G OAM

3G Service
2G Service
2G/3G
CPN
RNC
UBBPd5(GU)
IP7: xx.xx.xx.2/30 IP8: xx.xx.xx.1/30
CPN
UBBPd5(U) UMPTb1 VLAN8
IP Backbone
IP10: xx.51.25.5/32
Route
IP17: xx.xx.xx.x/32
IP18: xx.xx.xx.x/32 CPN CPN
BSC
Notes
 Any 2G or 3G is planned ONE VLANID (/32 subnet ) is required, any one technology added, one /32 IP is required;
 4G always require THREE VLANID(/32 subnet), one for 4G OAM&VF S1, one for 4G VF X2, the last one for TF S1&X2
 OAM IP is /32 and always reserved for each BBU

 2G Only or 3G Only (Beacon V2)
2G/3G IP address
 VDF 3G Service internal IP: IP17  external IP for 3G OAM&Service: IP7  Gateway IP address for 3G OAM&Service: IP8
 VLANID for 3G OAM&Service: VLAN 8 3G
VF/O2 internal 2G service IP: IP18  Gateway IP address for VF/O2 2G service: IP8
  External IP for VF/O2 2G Service: IP7
 VLANID for 2G: VLAN8 2G
U2000 3G OAM
3G Service
3G
CPN
RNC
UBBPd5(U)
CPN
IP Backbone
IP10: xx.51.25.5/32
Route
IP17: xx.xx.xx.x/32
CPN
U2000 2G OAM
2G Service
2G
CPN

UBBPd6(G) UMPTb1 VLAN8
IP Backbone
IP10: xx.51.25.5/32
Route
IP18: xx.xx.xx.x/32 CPN CPN

BSC

 2G-4G Co-MPT (Beacon V2)
2G/4G IP address
 VDF X2 CP&UP internal IP:IP13  external IP for O2 S1&X2: IP5  Gateway IP address for O2 S1&X2: IP6
  
 VLANID for 2G: VLAN8

2G
BSC
2G/4G

VLAN8
UBBPd5(G)
UMPTb1
IP11: xx.xx.xx.x/32 IP3: xx.17.73.2/30
IP12: xx.xx.xx.x/32
VLAN4
VLAN6 route VDF EPC
IP15: xx.xx.xx.x/32
IP16: xx.xx.xx.x/32
IP18: xx.xx.xx.x/32 IP60: xx.xx.xx.x
IP Backbone
CPN
O2 SecGW O2 EPC

 3G-4G Co-MPT (Beacon V2)
3G/4G IP address
 VDF X2 CP&UP internal IP:IP13  external IP for O2 S1&X2: IP5  Gateway IP address for O2 S1&X2: IP6
  
 VLANID for 3G: VLAN8

3G
RNC
3G/4G

VLAN8
UBBPd5(L)
UMPTb1
IP11: xx.xx.xx.x/32 IP3: xx.17.73.2/30
IP12: xx.xx.xx.x/32
VLAN4
VLAN6 route VDF EPC
IP15: xx.xx.xx.x/32
IP16: xx.xx.xx.x/32
IP60: xx.xx.xx.x
Notes IP17: xx.xx.xx.x/32
IP Backbone
 Compared with Lampsite, add IP Sec Tunnel for O2 if RAN Sharing is required; CPN
O2 SecGW
 Maximum 18 3G cells+ 18 4G cells can be support, depends on UBBP boards O2 EPC

 Co-MPT
Requirement
 2G/3G/4G Qos setting is consistent
 2G/3G/4G clock should be consistent
 2G/3G/4G signaling setting should be consistent (SCTP link parameters)
 2G/3G/4G OAM is the same;
 NBI should be changed;

 E1 for 2G/3G
2G
 Maximum 4E1 connected to GTMUb GTMUb for 2G
3G
 Maximum 8E1 connected to UTRP3;
UTRP3 for 3G

 E1 for 2G/3G
Cascaded E1 for 2G (1)

 TS(Time Slots) split and exchanged by DXX(CP3000)
 Already used in live network, BTS3900E
Partial TS(T1~T10)
Paging System
SDH DXX CP3K

BSC
Huawei BTS-1
Cascaded E1 for 2G (2)

 TS split and exchanged by Huawei Hub site BTS-1
 Both Hub and Leaf sites to be in the program (L4L) at the same time,
Physical 1 E1, Partial TS(Dynamic)

Full TS Full TS
SDH Huawei BTS-1 MW MW Huawei BTS-2

BSC

THANK YOU

G/U Co-TX(Option 1)
 Add new IP address: IP15, IP16, IP17, IP18, IP21, IP22
 Remove IP address IP11, IP12; IP10 change from /29 to /32
 GSM Service & OAM IP: IP16, BSC IP: IP21;
 UMTS IP Sec Tunnel will set between UMPT(IP13) to SecGW-1(IP41), UMTP(IP17) to SecGW-2(IP40) will be set for GSM;
 KPI server should be the same for GSM and UMTS sites;
 Only DL(not UL) for different operators will be monitored. IP20<->IP15(bear CP of VF&O2 and UP of VF) IP22<-> IP15 (bear UP of O2)
Notes/Advantage
 GSM use dedicated VLAN ID, UMTS OAM and Service is sharing the same VLAN ID; 3G OAM Channel IP10 < -- IP14-- > IP30
 Remote commissioning is difficult IP Sec
 More cost/resource/less technical skills required during migration;
SecGW-2
IP21: xx.xx.xx.x/32
IP40: xx.xx.xx.x/32
2G/3G BSC
GTMU
IP30: xx.17.29.146/27
WMPT-> UMPT
M2000
CPN
IP10: xx.51.25.3/32 L2 network IP42: xx.xx.xx.x/32
IP13: xx.17.73.2/30
IP15: xx.xx.xx.x/32 SecGW-1
IP14: xx.17.73.1/30
IP17: zz.zz.zz.z/30 IP Backbone
IP18: zz.zz.zz.z/30 CPN IP41: xx.xx.xx.x/32
4G UCIU IP20: xx.17.64.1/32

Tellabs
UMPT

G/U Co-TX(Option 2)
 Add new IP address: IP 15, IP 16, IP17, IP18, IP21, IP22
 GSM Service & OAM IP: IP 16, BSCIP: IP21;
 UMTS IP Sec Tunnel will set between UMPT(IP13) to SecGW-1, UMTP(IP17) to Sec GW-2 will be set for GSM;
 KPI server should be the same for GSM and UMTS sites;
 Only DL(not UL) for different operators will be monitored. IP20<->IP15(bear CP of VF&O2 and UP of VF) IP 22<-> IP15 (bear UP of O2)
Notes/Advantage
 GSM use dedicated VLAN ID, UMTS OAM and Service are separated by VLAN ID; 3G OAM Channel IP10 < -- IP12-- > IP30
 Remote commissioning is possible based on the assumption: OAM is over SSL; IP Sec
 Low cost/ less resource/less technical skills required during migration;
SecGW-2
IP21: xx.xx.xx.x/32
2G/3G BSC
GTMU
IP30: 172.17.29.146/27
WMPT-> UMPT IP12: 10.51.25.1/29 SSL

M2000
CPN
IP10: 10.51.25.3/29 IP11: 10.51.25.2/29
L2 network
IP15: xx.xx.xx.x/32
IP13: 10.17.73.2/30
SecGW-1
IP14: 10.17.73.1/30 IP Backbone
IP17: zz.zz.zz.z/30 CPN
IP18: zz.zz.zz.z/30
4G UCIU IP20: 10.17.64.1/32

Tellabs
UMPT

 3G-4G Co-MPT(Option 2)
3G/4G(Co-MPT, Option 2, All go to one Tunnel)

 VDF S1 CP internal IP: IP11  external IP for VDF OAM/S1/X2/3G Service: IP1  Gateway IP address for VDF OAM/S1/X2/3GService: IP2
 VDF S1 UP internal IP: IP12  external IP for O2 S1: IP5  Gateway IP address for X2 S1: IP6
 VF 3G Service internal IP: IP17
 O2 S1 CP internal IP: IP14  IPSec tunnel for VDF OAM/S1/X2/3G Service: IP1 <--> IP43  VLANID for VDF OAM/S1/X2/3G Service: VLAN 1
 O2 S1 UP internal IP: IP15  IPSec tunnel for O2 4G: IP5 <--> IP60  VLANID for O2 4G: VLAN 5
 O2 X2 CP&UP internal IP:IP16
3G/4G OAM
 3G/4G OAM internal IP: IP 10 3G Service
U2000
4G VF service S1/X2
4G O2 Service
IP Sec Tunnel
3G/4G
CPN
RNC
UBBPd6(L)
CPN
IP Backbone
VLAN5 Route
IP11: xx.xx.xx.x/32 IP43: xx.xx.xx.x
IP5: zz.zz.zz.2/30 IP6: zz.zz.zz.1/30
VDF EPC
IP14: xx.xx.xx.x/32
IP Backbone IP60: xx.xx.xx.x
IP15: xx.xx.xx.x/32
IP16: xx.xx.xx.x/32
IP17: xx.xx.xx.x/32
CPN
O2 SecGW O2 EPC
Advantage
 Save a lot of IP address, only add /32 IP is any service to be added, i.e. adding 2G Service

01 IP TX Design For GUL V2.6 - 20150602

Uploaded by

Copyright:

Available Formats

01 IP TX Design For GUL V2.6 - 20150602

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

01 IP TX Design For GUL V2.6 - 20150602

Uploaded by

Copyright:

Available Formats

What is the redundancy design discussed in the document?

What is the redundancy design discussed in the document?

What are the different phases of the BSC/RNC Tx design discussed?

What are the different phases of the BSC/RNC Tx design discussed?

Security Level: public

IP TX Design for GUL

2nd Jun 2015 www.huawei.com

HUAWEI TECHNOLOGIES CO., LTD.

 The Higher and Lower Route will be enabled on the route

 Two Device IP address will be assigned for two group

 Control Plane and User Plane will share the same IP

Agreed this solution on 25th, Jun, 2012

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 3

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 4

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 5

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 6

308_261 & 314_261

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 7

306_560 & 306_261

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 8

Design for IuB over IP(in SRAN)

 NodeB OAM IP: IP10, M2000 IP: IP 30

WMPT IP12: xx.51.25.1/29

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 9

2G/3G UCIU BSC

WMPT-> UMPTa1 IP12: xx.51.25.1/30

It will be discarded and updated to Co-MPT,

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 10

2G Abis CS speech service EF 46 46 EF 5 (SP) EF RT/EF 5

CS data service AF41 34 10 AF11 3 IC AF11 BE 1

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 12

IMS signalling (IMS EF 46 36 AF31 3 (WFQ) AF31 AF31 3

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 13

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential

IP10: xx.51.25.5/32 UMPTa2 IP2: xx.51.25.1/30

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 15

One example on the live network: S1 CP is x.x.a.b, S1 UP is x.x.(a+4).b, OAM is x.x.(a+8).b

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 16

Service Type DSCP DSCP VLAN Pri

ARP Without DSCP 5

The way of change the QoS configuration

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 17

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 18

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 19

2 Huawei root certification

VDF root certificate

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 20

Requirement for the transmission network

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 21

PV2 Huawei root certification

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 22

VLAN learning - Solution1

External FireWall M2000

1. VLAN VLAN learning by ARP Requests

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 23

VLAN learning -- Solution2

Configure port defaut VLAN as DHCP Server

DHCP discover without VLAN DHCP discover with VLAN X