ZTE MOBILE SOLUTIONS - itu.int

1 ZTEMOBILESOLUTIONSZTE MOBILE SOLUTIONSNOVEMBER 2008 TIMUR MAMATKHODJAEVZTE CORPORATION, UZBEKISTAN1Содержание ALL IP PLATFORMM obile network reliability issuesWiMAX2 MOBILE Network Future MOBILE Network Future TrendTrendALL IP A hit tIP Access NetworkIP Access NetworkIP Core NetworkIP Core Network ALL IP makes Core Network flat ALL IP Hardware platform ALL IP Architecture ALL IP Hardware Platform IP wireless Bearer IP interface Open Architecture IP service engine Abundant IP Multimedia ServiceIP Service NetworkIP Service NetworkIP Bearer NetworkIP Bearer NetworkIP End to End IP interface Abundant IP Multimedia ServiceIP O&M NetworkIP O&M NetworkIP Intelligent TerminalIP Intelligent TerminalEnd to End IP Core based on IN terminal Abundant IP Multimedia service experience ALL IP

2 Structure O&M Network Control based on IP simplified manage3 Unified Unified AllAll IP IP PlatformPlatformN*E1 STM-1 ClockModuleMonitorPOS/GE/FEModuleUnified hardware Unified hardware structure in all NEsstructure in all NEsIMA Access ModuleATM AccessIP Access Module CrossBar switching Maximum 80 Gswitch capacityNarrowbandIP Switch NetworkMain Flexible interface: TDM/ATM/IPTDM capacityNarrowband Signaling Process ModuleN*E1/STM-1 Main Signaling Control ModuleMain Control Module/Resource ControlIWF ModuleMRM Resource ModuleVoice TranscoderModuleDigital Trunk InterfaceTDMC ircuit Switch Network 256K*256K TDM switch networkDual switch platformDual switch platformDual switch platformDual switch platform4 256K*256K TDM switch network Interworking with TDM networkppFlexible interfaceFlexible interfaceppFlexible interfaceFlexible interfaceZTE V3 ZTE V3 Platform Platform HighlightsHighlightsAll-IP Unified platform Shared common boards: Easier maintenance, reduce CAPEX Modularized structure: Easier expansion All-IP structure.

3 Smooth evolution to IMS High integration, large capacity: IP -- 80 Gbps, TDM -- 256k*256kZTE VZTE V33 PlatformPlatform Abundant interfaces, flexible networking:E1/T1/N*E1/N*T1/FE/GE/POS/STM -1 ZTE VZTE V3 3 PlatformPlatform Perfect compatibility: inter-connect with PSTN/other PLMN/Internet Multi-level redundancy: Port-level-- 1+1,N+1,load sharing; Board-level--yg1+1,N+1,load sharing; NE-level-- MGW dual-homing, Iu-Flex (MSCS pool, SGSN pool), HLR disaster tolerance, GGSN load-sharing etc. Abundant service supporting: Meet the service SolutionGeneral Parameters for V3 Unified PlatformGeneral Parameters for V3 Unified PlatformRack SpecificationsRack Specifications Weight 350kg (Full configuration) Dimension (Depth Width Height): Dimension (Depth Width Height):800mm 600mm 2000mm Four shelves can be installed in each rack.

4 Each shelf contains 17 broad TypesShelf Types Control Shelf Takes charge of the signaling processing, operation maintenance within the rack. Bkl iBCTCB ackplane is BCTC Resource Shelf Takes charge of low level interface processing, user plane processing, and other process related with PS Domain. Backplane is IP Switch Shelf Provides first IP switch platform, and uses for the extension of resource shelf. Backplane is BPSN Circuit switch shelf Provides the circuit switch6 Circuit switch shelf Provides the circuit switch platform for the system. Backplane is BCSNAll IP Solution of ZTE All IP Solution of ZTE CNCN Centralized MSCS and distributed deployment ofHLRI nternetBilling ServerApp PlatformNMSPPS/SCPIP bearMSCSMSCSGGSNGGSNA dvantages for All IPAdvantages for All IPdistributed deployment of MGWs.

5 Centralized O&M and low OPEX Large Capacity can decreaseMSCSMSCSMSCSGGSNGGSNMSC POOLSGSN&GGSN POOLIP network Large Capacity can decrease CAPEX and OPEX TFO/TrFO give the high Quality of vice and cost less CAPXMGWMGWMGWSGSNSGSNA over IPGb over IPIuCS over IPIuPS over IPSGSNof vice and cost less CAPX MSC Pool and BSC Pool means stabler structure, load sharing, less CAPEXU ifidPltff ZCOREAllIP DiBSCRNCBSCRNCIub over IPAbis over IPless CAPEX Saving transmission investment Reducing cost of equipmentsUnified Platform for Z-COREAll-IP Design IP Architecture IP Interface IP transmission7 MSCSMSCS/MSCe /MSCe MGWMGW CSCFCSCFHLRHLR/HSS/HSSBSCBSC/RNC/RNC IP- based QoS Different NEs in one rackDifferent NEs in one rackZXWN MGWZXWN MGWZXWN MSCSZXWN MSCS/SS/SSFlexibleZXWN MGWZXWN MGWZXWN MSCS/HSSZXWN MSCS/HSSZXWN SGSNZXWN SGSNZXWN GGSNZXWN GGSNZXWN SGSNZXWN SGSN/HSS/HSSZXWNR esource ShelfControl ShelfControl ShelfControl ShelfControl ShelfResource ShelfControl ShelfControl ShelfZXWN GGSNZXWN GGSNS witch ShelfResource ShelfControl ShelfControl ShelfSwitch ShelfResource

