Vous êtes sur la page 1sur 40

UMTS RNC Overview and Integration

LWS
Phillip Thomas Feb 24, 2006

Objectives
To provide a basic overview of the Flexent RNC and explain how
it fits into the UMTS Network Architecture.

To describe the Flexent RNC Hardware components and their


function.

To outline the UMTS RNC Integration process. To explain the Call Through Testing verification process.

Lucent Technologies Proprietary Use pursuant to company instruction

UMTS Network Architecture

Lucent Technologies Proprietary Use pursuant to company instruction

UTRAN Network Architecture


Core Network MSC SGSN

IuCS (RANAP)

IuPS (RANAP)

UTRAN RNS RNC IuB (NBAP) NodeB IuB (NBAP) NodeB RNS IuR (RNSAP) Itf-R RNC IuB (NBAP) NodeB OMC-U

IuB (NBAP) NodeB

Uu (RRC)

UE

Lucent Technologies Proprietary Use pursuant to company instruction

UTRAN Network Interfaces


IuPS
Interface between RNC and SGSN Control plane uses RANAP protocol over SCCP signaling bearer GTP-U protocol is used as user data bearer Near term plans to support IP in addition or instead of ATM Interface between RNC and MSC Control plane uses RANAP protocol over SCCP signaling bearer Iu-UP protocol is used as user data bearer Implements Transport Network Control plane using ALCAP protocol Interface between RNC and Peer RNCs Control plane uses RNSAP protocol over SCCP signaling bearer Framing Protocol used as user data bearer Implements Transport Network Control plane using ALCAP protocol

IuCS

IuR

Lucent Technologies Proprietary Use pursuant to company instruction

UTRAN Network Interfaces (contd)


IuB
Interface between RNC and Node Bs Control plane uses NBAP protocol over SAAL-UNI signaling bearer Framing Protocol used as user data bearer Implements Transport Network Control plane using ALCAP protocol

Uu
Logical Interface between RNC and UEs Control plane uses RRC protocol over RLC/MAC/PHY User plane uses RLC/MAC/PHY

Itf-R
Interface between RNC and OMC-U for OA&M functions

Itf-B
Interface between NodeB and OMC-U for OAM functions
Lucent Technologies Proprietary Use pursuant to company instruction

Flexent UMTS RNC


Manage radio resources Process radio signaling Terminate radio access bearers Perform call setup and teardown Process user voice and data traffic Conduct power control Perform soft, hard and intersystem handoffs Provide OA&M capabilities

Lucent Technologies Proprietary Use pursuant to company instruction

RNC Architecture Design


Single logical unit with call processing software partitioned between two major subsystems: Control plane processing handled by the Base Station Controller Traffic plane processing handled by the Traffic Processing Unit Further significant subsystem to handle OA&M interactions between RNC and OMCU/LMT

Lucent Technologies Proprietary Use pursuant to company instruction

Medium Configuration

Lucent Technologies Proprietary Use pursuant to company instruction

Large Configuration

Lucent Technologies Proprietary Use pursuant to company instruction

10

RNC Hardware Description


For Both Configurations 12 FMS blades
2 FMS Blades in Slot 5 of both shelves are used for OAM purposes and are engineered as active/standby mode 10 FMS blades are used for call processing and all are in active modes

2 Pairs of GICC cards


GICC cards in Slot 3 of both shelves are used for IuB and IuR traffic GICC cards in Slot 20 of both shelves are used for IuCS and IuPS traffic

Common Infrastructure Cards


2 Alarm cards per shelf 2 ESC cards per shelf

Differences Medium Configuration has 10 CICC cards per RNC Large Configuration has 20 CICC cards per RNC

Lucent Technologies Proprietary Use pursuant to company instruction

11

RNC Hardware - Frame


Frame Interface Panel Power Input Terminals Power Distribution Shelf with 2 ECBUs and Cabinet Alarm Board

