CONTENTS

COVER

SERIES PAGE

TITLE PAGE

COPYRIGHT PAGE

PREFACE

CONTRIBUTORS

1 INTRODUCTION AND OVERVIEW

1.1 INTRODUCTION

1.2 RESIDENTIAL NETWORK ARCHITECTURES AND SERVICES

1.3 OAMPT (OPERATIONS, ADMINISTRATION, MAINTENANCE, PROVISIONING, TROUBLESHOOTING) FOR RESIDENTIAL SERVICES

1.4 BUSINESS NETWORK ARCHITECTURES AND SERVICES

1.5 OAMPT FOR BUSINESS SERVICES

1.6 FUTURE DIRECTIONS IN CABLE NETWORKS, SERVICES AND MANAGEMENT

2 RESIDENTIAL NETWORK ARCHITECTURES AND SERVICES

2.1 INTRODUCTION

2.2 DOCSIS 3.0/3.1 ARCHITECTURE AND SERVICES

2.3 PacketCable ARCHITECTURE AND SERVICES

2.4 IMS ARCHITECTURE AND SERVICES

2.5 IPTV ARCHITECTURE AND SERVICES

2.6 CDN ARCHITECTURE AND SERVICES

2.7 CCAP ARCHITECTURES AND SERVICES

2.8 WI-FI ARCHITECTURE AND SERVICES

2.9 CONCLUSION

REFERENCES

3 OPERATIONS, ADMINISTRATION, MAINTENANCE, PROVISIONING, AND TROUBLESHOOTING FOR RESIDENTIAL SERVICES

3.1 INTRODUCTION

3.2 OPERATIONAL SYSTEMS AND MANAGEMENT ARCHITECTURES

3.3 SERVICE ORDERS

3.4 PROVISIONING

3.5 FAULT MANAGEMENT

3.6 PERFORMANCE MANAGEMENT

3.7 BILLING SYSTEMS AND FORMATS

3.8 SECURITY

3.9 CONCLUSION

REFERENCES

4 BUSINESS NETWORK ARCHITECTURES AND SERVICES

4.1 INTRODUCTION

4.2 METRO ETHERNET ARCHITECTURE AND SERVICES

4.3 DPoE ARCHITECTURE AND SERVICES

4.4 EPoC ARCHITECTURE AND SERVICES

4.5 BUSINESS VOICE

4.6 CONCLUSION

REFERENCES

5 OPERATIONS, ADMINISTRATION, MAINTENANCE, PROVISIONING, AND TROUBLESHOOTING FOR BUSINESS SERVICES

5.1 INTRODUCTION

5.2 OPERATIONS SYSTEMS AND MANAGEMENT ARCHITECTURES

5.3 SERVICE ORDERS

5.4 PROVISIONING

5.5 FAULT MANAGEMENT

5.6 PERFORMANCE MANAGEMENT

5.7 BILLING SYSTEMS AND FORMATS

5.8 SECURITY

5.9 CONCLUSION

REFERENCES

6 FUTURE DIRECTIONS IN CABLE NETWORKS, SERVICES AND MANAGEMENT

6.1 INTRODUCTION

6.2 CLOUD SERVICES

6.3 VIRTUALIZATION

6.4 NETWORK FUNCTIONS VIRTUALIZATION

6.5 SOFTWARE-DEFINED NETWORKS

6.6 SELF-MANAGED NETWORKS

6.7 CONCLUSION

REFERENCES

INDEX

END USER LICENSE AGREEMENT

List of Tables

Chapter 02

Table 2.1. Community Wi-Fi Service Parameters

Chapter 03

Table 3.1. CM Management Servers

Table 3.2. CMTS/CCAP Management Servers

Table 3.3. SNMP MIBS for Certificate Management [14]

Table 3.4. SNMP MIBs for Managing Key Exchange [14]

Table 3.5. Configuration File TLV Encodings for Managing Key Exchange [13]

Table 3.6. SNMP MIBs for Managing SAV [12]

Table 3.7. PacketCable 1.5 Security Interfaces

Table 3.8. Provisioning Flows [17]

Table 3.9. Description of Provisioning Flows [17]

Table 3.10. Configuration File MIB Objects [18]

Table 3.11. Post-MTA Provisioning Security Flows [18]

Table 3.12. Packet Cable PKI Certificates

Table 3.13. PacketCable 1.5 Security MIBs [18]

Table 3.14. Access Domain Reference Points Description [20]

