PacketCable Networks VoIP Over HFC

1
PacketCable NetworksVoIP Over HFC

• Al McNichol
• Sr. Manager, Sales Engineering
• Broadband Division
• Atlanta, Ga.

2
AGENDAPacketCable VoIP Networks

• IP Telephony Enablers Drivers
• Migration- Circuit Switched to VoIP
• What is PacketCable
• PacketCable Specifications
• Relationship to Other Projects
• VoIP Overview
• Call Features Supported
• Alternative Access Methods
• Voice Quality
• Primary Line
• PacketCable Components
• Summary of Security Interface
• Provisioning Process
• Call Signaling Protocols

CMTS (DOCSIS 1.1) Foundation For IP Voice CMTS
Carrier-Class Architecture Interfaces Management
Event Mechanism E-MTA Indoor Vs. Outdoor
E-MTA MTA Evolution- Li-Ion vs. SLA Challenges
of PacketCable Telephony End to End IP Network
Components PacketCable Availability Model Loop
Diagnostics Power Management Multi-Vendor/
Interoperability Quiz
3
Today- Constant Bit Rate (TDM) Voice Over HFC
Network Architecture
HDT
Class 5 SWITCH
DS-1/ E-1 MPR
TXC
TIC
AIC
c o n t r o l l e r
m a p p e r
HDT MODEM
TR-303 DS-1s
NIU MODEM
LC
HFC
DS-1/ E-1 MPR
TXC
TIC
AIC
OSC 2.56 MHz
Digital TDM to PCM
Broadcast TDM/PCM
4
IP Telephony Enablers Drivers

• Distributed, rather than centralized call
  processing routing makes more efficient use of
  transport resources
• The statistical nature of voice traffic, fast and
  inexpensive DSP chips, and modern high speed
  packet network elements allow efficient
  packetization
• Service Providers believe one converged voice,
  video and data packet network is more efficient
  to operate than two or three separate networks
• About 1 million people use VoIP in the United
  States, using paid services such as Vonage,
  Net2Phone and Packet8. MSOs such as Advanced
  Cable Communications, Armstrong Cable Services,
  CableAmerica and Mid-Hudson Cablevision have
  signed deals with Vonage (gt100,000 Subs)
• Others use free services such as Skype, Free
  World Dial-Up, SIPphone or those from major
  instant messaging providers to chat only between
  computers.

5
Migration- Circuit Switched to VoIP
Metro Optical Transport
6
PacketCable Specifications
7
What is PacketCable Voice?

• Specifications- Complete Broadband digital
  telephony system
• Provisioning, billing, security
• Primary line, secondary line
• Supports GR-303 as interim solution
• Requires DOCSIS 1.1 (or DOCSIS 2.0)
• CM, eMTA and CMTS
• Many new devices compared to data deployment

8
(No Transcript)
9
PacketCable Specification

• PacketCable 1.X version numbering scheme
• 1.0 Basic telephony service (On-Net / On-net /
  Off-net)
• 1.1 Primary line service
• 1.2 Inter-domain IP service (MSO to MSO)
• 1.3 Call Management Servers
• PacketCable Multimedia

Any given specification may contain portions of
any 1.X architecture
10
PacketCable Telephony

• Merging of data and telephony worlds How to do
  telephony using transport protocols designed for
  data
• Began with strong data bias (Distributed, Web
  Paradigm)
• Now has strong telephony bias (Centralized, PSTN
  Paradigm)
• PacketCable Specifications are Essentially
  Complete
• PacketCable 1.0, 1.1, 1.2, 1.3 and Multimedia
  specifications and technical reports are publicly
  available.
• 20 specifications
• 12 technical reports
• Strong vendor participation
• Standard protocols, but specific profiles gt
  specialized boxes
• gt2,000 pages specs/tech reports/testing
  requirements
• Future
• PacketCable 2.x?

11
http//www.packetcable.com/specifications/

PacketCable 1.0 Specifications

• PacketCable 1.0 Technical Specifications
• NEW PacketCable Audio/Video Codecs
• NEW PacketCable Dynamic Quality-of-Service
• NEW PacketCable Network-Based Call Signaling
  Protocol
• NEW PacketCable Event Message Specification
• PacketCable Internet Signaling Transport
  Protocol (ISTP)
• NEW PacketCable MIBs Framework
• NEW PacketCable MTA MIB Specification
• NEW PacketCable Signaling MIB
• NEW PacketCable MTA Device Provisioning
• NEW PacketCable Security
• NEW PacketCable PSTN Gateway Call Signaling
  Protocol
• NEW CableLabs Definition MIB

• PacketCable 1.0 Technical Reports
• PacketCable NCS Basic Packages
• PacketCable Architecture Call Flows - On-Net MTA
  to On-Net MTA
• PacketCable Architecture Call Flows- On-Net MTA
  to PSTN Telephone
• PacketCable Architecture Call Flows - PSTN
  Telephone to On-Net MTA
