Lucent Technologies Proprietary Use pursuant to company instruction*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

Lucent Technologies Proprietary Use pursuant to company instruction*UMTS Network Architecture

Lucent Technologies Proprietary Use pursuant to company instruction

Lucent Technologies Proprietary Use pursuant to company instruction*UTRAN Network ArchitectureRNSRNCRNSRNCNodeBNodeBNodeBNodeBIuCS (RANAP)IuPS (RANAP)IuR(RNSAP)IuB (NBAP)IuB (NBAP)IuB (NBAP)IuB (NBAP)UTRANUu (RRC)Itf-R

Lucent Technologies Proprietary Use pursuant to company instruction

Lucent Technologies Proprietary Use pursuant to company instruction*UTRAN Network Interfaces IuPS Interface between RNC and SGSNControl plane uses RANAP protocol over SCCP signaling bearerGTP-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 MSCControl plane uses RANAP protocol over SCCP signaling bearerIu-UP protocol is used as user data bearerImplements Transport Network Control plane using ALCAP protocol IuRInterface between RNC and Peer RNCsControl plane uses RNSAP protocol over SCCP signaling bearerFraming Protocol used as user data bearer Implements Transport Network Control plane using ALCAP protocol

Lucent Technologies Proprietary Use pursuant to company instruction

Lucent Technologies Proprietary Use pursuant to company instruction*UTRAN Network Interfaces (contd) IuB Interface between RNC and Node BsControl plane uses NBAP protocol over SAAL-UNI signaling bearerFraming Protocol used as user data bearerImplements Transport Network Control plane using ALCAP protocol

Uu Logical Interface between RNC and UEsControl plane uses RRC protocol over RLC/MAC/PHYUser plane uses RLC/MAC/PHY

Itf-RInterface 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

Lucent Technologies Proprietary Use pursuant to company instruction*Flexent UMTS RNC Manage radio resourcesProcess radio signalingTerminate radio access bearersPerform call setup and teardownProcess user voice and data trafficConduct power controlPerform soft, hard and intersystem handoffsProvide OA&M capabilities

Lucent Technologies Proprietary Use pursuant to company instruction

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 OMC-U/LMT

Lucent Technologies Proprietary Use pursuant to company instruction

Lucent Technologies Proprietary Use pursuant to company instruction*Medium Configuration

Lucent Technologies Proprietary Use pursuant to company instruction

Lucent Technologies Proprietary Use pursuant to company instruction*Large Configuration

Lucent Technologies Proprietary Use pursuant to company instruction

Lucent Technologies Proprietary Use pursuant to company instruction*RNC Hardware DescriptionFor Both Configurations12 FMS blades2 FMS Blades in Slot 5 of both shelves are used for OAM purposes and are engineered as active/standby mode10 FMS blades are used for call processing and all are in active modes2 Pairs of GICC cardsGICC cards in Slot 3 of both shelves are used for IuB and IuR trafficGICC cards in Slot 20 of both shelves are used for IuCS and IuPS trafficCommon Infrastructure Cards2 Alarm cards per shelf2 ESC cards per shelfDifferencesMedium Configuration has 10 CICC cards per RNCLarge Configuration has 20 CICC cards per RNC

Lucent Technologies Proprietary Use pursuant to company instruction

Lucent Technologies Proprietary Use pursuant to company instruction*RNC Hardware - FrameCommon hardware architecture with CDMA RNCMost significant hardware is cPSB shelfExternal connections terminated in Frame Interface Panel

Dual cPSB ShelvesFrame Interface Panel Power Input TerminalsTerminal ServerPower Distribution Shelf with 2 ECBUs and Cabinet Alarm BoardCommon RNC Frame (ETSI)

Lucent Technologies Proprietary Use pursuant to company instruction

Lucent Technologies Proprietary Use pursuant to company instruction*RNC Hardware - cPSB ShelfEach 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

Lucent Technologies Proprietary Use pursuant to company instruction*cPSB OverviewPICMG 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 EthernetThe PICMG 2.16 specifications ratified September 2001 In 2003, 40 suppliers announced they were producing and shipping PICMG 2.16 compatible productsAdvantages of the specificationsCombination 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