Chapter 04

Table 4.1. MAC Addresses for L2 Control Protocols

Table 4.2. EVC Types and Service Codes/Modifiers

Table 4.3. UNI Port Speeds and Associated Service Codes/Modifiers

Table 4.4. Parameters of H, M, and L Classes

Table 4.5. An Example of PCP—CoS Mapping

Table 4.6. DSCP—CoS Mapping

Table 4.7. MEF Three CoS Bandwidth Constraints, and PCP and DSCP Mapping [70]

Table 4.8. SLAs for Point-to-Point EVCs of Three Service Categories (i.e., CoS), Spanning No More Than 250 Network km with 2 ms Propagation Delay of Metro Distances

Table 4.9. SLAs for Point-to-Point EVCs of Three Service Categories (i.e., CoS), Spanning No More Than 1200 km with 8 ms Propagation Delay of Regional Distances

Table 4.10. SLAs for Point-to-Point EVCs of Three Service Categories (i.e., CoS), Spanning No More Than 7000 km with 44 ms Propagation Delay of National/Continental Distances

Table 4.11 SLAs for Point-to-Point EVCs of Three Service Categories (i.e., CoS), Spanning No More Than 27,500 km with 44 ms Propagation Delay of Global/Intercontinental Distances

Table 4.12 Carrier Ethernet Services

Table 4.13. Basic OVC Services

Chapter 05

Table 5.1. The Full De-coded Type Length Value Data for a Typical DPoE ONU Configuration

Table 5.2. The Full Coded Type Length Value Data for a Typical DPoE ONU Configuration

Table 5.3. Description of Each TLV and sub-TLV

Table 5.4. MEG Levels

Table 5.5. SNMP MIBS for Certificate Management [30]

Table 5.6. SNMP MIB for DPoE Key Exchange

Table 5.7. SNMP MIBs for Managing SAV [30]

Chapter 06

Table 6.1. Standards Organizations for Cloud

Table 6.2. Actors in Cloud Computing

Table 6.3. OpenFlow Matching Parameters, Actions, and Statistics

List of Illustrations

Chapter 02

Figure 2.1. DOCSIS high-speed data or HSD services.

Figure 2.2. Data-over-cable reference architecture from PHY v3.0 [1].

Figure 2.3. DOCSIS 3.0 supported frequency bands.

Figure 2.4. DOCSIS 3.1 supported frequency bands.

Figure 2.5. QoS process.

Figure 2.6. PacketCable 1.5 architecture.

Figure 2.7. Comparing PacketCable 1.5 and 2.0.

Figure 2.8. IMS half-call model.

Figure 2.9. IMS architecture overview.

Figure 2.10. Registration—1st REGISTER request.

Figure 2.11. Registration—2nd REGISTER request.

Figure 2.12. Session establishment.

Figure 2.13. Video delivery from programmers to MSOs.

Figure 2.14. Example of multiple satellite-based reception sites for a single MSO (Adobe, 2012).

Figure 2.15. Video file segmentation and delivery.

Figure 2.16. ABR ad insertion.

Figure 2.17. Delivery of a web asset without and with a caching server.

Figure 2.18. Original use of CDN to cache large graphic files for websites.

Figure 2.19. CDN component overview.

Figure 2.20. Hierarchical cache algorithms cause caches to pull content from the most efficient peer.

Figure 2.21. Modular CMTS network diagram from MULPIv3.1.

Figure 2.22. MHA architecture.

Figure 2.23. Combined EPON and RFOG.

Figure 2.24. Distributed CCAP architecture: Remote PHY.

Figure 2.25. CCAP migration, technology and HFC evolution.

Figure 2.26. Community Wi-Fi home hotspots.

Figure 2.27. Public Wi-Fi hotspot.

Figure 2.28. Wireless service locator, WSL.

Figure 2.29. WSL database for sharing access point location data.

Chapter 03

Figure 3.1. Cable modem management architecture.

Figure 3.2. CMTS/CCAP management architecture.

Figure 3.3. CM configuration management via configuration file download process.

Figure 3.4. CM secure software download process.

Figure 3.5. IPDR/SP network model.

Figure 3.6. Simplified view of business and service management layer.

Figure 3.7. DOCSIS certificate PKI hierarchy.

Figure 3.8. Access domain reference points.

Figure 3.9. Internetwork domain reference points.

Figure 3.10. IMS registration message flow.

