MoCA Protocols

What exactly is this MoCA thing?

Moderator: Anton Monk - SWG Chair Panelists: Stephen Palm - Broadcom, Al Garrett - Conexant, Ron Lee - Entropic Certification Program: Tom Leacock - Chair Certification WG

Introduction
DBS

Office / Den

Master Bedroom

Kids Bedroom
MoCA / WiFi Bridge

Cable, Telco

MoCA Ethernet Bridge

Media Center PC

MoCA Client STB Coax

MoCA / WiFi Media Router

MoCA Client STB Coax

Broadband Multimedia

MoCA Home Server - DVR WebPad Family Room Kitchen

Outline

MoCA Technology Overview Physical Layer MAC Layer Parameterized QoS Certification

Video Networking Requirements

High Performance with wide outlet coverage

> 100Mbps net throughput at >95% of outlets

Inherent low BER/PER

Cannot rely on retransmissions

Low Latency independent of network load

No time to retransmit video frames

Coexist with Cable, DBS, Terrestrial, Telco Spectrum support for future performance increases (>1Gbps)

Installation Objectives

Easy installation in the home Low sensitivity to home coax topology

Be able to seamlessly support any type of Coax topography

Any network node can be connected to any outlet in the house Minimize need to replace splitters or add new wires

MoCA Technology Features

MAC throughput including 175 Mb/s (MoCA v1.1) Flexible spectrum usage 50 MHz in range 875 to 1525 MHz Support for 16 nodes (MoCA v1.1) PHY is Bitloaded OFDM optimizes PHY rate for any channel
Pre-equalization allows simple Reed Solomon FEC

Probing mechanism allows performance optimization per connection Fully coordinated and synchronized network
Transmission slots are assigned by a Network Controller (NC) per Request-Grant mechanism NC is automatically selected Preferred NC can be selected by higher layer applications (MoCA v1.1)

QoS
Prioritized QoS differentiated service for video, voice and gaming Parameterized QoS bandwidth reservation per flows (MoCA v1.1)

Management interface with detailed characteristics (improved in MoCA v1.1)

PHY

MoCA PHY Features

ACMT Adaptive Constellation Multitone
Pre-equalize modulation to frequency response of each path using bitloaded OFDM Channel profiling mechanism allows performance optimization per connection

50 MHz bandwidth
Allows for operation in all application spaces on coax

Constellation sizes up to 256-QAM

Up to 270Mbps PHY rate

Frequency allocation 875to 1525 MHz Dynamic range > 70 dB Forward error correction (RS)
Provides for low PER targets without cost of excessive code redundancy

PHY: Multipath Environment and Mitigation

Example Two splitters

L
(~0.4uSec/100m)

TX

Return Loss
Splitter Splitter

Isolation

RX

Isolation of first splitter and return loss of second filter creates first order reflections Return losses create additional lower second order reflections Splitter characteristics and wire lengths create arbitrary multipath scenarios
Arbitrary, but fixed

Reflections from splitters creates multipath

Channel characteristics are similar to wireless but have longer delay spread

Home Coax Network Characteristics

L
(~0.4uSec/100m)

TX
Isolation

Return Loss

splitter1
Reflections from splitters creates multipath Channel characteristics are similar to wireless but have longer delay spread 300 ft has a delay of about 0.4 sec MoCA supports delay spread up to 0.8 sec Reflections and isolation create very irregular/notched frequency responses

splitter2

RX

Random Echo Environment. Beware! Due to the random nature of splitter isolation, echoes can be smaller, equal to, or larger than the primary path

OFDM with Pre-equalization can easily OFDM with Pre-equalization can easily

handle these environments handle these environments

Channel characteristics examples

Multipath mitigation

Adaptive Constellation Multitone

Pre-equalization / Bitloaded OFDM optimizes the modulation to the channel response Only send QAM constellation on each subcarrier that can support the required 1e-9 BER Simplifies FEC

Continuously probe each path in both directions to account for changes in channel response Based on channel profile - optimize preamble and cyclic prefix to improve multicarrier efficiency

PHY: Spectral Compatibility

Satellite Plant Frequency Plan

Usable MoCA Bands (without Ku) A1, B1, C1,C2,C3,C4, D (1 8) ADSL, VDSL
outside/inside the house

Usable MoCA Bands (w/ Ku) A1 MoCA Channel Allocations

Powerline

B1 A1

C2 C4 C1 C3

D(1 8)

4 - 45MHz Baseband

Off Air 54 211MHz

250MHz
Digital, B-band

800 MHz 950MHz 750MHz

1.45GHz 1.65GHz 1.6GHz

Digital, Ku-band Digital, Ku/Ka-band

2.15GHz

HomePNA

From the dish into the House