Lucent Technologies Proprietary Use pursuant to company instruction*Flexent Blade PlatformCompact 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 BladesFlexent Mobility Server (FMS) bladeSupports BSC and OA&M functionalitySun Solaris 650 MHz UltraSPARCIIi 2.5GB RAM and 40GB Disk Common Intelligent Carrier Card (CICC)Traffic processing cardIBM 750FX 800 MHz PowerPC (3 processors)VxWorks realtime OS FMS BladeCommon ICC

Lucent Technologies Proprietary Use pursuant to company instruction

Lucent Technologies Proprietary Use pursuant to company instruction*Flexent Blade Platform (contd)Gateway ICC (GICC)Provides external network interfacesMotorola C-5 Network Processor Terminates OC-3C and EthernetMulti-Mode and Single-Mode fiber optionsGateway ICC

Lucent Technologies Proprietary Use pursuant to company instruction

Lucent Technologies Proprietary Use pursuant to company instruction*RNC Interface DescriptionATM InterfacesProvided by 2 pair of GICC cards4 OC-3c ports per GICCEach 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 trafficGICC pair in Slot 20 are used for IuCS and IuPS trafficSupport Multi-Mode and Single-Mode fibersSupport SC connectors on the ATM modules of the GICC cards

Lucent Technologies Proprietary Use pursuant to company instruction

Lucent Technologies Proprietary Use pursuant to company instruction*RNC Interface Description (contd)IP/Ethernet Interface2 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

Lucent Technologies Proprietary Use pursuant to company instruction*RNC Deployment OverviewTPU Call ProcessingTPU Call ProcessingOA&MOA&MBSCCall ProcessingBSCCall ProcessingBSCCall ProcessingBSCCall Processing

Lucent Technologies Proprietary Use pursuant to company instruction

Lucent Technologies Proprietary Use pursuant to company instruction*RNC IP Addressing Plan

Lucent Technologies Proprietary Use pursuant to company instruction

Lucent Technologies Proprietary Use pursuant to company instruction*RNC IP Addressing Plan (contd)

Lucent Technologies Proprietary Use pursuant to company instruction

Lucent Technologies Proprietary Use pursuant to company instruction*OMC-UPS Network Manager

Lucent Technologies Proprietary Use pursuant to company instruction

Lucent Technologies Proprietary Use pursuant to company instruction*OMC-UPS Network Manager (contd)

Lucent Technologies Proprietary Use pursuant to company instruction

Lucent Technologies Proprietary Use pursuant to company instruction*UMTS RNC Integration ProcessVerify completion of RNC installation servicesPerform power verification checks and power up cabinet.Verify input DC voltages to the cabinetCheck switches are on for each cPSB framePower on all circuit breakers in ECBU unitsVerify power through out the entire cabinet

Configure RNC network and check softwarePerform network configuration and software checks on CMM cards, FMS blades and ESC cards.Verify IP settings on CMM and ESC cardsPersonalize FMS blades in medium configurationCheck each FMS blade for factory installed bundlesVerify FMS blades are ready for software installation

Lucent Technologies Proprietary Use pursuant to company instruction

Lucent Technologies Proprietary Use pursuant to company instruction*UMTS RNC Integration Process (contd)Install and configure RNC initial softwarePerform software installation and activation on FMS blades.FTP the RNC software to an FMS bladeInstall and activate the RNC softwareConfigure RNC with site specific dataUpdate firmware on all the cPSB cards

Activate RNC process and boot TPUsPerform steps to activate the RNC process and bring RCC online.Verify TPUs are powered downBring RNC into ONLINE stateVerify BSC servers status on RNCBoot TPUs and check processor states

Lucent Technologies Proprietary Use pursuant to company instruction

Lucent Technologies Proprietary Use pursuant to company instruction*UMTS RNC Integration Process (contd)Integrate RNC to the Core NetworkPerform steps to integrate the RNC to the Core Network from the OMC-U console/client.Configure DHCP server on the OMC-URun CLI scripts to load network dataEstablish the Itf-R and Itf-B linksEstablish the IuCS, IuPS, IuB and IuR links

Call Through TestingPerform the following tests to verify that the following calls can originate/terminate on the RNC.Data call testsVoice call tests

Lucent Technologies Proprietary Use pursuant to company instruction

Lucent Technologies Proprietary Use pursuant to company instruction*RNC status commandstraceroute

