NODE-B connectivity

Table of Content
1. 2. 3. 4. 5. 6. 7. 8. 9. Reliance 3G Network Architecture RNC Card Configuration RNC NODEB connectivity Management flow from Node-B to RNC Service & Signaling Flow NodeB to RNC QOS Bandwidth required for Iub Details conclusion of IUB interface 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

12

16

20

26

32

RCB GIPI3 GIPI3(OMCB)

SDTI

12 3 2 2

16 4 2 4

22 5 2 4

26 6 2 4

30 7 2 4

34 9 2 4

Proprietary Confidential

Card Configuration in Type -2

#1 i e Fo tBad Cb t r n or an
PR WD
1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 11 1 1 1 1 1 1 1

FN A

G G I I P P I I 1 1 S B C X R C B R C B

S D T I S B C X R C B S D T I

S D T I S B C X R C B S D T I R C B R C B

R U B

R C B

R G G G G R R U U U I I U U B I I P P B B M M I I 1 1 R U U R R I I C I I O O C C B M M M M M M C C B B
FN A

R U B

R U B

T H U B R C B R U B

T H U B R C B R U B

R C B

G G I I P P I I 1 1

R U U C I I B M M C C G G U U I I M M
FN A

R C B R U B

R C B R U B

R C B R U B

R C B R U B

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

OMCB gatewayGIPI1 1.1 .11 1 1 .1 1/11 IUB OMCB interface IP router OMCB interface IP GIPI1 1.1 .1 1 VLAN 1 11 .1 /1 11 .1 /1 1.1 .1 1VLAN 1 NodeB OMCB management gateway IP 11 .1 / 1 1.1 .1 1VLAN 1
MAN-Router MCN- Router BN-L1Switch BN-L1switch -

OMCB management IP RPU 1.1 .1/1 1 .1 1 1

BAN- Router MAN MCN- Router BN-L1Switch BN-L1Switch Node-B MAN-Router

OMCB server IP SBCX 1.1 .11 1 1 .1 1/11

NodeB OMCB management IP 11 .1- /1 1.1 .1 1VLAN 1

Manage data from RNC to NodeB

DATA Source.IP Dest.IP Source.IP Dest.IP 1.1 .11 1.1 .1 1 .1 111 .1 1 .1 1 11 .1 1.1 .1 1.1 .1

Manage data from NodeB to RNC

Dest.IP Source.IP Dest.IP Source.IP DATA 1.1 .1 11 .1 1.1 .11 1.1 .1 1 .1 1 1.1 .1 1 .1 1 11 .1

IN IP OUT IP OUT 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

IP IN IP

IP IN 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:NodeB DHCP client

OMCB server 1 .1 .11 1 .1 1

Management process

DHCP process

Proprietary Confidential

5. Service & Signaling Flow NodeB to RNC

RNC service IP 1 1 .1 1 1 1.1 .1/1 IUB signaling /service interface IP router IUB signaling /service 1.1 .1 1VLAN 1 NodeB service gateway IP GIPI1 1.1 .1 1 VLAN1 interface IP 1 1 .1 / 1 1 1 .1 /1 1 1 .1 /1 1.1 .1 1VLAN 1
MAN -Router MCN Router BN-L1 -Switch BN-L1 -switch

BAN Router MAN MCN Router BN-L1Switch BN-L1 -Switch Node -B MAN -Router

RNC SCTP IP 1 1 .1 1 1 1.1 .1/1

NodeB service and signaling IP 1 1 .1 /1 1.1 .1 1VLAN 1

-

Signaling Data from RNC to NodeB

DATA Source ..IP 11 .1 1 1.1 .1 Dest.IP 11 .1 1.1 .1

Signaling Data from NodeB to RNC

Dest.IP 11 .1 1 1.1 .1 Source.IP 11 .1 1.1 .1 DATA

Service Data from RNC to NodeB

DATA Source ..IP 11 .1 1 1.1 .1 Dest.IP 11 .1 1.1 .1

Service Data from NodeB to RNC

Dest.IP 11 .1 1 1.1 .1 Source.IP 11 .1 1.1 .1 DATA

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 dont 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) Signalling (RANAP) Conversational Streaming Interactive Background SLA BFD Traffic Type(Iub Interface QOS default) Iub NBAP Signaling[1] Iub Common Transport Channel[1] RRC Connection[2] R99 Conversational[2] R99 Streaming[2] R99 Interactive[2] R99 Background[2] HSPA Conversational[2] HSPA Streaming[2] HSPA Interactive[2] HSPA Background[2] O&M[3] Clock over IP (PTP) [3]
[3]

DSCP (Bit) 101110 100100 100100 010100 000000 000000 000000 DSCP (Bit) 101110 101110 100100 100100 100100 010100 000000 100110 100110 010110 000000 000000 101110 000000 000000

IP TOS 0xB8 0x90 0x90 0x50 0x00 0x00 0x00 IP TOS 0xB8 0xB8 0x90 0x90 0x90 0x50 0x00 0x98 0x98 0x58 0x00 0x00 0xB8 0x00 0x00

Remark EF(Expedited Forwarding) AF42(Class4, Med Drop) AF42(Class4, Med Drop) AF22(Class2, Med Drop) Best effort Best effort Best effort Remark EF(Expedited Forwarding) EF(Expedited Forwarding) AF42(Class4, Med Drop) AF42(Class4, Med Drop) AF42(Class4, Med Drop) AF22(Class2, Med Drop) Best effort AF43(Class4, High Drop) AF43(Class4, High Drop) AF23(Class2, High Drop) Best effort Best effort EF(Expedited Forwarding) Best effort Best effort

BFD [3] DSCP to COS value 0~7 8~15 16~23 24~31 32~39 40~47 48~55 56~63

0 1 2 3 4 5 6 7

Proprietary Confidential

7. Bandwidth Requirement for IU interface

1.

Bandwidth Requirement for Iub interface :Version Bandwidth(Mbps) per Cell Peak HSPA HSPA+ 64QAM HSPA+ MIMO 14.4 21.6 28.8 Average 8 13 14 Bandwidth(Mbps) per Site Peak 43 65 86 Average 24 39 42 1 FE 1 FE 1 FE Interface

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