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

 Proprietary Confidential ▲

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

RCB 12 16 22 26 30 34

GIPI3 3 4 5 6 7 9

GIPI3(OMCB) 2 2 2 2 2 2

SDTI 2 4 4 4 4 4
 Proprietary Confidential ▲

Card Configuration in Type -2

#1
CabinetFrontBoa
rd
PWRD
1 1 1 1 1 1 1 1 11
1 1
1 1
1 1
1 1
1 1
1 1
1 1
1
F
AN
G G S S R R G G G G R R R R
I I D D U U U U I I U U U U
P P T T B B I I P P B B B B
I I I I M M I I
1 1 1 1
S S S R R U U R R I I T T
B B B C C I I O O C C H H
C C C B B M M M M M M U U
X X X C C B B B B
F
AN
R R R R R R R R U U R R R R R R
C C C C C C C C I I C C C C C C
B B B B B B B B M M B B B B B B
C C
G G S S G G R R R R R R
I I D D U U U U U U U U
P P T T I I B B B B B B
I I I I M M
1 1
F
AN
 Proprietary Confidential ▲

3. RNC – NODEB connectivity

ZTE is supplying Type-2 Model of RNC to Reliance

RNC 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.
 Proprietary Confidential ▲
Network diagram for NodeB connectivity:-

All GE ports are electrical

 Proprietary Confidential ▲

Single RNC Connection

 Proprietary Confidential ▲

3 RNC connection
 Proprietary Confidential ▲

4. Management Flow From NodeB to RNC

IUB OMCB interface IP router OMCB interface IP
）
OMCB gateway（GIPI1 （GIPI1）111.1
.1.1/1 1 VLAN 1 1 11.1.1
.1/1
1VLAN 1
NodeB OMCB management
11.1 .1
.11 1
1/11 gateway IP 1
11.1
.1 /1
.1 1VLAN 1

MAN-Router

MCN- Router
BN-L1
- Switch BN-L1
- switch

OMCB management IP （RPU）

11.1.1
.11/11 BAN- Router

MAN
MCN- Router BN-L1
- Switch
BN-L1
- Switch
OMCB server IP （SBCX） - Node-B
11.1.1.1 1 1
1/11 NodeB OMCB- management IP
MAN-Router
111.1
.1 - /1
.1 1VLAN
– 1

- -

-
Manage data from RNC to NodeB Manage data from NodeB to RNC
-
DATA Source.IP Dest.IP Source.IP Dest.IP Dest.IP Source.IP Dest.IP Source.IP
11.1
.1.111111.1.1.111.1.1.11111.1.1.1 1
1.1
.1 .11111.1.1.111
.1.1.111111.1.1.1 DATA
-
IN IP OUT IP OUT IP IN IP

IP IN IP IP IN IP
1
、We need all the switch or router in
the transmission network support DHCP
1
、We need you provide OMCB management IP
 Proprietary Confidential ▲

 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).
 Proprietary Confidential ▲

DHCP and Management Process:-

OMCB server
NodeB
（11.1.1.111
）
（DHCP client）
DHCP process
Management process
 Proprietary Confidential ▲

5. Service & Signaling Flow NodeB to RNC

IUB signaling/service interface IP router IUB signaling/service
RNC service IP .1.1.1/ 11VLAN 1 NodeB service gateway IP
（GIPI1）111 .1.1.1/11 VLAN1 interface IP 111
111
.1.1.11/11 111.1.1.1/11VLAN 1

MAN-Router

MCN- Router
BN-L1-Switch BN-L1-switch

BAN- Router

MAN
MCN- Router BN-L1- Switch
BN-L1-Switch
RNC SCTP IP - Node-B
111
.1.1.11
/11 MAN-Router NodeB service
- and signaling IP
- –
111
.1.1 .1/11VLAN 1

- -

-
Signaling Data from RNC to NodeB Signaling Data from NodeB to RNC
-
Source..IP Dest.IP Dest.IP Source.IP
DATA 111.1.1.11 111.1.1.1 DATA
111.1.1.11 111.1.1.1
-
- -

- Service Data from RNC to NodeB Service Data from NodeB to RNC
-
Source..IP Dest.IP Dest.IP Source.IP
DATA 111.1.1.11 111.1.1.1 DATA
111.1.1.11 111.1.1.1
-
 Proprietary Confidential ▲
 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.
 Proprietary Confidential ▲

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)
 Proprietary Confidential ▲
DSCP bits for different services:-

Traffic Type(IU interface QOS default) DSCP (Bit) IP TOS Remark

Signalling (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 effort
SLA 000000 0x00 Best effort
BFD 000000 0x00 Best effort
Traffic Type(Iub Interface QOS default) DSCP (Bit) IP TOS Remark
Iub 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 effort
HSPA 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 effort
O&M[3] 000000 0x00 Best effort
Clock over IP (PTP) [3] 101110 0xB8 EF(Expedited Forwarding)
[3]
000000 0x00 Best effort
BFD [3] 000000 0x00 Best effort
DSCP to COS value

0~7 0
8~15 1
16~23 2
24~31 3
32~39 4
40~47 5
48~55 6
56~63 7
 Proprietary Confidential ▲

7. Bandwidth Requirement for IU interface

1. Bandwidth Requirement for Iub interface :-
Version Bandwidth(Mbps) per Cell Bandwidth(Mbps) per Site Interface
Peak 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

 Per RNC:-
a) Bandwidth Required for Iub = 2449 Mbps
 Proprietary Confidential ▲

8. Details conclusion of IUB interface

 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.