6 ShelfSwitch ShelfControl Shelf It is easy to extend by adding single boards, shelfs or Содержание ALL IP PLATFORMM obile network reliability issuesWiMAX9 Build Build a a Reliable NetworkReliable NetworkNetwork ReliabilityNetwork ReliabilityMulti-NEs redundancyBoards redundancyPorts redundancyZTE provide perfect redundancy mechanism for operator 10to ensure the reliability of the MGW Load SharingLoad SharingBSC/RNC can access several MGW at same timeMSC ServerMSC ServerOne MSCS can manage Calling load sharingMGW1 MGW1 MGW2 MGW2 MGW Calling load sharing A RNC/BSC can be connected to several MGWs, load sharing between MGWs, ldidiff tMGWb djtLocal Local networknetworkload in different MGWs can be adjust flexibility when MSCS distributes resource.

7 When one MGW is down, load fRNC/BSC ill bt tthRNCRNCBSCBSC from RNC/BSC will be sent to another MGW without affecting services. Signaling load sharing arithmeticBTSBTSNode BNode BzM3UA transferzM2UA Master/Slave11zM3UA agentMGW Dual HomingMGW Dual Homing Dual home of Mc can be used for disaster recovery. MSC Server works in Primary orMSC Server1 MSC Server1 MSC Server2 MSC Server2 PrimaryPrimaryfor for RegionRegionAASlaveSlavefor for RegionRegionAA MSC Server works in Primary or Slave mode for a specific region. A slave MSC server will take over the control of service when PrimaryPrimaryfor for RegionRegionBBSlaveSlavefor for Region Region BBheartbeatRegion Region AARegion Region AAprimary one fails, and transfer the control back when primary one recovers.

8 Region Region BB Eliminating single point of failure via dual home Same signaling point code for Region ARegion AMGW1 MGW1 MGW2 MGW2 Region BRegion BMGW3 MGW3 MGW4 MGW4both primary and slave MSC Servers. Heart-beating Link is used to dt t ttfOne MGW can be connected with One MGW can be connected with two MSC Serverstwo MSC Servers12detect status of peer Homing SolutionDual Homing Solution Networking 1+1 load sharing Configuration dataConfiguration data Statistic settingStatistic setting Configuration dataConfiguration data Statistic settingStatistic setting 1+1 Master/Slave N+1 Master/Slave Data synchronization Subs location informationSubs location information Subs dataSubs data Authenticate tripletAuthenticate triplet Subs location informationSubs location information Subs dataSubs data Authenticate tripletAuthenticate triplet y Static data synchronization Dynamic data

9 Synchronizationheartbeat Authenticate tripletAuthenticate triplet Authenticate tripletAuthenticate triplet Reduce the influence when MSCS switch happening Call holding (1~30min that can be set) Short time switch (40s~2min) CDR won t loseCall holding 1~30 minutes, most calling 13will finish by itself MSC POOL SolutionMSC POOL Solution MGW can provide NNSF and virtual MGW function, do not need BSC POOLS ynchronize the location information in real time Support multi-capability of BSC and meet the requirements of smooth evolution for wireless MSCSMcMcMSCS support multi-capability of BSCsupport virtual based on TDMzBSC based on TDM and t NNSFMGWMGWNNSFNNSFBSCN brealized by MGW NNSF support NNSF zbased on IPzBSC based on IP and support NNSFIP BSCNNSFTDMTDM IP AAAA realized by BSC NNSF support NNSF User information synchronized automatically inside MSC POOL to resolve the called problemBSCNNSFTDM BSCBSCBSCIP signalingTDM signaling14to resolve the called trafficTDM trafficHLR RedundancyHLR Redundancy Mature 1+1 mutual backup redundancyDynamic 150%iHLR 250% serviceMutual

10 Backup World widely deployment N+1 redundancy50% service50% serviceredundancyStatic dataBOSS Mature N+1 redundancyHLR 1 HLR 2 HLR 3 HLR N Mature N+1 redundancy Deploy in operators like CMCC15 HLR 3N+1 Dynamic Disaster Tolerance HLRN+1 Dynamic Disaster Tolerance HLROSSOSSID isaster tolerance HLR SMUHLRHLROMCZTE N+1 dynamic disaster tolerance HLRBOSSBOSSUIMSPBINLPOMPSMU can be laid anywhereHLRDBI nterface serverOMC serverSSSSUUSSSSSOOCCSSD isaster tolerance HLRF rontFrontSMUMPMPMPMPIMIMMPMPMPMPMPMPMPLK LKMPMPUIUISPSPININSPSPSIUSUSSMSMSPSISISI IMIMPBPBLPLPPBPBPISISIMPMPPBPIPIPI16IP SigtranZTE USPP solutionZTE USPP solution Service is processed in distributed nodes, and every nodes worksin load sharing mode.