• PacketCable 1.0 Architecture Framework
• PacketCable OSS Overview Technical Report

12
PacketCable 1.1 Specifications
The PacketCable 1.1 and technical reports define
requirements for offering a Primary Line-capable
service using the PacketCable architecture. The
designation of a communications service as
"primary" means that the service is sufficiently
reliable to meet an assumed consumer expectation
of essentially constant availability.

• PacketCable Management Event MIB
• PacketCable Embedded MTA Primary Line Support
• PacketCable Management Event Mechanism
• NEW PacketCable Electronic Surveillance
• PacketCable Audio Server Protocol Specification

13
PacketCable 1.2 Specifications
The specifications and technical report define
the functional components and interfaces
necessary to allow communication between
PacketCable 1.0 networks using an IP transport or
backbone network. These specifications describe
the call signaling and quality-of-service (QoS)
extensions to the PacketCable 1.0 architecture to
enable cable operators to directly exchange
session traffic. This will allow a subscriber
on one PacketCable network to establish
end-to-end IP or "on-net" sessions, where the
call is established end-to-end on the IP network
without traversing the PSTN network at any time.

• PacketCable Call Management Server Signaling
• PacketCable Inter-domain Quality of Service
• PacketCable 1.2 Technical Reports
• PacketCable 1.2 Architecture Framework

14
PacketCable 1.3 Specifications
The PacketCable 1.3 defines the functional
components, interfaces and a data model to
perform subscriber provisioning on Call
Management Servers.

• PacketCable CMS Subscriber Provisioning
  Specification

15
PacketCable Multimedia Specification
The specification and technical report define
the functional components and interfaces
necessary to provide Quality-of-Service (QoS) and
Resource Accounting to any multimedia-based
application. A framework that provides
capabilities for service management on top of
DOCSIS and PacketCable These documents define
the PacketCable Multimedia architecture, Policy
and QoS signaling protocols, event message
generation for resource accounting, and security
interfaces

• PacketCable Multimedia Specification
• PacketCable Multimedia Technical Report
• PacketCable Multimedia Architecture Framework

PacketCable Multimedia enables the scalable
addition of new real-time services. Eight
suppliers participated in the non-certification
event. ARRIS, Cisco Systems and Motorola
Broadband supplied CMTSs. Camiant, Telcordia and
CableMatrix supplied policy servers, and
Ellacoya, Syndeo Corp. and Telcordia supplied
application managers.
16
Relationship to Other Projects
PacketCable is a set of protocols developed to
deliver Quality of Service enhanced
communications services using packetized data
transmission technology to a consumers home over
the cable network. PacketCable utilizes a
network superstructure that overlays the two-way
data-ready cable television network. While the
initial service offerings in the PacketCable
product line are anticipated to be Packet Voice
and Packet Video, the long-term project vision
encompasses a large family of packet-based
services.

• Framework for future CableLabs projects

17
Relationship to Other Projects

• First complex application to use DOCSIS 1.1
• Referred to as DSx (DSA, DSC, DSD)
• DSA Add service flow
• DSC Change service flow
• DSD Delete service flow
• Dynamic Service Flows
• Needed to guarantee bandwidth for call
• Provides QoS -- Quality of Service
• User experience like PSTN, not like Internet
  voice applications

18
VoIP Overview
19
PacketCable 1.0

• Basic telephony service
• Call signaling
• Quality of Service (QoS)
• Codec
• Client provisioning
• Billing event message collection
• PSTN (Public Switched Telephone Network)
  interconnection
• Security interfaces
• Single-zone PacketCable solution
• NCS basic packages
• Call flows
• On-net to on-net
• On-net to off-net
• Off-net to on-net
• PacketCable 1.0 architecture framework
• Operations support system framework

20
PacketCable 1.1

• Primary Line-capable service
• The designation of a communications service as
  "primary" means that the service is sufficiently
  reliable to meet an assumed consumer expectation
  of essentially constant availability.
• Availability during power failure at the
  customer's premises
• Access to emergency services (911, etc.).
• PacketCable 1.1 Technical Reports
• Line Control Signaling System Architecture
  Technical Report
• Management Event Identifiers Technical Report
• VoIP Availability and Reliability Model for the
  PacketCable Architecture Technical Report
• Electronic Surveillance Call Flows Technical
  Report

21
PacketCable 1.X

• PacketCable 1.2
• Communication between PacketCable 1.0 networks
  using an IP transport or backbone network.
• Call signaling
• Quality-of-service (QoS)
• Enables cable operators to directly exchange
  session traffic.

22
PacketCable Components
KDC
All interfaces secured
DOCSIS 1.1
PS
RKS
MTA
CMTS
CMS
MTA Multimedia Terminal Adapter (CPE)
CMTS Cable Modem Termination System
KDC Key Distribution Center (Security Server)
PS Provisioning Server (i/f to backoffice)
PSTN
RKS Record Keeping Server (i/f to billing
system)
GW
CMS Call Management Server (like C.O.)
PSTN G/W Gateway to the PSTN
23
PacketCable Primary Line