[RNC6:fms02]-> traceroute omcu01traceroute: Warning: Multiple interfaces found; using 10.16.185.1 @ dmfe0:5traceroute 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

Lucent Technologies Proprietary Use pursuant to company instruction*RNC status commandscmmget

cmm1-1# cmmget -l blade18 -d powerstateBoard is presentBoard HEALTHY# signal is assertedBoard has been powered up by the CMMBoard is in active mode.

Lucent Technologies Proprietary Use pursuant to company instruction

Lucent Technologies Proprietary Use pursuant to company instruction*RNC status commandsiucs_pvc_dump

-giccApp: iucs_pvc_dumpelement_name=[Circuit Switched Core Network] index=[1] #pvcs=[10]Link VPI VCI State AAL Proc Pri PathRef RNC IPAddr SGSNIPAddr SubnetMask Cids 0 47 37 PVC_ACTIVE 2 GRE 2 0x0a000600 0x00000000 0x00000000 0x00000000 1 47 38 PVC_ACTIVE 2 GRE 2 0x0a000700 0x00000000 0x00000000 0x00000000 0 47 39 PVC_ACTIVE 2 GRE 2 0x0a000800 0x00000000 0x00000000 0x00000000 1 47 40 PVC_ACTIVE 2 GRE 2 0x0a000900 0x00000000 0x00000000 0x00000000

Lucent Technologies Proprietary Use pursuant to company instruction

Lucent Technologies Proprietary Use pursuant to company instruction*RNC status commandsrnccheckrns

[RNC6:fms02]-> rnccheckrns ***** RNC Initialization Status *****FMSs are all active.Active CM host is fms02Active DataBlitz host is fms02Active disk mirror is on fms02RCC VMs are all active.AMW server status:AVAILABLE: 757 UNAVAILABLE: 0 INITIALIZED: 0 RECOVERING: 0AMW 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

Lucent Technologies Proprietary Use pursuant to company instruction*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 Proprietary Use pursuant to company instruction

Lucent Technologies Proprietary Use pursuant to company instruction*Glossary3GThird Generation Wireless SystemsATMAsynchronous Transfer ModeBSCBase Station ControllerCGFCharging Gateway FunctionCICCCommon Intelligent Carrier CardCNCore NetworkETSIEuropean Telecommunication Standard InstituteGICCGateway Intelligent Carrier CardGMSCGateway Mobile Switching CenterGGSNGateway GPRS Support NodeGPRSGeneral Packet Radio ServiceGSMGlobal System for Mobile Communications

Lucent Technologies Proprietary Use pursuant to company instruction

Lucent Technologies Proprietary Use pursuant to company instruction*GlossaryHLRHome Location RegisterIMSIInternational Mobile Subscriber IdentityIPInternet ProtocolMSMobile StationMSCMobile Switching CenterNodeBIn UTRAN, NodeB is the radio transmission and reception unit.OA&MOperation, Administration & MaintenanceOMC-UOperations Management Controller - UTRANPDPPacket Data ProtocolPLMNPublic Land Mobile NetworkPSTNPublic Switched-Core NetworkRANRadio Access Network

Lucent Technologies Proprietary Use pursuant to company instruction

Lucent Technologies Proprietary Use pursuant to company instruction*GlossaryRANAPRadio Access Network Application PartRCCReliable Cluster ControlRNCRadio Network ControllerSDCSoftware Distribution CenterSGSNServing GPRS Support NodeSS7Signaling System Number SevenUEUser EquipmentUMTSUniversal Mobile Telecommunication SystemUTRANUMTS Terrestrial Radio Access NetworkVLRVisitor Location Register

Lucent Technologies Proprietary Use pursuant to company instruction

Lucent Technologies Proprietary Use pursuant to company instruction*Appendix

Lucent Technologies Proprietary Use pursuant to company instruction

Lucent Technologies Proprietary Use pursuant to company instruction*Mobile Originated Call Setup (CS)The following steps need to be executed in order for a mobile originated call to complete:RRC Connection SetupService RequestSecurity Procedures (Identity, Authentication, Security mode)Call Setup RequestRadio Link and RAB ConfigurationCall Connection

Lucent Technologies Proprietary Use pursuant to company instruction

Lucent Technologies Proprietary Use pursuant to company instruction*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 UTRANEstablish an Iu connection to the CNMake an Attach RequestCarry out Security ProceduresComplete the AttachRequest PDP Context activationSetup RABs for the connectionCreate GTP connections and activate PDP Context at the GGSNComplete Data transfer

