Video Over DOCSIS. (VDOC) Tutorial. Video Over DOCSIS. (VDOC) Tutorial. Speakers: Byju Pularikkal, Jeff Riddel Cisco Systems Inc.

Transcription

1 Video Over DOCSIS Video Over DOCSIS (VDOC) Tutorial (VDOC) Tutorial Speakers: Byju Pularikkal, Jeff Riddel Cisco Systems Inc. 1

2 Acronyms/Abbreviations AM = Application Manager AS = Application Server ASM = Any Source Multicast BG = Bonding Group CIN = Converged Interconnect Network = Cable Modem TS = Cable Modem Termination System COPS = Common Open Policy Service DBC = Dynamic Bonding Change DEPI = Downstream External PHY Interface DIBA = DOCSIS IPTV Bypass Architecture DOCSIS = Data-Over-Cable Service Interface Specification DQoS = Dynamic QoS DRFI = Downstream Radio Frequency Interface DS = Downstream DSID = Downstream Service Identifier DTI = DOCSIS Timing Interface EQAM = Edge QAM FN = Fiber node GMAC = Group Media Access Control HFC = Hybrid Fiber Coaxial HSD = High Speed Data I-TS = Integrated TS IGMP = Internet Group Management Protocol IPTV = IP TeleVision M-TS = Modular TS MDF = Multicast DSID based Forwarding MLD = Multicast Listener Discovery MSO = Multiple Service Operator PM = PacketCable Multimedia PS = Policy Server RF = Radio Frequency RSVP = Resource reservation Protocol SF = Service Flow SRM = Session & Resource Manager SSM = Source Specific Multicast STB = Set-Top Box TP = TelePresence US = Upstream VDOC = Video over DOCsis VoD = Video On Demand VoIP = Voice over IP 2

3 Agenda Video over DOCSIS (VDOC) Technology Introduction VDOC Technology Key Drivers DOCSIS High Level Overview DOCSIS 3.0 Multicast Enhancements PM High Level Overview VDOC Architectures TS Bypass Architecture for VDOC TS Direct Architecture for VDOC Scaling the DOCSIS Network for Video TelePresence over DOCSIS Overview Summary/Q & A 3

4 Video Over DOCSIS VDOC Technology Introduction (VDOC) Tutorial 4

5 What is VDOC? VDOC stands for Video over DOCSIS The technology covers aspects of IP based video services over the same cable infrastructure used today for high speed data and Voice over IP services Today high speed Internet subscribers receiving Internet based video content is indistinguishable to the cable operator from other types of data traffic (commonly referred to as over-the-top video). As a result of this QoS for video is not easily achievable nor a means for preventing the duplication of traffic when multiple subscribers are viewing the same video content 5

6 What is VDOC? Contd.. Three aspects of video content streaming are covered Video on Demand (VoD) Broadcast Video (i.e. IPTV) Video Telephony and TelePresence Provides DOCSIS QoS to video streams Managed video service delivered via IP to the home Provides cost effective broadcast video solution VoD is unicast Broadcast video is multicast IP end points PC, STB, TelePresence End Point 6

7 Video Over DOCSIS VDOC Key Technology Drivers (VDOC) Tutorial 7

8 VDOC Key Technology Drivers With the introduction DOCSIS 3.0, Cable Operators are able to support much higher service tiers such as 100 Mbps bidirectional These higher tiers equip operators with the transport mechanism to offer new IP based video services Unified network infrastructure for providing triple services Use of common infrastructure for triple play services results in reduced CAPEX and OPEX Deliver IPTV services to multiple devices including TVs and PCs and Mobile devices Exponential Growth in Internet based video content 8

9 Video Over DOCSIS DOCSIS High Level Overview (VDOC) Tutorial 9

10 DOCSIS Data Over Cable Service Interface Specification (DOCSIS) Radio Frequency Interface Specification provides minimum recommended technical performance requirements for data Defines interface requirements for cable modems involved in high-speed data (HSD) distribution over cable television system networks 10

