Virtual converged cable access platform (CCAP) core

• US 10,020,962 B2
• Filed: 02/21/2017
• Issued: 07/10/2018
• Est. Priority Date: 02/22/2016
• Status: Active Grant

• Current Assignee: Harmonic Incorporated
• Original Assignee: Harmonic Incorporated
• Inventors: Patrick, Michael W., Elfassy, Nitsan S., Leventer, Amir, Rosenberg, Jeremy C.
• Primary Examiner(s): Elpenord, Candal
• Application Number:
  US15/438,432
• Publication Number:
  US 20170244577A1
• Time in Patent Office: 504 Days
• Field of Search: 370252, 370463
• CPC Class Codes: H04L 12/2801 Broadband local area networks
• CPC Class Codes: H04L 12/4633 Interconnection of networks using encapsulation techniques, e.g. tunneling
• CPC Class Codes: H04L 12/4641 Virtual LANs, VLANs, e.g. virtual private networks [VPN] LAN interconnection over a bridge based backbone H04L12/462; encapsulation techniques H04L12/4633; routing of packets H04L45/00; packet switches H04L49/00; virtual private networks for security H04L63/0272
• CPC Class Codes: Y02D 30/50 in wire-line communication networks, e.g. low power modes or reduced link rate

Abstract

Approaches for a virtualized Cable Modem Termination System (CMTS) for providing high speed data services to a remote physical device (RPD). The virtualized Cable Modem Termination System (CMTS) comprises a core routing engine (CRE) for performing packet switching and routing and one or more core servers (CS) that each perform CMTS functions for the one or more remote physical devices (RPDs). The core routing engine may comprise one or more core routing engine members. The core routing engine (CRE) and the one or more core servers (CS) are each implemented entirely on commercial off-the-shelf (COTS) hardware.

Claims

1. One or more non-transitory machine-readable storage mediums storing one or more sequences of instructions for a virtualized Cable Modem Termination System (CMTS), which when executed by one or more processors, cause:

said virtualized Cable Modem Termination System (CMTS) providing high speed data services to one or more remote physical devices (RPDs), wherein said virtualized Cable Modem Termination System (CMTS) comprises;

a core routing engine (CRE) performing packet switching and routing; and

one or more core servers (CSs) that each perform CMTS functions for said one or more remote physical devices (RPDs),

wherein said core routing engine (CRE) and said one or more core servers (CSs) are each implemented entirely on commercial off-the-shelf (COTS) hardware.

2. The one or more non-transitory machine-readable storage mediums of claim 1, wherein said core routing engine (CRE) dynamically allocates resources of said virtualized Cable Modem Termination System (CMTS) between downstream packet forward and upstream packet forwarding.

3. The one or more non-transitory machine-readable storage mediums of claim 1, wherein said commercial off-the-shelf (COTS) hardware implementing said core routing engine (CRE) and said one or more core servers (CSs) are arranged in one or more clusters to performing Network Function Virtualization (NFV).

4. The one or more non-transitory machine-readable storage mediums of claim 1, wherein a combination of said core routing engine (CRE) and said one or more core servers (CSs) emulate a single Layer 3 CMTS with a single point of management for both routing and DOCSIS mac domain operation.

5. The one or more non-transitory machine-readable storage mediums of claim 1, wherein said core routing engine (CRE) implements a Link Aggregation Group (LAG) of at least two Ethernet ports for connections to other network elements including two or more of:

(1) a first set of switch or routers that connect to the Internet via a Network Systems Interface (NSI), (2) a second set of switch or routers that connect towards head-ends and the one or more remote physical devices (RPDs) via a Converged Interconnect Network (CIN), and (3) trunk connections to said one or more core servers (CS).

6. The one or more non-transitory machine-readable storage mediums of claim 1, wherein operation of said core routing engine (CRE) and said one or more core servers (CS) are configured using a single configuration file maintained by one of said one or more core servers (CS).

7. The one or more non-transitory machine-readable storage mediums of claim 1, wherein said core routing engine (CRE) comprises a NSI virtual route forwarder (VRF) for routing public Internet traffic and a DSI virtual route forwarder (VRF) for routing cable operator private Converged Interconnect Network (CIN) traffic, and wherein said NSI VRF is separate and distinct from said DSI VRF.

8. The one or more non-transitory machine-readable storage mediums of claim 1, wherein one of said two or more core servers is designated as a virtual CCAP core manager (VCCM).

9. The one or more non-transitory machine-readable storage mediums of claim 1, wherein each core server (CS), of said one or more core servers (CSs), connects to the core routing engine (CRE) with a Link Aggregation Group (LAG) of two or more Ethernet links.

10. The one or more non-transitory machine-readable storage mediums of claim 1, wherein said one or more core servers (CSs) comprises at least two core servers (CSs), and wherein responsibility for any CMTS function performed by a first core server (CS) of said at least two core servers (CSs) is assumed by a second core server (CS) of said at least two core servers (CSs) when said first core server (CS) fails.

11. The one or more non-transitory machine-readable storage mediums of claim 1, wherein one core server, of said one or more core servers (CSs), implements a virtual IP address to which the one or more remote physical devices (RPDs) communicate.

12. The one or more non-transitory machine-readable storage mediums of claim 1, wherein each core server, of said one or more core servers (CSs), implements a separate L2TPv3 Logical Control Connection Endpoint (LCCE) IP address via which the one or more remote physical devices (RPDs) communicate.