Figure 3.11. SIP digest authentication.

Figure 3.12. Transport security.

Chapter 04

Figure 4.1. Basic network reference model [2].

Figure 4.2. Metro Ethernet network interfaces.

Figure 4.3. Protocol stack of Metro Ethernet networks [2].

Figure 4.4. Ethernet frame.

Figure 4.5. C-Tag and S-Tag.

Figure 4.6. (a) CPE supporting UNI (b) NID supporting UNI.

Figure 4.7. UNI and EVC relationship.

Figure 4.8. ENNI, EVC, and OVC.

Figure 4.9. Example of supporting multiple OEPs for one OVC.

Figure 4.10. UNI Tunnel Access (UTA) enabling EVC service frames associated with a remote user’s UNI to be tunneled through an Off-Net providers’ network [5].

Figure 4.11. Network topology with SP placing its own NID.

Figure 4.12. Network topology with SP relying on AP.

Figure 4.13. EVC types.

Figure 4.14. EPL example.

Figure 4.15. EVPL service.

Figure 4.16. E-PLAN service.

Figure 4.17. E-VPLAN service.

Figure 4.18. EP-Tree service.

Figure 4.19. EVP-Tree Service.

Figure 4.20. Access EPL service [10].

Figure 4.21. Access EVPL service [10].

Figure 4.22. Network topology with AP offering vNID functionality.

Figure 4.23. E-LAN service from a SP.

Figure 4.24. E-LAN service from a SP.

Figure 4.25. PON topology, (a) downstream frame and (b) upstream frame transmission.

Figure 4.26. DOCSIS provisioning of both DOCSIS and DPoE networks.

Figure 4.27. DOCSIS cable modem represented by vCM and ONU.

Figure 4.28. Four-step device provisioning process for DOCSIS and DPoE.

Figure 4.29. Service provisioning concepts as applied to an ONU.

Figure 4.30. Encapsulation operation in which tags are added to an Ethernet frame.

Figure 4.31. DPoE network architecture with EPoC fiber coax units.

Figure 4.32. Migration to FTTH with EPoC technology.

Figure 4.33. Hosted IP-Centrex architecture.

Figure 4.34. SIP Trunking architecture.

Figure 4.35. 3GPP IMS “loose route” registration procedure.

Figure 4.36. RFC 6140 “GIN” registration procedure.

Figure 4.37. Typical hosted IP-Centrex deployment.

Figure 4.38. ESG functions.

Figure 4.39. Provisioning gateway hierarchy diagram.

Chapter 05

Figure 5.1. Organization of typical MSO “systems” including back-office, OSS, and Operations systems.

Figure 5.2. Manual service provisioning.

Figure 5.3. Automatic service provisioning.

Figure 5.4. Detailed view of MPT systems.

Figure 5.5. XML example.

Figure 5.6. JSON object example.

Figure 5.7. XML object example.

Figure 5.8. Hexadecimal representation of TLV.

Figure 5.9. Link OAM use case.

Figure 5.10. CCM use case.

Figure 5.11. Loopback use case.

Figure 5.12. Linktrace use case.

Figure 5.13. Lock/Test use case.

Figure 5.14. Hierarchical OAM domains.

Figure 5.15. Frame loss ratio use case using DMM/DMR.

Figure 5.16. Frame loss ratio use case using SLM/SLR.

Figure 5.17. Frame loss ratio use case using 1SL.

Figure 5.18. Frame delay use case using 1DM.

Figure 5.19. Frame delay use case using DMM/DMR.

Figure 5.20. MEPs reporting PM metrics into back-office.

Figure 5.21. Simplified view of business services order management & billing vs residential.

Figure 5.22. DPoE certificate PKI hierarchy.

Chapter 06

Figure 6.1. NIST Cloud Computing Reference Architecture (CCRA). Reproduced from Ref. [2].

Figure 6.2. Interactions between the actors in cloud computing. Reproduced from Ref. [2].

Figure 6.3. Usage scenario for cloud carriers.

Figure 6.4. Usage scenario for cloud brokers.

Figure 6.5. Usage scenario for cloud auditors.

Figure 6.6. Example services for (a) SaaS, (b) IaaS, and (c) PaaS cloud consumer.

Figure 6.7. Scope of controls between provider and consumer.

Figure 6.8. Public cloud.

Figure 6.9. Private cloud.

Figure 6.10. On-site community cloud.

Figure 6.11. Hybrid cloud.