Dual cPSB Shelves Terminal Server

Common hardware architecture with CDMA RNC Most significant hardware is cPSB shelf External connections terminated in Frame Interface Panel

Common RNC Frame (ETSI)


Lucent Technologies Proprietary Use pursuant to company instruction 12

RNC Hardware - cPSB Shelf


Fan Tray Alarm Card Ethernet Switch Card Gateway ICC Blade Alarm Card 2 Power Supply Trays Chassis Air Filter FMS (Solaris) Blades Common ICC Blades

Each cPSB shelf holds: 2 Ethernet Switch Cards 2 Alarm Cards (shelf management) in one slot 18 slots for user processing boards 2 Network Processor boards for 4+4 STM1 links (GICC Blades) 16 slots to house FMS Blades or VxWorks processors (CICC Blades)
Lucent Technologies Proprietary Use pursuant to company instruction 13

cPSB Overview
PICMG 2.16 (Compact PCI Packet Switching Backplane) is one of the newer specifications issued by the PCI Industrial Computer Manufacturers Group (PICMG) PICMG 2.16 is an extension of the PICMG 2.x family of specifications that implements a packet-based switching architecture based on Ethernet

The PICMG 2.16 specifications ratified September 2001


In 2003, 40 suppliers announced they were producing and shipping PICMG 2.16 compatible products Advantages of the specifications Combination of robustness, reliability and hot-swap capabilities of Compact PCI with the ubiquity of Ethernet providing high availability, next-generation network applications (e.g. RNC)

Lucent Technologies Proprietary Use pursuant to company instruction

14

Flexent Blade Platform


Compact PCI Packet Switching Backplane (cPSB) Industry standard specification - PCI Industrial Computer Manufacturers Group (PICMG) Combines robustness, reliability, hot-swap capabilities of Compact PCI with the ubiquity of Ethernet for high availability, next-generation network applications Processing Blades Flexent Mobility Server (FMS) blade Supports BSC and OA&M functionality Sun Solaris 650 MHz UltraSPARCIIi 2.5GB RAM and 40GB Disk Common Intelligent Carrier Card (CICC)
FMS Blade

Traffic processing card


IBM 750FX 800 MHz PowerPC (3 processors) VxWorks realtime OS
Common ICC

Lucent Technologies Proprietary Use pursuant to company instruction

15

Flexent Blade Platform (contd)


Gateway ICC (GICC) Provides external network interfaces

Motorola C-5 Network Processor


Terminates OC-3C and Ethernet Multi-Mode and Single-Mode fiber options
Gateway ICC

Lucent Technologies Proprietary Use pursuant to company instruction

16

RNC Interface Description


ATM Interfaces Provided by 2 pair of GICC cards 4 OC-3c ports per GICC Each pair of GICC cards support 1+1 APS protocol on the OC-3c interfaces. Each
pair of GICC cards have 4 Protection Groups, ie 4+4 APS protected OC-3c ports.

GICC pair in Slot 3 are used for IuB and IuR traffic GICC pair in Slot 20 are used for IuCS and IuPS traffic Support Multi-Mode and Single-Mode fibers Support SC connectors on the ATM modules of the GICC cards

Lucent Technologies Proprietary Use pursuant to company instruction

17

RNC Interface Description (contd)


IP/Ethernet Interface 2 10/100/1000 Base-TX ports from each GICC.
One 10/100/1000 Base-TX ports from each GICC in Slot 3 of both shelves are used for the Itf-R interface. Thus, the Itf-R interface connection is in active/standby mode. Other 10/100/1000 ports on the GICCs are reserved for future use.

2 10/100/1000 Base-TX front panel ports from the ESC in Slot 21 on the top shelf
and 2 10/100/1000 Base-TX front panel ports from the ESC in Slot 2 on the bottom shelf are reserved for future use.

Lucent Technologies Proprietary Use pursuant to company instruction