13. The one or more non-transitory machine-readable storage mediums of claim 1, wherein Virtual LANs (VLANS) are employed on Ethernet links between the core routing engine (CRE) and the one or more core servers (CSs).

14. The one or more non-transitory machine-readable storage mediums of claim 1, wherein Multiprotocol Label Switching (MPLS) Transport Stream tunnels are employed on Ethernet links between the core routing engine (CRE) and the one or more core servers (CSs).

15. The one or more non-transitory machine-readable storage mediums of claim 1, wherein Ethernet links are established between the core routing engine (CRE) and the one or more core servers (CSs), wherein one or more of:

(a) a Virtual LAN (VLAN) and (b) a Multiprotocol Label Switching (MPLS) Transport Stream tunnel are employed on said Ethernet links, and wherein the VLAN or the MPLS tunnel encapsulates traffic for a Virtual Routing Function (VRF) implemented on the core routing engine (CRE).

16. The one or more non-transitory machine-readable storage mediums of claim 1, wherein Ethernet links are established between the core routing engine (CRE) and the one or more core servers (CSs), wherein one or more of:

(a) a Virtual LAN (VLAN) and (b) a Multiprotocol Label Switching (MPLS) Transport Stream tunnel are employed on said Ethernet links, and wherein the VLAN or the MPLS tunnel encapsulates traffic for IP hosts within a single CMTS cable bundle.

17. The one or more non-transitory machine-readable storage mediums of claim 1, wherein Ethernet links are established between the core routing engine (CRE) and the one or more core servers (CSs), wherein one or more of:

(a) a Virtual LAN (VLAN) and (b) a Multiprotocol Label Switching (MPLS) Transport Stream tunnel are employed on said Ethernet links, and wherein the VLAN or the MPLS tunnel encapsulates traffic for IP hosts in a single CMTS cable bundle for IP hosts distinguished by criteria gleaned from the DHCP protocol performed by those IP hosts.

18. The one or more non-transitory machine-readable storage mediums of claim 17, wherein the criteria gleaned from the DHCP protocol is the Embedded Service/Application Functional Entity (eSAFE) type of the IP hosts.

19. The one or more non-transitory machine-readable storage mediums of claim 1, wherein Ethernet links are established between the core routing engine (CRE) and the one or more core servers (CSs), wherein one or more of:

(a) a Virtual LAN (VLAN) and (b) a Multiprotocol Label Switching (MPLS) Transport Stream tunnel are employed on said Ethernet links, and wherein separate VLAN or MPLS tunnels encapsulated traffic for connection to the Network Side Interface (NSI) northbound of a traditional CMTS or a DOCSIS Side Interface (DSI) southbound of a traditional CMTS.

20. The one or more non-transitory machine-readable storage mediums of claim 1, wherein one of the core servers (CSs) implements a virtual IP address intended for management functions of the virtual CMTS.

21. The one or more non-transitory machine-readable storage mediums of claim 20, wherein said management functions include access to said virtual CMTS using one or more of the following protocols:

Secure Shell (SSH), Simple Network Management Protocol (SNMP), Telnet, Trivial File Transfer Protocol (TFTP), and File Transfer Protocol (FTP).

22. The one or more non-transitory machine-readable storage mediums of claim 1, wherein Ethernet links are established between the core routing engine (CRE) and the one or more core servers (CSs), wherein one or more of:

(a) a Virtual LAN (VLAN) and (b) a Multiprotocol Label Switching (MPLS) Transport Stream tunnel are employed on said Ethernet links, and wherein the VLAN or the MPLS tunnel carries traffic for a single DOCSIS L2VPN virtual LAN service.

23. The one or more non-transitory machine-readable storage mediums of claim 1, wherein the core routing engine (CRE) comprises two or more separate chassis members.

24. The one or more non-transitory machine-readable storage mediums of claim 23, wherein each core server (CS), of the one or more core servers (CSs), connects to at least two different Core Routing Engine (CRE) members.

25. An apparatus for operating a virtualized Cable Modem Termination System (CMTS), comprising:

one or more processors; and

one or more non-transitory computer-readable storage mediums storing one or more sequences of instructions, which when executed, cause;

said virtualized Cable Modem Termination System (CMTS) for providing high speed data services to one or more remote physical devices (RPDs), wherein said virtualized Cable Modem Termination System (CMTS) comprises;

a core routing engine (CRE) performing packet switching and routing; and

one or more core servers (CSs) that each perform CMTS functions for said one or more remote physical devices (RPDs),

wherein said core routing engine (CRE) and said one or more core servers (CSs) are each implemented entirely on commercial off-the-shelf (COTS) hardware.

26. A method for operating a virtualized Cable Modem Termination System (CMTS), comprising:

said virtualized Cable Modem Termination System (CMTS) for providing high speed data services to one or more remote physical devices (RPDs), wherein said virtualized Cable Modem Termination System (CMTS) comprises;

a core routing engine (CRE) performing packet switching and routing; and

one or more core servers (CSs) that each perform CMTS functions for said one or more remote physical devices (RPDs),

wherein said core routing engine (CRE) and said one or more core servers (CSs) are each implemented entirely on commercial off-the-shelf (COTS) hardware.