PacketCable Networks VoIP Over HFC. Al McNichol Sr. Manager, Sales Engineering Broadband Division Atlanta, Ga.

Transcription

1 PacketCable Networks VoIP Over HFC Al McNichol Sr. Manager, Sales Engineering Broadband Division Atlanta, Ga.

2 AGENDA PacketCable 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 2

3 Today- Constant Bit Rate (TDM) Voice Over HFC Network Architecture Class 5 SWITCH TR-303 DS-1s DS-1/ E-1 MPR DS-1/ E-1 MPR TXC TIC AIC TXC TIC AIC m a p p e r HDT MODEM c o n t r o l l e r HFC NIU MODEM LC Broadcast TDM/PCM Digital TDM to PCM AM - VSB HFC QPSK/QAM IP/ TDM/ TDMA Digital QPSK 3

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 (>100,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. 4

5 Migration- Circuit Switched to VoIP LEC IXC Circuit Switched Backbone Network SONET CLASS 5 LDS GR303 Reverse Gateway HDT Voice Ports Circuit Switched in the Access OSS Regional Data Network Metro Optical Transport Element Manager Audio Server SS7 STP Call Server Core Router SS7 + MF Trunk Gateways Other Internet POP Switch/ Routers IP CMTS IP over HFC DOCSIS 1.0 / 1.1 Cable Modems, emtas & Set top Boxes LEC IXC 5

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 7

8 DOCSIS/PacketCable Specifications Video NSI Managed Backbone MTA CMTS BPI+ RFI Core Router Data Combiner Splitter Fiber Cable T h e Coax Cable Drop Cable Fiber Node Transceiver Optical Transceiver PacketCable/VoIP 8 Voice Power Node Power Passing Tap CMCI

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 Any given specification may contain portions of any 1.X architecture PacketCable Multimedia 9

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 => specialized boxes >2,000 pages specs/tech reports/testing requirements Future PacketCable 2.x? 10

11 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 11

12 PacketCable 1.1 Specifications PacketCable Management Event MIB PacketCable Embedded MTA Primary Line Support PacketCable Management Event Mechanism NEW PacketCable Electronic Surveillance PacketCable Audio Server Protocol Specification 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 1.1 Technical Reports PacketCable Line Control Signaling System Architecture PacketCable Management Event Identifiers VoIP Availability and Reliability Model for the PacketCable Architecture PacketCable Electronic Surveillance Call Flows Technical Report 12 This also includes, specifically, availability during power failure at the customer's premises and (assuming the service is used to connect to the PSTN) access to emergency services (911, CALEA, etc.).

13 PacketCable 1.2 Specifications PacketCable Call Management Server Signaling PacketCable Inter-domain Quality of Service PacketCable 1.2 Technical Reports PacketCable 1.2 Architecture Framework 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-toend 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. 13

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 14

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. 15

16 Relationship to Other Projects Framework for future CableLabs projects PacketCable is a set of protocols developed to deliver Quality of Service enhanced communications services using packetized data transmission technology to a consumer s home over the cable network. PacketCable utilizes a network superstructure that overlays the two-way data-ready cable television network. 16 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.

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 17

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 19

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 20

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. 21

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

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 23

24 Full PacketCable Event Sequence 24

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 Call Waiting Cancel Call Waiting (*70) Call Waiting Deluxe Access to Telecommunications Relay Service (TDD) 25 Intercept Routing for blank/changed/etc. ph#s 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 - Don t 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 Line Number Portability Remote Activation of Call Forwarding (RACF) Outside Calling Area Alerting (OCAA)

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. 26

27 PacketCable Telephony PacketCable is first complete end-to-end telephonyover-ip architecture for any industry Billing interface Provisioning Interface to PSTN Security (for user and MSO) Toll quality (G.711) Support for data modems and faxes Supports inter-mso fully-ip calls CALEA Support for systems using Class 5 switch instead of pure IP 27

28 PacketCable Architecture Embedded MTA Client MTA Cable Modem emta HFC Access Network (DOCSIS) CMTS Call Management Server Announcement Server Announcement Controller Managed IP Network Announcement Player PSTN Gateway Embedded MTA Client MTA Cable Modem emta HFC Access Network (DOCSIS) CMTS Media Gateway Controller Media Gateway Signaling Gateway PSTN RKS/OSS Servers 28

29 Alternative Access Methods Telephony Switching Sub - system Application Servers SMTA ERMG Alternative Access Networks: Multi - service Metropolitan Network Wireless Access Non - managed IP networks Media Servers Audio Server UM Server Conference Server CALEA RKS KDC SG Pre Paid Server SMS Server LAN Video Comm Server CMS MGC STP EMTA EMTA HFC Access Network DOCSIS 1. 1 CMTS Managed IP/MPLS Network MG Public Telephone Networks DNS/DHCP TFTP ToD OSS Tools LDAP 29 Back Office Servers OSS Sub - system

30 Voice Quality Metric Target Fail RTP Packet Jitter Less then 30ms Above 80ms RTP Packet loss 1% 8% RTP QoS 100% 85% Physical layer packet errors? None Adversely affects QoS Excessive collisions Not to affect QoS Adversely affects QoS IP Transport layers packet errors? None Adversely affects QoS 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 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. 30

31 PacketCable 1.x Interfaces pkt-rtp1: Encoded voice, video, and fax Media flow between MTAs pkt-rtp3: Media flow between the MG and the MTA. Includes, for example, tones, announcements, and PSTN media flow sent to the MTA from the Media Gateway. 31

32 Summary of Security Interfaces Each interface is labeled as: <label>: <protocol> { <security protocol> / <key management protocol> } IPSEC IP Security Protocol IKE- Internet Key Exchange 32

33 PacketCable QoS Setup MTA smta emta CM CM DOCSIS 1.1 HFC Network Call Signaling QoS Setup 33 CMTS Gates Gate Setup (Policy Push) QoS Request DOCSIS 1.1 Dynamic Service Flows PacketCable DQoS Call Management Server Gate Controller Managed IP Network OSS: Provisioning, Security - KDC, Record Keeping Announcement Server Announcement Controller Announcement Player PSTN Gateway Media Gateway Controller Media Gateway Signaling Gateway PSTN

34 PacketCable Call Signaling Protocols PacketCable NCS (NCS is profile of MGCP) Call Management Server CMSS (SIP 2.0 w/extensions) Remote CMS (CMS) Announcement Server Announcement Controller MTA smta emta CM CM Call Signaling DOCSIS 1.1 HFC Network MTA to CMS CMS to MGC MG to PSTN CMS to SG MGC to SG CMTS SG to SS7 MGC to MG CMS to CMS Managed IP Network OSS: Provisioning, Security - KDC, Record Keeping Note: Defined in PacketCable 1.2 ISTP / TCAP CMSS (SIP 2.0) Announcement Player PSTN Gateway Media Gateway Controller Media Gateway Signaling Gateway ISTP / ISUP ISTP / TCAP TGCP ISUP / TCAP PSTN MF Signaling (In-Band) SS7 34

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 36

37 CMTS Foundation For IP Voice DOCSIS 1.1 IP filtering Baseline Privacy Interface + (BPI+) Packet classifiers Service flow policing Multiple upstream service types (i.e., UGS, UGS/AD, rtps, nrtps, BE) Differentiated service class support Upstream packet fragmentation Upstream packet concatenation Payload header suppression (PHS) DSx Dynamic Service Add/Chg/Del Advanced MIB support These two features make DOCSIS 1.1 more secure. These four features support DOCSIS 1.1 QoS and differentiated services. These four features make DOCSIS 1.1 downstream and upstream channels more efficient. e.g. DOCSIS 1.1 CMTS Support for 1.0 CM 37

38 CMTS Interfaces Network Access Modules 10/100baseT Gigabit Ethernet OC-n RF Modules With Up-converter Power Module A Midplane Power Module B Additional CMTS components Power Modules (e.g.) Control Complex System Control Fabric Control 38

39 CMTS Architecture Carrier-Class RF Redundancy Multiple Flexible Sparing Groups from 1+1 to 15+1 Redundant Power Module A Power Module B Midplane One RF Module sparing group with 14 or 15 actives and one spare

40 CMTS Wire Speed Packet Ingress Egress Scheduler Queue Forwarding Forwarding Policy Congestion Control Police IP Filter Classify Microprocessor Maintenance Controller OAM&P Software Maintenance Controller OAM&P Software Driver 40

41 Architecture Carrier-Class RF Redundancy No re-ranging or re-registering of CMs & EMTAs Must support Hitless RF Redundancy for sparing 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-realtime flows 41

42 Hitless Software Upgrade Chassis Running Full-Duplex 1 st then 2 nd SCM/FCM Pair Loaded Network Modules Upgraded Power Module A Power Module B Spare RF Module Upgraded 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 RF Module SPARE RF Module Active RF Module Active RF Module Active RF Module Active RF Module Active Midplane FABRIC SYSTEM

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 43

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 45

46 E-MTA: Merging Voice and High- Speed Data E-MTA USB Ethernet MTA Hardware MTA Software Cable Modem Cable Software Modem Hardware Cable Modem Firmware RJ-11 RJ-11 Configurable E-MTA Software that enables VoIP 46

47 E-MTA Block Diagram Mandatory Codec G.711 (µ-law and A-law) Recommended Codecs G.728 and G.729 Annex E 47

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

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 49

50 Indoor E-MTA Advantages Pros 50 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 51

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 52

53 So what s 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 53

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 55

56 The top variables are the most Voice & Data Tornado critical success Chart factors for the business case. 8 of the top 9 are directly influenced by Customer Satisfaction & Market Reputation Surprisingly, Capex items have a much smaller impact on the business case 56

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) 57