18

RNC Deployment Overview


1 2 3 4 5 6 7 TP 8 TP 9 TP 10 TP 11 CP 12 SP 13 TP 14 TP 15 TP 16 TP 17 18 19 20 21 FMS FMS FMS Alarm Cards (2) FMS FMS FMS

GICC

GICC 19 20 GICC

ESC

OA&M

BSC Call Processing

TP

TP

TP

TP

TP

TP

TP

TP

TP

TP

TPU Call Processing TP TP TP TP TP TP TP TP TP TP

BSC Call Processing

7 TP

8 TP

9 TP

10 TP

11 CP

12 SP

13 TP

14 TP

15 TP

16 TP

17

18

21

FMS FMS FMS


Alarm Cards (2)

FMS FMS FMS

GICC

ESC

BSC OA&M Call Processing

TP

TP

TP

TP

TP

TP

TP

TP

TP

TP

TPU Call Processing TP TP TP TP TP TP TP TP TP TP

BSC Call Processing

Lucent Technologies Proprietary Use pursuant to company instruction

ESC 19

ESC

RNC IP Addressing Plan

Lucent Technologies Proprietary Use pursuant to company instruction

20

RNC IP Addressing Plan (contd)

Lucent Technologies Proprietary Use pursuant to company instruction

21

OMC-UPS Network Manager

Lucent Technologies Proprietary Use pursuant to company instruction

22

OMC-UPS Network Manager (contd)

Lucent Technologies Proprietary Use pursuant to company instruction

23

UMTS RNC Integration Process


Verify completion of RNC installation services Perform power verification checks and power up cabinet.
Verify input DC voltages to the cabinet Check switches are on for each cPSB frame Power on all circuit breakers in ECBU units Verify power through out the entire cabinet

Configure RNC network and check software Perform network configuration and software checks on CMM cards, FMS blades
and ESC cards. Verify IP settings on CMM and ESC cards Personalize FMS blades in medium configuration Check each FMS blade for factory installed bundles

Verify FMS blades are ready for software installation

Lucent Technologies Proprietary Use pursuant to company instruction

24

UMTS RNC Integration Process (contd)


Install and configure RNC initial software Perform software installation and activation on FMS blades.
FTP the RNC software to an FMS blade Install and activate the RNC software Configure RNC with site specific data Update firmware on all the cPSB cards

Activate RNC process and boot TPUs Perform steps to activate the RNC process and bring RCC online.
Verify TPUs are powered down Bring RNC into ONLINE state Verify BSC servers status on RNC Boot TPUs and check processor states

Lucent Technologies Proprietary Use pursuant to company instruction

25

UMTS RNC Integration Process (contd)


Integrate RNC to the Core Network Perform steps to integrate the RNC to the Core Network from the OMC-U
console/client. Configure DHCP server on the OMC-U

Run CLI scripts to load network data


Establish the Itf-R and Itf-B links Establish the IuCS, IuPS, IuB and IuR links

Call Through Testing Perform the following tests to verify that the following calls can originate/terminate on
the RNC. Data call tests Voice call tests

Lucent Technologies Proprietary Use pursuant to company instruction

26

RNC status commands


traceroute
[RNC6:fms02]-> traceroute omcu01 traceroute: Warning: Multiple interfaces found; using 10.16.185.1 @ dmfe0:5 traceroute to omcu01 (10.189.18.216), 30 hops max, 40 byte packets 1 gicc-i-1-3 (10.16.185.13) 1.156 ms 0.483 ms 1.311 ms 2 * 10.16.184.2 (10.16.184.2) 1.712 ms 1.498 ms 3 10.16.105.129 (10.16.105.129) 10.609 ms 10.601 ms 15.274 ms 4 10.189.19.129 (10.189.19.129) 27.642 ms 10.640 ms *

5 omcu01 (10.189.18.216) 10.775 ms 10.750 ms 10.664 ms