• Adds requirements on MTA (separate spec)
• Quality, delay, etc. part of PacketCable 1.0
  specs
• Power
• Outdoor MUST support network power or local
  power supply (LPSU) and battery backup power
• MUST support center conductor and composite pair
  power delivery
• Indoor MUST support battery power
• Telemetry
• CM failures detection must meet DOCSIS
  requirements
• No separate MTA failure requirements
• Spec defines only battery-related alarms
• AC Failure
• Replace Battery
• Battery Missing
• Battery Low
• POTS interface
• Standard premises wire requirements for analog
  lines

24
Full PacketCable Event Sequence
25
Call Features Supported

• Automatic Number Assignment Confirmation
• Direct Distance Dialing
• Critical Interdigital Timing for Dialing Plan
• International DDD (IDDD) Local Billing Control
• Residence Distinctive Alerting Service
• Free Terminating Service
• Code Restriction Diversion
• Toll Restricted Service
• DTMF Dialing
• CLASSSM Calling Number Delivery
• CLASSSM Customer Originated Trace
• CLASSSM Anonymous Call Rejection
• CLASSSM Calling Number Delivery Blocking
• CLASSSM Calling Identity Delivery Suppression
• CLASSSM Calling Name Delivery Blocking
• CLASSSM Calling Name Delivery
• CLASSSM Calling Identity Delivery on Call
  Waiting
• Speed Calling 8
• Speed Calling 30

• Intercept
• Routing for blank/changed/etc. phs
• Customer-Changeable Speed Calling
• VIP Alert (Distinctive Ringing)
• Visual Message Waiting Indicator (FSK)
• Message Waiting Tone (stutter dial tone)
• Conference Calling - Six-Way Station Controlled
• Call Hold, Call Pick-up, Toll Free Calling
• E911
• Customer Call Back (Automatic Recall) (69)
• Three-Way Calling
• Call Forwarding Variable
• Call Forwarding Busy Line
• Call Forwarding - Dont Answer - All Calls
• Service Provider Originated Trace
• Courtesy Ring Generation
• Multiple Directory Numbers on a Line
• Customer Access Treatment (CAT) code restrictions
  
• Single-Digit Dialing

26
Management Event Mechanism

• Basically, signals when something unexpected
  happens
• 5 levels
• Critical
• Major
• Minor
• Warning
• Information
• Notification to
• local (kept on device)
• SNMPv3 TRAP
• SNMPv3 INFORM
• SYSLOG

PacketCable Elements elements MUST support a
mechanism to allow the element management system
to map each event to reported notification
mechanisms.
27
PacketCable Telephony
28
PacketCable Architecture
RKS/OSS Servers
29
Alternative Access Methods
Telephony Switching Sub
-
system
Application
Servers
CALEA
Pre Paid
Media Servers
Server
SMTA
Audio
SMS
Server
Alternative Access Networks
RKS
Server
Multi
-
service Metropolitan
l
UM
Network
Server
Wireless Access
l
ERMG
Non
-
managed IP networks
l
LAN
SG
KDC
Conference
Server
Video
Comm
Server
STP
CMS
MGC
EMTA
HFC Access
Public
CMTS
Network
Telephone
MG
DOCSIS
1
.
1
Networks
EMTA
Managed
IP/MPLS
Network
DNS/DHCP
TFTP
ToD
LDAP
Back Office Servers
OSS Sub
-
system
30
Voice Quality
MOS (Mean Opinion Score) Personal polling to
score a sound sample from 1 to 5. A MOS score of
4 is considered toll quality. PSQM (Perceived
Sound Quality Measurement) scores speech samples
on a scale of 015. Zero being a perfect score.
The PSTN generally scores for 0.5 to 2.0. Field
data An on-net to off-net 3-way calling scenario
shows an average PSQM score of 4.05 while average
delay is 78 mSec, and 4.04 when average delay is
91 mSec.
31
PacketCable 1.x Interfaces
32
Summary of Security Interfaces
Each interface is labeled as ltlabelgt ltprotocolgt
ltsecurity protocolgt / ltkey management protocolgt

IPSEC IP Security Protocol IKE- Internet Key
Exchange
33
PacketCable QoS Setup
Call Management Server
Announcement Server
Gate Controller
Announcement Controller
PacketCable DQoS
eMTA
Announcement Player
Managed IP Network
PSTN Gateway
DOCSIS 1.1 HFC Network
CMTS
Media Gateway Controller
Gates
sMTA
CM
Media Gateway
DOCSIS 1.1 Dynamic Service Flows
OSS Provisioning, Security - KDC, Record Keeping
PSTN
Signaling Gateway
34
PacketCable Call Signaling Protocols
PacketCable NCS (NCS is profile of MGCP)
Remote CMS
Call Management Server
Announcement Server
(CMS)
Announcement Controller
eMTA
Announcement Player
Managed IP Network
PSTN Gateway
DOCSIS 1.1 HFC Network
CMTS
Media Gateway Controller
sMTA
CM
PSTN
Media Gateway
OSS Provisioning, Security - KDC, Record Keeping
Call Signaling
Signaling Gateway
SS7
Note Defined in PacketCable 1.2
35
CMTS
36