11 Basic Cable System Topology Modem Fiber Node TS Servers: Provisioning Cache Web Internet Note: E/O and O/E refer to the Electrical to Optical conversion of the signals in a cable HFC system 11

12 Integrated-TS Logical Functions I-TS Wide Area Network DOCSIS MAC and upper layer protocols DS PHY US PHY Hybrid Fiber- Coax Network (HFC) 12

13 Modular-TS Logical Functions DTI DOCSIS Timing Server M-TS Core Wide Area Network DOCSIS MAC and upper layer protocols US PHY DEPI M-TS EQAM DS PHY DRFI Hybrid Fiber- Coax Network (HFC) 13

14 M-TS Components EQAM (Edge QAM Device): System with multiple Gigabit Ethernet interfaces on the input side and multiple QAM modulators and upconverters on the output side M-TS Core: Contains the DS MAC and all the initialization & operational DOCSIS related software. In the future US receivers may be external to the M-TS core DTI (DOCSIS Timing Interface) Server: Provides a Common Frequency of MHz and a DOCSIS time stamp to M-TS elements ERM (Edge Resource Manager): Manages the dynamic assignment of QAM channel resources to TS mac domains 14

15 DOCSIS 3.0 Introduction Series of Specifications that define the third generation of high speed data over cable systems DOCSIS 3.0 Addresses the following service goals increasing channel capacity, enhancing network security, expanding addressability of network elements, and deploying new service offerings 15

16 DOCSIS 3.0: Ideal for Video Channel Bonding Faster speeds provide competitive advantage for cable operators Fatter pipes enable greater efficiency Multicast Enhancements IPv6 Deliver linear IPTV via static or dynamic multicast Scale IP addresses for IP set-tops and other devices Converged Network Operate one network for all services 16

17 What is downstream channel bonding? An MLPPP like technology Each packet is tagged with a sequence number and a re-sequencing index: The sequence number is used to place packets back in order The re-sequencing index (DSID downstream service ID) is used so that each flow, or group of flows, could be resequenced independently 17

18 DS Channel Bonding ( Contd..) P3 P2 P1 TS Sequencing Distribution DBG: D1 D2 D3 Resequencing P3 P2 P1 With DOCSIS 3.0, the TS distributes a stream of downstream packets to a set of channels called a Downstream Bonding Group (DBG). The TS usually sequences bonded packets by marking them with a packet sequence number. Bonded packets may arrive at the out of sequence order. The resequences bonded packets and emits them in packet sequence order. 18

19 Channel Bonding creates efficiency gains Big Channel Packing Advantage Channel capacity SD HD SD SD SD No more room for HD HD HD SD 10 SD + 5 HD HD streams SD SD HD SD SD SD additional HD HD streams HD HD SD SD SD SD HD 10 SD + SD SD 5 HD HD streams HD SD HD SD SD SD Unbonded channels create inefficient boundaries Bonding drives efficient Packing Benefit varies MPEG2/4 HD/SD mix Bonding group size 4 separate QAM channels 4-channel bonding group 19

20 DOCSIS 3.0 Channel Bonding DS bonding group shared by all services with 8x4 Bonding Group 1 Service Group 1 Video Headend HSD/VoIP/IPTV IPTV System TS Internet Integrated or Modular Bonding Group n STB / PC STB / PC Service Group n STB / PC VoIP System HSD/VoIP/IPTV STB / PC STB / PC STB / PC 20

21 DOCSIS 3.0 Channel Bonding Concepts A is unaware of the concept of bonding groups; it is only aware of the set of downstreams it must tune to and the flows it must forward, as instructed by the TS A can receive traffic from multiple BGs simultaneously Bonding groups may have different aggregate BW based on services supported Different s in a Service Group can receive traffic from different bonding groups may tune to a subset of the downstreams configured for a SG Number of receive channels on does not need to equal number of RF channels allocated to DOCSIS service (HSD/VoIP/IPTV) 21

