Quick Start Steps - Network Eventos P… · Delivering CCAP (Hub in a Box) ... • SCTE 55-1:...

Remote PHY

Steve Condra, Director of Product Management

Todd McCrum, Director of Business Development

September 3rd, 2014

A Critical Component of Virtualization

Cisco Confidential 2 © 2013-2014 Cisco and/or its affiliates. All rights reserved.

Agenda

• The Vision for Cable MSO’s

• An Evolutionary Path toward the Future

• How does Remote PHY fit into this Evolutionary Path?

• Remote PHY Overview


The Vision


The Vision for Cable MSO’s

• Imagine a time when all services are integrated and managed together over a single infrastructure.

• Imagine a time when your Access plant choice didn’t matter (HFC, PON, SP Wifi, etc.).

• Imagine a time when new services and new service groups are launched directly from your HE/Data center without touching any physical assets in your plant.

• Imagine if this was all Standards based.

This vision is coming to life today with an elegant migration plan for you


Evolution to the Future


Example of elements in Today’s Network and Future’s Network

Data Center Headend/Hub Outside Plant Home/Business

Edge QAM CMTS HFC Node Linear/

Analog Optics Coax

Cable Modem/Settop

Encoders CDN

Metro Ethernet

Coax

CM DOCSIS 3.1/IP Settop R-PHY Node Datacenter

DS CMTS QAM

Modulation move to

the Node

US CMTS QAM demodulation

move to the Node

CMTS Routing and

DOCSIS functions run

in Virtual Machine at

DataCenter

DS QAM Modulation US QAM Modulation

Virtual CMTS

Encoding and Video

Procession functions

run in Virtual Machine

at DataCenter

Virtual Encoding

CDN and Transparent

Cashing functions run

in Virtual Machine at

DataCenter

Virtual CDN

Analog Optics from

HUB to Node became

Metro-Ethernet Links

Cloud DVR will be an

application running in

the Datacenter

TODAY

FUTURE

Cisco Confidential 7 © 2014 Cisco and/or its affiliates. All rights reserved.

Delivering CCAP (Hub in a Box)

• Convergence of all Broadcast and Narrowcast services

• 10x the bandwidth of existing CMTS platforms

• Reduce hub space & power by up to 50%

• Ground-up design for DOCSIS 3.1

- Scaling to 10Gbps DS & 2Gbps US per Service Group


Path to Virtualizing CCAP – Phase 1 Migration to Remote PHY & CCAP Cores

• Distributes DOCSIS PHY across hubs & nodes

- CMTS is comprised of CMTS Core, PHY and multiple remote PHY

• Enables reduction in number of CMTS Chassis’

- Scale number of Service Groups beyond capacity of existing CMTS’s

- Reduce power & rack space

• Delivers unprecedented scaling


• vCCAP = vCCAP Cores + distributed Remote PHYs

- vCCAP Cores: agile, elastic and on-demand

- Remote PHY nodes scale DOCSIS bandwidth at the fiber node

Virtualizing CCAP – Phase 2 CCAP Core Evolves into Virtualized Software (vCCAP Core)

• vCCAP scales subscribers and bandwidth without adding space and power in the hubs

• CCAP and vCCAP co-exists

- Operator chosen blend


• Fiber deep architecture

- Reduces OpEx and multiplies capacity

• MetroE and WDM Backbone

- Superior capacity and cost vs. analog fiber

- Low cost backbone for all Metro services

Access Architecture Agnostic (Powered by SDN) Multi Service Metro Network

• FTTH (PON) for selected customers

- Integrated on MetroE/WDM Backbone

• Blended DOCSIS and PON architecture

- Highest capacity and low cost

- Operator paced evolution


Remote PHY Introduction


Questions

• What is Remote PHY?

• How does it apply to DOCSIS, Video, OOB, Telemetry?

• What are DEPI, UEPI and R-DTI?

• What’s the deal with the US scheduler?


Remote PHY Vendor Business Goals

1 Interoperability between CCAP-Core and R-PHY Node

• Any CCAP-core vendor, any Remote PHY Node vendor

• For DOCSIS, MPEG-Video, OOB, and Telemetry

2 Continue to provide value in the CCAP-Core

• drive innovation and differentiation in the CCAP-core

3 Standardize the Remote PHY Entity

• specify the interface between the CCAP-core and Remote PHY

• specify to the level of detail that permits multiple silicon solutions

• leverage existing M-CMTS specifications

Neymar after scoring goal against Cameroon