• Cable Modem Termination System
• DOCSIS 1.1 or DOCSIS 2.0 required
• BPI turned on (unenforced requirement)
• New Interfaces terminating on CMTS
• Event Messaging to RKS (billing)
• Gate Control and Gate Coordination to CMS (ensure
  QoS given only to valid calls stop theft of
  service clean failure)
• Recent change Gate Coordination used to be
  separate interface
• Adding development delays
• (Network Time Protocol to NTP server)
• Pass-through specification changes for call
  signalling and bearer traffic
• e.g. MTA requests QoS for a call CMTS only
  grants request if it has been told to do so by
  the CMS -- DQoS

37
CMTS Foundation For IP Voice DOCSIS 1.1
These two features make DOCSIS 1.1 more secure.

• IP filtering
• Baseline Privacy Interface (BPI)

38
CMTS Interfaces

• Network Access Modules
• 10/100baseT
• Gigabit Ethernet
• OC-n

• RF Modules
• With Up-converter

• Control Complex
• System Control
• Fabric Control

• Additional CMTS components
• Power Modules (e.g.)

39
CMTS Architecture Carrier-Class RF Redundancy
Multiple Flexible Sparing Groups from 11 to 151
Redundant

• One RF Module sparing group with 14 or 15 actives
  and one spare

40
CMTS Wire Speed
Packet Ingress
Egress
Classify
Police
Forwarding
Queue
Scheduler
Congestion Control
IP Filter
Forwarding Policy
Microprocessor
Control Info
OAMP
OAMP
User Data Throughput Not Limited by Software
Processing Constraints
41
Architecture Carrier-Class RF Redundancy
Must support Hitless RF Redundancy for sparing

• No re-ranging or re-registering of CMs EMTAs
• CMTS design ensures CMs continue receiving SYNC
  and idle MAPs
• Service flow establishment occurs in priority
  order
• Less than 500 milliseconds for high-priority
  flows and approximately 2.5 seconds to restore
  all services flows
• VoIP (UGS) flows re-established first, ahead of
  non-real-time flows

42
Hitless Software Upgrade
Chassis Running Full-Duplex

• RF module 1 Fails over

• RF module 2 Fails over

• RF module 3 Fails over

• RF module 4 Fails over

• RF module 5 Fails over

Midplane
43
C4 CMTS Feature Hitless Software Upgrade Details

• Allows migration from current Release X.0 to X.1
• Loads new software image on stand-by control
  complex
• Uses hitless RF sparing capabilities to load
  new software image on each RF Module while the
  spare RF Module is providing service
• RF Module By RF Module is Failed Over Restored,
  until Complete
• Upgrade from Release X.1 to Release Y.0
• will require chassis reboot

Future All Major And Minor Releases Supported
44
EMTA
45

• Multimedia Terminal Adapter
• Consumer premises equipment
• Contains embedded DOCSIS 1.1 cable modem
  (standalone to follow Pc 1.3)
• Coax in, RJ11 or multiple rj11s out (typically
  supports four lines)
• Internal or external
• Utility power or battery backup (PC 1.1)
• Initial deployments residential, MDU and business
  later
• Retail model supported
• Responds to NCS signalling messages (e.G.,
  Provide dial tone, collect digits)
• Authenticates itself to network (believe who it
  is)
• Not trusted by the network
• Secure signalling and provisioning communication
  with CMS, PS, PSTN G/W
• Encrypts/decrypts bearer traffic

46
E-MTA Merging Voice and High-Speed Data
E-MTA
Configurable E-MTA Software that enables VoIP
47
E-MTA Block Diagram

• Mandatory Codec G.711 (µ-law and A-law)
• Recommended Codecs G.728 and G.729 Annex E

48
Telephony Adapter Definition

• Product is a Telephony-Only Device for
  co-deploying with Subscriber-Owned, Data-Only
  Cable Modem
• Intended for Indoor Deployment without Subscriber
  Interaction
• List of Features
• RF Coaxial Input
• 2-lines POTS

49
Indoor MTA

• DOCSIS / Euro 2.0 A-TDMA / PacketCable 1.0 Design
• 2 Lines of POTS
• 500 feet loop length (26 AWG Wire)
• 10 REN Total (Up to 5 REN per Line)
• High Speed Data
• 10/100BaseT RJ45 Ethernet Interface
• Full Speed (12Mbps) USB
• Standby and Reset Switches
• Status LEDs
• Horizontal/Vertical, Desktop/Wall Mount Options
• RF Video Terminating
• Locally AC Powered