Lucent Technologies Proprietary Use pursuant to company instruction

27

RNC status commands


cmmget
cmm1-1# cmmget -l blade18 -d powerstate Board is present Board HEALTHY# signal is asserted Board has been powered up by the CMM Board is in active mode.

Lucent Technologies Proprietary Use pursuant to company instruction

28

RNC status commands


iucs_pvc_dump
-giccApp<1-20-0>: iucs_pvc_dump element_name=[Circuit Switched Core Network] index=[1] #pvcs=[10] Link VPI VCI Mask Cids 0 47 37 0000 1 47 38 PVC_ACTIVE 2 GRE 2 0x0a000700 0x00000000 0x00000000 0x0000 PVC_ACTIVE 2 GRE 2 0x0a000800 0x00000000 0x00000000 0x0000 PVC_ACTIVE 2 GRE 2 0x0a000900 0x00000000 0x00000000 0x0000 PVC_ACTIVE 2 GRE 2 0x0a000600 0x00000000 0x00000000 0x0000 State AAL Proc Pri PathRef RNC IPAddr SGSNIPAddr Subnet

0000
0 47 39 0000 1 47 40 0000

Lucent Technologies Proprietary Use pursuant to company instruction

29

RNC status commands


rnccheckrns
[RNC6:fms02]-> rnccheckrns ***** RNC Initialization Status ***** FMSs are all active. Active CM host is fms02 Active DataBlitz host is fms02 Active disk mirror is on fms02 RCC VMs are all active. AMW server status: AVAILABLE: 757 UNAVAILABLE: 0 INITIALIZED: 0 RECOVERING: 0 AMW domain is completely up; all servers are AVAILABLE! RNC is completely initialized and ready! See /tmp/rnccheckrns.out for details.

Lucent Technologies Proprietary Use pursuant to company instruction

30

RNC status commands


RCCcstat
[RNC6:fms02]-> RCCcstat RCC Cluster [FLXcluster] Status fms01 fms02 fms03 fms04 fms05 fms06 fms07 fms08 fms09 fms10 fms11 fms12 2 3 4 5 6 7 8 9 10 11 12 13 A - ACTIVE A - ACTIVE A - ACTIVE L - LEAD A - ACTIVE A - ACTIVE A - ACTIVE A - ACTIVE A - ACTIVE A - ACTIVE A - ACTIVE A - ACTIVE

Lucent Technologies Proprietary Use pursuant to company instruction

31

Glossary
3G Third Generation Wireless Systems ATM Asynchronous Transfer Mode BSC Base Station Controller CGF Charging Gateway Function CICC Common Intelligent Carrier Card CN Core Network ETSI European Telecommunication Standard Institute GICC Gateway Intelligent Carrier Card GMSC Gateway Mobile Switching Center GGSN Gateway GPRS Support Node GPRS General Packet Radio Service GSM Global System for Mobile Communications

Lucent Technologies Proprietary Use pursuant to company instruction

32

Glossary
HLR Home Location Register IMSI International Mobile Subscriber Identity IP Internet Protocol MS Mobile Station MSC Mobile Switching Center NodeB In UTRAN, NodeB is the radio transmission and reception unit. OA&M Operation, Administration & Maintenance OMC-U Operations Management Controller - UTRAN PDP Packet Data Protocol PLMN Public Land Mobile Network PSTN Public Switched-Core Network RAN Radio Access Network

Lucent Technologies Proprietary Use pursuant to company instruction

33

Glossary
RANAP Radio Access Network Application Part RCC Reliable Cluster Control RNC Radio Network Controller

SDC
Software Distribution Center SGSN Serving GPRS Support Node SS7 Signaling System Number Seven UE

User Equipment
UMTS Universal Mobile Telecommunication System UTRAN UMTS Terrestrial Radio Access Network VLR Visitor Location Register

Lucent Technologies Proprietary Use pursuant to company instruction