Figure 6.12. Cloud system layers.

Figure 6.13. Cloud service management components.

Figure 6.14. Cloud carrier acting as a cloud broker [9].

Figure 6.15. Cloud service provider acting as a cloud broker. Reproduced from Ref. [9].

Figure 6.16. Cloud broker providing broker service for Ethernet Cloud Carrier and cloud service provider [9].

Figure 6.17. EPL connecting cloud consumers to cloud service provider. Reproduced from Ref. [9].

Figure 6.18. EVPLs from two cloud consumers multiplexed at cloud service provider’s UNI. Reproduced from Ref. [9].

Figure 6.19. EP-tree to interconnect cloud consumers with cloud service provider data centers. Reproduced from Ref. [9].

Figure 6.20. Example EVP-tree use case with EVPLs used to provide Internet connectivity. Reproduced from Ref. [9].

Figure 6.21. EP-LAN interconnecting cloud consumer sites with cloud service provider data centers.

Figure 6.22. Network interconnecting infrastructure.

Figure 6.23. Reference multilayer cloud service model (CSM). Reproduced from Figure 3 of Ref. [10].

Figure 6.24. Intercloud Control and Management Plane providing single control and management domain to heterogeneous intercloud infrastructure. Reproduced from Ref. [10].

Figure 6.25. Virtualized server with hypervisor layer [11].

Figure 6.26. Generic reference model for DC network virtualization over a layer 3 infrastructure. Reproduced from Ref. [13].

Figure 6.27. A hypervisor architecture.

Figure 6.28. A generic architecture for data centers.

Figure 6.29. Generic reference model for NV Edge.

Figure 6.30. NVO3 encapsulated frame.

Figure 6.31. OAM layers in an NVO3 network.

Figure 6.32. NVO3 for Tenant End System (TES) interconnection.

Figure 6.33. DC virtual network access via the Internet.

Figure 6.34. L3 VNI and L3 VPN interconnection across multinetworks.

Figure 6.35. Tenant virtual network with bridging/routing.

Figure 6.36. Virtual Data Center by using NVO3.

Figure 6.37. VN formed of EVCs where DCs and network are provided by one service provider.

Figure 6.38. VN formed of EVCs where DCs and network are provided by different service providers.

Figure 6.39. NFV framework.

Figure 6.40. End-to-end service.

Figure 6.41. An example Metro Ethernet Network.

Figure 6.42. SDN layers.

Figure 6.43. Layers of SDN.

Figure 6.44. Main components of an OpenFlow switch.

Figure 6.45. Packet flow in an OpenFlow switch.

Figure 6.46. Flow header.

Figure 6.47. SDN architecture for optical networks.

Figure 6.48. SDN architecture for a Virtual Data Center.

Figure 6.49. SDN with L3 virtualization.

Figure 6.50. Mapping of MEF specifications to SDN layers.

Figure 6.51. A likely SDN architecture for DOCSIS networks.

Figure 6.52. Centrally self-managed network architecture.

Figure 6.53. A centrally self-managed network architecture example.

Figure 6.54. Self-managed NE architecture.

Figure 6.55. Architecture of self-managing NMS.

Figure 6.56. Self-managing NMS GUI.

Figure 6.57. Intelligent agent architecture.

Figure 6.58. Intelligent NE architecture.

Figure 6.59. Intelligent NMS architecture.

Figure 6.60. Distributed self-managed network architecture.

Figure 6.61. Virtual networks over an underlay network of multiple technologies.

Figure 6.62. Centrally self-managed virtual network architecture.

Figure 6.63. Centrally self-managed multiple virtual networks.

Figure 6.64. Distributed self-managed virtual network architecture.

Figure 6.65. SDN architecture.

Figure 6.66. Centrally self-managed SDN architecture.

Figure 6.67. Self-managed SDN NE architecture.

Figure 6.68. Distributed self-managed network architecture.

Figure 6.69. Frame format for self-managed Ethernet networks.

Figure 6.70. Centrally self-managed network architecture.

Figure 6.71. Process flow for fixing failures in distributed self-managed network.

Figure 6.72. Process of fixing failures in centrally self-managed virtual network.

Figure 6.73. Process of fixing failures in self- and distributedly managed virtual network.

Figure 6.74. Process for fixing failures in centrally self-managed SDN.

Figure 6.75. Process of fixing failures in distributed self-managed SDN.

Guide

Cover