22 Bonding Group Selection A can receive traffic from multiple BGs Operator can steer flows to particular BGs by configuring Service Flow attributes for each BG TS uses SF-attributes when selecting BG for a flow Operator could choose to set aside a BG for Cable IPTV and a separate BG for HSD/VoIP 22

23 DOCSIS 3.0 Channel Bonding Separate DS bonding groups for HSD/Voice and IPTV HSD/VoIP Service Group 1 Video Headend IPTV System TS IPTV Internet Integrated or Modular IPTV STB / PC STB / PC Service Group n STB / PC VoIP System HSD/VoIP STB / PC STB / PC STB / PC 23

24 Video Over DOCSIS DOCSIS 3.0 Multicast Enhancements (VDOC) Tutorial 24

25 DOCSIS 3.0 Multicast Features SSM and IGMPv3 IPv6 multicast support (pre and post registration) Multicast QoS Support for bonded multicast Support for multicast authorization Multicast encryption Backward compatibility with legacy DOCSIS devices Explicit tracking of multicast listeners 25

26 DOCSIS 3.0 Multicast Architecture No IGMP snooping in the DSID label used to identify a replication of a multicast stream TS has complete control of multicast forwarding in the via DBC messaging Multicast filtering and replication within the Based on DSIDs GMAC promiscuous operation 26

27 Multicast DSID forwarding (MDF) support 27

28 Video Over DOCSIS PM High Level Overview (VDOC) Tutorial 28

29 PacketCable Multimedia Improved way of obtaining QoS! Signaling Agnostic More Generic compared to PacketCable Telephony Does not address application specifics (i.e. signaling, provisioning) MSO generated Policy Controls Dumb devices = less $$ 29

30 PacketCable Multimedia Prescribes how DQoS and BW can be used to create services that are formidable competitive weapons. Provides a generic application framework for enabling cable QoS for non-qos-aware devices. Soft-phones X-Box/Playstation gaming consoles Residential S-MTA Business-class IADs, IP Phones Builds upon DOCSIS and PacketCable, enabling numerous voice, video, and data applications: Bandwidth on Demand Video Telephony Low-latency Gaming IM/Chat with QoS voice and video Gaming with Audio/Video Presence-based voice/video Also can be used in conjunction with Deep Packet Inspection (DPI) devices 30

31 PM Architecture 31

32 PM client types Client type 1: (*) Policy is pushed to the TS, TS establishes the resources. Referred to as QoS unaware clients. Client type 2: Policy is pushed to the TS, endpoint requests resources from the TS. Referred to as Push model clients. Client type 3: Policy is pulled from the Policy Server by the TS, triggered by an RSVP request from the endpoint. Referred to as Pull model clients. * Currently, only Client type 1 is fully defined in the PM specifications. 32

33 Application Server (AS) Handles multimedia session requests on behalf of the client. AS may or may not be managed by the MSO. Protocol used between client and AS unspecified. 33

34 Application Manager (AM) Handles client requests either directly or via AS. The AM authenticates and authorizes client (or AS) requests based on predefined policies. Protocol between client and AM unspecified. Protocol between AS and AM is defined by PM (SOAP/XML). The AM determines the particular QoS parameters necessary to deliver the service to the client; could be specific or generic. It then sends a request for these resources to the appropriate Policy Server 34

35 Policy Server (PS) Takes service requests from the AM and converts them to resource policy requests used to set up TS QoS resources. PS implements MSO defined authorization and resourcemanagement rules. (examples include limits on number of gates per subscriber, types of QoS authorized for a given subscriber, limits on the impact of service on the TS, etc.) Policy servers can be deployed in a hierarchical topology to satisfy scalability and redundancy concerns PS can be stateful or stateless ; if stateful can keep track of gates and resources. Protocol between AM and PS is COPS. 35

36 TS Policies can be pushed to the TS from the PS or pulled from the TS to the PS Since currently only client type 1 is defined they will always be pushed. Thus DOCSIS DSX message transactions will always initiate from the TS TS can track DOCSIS resources based upon volume and time requirements. 36

