UMTS RNC Overview and Integration
-
Upload
moncef-manai -
Category
Documents
-
view
120 -
download
4
Transcript of UMTS RNC Overview and Integration
UMTS RNC Overview and Integration
Phillip Thomas Feb 24, 2006
LWS
Lucent Technologies – ProprietaryUse pursuant to company instruction 2
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 – ProprietaryUse pursuant to company instruction 3
UMTS Network Architecture
Lucent Technologies – ProprietaryUse pursuant to company instruction 4
UTRAN Network Architecture
RNS
RNC
RNS
RNC
NodeB NodeB NodeB NodeB
IuCS (RANAP) IuPS (RANAP)
IuR(RNSAP)
IuB (NBAP) IuB (NBAP)IuB (NBAP) IuB (NBAP)
Core Network
MSC SGSN
UTRAN
Uu (RRC)
UE
Itf-R
OMC-U
Lucent Technologies – ProprietaryUse pursuant to company instruction 5
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
IuCS
– 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
IuR– 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
Lucent Technologies – ProprietaryUse pursuant to company instruction 6
UTRAN Network Interfaces (cont’d) 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 – ProprietaryUse pursuant to company instruction 7
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 – ProprietaryUse pursuant to company instruction 8
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 OMC-U/LMT
Lucent Technologies – ProprietaryUse pursuant to company instruction 9
Medium Configuration
Lucent Technologies – ProprietaryUse pursuant to company instruction 10
Large Configuration
Lucent Technologies – ProprietaryUse pursuant to company instruction 11
RNC Hardware DescriptionFor 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 – ProprietaryUse pursuant to company instruction 12
RNC Hardware - Frame
– Common hardware architecture with CDMA RNC
– Most significant hardware is cPSB shelf
– External connections terminated in Frame Interface Panel
Dual cPSB Shelves
Frame Interface Panel Power Input Terminals
Terminal Server
Power Distribution Shelf with 2 ECBUs and Cabinet Alarm Board
Common RNC Frame (ETSI)
Lucent Technologies – ProprietaryUse pursuant to company instruction 13
RNC Hardware - cPSB Shelf
Fan Tray
Alarm Card
Ethernet Switch Card
Gateway ICC Blade
Alarm Card
2 Power Supply Trays
FMS (Solaris) Blades
Common ICC Blades
Chassis AirFilter
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 – ProprietaryUse pursuant to company instruction 14
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 – ProprietaryUse pursuant to company instruction 15
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)
• Traffic processing card
• IBM 750FX 800 MHz PowerPC (3 processors)
• VxWorks realtime OS
FMS Blade
Common ICC
Lucent Technologies – ProprietaryUse pursuant to company instruction 16
Flexent® Blade Platform (cont’d)
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 – ProprietaryUse pursuant to company instruction 17
RNC Interface DescriptionATM 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 – ProprietaryUse pursuant to company instruction 18
RNC Interface Description (cont’d)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 – ProprietaryUse pursuant to company instruction 19
RNC Deployment Overview
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21
TP TP TP TP CP SP TP TP TP TP
TP TP TP TP TP TP TP TP TP TP
TP TP TP TP TP TP TP TP TP TP
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21
TP TP TP TP CP SP TP TP TP TP
TP TP TP TP TP TP TP TP TP TP
TP TP TP TP TP TP TP TP TP TP
ES
C
Ala
rm C
ards
(2)
GIC
C
FMS FMS FMS FMS
ES
C
FMS
GIC
C
FMS
Ala
rm C
ards
(2)
ES
C
GIC
C
FMS FMS FMS
ES
C
GIC
C
FMS FMSFMS
TPU Call ProcessingTPU Call Processing
TPU Call ProcessingTPU Call Processing
OA&MOA&M
OA&MOA&M
BSCCall
Processing
BSCCall
Processing
BSCCall
Processing
BSCCall
Processing
BSCCall
Processing
BSCCall
Processing
BSCCall
Processing
BSCCall
Processing
Lucent Technologies – ProprietaryUse pursuant to company instruction 20
RNC IP Addressing Plan
Lucent Technologies – ProprietaryUse pursuant to company instruction 21
RNC IP Addressing Plan (cont’d)
Lucent Technologies – ProprietaryUse pursuant to company instruction 22
OMC-UPS Network Manager
Lucent Technologies – ProprietaryUse pursuant to company instruction 23
OMC-UPS Network Manager (cont’d)
Lucent Technologies – ProprietaryUse pursuant to company instruction 24
UMTS RNC Integration ProcessVerify 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 – ProprietaryUse pursuant to company instruction 25
UMTS RNC Integration Process (cont’d)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 – ProprietaryUse pursuant to company instruction 26
UMTS RNC Integration Process (cont’d)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 – ProprietaryUse pursuant to company instruction 27
RNC status commandstraceroute
[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 – ProprietaryUse pursuant to company instruction 28
RNC status commandscmmget
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 – ProprietaryUse pursuant to company instruction 29
RNC status commandsiucs_pvc_dump
-giccApp<1-20-0>: iucs_pvc_dump
element_name=[Circuit Switched Core Network] index=[1] #pvcs=[10]
Link VPI VCI State AAL Proc Pri PathRef RNC IPAddr SGSNIPAddr Subnet
Mask Cids
0 47 37 PVC_ACTIVE 2 GRE 2 0x0a000600 0x00000000 0x00000000 0x0000
0000
1 47 38 PVC_ACTIVE 2 GRE 2 0x0a000700 0x00000000 0x00000000 0x0000
0000
0 47 39 PVC_ACTIVE 2 GRE 2 0x0a000800 0x00000000 0x00000000 0x0000
0000
1 47 40 PVC_ACTIVE 2 GRE 2 0x0a000900 0x00000000 0x00000000 0x0000
0000
…
Lucent Technologies – ProprietaryUse pursuant to company instruction 30
RNC status commandsrnccheckrns
[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 – ProprietaryUse pursuant to company instruction 31
RNC status commandsRCCcstat
[RNC6:fms02]-> RCCcstat
RCC Cluster [FLXcluster] Status
fms01 2 A - ACTIVE
fms02 3 A - ACTIVE
fms03 4 A - ACTIVE
fms04 5 L - LEAD
fms05 6 A - ACTIVE
fms06 7 A - ACTIVE
fms07 8 A - ACTIVE
fms08 9 A - ACTIVE
fms09 10 A - ACTIVE
fms10 11 A - ACTIVE
fms11 12 A - ACTIVE
fms12 13 A - ACTIVE
Lucent Technologies – ProprietaryUse pursuant to company instruction 32
Glossary3G
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 – ProprietaryUse pursuant to company instruction 33
GlossaryHLR
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 – ProprietaryUse pursuant to company instruction 34
GlossaryRANAP
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 – ProprietaryUse pursuant to company instruction 35
Appendix
Lucent Technologies – ProprietaryUse pursuant to company instruction 36
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 – ProprietaryUse pursuant to company instruction 37
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 – ProprietaryUse pursuant to company instruction 38
Protocol Stack – Circuit Switched
3GMSC3GMSC
RNCRNC
Node BNode B
AA
MM
SM
MAC
Phy-up
PHY
codec
RRC
RLC
MM
CM
MAC
Phy-up
PHY
RRC
MTP
AAL5
SSCF
Iu UPQ2150.1
ATM
E1
AAL2
SSCOP
MTP3B
AAL5
SSCF
SCCP
SM
MM
RANAP
Iu UPSTC.1
ALCAP
STM-1
AAL2
SSCOP
MTP3B
AAL5
SSCF-NNI
SCCP
MM
CM
ATM
E1
FP
AAL2
STC.2
SSCOP
NBAP
AAL5
SSCF-UNI
PHY
ALCAP
Uu IuB IuCS
SSCOP
NBAP
AAL5
SSCOP
ALCAP
AAL5
SSCF SSCF FP
AAL2 AAL2
RLC
MAC
Phy-up
RRC
ATM
E1
NBAP
AAL5
SSCOP
MTP3-b
SSCF-NNI
SCCP
RANAP
ATM
STM-1
ALCAP
STC.2
SSCF-UNI
SSCOP
Iu UP
MAC
Phy-up
FP
AAL5
codec RRC
RLC
AAL2
ALCAP
STC.1
ATM
codec
RLC
Control Plane User Plane Transport Plane Common Control Plane User Plane Transport Plane Common
Lucent Technologies – ProprietaryUse pursuant to company instruction 39
Protocol Stack – Packet Switched
Q2150.1
SGSNSGSN
RNCRNC
Node BNode B
Control Plane User Plane Transport Plane Common Control Plane User Plane Transport Plane Common
MM
SM
MAC
Phy-up
PHY
codec
RRC
RLC
PMM
SM
MAC
Phy-up
PHY
RRC
IP
PDCP
RLC
SSCOP
NBAP
AAL5
SSCOP
ALCAP
AAL5
SSCF SSCF FP
AAL2 AAL2 AAL5 AAL5
SSCF
RLC
MAC
Phy-up SCCP
FP
RRC
ATM
E1
NBAP
AAL5 AAL2
SSCOP
MTP3-b
SSCF-N
SCCP
RANAP
RRC
ATM
STM-1
GTP-U
UDP
PDCP
ALCAP
STC.2
SSCF-UNI
SSCOP
IP
RLC
MAC
Phy-up
FP
AAL5
ATM
E1
FP
AAL2
SSCOP
ALCAP
AAL5
SSCOP
NBAP
AAL5
SSCF SSCF
PHY
ATM
E1/ STM-1
AAL2 AAL5
NBAP
PHY
ALCAP
SSCOP
STC.2
SSCF-UNIFP
SSCOP
MTP3B
AAL5
SSCF
Q2150.1
Q2150.1
Iu UP
ATM
E1
AAL2
SSCOP
MTP3B
AAL5
SSCF
SCCP
SM
MM
RANAP
SSCOP
MTP3-b
SSCF-N
SCCP
PMM
SM
ATM
STM-1
AAL5
IP
GTP-U GTP-C
UDP
L1
L2
SSCOP
MTP3B
AAL5
SSCF
Q2150.1
Q2150.1
IP
GTP-C
L1
GTP-U
UDP
L2
IP
GGSNGGSN
Uu IuB IuPS Gn
Lucent Technologies – ProprietaryUse pursuant to company instruction 40
References http://nwswww.ih.lucent.com/~philthom