Table of Contents

Begin Reading

Pages

ii

iii

iv

vii

viii

ix

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

61

62

63

64

65

66

67

68

69

70

71

72

73

74

75

76

77

78

79

80

81

82

83

84

85

86

87

88

89

90

91

92

93

94

95

96

97

98

99

100

101

102

103

104

105

106

107

108

109

110

111

112

113

114

115

116

117

118

119

120

121

122

123

124

125

126

127

128

129

130

131

132

133

134

135

136

137

138

139

140

141

142

143

144

145

146

147

148

149

150

151

152

153

154

155

156

157

158

159

160

161

162

163

164

165

166

167

168

169

170

171

172

173

174

175

176

177

178

179

180

181

182

183

184

185

186

187

188

189

190

191

192

193

194

195

196

197

198

199

200

201

202

203

204

205

206

207

208

209

210

211

212

213

214

215

216

217

218

219

220

221

222

223

224

225

226

227

228

229

230

231

232

233

234

235

236

237

238

239

240

241

242

243

244

245

246

247

248

249

250

251

252

253

254

255

256

257

258

259

260

261

262

263

264

265

266

267

268

269

270

271

272

273

274

275

276

277

278

279

280

281

282

283

284

285

286

287

288

289

290

291

292

293

294

295

296

297

298

299

300

301

302

303

304

305

306

307

308

309

310

311

312

313

314

315

316

317

318

319

320

321

322

323

324

325

326

327

328

329

330

331

332

333

334

335

336

337

338

339

340

341

342

343

344

345

346

347

348

349

350

351

352

353

354

355

356

357

358

IEEE Press
445 Hoes Lane
Piscataway, NJ 08854

IEEE Press Editorial Board
Tariq Samad, Editor in Chief

George W. Arnold
Dmitry Goldgof
Ekram Hossain
Mary Lanzerotti
Pui-In Mak
Ray Perez
Linda Shafer
MengChu Zhou
George Zobrist

Kenneth Moore, Director of IEEE Book and Information Services (BIS)

Cable Networks, Services, and Management

Edited by

Mehmet Toy

Copyright © 2015 by The Institute of Electrical and Electronics Engineers, Inc.

Published by John Wiley & Sons, Inc., Hoboken, New Jersey. All rights reserved
Published simultaneously in Canada

No part of this publication may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, electronic, mechanical, photocopying, recording, scanning, or otherwise, except as permitted under Section 107 or 108 of the 1976 United States Copyright Act, without either the prior written permission of the Publisher, or authorization through payment of the appropriate per-copy fee to the Copyright Clearance Center, Inc., 222 Rosewood Drive, Danvers, MA 01923, (978) 750-8400, fax (978) 750-4470, or on the web at www.copyright.com. Requests to the Publisher for permission should be addressed to the Permissions Department, John Wiley & Sons, Inc., 111 River Street, Hoboken, NJ 07030, (201) 748-6011, fax (201) 748-6008, or online at http://www.wiley.com/go/permissions.

Limit of Liability/Disclaimer of Warranty: While the publisher and author have used their best efforts in preparing this book, they make no representations or warranties with respect to the accuracy or completeness of the contents of this book and specifically disclaim any implied warranties of merchantability or fitness for a particular purpose. No warranty may be created or extended by sales representatives or written sales materials. The advice and strategies contained herein may not be suitable for your situation. You should consult with a professional where appropriate. Neither the publisher nor author shall be liable for any loss of profit or any other commercial damages, including but not limited to special, incidental, consequential, or other damages.

For general information on our other products and services or for technical support, please contact our Customer Care Department within the United States at (800) 762-2974, outside the United States at (317) 572-3993 or fax (317) 572-4002.

Wiley also publishes its books in a variety of electronic formats. Some content that appears in print may not be available in electronic formats. For more information about Wiley products, visit our web site at www.wiley.com.

Library of Congress Cataloging-in-Publication Data:

Cable networks, services and management / editor, Mehmet Toy.
  pages cm
 Includes bibliographical references.

 ISBN 978-1-118-83759-7 (hardback)
1. Integrated services digital networks. 2. Internet service providers–Management. 3. Home computer networks. 4. Cable television. I. Toy, Mehmet.
 TK5103.75.C33 2015
 384.068–dc23

      2014027711

PREFACE