37 Sample Signaling Flow Part I 37

38 Sample Signaling Flow Part II 38

39 Video Over DOCSIS VDOC Architecture (VDOC) Tutorial 39

40 VDOC Architecture Two different architectures TS Bypass TS Direct 40

41 Video Over DOCSIS TS Bypass Architecture for VDOC (VDOC) Tutorial 41

42 TS Bypass Solution - Overview Also referred to as DIBA DOCSIS IPTV Bypass Architecture One (or more) cable modem tuners dedicated to IPTV service (under control of Bypass System) Two entities controlling the modem (Bypass System and TS) Multiple tuners required per cable modem Channel change signaled from IP Set-top box to Bypass SRM/ ERM Utilizing upstream channel from cable modem to TS DOCSIS Framer/Edge QAM performs IGMP join as instructed by Bypass SRM/ERM and forwards multicast video to IP Settop box via Bypass channel TS is unaware of Bypass channels EQAMs don t need to be DOCSIS 3.0 capable 42

43 TS Bypass Solution Internet IPTV System M-TS Core Downstream Channels DTI Server EQAM f1 f2 f3 f4 Bonding Group w/ 3ch Bonding Group w/ 4ch f1 f2 f3 f4 HSD-only subscriber registers to 4-ch bonding group IP Network Upstream Channels HSD + IPTV subscriber Video Source Bypass SRM/ERM EQAM w/ DOCSIS Framer f(bp-1) f(bp-n) Bypass Channels (1-n) f1 f2 f3 f(bp-x) STB registers to 3-ch bonding group DOCSIS Downstream DOCSIS Upstream Bypass Channel 43

44 TS Bypass Solution Example: Multicast Video Internet IPTV System M-TS Core Downstream Channels DTI Server EQAM f1 f2 f3 f4 Bonding Group w/ 3ch Bonding Group w/ 4ch f1 f2 f3 f4 HSD-only subscriber registers to 4-ch bonding group IP Network Upstream Channels HSD + IPTV subscriber Video Source f1 f2 f3 Bypass SRM/ERM DOCSIS Framer EQAM f(bp-1) f(bp-n) Bypass Channels (1-n) f(bp-x) IP STB registers to 3-ch bonding group DOCSIS Downstream DOCSIS Upstream Bypass Channel Session Signaling Multicast Video 44

45 TS Bypass: Architecture and implementations caveats Custom Cable Modems Proprietary EQAM Non-DOCSIS 3.0 operation Multicast, DBC etc Need for Bypass SRM Network Silos Inability to re-purpose network capacity for other services Inability to dynamically share bandwidth across different MSO-managed services based on business rules Operational complexity Bypass cost savings only applicable to IPTV service 45

46 Video Over DOCSIS TS Direct Architecture for VDOC (VDOC) Tutorial 46

47 TS Direct Solution for VDOC TS Direct Architecture Modular/Integrated TS with DOCSIS 3.0 Downstreams All applications are routed through D3.0 TS All control plane signaling is routed through D3.0 TS D3.0 TS provides cable modem/set-top box registration, configuration, etc. Build a TS platform that: Provides all features for all services with one common transport Is based on existing DOCSIS 3.0 and M-TS specifications Is highly scalable Provides a price point per downstream that is competitive with existing video infrastructures 47

48 TS Direct Solution (M-TS model) IPTV System DTI Server Bonding Group w/ 4ch Internet IP Network M-TS Core Downstream Channels EQAM f1 f2 f3 f4 f1 f2 f3 f4 HSD only subscriber Upstream Channels Video Source f1 f2 f3 f4 IP STB HSD + IPTV subscriber DOCSIS Downstream DOCSIS Upstream 48

49 TS Direct Solution Example: Multicast Video IPTV System DTI Server Bonding Group w/ 4ch Internet IP Network M-TS Core Downstream Channels EQAM f1 f2 f3 f4 f1 f2 f3 f4 HSD only subscriber Upstream Channels Video Source f1 f2 f3 f4 IP STB HSD + IPTV subscriber DOCSIS Downstream DOCSIS Upstream Session Signaling Multicast Video 49