50
Indoor E-MTA Advantages

• Pros
• Improved Capital Expense
• Lower upfront cost
• Subscriber can take ownership
• Reduces Truck Roll for replacing battery and
  basic troubleshooting
• Self install for secondary line
• Note Primary line self-install is not feasible
  in most cases
• Installation Flexibility
• Locate device where desired

51
Outdoor MTA

• Designed to meet DOCSIS 1.1 and
• PacketCable 1.1 primary line requirements
• Multi-Line Voice Services
• Quality of Service achieved with DQoS
• Up to 4 lines of telephony
• Baseline Privacy Interface (BPI) for security
• High Speed Data Services
• DOCSIS 1.1 compliant
• QoS support for advanced data services
• 2 data access options
• 10 Base-T Ethernet
• Home Phoneline Network Alliance (HPNA) 2.0
• Software upgradeable from central network
• location

52
Outdoor CPE Advantages

• Pros
• Requires less interference with subscribers
  premise
• Identical demarcation to what ILEC has today
• Operator controls the coax drop to the side of
  the house (SNR)
• Incremental revenue opportunity for inside wiring
  maintenance
• Easy transition for existing customers
• Common installation procedure with Voice Ports
• Technician does not require access inside
  subscriber premise
• Can service unit any time after initial install
• Higher confidence and reliability less service
  calls
• Network power governs availability not power
  company
• Unlikely for subscriber tampering
• Prevents inadvertent power cord unplug
• CATV relay
• One unit is sole interface for operator

53
So whats best Indoor or Outdoor?

• Need to look at specific markets
• Churn rates
• Outdoor units are never lost while indoor units
  often disappear
• New resident more likely to go with the incumbent
• What is long-term vision
• Goal is to get triple play
• What will share of Video, HSD and Telephony be?
• Install E-MTAs right from the start
• Constant reminder/advertisement
• Service
• Calls are much more difficult to schedule and
  conduct with an indoor unit

54
Network Challenges
55
Agenda

• Indoor E-MTA Overview
• Challenges of Customer Satisfaction Market
  Reputation
• Battery Life Minimize Truck Rolls
• Some Challenges of Telephony
• EMTA Web Interface
• E-MTA Power Management
• E-MTA Troubleshooting Diagnostics
• Telephony Software Tools

56
Voice Data Tornado Chart
The top variables are the most critical success
factors for the business case. 8 of the top 9
are directly influenced by Customer Satisfaction
Market Reputation
57
EMTA

• Customer Satisfaction Challenge
• Delivering value-added services is difficult
• Need to be able to support the high demand
  services in order to capitalize on the full
  potential of telephony
• Revenue Enhancement
• Full 16 Service IDs Capability
• Cost of Ownership
• Minimize Truck Rolls (e.g. customer replaceable
  batteries)
• Longer Battery Life (6-10 years versus 3-5 years)
  
• Longer eMTA Mean Time Between Failure (MTBF)

58
MTA Evolution

• Full DOCSIS 2.0 Capability
• Voice Lines
• Bridged USB/Ethernet data interfaces
• Primary Line telephony with gt 16 hours standby
• Advanced Technology Lithium-ion battery backup.

59
Long Term Product Operations Costs Li-Ion vs.
SLA
Key Expense Assumptions SLA - 10, Li-Ion - 20,
Truck Roll- 50. Also includes estimated
shipping, storage and disposal expenses
60
End to End IP Network Components
Back OfficeSystems
MTA
STP
AudioServer
Managed IP Backbone Network
Management Systems
SS7

• Servers
• Call Server
• RKS
• CALEA
• KDC

SS7 MF
Fiber Ring
Line Trunk Gateways
Router
CMTS
PSTN IXC
PSTN LEC
61
Challenges of Telephony

• Adjustable loop current level allows operators to
  provide higher off-hook DC current
• Address audible volume issues on some low-cost
  phones
• Higher supervisory voltage
• Supports features such as Message Waiting
  indicator lamps on CPE
• Line card interfaces tested and field-proven for
  support of non-compliant CPE devices
• 10 Ring equivalence (10 REN) total, 5 REN per
  line
• Multiple CPE can operate on the same line

62
Telephony Line Interface Design Considerations

• On-hook Supervisory Voltage
• Telcordia TA909 Specs as low as 21V- Adequate in
  theory, for E-MTA applications
• Short Distance Between EMTA And CPE
• Typically Set At 48V Many CPE Designed For 48V
  Because That Had Become The Typical Voltage
  From The ILECS