From the dish into the House

From the dish into the House

Up

DOCSIS / Cable

Down

Cable Plant Frequency Plan

Usable MoCA Bands (no 1GHz DS) C1,C2,C3,C4, D (1 8) Usable MoCA Bands (w/ 1GHz DS) D (1 8)
outside/inside the house

MoCA Channel Allocations UPSTREAM RF DOWN STREAM RF

131 - 6MHz channels B1 A1 C1 C2 C4 C3 D(1 8)

54MHz Baseband

Analog

550MHz

Digital

800 MHz 860MHz

Future Digital

1GHz

1.6GHz

From the Street into the House

Inside the house, available for MoCA

MAC

MAC: Highlights
Channel Access: TDMA/TDD
All nodes use the same carrier for Transmit and Receive

Fully scheduled MAC no collisions

Channel access is fully controlled by a Network Controller (NC) Node Transmission Slots assigned by Request-Grant mechanism

QoS Support
Parameterized QoS bandwidth reservation per flow (MoCA v1.1) Prioritized QoS network wide

Ethernet convergence layer Packet aggregation (MoCA v1.1) MAC throughput up to 175Mb/s
MoCA 1.0 about 135 Mb/s

Average latency = 3.5 ms

or 4.5ms when more than 8 nodes are connected

Link Layer Privacy

MAC: NC Node

Network Coordinator (NC) Node Operation

Admits new nodes to the network Controls all transmissions on the network via MAP messages Manages Encryption Keys Automatically selected from nodes in a network Selection based on pre-assigned priorities and most advantageous location Preferred NC can be assigned by higher layer applications (MoCA v1.1)

Backup NC is assigned to ensure rapid handoff in the event of device failure

MAC: Network Creation

Creation of a new network

Depending on the product features, the nodes may scan through channels Upon tuning to a new channel nodes alternately listen for and send beacons New nodes first listen for beacons - If a new node hears a beacon, it tries to join the network by sending an Admission_Request If a new node doesnt hear any beacons, it will send beacons and listen for Admission_Request messages from other nodes A network is established once a NC node admits one other node to its network Subsequent new nodes will hear the NCs beacons and join the same network

MAC: Packet Scheduling

Pkt1 arrives at Node1 for Tx to Node2 Node1 requests BW for Pkt1
Rsvr_Req{}

Node1

Node2
MAPn {RRs, MAPn+1} Rsvr_Req{Pkt1} Rsvr_Req{} MAPn+1 {RRs, MAPn+2, Pkt1}

NC Node

Latency

NC Grants Pkt1 BW Node1 Transmits Pkt1 to Node2

Pkt1

Rsvr_Req{} MAPn+2 {RRs, MAPn+3, Pkt1}

Pkt1 is forwarded by Node2 MoCA layer

MoCA 1.1 Aggregation Performance

Original data: Field trial: 246 homes in more than 120 ZIP codes Aggregated number of packets = 4 or 6

MoCA Link Privacy

Protects the User against eavesdropping - Shared Medium Password based
Entered by user and stored in device Networks require nodes to have matching password Needed for admission

All transmissions encrypted except for beacons

56 bit DES Rotating Traffic keys

MAC: Parameterized QoS

MoCA Prioritized and PQoS Prioritized QoS

MoCA 1.0 Differentiated service for video, voice and gaming Three Queues

Parameterized QoS - PQoS

MoCA 1.1 Bandwidth reservation per flow Admission Control

Both require Request/Grant before every transmission

On a cycle basis, the NC will give away a reservation if no RR

MoCA Prioritized QoS

MoCAs Prioritized QoS allows applications such as DLNA to differentiate traffic

MoCA Priority Queues High Medium MoCA Throughput limit 9 Mb/s 64 Mb/s 802.1Q User Priority 6,7 4,5 0,3 Low 64 Mb/s 1,2 DLNAQOS_UP DLNA Transfer Mode

DLNAQOS_3 (Highest) DLNAQOS_2 DLNAQOS_1 DLNAQOS_0 (Lowest)

(Reserved for Voice) Streaming (Audio & Video) Interactive (Images) Background (All Media Classes)

PQoS Create/Update Flow

Admission Control Any node (called Entry Node) can attempt to create or update any PQoS Flow. A node submits a TSPEC with ingress & egress node IDs to NC NC asks all nodes to provide their current PQoS commitments and ability for newly requested flow NC calculates if PQoS flow can be accepted NC notifies nodes and Entry node
E N ntry ode N C O N ther odes

S it ubm W 0 ave R equest N requests fromall nodes C their current PQ oS com itm andw m ent hether the PQ Flowcanbe oS createdor updatedas requested

R esponse R esponse(s) W 1 ave R equest