Cable operators (MSOs) provide various types of voice, video, and data services to residential and commercial customers. The number of customers per operator is in the millions while the operator's network consists of equipment from various vendors. Compliance of equipment with international standards becomes a necessity for their interworking. Quality of service becomes a part of the contractual agreement with customers in commercial services.

Operations Support Systems, tools, and procedures for automation developed by the operators play an important role in managing these complex networks. Vendor-developed Network Management Systems (NMSs) and Element Management Systems (EMSs) are not widely used.

This is the first book describing cable networks, services, and their management in greater detail. The book is written by 13 experts in various fields covering network architectures and services, operations, administration, maintenance, provisioning, and troubleshooting (OAMPT) for residential services; network architectures, services, and OAMPT for business services; cloud, software-defined networks (SDN) and virtualization concepts and their applications as part of the future directions of cable networks. Finally, a proposed self-managed network concept is described.

The book begins by describing architecture and services for Data over Cable Service Interface Specification (DOCSIS) 3.0/3.1, Converged Cable Access Platform (CCAP), content distribution networks (CDNs), IP TV, and PacketCable and Wi-Fi for residential services. The book then follows with operational systems and management architectures, service orders, provisioning, fault management, performance management, billing systems and formats, and security for residential services.

Similar to residential services, the book describes architecture and services for Carrier Ethernet, DOCSIS provisioning over Ethernet Passive Optical Networks (EPON-DPoE), EPON Protocol over Coax (EPOC), CCAP, and IP Multimedia Subsystem (IMS) for business services. Following this, operational systems and management architectures, service orders, provisioning, fault management, performance management, billing systems and formats, and security for business services are explained.

As MSO networks and services change rapidly, future directions for cable networks are projected in Chapter 6 by describing cloud services, virtualization, SDN, and a self-managed network concept with their applications. I hope that this book provides guidance to all those involved in designing and operating MSO networks, researchers, and students.

I thank the co-authors who worked diligently to make this book a valuable reference; editors of IEEE Network Management series, Tom Plevyak and Dr. Veli Sahin, who asked me to write a book on cable networks and management, and provided valuable comments during the editing process; Mary Hatcher of John Wiley & Sons who helped greatly throughout the publication process; and Francois PascalRaj of SPi Global and Danielle LaCourciere of John Wiley & Sons who led the production of this book.

Mehmet Toy

Allendale, NJ

CONTRIBUTORS

Alireza Babaei, CableLabs, Denver, CO, USA

Victor Blake, Consultant, Leesburg, VA, USA

Niem Dang, Time Warner Cable, Herndon, VA, USA

Kirk Erichsen, Time Warner Cable, Colorado Springs, CO, USA

Sergio Gambro, Comcast Cable, Philadelphia, PA, USA

Kenneth Gould, Time Warner Cable, Herndon, VA, USA

Belal Hamzeh, CableLabs, Denver, CO, USA

David Hancock, CableLabs, Denver, CO, USA

Brian Hedstrom, OAM Technology Consulting, Denver, CO, USA

Stuart Hoggan, CableLabs, Denver, CO, USA

Curtis Knittle, CableLabs, Denver, CO, USA

Vikas Sarawat, CableLabs, Denver, CO, USA

Mehmet Toy, Comcast Cable, Mount Laurel, NJ, USA

1
INTRODUCTION AND OVERVIEW

Mehmet Toy

1.1 INTRODUCTION

Cable companies (multiple system operators or MSOs) have been offering phone and TV services over copper medium as the basic residential services for a long time. With the proliferation of broadband, fiber, and wireless technologies, fiber is deployed to provide TV, voice, and Internet services (i.e., triple play) while serving rates over cable are increased with new techniques in supporting triple-play services.

MSOs have been providing residential services over coaxial cable using the Data Over Cable Service Interface Specification (DOCSIS) protocol that permits the addition of high-speed data transfer to an existing cable TV (CATV) system in Mbps currently and aims at supporting capacities of at least 10 Gbps downstream and 1 Gbit/s upstream.

Lesen Sie weiter in der vollständigen Ausgabe!

Lesen Sie weiter in der vollständigen Ausgabe!

Lesen Sie weiter in der vollständigen Ausgabe!

Lesen Sie weiter in der vollständigen Ausgabe!

Lesen Sie weiter in der vollständigen Ausgabe!

Lesen Sie weiter in der vollständigen Ausgabe!

Lesen Sie weiter in der vollständigen Ausgabe!

Lesen Sie weiter in der vollständigen Ausgabe!