Presentation on theme: "Next Gen Access Architecture"— Presentation transcript:
1 Next Gen Access Architecture CCAP (CMAP) Program at ComcastSCTE 2011July, 2011
2 Why would MSOs need CCAP? Engineering: Capacity and efficiency, frees significant HE capacity50% space savings with 4x capacity60% power savings plus less coolingImprove existing UPS and battery backup performanceArchitecture: Simplicity and flexibility is already a key driverMinimum, simplified combining wiringFull-spectrum, MPEG/DOCSIS QAMs, easier migration to ADSFuture proof, single access platformPurchasing: Cost will quickly become a big driverCMTS 4-6 DOCSIS channel cost equals CCAP 16 DOCSIS + 16 MPEG Channels !!Operations: Reliability and manageability will also drive adoptionFully redundant (N+1 LC & 1+1 Commons)Configuration change between QAM types vs. equipment swap-outMuch shorter maintenance window (ISSU)Far less equipment to manage and maintain
3 CCAP space efficiency example Top view of headend rack line-upEach box represents a rackExample for illustrative purposesToday’s HE: 16 NC QAMs per SGAfter CCAP: 64 NC QAMs per SGDigital Broadcast20 QAMsOOBOOBSDV6 EQAM6EQAM4x CapacityVOD6 EQAM6EQAMCMTSCMTSCCAP1/2SpaceCombiner & AmpsRetFwdRetFwdLasers & ReceiversRetFwdRetFwdCCAP eliminates the need for headend expansionsNOTES:Deployment example assuming 40K homes passed, 200 nodes, 140 D3 HSD service groups at 16 SG/chassis, 120 VOD 6QAMs/SG and 4 QAMs/RF Port, and same SDV service groups.Larger or smaller headends would scale accordingly, but savings will be proportional.
4 CCAP yearly power savings in a typical headend DevicePre-CCAPKWH/YearPost-CCAPKWH SavingsPercentage SavedDigital Broadcast60,196100%SDV140,160VODCMTS->CCAP277,984227,76050,22418%Combine/Amp5,6763,7841,89233%Lasers/ReceiversNATotal624,176231,544392,63263%CCAP saves 60% of power, not including cooling energy savings!UPS and battery requirements are also reduced – existing capacity will last considerably longer when power is interrupted.
5 CCAP in a nutshell CCAP DS RF Port Modular CCAP Integrated CCAP Converged Cable Access PlatformCombines the functions of the CMTS and Edge QAMImplements all narrowcast and broadcast QAMsCCAP in a nutshellCCAP DS Port AssignmentsHSD CDVSimplify, and eventually eliminate RF CombiningDOCSISDS RF PortAVSVOD nDVRSDV32/48/64 NC QAMs BC QAMsMPEG TSBroadcastNarrowcast & Broadcast Digital ServicesModular CCAPIntegrated CCAPCCAPLegacy OOBAnalogUSDSSplitLegacy OOB
6 Operational features of CCAP Open decryption/encryption interfaces
7 Integrated vs. Modular CCAP components Similar boxes for bothHE RouterICCAPSingle CCAP VendorI-CCAPIPSub & FlowManagementRoutingPASIHE Router / M-CCAP PSICCAPBest-in-Class ExpertiseM-CCAP ASEach approach has pros and cons
8 CCAP use cases examples (two of several) Add density with CCAP Access Shelf in DS-only modeWhere I-CMTS existsFor M-CMTS marketsHE RouterHE RouterShorter TermBcastVODSDVBCastVODSDVHE RouterTodayURURM-CMTS CoreURI-CMTSUEQAMURUSUSM-CMTS CoreM-CCAP ASin DS modeDSDSUSDSEventually I-CCAP or……M-CCAPHE RouterMigrate to I-CCAP & relocate CCAP-ASOr, add CCAP PSHE RouterExisting Router w/PS SWAdd US LCsHE Router / M-CCAP PSLonger Term OptionsFutureURI-CCAPURURI-CCAPURM-CCAPASUSDSUSDSUSDS
9 CCAP migration options CapacityAugmentNew ServiceDeploymentInfrastructureUpgradeDrop in CCAP as SGs are split or EQAMs/CMTSs are addedKeep current equipment and eventually move to other locationsAdd CCAP for new serviceMaintain existing equipment for existing servicesEventually integrate other services into CCAPAdd CCAPs for all SGs in key HEsIndependent of servicesExisting equipment relocatedBroadcast and OOBBroadcast and OOBBroadcast and OOBSDV/VOD EQAMsSDV/VOD EQAMsCCAP for New ServiceCCAPCMTSsCCAPCMTSsCombinerCombinerCombinerLasers and ReceiversLasers and ReceiversLasers and ReceiversExisting SGsExisting SGsNew SGsExisting SGs
10 Preparing for CCAP Work underway in the many areas at Comcast: Systems: configuration, monitoring, logging, fault detection, trouble management, inventory, databases, etc.Operations: changes to deploy and manage single deviceTesting: process (who/how/when and what order), and edge QAM, DRFI performance, new features, and new services (RS-DVR, AVS)Deployment planning:Network models for system types: very large to very small HEsTrials starting in 2011: operational readiness focus, not equipmentNew combiner equipment: optimized for CCAP and remaining inputsWorking with Motorola and Cisco on encryption licensing model and ECMG implementation plan
11 CCAP operational readiness trial – concept diagram CCAP-like network to understand technical/ops issues and prepareOperational processes, tools, network engineering, etc.The trial is about MSO operations, NOT to test equipmentThe scope will be minimal but meaningful (few service groups)Collaborative effort with Cox and RogersOTHER QAMsCombinerANALOGTEST~1202-4DTAM-CCAP ASin DS-only mode6DSBCAST4SDV20-244VODAll services4M-CMTS CoreUS
12 Completing CCAP specifications Large team of industry experts developing CCAP specsKey engineers and architects from all EQAM and CMTS vendorsAgreements with Cablevision, Charter, Cox, LGI/UPC, NCTC, Rogers, and others, plus working with TWC on common requirementsDirect support from CableLabs; now working on CL CCAP SpecsCable Europe Labs representing the 15 largest MSOs in EuropeMSO specification documents:Phase 1 completed in March 2010 (focus on HW & Functions)Phase 2 completed in July 2010 (added Config & Mgmt and PASI)Phase 3 completed in Nov (expanded all specs; wrote CL TR)Phase 4 in progress, adding adv. Functions, ATP and updated CL TR (target Sept. ’11)CableLabs working on CCAP OSSI and PASI specsChanged name to converge TWC and Comcast efforts
13 Summary and conclusions Thank You!!Summary and conclusionsCCAP Platform is the Next Gen CMTS and Edge QAMNatural technology evolution; cost effective, simple and redundantSupports all digital services (VOD, SDV, Broadcast, HSD/voice)Easy migration from MPEG-TS to DOCSISMany MSOs need the CCAP ASAPOperational simplicity and benefits are staggeringCCAP QAMs are much more cost effectiveExpect initial trials in 2011 and initial deployments in 2012Please let us know of any interest in participating, or of questions, comments and especially suggestions