34

Appendix

Lucent Technologies Proprietary Use pursuant to company instruction

35

Mobile Originated Call Setup (CS)


The following steps need to be executed in order for a mobile originated call to complete: RRC Connection Setup Service Request Security Procedures (Identity, Authentication, Security mode) Call Setup Request Radio Link and RAB Configuration Call Connection

Lucent Technologies Proprietary Use pursuant to company instruction

36

Mobile Originated Call Setup (PS)


The following steps need to be executed in order for a mobile originated call to complete: Establish an RRC connection to the UTRAN Establish an Iu connection to the CN Make an Attach Request Carry out Security Procedures Complete the Attach Request PDP Context activation Setup RABs for the connection Create GTP connections and activate PDP Context at the GGSN Complete Data transfer

Lucent Technologies Proprietary Use pursuant to company instruction

37

Protocol Stack Circuit Switched


Uu Node B IuB RNC IuCS 3GMSC

codec

CM SM MM MM RRC RRC

CM MM MM SM RRC RRC RLC RLC MAC MAC ALCAP AA ALCAP Phy-up Phy-up Iu UP MTP3-b FP FP SSCF-NNI SSCOP AAL2 AAL2 AAL2 ATM ATM STM-1 E1 AAL5 RANAP ALCAP STC.1 SCCP RANAP ALCAP Iu UP SCCP STC.1 SCCP Q2150.1 Iu UP MTP3B MTP3B MTP SSCF-NNI SSCF SSCF SSCOP SSCOP AAL5 AAL2 AAL5 AAL5 AAL2 ATM ATM STM-1 E1 codec

RLC codec RLC MAC MAC Phy-up Phy-up

STC.2
FP PHY PHY PHY AAL2

NBAP

NBAP STC.2 NBAP ALCAP SSCF-UNI SSCF SSCF SSCOP SSCOP SSCOP AAL5 AAL5 AAL5

SSCF-UNI SSCOP AAL5 ATM E1

Control Plane

User Plane

Transport Plane

Common

Lucent Technologies Proprietary Use pursuant to company instruction

38

Protocol Stack Packet Switched


Uu Node B IuB RNC IuPS SGSN Gn GGSN

SM SM PMM IP MM PDCP RRC RRC RLC codec RLC MAC MAC Phy-up Phy-up

SM MM PMM SM RRC PDCP RRC RLC RLC MAC MAC Phy-up Phy-up GTP-U UDP RANAP FP RANAP GTP-U GTP-C

IP Q2150. GTP-C GTP-U 1 UDP Q2150. 1 MTP3B IP

Q2150. 1 UDP

ALCAP STC.2 NBAP ALCAP NBAP FP SSCF-UNI FP SSCF SSCF SSCOP SSCOP SSCOP AAL2 AAL5 AAL2 AAL5 AAL5 ATM ATM E1/ STM-1 E1

ALCAP NBAP STC.2 NBAP ALCAP

SCCP SCCP MTP3-b IP

PHY PHY

PHY PHY

SSCF-UNI SSCF SSCF SSCOP SSCOP SSCOP


AAL5 AAL5 AAL5

FP

FP

SSCF-N SSCF SSCOP AAL5 AAL5 AAL5

AAL2 AAL2 AAL2 ATM ATM STM-1 E1

SCCP Q2150. SCCP 1 Iu UP MTP3-b MTP3B MTP3B IP SSCF-N SSCF SSCF SSCOP SSCOP SSCOP AAL5 L2 AAL5 AAL5 AAL2 ATM ATM L1 STM-1 E1

Q2150.1 SSCF
SSCOP L2 AAL5 L1

Control Plane

User Plane

Transport Plane

Common

Lucent Technologies Proprietary Use pursuant to company instruction

39

References
http://nwswww.ih.lucent.com/~philthom

Lucent Technologies Proprietary Use pursuant to company instruction

40