Lucent Technologies Proprietary Use pursuant to company instruction

Lucent Technologies Proprietary Use pursuant to company instruction*Protocol Stack Circuit Switched 3GMSCRNCNode BAAMMSMMACPhy-up

PHY

codecRRCRLCMMCMMACPhy-up

PHY

RRC

MTPAAL5SSCF

Iu UP

Q2150.1ATME1AAL2SSCOPMTP3BAAL5SSCFSCCPSMMM

RANAP

Iu UP

STC.1ALCAPSTM-1AAL2SSCOPMTP3BAAL5SSCF-NNISCCPMMCMATME1

FP

AAL2STC.2SSCOPNBAPAAL5SSCF-UNI

PHY

ALCAPSSCOPNBAPAAL5SSCOPALCAPAAL5SSCFSSCF

FP

AAL2AAL2RLCMACPhy-up

RRCATME1NBAPAAL5SSCOPMTP3-bSSCF-NNISCCP

RANAP

ATMSTM-1ALCAPSTC.2SSCF-UNISSCOPIu UPMACPhy-up

FP

AAL5codecRRCRLCAAL2ALCAPSTC.1ATMcodecRLC

Lucent Technologies Proprietary Use pursuant to company instruction

Lucent Technologies Proprietary Use pursuant to company instruction*Protocol Stack Packet Switched

Lucent Technologies Proprietary Use pursuant to company instruction

Lucent Technologies Proprietary Use pursuant to company instruction*Referenceshttp://nwswww.ih.lucent.com/~philthom

Lucent Technologies Proprietary Use pursuant to company instruction