Higher On-hook Voltage (48V) Required To Assure
Legacy CPE Continues To Operate In A VoIP Network
63
PacketCable Availability Model
PacketCable (SA) 0.015
CMTS 99.75
Local IP
IP Backbone
HFC (DOCSIS)
NI
CM/MTA
CMTS
Edge Router
0.0025
0.0006
0.0019
0.01
0.005
0.02
(Implies No Power Failures)
Technical Report PKT-TR-VoIPAR-V01-001128 VoIP
Availability and Reliability Model for the
PacketCable Architecture
The end-to-end availability objective of the PSTN
And PacketCable networks, based upon Telcordia
documents, is 99.94, with individual elements
having the more well known value (goal) of
99.999.
UNAvailability E2E UELEMENT 1 UELEMENT 2
UELEMENT n 0.0664 (or 99.9336
Availability)
64
E-MTA MTBF Requirements
Technical Report (PKT-TR-VoIPAR-V01-001128 VoIP
Availability and Reliability Model for
PacketCable Architecture) defines a common set
of MTTR numbers for MSO equipment. A direct
access MTA is one that a service technician can
access without intervention or subscriber
obstructions Direct Access MTTR 4 hours
Otherwise MTTR 24 hours.
Availability 365 days 24 hours 60 525,600
minutes per year
65
E-MTA MTBF
Technical Report (PKT-TR-VoIPAR-V01-001128 VoIP
Availability and Reliability Model for
PacketCable Architecture) defines a common set
of MTTR numbers for MSO equipment. A direct
access MTA is one that a service technician can
access without intervention or subscriber
obstructions Direct Access MTTR 4 hours
Otherwise MTTR 24 hours.
Availability 365 days 24 hours 60 525,600
minutes per year
_at_ 99.9975
66
The Real Critical Success Factors
There Are Many Factors That Determine Success Or
Failure Of A VoIP Business Case.

• Customer Satisfaction Market Reputation
• Churn Rate
• Market Penetration
• Time to Reach Penetration Objective
• ARPU ability to maintain price points due to
  quality service
• Marketing, Customer Acquisition these costs go
  up as customer satisfaction goes down
• Customer Field Service Support
• Installation

A Sensitivity Analysis Can Determine Which
Factors Have The Most Influence Over The Entire
Business Case
67
Telephony Line Interface Trouble Considerations

• Extension-in-use Indicator Lamps dont work
• No LCD Caller ID Display
• Low Handset Volume
• No Message Indicator Light
• Fax Machines dont work properly
• No Auto-answer / Auto-dial
• No Analog Data Modems Ring Detection
• Faint Or Non-ringing Phones

Current Voltage Thresholds Could Affect Up To
8 Of Installations
68
Telephony Line Interface Design Considerations
(contd)

• Adjustable Off-Hook Loop Current
• Powers operation of most telephones
• Even units w/ auxiliary power can be dependent on
  loop current levels
• FCC regulates a minimum of 20mA
• Most Central Offices provide more than this
• Many phones expect higher off-hook currents
• Multiple phones off hook can result in low
  handset volume
• Poor wiring in older homes also a problem
• Higher Loop current, though, results in higher
  power consumption
• Drain on battery back-up units

E-MTA With Remotely Provisionable Loop Current
Boost From 20 To 40 ma Represents The Best Of
Both Worlds
69
Loop DiagnosticsImplementation

• Tests are supported through both private MIB and
  WEB GUI interfaces
• A remote automated system could initiate tests
  through SNMP MIB, then retrieve the results.
• A local technician could initiate tests by
  logging into the EMTAs maintenance WEB GUI
  locally or remotely during troubleshooting
  activities. The results would be displayed on
  the GUI and logged.

70
LED Patterns (TM402) Operation
71
Loop Fault Coverage

• Receiver Off-hook
• Line faults to ground
• Potentially hazardous voltages presence
• Number of CPE characterized (REN)
• Including detection of no CPE which could
  indicate an open line
• Characteristic Hardware faults
• Message Simulation detects any breakdown in
  provisioning or messaging between the MTA and the
  CMS

72
Touchstone Flexible, Efficient Power Management

• Operator Can Modify Battery Management Settings
  to extend back-up time
• 1st stage Data access is suspended when in
  battery power mode
• Default High Speed Data Access is suspended
  after 15 minutes
• 2nd stage During long power outages, Telephony
  Modem enters deep sleep
• No Incoming calls
• Normal operation returns if a phone goes off hook
• Significant increases (multiple days) in back-up
  time can be achieved in deep sleep mode.
• Default Deep sleep is NOT activated
• The timing for both stages are fully
  provisionable by the operator

73
Battery Telemetry Logs
ppSurvMtaPowerSupplyTele

• Normal the NIU is operating on AC power. The
  battery is charged and in good condition
• Battery Low the NIU has been operating from
  battery power, and has drawn down the battery to
  about 25 of its rated capacity
• AC power restored and the battery is recharging
• Battery Replace the battery has deteriorated to
  about 75 of its capacity and should be replaced
• Battery Low Replace the NIU has been operating
  from battery power, and has drawn down the
  battery to about 25
• The battery has deteriorated and should be
  replaced

• Shutdown Warning the NIU has nearly exhausted
  its battery power, and will lose power if AC
  power is not restored within a few minutes