50 TS Direct Solution with Dedicated IPTV DS Channels IPTV System DTI Server Bonding Group w/ 3ch Bonding Group w/ 4ch Internet IP Network M-TS Core Downstream Channels EQAM f1 f2 f3 f4 f(iptv-1) f(iptv-n) f1 f2 f3 f4 HSD only subscriber Upstream Channels Video Source IPTV DS Channels (1 n) f1 f2 f3 f(iptv-x) IP STB HSD + IPTV subscriber DOCSIS Downstream DOCSIS Upstream IPTV DS Channel 50

51 TS Direct Solution with Dedicated IPTV DS Channels IPTV System DTI Server Bonding Group w/ 3ch Bonding Group w/ 4ch Internet IP Network M-TS Core Downstream Channels EQAM f1 f2 f3 f4 f(iptv-1) f(iptv-n) f1 f2 f3 f4 HSD only subscriber Upstream Channels Video Source IPTV DS Channels (1 n) f1 f2 f3 f(iptv-x) IP STB HSD + IPTV subscriber DOCSIS Downstream DOCSIS Upstream IPTV DS Channel Session Signaling Multicast Video 51

52 RF Spanning A set of downstreams can be split to multiple/all SGs served by the TS Similar to broadcast QAMs, but limited to s served by a TS Downstreams use same RF frequencies in each SG The cost of these downstreams is amortized across multiple SGs Useful for initial deployments where penetration rate may be low IPTV clients may be lightly distributed across multiple SGs Operator can deploy a handful of downstreams to start IPTV service When combined with static multicast, can replicate a broadcast style architecture 52

53 RF Spanning Initial low-penetration IPTV deployments HSD/VoIP Service Group 1 Video Headend IPTV System TS RF Spanning Internet Integrated or Modular IPTV PC PC Service Group n STB / PC VoIP System HSD/VoIP PC PC STB / PC 53

54 D30 Multicast for Linear IPTV Popular channels (1->x): to all subs Long-tail (x->y): only to active viewers Viewership 1 x Channel Rank y Statically RF spanned Dynamic Narrowcast 54

55 Bonded Static Multicast A BG is RF-spanned to all SGs and carries multicast IPTV streams IPTV streams are delivered at all times as static multicast flows regardless of viewership Most popular content can be carried in a 4-channel BG Long-tail content is carried over narrowcast BGs Subset of receive channels on are statically tuned to this RFspanned BG to receive multicast IPTV streams Trade-offs The cost of the RF-spanned downstreams is amortized across multiple SGs Less spectrum efficient than narrowcast BGs if all static multicast IPTV streams are not viewed by at least one in each SG at all times Requires s with additional receive channels The number of video streams that can be carried in such fashion is dependent on number of receive channels available on and spectrum availability 55

56 DOCSIS 3.0 Channel Bonding DS bonding group shared by all services with 8x4 Popular TV channels are replicated to Video Headend each Service Group IPTV System TS Bonding Group 1 HSD/VoIP/IPTV Service Group 1 Internet Integrated or Modular Bonding Group n STB / PC STB / PC Service Group n STB / PC VoIP System HSD/VoIP/IPTV 35 SG s require 280 DS channels STB / PC STB / PC STB / PC 56

57 Static Multicast w/ RF Spanning Popular TV channels are broadcast on single RF-spanned Video Headend bonding group to all Service Groups IPTV System TS HSD/VoIP/ Narrowcast IPTV RF Spanning Service Group 1 Internet Integrated or Modular Broadcast IPTV STB / PC STB / PC Service Group n STB / PC VoIP System HSD/VoIP/ Narrowcast IPTV 35 SG s require 144 DS channels RF spanning saves 136 DS channels (48.5%) STB / PC STB / PC STB / PC 57

