ZTE NODE-B Connectivity

NODE-B connectivity

Table of Content

1. Reliance 3G Network Architecture

2. RNC Card Configuration

3. RNC –NODEB connectivity

4. Management flow from Node-B to RNC

5. Service & Signaling Flow NodeB to RNC

6. QOS

7. Bandwidth required for Iub

8. Details conclusion of IUB interface

9. IP Requirement Format

Proprietary Confidential ▲

1. Reliance 3G Network Architecture


2. RNC CARD CONFIGURATION

ZTE is supplying Type-2 Model of RNC to Reliance

Type-1 Type-2 Type-3 Type-4 Type-5 Type-6

RUB

8 12 16 20 26 32

RCB12 16 22 26 30 34

GIPI33 4 5 6 7 9

GIPI3(OMCB)2 2 2 2 2 2

SDTI 2 4 4 4 4 4


Card Configuration in Type -2

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17

GIPI3

GIPI3

SDTI

SDTI

RUB

RUB

GUI

M

GUI

M

GIPI3

GIPI3

RUB

RUB

RUB

RUB

SBCX

SBCX

SBCX

RCB

RCB

UI

MC

UI

MC

ROMB

ROMB

ICM

ICM

THUB

THUB

RCB

RCB

RCB

RCB

RCB

RCB

RCB

RCB

UI

MC

UI

MC

RCB

RCB

RCB

RCB

RCB

RCB

GIPI3

GIPI3

SDTI

SDTI

GUI

M

GUI

M

RUB

RUB

RUB

RUB

RUB

RUB

#1 Cabinet Front BoardPWRD

FAN

FAN

FAN


3. RNC – NODEB connectivity

ZTE is supplying Type-2 Model of RNC to RelianceRNC will have total 4 GIPI3 cards in which there will be one GE ports in each card for Iub connectivity.In this way one RNC will provide 4 GE Electrical ports towards Reliance MEN network for NODE-B connectivity in load sharing mode.


Network diagram for NodeB connectivity:-

All GE ports are electrical


Single RNC Connection


3 RNC connection


4. Management Flow From NodeB to RNC

MAN- Router

MAN- Router

MAN

BN-L2- Switch BN-L2- switch

MCN- Router

MCN- Router

Node-BNode-BNode-B-- –

-

BAN- Router

--

BN-L2- SwitchBN-L2- Switch

OMCB server IP（SBCX）10.9.1.146/240

OMCB gateway（GIPI3）10.9.1.145/240

IUB OMCB interface IP （GIPI3）172.1.1.1/30 VLAN 1

router OMCB interface IP 172.1.1.2/30 VLAN 1

NodeB OMCB management IP 172.1.3.1/30 VLAN 3

NodeB OMCB management gateway IP 172.1.3.2/30 VLAN 3

OMCB management IP （RPU）10.9.1.63/32

-

-

Dest.IP172.1.3.1

Source.IP10.9.1.63

Source.IP10.9.1.146

DATA Dest.IP172.1.3.1

Manage data from RNC to NodeB-

-

Source.IP172.1.3.1

Dest.IP10.9.1.63

Dest.IP10.9.1.146

DATASource.IP172.1.3.1

Manage data from NodeB to RNC

IP IN IP

OUT IPIN IP IN IPOUT IP

IP IN IP

1、We need all the switch or router in the transmission network support DHCP 2、We need you provide OMCB management IP


MANAGEMENT FLOW DETAIL:- When some data is sent from OMCB server then it has NODEB

Management IP as destination IP and OMCB server IP as source IP.

This data packet comes to GIPI3 card which is used for OMCB channel gateway. Then it is transferred to GIPI3 card which is used for Iub interface, during this time again IP encapsulation is done, OMCB Management IP defined in RPU will be added as source IP and NodeB management IP will be added as destination IP.

When it reaches to NODE-B then decapsulation starts and first OMCB management IP is decapsulated and then OMCB server IP will be decapsulated.

Here at RNC end we define the static route as:-

Destination IP = NODEB management IP

MASK = depend on subnets

Next hope = router OMCB port IP ( VLAN1 IP = IUB OMCB interface IP).


DHCP and Management Process:-

NodeB（DHCP client）

OMCB server（10.9.1.146）

DH

CP

pro

cess

Man

agem

ent p

roce

ss


5. Service & Signaling Flow NodeB to RNC

MAN- Router

MAN- Router

MAN

BN-L2- Switch BN-L2- switch

MCN- Router

MCN- Router

Node-BNode-BNode-B-- –

-

BAN- Router

--

BN-L2- SwitchBN-L2- Switch

RNC SCTP IP172.1.1.32/32

RNC service IP172.1.1.96/32

IUB signaling/service interface IP （GIPI3）172.1.2.1/30 VLAN 2

router IUB signaling/service interface IP 172.1.2.2/30 VLAN 2

NodeB service and signaling IP 172.1.4.1/30 VLAN 4

NodeB service gateway IP 172.1.4.2/30 VLAN 4