• Battery Missing the battery has been removed or
  has failed in such a way to appear to be removed
• Telemetry Unavailable
• Telemetry Invalid indicates a possible problem
  with the unit or the battery system
• Battery Reversed or Shorted The battery has
  either been installed backwards or the terminals
  have been shorted.

74
Web Interface - Basic

• Basic MIB browser provides insight into
  installation issues
• Status Page
• RF Parameters
• IP/MAC addresses
• Hardware Version
• Software Version
• Event Log
• Cable Modem State

75
Web Interface - Advanced
Advanced MIB browser provides network information
to assist in detailed troubleshooting

• Detailed Product Page
• Detailed product information
• RF Parameters
• MTA/DHCP
• DHCP parameters Security Settings
• CallP/QOS
• Feature Switch List
• Config Parameters
• File Names
• Access is tightly controlled
• No link from the Basic Page
• URL must be known
• Arris password of the day is required

76
E-MTA Troubleshooting Diagnostics

• E-MTA diagnostics - reporting back to a remote
  location
• Need to evaluate key areas of the network, not
  just the E-MTA itself
• Loop diagnostics- State of customers in-home
  wiring
• State of unit Hardware
• RF connection Details
• Provisioning
• Minimizes needs for truck rolls

Diagnostics Need To Provide Information That Can
Help Expedite Repairs And Minimize Truck Rolls
77
Loop DiagnosticsFuture Implementation

• Supported via both private MIB and WEB interfaces
  
• A remote automated system to initiate tests
  through SNMP MIB, then retrieve the results
• A local technician can initiate tests by logging
  into the EMTAs maintenance GUI locally or
  remotely during troubleshooting activities. The
  results would be displayed on the GUI and logged.
  
• Receiver Off-hook detected
• Line faults to ground detected
• Potentially hazardous voltages presence detected
• Number of CPE characterized (REN)
• Including detection of no CPE which could
  indicate a line open
• Miscellaneous hardware faults detected

78
Loop DiagnosticsFuture Implementation

• The same tools that are used for internal LC
  diagnostics will also allow the external loop to
  be characterized. The hooks are already in place.
• Tip to ground short detection
• Ring to ground short detection
• Tip to ring receiver off-hook detection
• Tip to ground foreign voltage detection
• Ring to ground foreign voltage detection
• Ringer Equivalence Network characterization test
• Off-hook message simulation test

79
EMTA Telephony Software with Configuration File
Editor
80
Packet Cable Barometer
PacketCable Compliance
ARRIS EMTA with PacketACE software facilitates
adjusting to lowest common denominator to ensure
interoperability
ISTP TGCP Security Event Messaging DQOS Provisioni
ng Codec NCS
Lowest common denominator to ensure
interoperability between elements
CPE
CMS
Prov
CMTS
81
E-MTA Merging Voice and High-Speed Data
E-MTA
Configurable E-MTA Software that enables VoIP
Under Many Conditions
82
Provisionable Configuration Process
Flexibility To Work In Current Network
Environments
1) Operator creates config file with config file
editor
2) Config file is transferred to TFTP Server
3) Config file is transferred to the EMTA as part
of regular DHCP/TFTP Bootup process
5) The EMTA changes its interface with other
PacketCable network element as specified in
config file
4) Parameters in config file modify the software
in the EMTA to reflect the PacketCable features
that are to be implemented on each interface
83
Control Your Evolution to Full PacketCable

• PacketCable Based
• Telephony Modems achieved PacketCable 1.0
  Certification in CW24 CM25
• ARRIS-specific, used to configure sub-set
  PacketCable features supported by selected
  network configuration.
• ProprietaryCfgMtaCallpFeatureSwitch MIB Provides
  variations to Full PacketCable Accommodate
  ranges of partially-compliant equipment network
  configurations
• CallP Feature Switch
• MTA Feature Switch
• CM Feature Switch
• (DHCP, DNS, TFTP) Options for CMTS, cable modems
  and MTAs for 1 or 2 MACs
• IPSec may be disabled using the
  pktcMtaDevCmsIpsecCtrl MIB
• Media encryption options, stored in NVRAM
  (pktcMtaDevCmsIpsecCtrl) can be disabled
• PacketCable without KDC
• DQOS or DSX QoS Mode
• Options for Voice and Signalling Ports
• CODECs and Packetization Rates (10, 20 30 ms)
• CM MTA SW Upgrade Process

84
SNMP Co-Existence

• SNMP Co-existence is a feature that allows SNMPv1
  and SNMPv2c network management systems to
  function within the context of SNMPv3 security
  for MIB access
• The NMS can use an SNMPv1 or SNMPv2 community
  string to access the MTAs MIBs or to receive
  traps
• By adding the necessary MIBs and TLVs to the
  configuration file

