Abstract: A novel method for provisioning network services for a cable system is provided. The method provides a configuration command interpreter/compiler that receives configuration commands of the cable system and generates configuration commands understood by the actual physical devices implementing the cable system. The interpreter transforms the configuration commands of the cable system into the configuration commands of the actual physical devices based on a set of normalized data models describing the cable system. The normalized data models are applicable to the cable system regardless of the actual devices implementing the cable system. The normalized data models are specified using normalized parameters that are generally applicable to different types devices that can be used to implement the cable system.

Abstract: A novel method of handling network traffic for cable service flows in a distributed cable system is presented. Such a cable systems use remote distribution nodes in the fields to handle RF communications with cable modems in a distributed fashion. A packet engine is configured to assign a logical interface to each cable service flow in the cable system. Each logical interface in the packet engine is uniquely identifiable by a compound identifier that includes the identifier of the corresponding service flow and the identifier of the remote distribution node. The packet engine is configurable to selectively provide L3 level routing or L2 level switching/bridging between different logical interfaces. In some embodiments, the controller selects between configuring the packet engine to perform L3 routing or configuring the packet engine to perform L2 bridging based on whether the packet engine support unnumbered interfaces and integrated routing and bridging (IRB).

Abstract: A novel method of handling network traffic for cable service flows in a distributed cable system is presented. Such a cable systems use remote distribution nodes in the fields to handle RF communications with cable modems in a distributed fashion. A packet engine is configured to assign a logical interface to each cable service flow in the cable system. Each logical interface in the packet engine is uniquely identifiable by a compound identifier that includes the identifier of the corresponding service flow and the identifier of the remote distribution node. Upon receiving upstream data packet from a particular cable service flow, the remote distribution node applies a set of tags or labels to the data packet identifying the data packet as being from the particular cable service flow. The remote distribution node then forwards the tagged packet toward the packet engine, where the tags/labels are used to direct the packet toward the corresponding logical interface of the particular cable service flow.

Abstract: A novel method of handling network traffic for cable service flows in a distributed cable system is presented. Such a cable systems use remote distribution nodes in the fields to handle RF communications with cable modems in a distributed fashion. A packet engine is configured to assign a logical interface to each cable service flow in the cable system. Each logical interface in the packet engine is uniquely identifiable by a compound identifier that includes the identifier of the corresponding service flow and the identifier of the remote distribution node. Each service flow is assigned a class of service (CoS) at the packet engine and guarantee a certain level of quality of service (QoS). In some embodiments, each cable service flow is assigned a CoS priority number. For each possible CoS priority number, the packet engine is configured to provide certain resources at certain quality level, i.e., certain level of QoS.

Abstract: A novel method of handling network traffic for cable service flows in a distributed cable system is presented. Such a cable systems use remote distribution nodes in the fields to handle RF communications with cable modems in a distributed fashion. A packet engine is configured to assign a logical interface to each cable service flow in the cable system. Each logical interface in the packet engine is uniquely identifiable by a compound identifier that includes the identifier of the corresponding service flow and the identifier of the remote distribution node. Upon receiving upstream data packet from a particular cable service flow, the remote distribution node applies a set of tags or labels to the data packet identifying the data packet as being from the particular cable service flow. The remote distribution node then forwards the tagged packet toward the packet engine, where the tags/labels are used to direct the packet toward the corresponding logical interface of the particular cable service flow.

Abstract: A novel method of handling network traffic for cable service flows in a distributed cable system is presented. Such a cable systems use remote distribution nodes in the fields to handle RF communications with cable modems in a distributed fashion. A packet engine is configured to assign a logical interface to each cable service flow in the cable system. Each logical interface in the packet engine is uniquely identifiable by a compound identifier that includes the identifier of the corresponding service flow and the identifier of the remote distribution node. The packet engine is configurable to selectively provide L3 level routing or L2 level switching/bridging between different logical interfaces. In some embodiments, the controller selects between configuring the packet engine to perform L3 routing or configuring the packet engine to perform L2 bridging based on whether the packet engine support unnumbered interfaces and integrated routing and bridging (IRB).

Abstract: A novel method for provisioning network services for a cable system is provided. The method provides a configuration command interpreter/compiler that receives configuration commands of the cable system and generates configuration commands understood by the actual physical devices implementing the cable system. The interpreter transforms the configuration commands of the cable system into the configuration commands of the actual physical devices based on a set of normalized data models describing the cable system. The normalized data models are applicable to the cable system regardless of the actual devices implementing the cable system. The normalized data models are specified using normalized parameters that are generally applicable to different types devices that can be used to implement the cable system.

Abstract: A novel method of handling network traffic for cable service flows in a distributed cable system is presented. Such a cable systems use remote distribution nodes in the fields to handle RF communications with cable modems in a distributed fashion. A packet engine is configured to assign a logical interface to each cable service flow in the cable system. Each logical interface in the packet engine is uniquely identifiable by a compound identifier that includes the identifier of the corresponding service flow and the identifier of the remote distribution node. Each service flow is assigned a class of service (CoS) at the packet engine and guarantee a certain level of quality of service (QoS). In some embodiments, each cable service flow is assigned a CoS priority number. For each possible CoS priority number, the packet engine is configured to provide certain resources at certain quality level, i.e., certain level of QoS.

Abstract: A network system includes a provider backbone bridged network (PBBN) and a multi-homed provider bridge network (PBN) having an L2 switch that operate as backboned edge bridge (BEBs) to bridge L2 packets between the PBN and the PBBN. The L2 switch executes a PBBN routing instance and a separate PBN routing instance. A plurality of packet-forwarding engine (PFE) of the L2 switch are configured to forward L2 packets between interfaces of the PBN routing instance and the PBBN routing instance. The PFEs store L2 network address tables that specify L2 network addresses reachable by the interfaces. The PFEs of the L2 switch are configured to selectively share L2 network addresses between the L2 network address tables of the PBN routing instance and the L2 network address tables of the PBBN routing instance.