58 Static Multicast with tuning A set of downstreams carrying multicast IPTV streams are RFspanned across all SGs These downstreams are not bonded The IPTV streams are delivered at all times as static multicast flows regardless of viewership Receive channels on can be dedicated to tune to one of these RF-spanned downstreams to receive a multicast IPTV stream can forward one IPTV stream from each receive channel Trade-offs The cost of the RF-spanned downstreams is amortized across multiple SGs Number of IPTV streams that can be part of static multicast line-up is not limited by the number of receive channels Less spectrum efficient than narrowcast BGs if all static multicast IPTV streams are not viewed by at least one in each SG at all times Requires s with additional receive channels, and independent tuning capability (or large capture window) 58

59 Static Multicast with Tuning HSD/VoIP/ Narrowcast IPTV Service Group 1 Video Headend IPTV System TS RF RF Spanning Spanning Internet Integrated or Modular Broadcast IPTV (non-bonded) STB / PC Service Group n STB / PC STB / PC VoIP System HSD/VoIP/ Narrowcast IPTV STB / PC STB / PC STB / PC 59

60 Multicast Video over DOCSIS Dynamic Multicast IGMP Join IP Network Multicast Video Source TS EQAM D30 IP STB Notes: TS dynamically forwards multicast video streams based on IGMP traffic from STB Entitlement is performed prior to STB issuing IGMP join TS configured with BW per multicast group address (CLI or SNMP) 60

61 Scaling the DOCSIS Network for Video 61

62 Scaling the DOCSIS Network for Video IP Statistical Multiplexing with VBR Video Utilize TS capabilities to deliver more video streams in less bandwidth Dynamic Bandwidth Sharing Increase bandwidth utilization for all services Admission Control and QoS Reserve DOCSIS bandwidth and ensure video quality Cable Modem Load Balancing Support multiple bonding groups per Service Group as IPTV grows 62

63 Efficiency Gains from VBR Video Support 40 60% more streams with VBR video Law of large number works in favor of VBR statmux in fat pipe 63

64 Delivering VBR Video over DOCSIS Networks Fat Pipe Asynchronous TS QoS Convergence DOCSIS 3.0 Channel Bonding 100ms CPE Jitter Tolerance Shaping Priority Service / Device ds1 ds2 ds3 ds4 ds5 ds6 Forwarder Queues High Medium Normal Low Transmission Queue Law of large numbers 60ms TS jitter No transrating 100% BW utilization 64

65 VBR Video over DOCSIS with IP Statmuxing Unprecedented bandwidth efficiency Up to 50% more streams than CBR video (with 4-channel bonding) 100% bandwidth utilization for convergence Cost effective & scalable TS queuing instead of transration Scalability independent of codec complexity Low latency Encryption agnostic Superior picture quality CBR VBR w. MPEG Statmux VBR Video over DOCSIS 65

66 VBR over DOCSIS: Packing Efficiency 66

67 Dynamic Bandwidth Sharing Data and video services delivered in shared bonding group Data service sponges excess bandwidth not used by video Data Average bitrate video Video 67

68 Dynamic Bandwidth Sharing Bonding Groups may overlap across a set of downstreams For overlapping BGs, a portion of the BW of each downstream is allocated to each BG via configuration TS is capable of dynamically sharing bandwidth across overlapping bonding groups based on the services consumed by the s receiving the BGs Enables the deployment of a mix of s with different number of receive channels Example: Deployment of 8-channel s doesn t require separate set of RF channels from those used for 4-channel s. 68

69 Dynamic Bandwidth Sharing with Overlapping Bonding Groups BG 1.1 Service Group 1 Video Headend IPTV System TS BG 1.2 BG 1.3 Internet Integrated or Modular BG n.1 STB / PC STB / PC Service Group n STB / PC VoIP System BG n.2 BG n.3 STB / PC STB / PC STB / PC 69