Specification Names and Acronyms Acronym MHA R-PHY Definition

DEPI ✔ ✔ Downstream External PHY Interface

UEPI ✔ Upstream External PHY Interface

ERMI ✔ Edge Resource Management Interface

DTI ✔ DOCSIS Timing Interface

R-DTI ✔ Remote DOCSIS Timing Interface

R-OOB ✔ Remote Out-of-Band

PMI ✔ Provisioning and Management Interface

VSI ✔ Video Stream Interface

R-PHY System ✔ Remote PHY Boot and Configuration

TR ✔ ? Technical Report


Current R-PHY Committee

Cisco

Casa

Arris (new addition)

Altera

Analog Devices

Broadcom

MaxLinear

Maxim

ST

Xilinx

CCAP Vendors (3)

Silicon Vendors (7)

Buckeye Cable

Brighthouse

Charter

Comcast

Cox

Get

LGI/UPC

Mediacom

Rogers

Shaw

Telenet

TWC

Videotron

Virgin Media

+ CableLabs

Cable Operators (14)

We want NET involved in this effort to

represent Latin America!


Remote PHY Philosophy 101

Remote PHY == Centralized Software

• R-PHY uses the MAC-PHY ASIC boundary

• R-PHY is a PHY ASIC at the end of a network.

• Remote entity is simplistic and stable as possible

• Central entity contains complexity and scalability


Upstream Scheduler Strategy

• ≤100 miles MAC-MAC:

• Current centralized scheduler

• >100 miles MAC-MAC:

• Enhanced Centralized scheduler

• DOCSIS scheduler is pipelined and adaptable to latency

• Backup plan

• For extreme distances, scheduler could be in the Remote PHY entity.

• However, this creates complexity and interoperability issues.

• Not needed at this time.

Head End Hub Node Home

CCAP-Core R-PHY CM/STB

PHY-to-PHY MAC-to-MAC

L3 L2 HFC


CCAP with Centralized PHY

• In a I-CCAP, the CMTS and EQAM share a common PHY


CCAP with Remote PHY

• The CCAP PHY chip is remotely located and connected by a pseudowire

• DEPI is the downstream pseudowire (PW)

• UEPI is the upstream pseudowire (based on DEPI)

• Remote DTI manages transfer of time and frequency


Remote PHY for CCAP

CCAP

Core

MAC +

Service

Flow

Engine

CCAP

Remote

PHY

DOCSIS

CMFiber (Digital, IP)

DOCSIS

Provisioning System

DOCSIS

Policy Server

DOCSIS

PacketCable

DOCSIS Signaling

Internet

Remote PHY Signaling

Coax

• Adapts CCAP to an HFC plant that contains digital

fiber instead of linear fiber

• DOCSIS signaling remains end-to-end


Remote PHY for Video

EQAM

Core

CAS

De-Jitter

PID

EQAM

Remote

PHY

Video

STBFiber (Digital, IP)

EQAM

Provisioning System

EQAM

ERMI

EQAM

Key Server

Video Signaling

VideoServers


Coax

• Edge QAM with a Remote PHY

• Central: CAS, large buffering, signaling

• Remote: QAM PHY, small buffering


Remote PHY for OOB

OOB

Core

CAS

De-Jitter

PID

OOB

Remote

PHY

Video

STBFiber (Digital, IP)

OOB

Provisioning System

OOB

Info

OOB

CAS Server

OOB Signaling

OOBServers


Coax

• SCTE 55-1: Motorola/Arris with MPEG-TS in

downstream and Aloha in the upstream

• SCTE 55-2: SA/Cisco with ATM over T1.

• Central: software and carousel

• Remote: PHY with some basic framing


R-DTI • Remote DOCSIS Timing Interface

• Different protocol than DTI

• Primary approach is IEEE-1588.

• DOCSIS 3.1 defines 1588 and DOCSIS relationship

• Other timing approaches include:

• Synchronous Ethernet

• CCAP-Core slave mode


Summary

• The industry is moving toward Virtualization

• The path to virtualization can be elegant and cost effective, utilizing multiple Access technologies

• SDN will make your plant services “Access Agnostic”

• Remote PHY is a critical component in the path to Virtualization and Cisco is leading the way toward standardization

Thank you.

Quick Start Steps - Network Eventos P… · Delivering CCAP (Hub in a Box) ... • SCTE 55-1:...

Documents

Transcript of Quick Start Steps - Network Eventos P… · Delivering CCAP (Hub in a Box) ... • SCTE 55-1:...