85
Configuration File Editor
Multiple Templates provides operators with a
series of templates for building their own
network-specific configuration file.
86
Configuration File Editor
Add MIBS PacketACE allows an operator to edit the
configuration file by adding additional
predefined MIBS.
87
Configuration File Editor
Changing MIB Attributes The attributes of the
MIBS can also be changed
Example If your configuration requires DSx-QoS
and PHS, set the feature switch in the
configuration file SnmpMib ppCfgMtaCallpFeature
Switch.0 hexstr 01.40.00
88
PacketCable (With No KDC) Sequence
89
Global Universal Provisioning Interface GUPI
Sequence
90
Single MAC/Configuration File Sequence
91
Trouble Shooting The CM

• The following variables are located in the
  Proprietary-CM-DEVICE-MIB and provide information
  specific to cable modems
• ProprietaryCmDevWanIsolationState
• Displays and controls the state of WAN Isolation
• Data traffic passes freely between the home
  users network and the Internet.
• The home users network is isolated from the
  Internet. Data traffic does not pass between the
  home user's network and the Internet
• ProprietaryCmDevSwImageName
• The name of the software image currently
  operating on the cable modem
• ProprietaryCmDevSwImageBuildTime
• The build date and time of the software image
  currently operating on the cable modem.

92
Proprietary EMTA MIBs

• ProprietaryCfgMtaCableTvEnable- Provides the
  ability to turn the cable TV off and on
• ProprietarySurvPortLcDiagRequest- Setting this
  value to true sends a command to diagnose
• ProprietarySurvPortMaintState - The maintenance
  state of the line
• isnr, isnr-trafbsy, istrblmismatch, istrbl-fef,
  istrbl-tstf, istrbl-diag, istrbllcprt,
  oosnr-unprov, oosnr, oostrbl, oostrbltstf,
  oostrbl-diag, oostrbl-lcprt
• ProprietarySurvPortLcDiagLastResult- The last
  result of diagnostics for this line
• slac-revision-failure, mpi-failure,
  power-or-clock-failure, pcm-failure,
  standby-hook-failure, active-hookfailure,
  vf-failure, ringing-failure, invalid-state-to-init
  diags, line-is-unprovisioned, diagnostics-resultsp
  ending
• ProprietarySurvMtaPowerSupplyTele- The battery
  telemetry state
• tlm-unavailable, tlm-invalid, tlm-shutdown-warnin
  g, tlm-batt-reversed-shorted, tlmbatt-low-replace-
  ac-fail, tlm-batt-low-replace, tlm-battlow-ac-fail
  , tlm-batt-low, tlm-batt-missing,
  tlm-ac-failbatt-replace, tlm-replace-batt,
  tlm-ac-fail, tlm-normal
• ProprietarySurvMtaMaintState-The maintenance
  state of the PacketPort
• isnr, istrbl, oos

93
Summary

• E-MTA Key Characteristics for Maximizing
  Acceptance and Minimizing Expense
• Robust line interface that accommodates variety
  of cpe
• Robust design that delivers high reliability
• Flexibility that facilitates network integration
• An E-MTAs capabilities impact the services an
  operator can deliver
• Not simply a terminating device but a client for
  enabling service

An E-MTAs Design And Functionality Are A Major
Factor In Maximizing Profitability For Operators
94
Multi-Vendor/Product/Protocol Integration Issues
Pieces of the may be puzzle missing
Fault Isolation equipment doesnt work who
owns?
IP Management
SS7 GW
CALEA Server
CMS
Missinghooks
NMS
Service Activation
PacketCable Provisioning
Media Server
KDC
Different size pieces from each vendor
RKS
PSTN Media GW
Vendors at different stages of PC compliance
Packet Cable spec changes
Frequent s/w rev changes
How to assemble all pieces and ensure it works?
95
Interoperability Levels

• Full Solution Integration Deployment Verified
• Alarm Surveillance and Telemetry
• Full CLASS features and interaction
• On-Net and Off-Net calling
• Network impairment performance testing
• Network fault insertion and recovery
• Dead system recovery
• System capacity loading
• High Traffic Runs - completion rates and test to
  fail
• Interface to Operational Support Systems

Upon successful completion, the solution should
meet the criteria for operational reliability and
scalability necessary for full scale commercial
deployment
96
Solutions Require Network Components
Interoperability
Billing Mediation
IP Management
SS7 GW
CMS
CALEA Server
Service Activation
NMS
RKS
PacketCable Provisioning
Media Server
PSTN Media GW
KDC
Letting Partners integrate solution de-risks
program
97
Quiz

• What are the drivers for IP telephony?

• Describe the network components that are
  necessary for IP Telephony on HFC.

• What are two ways for the IP telephony access
  network to interface with the PSTN?

• Discuss alternative ways to offer telephony, and
  the advantages and disadvantages of each

• Regarding reliability, what are the differences
  between PacketCable standards and traditional
  voice services?

• What is the most critical part of the network
  regarding the reliability of the telephony
  services?