70 Admission Control Ability to reserve set BW for video services per interface Ability to limit the flows that are admitted on an interface based on set criteria Admission Control is needed when bandwidth utilization starts approaching interface bandwidth Required for both multicast and unicast services TS can perform Admission Control Requires bandwidth requests to be signaled to the TS 70

71 Admission Control and QoS Multicast: IGMP Admission Control / Authorization IGMP Join IP Network Multicast Video Source TS DBC IP STB/PC TS forwards multicast video streams based on IGMP traffic from STB/PC TS pre-configured with video service class TS is configured with service-class per multicast group address TS performs admission control TS can perform multicast authorization 71

72 Admission Control and QoS Multicast: PM Policy Server PM Application Manager IP Network Admission Control Multicast TS DBC IP STB/PC Video Source Multicast extensions added to latest version of PM spec (PM I05) TS dynamically forwards multicast video streams based on PM signaling Policy Server performs authorization checks and signals TS with QoS requirements Upon receipt of Gate-Set, TS creates classifier and service flow and reserves BW Flexible forwarding to cable interface based on service flow attributes 72

73 Admission Control and QoS VoD: RSVP RSVP PATH (to STB) Admission Control VoD Streamer RSVP RESV TS IP STB/PC Entitlement performed prior to initiating the above sequence TS pre-configured with video service class Flexible forwarding to cable interface based on service flow attributes Upon receipt of RSVP, TS creates classifier and service flow and reserves BW 73

74 VOD: Video On Demand Signaling based approach for reserving DOCSIS QOS RSVP (Resource Reservation Protocol) used for signaling QOS TS acts as RSVP proxy and terminates RSVP STB is unaware of RSVP signaling 74

75 Admission Control and QoS VoD: PM PM Policy Server Application Manager Admission Control IP Network VOD streamer TS IP STB/PC TS forwards unicast video streams based on PM signaling Policy Server performs authorization checks and signals TS with QoS requirements Upon receipt of Gate-Set, TS creates classifier and service flow and reserves BW Flexible forwarding to cable interface based on service flow attributes 75

76 Video Over DOCSIS TelePresence over DOCSIS Overview (VDOC) Tutorial 76

77 TelePresence over DOCSIS (TPoD) Overview TelePresence is a technology that allows people who are in physically separate locations to communicate with each other as if they were in the same room. TelePresence combines professional video, professional audio, and networking to create a real-time in-person experience. TPoD could be for one of the following markets: Teleworker: The user is an employee of an enterprise and is working at home. The TelePresence is generally owned and operated on behalf of the corporation, and the service provider is providing transport. Consumer TelePresence: The user is a consumer who wants to use TelePresence for their own personal use. The service is managed by the service provider (SP) or by a third party. The service provider provides transport. for network connectivity 77

78 Business TelePresence over DOCSIS drivers Teleworker/SOHO with Enterprise Hosted TP services Premium HSD Tier or BoD - Permanent Teleworker -24 hr biz, work & at home -VIPs, Sr. Management, etc Enterprise B Enterprise A Home Gateway DMVPN over WWW Managed VPN MSO Network DOCSIS QoS Bandwidth on Demand End-to-end QoS Home Gateway Small Office B Enterprise Services QoS Extension - Small/Branch offices, Kiosks, Remote Teller, Expert Help, etc Teleworker Enterprise A C2C & C2B - Distant Friends & Family, - Doctor, Concierge, Yellow Pages Consumer 78

79 Video Over DOCSIS Summary/ Q&A (VDOC) Tutorial 79

80 Summary Increasing interest in IPTV and other video based services over DOCSIS VDOC Architecture highly leverages DOCSIS 3.0 and M-TS IP Video services are evolving. Replacement of current services will likely not be good enough. Service velocity will eventually require the full suite of DOCSIS services Have to demonstrate the value of IP PacketCable Multimedia and RSVP can be used to enable the dynamic creation, modification, and deletion of QoS for these video based services TelePresence enables communication between remote parties as if they were sitting in the same room User Experience New Devices New Content Service Velocity Capex Savings Opex Savings Efficiency 80

81 Questions/Answers 81