***2 CMM/AC per shelf2 ESC per shelf2 GICC per shelfUp to 6 SB per shelfUp to 10 CICC per shelf*During RNC firmware upgrade, no down time is expected. RNC still can process calls.RNC capacity/coverage: 100% capacity, 100% coverage.*During RNC firmware upgrade, no down time is expected. RNC still can process calls.RNC capacity/coverage: 100% capacity, 100% coverage.*During RNC firmware upgrade, no down time is expected. RNC still can process calls.RNC capacity/coverage: 100% capacity, 100% coverage.*During RNC firmware upgrade, no down time is expected. RNC still can process calls.RNC capacity/coverage: 100% capacity, 100% coverage.*ESC cards run active-active mode.ESC cards should be updated one at a time in the following order:esc1-2esc2-2esc2-21esc1-21Proceed to the next card only until the current card has been updated correctly.During ESC firmware update, no downtime is expected. RNC still can process calls.RNC capacity/coverage: 100% capacity, 100% coverage.*ESC cards run active-active mode.ESC cards should be updated one at a time in the following order:esc1-2esc2-2esc2-21esc1-21Proceed to the next card only until the current card has been updated correctly.During ESC firmware update, no downtime is expected. RNC still can process calls.RNC capacity/coverage: 100% capacity, 100% coverage.*ECBU looks for equipment level power faults, ECBU creates 2 separate power groups within the RNC vertical split.*ECBU looks for equipment level power faults, ECBU creates 2 separate power groups within the RNC vertical split.****During RNC firmware upgrade, no down time is expected. RNC still can process calls.RNC capacity/coverage: 100% capacity, 100% coverage.**During RNC firmware upgrade, no down time is expected. RNC still can process calls.RNC capacity/coverage: 100% capacity, 100% coverage.*During RNC firmware upgrade, no down time is expected. RNC still can process calls.RNC capacity/coverage: 100% capacity, 100% coverage.*During RNC firmware upgrade, no down time is expected. RNC still can process calls.RNC capacity/coverage: 100% capacity, 100% coverage.*During RNC firmware upgrade, no down time is expected. RNC still can process calls.RNC capacity/coverage: 100% capacity, 100% coverage.*Software download is accomplished by first ftp the gdf and bundle files from OMC-U to OAM SB and then rcp them to the rest of the SBs in parallel.Software installation is to install the packages within the downloaded bundle files. The software installation is performed 1 shelf at a time. Within each shelf, the SB installation is in parallel. After installation finished, a next link will be created if the package version in the downloaded bundles is newer than the current.During RNC preparation stage, no down time is expected. RNC still can process calls.*Software download is accomplished by first ftp the gdf and bundle files from OMC-U to OAM SB and then rcp them to the rest of the SBs in parallel.Software installation is to install the packages within the downloaded bundle files. The software installation is performed 1 shelf at a time. Within each shelf, the SB installation is in parallel. After installation finished, a next link will be created if the package version in the downloaded bundles is newer than the current.During RNC preparation stage, no down time is expected. RNC still can process calls.*Software download is accomplished by first ftp the gdf and bundle files from OMC-U to OAM SB and then rcp them to the rest of the SBs in parallel.Software installation is to install the packages within the downloaded bundle files. The software installation is performed 1 shelf at a time. Within each shelf, the SB installation is in parallel. After installation finished, a next link will be created if the package version in the downloaded bundles is newer than the current.During RNC preparation stage, no down time is expected. RNC still can process calls.*Software download is accomplished by first ftp the gdf and bundle files from OMC-U to OAM SB and then rcp them to the rest of the SBs in parallel.Software installation is to install the packages within the downloaded bundle files. The software installation is performed 1 shelf at a time. Within each shelf, the SB installation is in parallel. After installation finished, a next link will be created if the package version in the downloaded bundles is newer than the current.During RNC preparation stage, no down time is expected. RNC still can process calls.*Software download is accomplished by first ftp the gdf and bundle files from OMC-U to OAM SB and then rcp them to the rest of the SBs in parallel.Software installation is to install the packages within the downloaded bundle files. The software installation is performed 1 shelf at a time. Within each shelf, the SB installation is in parallel. After installation finished, a next link will be created if the package version in the downloaded bundles is newer than the current.During RNC preparation stage, no down time is expected. RNC still can process calls.*Software download is accomplished by first ftp the gdf and bundle files from OMC-U to OAM SB and then rcp them to the rest of the SBs in parallel.Software installation is to install the packages within the downloaded bundle files. The software installation is performed 1 shelf at a time. Within each shelf, the SB installation is in parallel. After installation finished, a next link will be created if the package version in the downloaded bundles is newer than the current.During RNC preparation stage, no down time is expected. RNC still can process calls.*Software download is accomplished by first ftp the gdf and bundle files from OMC-U to OAM SB and then rcp them to the rest of the SBs in parallel.Software installation is to install the packages within the downloaded bundle files. The software installation is performed 1 shelf at a time. Within each shelf, the SB installation is in parallel. After installation finished, a next link will be created if the package version in the downloaded bundles is newer than the current.During RNC preparation stage, no down time is expected. RNC still can process calls.*Software download is accomplished by first ftp the gdf and bundle files from OMC-U to OAM SB and then rcp them to the rest of the SBs in parallel.Software installation is to install the packages within the downloaded bundle files. The software installation is performed 1 shelf at a time. Within each shelf, the SB installation is in parallel. After installation finished, a next link will be created if the package version in the downloaded bundles is newer than the current.During RNC preparation stage, no down time is expected. RNC still can process calls.*Software download is accomplished by first ftp the gdf and bundle files from OMC-U to OAM SB and then rcp them to the rest of the SBs in parallel.Software installation is to install the packages within the downloaded bundle files. The software installation is performed 1 shelf at a time. Within each shelf, the SB installation is in parallel. After installation finished, a next link will be created if the package version in the downloaded bundles is newer than the current.During RNC preparation stage, no down time is expected. RNC still can process calls.*Software download is accomplished by first ftp the gdf and bundle files from OMC-U to OAM SB and then rcp them to the rest of the SBs in parallel.Software installation is to install the packages within the downloaded bundle files. The software installation is performed 1 shelf at a time. Within each shelf, the SB installation is in parallel. After installation finished, a next link will be created if the package version in the downloaded bundles is newer than the current.During RNC preparation stage, no down time is expected. RNC still can process calls.*Software download is accomplished by first ftp the gdf and bundle files from OMC-U to OAM SB and then rcp them to the rest of the SBs in parallel.Software installation is to install the packages within the downloaded bundle files. The software installation is performed 1 shelf at a time. Within each shelf, the SB installation is in parallel. After installation finished, a next link will be created if the package version in the downloaded bundles is newer than the current.During RNC preparation stage, no down time is expected. RNC still can process calls.***