U the responses sing received, N accepts or C rejects the requestedPQ oS Flowcreationor update

R equest

R esponse R esponse(s)

W 2 ave R equest

N notifies the Entrynode C of the result of its create or update PQ Flowrequest oS

R esponse

MoCA PQoS TSPEC

The MoCA PQoS TSPEC concentrates on a concise, practical representation of traffic Provided by upper layer application such as DLNA Player
MoCA TSPEC Parameter Peak Data Rate (T_PEAK_DATA_RATE) Packet Size (T_PACKET_SIZE) Lease Time (T_LEASE_TIME) Burst size (T_BURST_SIZE) Description The maximum number of kilobits of payload that a MoCA PQoS Flow transfers over a one second period in the MoCA Network The packet length in bytes of a flow. The bandwidth cost of the flow is calculated using this value. Number of seconds until nodes automatically release resources for the flow. The value 0x00000000 is used to indicate infinite lease time. The number of flow packets used to calculate the Injection Bit Rate and the Injection PDU Rate.

Admission Control Cost Information The basic information a node tracks for media access
Field EXISTING_STPS EXISTING_TXPS COST_STPTX COST_TXPS REM_NODE_CAPACITY Usage Duration in multiple of SLOT_TIME/second for the set of existing PQoS Flows for which this node is the ingress node. PQoS Flow transmissions/second for the set of existing flows for which this node is the ingress node Ingress nodes cost of new or updated PQoS Flow Ingress nodes calculation of the required number of PQoS Flow transmissions/second for the specified flow If this node is the ingress or the egress node for the PQoS Flow, the peak data rate (kb/s) that this node can commit to this PQoS Flow for the requested PQoS Flows T_PACKET_SIZE. If this node is an egress node for the PQoS Flow, the maximum T_BURST_SIZE value for which this node can accept the PQoS Flow Create/Update Transaction for the requested PQoS Flows T_PACKET_SIZE.

REM_BURST_SIZE

QoS for Content

MP3 Player

Prioritized PQoS

Network Storage

Certification

Why Certify?

Test interoperability on the coax between multiple vendors devices

Good customer experience when all devices interoperate Reduce the need for customer support calls Fewer returned devices and service provider calls

Document certified operation of the device with public certificate optionally posted on the MoCA website

Where to Certify?
MoCA Test Facility NTS (National Technical Systems)
NTS is the only test facility authorized by MoCA Industry leading computer hardware & software testing and compliance testing facility located in Culver City, California Performs certifications for USB, MoCA, WHQL/DTM, 1394, Xbox/Xbox 360, ZigBee, XM, and others In addition, also can perform other safety and regulatory tests (e.g., NEBS/Bellcore, FCC, CE Mark, VCCI, BSMI, EMC, etc.), as well as automation Certification testing requires one week (10 hour days) to perform Once you successfully complete testing, NTS will notify MoCA of results NTS can also perform pre-testing and debugging of your product Contact: Raymond Chung R&D Manager Tel. 310-641-7700 ext. 1056 raymond.chung@ntscorp.com www.ntscorp.com

How to Certify?

Two testing phases:

Self tests Tests run by vendor before Cert Lab tests For MoCA 1.0 there are about 25 test procedures Vendor uses his own nodes in place of Golden Nodes in the CTP Certification Lab tests at NTS facility Will run a subset of the tests core tests run in self tests Uses same test template as self tests Tests will be run on submitted devices with MoCA Golden Nodes Also will run interoperability tests with other vendor devices Certification Lab posts results on their website for access by certifying member and MoCA Certification Board

How to Certify?
Run self-tests with Certification Test Plan (CTP) at your own facility Record results on the CTP testing template Contact NTS to schedule certification testing date Submit self-tests results to the MoCA Certification Board Bring 5 devices and self test results to Lab Cert testing at NTS Also any special equipment needed for testing your device Complete certification test (3 to 5 days) and pay cert fee Leave 2 certified devices with NTS for interop testing

Certification Documents

Self-test template Waiver requests Identical Device Certification requests

Model number change and/or company name change to a PCMD (Previously Certified MoCA Device)

Re-certification requests
Some HW or SW changes to a PCMD Re-certification requirements depend on changes

All docs will soon be up on the MoCA website in the members only section. New email address for members: to send docs directly to Certification Board.

Reflectors

MoCA Specification Forum reflector for feedback on Spec questions MoCA Testing reflector for feedback on certification testing questions For other questions or to gain access to these reflectors send a request to help@mocalliance.org

Certification documents MoCA Certification email For sending:

Self-test data results Requests for Waivers Requests for Re-certifications or Identical Device Certifications Other special requests to the MoCA Certification Board

moca_cert_submissions@mail.mocalliance.org

Thank You!
Questions?