-

-

Dest.IP172.1.4.1

Source..IP172.1.1.32

DATA

Signaling Data from RNC to NodeB-

Source.IP172.1.4.1

Dest.IP172.1.1.32 DATA

Signaling Data from NodeB to RNC

--

-

-

Dest.IP172.1.4.1

Source..IP172.1.1.96

Service Data from RNC to NodeB-

Source.IP172.1.4.1

Dest.IP172.1.1.96 DATA

Service Data from NodeB to RNC

DATA


SERVICE AND SIGNALING FLOW DETAIL:- SIGNAL FLOW:- When some signal data is sent from RNC then it has NODE-B SIGNAL IP as destination

IP and RNC SCTP IP as source IP. This data packet comes to GIPI3 card which is used for Iub connection. And we create

static route in RNC as. Here at RNC end we define the static route as:- Destination IP = NODEB signal IP MASK = depend on subnets Next hope = router Iub port IP.(VLAN2 IP = IUB signal interface IP) SERVICE FLOW:- When some signal data is sent from RNC then it has NODE-B SERVICE IP as

destination IP and RNC USER PLANE IP as source IP. This data packet comes to GIPI3 card which is used for Iub connection. And we create

static route in RNC as. Here at RNC end we define the static route as:- Destination IP = NODEB signal IP MASK = depend on subnets Next hope = router Iub port IP.(VLAN2 IP = IUB service interface IP)

NOTE :- NODE-B service IP and NODE-B signal IP is same. We don’t separate sevice and signal layer for IUB, so at RNC side IUB service interface

IP and signal interface IP are the same. We just separate the NODE-B management layer and service/signal layer .


6. QOS Management

For the signaling QoS: NodeB site can configure signaling QoS itself.

For the service QoS:RNC send the service DSCP in the signaling trace ( NBAP messages)


DSCP bits for different services:-

Traffic Type(IU interface QOS default) DSCP (Bit) IP TOS RemarkSignalling (RANAP) 101110 0xB8 EF(Expedited Forwarding)Conversational 100100 0x90 AF42(Class4, Med Drop)Streaming 100100 0x90 AF42(Class4, Med Drop)Interactive 010100 0x50 AF22(Class2, Med Drop)Background 000000 0x00 Best effortSLA 000000 0x00 Best effortBFD 000000 0x00 Best effort

Traffic Type(Iub Interface QOS default) DSCP (Bit) IP TOS RemarkIub NBAP Signaling[1] 101110 0xB8 EF(Expedited Forwarding)Iub Common Transport Channel[1] 101110 0xB8 EF(Expedited Forwarding)RRC Connection[2] 100100 0x90 AF42(Class4, Med Drop)R99 Conversational[2] 100100 0x90 AF42(Class4, Med Drop)R99 Streaming[2] 100100 0x90 AF42(Class4, Med Drop)R99 Interactive[2] 010100 0x50 AF22(Class2, Med Drop)R99 Background[2] 000000 0x00 Best effortHSPA Conversational[2] 100110 0x98 AF43(Class4, High Drop)HSPA Streaming[2] 100110 0x98 AF43(Class4, High Drop)HSPA Interactive[2] 010110 0x58 AF23(Class2, High Drop)HSPA Background[2] 000000 0x00 Best effortO&M[3] 000000 0x00 Best effortClock over IP (PTP) [3] 101110 0xB8 EF(Expedited Forwarding)[3] 000000 0x00 Best effortBFD [3] 000000 0x00 Best effort

DSCP to COS value0~7 08~15 116~23 224~31 332~39 440~47 548~55 656~63 7


7. Bandwidth Requirement for IU interface 1. Bandwidth Requirement for Iub interface :-

Per RNC:-

a) Bandwidth Required for Iub = 2449 Mbps

VersionBandwidth(Mbps) per Cell Bandwidth(Mbps) per Site

InterfacePeak Average Peak Average

HSPA 14.4 8 43 24 1 FE

HSPA+ 64QAM 21.6 13 65 39 1 FE

HSPA+ MIMO 28.8 14 86 42 1 FE


1 、 Signal and Service layer ： RNC and NodeB don’t separate the signal and service layer ， it means each NodeB has the same signal and service IP and RNC configures the same interface IP address for IUB signal layer and service layer.But we separate the management layer.

2 、 For all NodeB that belong to same layer2 network ， NodeB has own signal/service IP 、 own vlan and own gateway in the access router

2 、 Management layer ： for all NodeB that belong to same layer2 network ， they will have same vlan and same gateway in the access router

3 、 There will be only one router for each layer2 NodeB to access 4 、 All the NodeB vlan-terminal should be done by router ， RNC

don't configure NodeB vlan 5 、 The details plan will be provided in two weeks ， including IP

、 vlan ， etc.

8. Details conclusion of IUB interface

ZTE NODE-B Connectivity

Documents

create static

signaling

omcb server

nodeb management

static route

management

iub interface

iub connection