58 MTA Evolution Full DOCSIS 2.0 Capability # Voice Lines Bridged USB/Ethernet data interfaces Primary Line telephony with > 16 hours standby Advanced Technology Lithiumion battery backup. 58

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 59

60 End to End IP Network Components Back Office Systems MTA Management Systems SS7 Managed IP Backbone Network HFC Audio Server Power Node STP Servers: r Call Server RKS CALEA KDC SS7 + MF Fiber Ring Line Trunk Gateways Router CMTS PSTN LEC 60 PSTN IXC

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 61

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 62

63 PacketCable Availability Model (Implies No Power Failures) Technical Report PKT-TR-VoIPAR- V : 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 %. UNAvailability E2E = UELEMENT 1 + UELEMENT UELEMENT n = % (or ~ % Availability) 63

64 E-MTA MTBF Requirements Technical Report (PKT-TR-VoIPAR-V 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 MTBF MTA Availability = Reference MTTR + MTBF = 100% % = % [ Therefore, Unavailability = min / yr ] Direct Access Delayed Access MTBF MTBF = 525, = 525, min/yr [ Therefore, MTBF = 7.99 years ] = 525, = 525, min/yr [ Therefore, MTBF = years ] 64

65 E-MTA MTBF Technical Report (PKT-TR-VoIPAR-V 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 % MTBF MTA Availability = Reference MTTR + MTBF = 100% % = % [ Therefore, Unavailability = min / yr ] Direct Access Delayed Access MTBF MTBF = 525, = 525, min/yr [ Therefore, MTBF = 7.99 years ] = 525, = 525, min/yr [ Therefore, MTBF = years ] 65

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 66

67 Telephony Line Interface Trouble Considerations Extension-in-use Indicator Lamps don t work No LCD Caller ID Display Low Handset Volume No Message Indicator Light Fax Machines don t 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 67

68 Telephony Line Interface Design Considerations (cont d) 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 68

69 Loop Diagnostics Implementation 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 EMTA s maintenance WEB GUI locally or remotely during troubleshooting activities. The results would be displayed on the GUI and logged. 69

70 LED Patterns: (TM402) Operation 70

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 71

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 72